ECMA 309-2001 Corporate Telecommunication Networks Signalling Interworking between QSIG and H 323 Call Diversion Supplementary Services《企业电信网络 QSIG和H 323之间的信令互联 呼叫转移补充业务 第2版》.pdf

《ECMA 309-2001 Corporate Telecommunication Networks Signalling Interworking between QSIG and H 323 Call Diversion Supplementary Services《企业电信网络 QSIG和H 323之间的信令互联 呼叫转移补充业务 第2版》.pdf》由会员分享，可在线阅读，更多相关《ECMA 309-2001 Corporate Telecommunication Networks Signalling Interworking between QSIG and H 323 Call Diversion Supplementary Services《企业电信网络 QSIG和H 323之间的信令互联 呼叫转移补充业务 第2版》.pdf（48页珍藏版）》请在麦多课文档分享上搜索。

1、Standard ECMA-3092nd 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 Diversion Supplementar

2、yServices.Standard ECMA-3092nd 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-309.DOC 11-07-01 11,02Corporate TelecommunicationNetworks Signalling Interworking betweenQS

3、IG and H.323 Call Diversion SupplementaryServices.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-00194.This particular Standard defines the signalling protocol interworking for call diversion supplementary servicesbetween a Private Integra

5、ted Services Network (PISN) and a packet-based private telecommunications network basedon the Internet Protocol (IP). It is further assumed that the protocol for the PISN part is that defined for the Qreference point (QSIG) and that the protocols for the IP-based network are based on ITU-T Recommend

6、ation 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 consen

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

8、 External definitions 24.2 Other definitions 24.2.1 Association D 24.2.2 Association E 24.2.3 Association F 24.2.4 Association G 24.2.5 Entity A 34.2.6 Entity B 34.2.7 Entity B 34.2.8 Entity C 34.2.9 Entity D 34.2.10 Entity E 34.2.11 Entity F 34.2.12 Entity G 34.2.13 Entity H 34.2.14 Gateway 34.2.15

9、 Leg A 34.2.16 Leg B 34.2.17 Leg B 34.2.18 Leg C 34.2.19 Rerouting entity 34.2.20 Scenario A1 34.2.21 Scenario A2 34.2.22 Scenario B1 34.2.23 Scenario B2 44.2.24 Scenario C1 44.2.25 Scenario C2 44.2.26 Scenario D1 44.2.27 Scenario D2 44.2.28 Scenario E1 44.2.29 Scenario E2 44.2.30 Scenario F1 44.2.3

10、1 Scenario F2 44.2.32 Scenario G1 44.2.33 Scenario G2 4- ii -5 Acronyms 46 Service architecture 56.1 Service architecture for invocation and operation 56.1.1 ECMA-174 service architecture 56.1.2 H.450.3 service architecture 56.1.3 Scenarios for interworking 66.1.4 Determination of the location of th

11、e rerouting entity when interworking 76.2 Service architecture for activation, deactivation and interrogation 76.2.1 ECMA-174 service architecture 76.2.2 H.450.3 service architecture 86.2.3 Scenarios for interworking 87 Protocol interworking General requirements 98 Protocol interworking Messages and

12、 APDUs 98.1 Scenario A1 98.2 Scenario A2 118.3 Scenario B1 128.4 Scenario B2 138.5 Scenario C1 148.6 Scenario C2 148.7 Scenario D1 158.8 Scenario D2 158.9 Scenario E1 168.10 Scenario E2 168.11 Scenario F1 178.12 Scenario F2 178.13 Scenario G1 188.14 Scenario G2 18Annex A - Implementation Conformance

13、 Statement (ICS) proforma 19Annex B - Example message sequence diagrams 311ScopeThis Standard specifies signalling interworking between “QSIG” and “H.323” in support of call diversionsupplementary services within a Corporate telecommunication Network (CN).“QSIG” is a signalling protocol that operate

14、s at the Q reference point between Private Integrated ServiceseXchanges (PINX) within a Private 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 Standard

15、s, in particular ECMA-143 (call control in support of basic services), ECMA-165(generic functional protocol for the support of supplementary services) and a number of standards specifyingindividual supplementary services. ECMA-174 specifies the QSIG protocol in support of call diversionservices.“H.3

