ETSI TR 124 969-2016 Universal Mobile Telecommunications System (UMTS) LTE Business Trunking Next Generation Corporate Network (NGCN) - Next Generation Network (NGN) interfaces imp.pdf

《ETSI TR 124 969-2016 Universal Mobile Telecommunications System (UMTS) LTE Business Trunking Next Generation Corporate Network (NGCN) - Next Generation Network (NGN) interfaces imp.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 124 969-2016 Universal Mobile Telecommunications System (UMTS) LTE Business Trunking Next Generation Corporate Network (NGCN) - Next Generation Network (NGN) interfaces imp.pdf（71页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 1Universal Mobile TelBuNext Generatio- Next Geinterface(3GPP TR 24.9TECHNICAL REPORT 124 969 V13.0.0 (2016elecommunications System (LTE; Business trunking; tion Corporate Network (NGCNGeneration Network (NGN) ces implementation guide .969 version 13.0.0 Release 1316-01) (UMTS); CN) ) ETSI E

2、TSI TR 124 969 V13.0.0 (2016-01)13GPP TR 24.969 version 13.0.0 Release 13Reference RTR/TSGC-0124969vd00 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis 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 lucra

3、tif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the pr

4、esent document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network

5、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 find errors in the prese

6、nt document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorize

7、d by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTES

8、TSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association.

9、 ETSI ETSI TR 124 969 V13.0.0 (2016-01)23GPP TR 24.969 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI memb

10、ers 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 available on the ETSI Web server (https:/ipr.etsi

11、.org/). 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 Web server) which are, or may be, or may become, essential to the

12、 present document. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being refer

13、ences to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not

14、“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 124 969 V13.0.0 (2016-01)33GPP TR 24.969 ver

15、sion 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 6g31 Scope 7g32 References 7g33 Definitions and abbreviations . 11g33.1 Definitions 11g33.2 Abbreviations . 11g34 Overview 11g34.1 Business Trunking architecture and protocols 11g34.2 R

16、oadmap to relevant specifications 12g34.3 Specification methodology . 12g34.3.1 General 12g34.3.2 Notation for status codes . 12g34.4 Major capabilities at the NGCN-NGN interface 13g34.4.1 Service capabilities . 13g34.4.2 Protocol capabilities 14g34.4.2.1 General 14g34.4.2.2 Basic requirements 14g34

17、.4.2.3 Extensions for session control . 14g34.4.2.4 Extensions for registration (subscription based approach only) 15g35 Common guidelines 16g35.1 Reference model for interconnection . 16g35.2 Control plane interconnection 16g35.2.1 SIP procedures 16g35.2.1.1 Outgoing requests from NGCN site 16g35.2

18、.1.1.1 General 16g35.2.1.1.2 Calling and connected identifiers 16g35.2.1.1.3 Privacy . 17g35.2.1.1.4 Called identifier . 17g35.2.1.2 Incoming requests to NGCN site 17g35.2.1.2.1 General 17g35.2.1.2.2 Calling identity 17g35.2.1.2.3 Called identity . 17g35.2.1.2.4 Request-URI 18g35.2.2 SIP protocol el

19、ements . 18g35.2.2.1 General 18g35.2.2.2 Methods. 18g35.2.2.3 Responses 19g35.2.2.4 Header fields . 21g35.2.2.4.1 General 21g35.2.2.4.2 Accept 21g35.2.2.4.3 Allow . 21g35.2.2.4.4 Contact. 21g35.2.2.4.5 Max-Breadth 21g35.2.2.4.6 Max-Forwards . 22g35.2.2.4.7 P-Private-Network-Indication . 22g35.2.2.4.

20、8 Record-Route . 22g35.2.2.4.9 Route . 22g35.2.2.4.10 Via . 22g35.2.2.4.11 Summary of message headers 22g3ETSI ETSI TR 124 969 V13.0.0 (2016-01)43GPP TR 24.969 version 13.0.0 Release 135.2.2.5 Supported Message bodies 47g35.2.2.6 Event packages 48g35.2.3 SDP protocol . 48g35.2.3 SDP protocol. 48g35.

