Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.003  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   2…   2.8…   3…   4…   5…   6…   7…   8…   9…   10…   11   12…   13…   14…   15…   16…   17…   18…   19…   19.4…   19.5…   20…   21…   22…   23…   24…   25…   26…   27…   28…   28.3.2.2…   28.3.2.2.6…   28.3.2.3…   28.4…   28.7…   28.8…   29…   A…   B…   C…   D   E… 
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  28.3.2.3.3 NRF URI  28.3.2.4 Network Slice Selection Function (NSSF) FQDN  28.3.2.4.1 General  28.3.2.4.2 Format of NSSF FQDN  28.3.2.4.3 NSSF URI  28.3.2.5 AMF Name  28.3.2.6 5GS Tracking Area Identity (TAI) FQDN  28.3.2.7 AMF Set FQDN  28.3.2.8 AMF Instance FQDN  28.3.2.9 SMF Set FQDN  28.3.2.10 Short Message Service Function (SMSF) FQDN  28.3.2.11 5G DDNMF FQDN 
...

 

28.3.2.3  PLMN level and Home NF Repository Function (NRF) FQDN  p. 120

28.3.2.3.1  General  p. 120
When an NF is instantiated, it may register with a PLMN level NF Repository Function (NRF). It may then discover other NF instance(s) in the 5GC by querying the PLMN level NRF. The IP address of the PLMN level NRF can be provisioned into the NF, or the NF can be pre-configured with the FQDN of the PLMN level NRF. If the PLMN level NRF addresses and FDQN are not provisioned into the NF, the NF self-constructs the PLMN level NRF FQDN as per the format specified in clause 28.3.2.3.2.
For NF discovery across PLMNs, the NRF (e.g vNRF) shall self-construct the PLMN level NRF FQDN of the target PLMN (e.g hNRF) as per the format specified in clause 28.3.2.3.2, and the hNRF URI as per the format specified in subclause 28.3.2.3.3, if the NRF has not obtained the NRF FQDN of the target PLMN.
Up
28.3.2.3.2  Format of NRF FQDN  p. 120
The NRF FQDN for an NRF in an operator's PLMN shall be constructed by prefixing the Home Network Domain Name (see clause 28.2) of the PLMN in which the NRF is located with the label "nrf." as described below:
  • nrf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org
If the SUPI of the UE for construction of the NRF FQDN is of a type other than IMSI (e.g., NSI such as user@operator.com), the NRF FQDN of an NRF in an operator's SNPN, if not pre-configured in the NF, shall be constructed by prefixing the Home Network Domain Name (see clause 28.2) of the SNPN in which the NRF is located with the label "nrf."e.g.
  • nrf.operator.com:
  • nrf.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org (for SNPN scenarios where NID is available)
If the SUPI of the UE for construction of the NRF FQDN is of type IMSI, the NID is not available to the NF. Therefore, the NRF FQDN of an NRF in an operator's SNPN, if not pre-configured in the NF, is that of the NRF of the PLMN that owns the MCC and MNC as described below:
  • nrf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org
Up
28.3.2.3.3  NRF URI  p. 120
In absence of any other local configuration available in the vNRF, the API URIs of the hNRF shall be constructed by deriving the API root (see TS 29.501) as follows:
  • the authority part shall be set to the NRF FQDN as specified in clause 28.3.2.3.2
  • the scheme shall be "https"
  • the port shall be the default port for the "https" scheme, i.e. 443.
  • the API prefix optional component shall not be used
EXAMPLE:
For an MCC = 012 and MNC = 345, the API root of the NRF services shall be:
"https://nrf.5gc.mnc345.mcc012.3gppnetwork.org/"
Up

28.3.2.4  Network Slice Selection Function (NSSF) FQDN  p. 120

28.3.2.4.1  General  p. 120
For roaming service, the vNSSF may invoke the Nnssf_NSSelection_Get service operation from the hNSSF. For routing of the HTTP/2 messages across the PLMN, the vNSSF self-constructs the FQDN of the hNSSF as per the format specified in clause 28.3.2.4.2 and the URI of the hNSSF as per the format specified in clause 28.3.2.4.3. The Home Network is identified by the PLMN ID of the SUPI provided to the vNSSF by the NF Service Consumer (e.g. the AMF).
Up
28.3.2.4.2  Format of NSSF FQDN  p. 121
The NSSF FQDN for an NSSF in an operator's PLMN shall be constructed by prefixing its Home Network Domain Name (see clause 28.2) with the label "nssf." as described below:
  • nssf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org
The NSSF FQDN for an NSSF in an operator's SNPN, if not pre-configured in the NF, shall be constructed by prefixing the Home Network Domain Name (see clause 28.2) of the SNPN in which the NSSF is located with the label "nssf." as described below:
  • nssf.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org