16、23” 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, eith

17、er 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

18、H.450.1 (generic functionalprotocol for the support of supplementary services). Recommendation H.450.3 specifies the H.323 protocol insupport of call diversion services.NOTEH.450.3 applies only to the 1998 version of H.323 (also known as H.323 version 2) and to later versions.In both ECMA-174 (QSIG)

19、 and ITU-Recommendation H.450.3 (H.323), the call diversion supplementaryservices are Call Forwarding Unconditional (SS-CFU), Call Forwarding Busy (SS-CFB), Call Forwarding NoReply (SS-CFNR) and Call Deflection (SS-CD). These supplementary services apply during callestablishment and provide diversio

20、n of an incoming call to another destination.Interworking between QSIG and H.323 permits 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 ca

21、pabilities: a call originating from a PISN and destined for a user of an H.323 network to be diverted by the H.323network to an alternative destination; a call originating from an H.323 network and destined for a user of a PISN to be diverted by the PISN toan alternative destination; a call destined

22、 for a user of a PISN to be diverted to an alternative destination where that alternativedestination is in an H.323 network; a call destined for a user of an H.323 network to be diverted to an alternative destination where thatalternative destination is in a PISN.This Standard is applicable to any i

23、nterworking 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 requirements identified in the ImplementationConformance Statement (ICS) proforma in annex A.3 Normative references

24、The following standards contain provisions which, through reference in this text, constitute provisions of thisStandard. All standards are subject to revision, and parties to agreements based on this Standard areencouraged to investigate the possibility of applying the most recent editions of the st

25、andards indicatedbelow.- 2 -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 given in brackets after the ECMA reference.ECMA-133 Private Integrated Services Network (PISN) - Reference Con

26、figuration for PISNExchanges (PINX) (International Standard ISO/IEC 11579-1)ECMA-143 Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - Inter-Exchange Signalling Procedures and Protocol (International Standard ISO/IEC 11572)ECMA-165 Private Integrated Services Network (PISN)

27、 - Generic Functional Protocol for theSupport of Supplementary Services - Inter-Exchange Signalling Procedures andProtocol (International Standard ISO/IEC 11582)ECMA-174 Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol -Call Diversion Supplementary Services (Internatio

28、nal Standard ISO/IEC 13873)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 packetiz

29、ation for packet-based 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 supplem

30、entary services in H.323 (1998)ITU-T Rec. H.450.3 Call diversion 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

31、telecommunication Network (CN) (ECMA-307) Endpoint (ITU-T Rec. H.323) Gatekeeper (ITU-T Rec. H.323) IP network (ECMA-307) Private Integrated Services Network (PISN) (ECMA-307) Private Integrated services Network eXchange (PINX) (ECMA-133)Additionally the definitions in ECMA-174 and ITU-T Recommendat

32、ion H.450.3 apply as appropriate.4.2 Other definitions4.2.1 Association DSignalling association between entity D and entity G.4.2.2 Association ESignalling association between entity E and entity G.4.2.3 Association FSignalling association between entity F and entity G.4.2.4 Association GSignalling

33、association between entity G and entity H.- 3 -4.2.5 Entity ASignalling entity at the PINX or H.323 endpoint serving the calling user (user A).4.2.6 Entity BSignalling entity at the PINX serving the diverting user (user B) or H.323 entity that invokes diversionon behalf of user B.4.2.7 Entity BSigna

34、lling entity at the H.323 endpoint serving user B.4.2.8 Entity CSignalling entity at the PINX or H.323 endpoint serving the diverted-to-user (user C).4.2.9 Entity DSignalling entity at the PINX or H.323 endpoint serving an activating user.4.2.10 Entity ESignalling entity at the PINX or H.323 endpoin

35、t serving a deactivating user.4.2.11 Entity FSignalling entity at the PINX or H.323 endpoint serving an interrogating user.4.2.12 Entity GSignalling entity for activation / deactivation / interrogation at a PINX or H.323 endpoint serving adiverting endpoint.4.2.13 Entity HSignalling entity for restr

36、iction checking at a PINX or H.323 endpoint serving a diverted-to endpoint.4.2.14 GatewayA gateway as defined in H.323 specifically for the purpose of interworking with a network employingQSIG.4.2.15 Leg ACall segment that lies between entity A and the rerouting entity.4.2.16 Leg BCall segment that

