Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.003  Word version:  18.4.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.2  N3IWF FQDNp. 110

28.3.2.2.1  Generalp. 110
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.
  • SNPN Identifier based N3IWF FQDN.
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.1.
The Visited Country FQDN for SNPN N3IWF is used by a UE in the visited country to determine whether the visited country mandates the selection of an N3IWF in this country for the SNPN identified by the SNPN Identifier provided by the UE. The Visited Country FQDN for SNPN N3IWF shall be constructed as specified in clause 28.3.2.2.6. The Replacement field used in DNS-based Discovery of SNPN N3IWF for regulatory requirements shall be constructed as specified in clause 28.3.2.2.7.2.
The Visited Country FQDN for N3IWF supporting Onboarding is used by a UE in the visited country to determine whether the visited country mandates the selection of an N3IWF in this country for onboarding services. The Visited Country FQDN with N3IWF supporting Onboarding shall be constructed as specified in clause 28.3.2.2.4.3. The Replacement field used in DNS-based Discovery of regulatory requirements shall be constructed as specified in clause 28.3.2.2.5.3.
The Visited Country FQDN for SNPN N3IWF supporting Onboarding is used by a UE in the visited country to determine whether the visited country mandates the selection of an SNPN N3IWF in this country for onboarding services. The Visited Country FQDN with SNPN N3IWF supporting Onboarding shall be constructed as specified in clause 28.3.2.2.6.2. The Replacement field used in DNS-based Discovery of SNPN N3IWF for regulatory requirements shall be constructed as specified in clause 28.3.2.2.7.2
Up
28.3.2.2.2  Operator Identifier based N3IWF FQDNp. 111
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 N3IWF FQDN shall be constructed as follows:
"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.
In order to guarantee inter-PLMN DNS translation, the <MNC> and <MCC> coding used in the "n3iwf.­5gc.­mnc<MNC>.­mcc<MCC>.­pub.­3gppnetwork.­org" format of the Operator Identifier based N3IWF FQDN shall be:
  • <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 N3IWF FQDN.
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".
Up
28.3.2.2.3  Tracking Area Identity based N3IWF FQDNp. 111
The Tracking Area Identity based N3IWF FQDN is used to support location based N3IWF selection within a PLMN.
There are two N3IWF FQDNs defined one based on a TAI with a 2 octet TAC and a 5GS one based on a 3 octet TAC.
  1. The Tracking Area Identity based N3IWF FQDN using a 2 octet TAC shall be constructed respectively as:
    "tac-lb<TAC-low-byte>.tac-hb<TAC-high-byte>.tac.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org"
    where
    • the <MNC> and <MCC> shall identify the PLMN where the N3IWF 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 N3IWF FQDN.
    • the <TAC>, together with the <MCC> and <MNC> shall identify the Tracking Area Identity the UE is located in.
      The TAC is a 16-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-high-byte> or <TAC-low-byte >, "0" digit(s) shall be inserted at the left side to fill the 2 digit coding;
    As examples,
    • the Tracking Area Identity based N3IWF FQDN for the TAC H'0B21, MCC 345 and MNC 12 is coded in the DNS as:
      "tac-lb21.tac-hb0b.tac.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org"
  2. The 5GS Tracking Area Identity based N3IWF FQDN using a 3 octet TAC shall be constructed respectively as:
    "tac-lb<TAC-low-byte>.tac-mb<TAC-middle-byte>.tac-hb<TAC-high-byte>.5gstac.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org"
    where
    • the <MNC> and <MCC> shall identify the PLMN where the N3IWF 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 N3IWF FQDN.
    • the <TAC>, together with the <MCC> and <MNC> shall identify the 5GSTracking Area Identity the UE is located in.
      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 digit coding;
    As examples,
    • the 5GS Tracking Area Identity based N3IWF FQDN for the 5GS TAC H'0B1A21, MCC 345 and MNC 12 is coded in the DNS as:
      "tac-lb21.tac-mb1a.tac-hb0b.5gstac.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org"
Up
28.3.2.2.4  Visited Country FQDN for N3IWFp. 112
28.3.2.2.4.1  General p. 112
The Visited Country FQDN for N3IWF, used by a roaming UE to determine whether the visited country mandates the selection of an N3IWF in this country, shall be constructed as described below.
The Visited Country FQDN shall contain a MCC that uniquely identifies the country in which the UE is located.
The Visited Country FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The fourth label shall be "visited-country". The third label shall uniquely identify the MCC of the visited country. The first and second labels shall be "n3iwf.5gc". The resulting Visited Country FQDN of N3IWF shall be constructed as follows:
"n3iwf.5gc.mcc<MCC>.visited-country.pub.3gppnetwork.org"
The <MCC> coding used in this FQDN shall be:
  • <MCC> = 3 digits
