ETSI TR 102 634-2008 Coporate Networks (NGCN) Next Generation Corporate Networks (NGCN) - Identification and Routing (V1 1 1)《企业网络(NGCN)的下一代企业网络(NGCN) 识别和路由(版本1 1 1)》.pdf

1、 ETSI TR 102 634 V1.1.1 (2008-11)Technical Report Coporate Networks (NGCN)Next Generation Corporate Networks (NGCN) -Identification and RoutingETSI ETSI TR 102 634 V1.1.1 (2008-11) 2Reference DTR/ECMA-00353 Keywords ID, IP, SIP ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.

2、: +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 present document may be made a

3、vailable 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 printers of the PDF version kept o

4、n 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/status/status.asp If you fin

5、d 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 restriction extend to reproduction

6、 in all media. European Telecommunications Standards Institute 2008. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Membe

7、rs and of the 3GPP Organizational Partners. ETSI ETSI TR 102 634 V1.1.1 (2008-11) 3Contents Intellectual Property Rights 4g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 6g33 Definitions 7g33.1 External definitions 7g33.2 Other defi

8、nitions . 7g33.2.1 Number-based SIP URI 7g33.2.2 Home number-based SIP URI 7g33.2.3 Transient number-based SIP URI . 7g33.2.4 Telephone number 8g34 Abbreviations . 8g35 Background 8g36 Identified entities 8g37 Types of identifier 9g37.1 SIP, SIPS and TEL URIs as user identifiers (AoRs) 9g37.1.1 Use

9、of E.164 numbers . 12g37.1.2 Private numbers formatted as telephone-subscriber strings 14g37.1.3 Email-style SIP URIs 15g37.2 Dial strings . 16g37.3 Service identifiers . 16g37.4 Device identifiers . 17g38 Routing . 17g38.1 General routing principles 17g38.2 Routing to the enterprise domain . 18g38.

10、3 Routing to the home server within the enterprise domain 19g38.4 Roaming considerations . 19g39 Identification delivery and restriction 20g39.1 Identification delivery 20g39.2 Authenticity 21g39.3 Restriction 21g310 Summary of requirements and standardisation gaps 22g310.1 Requirements on NGNs 22g3

11、10.2 Requirements on enterprise networks. 23g310.3 Standardisation gaps . 23g3History 24g3ETSI ETSI TR 102 634 V1.1.1 (2008-11) 4Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential

12、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“, which is available from the ETSI Secretariat. Latest updates are

13、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 not referenced in ETSI SR 000 314 (or the updates on the ETSI We

14、b 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 (ETSI). Introduction The present document is one of a series of EC

15、MA publications that explore IP-based enterprise communication involving Corporate telecommunication Networks (CNs) (also known as enterprise networks) and in particular Next Generation Corporate Networks (NGCN). The series particularly focuses on inter-domain communication, including communication

16、between parts of the same enterprise, between enterprises and between enterprises and carriers. The present document discusses issues related to user identities and routing and builds upon concepts introduced in ECMA TR/95. The present document is based upon the practical experience of ECMA member c

17、ompanies 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. In particular, ECMA acknowledges valuable input from experts in ETSI

18、 TISPAN. ETSI ETSI TR 102 634 V1.1.1 (2008-11) 51 Scope The present document is one of a series of publications that provides an overview of IP-based enterprise communication involving Corporate telecommunication Networks (CNs) (also known as enterprise networks) and in particular Next Generation Co

19、rporate Networks (NGCN). The series particularly focuses on session level communication based on the Session Initiation Protocol (SIP) i.4, with an emphasis on inter-domain communication. This includes communication between parts of the same enterprise (on dedicated infrastructures and/or hosted), b

20、etween enterprises and between enterprises and public networks. Particular consideration is given to Next Generation Networks (NGN) as public networks and as providers of hosted enterprise capabilities. Key technical issues are investigated, current standardisation work and gaps in this area are ide

21、ntified, and a number of requirements are stated. Among other uses, this series of publications can act as a reference for other standardisation bodies working in this field, including ETSI TISPAN, 3GPP, IETF and ITU-T. The present document discusses session level user identification and routing. It

22、 uses terminology and concepts developed in TR/NGCN-General i.3. It identifies a number of requirements impacting NGN standardisation and concerning deployment of enterprise networks. The scope of the present document is limited to communications with a real-time element, including but not limited t

23、o voice, video, real-time text and instant messaging. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a com

24、plete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly availa

25、ble in the expected location might be found at http:/docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Fur

26、thermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hy

27、perlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For

28、non-specific references, the latest edition of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TR 102 634 V1.1.1 (2008-11) 62.2 Informative references The following referenced documents are not essential to the use of the present document but they assist the use

29、r with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. i.1 ECMA-155: “Private Integrated Services Networks - Addressing“. i.2 ECMA TR/86: “Corporate Telecommunication Networks - User Identification in

30、 a QSIG/SIP Environment“. i.3 ECMA TR/95: “Next Generation Corporate Networks (NGCN) - General“. i.4 IETF RFC 3261: “SIP: Session Initiation Protocol“. i.5 IETF RFC 3263: “Session Initiation Protocol (SIP): Locating SIP Servers“. i.6 IETF RFC 3323: “A Privacy Mechanism for the Session Initiation Pro

31、tocol (SIP)“. i.7 IETF RFC 3325: “Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks“. i.8 IETF RFC 3327: “Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts“. i.9 IETF RFC 3608: “Session Initiation Pr

32、otocol (SIP) Extension Header Field for Service Route Discovery During Registration“. i.10 IETF RFC 3761: “The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)“. i.11 IETF RFC 3966: “The tel URI for Telephone Numbers“. i.12 IETF RFC 4474: “Enh

