1、 ETSI TS 183 066 V2.1.1 (2009-01)Technical Specification Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);Network Attachment Sub-System (NASS);a4 interface based on the DIAMETER protocolETSI ETSI TS 183 066 V2.1.1 (2009-01)2Reference DTS/TISPAN-03189-N
2、GN-R2 Keywords Stage 3, interface 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual co
3、pies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available 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
4、 (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the 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 current sta
5、tus 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: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced exce
6、pt as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registe
7、red for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo ar
8、e Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 183 066 V2.1.1 (2009-01)3Contents Intellectual Property Rights 5g3Foreword . 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 7g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 A
9、bbreviations . 7g34 Overview 8g35 Procedure descriptions . 8g35.1 General . 8g35.1.1 Information elements 8g35.1.2 NASS User profile 9g35.2 Procedures on the a4 interface 10g35.2.1 Access profile push . 10g35.2.1.1 Overview . 10g35.2.1.2 Procedure at the UAAF side 11g35.2.1.3 Procedure at the CLF si
10、de . 11g35.2.2 Access profile pull 12g35.2.2.1 Overview . 12g35.2.2.2 Procedure at the CLF side . 13g35.2.2.3 Procedure at the UAAF side 13g35.2.3 Remove Access Profile . 14g35.2.3.1 Overview. 14g35.2.3.2 Procedure at the UAAF side 14g35.2.3.3 Procedure at the CLF side . 15g36 Use of the Diameter ba
11、se protocol . 15g36.1 Securing Diameter Messages . 15g36.2 Accounting functionality 15g36.3 Use of sessions . 15g36.4 Transport protocol 15g36.5 Routing considerations . 16g36.6 Advertising Application Support 16g37 DIAMETER application. 16g37.1 Commands 16g37.1.1 User-Data-Request command . 17g37.1
12、.2 User-Data-Answer command 17g37.1.3 Push-Notification-Request command . 17g37.1.4 Push-Notification-Answer command 18g37.2 Result-Code AVP values 18g37.2.1 Success 18g37.2.2 Permanent failures 18g37.2.3 Transient failures 19g37.3 AVPs 19g37.3.1 Data-Operation-Indicator 20g37.4 Use of namespaces .
13、20g37.4.1 AVP codes 20g37.4.2 Experimental-Result-Code AVP values 20g37.4.3 Command Code values . 21g37.4.4 Application-ID value 21g3ETSI ETSI TS 183 066 V2.1.1 (2009-01)4Annex A (informative): Mapping of a4 operations and terminology to Diameter . 22g3History 23g3ETSI ETSI TS 183 066 V2.1.1 (2009-0
14、1)5Intellectual 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 found in ETSI SR 000 314: “Intellectual Prope
15、rty 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:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, incl
16、uding 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 Technical Specification (TS) h
17、as been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). ETSI ETSI TS 183 066 V2.1.1 (2009-01)61 Scope The present document defines a protocol applicable to the a4 interface between the User Access Authorization F
18、unction (UAAF) and the Connectivity session Location and repository Function (CLF), based on the Diameter protocol. Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this i
19、s not possible, extensions to Diameter are defined within the present document. 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
20、 may be made only to a complete 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 f
21、ound 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 were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documen
22、ts are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. 1 ETSI ES 282 004: “Telecommunications and Internet converged Service
23、s and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)“. 2 ETSI TS 129 229: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Cx and Dx interfaces based on the Diameter protocol; Pro
24、tocol details (3GPP TS 29.229)“. 3 ETSI TS 129 329: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Sh interface based on the Diameter protocol; Protocol details (3GPP TS 29.329)“. 4 ETSI ES 283 034: “ Telecommunications and Internet converg
25、ed Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol“. 5 ETSI TS 183 020: “ Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment: Roaming in TISPA
26、N NGN Network Accesses; Interface Protocol Definition“. 6 IETF RFC 2960: “Stream Control Transmission Protocol“. 7 IETF RFC 3309: “Stream Control Transmission Protocol (SCTP) Checksum Change“. ETSI ETSI TS 183 066 V2.1.1 (2009-01)78 IETF RFC 3554: “On the Use of Stream Control Transmission Protocol
27、(SCTP) with IPSec“. 9 IETF RFC 3588: “Diameter Base Protocol“. 10 ETSI TS 183 059-1: “Telecommunications and Internet Converged Services and Protocols for Advanced Networks (TISPAN); Network Attachment Sub-System (NASS); a2 interface based on the DIAMETER protocol“. 2.2 Informative references The fo
28、llowing referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. 3 Definitions and abbrev
29、iations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Attribute-Value Pair (AVP): corresponds to an Information Element in a Diameter message NOTE: See definition in RFC 3588 9. NASS User: See definition in ES 282 004 1. 3.2 Abbreviations For th
30、e purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form AVP Attribute-Value Pair CLF Connectivity session Location and repository Function CNGCF Customer Network Gateway Configuration Function DHCP Dynamic Host Configuration Protocol IANA Internet Assig
31、ned Numbers Authority IETF Internet Engineering Task Force IP Internet Protocol IPSec IP SecurityNAS Network Access Server NASS Network Attachment Sub-System P-CSCF Proxy Call Session Control Function PDBF Profile Data Base Function PNA Push-Notification-AnswerPNR Push-Notification-Request PPP Point
32、-to-Point Protocol RACS Resource and Admission Control Subsystem RFC Request For Comments SCTP Stream Control Transport Protocol UAAF User Access Authorization Function UDA User-Data-Answer UDR User-Data-Request ETSI ETSI TS 183 066 V2.1.1 (2009-01)84 Overview The Network Attachment Sub-System (NASS
33、), defined in ES 282 004 1, maintains information about IPconnectivity associated with NASS User connected to TISPAN networks. The document specifies the protocol for the NASS a4 interface between the User Access Authorization Function (UAAF) and the Connectivity session Location and repository Func
34、tion (CLF), based on the Diameter protocol. Figure 4.1: a4 interface The a4 interface allows the CLF to register the association between the NASS User identity and the NASS User preferences regarding the privacy of location information provided by the UAAF. The a4 interface is also used to register
35、NASS User network profile information (QoS profile). The CLF may retrieve the NASS User network profile from the UAAF. The UAAF - CLF relationship may be operated in pull mode or push mode. The push mode is used when the UAAF is involved in the processing of network access requests in order to autho
36、rize or deny access to the network (e.g. when explicit authentication is used). The pull mode is used when implicit authentication is used or in support of CLF recovery procedures. The following information flows are used on the a4 interface: Access Profile Push. Access Profile Pull. Remove Access P
37、rofile. 5 Procedure descriptions 5.1 General 5.1.1 Information elements The following clauses describe the realization of the functional procedures defined in the NASS (ES 282 004 1) using Diameter commands described in clause 7. This involves describing a mapping between the Information Elements de
38、fined in the NASS specification (ES 282 004 1) and Diameter AVPs. Admission applicationsUETE CNG ARF AMFCNGCF NACF UAAF PDBF CLF Service controlsubsystems andResourceControlSubsystem e3e1 e1a1 a3a2 a4e4e2e2e2e5Scope of the present document ETSI ETSI TS 183 066 V2.1.1 (2009-01)9In the tables that des
39、cribe 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 ans
40、wer 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 corresponding Diameter AVP defined by the AVP Code and the other fields set as expect
41、ed for this Information Element. A conditional Information Element (marked as (C) in the table) shall be present in the command if certain conditions are fulfilled: - If the receiver detects that those conditions are fulfilled and the Information Element is absent, an application error occurs and an
42、 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 corresponding Diameter AVP defined by the AVP Code and the other fields set as ex
43、pected for this Information Element. If multiple Information Elements are missing, all corresponding AVP codes shall be included in the Failed-AVP AVP. - If those conditions are not fulfilled, the Information Element shall be absent. If however this Information Element appears in the message, it sha
44、ll not cause an application error and it may be ignored by the receiver if this is not explicitly defined as an error case. Otherwise, an application error occurs at the receiver and an answer message with the Result-Code set to DIAMETER_AVP_NOT_ALLOWED shall be sent back to the originator of the re
45、quest. A Failed-AVP AVP containing a copy of the corresponding Diameter AVP shall be included in this message. An optional Information Element (marked as (O) in the table) may be present or absent in the command, at the discretion of the application at the sending entity. Absence or presence of this
46、 Information Element shall not cause an application error and may be ignored by the receiver. 5.1.2 NASS User profile NASS User profile information sent over the a4 interface comprises QoS profile information and initial gate setting information. Each of these pieces of information may be sent in th
47、e form of an identifier using the QoS-Profile-ID and Initial-Gate-Setting-ID AVPs or in the form of an explicit description using the QoS-Profile-Description and Initial-Gate-Setting-Description AVPs. Tables 5.1 and 5.2 detail the information elements involved in the second case as defined in the NA
48、SS specification ES 282 004 1 and their mapping to DIAMETER AVPs. Table 5.1: Initial gate setting description Information element name Mapping to Diameter AVP Cat. Description List of allowed destinations as well as multicast flows NAS-Filter-Rule O In case of unicast data, the list of default desti
49、nation IP addresses, ports, prefixes and port ranges to which traffic can be sent. In case of multicast, the list of IP-Multicast group addresses and/or the list of (Source IP address, IP-Multicast group address) pairs which traffic can be received from by the attached NASS User. List of denied destinations as well as multicast flows NAS-Filter-Rule O In case of unicast, the list of default destination IP addresses, ports, prefixes and port ranges to which traffic is denied. In case of multicast, the list of IP-Multicast group a
