ETSI ES 283 035-2015 Network Technologies (NTECH) Network Attachment e2 interface based on the DIAMETER protocol (V3 1 1)《网络技术 (NTECH) 网络连接 基于DIAMETER协议的e2接口 (V3 1 1)》.pdf

《ETSI ES 283 035-2015 Network Technologies (NTECH) Network Attachment e2 interface based on the DIAMETER protocol (V3 1 1)《网络技术 (NTECH) 网络连接 基于DIAMETER协议的e2接口 (V3 1 1)》.pdf》由会员分享，可在线阅读，更多相关《ETSI ES 283 035-2015 Network Technologies (NTECH) Network Attachment e2 interface based on the DIAMETER protocol (V3 1 1)《网络技术 (NTECH) 网络连接 基于DIAMETER协议的e2接口 (V3 1 1)》.pdf（29页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI ES 283 035 V3.1.1 (2015-04) Network Technologies (NTECH); Network Attachment; e2 interface based on the DIAMETER protocol ETSI STANDARD ETSI ETSI ES 283 035 V3.1.1 (2015-04) 2 Reference RES/NTECH-00024-DIAMETER-e2 Keywords interface, network, system ETSI 650 Route des Lucioles F-06921 Sophia A

2、ntipolis 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 The present document can be downloaded from: http:/www.etsi.org/standards-search The presen

3、t document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such version

4、s and/or in print, the only prevailing document is the print of the Portable Document Format (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 curr

5、ent 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 document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be

6、reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized 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 restr

7、iction extend to reproduction in all media. European Telecommunications Standards Institute 2015. All rights reserved. DECTTM, PLUGTESTSTM, 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

8、its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI ES 283 035 V3.1.1 (2015-04) 3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1 Normative re

9、ferences . 6g32.2 Informative references 7g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Overview 8g35 Procedure descriptions . 9g35.1 General . 9g35.2 Procedures on the CLF - AF interface 10g35.2.1 Information query . 10g35.2.1.1 Overview. 10g35.2.1.2 Procedure a

10、t the AF side . 11g35.2.1.3 Procedure at the CLF side . 11g35.2.2 Event Registration/Deregistration . 12g35.2.2.1 Overview . 12g35.2.2.2 Procedure at the AF side . 13g35.2.2.3 Procedure at the CLF side . 13g35.2.3 Notification Events . 14g35.2.3.1 Overview . 14g35.2.3.2 Procedure at the CLF side . 1

11、4g35.2.3.3 Procedure at the AF side . 15g36 Use of the Diameter base protocol . 15g36.0 General . 15g36.1 Securing Diameter messages 15g36.2 Accounting functionality 15g36.3 Use of sessions . 15g36.4 Transport protocol 16g36.5 Routing considerations . 16g36.6 Advertising application support . 16g37

12、DIAMETER application. 16g37.0 General . 16g37.1 Commands 17g37.1.0 General 17g37.1.1 User-Data-Request command . 17g37.1.2 User-Data-Answer command 17g37.1.3 Subscribe-Notifications-Request (SNR) Command . 18g37.1.4 Subscribe-Notifications-Answer (SNA) Command 18g37.1.5 Push-Notification-Request (PN

13、R) Command . 19g37.1.6 Push-Notifications-Answer (PNA) Command 19g37.2 Result-Code AVP values 19g37.2.0 General 19g37.2.1 Success 20g37.2.2 Permanent failures 20g37.2.3 Transient failures 20g37.3 AVPs 20g37.3.0 General 20g37.3.1 Location-Information AVP . 22g37.3.1A Civic-Location AVP . 22g3ETSI ETS

14、I ES 283 035 V3.1.1 (2015-04) 4 7.3.1B Geospatial-Location AVP . 22g37.3.2 Policy-Control-Contact-Point AVP 22g37.3.3 Terminal-Type AVP . 22g37.3.4 Requested-Information AVP 22g37.3.5 Line-Identifier AVP 23g37.3.6 Event-Type AVP 23g37.4 Use of namespaces . 25g37.4.0 General 25g37.4.1 AVP codes 25g37

15、.4.2 Experimental-Result-Code AVP values 25g37.4.3 Command Code values . 25g37.4.4 Application-ID value 25g3Annex A (informative): Application to NGN Architectures . 26g3A.1 Overview 26g3A.2 Mapping of e2 operations and terminology to Diameter 26g3Annex B (informative): Change history . 28g3History

16、29g3ETSI ETSI ES 283 035 V3.1.1 (2015-04) 5 Intellectual 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 non-members, and can be foun

17、d 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 (http:/ipr.etsi.org). Pursuant to the ETSI IPR Polic

18、y, 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 document. Foreword This ETSI

19、Standard (ES) has been produced by ETSI Technical Committee Network Technologies (NTECH). Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ET

20、SI 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 ES 283 035 V3.1.1 (2015-04) 6 1 Scope The present document specifies a Diameter application for use between a Connectivity sess

21、ion Location and repository Function (CLF) and an Application Function (AF). 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For

22、non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause w

23、ere valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 Void. 2 Void. 3 Void. 4 Void. 5 ETSI ES 283 034: “Telecommunications and Internet converged Services and Protocols for

24、 Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol“. 6 ETSI TS 129 229: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Cx and Dx interfaces based on the Diameter protocol; P

25、rotocol details (3GPP TS 29.229)“. 7 ETSI TS 129 329: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Sh interface based on the Diameter protocol; Protocol details (3GPP TS 29.329)“. 8 ETSI TS 129 209: “Universal Mobile Telecommunicatio

26、ns System (UMTS); Policy control over Gq interface (3GPP TS 29.209)“. 9 IETF RFC 2960: “Stream Control Transmission Protocol“. 10 IETF RFC 6733: “Diameter Base Protocol“. 11 IETF RFC 3309: “Stream Control Transmission Protocol (SCTP) Checksum Change“. 12 IETF RFC 3554: “On the use of Stream Control

27、Transmission Protocol (SCTP) with IPSec“. 13 ETSI TS 182 008: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Presence Service; Architecture and functional description Endorsement of 3GPP TS 23.141 and OMA-AD-Presence_SIMPLE-V1_0“. 14 Void. 15 IETF

28、 RFC 4776: “Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information“. 16 IETF RFC 3825: “Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information“. ETSI ETSI ES 283 035 V3.1.1 (2015-04) 7 17 IETF RFC 4234:

29、 “Augmented BNF for Syntax Specifications: ABNF“. 18 Recommendation ITU-T M.1400: “Designations for interconnections among operators networks“. 19 ISO 3166-1: “Codes for the representation of names of countries and their subdivisions - Part 1: Country codes“. 20 ETSI TS 129 061: “Digital cellular te

30、lecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) (3GPP TS 29.061)“. 21 ETSI TS 124 229: “IP multimedia call control protocol based on

