ECMA TR 81-2000 Interoperation of PISNs with IP Networks《带IP网络的专用综合业务网络(PISN)的互操作》.pdf

《ECMA TR 81-2000 Interoperation of PISNs with IP Networks《带IP网络的专用综合业务网络(PISN)的互操作》.pdf》由会员分享，可在线阅读，更多相关《ECMA TR 81-2000 Interoperation of PISNs with IP Networks《带IP网络的专用综合业务网络(PISN)的互操作》.pdf（74页珍藏版）》请在麦多课文档分享上搜索。

1、ECMA Technical Report TR/81September 2000Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chInteroperation of PISNs with IPNetworks.ECMA Technical Report TR/81September 2000Standardizing Information a

2、nd Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW TR-081.DOC 02-05-01 16,18Interoperation of PISNs with IPNetworks.Brief HistoryThis Technical Report investigates the interoperability of Private Integrated Services Networks

3、 (PISNs) and InternetProtocol (IP) networks within the context of Corporate Telecommunication Networks. The purpose is to identifypossible scenarios for interoperation, problems that will have to be solved if particular scenarios are to be pursuedfurther, and possible future standardization activiti

4、es in this area. It forms the foundation for further work in ECMAon this subject, including the production of Standards where found to be required.This Technical Report is based upon the practical experience of ECMA member companies and the results of theiractive and continuous participation in the

5、work of ISO/IEC JTC1, ITU-T, ETSI, IETF and other international andnational standardization bodies. It represents a pragmatic and widely based consensus.This ECMA Technical Report has been adopted by the General Assembly in September 2000.List of corrected errata for ECMA TR/8114 December 2000Summar

6、yFollowing is a summary of errors detected and corrected in Technical Report ECMA TR/81, Interoperation ofPISNs with IP Networks.Clause 4 Acronyms “SCTP“ stands now for “Stream Control Transmission Protocol“ and is specified in IETF RFC 2960.Corrected:SCTP Stream Control Transmission ProtocolOrigina

7、l:SCTP Simple Control Transport ProtocolClause 7.4.2.7 Simple Control Transport Protocol (SCTP) Due to the change mentioned above, the title of clause 7.4.2.7 and the 1st paragraph of this clause shouldbe modified.Corrected:“7.4.2.7 Stream Control Transmission Protocol (SCTP)Work in the IETF SIGTRAN

8、 group has produced a transport protocol suitable for carrying signalling, inparticular taking into account the high demands of SS7. RFC 2960 specifies a Stream Control TransmissionProtocol (SCTP). Although it has a number of possible applications, the initial aim is to fulfil requirements ofinterfa

9、ce K between an LLS functional entity and an HLS functional entity, as shown in figure 12 and figure13.“Original:“7.4.2.7 Simple Control Transport Protocol (SCTP)Work in the IETF SIGTRAN group is aimed at producing a transport protocol suitable for carrying signalling,in particular taking into accou

10、nt the high demands of SS7. Currently work is in progress on a Simple ControlTransport Protocol (SCTP). Although it has a number of possible applications, the initial aim is to fulfilrequirements of interface K between an LLS functional entity and an HLS functional entity, as shown infigure 12 and f

11、igure 13.“Clause 9.3.2 Aspects requiring further study or standardization work Due to the change in the clause 4 Acronym, the third dotted line should be modified.Corrected:“The application of SIGTRANs Stream Control Transmission Protocol (SCTP) for transport of QSIG andScenSIG information over the

12、IP-network.“Original:“The application of SIGTRANs Simple Control Transmission Protocol (SCTP) for transport of QSIG andScenSIG information over the IP-network.“Clause 9.4.1 Architecture Figure 21 - Architecture for solution 2 shows connections between each MPP and the ICN, but notbetween RC-U and IC

13、N, SC-U and ICN, and RGT and ICN. Therefore it should be corrected.Corrected:PINXMPMPPRC-USC-URGTQSWICCCCSMCIVN(IP network)PINXMPMPPRC-USC-URGTQSWICC CCSMCFigure 21 Architecture for solution 2Original:PINXMPMPPRC-USC-URGTQSWICCCCSMCIVN(IP network)PINXMPMPPRC-USC-URGTQSWICC CCSMCFigure 21 Architectur

14、e for solution 2Annex D Architecture for Signalling Transport over IP-networks (SIGTRAN) Due to the change in the clause 4 Acronym, the last sentence of the 1st paragraph below figure 29 shouldbe modified.Corrected:“This protocol under development is known as the “Stream Control Transmission Protoco

15、l (SCTP)”.“Original:“This protocol under development is known as the “Simple Control Transport Protocol (SCTP)”.“- i -Table of contents1Scope 12 References 13 Definitions 33.1 Corporate telecommunication Network (CN) 33.2 Internet 33.3 Intranet 33.4 Internet Protocol (IP) 33.5 IP network 33.6 Privat

16、e Integrated Services Network (PISN) 33.7 Private Integrated services Network eXchange (PINX) 33.8 Switched Circuit Network (SCN) 33.9 Tunnelling 44 Acronyms 45 Introduction 55.1 Background 55.2 Types of network 75.3 Arrangements for interworking of SCNs and IP networks 85.4 Arrangements for interco