Up
28.3.2.4.3  NSSF URI  p. 121
In absence of any other local configuration available in the vNSSF, the API URIs of the hNSSF shall be constructed by deriving the API root (see TS 29.501) as follows:
  • the authority part shall be set to the NSSF FQDN as specified in clause 28.3.2.4.2
  • the scheme shall be "https"
  • the port shall be the default port for the "https" scheme, i.e. 443.
  • the API prefix optional component shall not be used
EXAMPLE:
For an MCC = 012 and MNC = 345, the API root of the NSSF services shall be:
"https://nssf.5gc.mnc345.mcc012.3gppnetwork.org/"
Up

28.3.2.5  AMF Name  p. 121

The AMF Name FQDN shall uniquely identify an AMF.
The AMF Name FQDN for an AMF within an operator's PLMN shall be constructed as follows:
"<AMF-id>.amf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org"
where
  • the <MNC> and <MCC> shall identify the PLMN where the AMF is located and shall be encoded as
    • <MNC> = 3 digits
    • <MCC> = 3 digits
    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 AMF Name FQDN.
  • the <AMF-id> shall contain at least one label.
As example,
  • If <AMF-id> is amf1.cluster1.net2, the AMF Name FQDN for MCC 345 and MNC 12 is:
    "amf1.cluster1.net2.amf.5gc.mnc012.mcc345.3gppnetwork.org"
The AMF Name FQDN for an AMF within an operator's SNPN, if not pre-configured in the NF, shall be constructed as follows:
"<AMF-id>.amf.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org"
where
  • <MNC> and <MCC> shall be encoded as specified above;
  • NID shall be encoded as hexadecimal digits as specified in clause 12.7.
As example,
  • If <AMF-id> is amf1.cluster1.net2, the AMF Name FQDN for MCC 345, MNC 12 and NID 000007ed9d5 (hexadecimal) is:
    "amf1.cluster1.net2.amf.5gc.nid000007ed9d5.mnc012.mcc345.3gppnetwork.org"
Up

28.3.2.6  5GS Tracking Area Identity (TAI) FQDN  p. 122

The 5GS Tracking Area Identity (TAI) FQDN shall be constructed as follows:
"tac-lb<TAC-low-byte>.tac-mb<TAC-middle-byte>.tac-hb<TAC-high-byte>.5gstac. 5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org"
where the <TAC>, together with the <MCC> and <MNC> shall identify the 5GS Tracking Area Identity, and shall be encoded as follows:
  • <MNC> = 3 digits
  • <MCC> = 3 digits
    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 5GS TAI FQDN.
  • The 5GS TAC is a 24-bit integer. The <TAC-high-byte> is the hexadecimal string of the most significant byte in the TAC and the <TAC-low-byte > is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in <TAC-low-byte>, <TAC-middle-byte> or <TAC-high-byte >, "0" digit(s) shall be inserted at the left side to fill the 2 digits coding;
As an example, the 5GS Tracking Area Identity for the 5GS TAC H'0B1A21, MCC 345 and MNC 12 is coded in the DNS as:
"tac-lb21.tac-mb1a.tac-hb0b.5gstac.5gc.mnc012.mcc345.3gppnetwork.org"
Up

28.3.2.7  AMF Set FQDN  p. 122

An AMF Set within an operator's PLMN is identified by its AMF Set ID, AMF Region ID, MNC and MCC.
A subdomain name shall be derived from the MNC and MCC by adding the label "amfset" to the beginning of the Home Network Realm/Domain (see clause 28.2).
The AMF Set FQDN shall be constructed as follows:
set<AMF Set Id>.region<AMF Region Id>.amfset.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org
where
  • <MNC> = 3 digits
  • <MCC> = 3 digits
    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 AMF Set FQDN.
  • <AMF Set Id> and <AMF Region Id> are the hexadecimal strings of the AMF Set ID and AMF Region ID. If there are less than 2 significant digits in <AMF Region Id>, "0" digit(s) shall be inserted at the left side to fill the 2 digits coding. If there are less than 3 significant digits in <AMF Set Id>, "0" digit(s) shall be inserted at the left side to fill the 3 digits coding.
