1、 Reference number ISO/IEC TR 12861:2009(E) ISO/IEC 2009TECHNICAL REPORT ISO/IEC TR 12861 First edition 2009-04-15Information technology Telecommunications and information exchange between systems Next Generation Corporate Networks (NGCN) Identification and routing Technologies de linformation Tlcomm
2、unications et change dinformation entre systmes Rseaux dentreprise de prochaine gnration (NGCN) Identification et routage ISO/IEC TR 12861:2009(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not
3、 be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe
4、 is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO me
5、mber bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2009 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any for
6、m or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09
7、47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2009 All rights reservedISO/IEC TR 12861:2009(E) ISO/IEC 2009 All rights reserved iiiContents Page Foreword iv Introduction.v 1 Scope1 2 Normative references1 3 Terms and definitions .2 3.1 External definitions .2 3.2 Oth
8、er definitions3 4 Abbreviated terms .3 5 Background4 6 Identified entities .4 7 Types of identifier5 7.1 SIP, SIPS and TEL URIs as user identifiers (AoRs) .5 7.1.1 Use of E.164 numbers.8 7.1.2 Private numbers formatted as telephone-subscriber strings.10 7.1.3 Email-style SIP URIs11 7.2 Dial strings
9、.12 7.3 Service identifiers13 7.4 Device identifiers.13 8 Routing .14 8.1 General routing principles14 8.2 Routing to the enterprise domain15 8.3 Routing to the home server within the enterprise domain .15 8.4 Roaming considerations.16 9 Identification delivery and restriction .17 9.1 Identification
10、 delivery17 9.2 Authenticity17 9.3 Restriction18 10 Summary of requirements and standardisation gaps .19 10.1 Requirements on NGNs 19 10.2 Requirements on enterprise networks20 10.3 Standardisation gaps 20 ISO/IEC TR 12861:2009(E) iv ISO/IEC 2009 All rights reservedForeword ISO (the International Or
11、ganization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the
12、respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of info
13、rmation technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft Internati
14、onal Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document ma
15、y be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC TR 12861 was prepared by Ecma International (as ECMA TR/96) and was adopted, under a special “fast-track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Informa
16、tion technology, in parallel with its approval by national bodies of ISO and IEC. ISO/IEC TR 12861:2009(E) ISO/IEC 2009 All rights reserved vIntroduction This Technical Report is one of a series of Ecma publications that explore IP-based enterprise communication involving Corporate telecommunication
17、 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 between parts of the same enterprise, between enterprises and between enterprises and carriers. This
18、 particular Technical Report discusses issues related to user identities and routing and builds upon concepts introduced in ISO/IEC TR 12860. This Technical Report is based upon the practical experience of Ecma member companies and the results of their active and continuous participation in the work
19、 of ISO/IEC JTC 1, 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 TISPAN. TECHNICAL REPORT ISO/IEC TR 12861:2009(E) ISO/IEC 2009 All rights reser
20、ved 1Information technology Telecommunications and information exchange between systems Next Generation Corporate Networks (NGCN) Identification and routing 1 Scope This Technical Report is one of a series of publications that provides an overview of IP-based enterprise communication involving Corpo
21、rate telecommunication Networks (CNs) (also known as enterprise networks) and in particular Next Generation Corporate Networks (NGCN). The series particularly focuses on session level communication based on the Session Initiation Protocol (SIP) 4, with an emphasis on inter-domain communication. This
22、 includes communication between parts of the same enterprise (on dedicated infrastructures and/or hosted), between 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 cap
23、abilities. Key technical issues are investigated, current standardisation work and gaps in this area are identified, 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 TI
24、SPAN, 3GPP, IETF and ITU-T. This particular Technical Report discusses session level user identification and routing. It uses terminology and concepts developed in ISO/IEC TR 12860. It identifies a number of requirements impacting NGN standardisation and concerning deployment of enterprise networks.
25、 The scope of this Technical Report is limited to communications with a real-time element, including but not limited to voice, video, real-time text and instant messaging. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated refe
26、rences, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. 1 ISO/IEC 11571:1998, Information technology Telecommunications and information exchange between systems Private Integrated Services Networks Addressing 2
27、 ECMA TR/86, Corporate Telecommunication Networks User Identification in a SIP/QSIG Environment 3 ISO/IEC TR 12860:2009, Information technology Telecommunications and information exchange between systems Next Generation Corporate Networks (NGCN) General 4 IETF RFC 3261, SIP: Session Initiation Proto
28、col 5 IETF RFC 3263, Session Initiation Protocol (SIP): Locating SIP Servers 6 IETF RFC 3323, A Privacy Mechanism for the Session Initiation Protocol (SIP) 7 IETF RFC 3325, Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks ISO/IEC TR 12861:2009
29、(E) 2 ISO/IEC 2009 All rights reserved8 IETF RFC 3327, Session Initiation Protocol (SIP) Extension Header Field for Registering Non- Adjacent Contacts 9 IETF RFC 3608, Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration 10 IETF RFC 3761, The E.164
30、 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) 11 IETF RFC 3966, The tel URI for Telephone Numbers 12 IETF RFC 4474, Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP) 13 IETF RFC 4916, Connected Identity
31、in the Session Initiation Protocol (SIP) 14 IETF RFC 4967, Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier 15 IETF RFC 5031, A Uniform Resource Name (URN) for Emergency and Other Well-Known Services 16 IETF draft-ietf-sip-gruu-15, Obtaining and Using Globally Ro
32、utable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP) NOTE At the time of publication of this Technical Report, the IETF had approved draft-ietf-sip-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 ava
33、ilable, readers should look for the RFC with the same title. 17 ITU-T Rec. E.164, The international public telecommunication numbering plan 18 ITU-T Rec. H.350, Directory services architecture for multimedia conferencing 3 Terms and definitions For the purposes of this document, the following terms
34、and definitions apply. 3.1 External definitions This Technical Report uses the following terms defined in ISO/IEC TR 12860: Domain Enterprise network Home server Next Generation Corporate Network (NGCN) Next Generation Network (NGN) Private network traffic Public network traffic Roaming Roaming hub
35、ISO/IEC TR 12861:2009(E) ISO/IEC 2009 All rights reserved 3 SIP intermediary This Technical Report uses the following terms defined in ISO/IEC 11571 1: Numbering plan Private numbering plan 3.2 Other definitions 3.2.1 Number-based SIP URI A SIP or SIPS URI that contains a user=phone parameter, denot
36、ing 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 number-based SIP URI A number-based SIP URI for a user in which the domain part identifies the domain that provides home server (re
37、gistrar 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 domain that provides home server (registrar and proxy) functionality for that user. NOTE Transient number-based SIP URIs are aliases f
38、or 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, contain the domain of an NGN that supports the enterprise concerned, rather than the enterprise itself. 3.2.4 Telephone number A numer
39、ic identifier that conforms to the numbering plan of a circuit-switched network. 4 Abbreviated terms AoR Address of Record B2BUA Back-to-Back UA DNS Domain Name System GRUU Globally Routable UA URI IMS IP Multimedia Subsystem IP Internet Protocol ISDN Integrated Services Digital Network NGCN Next Ge
40、neration Corporate Network NGN Next Generation Network PSTN Public Switched Telephone Network SIP Session Initiation Protocol ISO/IEC TR 12861:2009(E) 4 ISO/IEC 2009 All rights reservedUA User Agent URI Universal Resource Identifier URN Universal Resource Name 5 Background General concepts of NGCNs
41、are discussed in 3. In particular, that document describes use of the Session Initiation Protocol (SIP) 4 for session level communications within enterprise networks and with other domains. It focuses on enterprise networks based on enterprise infrastructure (NGCN), but also covers hosting on other
42、networks, in particular NGNs, using the same infrastructure that supports public networks. A major consideration for SIP-based 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 t
43、he user with which the session is to be established, and the network needs to establish the session to that user or to a nominated 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 receiv
44、e the identity of the user to which the communication session is eventually established, which might not be the user to which establishment was originally requested. SIP provides various forms of identifiers for users. These have already been discussed in ECMA TR/86 2, primarily for the purpose of i
45、nterworking with circuit-switched enterprise networks based on the QSIG signalling protocol. However, the topic needs to be examined from the broader perspective of NGCNs and their SIP-based operation with other domains. 6 Identified entities Identifiers are needed for entities involved in communica
46、tion within an enterprise network. For the purposes of this Technical Report, the most important identified entity is a user. 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
47、 communication (e.g., the identity of the calling user or the identity of the user who has responded to a communication request); charging. Although 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.g.: a role or
48、 function performed by a single human user (e.g., director of finance), this identifier remaining the same even though the occupant of the role might change; a group of human users (e.g., a department or function); a service or function performed by an automaton (e.g., voicemail or conferencing serv
49、ice). A user identifier does not explicitly identify a particular device (e.g., terminal, server). In particular cases there may be a one-to-one relationship between device and user, but in many cases this will not be so: a user can have more than one device (e.g., a user with a PC, a fixed phone and a mobile phone or PDA; a service replicated on a number of servers); a device can support more than one user (e.g., two or more u
