1、 ETSI TS 129 405 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; Nq and Nq Application Protocol (Nq-AP); Stage 3 (3GPP TS 29.405 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 129 405 V14.0.0 (2017-04)13GPP TS 29.405 version 14.0.0 Release 14Reference RTS/T
2、SGC-0429405ve00 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 lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present d
3、ocument 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 document shall not be modified without the prior written authorization of ETSI. In
4、 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 within ETSI Secretariat. Users of the present document should be aware that the do
5、cument may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:
6、/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 written permission of ETSI. The content of the PDF version shall not be m
7、odified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benef
8、it of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 405
9、V14.0.0 (2017-04)23GPP TS 29.405 version 14.0.0 Release 14Intellectual 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, a
10、nd 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/). Pursuant to th
11、e 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 document. For
12、eword This Technical Specification (TS) 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 the co
13、rresponding 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“ and “c
14、annot“ 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 TS 129 405 V14.0.0 (2017-04)33GPP TS 29.405 version 14.0.0 Rel
15、ease 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 General Description 7g35 Procedures for Nq-AP 7g35.1 Introduction 7g35.2 IMSI an
16、d APN Information Retrieval Procedure . 7g35.2.1 General 7g35.2.2 IMSI and APN Information Retrieval Procedure Initiation 7g35.2.2.1 Procedures in the RCAF 7g35.2.2.2 Procedures in the MME 8g35.3 APN Information Retrieval Procedure . 8g35.3.1 General 8g35.3.2 APN Information Retrieval Procedure Init
17、iation 8g35.3.2.1 Procedures in the RCAF 8g35.3.2.2 Procedures in the SGSN 9g36 Transport 9g36.1 General . 9g36.2 IP layer . 9g36.3 Transport layer . 9g37 Error Handling 10g37.1 General . 10g37.2 Message too short . 10g37.3 Unknown or unforeseen message type . 10g37.4 Missing mandatory information e
18、lement 10g37.5 Information elements unknown or unforeseen in the message . 10g37.6 Out of sequence information elements . 10g37.7 Repeated information elements 10g37.8 Syntactically incorrect mandatory information element. 11g37.9 Syntactically incorrect optional information elements . 11g37.10 Cond
19、itional information element errors . 11g37.11 Information elements with semantically incorrect contents . 11g37.12 NqAP Message of Invalid Length 11g38 Messages Description . 12g38.1 NqAP-IMSI-APN-INFORMATION-REQUEST Message 12g38.1.1 Message definition 12g38.2 NqAP-IMSI-APN-INFORMATION-RESPONSE Mes
20、sage 12g38.2.1 Message definition 12g38.3 NqAP-APN-INFORMATION-REQUEST Message . 12g38.3.1 Message definition 12g38.4 NqAP-APN-INFORMATION-RESPONSE Message . 13g38.4.1 Message definition 13g39 Information Elements . 13g39.1 Overview 13g39.1.1 Presence requirements for Information Elements . 13g3ETSI
21、 ETSI TS 129 405 V14.0.0 (2017-04)43GPP TS 29.405 version 14.0.0 Release 149.1.2 Grouped Information Elements . 14g39.2 Message Type . 14g39.3 Information Element Coding 15g39.3.1 Information Element Types 15g39.3.2 Information Element Format. 15g39.4 Information elements 15g39.4.1 International Mob
22、ile Subscriber Identity (IMSI) 15g39.4.2 Access Point Name (APN) . 16g39.4.3 RAN Entity Identifier . 16g39.4.4 Subscriber-Information . 17g39.4.5 RAN Associated Information . 18g39.4.6 Cause 18g39.4.7 Fully Qualified Domain Name (FQDN) . 19g3Annex A (informative): Change history . 20g3History 21g3ET
23、SI ETSI TS 129 405 V14.0.0 (2017-04)53GPP TS 29.405 version 14.0.0 Release 14Foreword This Technical Specification 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
24、 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 approva
25、l; 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. ETSI ETSI
26、 TS 129 405 V14.0.0 (2017-04)63GPP TS 29.405 version 14.0.0 Release 141 Scope The present document specifies the procedures and the Nq and Nq Application Protocol (Nq-AP) messages used on the Nq/Nq interfaces between the RAN Congestion Awareness Function (RCAF) and the Mobility Management Entity (MM
27、E) or the Serving GPRS Support Node (SGSN). The related stage 2 requirements are specified in 3GPP TS 23.401 2 and 3GPP TS 23.060 3. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either s
28、pecific (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 GSM document), a no
29、n-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 23.401: “General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Networ
30、k (E-UTRAN) access“. 3 3GPP TS 23.060: “General Packet Radio Service (GPRS); Service description; Stage 2“. 4 3GPP TS 29.303: “Domain Name System Procedures; Stage 3“ 5 3GPP TS 23.003: “Numbering, addressing and identification“. 6 IETF RFC 791 (September 1981): “Internet Protocol“. 7 IETF RFC 2460 (
31、December 1998): “Internet Protocol, Version 6 (IPv6) Specification“. 8 IETF RFC 4960 (September 2007): “Stream Control Transmission Protocol“. 9 ITU-T Recommendation E.212: “The international identification plan for mobile terminals and mobile users“. 10 3GPP TS 36.413: “Evolved Universal Terrestria
32、l Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)“. 11 IETF RFC 1035: “Domain Names - Implementation and Specification“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following
33、apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. ETSI ETSI TS 129 405 V14.0.0 (2017-04)73GPP TS 29.405 version 14.0.0 Release 143.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905
34、 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. RCAF RAN Congestion Awareness Function 4 General Description This document describes the procedures, messages and information elements ov
35、er the Nq and Nq interfaces between the MME/SGSN and the RCAF to transfer the IMSI/APN information associated to the eNodeB or E-UTRAN cells or UTRAN Service Area experiencing user plane congestion. The Nq interface is located between the RCAF and the MME. The Nq interface is located between the RCA
36、F and the SGSN. Both the Nq and the Nq interfaces use the Nq-AP protocol. The Nq-AP protocol described in this document uses a Type, Length and Value (TLV) encoding of messages over an SCTP transport. The SCTP transport is described in clause 6. The Nq-AP messages and the Information Elements are de
37、scribed in clause 8 and 9 respectively. 5 Procedures for Nq-AP 5.1 Introduction The Nq interface is used between the RCAF and MME for the IMSI and APN information retrieval procedures as specified in sub-clause 5.9.3 of 3GPP TS 23.401 2. The Nq interface is used between the RCAF and SGSN for the APN
38、 information retrieval procedure as specified in sub-clause 6.17 of 3GPP TS 23.060 3. 5.2 IMSI and APN Information Retrieval Procedure 5.2.1 General The IMSI and APN information retrieval procedure is used between the RCAF and the MME over the Nq interface. The RCAF uses this procedure to retrieve f
39、rom the MME: - the IMSIs that are currently in ECM-CONNECTED state and having active E-RABs under a given eNodeB or E-UTRAN cell; - for each IMSI the list of APNs currently having active PDN connections. The RCAF selects the MME(s) serving a user plane congested eNodeB or an E-UTRAN cell through the
40、 DNS procedure as specified in sub-clause 5.4 of 3GPP TS 29.303 4. 5.2.2 IMSI and APN Information Retrieval Procedure Initiation 5.2.2.1 Procedures in the RCAF When the RCAF needs to retrieve the IMSI(s) / APN(s) information for a given user plane congested area, the RCAF shall send the NqAP-IMSI-AP
41、N-INFORMATION-REQUEST message towards the MME(s). The RCAF shall include in the NqAP-IMSI-APN-INFORMATION-REQUEST message: ETSI ETSI TS 129 405 V14.0.0 (2017-04)83GPP TS 29.405 version 14.0.0 Release 14- the Global eNodeB ID IE(s) if it requests the IMSI(s) and APN(s) for a given user plane congeste
42、d area at an eNodeB level; - the ECGI IE(s) if it requests the IMSI(s) and APN(s) for a given user plane congested area at an E-UTRAN cell level. NOTE: For a given user plane congested area, the RCAF retrieves the IMSI and APN information from the MME at a eNodeB level or E-UTRAN cell level based on
43、 local policy at the RCAF. 5.2.2.2 Procedures in the MME When the MME receives the NqAP-IMSI-APN-INFORMATION-REQUEST message from the RCAF, the MME shall report in the NqAP-IMSI-APN-INFORMATION-RESPONSE message, for each eNodeB or E-UTRAN cell requested by the RCAF, that has at least one subscriber:
44、 - the Macro eNodeB ID or Home eNodeB ID or the E-UTRAN cell ID in the RAN Entity value field of the RAN Entity Identifier IE for which the MME(s) report the IMSI and the APN information. - all the subscribers that are currently in ECM-CONNECTED state and having active E-RABs, except the subscribers
45、 involved in an Emergency call, under the given eNodeB or E-UTRAN cell in the Subscriber-Information IE. Multiple instances of the Subscriber-Information IE shall be included if there are multiple subscribers under the given eNodeB or E-UTRAN cell. - for each subscriber, the IMSI in the IMSI IE and
46、APNs currently having active PDN connections in the APN IE. Multiple instances of the APN IE shall be included under a Subscriber-Information IE if the subscriber has active PDN connections towards multiple APNs. The information reported by the MME for each eNodeB or E-UTRAN cell shall be encoded as
47、 an instance of the RAN Associated Information IE. For a single NqAP-IMSI-APN-INFORMATION-REQUEST message from the RCAF, the MME may send multiple NqAP-IMSI-APN-INFORMATION-RESPONSE messages. There shall be no NqAP-IMSI-APN-INFORMATION-RESPONSE sent, if the MME does not find any subscriber under any
48、 of the requested eNodeB or E-UTRAN cell. 5.3 APN Information Retrieval Procedure 5.3.1 General The APN information retrieval procedure is used between the RCAF and the SGSN over the Nq interface. The RCAF uses this procedure to retrieve from the SGSN: - the APNs that are currently having PDP contex
49、ts activated for each IMSI provided by the RCAF. The RCAF selects the SGSN(s) serving a user plane congested SAI through the DNS procedure as specified in sub-clause 5.5 of 3GPP TS 29.303 4. 5.3.2 APN Information Retrieval Procedure Initiation 5.3.2.1 Procedures in the RCAF When the RCAF needs to retrieve the APN(s) for the list of IMSI(s) experiencing RAN user plane congestion, the RCAF shall send the NqAP-APN-INFORMATION-REQUEST message towards the SGSN(s). The RCAF shall include the following information in the NqAP-APN-INF
