1、 ETSI ES 283 034 V2.2.0 (2008-07)ETSI Standard Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);Network Attachment Sub-System (NASS);e4 interface based on the DIAMETER protocolETSI ETSI ES 283 034 V2.2.0 (2008-07) 2 Reference RES/TISPAN-03139-NGN-R2 Ke
2、ywords interface, network, system 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 2008. 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. ETSI ETSI ES 283 034 V2.2.0 (2008-07) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 2.1 Normative references .6 2.2 Inf
8、ormative references7 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4 Overview 8 5 Procedure descriptions .9 5.1 General .9 5.1.1 Information elements 9 5.1.2 NASS User profile9 5.2 Procedures on the CLF - A-RACF interface 10 5.2.1 Access profile push.10 5.2.1.1 Overview.10
9、5.2.1.2 Procedure at the CLF side .11 5.2.1.3 Procedure at the A-RACF side11 5.2.2 Access Profile Pull12 5.2.2.1 Overview.12 5.2.2.2 Procedure at the A-RACF side13 5.2.2.3 Procedure at the CLF side .13 5.2.3 IP connectivity release indication .14 5.2.3.1 Overview.14 5.2.3.2 Procedure at the CLF side
10、 .14 5.2.3.3 Procedure at the A-RACF side15 6 Use of the Diameter base protocol .15 6.1 Securing Diameter messages15 6.2 Accounting functionality15 6.3 Use of sessions .15 6.4 Transport protocol 15 6.5 Routing considerations .16 6.6 Advertising application support .16 7 DIAMETER application.16 7.1 C
11、ommands16 7.1.1 User-Data-Request command .17 7.1.2 User-Data-Answer command17 7.1.3 Push-Notification-Request command .18 7.1.4 Push-Notification-Answer command18 7.2 Result-Code AVP values18 7.2.1 Success19 7.2.2 Permanent failures 19 7.2.3 Transient failures 19 7.3 AVPs 19 7.3.1 Globally-Unique-A
12、ddress AVP21 7.3.2 Address-Realm AVP.21 7.3.3 Logical-Access-ID AVP .21 7.3.4 Initial-Gate-Setting-Description AVP.21 7.3.5 QoS-Profile-Description AVP 21 7.3.6 IP-Connectivity-Status AVP.22 7.3.7 Access-Network-Type AVP .22 ETSI ETSI ES 283 034 V2.2.0 (2008-07) 4 7.3.8 Aggregation-Network-Type AVP.
13、22 7.3.9 Maximum-Allowed-Bandwidth-UL AVP 22 7.3.10 Maximum-Allowed-Bandwidth-DL AVP 22 7.3.11 Reservation-Priority22 7.3.12 Transport-Class.23 7.3.13 Application-Class-ID23 7.3.14 Physical-Access-ID.23 7.3.15 NAS-Port-Type AVP23 7.3.16 NAS-Filter-Rule AVP.23 7.3.17 Framed-IP-Address AVP24 7.3.18 Fr
14、amed-IP-Prefix AVP .24 7.3.19 Origin-Host AVP 24 7.3.20 AF-Application-Identifier AVP24 7.3.21 Media-Type AVP24 7.3.22 Initial-Gate-Setting-ID AVP.24 7.3.23 QoS-Profile-ID AVP.24 7.4 Use of namespaces .24 7.4.1 AVP codes 24 7.4.2 Experimental-Result-Code AVP values24 7.4.3 Command Code values .24 7.
15、4.4 Application-ID value 25 Annex A (informative): Mapping of e4 operations and terminology to Diameter26 History 27 ETSI ETSI ES 283 034 V2.2.0 (2008-07) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pe
16、rtaining 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 Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secr
17、etariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). 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 (o
18、r the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). ETSI ETSI ES
19、 283 034 V2.2.0 (2008-07) 6 1 Scope The present document defines a protocol for use between the TISPAN NGN Network Attachment Sub-System (NASS) and the Resource and Admission Control Subsystem (RACS), based on Diameter. The present document is applicable to the e4 interface between the Connectivity
20、Session Location and Repository Function (CLF) and the RACS. 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 is not possible, extensions to Diameter are defined with
21、in 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 may be made only to a complete document or a part ther
22、eof 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 found to be publicly available in the expected location
23、might be found at http:/docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference shoul
24、d, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this cla
25、use were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the
26、latest edition of the referenced document (including any amendments) applies. 1 ETSI ES 282 004: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)“. 2 ETSI ES 282 003: “Telecommunicati
27、ons and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS); Functional Architecture“. 3 ETSI TS 129 229: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Cx and Dx inte
28、rfaces based on the Diameter protocol; Protocol details (3GPP TS 29.229)“. 4 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)“. ETSI ETSI ES 283 0
29、34 V2.2.0 (2008-07) 7 5 ETSI TS 129 209: “Universal Mobile Telecommunications System (UMTS); Policy control over Gq interface (3GPP TS 29.209)“. 6 IETF RFC 2960: “Stream Control Transmission Protocol“. 7 IETF RFC 3588: “Diameter base protocol“. 8 IETF RFC 3309: “Stream Control Transmission Protocol
30、(SCTP) Checksum Change“. 9 IETF RFC 4005: “Diameter Network Access Server application“. 10 IETF RFC 3554: “On the use of Stream Control Transmission Protocol (SCTP) with IPsec“. 11 IETF RFC 3046: “DHCP Relay Agent Information Option“. 12 ETSI TS 183 017: “Telecommunications and Internet Converged Se
31、rvices and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for session based policy set up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification“. 2.2 Informative references The
32、 following 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 abb
33、reviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Application Function (AF): element of the service layer architecture offering applications that require information about the characteristics of the IP-connectivity session used to access
34、such applications Attribute-Value Pair (AVP): corresponds to an information element in a Diameter message NOTE: See RFC 3588 7. NASS User: See definition in 1. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form AF Applicatio
35、n Function A-RACF Access-Resource and Admission Control Function ATM Asynchronous Transfer Mode AVP Attribute-Value Pair CLF Connectivity session Location and repository Function DHCP Dynamic Host Configuration Protocol FQDN Fully Qualified Domain Name IANA Internet Assigned Numbers Authority ID IDe
36、ntifier IETF Internet Engineering Task Force IPSec IP Security NAS Network Access Server ETSI ETSI ES 283 034 V2.2.0 (2008-07) 8 NASS Network Attachment Sub-System PDBF Profile Data Base Function PNA Push-Notification-Answer PNR Push-Notification-Request QoS Quality of Service RACF Resource and Admi
37、ssion Control Function RACS Resource and Admission Control Subsystem RCEF Resource Control Enforcement Function RFC Request For Comments SCTP Stream Control Transport Protocol SPDF Service-based Policy Decision Function UAAF User Authentication and Authorization Function UDA User-Data-Answer UDR Use
38、r-Data-Request VC Virtual Channel VP Virtual Path4 Overview The Network Attachment Sub-System (NASS), defined in ES 282 004 1, maintains information about IP-connectivity associated with uNASS Users connected to TISPAN networks. This information is stored in the Connectivity session Location and rep
39、ository Function (CLF) and made accessible to other subsystems and applications through the following two interfaces (see figure 1): The e2 interface enables Application Functions (AF) to retrieve IP-connectivity related session data. The e4 interface enables the IP-connectivity related session data
40、 to be exchanged between the NASS and the Resource and Admission Control Subsystem (RACS) defined in ES 282 003 2. The present document specifies the protocol for the e4 interface. NASSCLFA-RACFRACSService Control Subsystems and ApplicationsAFTransfer Functionse2e4Scope of the present document Figur
41、e 1: NASS external interfaces ETSI ETSI ES 283 034 V2.2.0 (2008-07) 9 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 and RACS specifications (ES 282 003 2) using Diameter c
42、ommands described in clause 7. This involves describing a mapping between the information elements defined in the NASS specification (ES 282 004 1) and Diameter AVPs. In the tables that describe this mapping, each information element is marked as (M) Mandatory, (C) Conditional or (O) Optional: A man
43、datory information element (marked as (M) in tables 1 to 8) 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_MISSIN
44、G_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 expected for this information element. A conditional information element (marked as (C) in tables 1 to 8) shall b
45、e 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 answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETE
46、R_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 expected for this information element. If multiple information elements are missing, all corresponding AV
47、P 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 shall not cause an application error and it may be ignored by the receiver if this is not explicitly defin
48、ed 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 request. A Failed-AVP AVP containing a copy of the corresponding Diameter AVP shall be included in this m
49、essage. An optional information element (marked as (O) in tables 1 to 8) may be present or absent in the command, at the discretion of the application at the sending entity. Absence or presence of this 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 e4 interface comprises QoS profile information and initial gate setting information. Each of these pieces of information may be sent in the form of an identifier using t