21、2.4 Control plane transport . 50g35.3 User plane interconnection . 50g35.3.1 Media and Codec 50g35.4 Numbering, naming and addressing . 51g35.5 IP Version . 51g35.6 Security 52g36 Specific guidelines for the subscription based approach 52g36.1 Reference model for interconnection . 52g36.1.1 General

22、52g36.1.2 Functionalities performed by entities at the service layer . 52g36.1.2.1 P-CSCF, S-CSCF 52g36.1.2.2 AS . 52g36.1.2.3 NGCN . 52g36.1.3 Functionalities performed by entities at the transport layer 52g36.1.3.1 C-BGF . 52g36.2 Control plane interconnection 53g36.2.1 SIP procedures 53g36.2.1.1

23、Outgoing requests from NGCN site 53g36.2.1.1.1 General 53g36.2.1.1.2 Calling and connected identifiers 53g36.2.1.1.3 Privacy . 53g36.2.1.1.4 Called identifier . 53g36.2.1.1.5 SDP offer . 53g36.2.1.2 Incoming requests to NGCN site 54g36.2.1.2.1 General 54g36.2.1.2.2 Calling identity 54g36.2.1.2.3 Cal

24、led identity . 54g36.2.1.2.4 Request-URI 54g36.2.1.3 Registration . 54g36.2.2 SIP protocol elements . 55g36.2.2.1 General 55g36.2.2.2 Methods. 55g36.2.2.3 Responses 55g36.2.2.4 Header fields . 55g36.2.2.5 Supported message bodies 61g36.2.2.6 Event packages 61g36.2.3 SDP protocol . 61g36.2.4 Control

25、plane transport . 61g36.2.4.1 Keep alive mechanism 61g36.2.4.2 P-CSCF redundancy 62g36.3 User plane interconnection . 62g36.3.1 Media and Codec 62g36.4 Numbering, naming and addressing . 62g36.5 IP Version . 62g36.6 Security 62g37 Specific guidelines for the peering-based approach . 63g37.1 Referenc

26、e model for interconnection . 63g37.1.1 General 63g37.1.2 Functionalities performed by entities at the service layer . 63g37.1.2.1 Interconnection Border Control Function (IBCF) . 63g37.1.2.2 NGCN . 63g37.2 Control plane interconnection 63g37.2.1 SIP procedures 63g37.2.1.1 Outgoing requests from NGC

27、N site 63g37.2.1.2 Incoming requests to NGCN site 64g37.2.1.3 Registration . 64g3ETSI ETSI TR 124 969 V13.0.0 (2016-01)53GPP TR 24.969 version 13.0.0 Release 137.2.2 SIP protocol elements . 64g37.2.2.1 General 64g37.2.2.2 Methods. 64g37.2.2.3 Responses 64g37.2.2.4 Header fields . 64g37.2.2.5 Support

28、ed message bodies 67g37.2.2.6 Event packages 67g37.2.3 SDP protocol . 67g37.3 User plane interconnection . 67g37.3.1 Media and Codec 67g37.4 Numbering, naming and addressing . 68g37.5 IP Version . 68g3Annex A: Change history 69g3History 70g3ETSI ETSI TR 124 969 V13.0.0 (2016-01)63GPP TR 24.969 versi

29、on 13.0.0 Release 13Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present doc

30、ument, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change con

31、trol. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 124 969 V13.0.0 (2016-01)73GPP TR 24.969 version 13.0.0 Rele

32、ase 131 Scope The purpose of the present document is to give an implementation guide to the relevant Common IMS specifications and functions used in the interconnection of a Next Generation Corporate Network site (NGCN site) to the NGN. The present document addresses control plane signalling (usage

33、of SIP and SDP protocols, required SIP headers) as well as other interconnecting aspects like security, numbering/naming/addressing and user plane issues such as transport protocol, media and codecs actually covered in a widespread set of 3GPP and ETSI TISPAN specifications, as seen from the perspec

34、tive of an NGCN site. Advice-of-charge aspects are addressed as far as SIP signalling is concerned. The present document is based on 3GPP TS 24.229 12. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - Refe

35、rences are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a

36、GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 IETF RFC 3261 (2002): “SIP: Session Initiation Protocol“. 2 3GPP TS 22.519: “; Business communication requirements, stage 1“. 3 3GPP TS 24.525: “Business tr

