Content for  TS 23.003  Word version:  19.0.0

The Generic Public Subscription Identifier (GPSI) is defined in clause 5.9.8 of TS 23.501. The GPSI is defined as:

• a GPSI type: in this release of the specification, it may indicate an MSISDN or an External Identifier; and
• dependent on the value of the GPSI type:
  • an MSISDN as defined in clause 3.3; or
  • an External Identifier as defined in clause 19.7.2.

Internal-Group Identifier is a network internal globally unique ID which identifies a set of SUPIs (e.g. MTC devices) from a given network that are grouped together for one specific group related service (see clause 5.9.7 of TS 23.501). An Internal-Group Identifier shall be composed in the same way as IMSI-Group Identifier (see clause 19.9). If a 5G subscriber's IMSI belongs to an IMSI-Group identified by a given IMSI-Group Identifier X, the IMSI shall also belong to the Internal-Group identified by the Internal-Group Identifier X.

The Presence Reporting Area Identifier (PRA ID) is used to identify a Presence Reporting Area (PRA). PRAs can be used for reporting changes of UE presence in a PRA, e.g. for policy control or charging decisions. See TS 23.501 and TS 23.503. A PRA is composed of a short list of TAs and/or NG-RAN nodes and/or cells identifiers in a PLMN.A PRA can be:

• either a "UE-dedicated PRA", defined in the subscriber profile;
• or a "Core Network predefined PRA", pre-configured in AMF.

PRA IDs used to identify "Core Network predefined PRAs" shall not be used for identifying "UE-dedicated PRAs". The same PRA ID may be used for different UEs to identify different "UE-dedicated PRAs", i.e. PRA IDs may overlap between different UEs, while identifying different "UE-dedicated PRAs". The PRA ID shall be formatted as an integer within the following ranges:

A Closed Access Group (CAG) within a PLMN is uniquely identified by a CAG-Identifier (see TS 23.501). The CAG-Identifier shall be a fixed length 32 bit value.

A NF Set Identifier is a globally unique identifier of a set of equivalent and interchangeable CP NFs from a given network that provide distribution, redundancy and scalability (see clause 5.21.3 of TS 23.501). An NF Set Identifier shall be constructed from the MCC, MNC, NID (for SNPN), NF type and a Set ID. A NF Set Identifier shall be formatted as the following string: where:

• the <MCC> and <MNC> shall identify the PLMN of the NF Set and shall be encoded as follows:
  • <MCC> = 3 digits
  • <MNC> = 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.
• the Network Identifier (NID) shall be encoded as hexadecimal digits as specified in clause 12.7.
• the <NFType> shall identify the NF type of the NFs within the NF set and shall be encoded as a value of Table 6.1.6.3.3-1 of TS 29.510 but with lower case characters;
• the Set ID shall be a NF type specific Set ID within the PLMN, chosen by the operator, that shall consist of alphabetic characters (A-Z and a-z), digits (0-9) and/or the hyphen (-) and that shall end with either an alphabetic character or a digit;
• the case of alphabetic characters is not significant (i.e. two NF Set IDs with the same characters but using different lower and upper cases identify the same NF Set).
  For an AMF set, the Set ID shall be set to "<AMF Set ID>-region<AMF Region ID>", with the AMF Region ID and AMF Set ID encoded as defined in TS 29.571.

EXAMPLE 1: EXAMPLE 2: EXAMPLE 3: EXAMPLE 4: FQDN. NF Instances of an NF Set are equivalent and share the same MCC, MNC, NID (for SNPN), NF type and NF Set ID. In earlier versions of this specification, the Set ID of an AMF Set was defined to be set to the string "<AMF Set ID>.region<AMF Region ID>". For backward compatibility with AMF implementations complying with these earlier versions of the specifications, AMF peers' implementations shall:

• support receiving such a former encoding of an AMF Set ID in 3GPP custom HTTP headers (e.g. 3gpp-Sbi-Binding header or 3gpp-Sbi-Producer header) and shall interpret it the same as if they receive these headers with the AMF Set format defined in the current version of the specification; and
• use the amf-region-id and the amf-set-id query parameters when they need to discover the AMF profiles of the AMF set registered at the NRF, when receiving a binding header with such a former encoding of the AMF Set ID.

A NF Service Set Identifier is a globally unique identifier of a set of equivalent and interchangeable CP NF service instances within a NF instance from a given network that provide distribution, redundancy and scalability (see clause 5.21.3 of TS 23.501). An NF Service Set Identifier shall be constructed from the MCC, MNC, NID (for SNPN), NF instance Identifier, service name and a Set ID. A NF Service Set Identifier shall be formatted as the following string: where:

• the <MCC> and <MNC> shall identify the PLMN of the NF Service Set and shall be encoded as follows:
  • <MCC> = 3 digits
  • <MNC> = 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.
• the Network Identifier (NID) shall be encoded as hexadecimal digits as specified in clause 12.7.
• the NFInstanceID shall identify the NF instance of the NF Service set, as defined by TS 23.501 and TS 29.510;
• the ServiceName shall identify the NF service of the NF Service set, as defined by TS 29.510;
• the Set ID shall be a service specific Set ID within the NF instance, chosen by the operator that shall consist of alphabetic characters (A-Z and a-z), digits (0-9) and/or the hyphen (-) and that shall end with either an alphabetic character or a digit;
• the case of alphabetic characters is not significant (i.e. two NF Service Set IDs with the same characters but using different lower and upper cases identify the same NF Service Set).

EXAMPLE 1: EXAMPLE 2: EXAMPLE 3: NF service instances from different NF instances are equivalent NF service instances if they share the same MCC, MNC, NID (for SNPN), ServiceName and Set ID. NF Service Sets belonging to different NF Instances are said to be equivalent, if they share the same MCC, MNC, NID (for SNPN), ServiceName and Set ID.

A Data Network Access Identifier (DNAI) is an operator defined identifier of a user plane access to one or more DN(s) where applications are deployed (see clauses 3.1 and 5.6.7 of TS 23.501). The same DN may also be referred to by multiple DNAIs. DNAI is represented as an operator specific string (see clause A.2 of TS 29.571. The format of the DNAI is defined by the operator and is not standardized.

The 5GC nodes DNS subdomain (DNS zone) shall be derived from the MNC and MCC by adding the label "node" to the beginning of the Home Network Domain for 5GC (see clause 28.2) and shall be constructed as: This DNS subdomain is formally placed into the operator's control. 3GPP shall never take this DNS subdomain back or any zone cut/subdomain within it for any purpose. As a result the operator can safely provision any DNS records it chooses under this subdomain without concern about future 3GPP standards encroaching on the DNS names within this zone.

The User Location information for a UE behind the 5G-RG using trusted N3GPP access (see clause 7.2.8.1 of TS 23.316), shall include a TNAP ID with 5G-RG civic address information.