ECMA 308-2001 Corporate Telecommunication Networks Signalling Interworking between QSIG and H 323 Call Transfer Supplementary Services (2nd Edition)《企业电信网络 QSIG和H 323之间的信令互联 呼叫转移补充.pdf

1、Standard ECMA-3082nd Edition - June 2001Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chCorporate TelecommunicationNetworks Signalling Interworking betweenQSIG and H.323 Call Transfer Supplementary

2、 Services.Standard ECMA-3082nd Edition - June 2001Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW ECMA-308.DOC 11-07-01 10,55Corporate TelecommunicationNetworks Signalling Interworking betweenQS

3、IG and H.323 Call Transfer Supplementary Services.Brief HistoryThis Standard is one of a series of ECMA Standards defining the interworking of services and signalling protocolsdeployed in Corporate telecommunication Networks (CNs). The series uses telecommunication concepts as developedby ITU-T and

4、conforms to the framework of International Standards on Open Systems Interconnection as defined byISO/IEC. It has been produced under ETSI work item DEN/ECMA-00195.This particular Standard defines the signalling protocol interworking for call transfer supplementary services betweena Private Integrat

5、ed Services Network (PISN) and a packet-based private telecommunications network based on theInternet Protocol (IP). It is further assumed that the protocol for the PISN part is that defined for the Q referencepoint (QSIG) and that the protocols for the IP-based network are based on ITU-T Recommenda

6、tion H.323.This Standard is based upon the practical experience of ECMA member companies and the results of their active andcontinuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and nationalstandardization bodies. It represents a pragmatic and widely based consens

7、us.This ECMA Standard is in complete alignment with International Standard ISO/IEC 21410:2001(E) to be publishedby ISO/IEC in 2001.Adopted as 2nd Edition of Standard ECMA-308 by the General Assembly of June 2001.- i -Table of contents1Scope 12 Conformance 23 Normative references 24 Definitions 24.1

8、External definitions 24.2 Other definitions 34.2.1 Entity A 34.2.2 Entity A* 34.2.3 Entity B 34.2.4 Entity B* 34.2.5 Entity B 34.2.6 Entity C 34.2.7 Entity C* 34.2.8 Entity C 34.2.9 Gateway 34.2.10 Leg AB 34.2.11 Leg AB* 34.2.12 Leg AC 34.2.13 Leg BC 34.2.14 Leg BC* 34.2.15 Leg B 34.2.16 Leg B* 44.2

9、.17 Leg C 44.2.18 Scenario AB1 44.2.19 Scenario AB*1 44.2.20 Scenario AB2 44.2.21 Scenario AB*2 44.2.22 Scenario AC1 44.2.23 Scenario AC2 44.2.24 Scenario BC1 44.2.25 Scenario BC*1 44.2.26 Scenario BC2 44.2.27 Scenario BC*2 44.2.28 Scenario B1 44.2.29 Scenario B*1 44.2.30 Scenario B2 44.2.31 Scenari

10、o B*2 44.2.32 Scenario C1 44.2.33 Scenario C2 4- ii -5 Acronyms 56 Service architecture 56.1 Service architecture for invocation and operation 56.1.1 QSIG service architecture 56.1.2 H.450.2 service architecture 86.1.3 Scenarios for interworking 116.1.4 Determination of the location of entities when

11、 interworking 126.2 Service architecture for activation, deactivation and interrogation 196.2.1 QSIG service architecture 196.2.2 H.450.2 service architecture 196.2.3 Scenarios for interworking 197 Protocol interworking General requirements 198 Protocol interworking Messages and APDUs 198.1 Scenario

12、 AB1 198.2 Scenario AB2 208.3 Scenario AC1 218.4 Scenario AC2 218.5 Scenario BC1 228.6 Scenario BC2 238.7 Scenario B1 248.8 Scenario B2 258.9 Scenario C1 268.10 Scenario C2 278.11 Scenario AB*1 278.12 Scenario AB*2 288.13 Scenario BC*1 298.14 Scenario BC*2 308.15 Scenario B*1 318.16 Scenario B*2 329

13、 Protocol interworking Content of APDUs 329.1 APDU content mapping from QSIG to H.323 339.1.1 QSIG ssctInitiate invoke APDU mapping to H.323 callTransferInitiate invokeAPDU 339.1.2 QSIG ssctSetup invoke APDU mapping to H.323 callTransferSetup invoke APDU 339.2 APDU content mapping from H.323 to QSIG

14、 339.2.1 H.323 callTransferInitiate invoke APDU mapping to QSIG ssctInitiate invokeAPDU 339.2.2 H.323 callTransferSetup invoke APDU mapping to QSIG ssctSetup invoke APDU 34Annex A - Implementation Conformance Statement (ICS) proforma 35Annex B - Example message sequence diagrams 511ScopeThis Standar

