Tech-invite   3GPPspecs   RFCs   Search in Tech-invite

full Table of Contents for  TS 23.003  Word version:   16.0.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. 104
28.1  Introduction
28.2  Home Network Domain
→  "5gc.mnc<MNC>.mcc<MCC>"
28.3  Identifiers for Domain Name System procedures
28.3.1  IntroductionUp
28.3.2  Fully Qualified Domain Names (FQDNs)  General  N3IWF FQDN  General  Operator Identifier based N3IWF FQDNWord-p. 105
→  "n3iwf.5gc.mnc<MNC>.mcc<MCC>"  Tracking Area Identity based N3IWF FQDN
→  for 2-byte TAC:
→  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>"  Visited Country FQDN for N3IWFWord-p. 106
→  "n3iwf.5gc.mcc<MCC>"  Replacement field used in DNS-based Discovery of regulatory requirements  PLMN level and Home NF Repository Function (NRF) FQDNWord-p. 107  GeneralUp  Format of NRF FQDN
→  "nrf.5gc.mnc<MNC>.mcc<MCC>"  NRF URI  Network Slice Selection Function (NSSF) FQDN  General  Format of NSSF FQDN
→  "nssf.5gc.mnc<MNC>.mcc<MCC>"  NSSF URIWord-p. 108  AMF Name
→  "<AMF-id>.amf.5gc.mnc<MNC>.mcc<MCC>"  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>"  AMF Set FQDNWord-p. 109
→  "set<AMF Set Id>.region<AMF Region Id>.amfset.5gc.mnc<MNC>.mcc<MCC>"  AMF Instance FQDNUp
→  "pt<AMF Pointer>.set<AMF Set Id>.region<AMF Region Id>.amfi.5gc.mnc<MNC>.mcc<MCC>"  SMF Set FQDN [R16]Word-p. 110
28.4  Information for Network Slicing
28.5  NF FQDN Format for Inter PLMN RoutingWord-p. 111
28.6  5GS Tracking Area Identity (TAI)
3GPP Identifier: 5GS-TAI (5GS Tracking Area Identity)
28.7  Network Access Identifier (NAI)Word-p. 112
→  defined in RFC 7542Section 2.2  (either of: "username", "@realm", "username@realm")
28.7.1  IntroductionUp
28.7.2  NAI format for SUPI
→  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. 113
→  "imei<IMEI>@sos.invalid"
→  "mac<MAC>@sos.invalid" (if IMEI is not available)
28.7.5  Alternative NAI
→  "<any_non_null_string>"
28.8  Generic Public Subscription Identifier (GPSI)
28.9  Internal-Group IdentifierWord-p. 114
28.10  Presence Reporting Area Identifier (PRA ID)
28.11  CAG-Identifier [R16]
28.12  NF Set Identifier (NF Set ID) [R16]
28.13  NF Service Set Identifier (NF Service Set ID) [R16]Word-p. 115
29  Numbering, addressing and identification for RACS [R16]

Up   Top   ToC