1、INTERNATIONAL TELECOMMUNICATION UNION)45G134 1 TELECOMMUNICATION (10/95)STANDARDIZATION SECTOROF ITU$)4!,G0G035“3#2)“%2G0G03).!,).3934%-G0G0.O G0G0 ).4%2!4%$G0G03%26)#%3G0G0$)4!,G0G0.%47/2+)3$.G9G0G0 G0G034!%G0G0 G0G0$%3#2)04)/.G0G0 or to move one terminal from one socket to another within one given
2、 basic access; or to move one call from one terminal to another terminal within one given basic access.The portability of a terminal during the Null call state is part of the basic access capabilities and does not require anyprocedure.The portability of a terminal in the call establishment and in th
3、e call clearing phases is not possible.It is a users responsibility to resume the call with a terminal which is compatible both with the remote terminal and thetype of connection previously established.The TP supplementary service is applicable to all circuit-switched telecommunication services requ
4、iring the attendanceof a human being, such as telephony, videotelephony, etc.The TP supplementary service does not apply to non-interactive services such as facsimile, teletex, mixed-mode,computer communication, etc. However, the network will not take any action to its applicability.Further part(s)
5、of this Recommendation shall specify the method of testing required to identify conformance to thisRecommendation.This Recommendation is applicable to equipment, supporting the TP supplementary service, to be attached at either sideof a T reference point or coincident S and T reference points when u
6、sed as an access to the public ISDN.4.2 ReferencesThe following Recommendations and other references contain provisions which, through reference in this text, constituteprovisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendationsand other refe
7、rences are subject to revision; all users of this Recommendation are therefore2 Recommendation Q.953 (10/95)encouraged to investigate the possibility of applying the most recent edition of the Recommendations and otherreferences listed below. A list of currently valid ITU-T Recommendations is regula
8、rly published.1 ITU-T Recommendation I.411 (1993), ISDN user-network interfaces Reference configurations.2 CCITT Recommendation I.130 (1988), Method for the characterization of telecommunication services supportedby an ISDN and network capabilities of an ISDN.3 ITU-T Recommendation clause 2/Q.954 (1
9、993), Stage 3 service description for multiparty supplementaryservices using DSS 1 Three-Party service.4 ITU-T Recommendation clause 2/Q.956 (1995), Integrated Services Digital Network (ISDN) Stage 3 servicedescription for charging supplementary services using DSS 1 Advice Of Charge.5 CCITT Recommen
10、dation I.253 (1988), Call completion supplementary services.6 ITU-T Recommendation Q.931 (1993), Digital Subscriber Signalling System No. 1 (DSS 1) ISDN user-networkinterface layer 3 specification for basic call control.7 ITU-T Recommendation Q.920 (1993), Digital Subscriber Signalling System No. 1
11、(DSS 1) ISDN user-networkinterface data link layer General aspects.8 ITU-T Recommendation clause 1/Q.957 (1993), Stage 3 description for additional information transfersupplementary services using DSS 1 User-to-User Signalling (UUS).4.3 DefinitionsFor the purposes of this Recommendation, the followi
12、ng definitions apply:4.3.1 connection endpoint identifier (CEI): See 3.4.1/Q.920 7.4.3.2 location interaction: An interaction of the protocol for two or more supplementary services where the serveduser (of all supplementary services) is on the same access.4.3.3 local interaction for the CEI: The cal
13、ls for which the local interaction exists are at the same access and areidentified by the same CEI.4.3.4 local interaction for the call: The local interaction exists on a single call, i.e. both supplementary services areinvoked by the same call.4.3.5 network: The DSS 1 protocol entity at the network
14、 side of the user-network interface.4.3.6 no impact: The interaction between the two identified supplementary services contains no requirements for theprotocol over and above the requirements of the Recommendation for each individual supplementary service.NOTE Other aspects of interactions that do n
15、ot affect the DSS 1 protocol are covered in the service description of therelevant supplementary service.4.3.7 not applicable: The interaction between the two identified supplementary services is outside the scope of thisRecommendation, e.g. the interaction is between the supplementary service and i
16、tself, and is therefore covered in theRecommendation for the individual supplementary service.4.3.8 remote interaction: An interaction of the protocol for two or more supplementary services where one user isthe served user for one supplementary service and (for the same call) the remote user for ano
17、ther supplementary service.The interaction for the served users supplementary service exists at the remote user.4.3.9 remote user: The DSS 1 protocol entity at the user side of the user-network interface which is involved in aninstance of this supplementary service, but which has no control of it.4.
18、3.10 user: The DSS 1 protocol entity at the user side of the user-network interface.Recommendation Q.953 (10/95) 34.4 AbbreviationsFor the purposes of this Recommendation, the following abbreviations are used:CEI Connection Endpoint IdentifierDSS 1 Digital Subscriber Signalling System No. 1ISDN Inte
19、grated Services Digital NetworkTP Terminal Portability4.5 DescriptionThe general description of the TP supplementary service is specified in clause 4/I.253 5.The procedures make use of the suspend and resume functions as described in Recommendation Q.931 6.4.6 Operational requirements4.6.1 Provision
20、/withdrawalThis supplementary service may be provided by a prior arrangement with the service provider or may be generallyavailable. Withdrawal shall be at the request of the customer or for administrative reasons.4.6.2 Requirements on the originating network sideThe procedures according to 5.6/Q.93
21、1 6 shall apply.4.6.3 Requirements on the destination network sideThe procedures according to 5.6/Q.931 6 shall apply.4.7 Coding requirementsAll parameters or parameter values required for the TP supplementary service are specified in Recommendation Q.9316. If the user provides IA5 characters in the
22、 Call identity information element, these shall be encoded with bit eight ofoctet three set to “0”.4.8 State definitionsThe states associated with basic call control according to clause 2/Q.931 6 shall apply.4.9 Signalling procedures at the coincident S and T reference point4.9.1 Invocation and oper
23、ation4.9.1.1 Normal operationFor call suspension, 5.6.1/Q.931 and 5.6.2/Q.931 6 shall apply.For call re-establishment, 5.6.4/Q.931 6 shall apply.4.9.1.2 Exceptional proceduresIn addition to the situations listed below, the normal error handling procedures according to 5.8/Q.931 6 shall apply: for ca
24、ll suspend error, 5.6.3/Q.931 6 shall apply; for call resume errors, 5.6.5/Q.931 6 shall apply; for call double suspension, 5.6.6/Q.931 6 shall apply.4.10 Procedures for interworking with private ISDNsThe procedures of 5.6.7/Q.931 6 shall apply.4 Recommendation Q.953 (10/95)4.11 Interaction with oth
25、er networks4.11.1 Interactions with non-ISDNsNo impact on the protocol.4.12 Interaction with other supplementary servicesThe following principle applies for the interaction of the TP supplementary service with other supplementary services, ifthe remote network or the remote user send a NOTIFY messag
26、e during the suspension phase of a call, then the networkof the suspending user shall discard this message.4.12.1 Call WaitingNo impact.4.12.2 Explicit Call TransferNo applicable interaction at this time.4.12.3 Connected Line Identification PresentationNo impact.4.12.4 Connected Line Identification
27、RestrictionNo impact.4.12.5 Calling Line Identification PresentationNo impact.4.12.6 Calling Line Identification RestrictionNo impact.4.12.7 Closed User GroupNo impact.4.12.8 Conference Calling4.12.8.1 The served user of the Conference supplementary service uses the TP supplementary service4.12.8.1.
28、1 Normal operationNo impact.NOTE The invocation of the TP supplementary service is not allowed for the served user of the Conferencesupplementary service.4.12.8.1.2 Exceptional proceduresIf, within the TP supplementary service, the network refuses a request to suspend a call because the call is part
29、 of aconference controlled by the same served user (local interaction for the call), or because another call for that CEI is partof a conference for which the served user is located at that CEI (local interaction for the CEI), the SUSPEND REJECTmessage shall contain cause value #29 “facility rejecte
30、d”.4.12.8.2 The remote user of the Conference supplementary service uses the TP supplementary service4.12.8.2.1 Normal operationIf, during operation of the Conference supplementary service, a remote user uses the TP supplementary service (remoteinteraction), then notifications concerning the TP supp
31、lementary service shall be sent to the controller of the Conferencesupplementary service as specified in 1.6.8/Q.954 3, i.e. the PartyId of the suspending user is included.Recommendation Q.953 (10/95) 54.12.8.2.2 Exceptional proceduresNo impact.4.12.9 Direct-Dialling-InNo impact.4.12.10 Call Diversi
32、on (Call Forwarding) services4.12.10.1 Call Forwarding BusyNo impact.4.12.10.2 Call Forwarding No ReplyNo impact.4.12.10.3 Call Forwarding UnconditionalNo impact.4.12.10.4 Call DeflectionNo impact.4.12.11 Line HuntingNo access signalling requirements defined.4.12.12 Three-Party service4.12.12.1 The
33、served user of the Three-Party supplementary service uses the TP supplementary service4.12.12.1.1 Normal operationNo impact.NOTE The invocation of the TP supplementary service is not allowed for the served user of the Three-Partysupplementary service.4.12.12.1.2 Exceptional proceduresIf, within the
34、TP supplementary service, the network refuses a request to suspend a call because the call is part of athree-way conversation controlled by the same served user (local interaction for the call), or because another call for thatCEI is part of a three-way conversation controlled by the same served use
35、r (local interaction for the CEI), the SUSPENDREJECT message shall contain cause value #29 “facility rejected”.4.12.12.2 The remote user of the Three-Party supplementary service uses the TP supplementary service4.12.12.2.1 Normal operationIf, during operation of the Three-Party supplementary service
36、, a remote user uses the TP supplementary service (remoteinteraction), then notifications concerning the TP supplementary service shall be sent as normal to the controller of theThree-Party supplementary service.4.12.12.2.2 Exceptional proceduresNo impact.4.12.13 User-to-User Signalling4.12.13.1 Ser
37、vice 1No impact.4.12.13.2 Service 2No impact.6 Recommendation Q.953 (10/95)4.12.13.3 Service 3See 1.6.18/Q.957.1 8.4.12.14 Multiple Subscriber NumberNo impact.4.12.15 Call Hold4.12.15.1 The served user of the Call Hold supplementary service uses the TP supplementary service4.12.15.1.1 Normal operati
38、onNo impact.NOTE The invocation of the TP supplementary service is not allowed for the served user of the Call Hold supplementaryservice.4.12.15.1.2 Exceptional proceduresIf, within the TP supplementary service, the network refuses a request to suspend a call, e.g. because the call is in theCall Hel
39、d auxiliary state (local interaction for the call), or because another call for that CEI is part of a Call Heldauxiliary state (local interaction for the CEI), the SUSPEND REJECT message shall contain cause value #29 “facilityrejected”.4.12.15.2 Remote user of the HOLD supplementary service uses the
40、 TP supplementary serviceNo impact.4.12.16 Advice Of ChargeSee 2.6.18/Q.956 4.4.12.17 Sub-addressingNo impact.4.12.18 Terminal PortabilityNot applicable.4.12.19 Completion of Calls to Busy SubscriberNo applicable interaction at this time.4.12.20 Malicious Call IdentificationNo applicable interaction
41、 at this time.4.12.21 Reverse Charging Case A and Case DNot applicable. Case B (requested by the calling user)If the user of the Reverse Charging supplementary service requests the TP supplementary service whilethe users network is in Reverse Charging request or Reverse Charging indication state, th
42、en the networkshall rejct this request by sending a SUSPEND REJECT message with cause value #29 “facility rejected”to the user.If the destination network of the user who has activated the TP supplementary service receives a requestfor the Reverse Charging supplementary service from the originating n
43、etwork, then the destinationnetwork rejects this request by sending a FACILITY message with the Return error value“supplementaryServiceInteractionNotAllowed” to the calling user.Recommendation Q.953 (10/95) 7 Case B (requested by the called user) and Case CIf the called user requests the Reverse Cha
44、rging supplementary service (Case B: requested by the calleduser or Case C) while the calling user has suspended the call, then the calling users network shall discardthe notification of Reverse Charging to the calling user.4.12.22 Multi-level Precedence and PreemptionNo impact.4.12.23 Support of Pr
45、ivate Numbering PlansNo applicable interaction at this time.4.12.24 International Telecommunication Charge CardNo applicable interaction at this time.4.12.25 Global virtual network servicesNo applicable interaction at this time.4.13 Parameter values (timers)The following timers as specified in claus
46、e 9/Q.931 6 shall be relevant in the context of the TP supplementary service: user timer T319; user timer T318; network timer T307.4.14 Dynamic description (SDLs)Annex A/Q.931 6 shall apply.Appendix ISignalling flows(This appendix does not form an integral part of this Recommendation)The signalling flows for normal procedures are shown in Figure 4-I.1.T1178270-96/d01T319T318T317User A Network A Network B User BSUSPENDSUSPEND ACKRESUMERESUME ACKstopNOTIFYNOTIFYstopFIGURE 4-I.1/Q.953Successful invocation and completion of the TP supplementary servicestopFIGURE 4-I.1/Q953.D01 = 7.5 CM (118%)