15、d specifies signalling interworking between “QSIG” and “H.323” in support of the call transfersupplementary services within a Corporate telecommunication Network (CN).“QSIG” is a signalling protocol that operates at the Q reference point between Private Integrated ServiceseXchanges (PINX) within a P

16、rivate Integrated Services Network (PISN). The Q reference point is defined inECMA-133. A PISN provides circuit-switched basic services and supplementary services to its users. QSIG isspecified in other Standards, in particular ECMA-143 (call control in support of basic services), ECMA-165(generic f

17、unctional protocol for the support of supplementary services) and a number of standards specifyingindividual supplementary services. ECMA-178 specifies the QSIG protocol in support of call transfer byconsultation and ECMA-300 specifies the QSIG protocol in support of single step call transfer.“H.323

18、” is a set of signalling protocols for the support of voice or multimedia communication within a packetnetwork, in particular a packet network that uses the Internet Protocol (IP) as its network layer protocol (IPnetwork). H.323 signalling protocols operate between endpoints in an IP network, either

19、 indirectly via one ormore gatekeepers, or directly. An endpoint can be a terminal or a gateway to another network. H.323 is an“umbrella” recommendation referring to various ITU-T recommendations, in particular RecommendationsH.225.0 and H.245 (basic communication capabilities) and Recommendation H.

20、450.1 (generic functionalprotocol for the support of supplementary services). Recommendation H.450.2 specifies the H.323 protocol insupport of call transfer.NOTEH.450.2 applies only to the 1998 version of H.323 (also known as H.323 version 2) and to later versions.Call transfer by consultation, as s

21、upported by ECMA-178, is a supplementary service that enables a user (userA) to transform two of that users calls (at least one of which must be answered) into a new call between thetwo other users in the two calls (users B and C).Single step call transfer, as supported by ECMA-300, is a supplementa

22、ry service that enables a user (user A)to transform an existing call between user A and user B into a new call between user B and user C withoutuser A needing to establish a call with user C prior to transfer.Call transfer, as supported by H.450.2, is a supplementary service that enables the served

23、user (user A) totransform an existing call with a second user (user B) into a new call between user B and a third user (user C)selected by user A. User A may or may not have a call established with user C prior to call transfer. If a call isalready established between user A and user C, this is know

24、n as transfer by consultation and is equivalent tocall transfer as supported by ECMA-178. If a call is not already established between user A and user C, this isknown as single step call transfer and is equivalent to call transfer as supported by ECMA-300.Interworking between QSIG and H.323 permits

25、a call originating at a user of a PISN to terminate at a user ofan IP network, or a call originating at a user of an IP network to terminate at a user of a PISN. This Standardprovides the following additional capabilities: a PISN user with two calls established, at least one of which being to or fro

26、m a user in an IP network, tobe able to transform those two calls into a new call between the other two users involved; a PISN user with a call established to or from a user in an IP network to be able to transform that call intoa new call between the IP network user and a third user selected by the

27、 PISN user, that third user beingeither in the IP network or in the PISN; a PISN user with a call established to a second PISN user to be able to transfer that call into a new callbetween the second user and a third user selected by the first user, that third user being in an IP network; an IP netwo

28、rk user with two calls established, at least one of which being to or from a user in a PISN, tobe able to transform those two calls into a new call between the other two users involved; an IP network user with a call established to or from a user in a PISN to be able to transform that call intoa new

29、 call between the PISN user and a third user selected by the IP network user, that third user beingeither in the IP network or in the PISN; and- 2 - an IP network user with a call established to a second user in the IP network to be able to transfer that callinto a new call between the second user a

30、nd a third user selected by the first user, that third user being ina PISN.This Standard is applicable to any interworking unit that can act as a gateway between a PISN employingQSIG and an IP network employing H.323.2 ConformanceIn order to conform to this Standard, a gateway shall satisfy the requ

31、irements identified in the ImplementationConformance Statement (ICS) proforma in annex A.3 Normative referencesThe following standards contain provisions which, through reference in this text, constitute provisions of thisStandard. All standards are subject to revision, and parties to agreements bas

32、ed on this Standard areencouraged to investigate the possibility of applying the most recent editions of the standards indicatedbelow.In the case of references to ECMA Standards that are aligned with ISO/IEC International Standards, thenumber of the appropriate ISO/IEC International Standard is give

33、n in brackets after the ECMA reference.ECMA-133 Private Integrated Services Network (PISN) - Reference Configuration for PISNExchanges (PINX) (International Standard ISO/IEC 11579-1)ECMA-143 Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - Inter-Exchange Signalling Procedu

34、res and Protocol (International Standard ISO/IEC 11572)ECMA-165 Private Integrated Services Network (PISN) - Generic Functional Protocol for theSupport of Supplementary Services - Inter-Exchange Signalling Procedures andProtocol (International Standard ISO/IEC 11582)ECMA-178 Private Integrated Servi