31、Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229)“. 22 IETF RFC 3986: “Uniform Resource Identifier (URI): Generic Syntax“. 23 IETF RFC 4119: “A Presence-based GEOPRIV Location Object Format“. 2.2 Informative references References are either specific (

32、identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks included in th

33、is clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI ES 282 001: “Telecommunication

34、s and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture“. i.2 ETSI ES 282 004: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)“.

35、 i.3 ETSI ES 282 003: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture“. i.4 ETSI ES 282 007: “Telecommunications and Internet converged Services and Protocols for Advanced Ne

36、tworking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: access identifier: identifier of an access network termination point NOTE: Examples of acce

37、ss identifiers include wireline terminations identifiers in fixed access networks and mobile cell identifiers. access network: collection of network entities and interfaces that provide the underlying IP transport connectivity between end user devices and other networks access record: set of informa

38、tion stored in the CLF in relation to an access identifier Application Function (AF): element of the network architecture offering - or providing access to - applications that require information about the characteristics of the IP-connectivity session used to access such applications ETSI ETSI ES 2

39、83 035 V3.1.1 (2015-04) 8 Attribute-Value Pair (AVP): Information Element in a Diameter message NOTE: See RFC 6733 10. IP connectivity user: entity requesting IP connectivity from an access network session record: set of information stored in the CLF in relation to an IP address 3.2 Abbreviations Fo

40、r the purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form AF Application Function ASCII American Standard Code for Information Interchange ASF Application Server Function AVP Attribute-Value PairCLF Connectivity session Location and repository Functio

41、n CSCF Call Session Control Function DHCP Dynamic Host Configuration Protocol FQDN Fully Qualified Domain Name IANA Internet Assigned Numbers Authority IBCF Interconnection Border Control Function ICC ITU Carrier Code IETF Internet Engineering Task Force IMS IP Multimedia Subsystem IP Internet Proto

42、col LAC Location-Area-CodeLCI Location Configuration Information NASS Network Attachment Sub-SystemNGN Next Generation Network NOC Network-Operator-Code P-CSCF Proxy Call Session Control Function PDBF Profile Data Base Function PIDF LO Presence Information Data Format Location Object PNA Presence Ne

43、twork Agent PNR Push-Notification-Request RACF Resource and Admission Control Function RACS Resource and Admission Control Subsystem RFC Request For Comments SCTP Stream Control Transport Protocol SNA Subscribe-Notifications-AnswerSNR Subscribe-Notifications-Request UAAF User Authentication and Auth

44、orization Function UDA User-Data-Answer UDR User-Data-Request UE User EquipmentURI Uniform Resource Identifier 4 Overview The present document specifies a Diameter application for use between a Connectivity session Location and repository Function (CLF) and an Application Function (AF). The interfac

45、e between the CLF and the AF is known as the e2 interface (figure 1). A Connectivity session Location and repository Function (CLF) is a data base in an access network that maintains information associated to an IP address and/or an access identifier in the form of dynamic session records or static

46、access records, respectively. How a CLF obtains this information is outside the scope of the present document. ETSI ETSI ES 283 035 V3.1.1 (2015-04) 9 In the context of the present document, an Application Function (AF) represents any network element offering - or providing access to - applications

47、that require information about the characteristics of the IP-connectivity session used to access such applications. Annex A provides background information on the use of a CLF in NGN architectures (ETSI ES 282 001 i.1). g4g38g18g62g38g104g28 g4g272g272g286g400g400g3g69g286g410g449g381g396g364g3g90g2

48、86g400g381g437g396g272g286g400g286g1006g94g272g381g393g286g3g381g296g3g410g346g349g400g3g282g381g272g437g373g286g374g410Figure 1: e2 interface 5 Procedure descriptions 5.1 General The following clauses describe the procedures for supporting interactions between an AF and a CLF. In the tables that de

49、scribe this mapping, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional. A mandatory Information Element (marked as (M) in the table) shall always be present in the command. If this Information Element is absent, an application error occurs at the receiver and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER_MISSING_AVP. This message shall also include a Failed-AVP AVP containing the missing Information Element i.e. the cor