1、 ETSI TS 1Universal Mobile TelDomain Na(3GPP TS 29.3TECHNICAL SPECIFICATION129 303 V13.3.0 (2016elecommunications System (LTE; Name System Procedures; Stage 3 .303 version 13.3.0 Release 1316-04) (UMTS); 13) ETSI ETSI TS 129 303 V13.3.0 (2016-04)13GPP TS 29.303 version 13.3.0 Release 13Reference RTS
2、/TSGC-0429303vd30 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
3、 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 document shall not be modified without the prior written authorization of ETSI.
4、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 within ETSI Secretariat. Users of the present document should be aware that the
5、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 document, please send your comment to one of the following services: https:/portal.
6、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 modified
7、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, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of it
8、s 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 ETSI TS 129 303 V13.3.0 (2016-04)23GPP TS 29.303 version 13.3.0 Release 13Intell
9、ectual 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 Property Right
10、s (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 the ETSI IPR Policy, no investigation, including IPR searches, has
11、 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) has been produced by ETS
12、I 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 corresponding ETSI deliverables. The cross reference between GSM,
13、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 “cannot“ are to be interpreted as described in clause 3.2 of the E
14、TSI 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 303 V13.3.0 (2016-04)33GPP TS 29.303 version 13.3.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Mo
15、dal verbs terminology 2g3Foreword . 6g31 Scope 7g32 References 7g33 Definitions, symbols and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 General DNS Based Node Selection Description 9g34.1 Resource Records . 9g34.1.1 A and AAAA 9g34.1.2 NAPTR . 9g34.1.3 SRV 9g34.2 Selecting Domain
16、 Names . 10g34.3 Identifying Nodes, Services and Protocols . 10g34.3.1 IETF RFC 3958 Service and Protocol service names for 3GPP . 10g34.3.2 Identification of canonical node names 10g34.3.3 Services from node names or other FQDN identifying a service 11g34.3.3.1 General 11g34.3.3.2 Procedure 12g34.3
17、.3.2.1 S-NAPTR Procedure - General . 12g34.3.3.2.2 S-NAPTR Procedure for a canonical node name 12g34.3.3.3 Services of a PGW from PGW node name (or collocated PGW/GGSN) . 12g34.3.3.4 Services of a MME from MME node name (or GUTI) . 14g34.3.3.5 Services of an SGSN from a P-TMSI . 15g34.3.3.6 Services
18、 of an SGW from SGW canonical node name . 16g34.3.3.7 Services of an MSC Server from MSC Server canonical node name . 17g34A SGW/PGW selection using GTP-C load control 17g34A.1 General . 17g34A.2 Node-level load control 17g34A.3 APN-level load control . 18g35 Procedures for EPC Node Discovery and Se
19、lection . 19g35.1 Procedures for Discovering and Selecting a PGW . 19g35.1.1 Discovering a PGW for a 3GPP Access . 19g35.1.1.1 General 19g35.1.1.2 Discovering a PGW or collocated PGW/GGSN for a 3GPP Access - S8/Gp roaming case existing PDN . 20g35.1.1.3 Discovering a PGW or collocated PGW/GGSN for a
20、 3GPP Access - S5/Gn intra-operator existing PDN . 21g35.1.1.4 Discovering a PGW, collocated PGW/GGSN or GGSN for a 3GPP Access - S5/Gn intra-operator initial attach. 23g35.1.2 Discovering a PGW for a non-3GPP Access with Network Based Mobility Management 23g35.1.2.1 Discovering a PGW for a non-3GPP
21、 Access S2a/S2b initial attach for roaming and non-roaming . 23g35.1.2.2 Discovering a PGW for a non-3GPP Access S2a/S2b initial attach and chained PMIP-based S8-S2a/S2b 23g35.1.3 Discovering a PGW for a non-3GPP Access with DSMIPv6 . 24g35.1.3.1 Discovering a PGW for a non-3GPP Access S2c initial a
22、ttach 24g35.2 Procedures for Discovering and Selecting a SGW . 24g35.2.1 General 24g3ETSI ETSI TS 129 303 V13.3.0 (2016-04)43GPP TS 29.303 version 13.3.0 Release 135.2.2 SGW Selection during TAU or RAU with SGW change - 3GPP roaming case . 25g35.2.3 SGW Selection during TAU or RAU with SGW change -
23、non-roaming case 26g35.2.4 SGW Selection during non-3GPP handover to 3GPP access . 27g35.3 Procedures for Discovering and Selecting a PGW and SGW 27g35.4 Procedures for Discovering and Selecting an MME 28g35.5 Procedures for Discovering and Selecting an SGSN 29g35.5.1 General 29g35.5.2 SGSN initial
24、target selection based on RAI (UTRAN target/GERAN Iu mode target/GERAN Gb mode target) 30g35.5.3 SGSN initial target selection based on RNC-ID (UTRAN target/GERAN Iu mode target) . 31g35.5.4 Void 33g35.6 GW Selection for SIPTO 33g35.6.1 SIPTO above RAN . 33g35.6.2 SIPTO at the local network with LGW
25、 collocated with the (H)(e)NB . 33g35.6.3 SIPTO at the local network with stand-alone GW (LGW collocated with SGW) 33g35.6.4 SIPTO for eHRPD 33g35.7 Procedures for Discovering and Selecting an MSC Server 34g35.7.1 General 34g35.7.2 Selection of the MSC server enhanced for SRVCC based on target RAI (
26、UTRAN / GERAN Iu 2 presented to TSG for approval; 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 ha
27、ve been incorporated in the document. ETSI ETSI TS 129 303 V13.3.0 (2016-04)73GPP TS 29.303 version 13.3.0 Release 131 Scope The present document describes Domain Name System (DNS) Procedures for the Evolved Packet System. This document covers the Evolved Packet Core gateway node selection using DNS
28、 (e.g. SGW and PGW nodes) excluding all User Equipment (UE) initiated DNS-based discovery and selection procedures. The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. 2
29、 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent
30、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 non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905:
31、 “Vocabulary for 3GPP Specifications“. 2 IETF RFC 1034:“DOMAIN NAMES - CONCEPTS AND FACILITIES“. 3 IETF RFC 1035:“DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION“. 4 3GPP TS 23.003: “Numbering, addressing and identification“. 5 GSMA PRD IR.67: “DNS Guidelines for Operators“ Version 2.1.0. 6 IETF RFC
32、 3596: “DNS Extensions to Support IP Version 6“. 7 IETF RFC 3403: “ Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database“. 8 IETF RFC 2782: “A DNS RR for specifying the location of services (DNS SRV)“. 9 IETF RFC 3958: “Domain-Based Application Service Locatio
33、n Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)“. 10 IETF RFC 3401: “Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS“. 11 3GPP TS 23.401: “GPRS enhancements for E-UTRAN access “. 12 3GPP TS 25.413: “UTRAN Iu interface RANAP signalling“. 13 IETF RFC 267
34、1: “Extension Mechanisms for DNS (EDNS0)“. 14 IETF RFC 3402: “Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm“. 15 IETF RFC 2308: “Negative Caching of DNS Queries (DNS NCACHE)“. 16 IETF RFC 3330: “Special Use IPv4 Addresses“. 17 IETF RFC 3849: “IPv6 Address Prefix Reserved for Doc
35、umentation“. 18 3GPP TS 23.060: “General Packet Radio Service (GPRS); Service Description; Stage 2“. ETSI ETSI TS 129 303 V13.3.0 (2016-04)83GPP TS 29.303 version 13.3.0 Release 1319 3GPP TS 36.413: “Evolved Universal Terrestrial Access Network (E-UTRAN); S1 Application Protocol (S1AP)“. 20 3GPP TS
36、23.216: “Single Radio Voice Call Continuity (SRVCC)“. 21 3GPP TS 36.413: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)“. 22 3GPP TS 36.300: “ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-
37、UTRAN); Overall description; Stage 2“. 23 3GPP TS 29.274: “3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3“. 24 3GPP2 X.S0057-B: “E-UTRAN - eHRPD Connectivity and Interworking: Core Network Aspects“. 25 3GPP TS 23
38、.402: “Architecture enhancements for non-3GPP accesses“. 3 Definitions, symbols and abbreviations 3.1 Definitions For 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 de
39、finition of the same term, if any, in 3GPP TR 21.905 1. Domain Name System as defined in IETF RFC 1034 2, IETF RFC 10353, and as used in 3GPP in 3GPP TS 23.003 4 and GSMA PRD IR.67 5 The phrase “operators shall provision“ in this document is intended to convey what is required to provision in DNS to
40、 provide DNS based selection for the corresponding function documented here. If there is a non-DNS procedure in an operators network for that function then there is no functional requirement for the operator to provision such DNS records. The term “S4-SGSN“ refers to a Release-8 SGSN that has at lea
41、st one set of S4/S3/S16 interfaces enabled. The term “Release 8 SGSN supporting only Gn/Gp“ refers to a Release 8 or later SGSN that either explicitly does not support S4 interfaces or all S4/S3/S16 interfaces are disabled due to operator policy. Such a node cannot use an SGW but can use a collocate
42、d PGW/GGSN. See 3GPP TS 23.401 11 Annex D for use cases. The term “Release-8 SGSN“ applies to either case. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.9051 and the following apply. An abbreviation defined in the present document takes precedence
43、over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. DCN Dedicated Core Network DDDS Dynamic Delegation Discovery Service DNS Domain Name System ECGI E-UTRAN Cell Global Identification eHRPD evolved High Rate Packet Data FQDN Fully Qualified Domain Name GUTI Globally Unique Tem
44、porary Identity HSGW eHRPD Serving Gateway LGW Local Gateway LIPA Local IP Access PGW PDN GatewayETSI ETSI TS 129 303 V13.3.0 (2016-04)93GPP TS 29.303 version 13.3.0 Release 13RAI Routing Area Identity SGW Serving Gateway SIPTO Selected IP Traffic Offload TAI Tracking Area Identity TAU Tracking Area
45、 Update TWAN Trusted WLAN Access Network 4 General DNS Based Node Selection Description 4.1 Resource Records 4.1.1 A and AAAA The A resource record is used to define IPv4 host address corresponding to fully qualified name of the host as defined in IETF RFC 1035 3. The AAAA resource record is used to
46、 define IPv6 host address corresponding to fully qualified name of the host as defined in IETF RFC 3596 6. It should be noted that in DNS A or AAAA record names, in general, represent a host and its “equivalent“ interface. Host names, in general, cannot be used as node names. A node may need to have
47、 more than one host name for the simple reason that it can have multiple interfaces for different purposes. 4.1.2 NAPTR The NAPTR resource record is defined in IETF RFC 3403 7 and is a powerful tool that allows DNS to be used to lookup services for a wide variety of resource names, which are not in
48、domain name syntax. NAPTR would be used by a client program to rewrite a string into a domain name. The rewrite process is controlled by flags that provide information on how to communicate with the host at the domain name that was the result of the rewrite. If DNS returns multiple NAPTR resource re
49、cords those can be prioritized using embedded order and preference values defined by the DNS administrator. The S-NAPTR procedure i.e., the “Straightforward-NAPTR“ procedure, is defined in IETF RFC 3958 9 and describes a Dynamic Delegation Discovery System (DDDS) 10 application procedures on how to resolve a domain name, application service name, and application protocol dynamically to target server and port by using both NAPTR and SRV (see IETF RFC 2782 8) resource records. The S-NA