17、nnection of SCN components over IP networks 96 General principles of multimedia communication over an IP network 96.1 Architecture 106.1.1 Media processing and packetization (MPP) functional entity 106.1.2 Resource control (RC) functional entity 116.1.3 Session control (SC) functional entity 116.1.4

18、 SC-redirect (SC-R), SC-proxy (SC-P) and RC-proxy (RC-P) functional entities 116.1.5 Admission control (AC) functional entities 126.1.6 Identity resolution (IR) functional entity 126.1.7 Registrar (RGR) and registrant (RGT) functional entities 136.1.8 Generic functional architecture (non-interworkin

19、g) 136.1.9 Physical realizations of generic functional architecture for multimediacommunication over an IP network (non-interworking) 136.1.10 Generic functional architecture for interworking with an SCN 146.1.11 Physical realizations of generic functional architecture for interworking with anSCN 15

20、6.1.12 Simple terminals 176.2 Naming and addressing 186.3 Security 186.4 Quality of service (QoS) 186.5 Mobility 19- ii -7 Standards for multimedia communication over an IP network 207.1 Overview 207.2 The ITU-T H.323 family of recommendations 217.2.1 Functional architecture 217.2.2 Naming and addre

21、ssing 227.2.3 Supplementary services 227.2.4 Security 237.2.5 Quality of service 247.2.6 Mobility 247.3 Other ITU-T standards 247.3.1 H.248 247.3.2 BICC 257.4 IETF specifications for IP telephony 257.4.1 Functional architecture 257.4.2 Main protocols 267.4.3 Naming and addressing 277.4.4 Supplementa

22、ry services 277.4.5 Security 287.4.6 Quality of service 297.4.7 Mobility 297.5 ETSI TIPHON specifications 297.6 Terminal specifications from TIA TR-41.3.4 298Interworking of PISNs and IP networks via a gateway 308.1 Architecture 308.2 Signalling 318.3 Naming and addressing 318.3.1 Naming and address

23、ing in PISNs 318.3.2 Naming and addressing in IP networks 318.3.3 Naming and addressing interworking when H.323 used in the IP network 318.3.4 Naming and addressing interworking when SIP used in the IP network 328.4 Supplementary services 328.4.1 H.323 supplementary services 328.4.2 SIP supplementar

24、y services 338.5 Security 338.6 Quality of service 338.7 Mobility 338.8 Network management 338.9 Aspects requiring further study or standardization work 349 Interconnection of remote PISNs via an IP network 349.1 Classification of scenarios for the interconnection of PISNs 349.2 Solutions for the in

25、terconnection of remote PISNs via an IP network 369.3 Solution 1 QSIG tunnelling over IP network transport layer protocol 369.3.1 Architecture 369.3.2 Aspects requiring further study or standardization work 37- iii -9.4 Solution 2 QSIG tunnelling over IP network session control protocol 389.4.1 Arch

26、itecture 389.4.2 Aspects requiring further study or standardization work 399.5 Solution 3 enhanced QSIG in the IP network 399.5.1 Architecture 399.5.2 Aspects requiring further study or standardization work 3910 Connection of telephones to a PINX via an IP network 3910.1 Architecture 4010.2 Aspect r

27、equiring standardization work 4211 Summary 42Annex A - Overview and status of H.323 45Annex B - Overview and status of SIP 49Annex C - Overview of H.248 / MEGACO protocol 53Annex D - Architecture for Signalling Transport over IP-networks (SIGTRAN) 55- iv -.1ScopeThe purpose of this Technical Report

28、is to investigate the interoperability of Private Integrated ServicesNetworks (PISNs) and Internet Protocol (IP) networks, with a view to identifying possible scenarios forinteroperation, problems that will have to be solved if particular scenarios are to be pursued further, andpossible future stand

29、ardization activities in this area. In particular, the following aspects of interoperabilityare investigated: the interworking of PISNs and IP networks via a gateway; the connection of PISN components via IP networks.For each of the above, aspects considered include architecture, addressing (includi

30、ng use of IP addressing),services, protocols, security, quality of service and mobility. This is conducted within the context of leadingstandards for voice and multimedia communication over IP networks, including ITU-T recommendationH.323, IETF Session Initiation Protocol (SIP) and ITU-T recommendat

31、ion H.248.Possible future standardization activities resulting from this Technical Report can include work items relatingto IP networks and work items relating to PISNs, as well as work items concerned specifically withinteroperability.The dominant traffic in PISNs is voice, and therefore this Techn

32、ical Report focuses on interoperabilityconsiderations for voice traffic. However, many of the standards that support voice in an IP network are alsoapplicable to multi-media traffic (e.g., voice, video and data). Although in many respects similar to voice, faxtraffic has slightly different requireme

33、nts and is not explicitly considered in this Technical Report. It could bethe subject of further study.2 ReferencesECMA-133 Private Integrated Services Network (PISN) - Reference Configuration for PISNExchanges (PINX) (International Standard ISO/IEC 11579-1)ECMA-143 Private Integrated Services Netwo

