1、 ETSI TR 102 478 V1.1.1 (2006-03)Technical Report Corporate telecommunication Networks (CN);Enterprise communication involvingNext Generation carrier Networks (NGN)2 ETSI ETSI TR 102 478 V1.1.1 (2006-03) Reference DTR/ECMA-00295 Keywords network, service ETSI 650 Route des Lucioles F-06921 Sophia An
2、tipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The pre
3、sent document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printer
4、s of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/s
5、tatus/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restric
6、tion extend to reproduction in all media. European Telecommunications Standards Institute 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for th
7、e benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. 3 ETSI ETSI TR 102 478 V1.1.1 (2006-03) Contents Intellectual Property Rights5 Foreword.5 Brief History.5 1 Scope 6 2 References 6 3 Definitions and abbreviatio
8、ns.6 3.1 Definitions6 3.2 Abbreviations .7 4 Void7 5 Background 7 5.1 Provision of services by NGNs 8 5.1.1 Levels of service provision .8 5.1.2 Use of NGN services by NGCNs9 5.1.3 Home NGN.9 5.2 Management considerations .10 6 Basic Configurations and General Requirements.10 6.1 Scenario 1 - Commun
9、ication between NGCNs via an NGN using a VPN.11 6.2 Scenario 2 - Communication between NGCNs via an NGN not using a VPN 11 6.3 Scenario 3 - Communication between NGCN and TE via an NGN using a VPN12 6.4 Scenario 4 - Communication between NGCN and TE via an NGN not using a VPN .13 6.5 Scenario 5 - Co
10、mmunication between NGCN and PSTN/ISDN via an NGN13 6.6 General requirements on NGNs .14 6.7 General requirements on NGNs concerning measures for compliance with regulations .15 7 Technical issues and requirements on NGN related to session service provision15 7.1 Signalling architecture16 7.1.1 Scen
11、ario 1 - Communication between NGCNs using a VPN .17 7.1.2 Scenario 2 - Communication between NGCNs not using a VPN .17 7.1.3 Scenario 3 - Communication between NGCN and TE using a VPN 18 7.1.4 Scenario 4 - Communication between NGCN and TE not using a VPN 18 7.1.5 Scenario 5 - Communication between
12、 NGCN and PSTN/ISDN 18 7.2 NAT traversal.19 7.2.1 NAT traversal for SIP signalling 19 7.2.1.1 Scenario 1 - Communication between NGCNs using a VPN .19 7.2.1.2 Scenario 2 - Communication between NGCNs not using a VPN .19 7.2.1.3 Scenario 3 - Communication between NGCN and TE using a VPN 20 7.2.1.4 Sc
13、enario 4 - Communication between NGCN and TE not using a VPN 20 7.2.1.5 Scenario 5 - Communication between NGCN and PSTN/ISDN.20 7.2.2 NAT traversal for media streams20 7.2.2.1 Scenario 1 - Communication between NGCNs using a VPN .21 7.2.2.2 Scenario 2 - Communication between NGCNs not using a VPN .
14、21 7.2.2.3 Scenario 3 - Communication between NGCN and TE using a VPN 21 7.2.2.4 Scenario 4 - Communication between NGCN and TE not using a VPN 21 7.2.2.5 Scenario 5 - Communication between NGCN and PSTN/ISDN.21 7.3 Firewall traversal21 7.3.1 Scenario 1 - Communication between NGCNs using a VPN .22
15、7.3.2 Scenario 2 - Communication between NGCNs not using a VPN .22 7.3.3 Scenario 3 - Communication between NGCN and TE using a VPN 22 7.3.4 Scenario 4 - Communication between NGCN and TE not using a VPN 22 7.3.5 Scenario 5 - Communication between NGCN and PSTN/ISDN 22 7.4 Identification 22 7.5 Prov
16、ision of identification information 23 7.5.1 Scenario 1 - Communication between NGCNs using a VPN .24 7.5.2 Scenario 2 - Communication between NGCNs not using a VPN .24 4 ETSI ETSI TR 102 478 V1.1.1 (2006-03) 7.5.3 Scenario 3 - Communication between NGCN and TE using a VPN 24 7.5.4 Scenario 4 - Comm
17、unication between NGCN and TE not using a VPN 24 7.5.5 Scenario 5 - Communication between NGCN and PSTN/ISDN 24 7.6 Security 25 7.6.1 Signalling security 25 7.6.1.1 Scenario 1 - Communication between NGCNs using a VPN .26 7.6.1.2 Scenario 2 - Communication between NGCNs not using a VPN .26 7.6.1.3 S
18、cenario 3 - Communication between NGCN and TE using a VPN 26 7.6.1.4 Scenario 4 - Communication between NGCN and TE not using a VPN 26 7.6.1.5 Scenario 5 - Communication between NGCN and PSTN/ISDN.27 7.6.2 Media security 27 7.6.2.1 Scenario 1 - Communication between NGCNs using a VPN .28 7.6.2.2 Sce
19、nario 2 - Communication between NGCNs not using a VPN .28 7.6.2.3 Scenario 3 - Communication between NGCN and TE using a VPN 29 7.6.2.4 Scenario 4 - Communication between NGCN and TE not using a VPN 29 7.6.2.5 Scenario 5 - Communication between NGCN and PSTN/ISDN.29 7.7 Session policy.29 7.7.1 Scena
20、rio 1 - Communication between NGCNs using a VPN .29 7.7.2 Scenario 2 - Communication between NGCNs not using a VPN .29 7.7.3 Scenario 3 - Communication between NGCN and TE using a VPN 30 7.7.4 Scenario 4 - Communication between NGCN and TE not using a VPN 30 7.7.5 Scenario 5 - Communication between
21、NGCN and PSTN/ISDN 30 7.8 Emergency calls .30 7.8.1 Scenario 1 - Communication between NGCNs using a VPN .30 7.8.2 Scenario 2 - Communication between NGCNs not using a VPN .30 7.8.3 Scenario 3 - Communication between NGCN and TE using a VPN 31 7.8.4 Scenario 4 - Communication between NGCN and TE not
22、 using a VPN 31 7.8.5 Scenario 5 - Communication between NGCN and PSTN/ISDN 31 7.9 Geographic location .31 7.9.1 Scenario 1 - Communication between NGCNs using a VPN .31 7.9.2 Scenario 2 - Communication between NGCNs not using a VPN .31 7.9.3 Scenario 3 - Communication between NGCN and TE using a VP
23、N 32 7.9.4 Scenario 4 - Communication between NGCN and TE not using a VPN 32 7.9.5 Scenario 5 - Communication between NGCN and PSTN/ISDN 32 History 33 5 ETSI ETSI TR 102 478 V1.1.1 (2006-03) Intellectual Property Rights IPRs essential or potentially essential to the present document may have been de
24、clared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, whi
25、ch is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs no
26、t referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ECMA on behalf of its members and those of the European Telecommunications Standards Institute (ETS
27、I). Brief History This Ecma Technical Report provides an overview of IP-based enterprise communication from/to Corporate telecommunication Networks (CNs) (also known as enterprise networks) including aspects of privately used home networks accessing public next generation networks (NGN). The present
28、 document is based upon the practical experience of Ecma member companies and the results of their active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI, IETF and other international and national standardization bodies. It represents a pragmatic and widely based consensus. Thi
29、s Ecma Technical Report has been adopted by the General Assembly of December 2005. 6 ETSI ETSI TR 102 478 V1.1.1 (2006-03) 1 Scope The present document identifies key use cases for communication with or between IP-based Next Generation Corporate Networks (NGCN) involving public next generation netwo
30、rks (NGN), analyses these use cases in terms of available or planned standardized technology and identifies requirements that will have to be met. The present document investigates configurations involving NGCNs and NGNs and their interoperating requirements. Non-IP-based interoperation, i.e. using
31、circuit-switched technology, between NGCNs and NGNs is outside the scope of the present document. The present document does not discriminate between wireless and wired access technology. All mobility aspects are outside the scope of the present document. They are covered by a companion Technical Rep
32、ort ECMA TR/92 1. Application considerations such as IP Centrex and CSTA (Computer Supported Telecommunications Applications) are outside the scope of the present document. 2 References 1 ECMA TR/92: “Corporate Telecommunication Networks - Mobility for Enterprise Communication“. 2 ECMA-307: “Corpora
33、te Telecommunication Networks - Signalling Interworking between QSIG and H.323 - Generic Functional Protocol for the Support of Supplementary Services (June 2000)“. 3 ITU-T Recommendation H.323: “Packet-based multimedia communications systems“. 4 IETF RFC 3261: “(SIP) Session Initiation Protocol“. 5
34、 IETF RFC 3489: “(STUN) Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)“. 6 IETF RFC 3711: “The Secure Real-time Transport Protocol (SRTP)“. 7 IETF RFC 3761: “The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Applic
35、ation (ENUM)“. 8 IETF RFC 3966: “The tel URI for Telephone Numbers“. 9 IETF RFC 2401: “Security Architecture for the Internet Protocol (IPSEC)“. 10 ITU-T Recommendation E.164: “The international public telecommunication numbering plan“. 3 Definitions and abbreviations 3.1 Definitions For the purpose
36、s of the present document the following definitions apply: Corporate telecommunication Network (CN): sets of equipment (Customer Premises Equipment and/or Customer Premises Networks) that are located at geographically dispersed locations and are interconnected to provide telecommunication services t
37、o a defined group of users Next Generation CN (NGCN): self-contained corporate network designed to take advantage of emerging IP-based communications solutions and that can have its own applications and service provisioning Next Generation Network (NGN): packet based public network able to provide t
38、elecommunication services, able to make use of multiple QoS enabled transport technologies and in which service related functions are independent of underlying transport related technologies 7 ETSI ETSI TR 102 478 V1.1.1 (2006-03) Virtual Private Network (VPN): virtual network that can deliver ubiqu
39、itous and secure connectivity over a shared network infrastructure (e.g. public carrier networks) using the same access policies as an enterprise network Application Service Provider (ASP): entity that provides telecommunication applications Session Service Provider (SSP): entity that intervenes in
40、and adds value to signalling for the establishment and control of multi-media sessions and optionally intervenes in and adds value to the multi-media sessions themselves Transport Service Provider (TSP): entity that provides IP connectivity 3.2 Abbreviations ALG Application Layer Gateway API Applica
41、tion Protocol Interface ASP Application Service ProviderB2BUA Back-to-Back User Agent CA Certification Authority CN Corporate telecommunication Network CSTA Computer Supported Telecommunications Applications ECC Emergency Call Centres ICE Interactive Connectivity Establishment IDSN Integrated Servic
42、es Digital Network IP Internet Protocol IPSEC IP SECurity ISDN Integrated Services Digital Network MIKEY Multimedia Internet KEYing NAT Network Address Translator NGCN Next Generation Corporate Network NGN public Next Generation Network PKI Public Key Infrastructure PSTN Packet Switched Public Data
43、Network QoS Quality of Service RTCP RTP Control Protocol RTP Real-Time ProtocolSBC Session Border Controller SDP Session Description Protocol SIP Session Initiation Protocol SOHO Single Office Home Office SRTCP Secure RTCP SRTP Secure Real-time Transport Protocol SSP Session Service Provider STUN Si
44、mple Traversal of UDP through NATS TCP Transmission Control Protocol TE Terminal EquipmentTLS Transport Layer Security TSP Transport Service Provider UA User Agent UAC User Agent Client UAS User Agent Server UDP User Datagram Protocol VoIP Voice over IP VPN Virtual Private Network 4 Void 8 ETSI ETSI
45、 TR 102 478 V1.1.1 (2006-03) 5 Background There has been a major evolution in enterprise telecommunications during the last few years. Prior to that, enterprise telecommunication networks (or corporate telecommunication networks, CN) were based on 64 kbit/s circuit-switched technology, which had syn
46、ergy with corresponding technology deployed in public Integrated Services Digital Networks (ISDN) and traditional analogue services. Those CNs primarily delivered a voice or telephony service to their users, although in principle they were capable of other services too, including video and various t
47、ypes of data service. For communication outside the enterprise, CNs were able to interwork with public ISDNs. Many public networks also offered optional services to corporate customers, such as Centrex services and premise equipment leasing and maintenance. With the advent of technologies for transm
48、itting voice and other real-time media over the Internet Protocol (IP) (e.g. based on Real Time Protocol (RTP) and corresponding new signalling protocols (e.g. H.323, SIP), there was potential for providing telephony and other real-time person-to-person services in the public Internet. Moreover, suc
49、h services also became possible in the IP-based “intranets“ already deployed in enterprises for data services such as corporate email, file transfer, corporate web services and access to the world wide web. Enterprises saw advantages such as savings on infrastructure costs (e.g. one wire to the desk) and the introduction of innovative services that exploited the convergence of real-time and data communication. The traditional PBX (Private Branch Exchange) was replaced by or evolved to an “IP-PBX“ or soft switch that supported IP connectivity to the desktop