37、lies between the rerouting entity and entity B.4.2.17 Leg BCall segment that lies between entity B and entity B.4.2.18 Leg CCall segment that lies between the rerouting entity and entity C.4.2.19 Rerouting entitySignalling entity that initiates the rerouting of a call towards user C and clears the c

38、all towards user B.4.2.20 Scenario A1Interworking arrangement in which entity A (PINX A) is in the PISN and the rerouting entity is in the IPnetwork.4.2.21 Scenario A2Interworking arrangement in which entity A (endpoint A) is in the IP network and the rerouting entity isin the PISN.4.2.22 Scenario B

39、1Interworking arrangement in which entity B (PINX B) is in the PISN and the rerouting entity is in the IPnetwork.- 4 -4.2.23 Scenario B2Interworking arrangement in which entity B (diverting endpoint or its gatekeeper) is in the IP networkand the rerouting entity is in the PISN.4.2.24 Scenario C1Inte

40、rworking arrangement in which entity C (PINX C) is in the PISN and the rerouting entity is in the IPnetwork.4.2.25 Scenario C2Interworking arrangement in which entity C (endpoint C) is in the IP network and the rerouting entity isin the PISN.4.2.26 Scenario D1Interworking arrangement in which entity

41、 D (PINX D) is in the PISN and entity G (endpoint G) is in theIP network.4.2.27 Scenario D2Interworking arrangement in which entity D (endpoint D) is in the IP network and entity G (PINX G) isin the PISN.4.2.28 Scenario E1Interworking arrangement in which entity E (PINX E) is in the PISN and entity

42、G (endpoint G) is in theIP network.4.2.29 Scenario E2Interworking arrangement in which entity E (endpoint E) is in the IP network and entity G (PINX G) isin the PISN.4.2.30 Scenario F1Interworking arrangement in which entity F (PINX F) is in the PISN and entity G (endpoint G) is in theIP network.4.2

43、.31 Scenario F2Interworking arrangement in which entity F (endpoint F) is in the IP network and entity G (PINX G) isin the PISN.4.2.32 Scenario G1Interworking arrangement in which entity G (PINX G) is in the PISN and entity H (endpoint H) is in theIP network.4.2.33 Scenario G2Interworking arrangemen

44、t in which entity G (endpoint G) is in the IP network and entity H (PINX H) isin the PISN.5 AcronymsAPDU Application Protocol Data UnitCN Corporate telecommunication NetworkICS Implementation Conformance StatementIP Internet ProtocolPINX Private Integrated services Network eXchangePISN Private Integ

45、rated Services NetworkSS-CD Supplementary Service Call DeflectionSS-CFB Supplementary Service Call Forwarding BusySS-CFNR Supplementary Service Call Forwarding No Reply- 5 -SS-CFU Supplementary Service Call Forwarding Unconditional6 Service architecture6.1 Service architecture for invocation and ope

46、ration6.1.1 ECMA-174 service architectureThe QSIG protocol for call diversion invocation and operation is based around four signalling entities orPINX types: entity A the PINX serving the calling user (user A); entity B the PINX serving the diverting user (user B); entity C the PINX serving the dive

47、rted-to user (user C); rerouting entity the PINX that initiates the rerouting of the call towards user C and clears the calltowards user B.Where a user is in another network, the role of entity A, entity B or entity C is performed by the othernetwork, the gateway PINX or the two in combination. Howe

48、ver, from the QSIG point of view the roleis performed by the gateway PINX.This can be represented diagrammatically as shown in figure 1.Entity A ReroutingentityEntity BEntity CLeg ALeg BLeg CFigure 1 Call diversion architecture for QSIGFrom this it can be seen that there are three segments or “legs”

49、 to the call: leg A from entity A to the rerouting entity; leg B from the rerouting entity to entity B; leg C from the rerouting entity to entity C.The QSIG protocol supports each of these three legs.The rerouting entity is constrained to be collocated with (in the same PINX as) entity A or entity B (orboth if entity A and entity B are collocated). In addition, entity C can be collocated with the reroutingentity (and therefore with entity A and/or entity B). When an entity is collocated with the reroutingentity, the leg of the call concerned is i