35、ces Network (PISN) - Inter-Exchange Signalling Protocol -Call Transfer Supplementary Service (International Standard ISO/IEC 13869)ECMA-300 Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol -Single Step Call Transfer Supplementary Service (International Standard ISO/IEC

36、19460)ECMA-307 Corporate Telecommunication Networks - Signalling Interworking between QSIG andH.323 - Generic Functional Protocol for the Support of Supplementary Services(International Standard ISO/IEC 21409)ITU-T Rec. H.225.0 Call signalling protocols and media stream packetization for packet-base

37、d multimediacommunication systems (1998 or later)ITU-T Rec. H.245 Control protocol for multimedia communication (1998 or later)ITU-T Rec. H.323 Packet-based multimedia communications systems (1998 or later)ITU-T Rec. H.450.1 Generic functional protocol for the support of supplementary services in H.

38、323 (1998)ITU-T Rec. H.450.2 Call transfer supplementary service for H.323 (1998)4 DefinitionsFor the purposes of this Standard, the following definitions apply.4.1 External definitionsThis Standard uses the following terms defined in other documents: Call (ECMA-307) Corporate telecommunication Netw

39、ork (CN) (ECMA-307) Endpoint (ITU-T Rec. H.323)- 3 - IP network (ECMA-307) Gatekeeper (ITU-T Rec. H.323) Private Integrated Services Network (PISN) (ECMA-307) Private Integrated services Network eXchange (PINX) (ECMA-133)Additionally the definitions in ECMA-178, ECMA-300 and ITU-T Recommendation H.4

40、50.2 apply asappropriate.4.2 Other definitions4.2.1 Entity AIn call transfer by consultation, the signalling entity at the PINX or H.323 endpoint serving thetransferring user (user A).4.2.2 Entity A*In single step call transfer, the signalling entity at the PINX or H.323 endpoint serving the transfe

41、rringuser (user A).4.2.3 Entity BIn call transfer by consultation, the signalling entity in the PISN or IP network associated with the callbetween the transferring user (user A) and the transferred user (user B).4.2.4 Entity B*In single step call transfer, the signalling entity in the PISN or IP net

42、work associated with the callbetween the transferring user (user A) and the transferred user (user B).4.2.5 Entity BSignalling entity at the PINX or the H.323 endpoint serving the transferred user (user B).4.2.6 Entity CIn call transfer by consultation, the signalling entity in the PISN or IP networ

43、k associated with the callbetween the transferring user (user A) and the transferred-to-user (user C).4.2.7 Entity C*In single step call transfer, the signalling entity in the PISN or IP network associated with the callbetween the transferred user (user B) and the transferred-to-user (user C).4.2.8

44、Entity CSignalling entity at the PINX or H.323 endpoint serving the transferred-to-user (user C).4.2.9 GatewayA gateway as defined in H.323 specifically for the purpose of interworking with a network employingQSIG.4.2.10 Leg ABIn call transfer by consultation, the call segment that lies between enti

45、ty A and entity B.4.2.11 Leg AB*In single step call transfer, the call segment that lies between entity A* and entity B*.4.2.12 Leg ACIn call transfer by consultation, the call segment that lies between entity A and entity C.4.2.13 Leg BCIn call transfer by consultation, the call segment that lies b

46、etween entity B and entity C.4.2.14 Leg BC*In single step call transfer, the call segment that lies between entity B* and entity C*.4.2.15 Leg BIn call transfer by consultation, the call segment that lies between the entity B and entity B.- 4 -4.2.16 Leg B*In single step call transfer, the call segm

47、ent that lies between entity B* and entity B.4.2.17 Leg CIn call transfer by consultation, the call segment that lies between entity C and entity C.4.2.18 Scenario AB1Interworking arrangement in which entity A (PINX A) is in the PISN and entity B is in the IP network.4.2.19 Scenario AB*1Interworking

48、 arrangement in which entity A* (PINX A) is in the PISN and entity B* is in the IPnetwork.4.2.20 Scenario AB2Interworking arrangement in which entity A (endpoint A) is in the IP network and entity B is in thePISN.4.2.21 Scenario AB*2Interworking arrangement in which entity A* (endpoint A) is in the

49、IP network and entity B* is in thePISN.4.2.22 Scenario AC1Interworking arrangement in which entity A (PINX A) is in the PISN and entity C is in the IP network.4.2.23 Scenario AC2Interworking arrangement in which entity A (endpoint A) is in the IP network and entity C is in thePISN.4.2.24 Scenario BC1Interworking arrangement in which entity B (PINX B) is in the PISN and entity C is in the IP network.4.2.25 Scenario BC*1Interworking arrangement in which entity B* (PINX B) is in the PISN and entity C* is in the IP network.4.2.26 Scenario BC2Interworking arran