C.3 Target ID
23.0033GPPNumbering, addressing and identificationRelease 18TS
This clause describes a possible way to support SRNS relocation.
In UMTS, when SRNS relocation is executed, a target ID which consists of MCC, MNC and RNC ID is used as routeing information to route to the target RNC via the new SGSN. An old SGSN shall resolve a new SGSN IP address by a target ID to send the Forward Relocation Request message to the new SGSN.
It shall be possible to refer to a target ID by a logical name which shall be translated into an SGSN IP address to take into account inter-PLMN handover. The old SGSN transforms the target ID information into a logical name of the form:
rncXXXX.mncYYY.mccZZZ.gprs
X shall be Hex coded digits; Y and Z shall be encoded as single digits (in the range 0-9). If there are less than 4 significant digits in XXXX, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digits coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digit coding. Then, for example, a DNS server is used to translate the logical name to an SGSN IP address.
As an example, the logical name for RNC 1B34, MCC 167 and MNC 92 will be coded in the DNS server as:
rnc1B34.mnc092.mcc167.gprs
Annex D (informative):
Applicability and use of the ".3gppnetwork.org" domain name
There currently exists a private IP network between operators to provide connectivity for user transparent services that utilise protocols that rely on IP. This includes (but is not necessarily limited to) such services as GPRS/PS roaming, WLAN roaming, GPRS/PS inter‑PLMN handover and inter‑MMSC MM delivery. This inter‑PLMN IP backbone network consists of indirect connections using brokers (known as GRXs – GPRS Roaming Exchanges) and direct inter‑PLMN connections (e.g. private wire); it is however not connected to the Internet. More details can be found in GSMA PRD IR.34 [57].
Within this inter‑PLMN IP backbone network, the domain name ".gprs" was originally conceived as the only domain name to be used to enable DNS servers to translate logical names for network nodes to IP addresses (and vice versa). However, after feedback from the Internet Engineering Task Force (IETF) it was identified that use of this domain name has the following drawbacks:
1. Leakage of DNS requests for the ".gprs" top level domain into the public Internet is inevitable at sometime or other, especially as the number of services (and therefore number of nodes) using the inter‑PLMN IP backbone increases. In the worst case scenario of faulty clients, the performance of the Internet’s root DNS servers would be seriously degraded by having to process requests for a top level domain that does not exist.
2. It would be very difficult for network operators to detect if/when DNS requests for the ".gprs" domain were leaked to the public Internet (and therefore the security policies of the inter‑PLMN IP backbone network were breached), because the Internet’s root DNS servers would simply return an error message to the sender of the request only.
To address the above, the IETF recommended using a domain name that is routable in the pubic domain but which requests to it are not actually serviced in the public domain. The domain name ".3gppnetwork.org" was chosen as the new top level domain name to be used (as far as possible) within the inter‑PLMN IP backbone network.
Originally, only the DNS servers connected to the inter‑PLMN IP backbone network were populated with the correct information needed to service requests for all sub‑domains of this domain. However, it was later identified that some new services needed their allocated sub‑domain(s) to be resolvable by the UE and not just inter-PLMN IP network nodes. To address this, additional, higher‑level sub‑domains were created:
– "pub.3gppnetwork.org", which is to be used for domain names that need to be resolvable by UEs (and possibly network nodes too) that are connected to a local area network that is connected to the Internet; and
– "ipxuni.3gppnetwork.org", which is to be used for domain names for UNI interfaces that need to be resolvable by UEs that are connected to a local area network that is not connected to the Internet (e.g. local area networks connected to the inter-PLMN IP network of the IPX).
Therefore, DNS requests for the above domain names can be resolved, while requests for all other sub‑domains of "3gppnetwork.org" can simply be configured to return the usual DNS error for unknown hosts (thereby avoiding potential extra, redundant load on the Internet’s root DNS servers).
The GSM Association is in charge of allocating new sub‑domains of the ".3gppnetwork.org" domain name. The procedure for requesting new sub‑domains can be found in Annex E.
Annex E (normative):
Procedure for sub‑domain allocation
When a 3GPP member company identifies the need for a new sub‑domain name of ".3gppnetwork.org", that 3GPP member company shall propose a CR to this specification at the earliest available meeting of the responsible working group for this TS. The CR shall propose a new sub‑domain name. The new sub‑domain proposed shall be formatted in one of the formats as described in the following table.
|
Sub‑domain Format |
Intended Usage |
|
<service_id>.mnc<MNC>.mcc<MCC>.3gppnetwork.org (see notes 1 and 2) |
Domain name that is to be resolvable by network nodes only. This format inherently adds protection to the identified node, in that attempted DNS resolutions instigated directly from end user equipment will fail indefinitely. |
|
<service_id>.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org (see notes 1 and 2) |
Domain name that is to be resolvable by UEs and/or network nodes. This format inherently adds global resolution capability, but at the expense of confidentiality of network topology. |
|
<service_id>.mnc<MNC>.mcc<MCC>.ipxuni.3gppnetwork.org (see notes 1 and 2) |
Domain name for UNI interface that is to be resolvable by UEs that are connected to an inter-PLMN IP network that has no connectivity to the Internet. This format inherently adds resolution capability for UEs in closed IP networks e.g. IPX. |
|
<service_id>.mcc<MCC>.visited-country.pub.3gppnetwork.org (see notes 1 and 2) |
Domain name in the visited country that is to be resolvable by UEs and/or network nodes, which is not specific to an individual operator. |
|
<service_id>.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org (see notes 1 and 3) |
Domain name of a Stand-alone non-public network that is to be resolvable by network nodes only. This format inherently adds protection to the identified node, in that attempted DNS resolutions instigated directly from end user equipment will fail indefinitely. |
Table E.1: Sub‑domain formats for the "3gppnetwork.org" domain and their respective intended usage
NOTE 1: "<service_ID>" is a chosen label, conformant to DNS naming conventions (usually IETF RFC 1035 [19] and IETF RFC 1123 [20]) that clearly and succinctly describe the service and/or operation that is intended to use this sub‑domain.
NOTE 2: "<MNC>" and "<MCC>" are the MNC (padded to the left with a zero, if only a 2‑digit MNC) and MCC of a PLMN.
NOTE 3: "NID", "<MNC>" and "<MCC>" are the NID (hexadecimal digits as specified in clause 12.7), MNC (padded to the left with a zero, if only a 2‑digit MNC) and MCC identifying a Stand-alone Non-Public Network (SNPN).
Care should be taken when choosing which format a domain name should use. Once a format has been chosen, the responsible working group shall then check the CR and either endorse it or reject it. If the CR is endorsed, then the responsible working group shall send an LS to the GSMA NG with TSG-CT in copy. The LS shall describe the following key points:
– the context
– the service
– intended use
– involved actors
– proposed new sub‑domain name
GSMA NG will then verify the consistence of the proposal and its usage within the domain’s structure and interworking rules (e.g. access to the GRX/IPX Root DNS servers). GSMA NG will then endorse or reject the proposal and inform the responsible working group (in 3GPP) and also TSG CT. It is possible that GSMA NG will also specify, changes to the newly proposed sub‑domain name (e.g. due to requested sub‑domain name already allocated).
NOTE 4: There is no need to request GSMA NG for new labels to the left of an already GSMA NG approved "<service_ID>". It is the responsibility of the responsible working group to ensure uniqueness of such new labels.
It should be noted that services already defined to use the ".gprs" domain name will continue to do so and shall not use the new domain name of ".3gppnetwork.org"; this is to avoid destabilising services that are already live.
Annex F (informative):
Change history
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
|
Apr 1999 |
GSM 03.03 |
Transferred to 3GPP CN1 |
||||||
|
CN#03 |
23.003 |
Approved at CN#03 |
3.0.0 |
|||||
|
CN#04 |
23.003 |
001 |
Definition of escape PLMN code |
3.1.0 |
||||
|
CN#04 |
23.003 |
002r1 |
SSN reallocation for CAP, gsmSCF, SIWF, GGSN, SGSN, |
3.1.0 |
||||
|
CN#04 |
23.003 |
003 |
Correction of VGC/VBC reference |
3.1.0 |
||||
|
CN#04 |
23.003 |
004 |
Harmonisation of the MNC-length; correction of CR A019r1 |
3.1.0 |
||||
|
CN#04 |
23.003 |
005 |
Correction to the MNC length |
3.1.0 |
||||
|
CN#05 |
23.003 |
007r1 |
ASCII coding of <MNC> and <MCC> in APN OI |
3.2.0 |
||||
|
CN#05 |
23.003 |
008 |
New SSN allocation for RANAP and RNSAP |
3.2.0 |
||||
|
CN#06 |
23.003 |
011 |
Support of VLR and HLR Data Restoration procedures with LCS |
3.3.0 |
||||
|
CN#07 |
23.003 |
014 |
Necessity of the function of the calculation of an SGSN IP address from the target ID |
3.4.0 |
||||
|
CN#07 |
23.003 |
016 |
Definition of Service Area Identification |
3.4.0 |
||||
|
CN#07 |
23.003 |
017r2 |
Modification of clause 6.2 to enhance IMEI security |
3.4.0 |
||||
|
CN#07 |
23.003 |
018 |
Coding of a deleted P-TMSI signature |
3.4.0 |
||||
|
CN#07 |
23.003 |
013r2 |
Introduction of Reserved Service Labels in the APN |
3.4.1 |
||||
|
CN#08 |
23.003 |
019 |
Missing UTRAN identifiers |
3.5.0 |
||||
|
CN#08 |
23.003 |
021r1 |
Editorial Modification of clause 6.2.2. |
3.5.0 |
||||
|
CN#08 |
23.003 |
022 |
IMEI Formats and Encoding |
3.5.0 |
||||
|
CN#09 |
23.003 |
023 |
Alignment of 23.003 with text from 25.401 |
3.6.0 |
||||
|
CN#10 |
23.003 |
024 |
Moving informative Annex A from 3G TS 29.060 and making it normative. |
3.7.0 |
||||
|
CN#11 |
23.003 |
025 |
Clarification to Definition of Service Area Identifier |
3.8.0 |
||||
|
CN#11 |
23.003 |
026 |
Forbidden APN network identifier labels |
3.8.0 |
||||
|
CN#11 |
23.003 |
Updated from R99 to Rel-4 after CN#11 |
4.0.0 |
|||||
|
CN#12 |
23.003 |
028r1 |
Remove reference to TS23.022 |
4.1.0 |
||||
|
CN#12 |
23.003 |
029r1 |
New Subsystem Number for the Position Calculation Application Part on the Iupc interface |
5.0.0 |
||||
|
CN#13 |
23.003 |
032 |
Clarification on APN labels that begin with a digit |
5.1.0 |
||||
|
CN#13 |
23.003 |
Editorial clean up |
5.1.0 |
|||||
|
CN#14 |
23.003 |
033 |
Rules for TMSI partitioning |
5.2.0 |
||||
|
CN#14 |
23.003 |
035 |
Introduction of Global CN-ID definition |
5.2.0 |
||||
|
CN#16 |
23.003 |
037r1 |
IuFlex support for determining old SGSN during handover/relocation |
5.3.0 |
||||
|
CN#16 |
23.003 |
038 |
Allocation of unique prefixes to IPv6 terminals |
5.3.0 |
||||
|
CN#16 |
23.003 |
041r2 |
Use of a temporary public user identity |
5.3.0 |
||||
|
CN#16 |
23.003 |
044 |
Restructuring the IMEI to combine the TAC and FAC |
5.3.0 |
||||
|
CN#16 |
23.003 |
045 |
Use of the TLLI codespace in GERAN Iu mode |
5.3.0 |
||||
|
CN#17 |
23.003 |
048r3 |
Clarification on the definition of DNS |
5.4.0 |
||||
|
CN#17 |
23.003 |
050r1 |
Support for Shared Network in connected mode: definition of SNA |
5.4.0 |
||||
|
CN#17 |
23.003 |
053r1 |
Restructuring the IMEI to combine the TAC and FAC in Annex B |
5.4.0 |
||||
|
CN#17 |
23.003 |
054 |
SCCP sub-system Number for IM-SSF |
5.4.0 |
||||
|
CN#18 |
23.003 |
055r1 |
Iur‑g Introduction |
5.5.0 |
||||
|
CN#18 |
23.003 |
056r2 |
Editorial clean‑up |
5.5.0 |
||||
|
CN#18 |
23.003 |
057 |
Correction of the private user identity’s form |
5.5.0 |
||||
|
CN#18 |
23.003 |
058 |
Addition of a reference to the ITU-T RECOMMENDATION E.212 for Mobile Country Codes |
5.5.0 |
||||
|
CN#18 |
23.003 |
059 |
Correction to the form of public user identity |
5.5.0 |
||||
|
CN#18 |
23.003 |
062 |
Fix miss-interworking for LMSI handling (LMSI definition) |
5.5.0 |
||||
|
CN#18 |
23.003 |
Corrupted figures 13 – 18 fixed |
5.5.1 |
|||||
|
CN#20 |
23.003 |
065 |
Correction to Annex C.3 – Target ID |
5.6.0 |
||||
|
CN#21 |
23.003 |
072 |
Correction to definition of Group-ID, Group call area ID and Group Call Reference |
5.7.0 |
||||
|
CN#21 |
23.003 |
073r2 |
PSI definition |
6.0.0 |
||||
|
CN#22 |
23.003 |
078 |
On the length of the APN NI |
6.1.0 |
||||
|
CN#23 |
23.003 |
081 |
Changes and corrections to DNS names |
6.2.0 |
||||
|
CN#23 |
23.003 |
083r2 |
Changes to enable the GSMA root DNS architecture using ".3gppnetwork.org" TLD |
6.2.0 |
||||
|
CN#23 |
23.003 |
085r1 |
WLAN access parameters moved from TS 24.234 to TS 23.003 |
6.2.0 |
||||
|
CN#23 |
23.003 |
087 |
Assignment of SSN for Presence Network Agent |
6.2.0 |
||||
|
CN#24 |
23.003 |
086r4 |
Clarification of the uses of SIP URIs for Public User ID |
6.3.0 |
||||
|
CN#24 |
23.003 |
088r1 |
Addition of TMGI |
6.3.0 |
||||
|
CN#25 |
23.003 |
089 |
Background of and procedures for the ".3gppnetwork.org" domain name |
6.4.0 |
||||
|
CN#25 |
23.003 |
090r2 |
Decorated NAI format |
6.4.0 |
||||
|
CN#25 |
23.003 |
091r1 |
Introduction of temporary identities |
6.4.0 |
||||
|
CN#26 |
23.003 |
092r2 |
‘otherrealm’ format of Decorated NAI |
6.5.0 |
||||
|
CN#26 |
23.003 |
095r1 |
Clarification of NRI position within (P)-TMSI |
6.5.0 |
||||
|
CN#26 |
23.003 |
096r1 |
BSF address |
6.5.0 |
||||
|
CN#27 |
23.003 |
097 |
Clarification of the TMGI |
6.6.0 |
||||
|
CN#27 |
23.003 |
093r3 |
Definition of Alternative NAI |
6.6.0 |
||||
|
CT#28 |
23.003 |
0099r4 |
W-APN Definition |
6.7.0 |
||||
|
CT#28 |
23.003 |
0100r5 |
Correction to wildcards in PSI |
6.7.0 |
||||
|
2005-07: Correct line break before clause 14 header |
6.7.1 |
|||||||
|
CT#29 |
23.003 |
0102r2 |
Corrections to "3gppnetwork.org" addressing |
6.8.0 |
||||
|
CT#29 |
23.003 |
0103 |
Addition of addressing for the Generic Access Network |
6.8.0 |
||||
|
CT#29 |
23.003 |
0104r1 |
PSI routing |
6.8.0 |
||||
|
CT#31 |
23.003 |
0106r1 |
IETF references update |
6.9.0 |
||||
|
CT#32 |
23.003 |
0107r1 |
Fast re-authentication identity clarification |
6.10.0 |
||||
|
CT#32 |
23.003 |
0109r1 |
Case insensitive naming convention |
6.10.0 |
||||
|
0111r1 |
Correction to the W-APN definition |
|||||||
|
CT#32 |
23.003 |
0112r1 |
Definition of Anonymous URI in IMS |
7.0.0 |
||||
|
CT#33 |
23.003 |
0117r1 |
Re-authentication identity definition correction |
7.1.0 |
||||
|
0115r3 |
Definition of MBMS SAI |
|||||||
|
CT#34 |
23.003 |
0118 |
Voice Call Continuity Identification and Addressing |
7.2.0 |
||||
|
0119r2 |
Unavailable User Identity |
|||||||
|
0120 |
Emergency Realm for I-WLAN network advertisment |
|||||||
|
0121 |
Definition of emergency W-APN |
|||||||
|
0122r2 |
Format of emergency public identity |
|||||||
|
CT#35 |
23.003 |
0128r2 |
Definition of Private Service identity |
7.3.0 |
||||
|
0126r2 |
Definition of emergency APN for IMS em-calls |
|||||||
|
0129r2 |
Clarification to TMGI definition |
|||||||
|
CT#36 |
23.003 |
0131r2 |
Correction of derivation of identifiers, by the UE, using the IMSI |
7.4.0 |
||||
|
CT#37 |
23.003 |
0134r1 |
Home realm construction for MBMS roaming |
7.5.0 |
||||
|
0135r2 |
PSI clarification |
|||||||
|
0136 |
Remove emergency APN |
|||||||
|
CT#38 |
23.003 |
0138 |
Correction to text describing W-APN format |
7.6.0 |
||||
|
CT#39 |
23.003 |
0141r1 |
Structure of TMGI |
7.7.0 |
||||
|
CT#39 |
23.003 |
0140 |
Wildcarded Public User Identities format |
8.0.0 |
||||
|
CT#40 |
23.003 |
0142r2 |
IMS public and private identity derivation in 3GPP2 |
8.1.0 |
||||
|
0144 |
Minor corrections to the IMS clause |
|||||||
|
0146r2 |
NAI for 3GPP access to Non-3GPP Access Interworking |
|||||||
|
0143r2 |
Addition of IMS Centralized Services related identities |
|||||||
|
CT#41 |
23.003 |
0150 |
Emergency Public User Identity Removal |
8.2.0 |
||||
|
0152r3 |
Introduction of IMC in support of common IMS |
|||||||
|
0153r1 |
Introduction of STN-SR |
|||||||
|
0154r1 |
Addition and correction of DNS related identifiers for EPC |
|||||||
|
0155r1 |
Definition of Globally Unique Temporary UE Identity |
|||||||
|
0156 |
Reference correction |
|||||||
|
0158r1 |
Addition of Conference Factory URI for IMS Centralized Services |
|||||||
|
0159r1 |
Naming for HA discovery HA-APN |
|||||||
|
0160r2 |
Definition and format of access network identifier |
|||||||
|
CT#42 |
23.003 |
0161 |
SGSN related FQDNs |
8.3.0 |
||||
|
0162 |
New "nodes" subdomain for EPC |
|||||||
|
0165 |
Clarify the mapping between M-TMSI and P-TMSI |
|||||||
|
0166 |
Revising the GUTI Definition |
|||||||
|
0163r4 |
Closed Subscriber Group |
|||||||
|
0167r1 |
Adding the S-TMSI Definition |
|||||||
|
0168r1 |
Definition of instance Id |
|||||||
|
0169 |
STN-SR in SGSN |
|||||||
|
CT#43 |
23.003 |
0170 |
Correction to NAI format |
8.4.0 |
||||
|
0172 |
Missing service identifiers for DNS procedures |
|||||||
|
0174 |
Correction of the GUTI format |
|||||||
|
0176r1 |
Correction of the GUTI P-TMSI mapping |
|||||||
|
0177 |
Corrections to Service Continuity addressing |
|||||||
|
0178r1 |
Support of EAP-AKA’ |
|||||||
|
0179r2 |
Naming for ANDSF discovery |
|||||||
|
0180r1 |
ePDG naming |
|||||||
|
0181r2 |
Clarification about canonical form of IMS Public User Identity when format is TEL URL |
|||||||
|
0182 |
Temporary Identity Tag Values for Fast Re-authentication Ids |
|||||||
|
0187r2 |
DNS-APN-OI |
|||||||
|
CT#44 |
23.003 |
0189r1 |
HNB Name Definition |
8.5.0 |
||||
|
0190r1 |
Clarification on TAI FQDN |
|||||||
|
0191 |
Service Parameters for S2c |
|||||||
|
0193r2 |
Reference update for draft-montemurro-gsma-imei-urn |
|||||||
|
CT#45 |
23.003 |
0194r1 |
Public User Identity definition in TS 23.003 |
8.6.0 |
||||
|
0197r1 |
Inclusion of CSG Type |
|||||||
|
CT#45 |
23.003 |
0199r1 |
IMEI Based NAI definitions for emergency services |
9.0.0 |
||||
|
CT#46 |
23.003 |
0200r1 |
IMEI based NAI |
9.1.0 |
||||
|
0205r4 |
IMEI Based NAI |
|||||||
|
0210r1 |
Reintroducing Emergency APN definition for IMS based Emergency Call |
|||||||
|
0212r1 |
Clarification for the format of ANDSF-SN in roaming scenario |
|||||||
|
0215 |
Tracking Area Code |
|||||||
|
0217 |
E-UTRAN Cell Global Identification definition |
|||||||
|
CT#47 |
23.003 |
0213r4 |
Defining H(e)NB identity |
9.2.0 |
||||
|
0219r2 |
Exclude prepended digit from the NAI in PMIPv6 |
|||||||
|
0221r2 |
APN-FQDN construction |
|||||||
|
0223 |
Corrections to APN structure |
|||||||
|
0225r1 |
Correction on Home Network Realm/Domain |
|||||||
|
0227 |
Corrections to IMS Public Identity |
|||||||
|
CT#48 |
23.003 |
0229r1 |
Removal of the redundancy reference to 23.401 |
9.3.0 |
||||
|
0232r1 |
IMEI and IMEISV |
|||||||
|
0235r1 |
Remove ambiguities and improved definition of HNB Unique Identity |
|||||||
|
0237r2 |
Essential corrections to GUTI mapping |
|||||||
|
CT#49 |
23.003 |
0242r1 |
PSI use for services hosted in an AS |
9.4.0 |
||||
|
0246r3 |
Essential corrections to GUTI mapping |
|||||||
|
0247r2 |
Use of NRI |
|||||||
|
0256 |
Format of the Unavailable User Identity |
|||||||
|
0257 |
Clarification of UE behaviour with regards to LAC format |
|||||||
|
CT#50 |
23.003 |
0252r2 |
Correction of C-MSISDN definition |
9.5.0 |
||||
|
0265 |
Updating IMEI URN draft reference |
|||||||
|
0268r1 |
Determination of type of source node during TAU/RAU |
|||||||
|
CT#50 |
23.003 |
0258r3 |
eNodeB-ID FQDN for DNS procedures |
10.0.0 |
||||
|
0269r1 |
Determination of type of source node during TAU/RAU |
|||||||
|
0259 |
Service Parameter on PGW selection for GTP based S2b |
|||||||
|
CT#51 |
23.003 |
0274r3 |
Relay Node OAM system identification |
10.1.0 |
||||
|
0279r3 |
Correction of C-MSISDN definition |
|||||||
|
0277r1 |
Determination of type of source node during TAU/RAU |
|||||||
|
0285 |
Correction to a reference of an outdated IETF draft to an RFC |
|||||||
|
0280r2 |
Correction to the reserved values for Tracking Area Code (TAC) |
|||||||
|
0286 |
DNS Service Support For Sv |
|||||||
|
0289 |
Clarfication of decoding of NRI |
|||||||
|
CT#52 |
23.003 |
0290 |
Closed Subscriber Group clarification |
10.2.0 |
||||
|
0293r2 |
UE moving from E-UTRAN to GERAN |
|||||||
|
0294r2 |
XCAP Addressing |
|||||||
|
0296r1 |
APN Network Identifier |
|||||||
|
0299 |
Updating IMEI URN draft reference |
|||||||
|
CT#53 |
23.003 |
0307 |
Updating IMEI URN draft reference |
10.3.0 |
||||
|
0282r4 |
Format of Public User Identities and SIP/TEL URI |
|||||||
|
0303r3 |
Emergency NAI for UICC-less Terminal |
|||||||
|
CT#54 |
23.003 |
0316r1 |
Definition of Distinct Public User Identity |
10.4.0 |
||||
|
0309r1 |
Emergency NAI for UICC-less Terminal |
|||||||
|
CT#54 |
23.003 |
0308r2 |
APN Operator Identifier for local breakout |
11.0.0 |
||||
|
0312r2 |
Definition of STI-rSR |
|||||||
|
CT#55 |
23.003 |
0334 |
BSF address correction |
11.1.0 |
||||
|
0322r2 |
Correction to domain name for XCAP Root URI |
|||||||
|
0325 |
Updating IMEI URN draft reference |
|||||||
|
0317r2 |
Clarification of GUTI mapping |
|||||||
|
0318 |
Service Parameter on PGW selection for GTP based S2a |
|||||||
|
CT#56 |
23.003 |
0320r6 |
MTC External Identifier |
11.2.0 |
||||
|
0337r1 |
New Service Parameters for CS to PS SRVCC |
|||||||
|
0319r5 |
Definition of A-MSISDN |
|||||||
|
0335r2 |
MME Number for SMS in MME |
|||||||
|
0311r7 |
SSN Reallocation for CSS and its Number Definition |
|||||||
|
CT#57 |
23.003 |
0338r1 |
External Identifier definition |
11.3.0 |
||||
|
0339r1 |
PS only subscription w/o MSISDN |
|||||||
|
0340r1 |
NCC allocation in a shared network |
|||||||
|
0342r1 |
MSB in the GUTI and P-TMSI mapping |
|||||||
|
0345r2 |
Clarification to MME FQDN |
|||||||
|
CT#58 |
23.003 |
0347 |
Clarification on the use of APN Operator Identifier |
11.4.0 |
||||
|
0348r1 |
PS only subscription without MSISDN |
|||||||
|
0352r1 |
Updating IMEI URN draft reference |
|||||||
|
CT#59 |
23.003 |
0346r5 |
MME FQDN Clarification |
11.5.0 |
||||
|
CT#61 |
23.003 |
0358 |
Updating IMEI URN draft reference |
11.6.0 |
||||
|
0361r1 |
MBMS SAI Definition Correction for LTE Access |
|||||||
|
0363r2 |
NRI and MMEC coordination |
|||||||
|
CT#61 |
23.003 |
0362r2 |
SIPTO permission for Local Network LHN ID definition |
12.0.0 |
||||
|
0364 |
GERAN Iu Mode |
12.0.0 |
||||||
|
CT#62 |
23.003 |
0370 |
Updating IMEI URN draft reference |
12.1.0 |
||||
|
0365r3 |
Multi-Vendor eNB Plug and Play |
12.1.0 |
||||||
|
CT#63 |
23.003 |
0379 |
Updating IMEI URN draft reference |
12.2.0 |
||||
|
0371r2 |
Update of working procedures with GSMA IREG |
12.2.0 |
||||||
|
0372r1 |
TWAN Operator Name |
12.2.0 |
||||||
|
CT#64 |
23.003 |
0381r4 |
Addition of ProSe Application ID format |
12.3.0 |
||||
|
0382r5 |
Addition of ProSe Application Code format |
12.3.0 |
||||||
|
0383r1 |
Correct definition of Decorated NAI for Evolved Packet Core (EPC) |
12.3.0 |
||||||
|
0384r1 |
Definition of Alternative NAI for Evolved Packet Core (EPC) |
12.3.0 |
||||||
|
0386r6 |
Conference Factory URI for IMS |
12.3.0 |
||||||
|
07-2014 |
23.003 |
Clause 19.3.7 title corrected |
12.3.1 |
|||||
|
CT#65 |
23.003 |
0391 |
Updating IMEI URN draft reference to RFC 7254 |
12.4.0 |
||||
|
0392r2 |
Identification of the HSS |
12.4.0 |
||||||
|
0393r2 |
Update of ProSe Application Code format |
12.4.0 |
||||||
|
0394 |
IMSI based Decorated NAI |
12.4.0 |
||||||
|
10-2014 |
23.003 |
Clause number 10.2.2 added. |
12.4.1 |
|||||
|
CT#66 |
23.003 |
0398r1 |
Clarification of NAI handling |
12.5.0 |
||||
|
0399r2 |
Maintenance of I-WLAN requirements |
12.5.0 |
||||||
|
0402 |
Addressing and Identifications for Bootstrapping MBMS Service Announcement |
12.5.0 |
||||||
|
0401r1 |
Definiton for EPC Prose User ID |
12.5.0 |
||||||
|
0403r1 |
Prose Application ID Name description |
12.5.0 |
||||||
|
CT#66 |
23.003 |
0396r3 |
Defining app protocol name for Nq and Nq’ |
13.0.0 |
||||
|
CT#67 |
23.003 |
0409r2 |
Extension of decorated NAI |
13.1.0 |
||||
|
0414 |
Definition of Vendor ID |
13.1.0 |
||||||
|
0413r2 |
Clarification in the definition of the ProSe Application Code |
13.1.0 |
||||||
|
CT#68 |
23.003 |
0412r6 |
Clarification of Root NAI and Decorated NAI |
13.2.0 |
||||
|
0416r1 |
Correction of examples for the Fast-Reauth NAI |
13.2.0 |
||||||
|
0417r1 |
Domain name starting by a digit |
13.2.0 |
||||||
|
CT#69 |
23.003 |
0420 |
Removal of Editor’s Note about ProSe Application Code Length |
13.3.0 |
||||
|
0418r3 |
Definition of IMSI-Group Identifier |
13.3.0 |
||||||
|
0421r1 |
FQDN format for ProSe Function |
13.3.0 |
||||||
|
CT#70 |
23.003 |
0423r2 |
FQDN for ePDG selection for emergency bearer services |
13.4.0 |
||||
|
0424r1 |
FQDN for ePDG selection (for non-emergency bearer services) |
13.4.0 |
||||||
|
0431r4 |
Introduce home network domain name for OCS |
13.4.0 |
||||||
|
0426r2 |
ProSe Application code and Metadata index |
13.4.0 |
||||||
|
0427r1 |
ProSe identifiers for restricted ProSe direct discovery |
13.4.0 |
||||||
|
0433r1 |
ProSe identifiers used in direct discovery for public safety |
13.4.0 |
||||||
|
0429r1 |
Presence Reporting Area Identifier |
13.4.0 |
||||||
|
0432r2 |
Enhancement of service parameters to support Decor |
13.4.0 |
||||||
|
CT#71 |
23.003 |
0434r1 |
Addition of ProSe Application Code Prefix and ProSe Application Code Suffix formats |
13.5.0 |
||||
|
0437r1 |
ePDG selection with DNS-based Discovery of Regulatory Requirements |
13.5.0 |
||||||
|
0438r1 |
Clarification of TAC Allocation |
13.5.0 |
||||||
|
2016-06 |
CT#72 |
CP-160237 |
0441 |
1 |
Replacement field used in DNS-based Discovery of regulatory requirements |
13.6.0 |
||
|
2016-06 |
CT#72 |
CP-160237 |
0441 |
1 |
Replacement field used in DNS-based Discovery of regulatory requirements |
13.6.0 |
||
|
2016-06 |
CT#72 |
CP-160219 |
0439 |
3 |
Clarification on the construction of the private user identity |
14.0.0 |
||
|
2016-09 |
CT#73 |
CP-160425 |
0443 |
1 |
Domain Name for MCPTT confidentiality protection |
14.1.0 |
||
|
2016-09 |
CT#73 |
CP-160417 |
0445 |
– |
Update of definition of BSIC to include Radio frequency Colour Code |
14.1.0 |
||
|
2016-12 |
CT#74 |
CP-160679 |
0448 |
1 |
FQDNs for ePDG selection for Emergency services |
14.2.0 |
||
|
2016-12 |
CT#74 |
CP-160679 |
0449 |
1 |
NAI for Emergency services for UEs without IMSI or with unauthenticated IMSI |
14.2.0 |
||
|
2016-12 |
CT#74 |
CP-160672 |
0456 |
1 |
Unknown User Identity |
14.2.0 |
||
|
2016-12 |
CT#74 |
CP-160666 |
0458 |
1 |
IMSI-Group-Id |
14.2.0 |
||
|
2016-12 |
CT#74 |
CP-160781 |
0459 |
3 |
KeyName-NAI format |
14.2.0 |
||
|
2017-03 |
CT#75 |
CP-170042 |
0447 |
4 |
DCN Identifier |
14.3.0 |
||
|
2017-03 |
CT#75 |
CP-170045 |
0460 |
– |
Mission Critical Services |
14.3.0 |
||
|
2017-06 |
CT#76 |
CP-171016 |
0464 |
1 |
Add an explicit reference to TS33.234 and TS24.234 |
14.4.0 |
||
|
2017-06 |
CT#76 |
CP-171033 |
0465 |
2 |
FQDN for DNS Query of Local Emergency Numbers |
14.4.0 |
||
|
2017-06 |
CT#76 |
CP-171033 |
0466 |
1 |
NAI for emergency services over WLAN access to EPC |
14.4.0 |
||
|
2017-06 |
CT#76 |
CP-171032 |
0467 |
1 |
Addition of V2X Control Function FQDN format |
14.4.0 |
||
|
2017-06 |
CT#76 |
CP-171029 |
0470 |
1 |
External Group Identifier |
14.4.0 |
||
|
2017-06 |
CT#76 |
CP-171036 |
0471 |
2 |
Sx Service Parameters |
14.4.0 |
||
|
2017-06 |
CT#76 |
CP-171031 |
0472 |
1 |
Reserved range of TMGI for Receive Only Mode |
14.4.0 |
||
|
2017-06 |
CT#76 |
CP-171040 |
0468 |
1 |
External Identifier on Sh |
15.0.0 |
||
|
2017-09 |
CT#77 |
CP-172015 |
0475 |
– |
PGW selection for WLAN with deployed DCNs |
15.1.0 |
||
|
2017-09 |
CT#77 |
CP-172024 |
0476 |
1 |
WebRTC Web Server Function discovery |
15.1.0 |
||
|
2017-12 |
CT#78 |
CP-173034 |
0479 |
1 |
N3IWF FQDN |
15.2.0 |
||
|
2017-12 |
CT#78 |
CP-173034 |
0480 |
1 |
Definition of 5G-GUTI and mapping between 5G-GUTI and EPS GUTI |
15.2.0 |
||
|
2017-12 |
CT#78 |
CP-173034 |
0485 |
1 |
Introducing the S-NSSAI definition |
15.2.0 |
||
|
2017-12 |
CT#78 |
CP-173036 |
0482 |
1 |
SGW/PGW selection for NR |
15.2.0 |
||
|
2017-12 |
CT#78 |
CP-173022 |
0484 |
2 |
Align emergency number FQDN and Replacement field with procedures in TS 24.302 |
15.2.0 |
||
|
2017-12 |
CT#78 |
CP-173024 |
0486 |
2 |
IMEI based SIP URI for P-Preferred-Identity |
15.2.0 |
||
|
2018-03 |
CT#79 |
CP-180017 |
0488 |
– |
Specifying the length of the sub-label of the Country based Emergency Numbers FQDN |
15.3.0 |
||
|
2018-03 |
CT#79 |
CP-180024 |
0489 |
1 |
Definition of Service ID for WLAN based ProSe Direct Discovery |
15.3.0 |
||
|
2018-03 |
CT#79 |
CP-180022 |
0490 |
2 |
Rename entity that do national allocation/assignment of numbering/addressing/identification resources |
15.3.0 |
||
|
2018-03 |
CT#79 |
CP-180022 |
0491 |
2 |
Correct parts concerning ITU-T Rec. E.212 that is not correct in TS 23.003 |
15.3.0 |
||
|
2018-03 |
CT#79 |
CP-180022 |
0492 |
2 |
Change terminology from ISDN number/ISDN numbering plan to E.164 number and E.164 numbering plan and adjust abbreviation of MSISDN |
15.3.0 |
||
|
2018-03 |
CT#79 |
CP-180026 |
0494 |
1 |
Definition of NCI and NCGI |
15.3.0 |
||
|
2018-03 |
CT#79 |
CP-180026 |
0498 |
1 |
External identifier in 5G |
15.3.0 |
||
|
2018-06 |
CT#80 |
CP-181132 |
0497 |
4 |
NF Service Endpoint Format for Inter PLMN Routing |
15.4.0 |
||
|
2018-06 |
CT#80 |
CP-181132 |
0500 |
2 |
NRF FQDN specification for NRF discoverability |
15.4.0 |
||
|
2018-06 |
CT#80 |
CP-181132 |
0501 |
2 |
NSSF FDQN for NSSF discovery before NRF is queried |
15.4.0 |
||
|
2018-06 |
CT#80 |
CP-181132 |
0502 |
1 |
AMF Name |
15.4.0 |
||
|
2018-06 |
CT#80 |
CP-181132 |
0504 |
2 |
Structure of SUPI and SUCI |
15.4.0 |
||
|
2018-06 |
CT#80 |
CP-181132 |
0505 |
1 |
GUAMI |
15.4.0 |
||
|
2018-06 |
CT#80 |
CP-181132 |
0508 |
2 |
Definition of DNN |
15.4.0 |
||
|
2018-06 |
CT#80 |
CP-181182 |
0503 |
2 |
Changed length and mapping of 5GS Temporary Identifiers |
15.4.0 |
||
|
2018-09 |
CT#81 |
CP-182084 |
0509 |
5 |
TAI in 5GC |
15.5.0 |
||
|
2018-09 |
CT#81 |
CP-182084 |
0511 |
3 |
SST value not associated with any valid SD |
15.5.0 |
||
|
2018-09 |
CT#81 |
CP-182084 |
0512 |
3 |
Definition of PEI |
15.5.0 |
||
|
2018-09 |
CT#81 |
CP-182084 |
0514 |
1 |
5GS TAI FQDN |
15.5.0 |
||
|
2018-09 |
CT#81 |
CP-182084 |
0515 |
– |
5GS Tracking Area Identity based ePDG FQDN |
15.5.0 |
||
|
2018-09 |
CT#81 |
CP-182084 |
0516 |
1 |
SUPI definition and NAI format |
15.5.0 |
||
|
2018-09 |
CT#81 |
CP-182084 |
0517 |
4 |
SUCI definition and NAI format |
15.5.0 |
||
|
2018-09 |
CT#81 |
CP-182084 |
0518 |
1 |
Network Capability SMF |
15.5.0 |
||
|
2018-09 |
CT#81 |
CP-182084 |
0519 |
1 |
AMF Discovery by 5G-AN |
15.5.0 |
||
|
2018-09 |
CT#81 |
CP-182067 |
0510 |
1 |
DNS records for selecting a node with a network capability in a Dedicated Core Network |
15.5.0 |
||
|
2018-12 |
CT#82 |
CP-183092 |
0529 |
3 |
SUCI definition and NAI format |
15.6.0 |
||
|
2018-12 |
CT#82 |
CP-183092 |
0520 |
1 |
Internal-Group Identifier |
15.6.0 |
||
|
2018-12 |
CT#82 |
CP-183092 |
0521 |
1 |
Definition of GPSI |
15.6.0 |
||
|
2018-12 |
CT#82 |
CP-183092 |
0522 |
– |
Selection of a PGW-U/UPF |
15.6.0 |
||
|
2018-12 |
CT#82 |
CP-183092 |
0523 |
1 |
15.6.0 |
|||
|
2018-12 |
CT#82 |
CP-183092 |
0524 |
2 |
Telescopic FQDN |
15.6.0 |
||
|
2018-12 |
CT#82 |
CP-183092 |
0525 |
1 |
Clarification of MSIN in SUCI |
15.6.0 |
||
|
2018-12 |
CT#82 |
CP-183092 |
0526 |
– |
Routing ID |
15.6.0 |
||
|
2018-12 |
CT#82 |
CP-183092 |
0527 |
1 |
SUPI definition |
15.6.0 |
||
|
2018-12 |
CT#82 |
CP-183092 |
0528 |
– |
EPS interworking with 5GS |
15.6.0 |
||
|
2019-06 |
CT#84 |
CP-191058 |
0530 |
1 |
Derivation of SUPI from SUCI |
15.7.0 |
||
|
2019-06 |
CT#84 |
CP-191058 |
0533 |
– |
NRF and NSSF URIs |
15.7.0 |
||
|
2019-09 |
CT#85 |
CP-182116 |
0541 |
– |
Presence Reporting Area Identifier (PRA ID) in 5GS |
15.8.0 |
||
|
2019-09 |
CT#85 |
CP-182232 |
0540 |
3 |
Clarification about the Routing Indicator |
15.8.0 |
||
|
2019-09 |
CT#85 |
CP-192133 |
0534 |
– |
Closed Access Group |
16.0.0 |
||
|
2019-09 |
CT#85 |
CP-192133 |
0539 |
2 |
Network Identifier for SNPN |
16.0.0 |
||
|
2019-09 |
CT#85 |
CP-192189 |
0543 |
1 |
UE radio capability ID format |
16.0.0 |
||
|
2019-09 |
CT#85 |
CP-192194 |
0536 |
2 |
ID |
16.0.0 |
||
|
2019-09 |
CT#85 |
CP-192194 |
0537 |
1 |
ID |
16.0.0 |
||
|
2019-09 |
CT#85 |
CP-192194 |
0538 |
1 |
SMF Set FQDN |
16.0.0 |
||
|
2019-12 |
CT#86 |
CP-193037 |
0549 |
– |
Clarification of possible values for Home Network Public Key Identifier of SUCI |
16.1.0 |
||
|
2019-12 |
CT#86 |
CP-193037 |
0556 |
1 |
Slice Differentiator (SD) in S-NSSAI |
16.1.0 |
||
|
2019-12 |
CT#86 |
CP-193037 |
0560 |
1 |
DNAI definition |
16.1.0 |
||
|
2019-12 |
CT#86 |
CP-193046 |
0550 |
1 |
Definition of Global Line Identifier |
16.1.0 |
||
|
2019-12 |
CT#86 |
CP-193046 |
0552 |
1 |
MAC Address as PEI format |
16.1.0 |
||
|
2019-12 |
CT#86 |
CP-193046 |
0558 |
1 |
NAI format used for 5G registration via trusted non-3GPP access |
16.1.0 |
||
|
2019-12 |
CT#86 |
CP-193050 |
0559 |
– |
FQDNs for Stand-alone Non-Public Networks |
16.1.0 |
||
|
2019-12 |
CT#86 |
CP-193240 |
0553 |
4 |
Global uniqueness of NID |
16.1.0 |
||
|
2019-12 |
CT#86 |
CP-193057 |
0544 |
1 |
Format of NF (Service) Set ID |
16.1.0 |
||
|
2019-12 |
CT#86 |
CP-193062 |
0548 |
– |
Update of UE radio capability ID format |
16.1.0 |
||
|
2019-12 |
CT#86 |
CP-193062 |
0561 |
Removal of TAC+SVN from network assigned UE Radio Capability IDs |
16.1.0 |
|||
|
2020-03 |
CT#87e |
CP-200032 |
0563 |
1 |
NID |
16.2.0 |
||
|
2020-03 |
CT#87e |
CP-200032 |
0565 |
2 |
NF (Service) Set ID definitions for Standalone Non-Public Networks |
16.2.0 |
||
|
2020-03 |
CT#87e |
CP-200032 |
0571 |
1 |
CAG-ID size |
16.2.0 |
||
|
2020-03 |
CT#87e |
CP-200032 |
0572 |
1 |
UE identifier for SNPN |
16.2.0 |
||
|
2020-03 |
CT#87e |
CP-200021 |
0564 |
2 |
UE Radio Capability ID |
16.2.0 |
||
|
2020-03 |
CT#87e |
CP-200021 |
0574 |
– |
DNS identifiers for UCMF |
16.2.0 |
||
|
2020-03 |
CT#87e |
CP-200035 |
0567 |
SUPI definition for 5G-RG and FN-RG |
16.2.0 |
|||
|
2020-03 |
CT#87e |
CP-200035 |
0568 |
3 |
SUCI definition for 5G-RG and FN-RG |
16.2.0 |
||
|
2020-03 |
CT#87e |
CP-200035 |
0569 |
3 |
User Location for RG accessing the 5GC via W-5GCAN or W-5GBAN |
16.2.0 |
||
|
2020-03 |
CT#87e |
CP-200035 |
0570 |
3 |
PEI for UEs not supporting any 3GPP access technologies |
16.2.0 |
||
|
2020-03 |
CT#87e |
CP-200035 |
0573 |
3 |
NAI format used for 5G registration via trusted non-3GPP access – part 2 |
16.2.0 |
||
|
2020-06 |
CT#88e |
CP-201014 |
0578 |
1 |
DNS subdomain for operator usage in 5GC |
16.3.0 |
||
|
2020-06 |
CT#88e |
CP-201046 |
0577 |
1 |
Definition of Truncated 5G-S-TMSI |
16.3.0 |
||
|
2020-06 |
CT#88e |
CP-201045 |
0579 |
– |
Remove Editor’s Note on New sub-domain for Interworking with SNPN |
16.3.0 |
||
|
2020-06 |
CT#88e |
CP-201045 |
0591 |
1 |
NID in TAI / ECGI / NCGI for SNPNs |
16.3.0 |
||
|
2020-06 |
CT#88e |
CP-201048 |
0580 |
1 |
Removal of the Editor’s Notes |
16.3.0 |
||
|
2020-06 |
CT#88e |
CP-201048 |
0590 |
– |
NAI format for SUCI containing a GLI or GCI |
16.3.0 |
||
|
2020-06 |
CT#88e |
CP-201035 |
0587 |
– |
Version ID in UE Radio Capability ID |
16.3.0 |
||
|
2020-06 |
CT#88e |
CP-201030 |
0588 |
1 |
Equivalent Service Sets |
16.3.0 |
||
|
2020-06 |
CT#88e |
CP-201030 |
0589 |
1 |
16.3.0 |
|||
|
2020-09 |
CT#89e |
CP-202043 |
0594 |
1 |
SMSF FQDN |
16.4.0 |
||
|
2020-09 |
CT#89e |
CP-202095 |
0592 |
1 |
Editor’s note in introduction clauses |
16.4.0 |
||
|
2020-09 |
CT#89e |
CP-202106 |
0595 |
– |
Adding definition for HRNN |
16.4.0 |
||
|
2020-09 |
CT#89e |
CP-202105 |
0596 |
1 |
Correction on Truncated 5G-S-TMSI |
16.4.0 |
||
|
2020-12 |
CT#90e |
CP-203039 |
0559 |
– |
Removal of Editor’s note for N5CW |
16.5.0 |
||
|
2020-12 |
CT#90e |
CP-203039 |
0598 |
1 |
GLI and GCI in SUCI |
16.5.0 |
||
|
2020-12 |
CT#90e |
CP-203058 |
0597 |
1 |
Support of PGW-C/SMF change |
17.0.0 |
||
|
2021-03 |
CT#91e |
CP-210052 |
0604 |
– |
Correcting APN-OI replacement specification mismatch between stage 2 and stage 3 |
17.1.0 |
||
|
2021-03 |
CT#91e |
CP-210049 |
0606 |
– |
DCN support for AMF discovery |
17.1.0 |
||
|
2021-03 |
CT#91e |
CP-210047 |
0609 |
1 |
Visited Country FQDN for SNPN N3IWF |
17.1.0 |
||
|
2021-06 |
CT#92e |
CP-211059 |
0615 |
1 |
Essential Correction on AMF Set ID |
17.2.0 |
||
|
2021-06 |
CT#92e |
CP-211034 |
0610 |
1 |
17.2.0 |
|||
|
2021-06 |
CT#92e |
CP-211034 |
0611 |
1 |
Including support for SNPN-based IMS identities |
17.2.0 |
||
|
2021-06 |
CT#92e |
CP-211034 |
0612 |
1 |
17.2.0 |
|||
|
2021-09 |
CT#93e |
CP-212039 |
0616 |
– |
F |
Self-assignment NID |
17.3.0 |
|
|
2021-09 |
CT#93e |
CP-212035 |
0618 |
– |
B |
Definition of Area Session ID |
17.3.0 |
|
|
2021-09 |
CT#93e |
CP-212035 |
0617 |
– |
B |
Definition of TMGI for MBS in 5GS |
17.3.0 |
|
|
2021-09 |
CT#93e |
CP-212058 |
0619 |
1 |
F |
FQDN for N3IWF selection for emergency services |
17.3.0 |
|
|
2021-09 |
CT#93e |
CP-212026 |
0620 |
– |
F |
Slice SD ranges |
17.3.0 |
|
|
2021-12 |
CT#94e |
CP-213148 |
0624 |
1 |
A |
Realm in SUCI in NAI format |
17.4.0 |
|
|
2021-12 |
CT#94e |
CP-213097 |
0621 |
– |
B |
Selection of a combined UPF/MB-UPF |
17.4.0 |
|
|
2022-03 |
CT#95e |
CP-220073 |
0632 |
– |
A |
RID for SNPN UEs |
17.5.0 |
|
|
2022-03 |
CT#95e |
CP-220047 |
0625 |
1 |
F |
SNPN impacts – NID length |
17.5.0 |
|
|
2022-03 |
CT#95e |
CP-220047 |
0626 |
1 |
B |
Anonymous SUCI |
17.5.0 |
|
|
2022-06 |
CT#96 |
CP-221023 |
0635 |
1 |
B |
MBS Frequency Selection Area ID |
17.6.0 |
|
|
2022-06 |
CT#96 |
CP-221030 |
0633 |
2 |
F |
Decorated NAI format for SUCI |
17.6.0 |
|
|
2022-06 |
CT#96 |
CP-221036 |
0628 |
4 |
F |
Correction to SNPN realm part of NAI |
17.6.0 |
|
|
2022-06 |
CT#96 |
CP-221036 |
0636 |
– |
F |
Group Identifier for Network Selection |
17.6.0 |
|
|
2022-06 |
CT#96 |
CP-221045 |
0634 |
– |
F |
Realm in SUCI in NAI format |
17.6.0 |
|
|
2022-09 |
CT#97e |
CP-222064 |
0639 |
1 |
A |
DNN Operator Identifier in SNPN |
17.7.0 |
|
|
2022-09 |
CT#97e |
CP-222031 |
0643 |
– |
F |
Editor’s note on Structure of TMGI |
17.7.0 |
|
|
2022-09 |
CT#97e |
CP-222035 |
0644 |
1 |
F |
NAI Format for PRUK ID and 5G PRUK ID |
17.7.0 |
|
|
2022-12 |
CT#98e |
CP-223048 |
0642 |
7 |
F |
NAI format for 5G NSWO |
17.8.0 |
|
|
2022-12 |
CT#98e |
CP-223054 |
0645 |
1 |
F |
Definition of 5G DDNMF FQDN |
17.8.0 |
|
|
2022-12 |
CT#98e |
CP-223054 |
0646 |
2 |
F |
PRUK and 5GPRUK Name Alignment |
17.8.0 |
|
|
2022-12 |
CT#98e |
CP-223031 |
0647 |
– |
B |
Slice-specific N3IWF FQDNs |
18.0.0 |
|
|
2022-12 |
CT#98e |
CP-223264 |
0648 |
5 |
B |
NAI format for 5G registration via trusted access using SNPN |
18.0.0 |
|