As an example, the AMF Set FQDN for the AMF Set 1, AMF Region 48 (hexadecimal), MCC 345 and MNC 12 is coded as:
"set001.region48.amfset.5gc.mnc012.mcc345.3gppnetwork.org"
An AMF Set within an operator's Stand-alone Non-Public Network (SNPN) shall be identified by its AMF Set ID, AMF Region ID and by either its Network Identifier (NID), MNC and MCC or an SNPN domain name pre-configured in the NF.
The AMF Set FQDN shall be constructed as follows:
set<AMF Set Id>.region<AMF Region Id>.amfset.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org
or
set<AMF Set Id>.region<AMF Region Id>.amfset.<SNPN domain name>
where
  • <MNC> and <MCC> shall be encoded as specified above;
  • NID shall be encoded as hexadecimal digits as specified in clause 12.7;
  • <SNPN domain name> is a domain name chosen by the SNPN operator.
As an example, the AMF Set FQDN for the AMF Set 1, AMF Region 48 (hexadecimal), NID 000007ed9d5 (hexadecimal), MCC 345 and MNC 12 is coded as:
"set001.region48.amfset.5gc.nid000007ed9d5. mnc012.mcc345.3gppnetwork.org"
Up

28.3.2.8  AMF Instance FQDN  p. 123

The AMF Instance FQDN shall uniquely identify an AMF instance.
The AMF Instance FQDN shall be constructed as:
pt<AMF Pointer>.set<AMF Set Id>.­region<AMF Region Id>.­amfi.­5gc.mnc<MNC>.­mcc<MCC>.­3gppnetwork.org
where
  • <MNC> = 3 digits
  • <MCC> = 3 digits
    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 AMF Instance FQDN.
  • <AMF Pointer>, <AMF Set Id> and <AMF Region Id> are the hexadecimal strings of the AMF Pointer, AMF Set ID and AMF Region ID. If there are less than 2 significant digits in <AMF Pointer> or <AMF Region Id>, "0" digit(s) shall be inserted at the left side to fill the 2 digits coding of the AMF Pointer or AMF Region Id respectively. If there are less than 3 significant digits in <AMF Set Id>, "0" digit(s) shall be inserted at the left side to fill the 3 digits coding.
As an example, the AMF Instance FQDN for the AMF Pointer 12 (hexadecimal), AMF Set 1, AMF Region 48 (hexadecimal), MCC 345 and MNC 12 is coded as:
"pt12.set001.region48.amfi.5gc.mnc012.mcc345.3gppnetwork.org"
Up

28.3.2.9  SMF Set FQDN |R16|  p. 123

An SMF Set within an operator's network is identified by its NF Set ID as defined in clause 28.12, with NFType set to "smf".
For an SMF Set within an operator's PLMN, a subdomain name shall be derived from the MNC and MCC by adding the label "smfset" to the beginning of the Home Network Realm/Domain (see clause 28.2).
The SMF Set FQDN shall be constructed as follows:
set<Set Id>.smfset.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org
where
  • <MNC> = 3 digits
  • <MCC> = 3 digits
    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 AMF Set FQDN.
  • <Set Id> is the string representing the Set ID part within the NF Set ID defined in clause 28.12.
EXAMPLE:
"set12. smfset.5gc.mnc012.mcc345.3gppnetwork.org"
(for the SMF set from MCC 345, MNC 12 and SetID "12")
For an SMF Set within an operator's Stand-alone Non-Public Network (SNPN), the SMF Set FQDN shall be constructed from its Network Identifier (NID), MNC and MCC or an SNPN domain name pre-configured in the NF, as follows:
set<Set Id>.smfset.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org
or
set<Set Id>.smfset.<SNPN domain name>
where
  • <MNC> and <MCC> shall be encoded as specified above;
  • NID shall be encoded as hexadecimal digits as specified in clause 12.7;
  • <SNPN domain name> is a domain name chosen by the SNPN operator.
EXAMPLE:
"set12.smfset.5gc.nid000007ed9d5.mnc012.mcc345.3gppnetwork.org"
(for an SMF set from MCC 345, MNC 12, NID 000007ed9d5 (hexadecimal) and SetID "12")
Up

28.3.2.10  Short Message Service Function (SMSF) FQDN  p. 124

The Short Message Service Function (SMSF) FQDN shall be constructed by prefixing its Home Network Domain Name (see clause 28.2) with the label "smsf" and with label(s) assigned by a PLMN as described below:
  • <label(s) assigned by a PLMN>.smsf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org
This format shall be used as a Diameter identity of an SMSF. A Diameter realm of an SMSF shall be a Home Network Domain Name (see clause 28.2), i.e.:
  • 5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org
Up

28.3.2.11  5G DDNMF FQDN |R17|  p. 124

The UE may construct the 5G DDNMF FQDN to discover the 5G DDNMF as specified in TS 23.304. The 5G DDNMF FQDN shall be constructed as follows:
"ddnmf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org"
where the <MCC> and <MNC> shall identify the PLMN where the 5G DDNMF is located. 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 5G DDNMF FQDN.
Up

Up   Top   ToC