37、unking; Architecture and functional description“. 4 3GPP TS 24.523: “Core and enterprise NGN interaction scenarios; Architecture and functional description“. 5 IETF RFC 2976 (2000): “The SIP INFO Method“. 6 IETF RFC 3262 (2002): “Reliability of Provisional Responses in the Session Initiation Protoco

38、l (SIP)“. 7 IETF RFC 3515 (2003): “The Session Initiation Protocol (SIP) Refer Method“. 8 IETF RFC 3311 (2002): “The Session Initiation Protocol (SIP) UPDATE method“. 9 IETF RFC 6665 (2012): “Session Initiation Protocol (SIP) Specific Event Notification“. 10 IETF RFC 3428: “Session Initiation Protoc

39、ol (SIP) Extension for Instant Messaging“. 11 IETF RFC 3903: “An Event State Publication Extension to the Session Initiation Protocol (SIP)“. 12 3GPP TS 24.229: “ Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)

40、; Stage 3 “. 13 IETF RFC 791 (1981): “DARPA Internet Program Protocol Specification“. 14 IETF RFC 2460 (1998): “Internet Protocol, Version 6 (IPv6) Specification“. 15 Void. 16 ETSI ES 282 001 (V2.y.z): “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN)

41、; NGN Functional Architecture“. ETSI ETSI TR 124 969 V13.0.0 (2016-01)83GPP TR 24.969 version 13.0.0 Release 1317 3GPPTS 23.228: “ IP Multimedia Subsystem (IMS); Stage 2“. 18 IETF RFC 3966 (2004): “The tel URI for Telephone Numbers“. 19 IETF RFC 3860 (2004): “Common Profile for Instant Messaging (CP

42、IM)“. 20 IETF RFC 3859 (2004): “Common Profile for Presence (CPP)“. 21 3GPP TS 29.162: “Interworking between IM CN Sub-system and IP networks“. 22 ECMA TR/96 “NGCN-Identity: “Next Generation Corporate Networks (NGCN) - Identification and routing“. 23 IETF RFC 3841 (2004): “Caller Preferences for the

43、 Session Initiation Protocol (SIP)“. 24 IETF RFC 6442 (December 2011): “Location Conveyance for the Session Initiation Protocol“. 25 IETF RFC 7044 (2014): “An Extension to the Session Initiation Protocol (SIP) for Request History Information“. 26 IETF RFC 3911 (2004): “The Session Initiation Protoco

44、l (SIP) “Join“ Header“. 27 IETF RFC 4028 (April 2005): “Session Timers in the Session Initiation Protocol (SIP)“. 28 IETF RFC 7315 (2014): “Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)“. 29 IETF RFC 3325 (2002): “Priv

45、ate Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks“. 30 IETF RFC 3323 (2002): “A Privacy Mechanism for the Session Initiation Protocol (SIP)“. 31 IETF RFC 3326 (2002): “The Reason Header Field for the Session Initiation Protocol (SIP)“. 32 I

46、ETF RFC 3329 (2003): “Security Mechanism Agreement for the Session Initiation Protocol (SIP)“. 33 IETF RFC 3892 (2004): “The Session Initiation Protocol (SIP) Referred-By Mechanism“. 34 IETF RFC 6050 (November 2010): “A Session Initiation Protocol (SIP) Extension for the Identification of Services“.

47、 35 IETF RFC 5002 (2007): “The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)“. 36 IETF RFC 4457 (2006): “The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-header)“. 37 IETF RFC 3313 (2003): “Private Session Initiation Protocol (SIP) Extensions for Me

48、dia Authorization“. 38 IETF RFC 5009 (2007): “Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media“. 39 IETF RFC 3891 (2004): “The Session Initiation Protocol (SIP) “Replaces“ Header“. 40 IETF RFC 4412 (2006): “Communications Resource Priority

49、 for the Session Initiation Protocol (SIP)“. 41 ISO/IEC 9646-7 (1995): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements“. 42 ETSI ES 282 007: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture“. 43 IETF RFC 3856 (2004): “A Presence Event Package for the Session Initiation Protocol (SI