Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Table of Contents for  TS 23.003  Word version:   16.2.0

Top   Up   Prev   Next
1…   3…   4…   9…   13…   19…   20…   24…   28…   A…

 

28  Numbering, addressing and identification for 5G System (5GS) [R15]Word-p. 107
28.1  IntroductionUp
28.2  Home Network Domain
The Home Network Domain for 5GC shall be in the format specified in IETF RFC 1035 and IETF RFC 1123 and shall be structured as:
"5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org",
where "<MNC>" and "<MCC>" fields correspond to the MNC and MCC of the operator's PLMN. Both the "<MNC>" and "<MCC>" fields are 3 digits long. If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the NF service endpoint format for inter PLMN routing. As an example, the Home Network Domain for MCC 345 and MNC 12 is coded as:
"5gc.mnc012.mcc345.3gppnetwork.org".
The Home Network Domain for a Stand-alone Non-Public Network (SNPN) shall be in the format specified in IETF RFC 1035 and IETF RFC 1123 and, if not pre-configured in the NF, shall be structured as:
"5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org",
where <MNC> and <MCC> shall be encoded as specified above, and the NID shall be encoded as hexadecimal digits as specified in clause 12.7.
As an example, the Home Network Domain for MCC 345, MNC 12 and NID 0000343261ad5 (hexadecimal) is coded as:
"5gc.nid0000343261ad5.mnc012.mcc345.3gppnetwork.org".
NOTE: For interworking with an SNPN (e.g. discovery of AMFs from an SNPN by a shared NG RAN), the above sub-domain can be used when the MCC, MNC and NID uniquely identifies the SNPN. For signalling within an SNPN, the above sub-domain can be used regardless of whether the MCC, MNC and NID uniquely identifies the SNPN or not.
28.3  Identifiers for Domain Name System proceduresWord-p. 108
28.3.1  Introduction
28.3.2  Fully Qualified Domain Names (FQDNs)
28.3.2.1  General
28.3.2.2  N3IWF FQDN
28.3.2.2.1  General
The N3IWF Fully Qualified Domain Name (N3IWF FQDN) shall be constructed using one of the following formats, as specified in clause 6.3.6 of TS 23.501:
  • Operator Identifier based N3IWF FQDN;
  • Tracking Area Identity based N3IWF FQDN;
  • the N3IWF FQDN configured in the UE by the HPLMN.
    NOTE: The N3IWF FQDN configured in the UE can have a different format than those specified in the following clauses.
The Visited Country FQDN for N3IWF is used by a roaming UE to determine whether the visited country mandates the selection of an N3IWF in this country. The Visited Country FQDN for N3IWF shall be constructed as specified in clause 28.3.2.2.4. The Replacement field used in DNS-based Discovery of regulatory requirements shall be constructed as specified in clause 28.3.2.2.5.
28.3.2.2.2  Operator Identifier based N3IWF FQDN
The N3IWF Fully Qualified Domain Name (N3IWF FQDN) contains an Operator Identifier that shall uniquely identify the PLMN where the N3IWF is located. The N3IWF FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The third and fourth labels together shall uniquely identify the PLMN. The first two labels shall be "n3iwf.5gc". The result of the N3IWF FQDN will be:
"n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org"
In the roaming case, the UE can utilise the services of the VPLMN or the HPLMN. In this case, the Operator Identifier based N3IWF FQDN shall be constructed as described above, but using the MNC and MCC of the VPLMN or the HPLMN.
As an example, the Operator Identifier based N3IWF FQDN for MCC 345 and MNC 12 is coded in the DNS as:
"n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org".
28.3.2.2.3  Tracking Area Identity based N3IWF FQDNWord-p. 109
for 2-byte TAC:
"tac-lb<TAC-low-byte>.tac-hb<TAC-high-byte>.tac.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org"
for 3-byte TAC (5GS TAI):
"tac-lb<TAC-low-byte>.tac-mb<TAC-middle-byte>.tac-hb<TAC-highbyte>.5gstac.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org"
28.3.2.2.4  Visited Country FQDN for N3IWFWord-p. 110
"n3iwf.5gc.mcc<MCC>.visited-country.pub.3gppnetwork.org"
28.3.2.2.5  Replacement field used in DNS-based Discovery of regulatory requirements
28.3.2.3  PLMN level and Home NF Repository Function (NRF) FQDN
28.3.2.3.1  General
28.3.2.3.2  Format of NRF FQDN
"nrf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org"
28.3.2.3.3  NRF URIWord-p. 111
28.3.2.4  Network Slice Selection Function (NSSF) FQDN
28.3.2.5  AMF NameWord-p. 112
"<AMF-id>.amf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org"
28.3.2.6  5GS Tracking Area Identity (TAI) FQDN
"tac-lb<TAC-low-byte>.tac-mb<TAC-middle-byte>.tac-hb<TAC-high-byte>.5gstac.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org"
28.3.2.7  AMF Set FQDNWord-p. 113
"set<AMF Set Id>.region<AMF Region Id>.amfset.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org"
28.3.2.8  AMF Instance FQDN
"pt<AMF Pointer>.set<AMF Set Id>.region<AMF Region Id>.amfi.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org"
28.3.2.9  SMF Set FQDNWord-p. 114
28.4  Information for Network SlicingWord-p. 115
28.5  NF FQDN Format for Inter PLMN Routing
28.6  5GS Tracking Area Identity (TAI)Word-p. 116
3GPP Identifier: 5GS-TAI (5GS Tracking Area Identity)
28.7  Network Access Identifier (NAI)
defined in RFC 7542Section 2.2  (either of: "username", "@realm", "username@realm")
28.7.1  Introduction
28.7.2  NAI format for SUPIWord-p. 117
of the form: "username@realm"
28.7.3  NAI format for SUCI
of the form: "username"
for the null-scheme:
"type<supi type>.rid<routing indicator>.schid<protection scheme id>.userid<MSIN or Network Specific Identifier SUPI username>"
for the Scheme Output for Elliptic Curve Integrated Encryption Scheme Profile A and Profile B:
"type<supi type>.rid<routing indicator>.schid<protection scheme id>.hnkey<home network public key id>.ecckey<ECC ephemeral public key value>.cip<ciphertext value>.mac<MAC tag value>"
for HPLMN proprietary protection schemes:
"type<supi type>.rid<routing indicator>.schid<protection scheme id>.hnkey<home network public key id>.out<HPLMN defined scheme output>"
28.7.4  Emergency NAI for Limited Service StateWord-p. 118
"imei<IMEI>@sos.invalid"
"mac<MAC>@sos.invalid" (if IMEI is not available)
28.7.5  Alternative NAI
"<any_non_null_string>@unreachable.3gppnetwork.org"
28.7.6  NAI used for 5G registration via trusted non-3GPP access [R16]
28.7.7  NAI used by N5CW devices via trusted non-3GPP access [R16]
28.8  Generic Public Subscription Identifier (GPSI)Word-p. 119
28.9  Internal-Group Identifier
28.10  Presence Reporting Area Identifier (PRA ID)
28.11  CAG-IdentifierWord-p. 120
28.12  NF Set Identifier (NF Set ID)
28.13  NF Service Set Identifier (NF Service Set ID)Word-p. 121
28.14  Data Network Access Identifier (DNAI) [R16]
28.15  Global Cable Identifier (GCI) [R16]Word-p. 122
28.16  Global Line Identifier (GLI) [R16]Word-p. 123
29  Numbering, addressing and identification for RACS [R15]Word-p. 124

Up   Top   ToC