34、rk (PISN) - Circuit-mode Bearer Services - Inter-Exchange Signalling Procedures and Protocol (International StandardISO/IEC 11572)ECMA-155 Private Integrated Services Networks - Addressing (International StandardISO/IEC 11571)ECMA-163 Private Integrated Services Network (PISN) - Specification, Funct

35、ional Model andInformation Flows - Name Identification Supplementary Services (InternationalStandard ISO/IEC 13864)ECMA-164 Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol -Name Identification Supplementary Services (International StandardISO/IEC 13868)ECMA-165 Privat

36、e Integrated Services Network (PISN) - 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 Diversio

37、n Supplementary Services (International Standard ISO/IEC 13873)ECMA-178 Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol -Call Transfer Supplementary Service (International Standard ISO/IEC 13869)ECMA-186 Private Integrated Services Network (PISN) - Inter-Exchange Sign

38、alling Protocol -Call Completion Supplementary Services (International Standard ISO/IEC 13870)ECMA-242 Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol -Message Waiting Indication Supplementary Service (International StandardISO/IEC 15506)- 2 -ECMA-300 Private Integrat

39、ed Services Network (PISN) - InterExchange Signalling Protocol -Single Step Call Transfer Supplementary Service (International Standard ISO/IECDIS 19460)ECMA TR/57 Private Integrated Services NetworksECMA TR/76 Private Integrated Services Network (PISN) - Architecture and Scenarios forPrivate Integr

40、ated Services NetworkingETSI TS 101 313 Telecommunications and Internet Protocol Harmonization over Networks(TIPHON); Network architecture and reference configurations; Phase II: Scenario 1+ Scenario 2ITU-T Rec. G.107 The E-Model, a computational model for use in transmission planningITU-T Rec. G.71

41、1 Pulse Code Modulation (PCM) of voice frequenciesITU-T Rec. G.723.1 Dual rate speech coder for multimedia communications transmitting at 5.3 and6.3 kbit/sITU-T Rec. H.225.0 Call signalling protocols and media stream packetization for packet-basedmultimedia communication systemsITU-T Rec. H.235 Secu

42、rity and encryption for H-Series (H.323 and other H.245-based) multimediaterminalsITU-T Rec. H.245 Control protocol for multimedia communicationITU-T Rec. H.248 Gateway control protocolITU-T Rec. H.261 Video codec for audiovisual services at p x 64 kbitsITU-T Rec. H.320 Narrow-band visual telephone

43、systems and terminal equipmentITU-T Rec. H.323 Packet based multimedia communications systemsITU-T Rec. H.450.1 Generic functional protocol for the support of supplementary services in H.323ITU-T Rec. H.450.2 Call transfer supplementary service for H.323ITU-T Rec. H.450.3 Call diversion supplementar

44、y service for H.323ITU-T Rec. H.450.4 Call hold supplementary service for H.323ITU-T Rec. H.450.5 Call park and call pickup supplementary services for H.323ITU-T Rec. H.450.6 Call waiting supplementary service for H.323ITU-T Rec. H.450.7 Message waiting indication supplementary service for H.323ITU-

45、T Rec. H.450.8 Name identification supplementary service for H.323ITU-T Rec. H.450.9 (draft) Call completion supplementary services for H.323ITU-T Rec. Q.921 ISDN user-network interface - Data link layer specificationITU-T Rec. Q.931 Digital Subscriber Signalling system no. 1 (DSS1) - ISDN user-netw

46、ork interfacelayer 3 specification for basic call controlIETF RFC 791 Internet Protocol (IP), version 4.IETF RFC 1034 Domain names - concepts and facilitiesIETF RFC 1035 Domain names - implementation and specificationIETF RFC 1889 RTP: a transport protocol for real-time applicationsIETF RFC 2205 Res

47、ource ReSerVation Protocol (RSVP) - Version 1 functional specificationIETF RFC 2246 The TLS Protocol Version 1.0IETF RFC 2251 Lightweight Directory Access Protocol (version 3)- 3 -IETF RFC 2326 Real-time streaming protocol (RTSP) for controlling delivery of streaming mediaIETF RFC 2327 SDP: Session

48、Description ProtocolIETF RFC 2401 Security Architecture for the Internet Protocol (IPSec)IETF RFC 2402 IP Authentication Header (AH)IETF RFC 2406 IP Encapsulating Security Payload (ESP)IETF RFC 2407 The Internet IP Security Domain of Interpretation for ISAKMPIETF RFC 2408 Internet Security Associati

49、on and Key Management Protocol (ISAKMP)IETF RFC 2460 Internet Protocol, Version 6 (IPv6) SpecificationIETF RFC 2475 An architecture for differentiated servicesIETF RFC 2543 SIP: Session Initiation ProtocolIETF RFC 2719 Framework architecture for signaling transportTIA/EIA/IS-811 Telephone Terminal Equipment - Performance and Interoperability Requirementsfor Voice-over-IP (VoIP) Feature TelephonesTIA/EIA/TSB-116 Voice Quality Recommendations for IP Telephony3 DefinitionsFor the purposes of this Technical Report the following definitions apply.3.1 Corporate telecommuni