33、ancements for Identity Management in the Session Initiation Protocol (SIP)“. i.13 IETF RFC 4916: “Connected Identity in the Session Initiation Protocol (SIP)“. i.14 IETF RFC 4967:“Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier“. i.15 IETF RFC 5031:“A Uniform Re

34、source Name (URN) for Emergency and Other Well-Known Services“. i.16 IETF draft-ietf-sip-gruu-15 “Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP)“. NOTE: At the time of publication of the present document, the IETF had approved draft-ietf-si

35、p-gruu-15 as a standards track RFC but had not published the RFC and had not allocated an RFC number. If the draft is no longer available, readers should look for the RFC with the same title. i.17 ITU-T Recommendation E.164: “The international public telecommunication numbering plan“. i.18 ITU-T Rec

36、ommendation H.350: “Directory services architecture for multimedia conferencing“. ETSI ETSI TR 102 634 V1.1.1 (2008-11) 73 Definitions For the purposes of the present document the following terms and definitions apply: 3.1 External definitions The present document uses the following terms defined in

37、 ECMA TR/95 i.3: Domain Enterprise network Home server Next Generation Corporate Network (NGCN) Next Generation Network (NGN) Private network traffic Public network traffic Roaming Roaming hub SIP intermediary The present document uses the following terms defined in ECMA-155 i.1: Numbering plan Priv

38、ate numbering plan 3.2 Other definitions 3.2.1 Number-based SIP URI A SIP or SIPS URI that contains a user=phone parameter, denoting the presence of a telephone number in telephone-subscriber format in the user part. NOTE: The telephone number can be an E.164 number or a private number. 3.2.2 Home n

39、umber-based SIP URI A number-based SIP URI for a user in which the domain part identifies the domain that provides home server (registrar and proxy) functionality for that user. 3.2.3 Transient number-based SIP URI A number-based SIP URI for a user in which the domain part does not identify the doma

40、in that provides home server (registrar and proxy) functionality for that user. NOTE: Transient number-based SIP URIs are aliases for the home number-based SIP URI for the telephone number concerned. Typically they are used during the routing of a SIP request. The domain part might, for example, con

41、tain the domain of an NGN that supports the enterprise concerned, rather than the enterprise itself. ETSI ETSI TR 102 634 V1.1.1 (2008-11) 83.2.4 Telephone number A numeric identifier that conforms to the numbering plan of a circuit-switched network. 4 Abbreviations AoR Address of Record B2BUA Back-

42、to-Back UA DNS Domain Name System GRUU Globally Routable UA URI IMS IP Multimedia Subsystem IP Internet Protocol ISDN Integrated Services Digital Network NAT Network Address Translation NGCN Next Generation Corporate Network NGN Next Generation Network PDA Personal Digital AssistantPSTN Public Switc

43、hed Telephone Network SIP Session Initiation Protocol UA User Agent URI Universal Resource Identifier URN Universal Resource Name 5 Background General concepts of NGCNs are discussed in i.3. In particular, that document describes use of the Session Initiation Protocol (SIP) i.4 for session level com

44、munications within enterprise networks and with other domains. It focuses on enterprise networks based on enterprise infrastructure (NGCN), but also covers hosting on other networks, in particular NGNs, using the same infrastructure that supports public networks. A major consideration for SIP-based

45、communications is identification of the users involved and routing based on such identifiers. When one user initiates a communications session, that user needs to identify the user with which the session is to be established, and the network needs to establish the session to that user or to a nomina

46、ted alternative. The second user often needs to receive the identity of the first user (the calling user) for various purposes. Likewise the first user often needs to receive the identity of the user to which the communication session is eventually established, which might not be the user to which e

47、stablishment was originally requested. SIP provides various forms of identifiers for users. These have already been discussed in ECMA TR/86 i.2, primarily for the purpose of interworking with circuit-switched enterprise networks based on the QSIG signalling protocol. However, the topic needs to be e

48、xamined from the broader perspective of NGCNs and their SIP-based operation with other domains. 6 Identified entities Identifiers are needed for entities involved in communication within an enterprise network. For the purposes of the present document, the most important identified entity is a user.

49、A users identifier is used for several purposes, including: indicating the user with which a communication is to be established; identifying a user already participating in a communication (e.g. the identity of the calling user or the identity of the user who has responded to a communication request); charging. ETSI ETSI TR 102 634 V1.1.1 (2008-11) 9Although in many cases a user identifier, or an Address of Record (AoR), can identify a single human user, often it can indicate something else, e.