As an example, the Visited Country FQDN for MCC 345 is coded in the DNS as:
"n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org".
Up
28.3.2.2.4.2  Visited Country Emergency N3IWF FQDN p. 112
The Visited Country Emergency N3IWF FQDN, used by a roaming UE shall be constructed as specified for the Visited Country FQDN for N3IWF in clause 28.3.2.2.4.1, with the addition of the label "sos" before the labels "n3iwf.5gc".
The resulting Visited Country Emergency N3IWF FQDN shall be constructed as follows:
"sos.n3iwf.5gc.mcc<MCC>.visited-country.pub.3gppnetwork.org"
As an example, the Visited Country FQDN for MCC 345 is coded in the DNS as:
"sos.n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org".
Up
28.3.2.2.4.3  Visited Country FQDN for N3IWF supporting Onboarding p. 113
UE onboarding for access to SNPN services is specified in clause 5.30.2.12 of TS 23.501. Visited Country FQDN for N3IWF supporting Onboarding encoding is constructed by adding a label "onboarding" to Visited Country FQDN for N3IWF FQDN (see clause 28.3.2.2.4.1), indicating that the N3IWF identified by the N3IWF identifier in the DNS response shall supports onboarding.
Visited Country FQDN for N3IWF supporting Onboarding is constructed as follows:
"onboarding.n3iwf.5gc.mcc<MCC>.visited-country.pub.3gppnetwork.org"
As an example, the Visited Country FQDN for N3IWF supporting Onboarding for MCC 345, is coded in the DNS as:
"onboarding.n3iwf.5gc.­mcc345.­visited-country.­pub.­3gppnetwork.­org".
Up
28.3.2.2.5  Replacement field used in DNS-based Discovery of regulatory requirementsp. 113
28.3.2.2.5.1  General p. 113
If the visited country mandates the selection of an N3IWF in this country, the NAPTR record(s) associated to the Visited Country FQDN shall be provisioned with the replacement field containing the identity of the PLMN(s) in the visited country which may be used for N3IWF selection.
The replacement field shall take the form of an Operator Identifier based N3IWF FQDN as specified in clause 28.3.2.2.2.
For countries with multiple MCC, the NAPTR records returned by the DNS may contain a different MCC than the MCC indicated in the Visited Country FQDN.
As an example, the NAPTR records associated to the Visited Country FQDN for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as:
n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org
; IN NAPTR order
;              pref.
;                  flag
;                     service
;                        regexp
;                          replacement
  IN NAPTR 100 999 "" ""   n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org
  IN NAPTR 100 999 "" ""   n3iwf.5gc.mnc013.mcc345.pub.3gppnetwork.org
  IN NAPTR 100 999 "" ""   n3iwf.5gc.mnc014.mcc345.pub.3gppnetwork.org
Up
28.3.2.2.5.2  Replacement field used in DNS-based Discovery of regulatory requirements for emergency services via N3IWF p. 113
The NAPTR record(s) associated to the Visited Country Emergency N3IWF FQDN shall be provisioned with the replacement field containing the identity of the PLMN(s) in the visited country supporting emergency services in non-3GPP access via N3IWF.
The replacement field shall take the form of an operator identifier based N3IWF FQDN as specified clause 28.3.2.2.2, with the addition of the label "sos" before the labels "n3iwf.5gc".
As an example, the NAPTR records associated to the Visited Country Emergency N3IWF FQDN for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as:
sos.n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org
; IN NAPTR order
;              pref.
;                  flag
;                     service
;                        regexp
;                          replacement
  IN NAPTR 100 999 "" ""   sos.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org
  IN NAPTR 100 999 "" ""   sos.n3iwf.5gc.mnc013.mcc345.pub.3gppnetwork.org
  IN NAPTR 100 999 "" ""   sos.n3iwf.5gc.mnc014.mcc345.pub.3gppnetwork.org
Up
28.3.2.2.5.3  Replacement field used in DNS-based Discovery of N3IWF supporting Onboarding p. 114
If the visited country mandates the selection of an N3IWF supporting onboarding in this country, the NAPTR record(s) associated to the Visited Country FQDN for N3IWF supporting Onboarding shall be provisioned with the replacement field containing the Operator Identifier based Onboarding FQDN for N3IWF located in the visited country.
When UE sends the DNS query to the DNS server containing the Visited Country Onboarding FQDN for N3IWF (see clause 28.3.2.2.4.3), the DNS response should contain the Operator Identifier based Onboarding FQDN for N3IWF containing the identity of the PLMN(s) in the visited country which may be used for N3IWF selection in the visited country supporting Untrusted non-3GPP access for UE Onboarding via N3IWF.
If the UE has selected an PLMN for onboarding, the UE sends DNS query to the DNS server containing the Operator Identifier based Onboarding FQDN for N3IWF to query the identifier of the N3IWF supporting Onboarding, the DNS response should contain the identifier of the N3IWF supporting the onboarding in the PLMN identified by the PLMN ID.
The replacement field shall take the form of Operator Identifier based Onboarding FQDN for N3IWF as below:
"onboarding.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org"
For countries with multiple MCC, the NAPTR records returned by the DNS may contain a different MCC than the MCC indicated in the Visited Country FQDN for N3IWF supporting Onboarding.
As an example, the NAPTR records associated to the Visited Country FQDN for N3IWF supporting Onboarding for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as:
onboarding.n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org
; IN NAPTR order
;              pref.
;                  flag
;                     service
;                        regexp
;                          replacement
  IN NAPTR 100 999 "" ""   onboarding.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org
  IN NAPTR 100 999 "" ""   onboarding.n3iwf.5gc.mnc013.mcc345.pub.3gppnetwork.org
  IN NAPTR 100 999 "" ""   onboarding.n3iwf.5gc.mnc014.mcc345.pub.3gppnetwork.org
Up

Up   Top   ToC