1、 ETSI TR 1Digital cellular telecoUniversal Mobile TelDiameter-barecom(3GPP TR 29.9TECHNICAL REPORT 129 909 V13.0.0 (2016communications system (Phaelecommunications System (LTE; based protocols usage and mmendations in 3GPP .909 version 13.0.0 Release 1316-01) hase 2+); (UMTS); 13) ETSI ETSI TR 129 9
2、09 V13.0.0 (2016-01)13GPP TR 29.909 version 13.0.0 Release 13Reference RTR/TSGC-0329909vd00 Keywords GSM,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 lucratif enre
3、gistre 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 present do
4、cument 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 drive wi
5、thin 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 present docum
6、ent, 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 authorized by wri
7、tten 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, PLUGTESTSTM, UM
8、TSTMand 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. ETSI ET
9、SI TR 129 909 V13.0.0 (2016-01)23GPP TR 29.909 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 members and
10、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.org/).
11、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 present
12、 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 references to
13、 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“, “can“
14、 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 129 909 V13.0.0 (2016-01)33GPP TR 29.909 version 13.
15、0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Symbols 7g33.3 Abbreviations . 7g34 The status of Diameter in 3GPP . 7g3Genera
16、l 7g3Diameter-based applications before Release 8 7g3Problem description. 8g3Existing and ongoing effort . 9g35 Proposed alternatives rules for identified problems . 9g35.1 General . 9g35.2 Item 1: Setting of “M“ bit on 3GPP defined AVPs 10g35.2.0 General 10g35.2.1 Proposal 1 (IETF) . 10g35.2.2 Prop
17、osal 2 . 10g35.2.3 3GPP evaluation . 10g35.3 Item 2: Re-use of AVPs 10g35.3.1 General 10g35.3.2 Proposal 1 . 10g35.3.3 Proposal 2 (IETF) . 10g35.3.4 3GPP evaluation . 11g35.4 Item 3: Version handling 11g35.4.0 General 11g35.4.1 Proposal 1 . 11g35.4.2 Proposal 2 . 11g35.4.3 Proposal 3 - IETF 11g35.4.
18、4 Proposal 4 . 11g35.4.5 Proposal 5 . 12g35.4.5.1 General 12g35.4.5.2 Defining new functionality . 12g35.4.5.2.1 General 12g35.4.5.2.2 Changing the version of the interface 12g35.4.5.2.3 Capabilities Exchange Request . 12g35.4.5.2.4 Capabilities Exchange Answer 13g35.4.5.2.5 AVPs . 13g35.4.5.2.5.1 S
19、upported-Application-Variant AVP 13g35.4.5.2.5.2 Vendor-Specific-Application-Variant AVP 14g35.4.6 3GPP evaluation . 14g35.5 Item 4: Setting of a new Application-Id . 14g35.5.0 General 14g35.5.1 Proposal 1 - IETF 15g35.5.2 Proposal 2 . 15g35.5.3 Proposal 3 . 16g35.5.4 3GPP evaluation . 16g3ETSI ETSI
20、 TR 129 909 V13.0.0 (2016-01)43GPP TR 29.909 version 13.0.0 Release 135.6 Item 5: New Values to an existing enumerated AVP . 16g35.6.1 Proposal 1 . 16g35.6.2 Proposal 2 . 16g35.6.3 Proposal 3 . 16g35.6.4 Proposal 4 . 17g35.6.5 Proposal 5 . 17g35.6.6 3GPP evaluation . 17g35.7 Item 6: Re-use of comman
21、ds in new applications 17g35.7.0 General 17g35.7.1 Proposal 1 . 17g35.7.2 3GPP evaluation . 17g36 Conclusion 18g3Annex A (Informative): Roaming Infrastructure 19g3A.0 General . 19g3A.1 Deployment of S6a-Diameter Relay Pools. 19g3A.2 Deployment of S9 and Wd*-Diameter Relay Pools . 21g3A.3 Guidelines
22、for connecting to the inter-operator Diameter infrastructure 21g3A.4 Void 22g3Annex B (Normative): Diameter routing extensions . 23g3B.0 General . 23g3B.1 Realm-based routing. 23g3B.2 NAI decoration . 23g3B.3 Explicit routing . 23g3B.4 Preserving the User-Name AVP . 23g3Annex C: Change history 24g3H
23、istory 25g3ETSI ETSI TR 129 909 V13.0.0 (2016-01)53GPP TR 29.909 version 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 form
24、al TSG approval. Should the TSG modify the contents of the present document, 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 a
25、pproval; 3 or greater indicates TSG approved document under change control. 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. Int
26、roduction As a new generation AAA (Authentication, Authorization and Accounting) protocol, Diameter has been used widely and will be used more and more widely in 3GPP. Since several 3GPP WGs are developing Diameter based interfaces, e.g. CT3, CT4, etc, so in order to ensure correctness and consisten
27、cy of using Diameter within all 3GPP WGs, a common set of principles, rules and recommendations across 3GPP WGs are necessary to be given clearly and followed. The present is to describe existing status of Diameter usage within 3GPP, find existing inconsistency of rules used for Diameter based inter
28、faces which were specified in 3GPP and propose common recommendations of using Diameter to all 3GPP WGs to follow. With more and more Diameter deployment, an inter-operator Diameter signalling network infrastructure will become necessary, so the present document will also study Diameter inter-operat
29、or considerations with brief guidelines on how to deploy Stage 3“. 6 IETF RFC 4072 (August 2005): “Diameter Extensible Authentication Protocol (EAP) Application“. 7 3GPP TS 32.299: “Diameter charging applications “. 8 3GPP TS 29.229: “Cx and Dx interfaces based on the Diameter protocol; Protocol det
30、ails“. 9 3GPP TS 29.230: “Diameter applications; 3GPP specific codes and identifiers“. 10 3GPP TS 29.061: “Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)“ 11 IETF Draft, “Diameter Base Protocol“, draft-ietf-dime-rfc3588bis-0
31、8.txt, working in progress. 12 IETF Draft, “Diameter Applications Design Guidelines“, draft-ietf-dime-app-design-guide-03.txt, working in progress. ETSI ETSI TR 129 909 V13.0.0 (2016-01)73GPP TR 29.909 version 13.0.0 Release 1313 GSMA PRD IR.34 v4.1, “Inter-Service Provider IP Backbone Guidelines“ 1
32、4 GSMA PRD IR.67 v2.1.0, “DNS Guidelines for Operators“ 15 GSMA PRD IR.40 v4.0, “Guidelines for IPv4 Addressing and AS Numbering for GPRS Network Infrastructure and Mobile Terminals“ 16 Void 17 3GPP TS 23.003: “Numbering, addressing and identification; Stage 3“ 18 IETF RFC 4282, “The Network Access
33、Identifier“ 19 3GPP TS 24.234: “3GPP System to WLAN Interworking; UE to Network protocols; Stage 3“ 20 IETF Draft, “Diameter User-Name and Realm Based Request Routing Clarifications“, draft-korhonen-dime-nai-routing-02.txt, Work in progress. 3 Definitions, symbols and abbreviations 3.1 Definitions F
34、or the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1. (none) 3.2 Symbols For the purposes of the present document
35、, the following symbols apply: (none) 3.3 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.
36、905 1. SAE System Architecture Evolution SDO Standard Development Organization 4 The status of Diameter in 3GPP General This subclause describes current status of Diameter usage before Release 8 and summarizes some problems of using Diameter protocol to satisfy 3GPP-specific requirements in the past
37、. This subclause is a basis for further discussion to give proposed rules in subclause 5. Diameter-based applications before Release 8 Diameter Base Protocol (see IETF RFC 3588 2) provides a set of messages and parameters to support AAA-related functionality with built-in protocol management mechani
38、sm, e.g. peer discovery, message routing, error handling, etc. Based on Diameter Base Protocol, IETF also defines many Diameter applications to support more specific requirements ETSI ETSI TR 129 909 V13.0.0 (2016-01)83GPP TR 29.909 version 13.0.0 Release 13in different scenarios, e.g. NASREQ (see I
39、ETF RFC 4284 3), Diameter Credit Control (see IETF RFC 4006 4), etc. Another important feature of Diameter Base Protocol 2 is that it also provides a set of principles and rules for extensibility to support more functionality in the future. That allows other SDOs like 3GPP to define more specific ap
40、plications, messages, parameters (AVPs) and values to fulfil SDO-specific requirements. Because of powerful functions and good extensibility, since Release 5, Diameter has been used widely in 3GPP systems, e.g. IMS, GBA, Interworking WLAN, Charging systems, PCC, etc. The Diameter protocol is designe
41、d to be extensible, using several mechanisms, including defining new AVP values, creating new AVPs, creating new Diameter applications, in addition to reuse of existing AVP values, AVPs and Diameter applications (see IETF RFC 3588 2 for more details). Based on different principles and requirements,
42、3GPP WGs, i.e. CT3, CT4 and SA5, develop their Diameter-based interfaces with different approach. Some interfaces are based on existing IETF-defined Diameter applications, for example Wa interface (see 3GPP TS 29.234 5) is based on Diameter base protocol (IETF RFC 3588 2), NASREQ (IETF RFC 4005 3) a
43、nd Diameter EAP application (IETF RFC 4072 6). Some interfaces are based on existing IETF-defined Diameter applications with 3PPP-specific AVPs/Values, for example Ro interfaces (see 3GPP TS 32.299 7) is based on Diameter Credit-Control Application (IETF RFC 4006 4) with some new 3GPP-specific AVPs.
44、 And some interfaces are new 3GPP-specific Diameter applications, e.g. Cx interface specified in 3GPP TS 29.229 8 which includes 3GPP-specific commands, AVP codes and results codes. 3GPP TS 29.230 9 serves as a placeholder for all 3GPP-specific Diameter applications, commands, AVP codes and result c
45、odes. Problem description During developing Diameter based interfaces, some inconsistent rules are found about how to using Diameter protocol to satisfy 3GPP-specific requirements in different 3GPP WGs. This subclause describes some examples of this issue. Wx interface, between a 3GPP AAA Server and
46、 a HSS, is specified in 3GPP TS 29.234 5 by CT4. A new application ID is allocated to it as some new AVPs with “M“ bit set are added to existing commands, e.g. 3GPP-AAA-Server-Name AVP, WLAN-User-Data AVP, etc. Wm interface, between a PDG and a 3GPP AAA Server/Proxy, is specified in 3GPP TS 29.234 5
47、 by CT4. For example, the 3GPP-WLAN-APN-Id AVP, with “M“ bit set (see table 10.1.1 in section 10.1, 3GPP TS 29.234 5), is a 3GPP-defined AVP and added to AAR command for authorization purpose, but no new application is applied for Wm interface. Gmb interface, between a GGSN and a BM-SC, is specified
48、 in 3GPP TS 29.061 10 by CT3. A new application ID is allocated to it as some new AVPs with “M“ bit set are added to existing commands, e.g. TMGI AVP, Required-MBMS-Bearer-Capabilities AVP, etc. So it is seen that cross CT WGs there are some inconsistent principles or rules of usage of application I
49、Ds and 3GPP-speific AVPs with “M“ bit set. There is another 3GPP-specific issue when Diameter is used in 3GPP, i.e. so-called cross-release issue. New AVPs may be added to the same interface (Diameter Application) in different Releases. If all these AVPs are “M“ bit set and added to the same Diameter Application (the same Application ID), inter-operability may occur when equipments following different releases are connected. For the issue, different principles are applied to different interfaces. One cas
