Content for  TS 23.502  Word version:  18.5.0

Service description:

Service operation name: Description: Inputs, Required: Inputs, Optional:

• If the consumer NF stores Data Set(s) (e.g. UDR): Range(s) of SUPIs, range(s) of GPSIs, range(s) of external group identifiers, Data Set Identifier(s).
• If the consumer is BSF: Range(s) of SUPIs, range(s) of GPSIs, Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes, IP domain list as described in clause 6.1.6.2.21 of TS 29.510, Range(s) of SUPIs, range(s) of GPSIs.
• If the consumer is UDM, UDR, PCF, BSF or AUSF, they can include UDM Group ID, UDR Group ID, PCF Group ID, BSF Group ID, AUSF Group ID respectively.
• For UDM and AUSF, Routing Indicator, or Routing Indicator and Home Network Public Key identifier; Home Network Identifier: PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN. Optionally, some NFs may additionally include a Home Network Identifier (including the identification of the CH with AAA Server or DCS with AAA Server) in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using a DCS with AAA Server.
• For NSSAAF, Home Network Identifier in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using credentials from a DCS with AAA Server.
• If the consumer is AMF, it includes list of GUAMI(s). In addition, AMF may include list of GUAMI(s) for which it can serve as backup for failure/maintenance.
• If the consumer is CHF, it may include Range(s) of SUPIs, Range(s) of GPSIs, or Range(s) of PLMNs as defined in TS 32.290.
• If the consumer is CHF, primary CHF instance and the secondary CHF instance pair. If the CHF does not provide NF set ID or NF Service Set ID, it shall provide a primary CHF instance and the secondary CHF instance pair and otherwise it may do so.
• If the consumer is P-CSCF, the P-CSCF IP address(es) to be provided to the UE by SMF.
• If the consumer is HSS, IMPI range, IMPU range, HSS Group ID (as defined in TS 23.228) can be used as optional input parameters.
• For the UPF Management: UPF Provisioning Information as defined in clause 4.17.6.
• S-NSSAI(s) and the associated NSI ID(s) (if available).
• DNN(s) if the consumer is PCF or BSF. DNN(s) per S-NSSAI if the consumer is SMF, UPF or TSCTSF.
• If the consumer is a trusted AF it may include one or multiple combination(s) of S-NSSAI and DNN corresponding to the AF. In addition, it may include supported Application Id(s), Event ID(s) and Internal-Group Identifier. It may include an indication whether it supports mapping between UE IP address (IPv4 address or IPv6 prefix) and UE ID (i.e. SUPI).
• Information about the location of the NF consumer (operator specific information, e.g. geographical location, data centre).
• TAI(s).
• NF Set ID.
• NF Service Set ID.
• If the consumer is PCF or SMF, it includes the MA-PDU Session capability to indicate if the NF instance supports MA-PDU session or not.
• If the consumer is PCF, it includes the DNN replacement capability to indicate if the NF instance supports DNN replacement or not.
• If the consumer is PCF or SMF, it includes the slice replacement capability to indicate if the NF instance supports slice replacement or not.
• If the consumer is PCF, it may include the 5G ProSe Capability as specified in TS 23.304.
• If the consumer is PCF, it may include the V2X capability as specified in TS 23.287.
• If the consumer is PCF, it may include the A2X capability as specified in TS 23.256.
• If the consumer is PCF, it may include the Ranging/SL Positioning Capability as specified in TS 23.586.
• If the consumer is PCF, it may include the indication of PCF support of URSP delivery in EPS.
• If the consumer is PCF, it may include the indication of PCF support of VPLMN specific rules.
• If the consumer is PCF, it may include the indication of PCF support of URSP rule enforcement.
• If the consumer is NWDAF, it may include:
  • Analytics ID(s) (possibly per service).
  • NWDAF Serving Area information and Supported Analytics Delay per Analytics ID(s) (if available).
  • Analytics aggregation capability and/ or Analytics metadata provisioning capability if such capability is provided by the NWDAF.
  • Roaming exchange capability if such capability is provided by NWDAF.
  • If the consumer NWDAF contains MTLF, it may also include the ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator per Analytics ID(s), if available (see clause 5.2 of TS 23.288).
  • If the consumer is NWDAF containing MTLF with Federated Learning (FL) capability, it includes FL capability information per analytics ID containing FL capability type (i.e. FL client and/or FL server, if available) and Time interval supporting FL, if available (see clause 5.2 of TS 23.288).
  • If the consumer is NWDAF containing MTLF with ML Model Accuracy checking capability, it includes ML Model Accuracy checking capability for ML model accuracy monitoring (see clause 5.2 of TS 23.288).
  • If the consumer is NWDAF containing AnLF with Analytics Accuracy checking capability, it includes Analytics Accuracy checking capability for Analytics Accuracy Monitoring (see clause 5.2 of TS 23.288).
  • It may also include NF Set ID and NF Type of the NF data sources, if data management service is available.
  Details about NWDAF specific information are described in clause 6.3.13 of TS 23.501.
• If the consumer is ADRF, it may include:
  • Data and analytics storage and retrieval capability if available.
  • ML model storage and retrieval capability if available.
  Details about ADRF specific information are described in clause 6.3.20 of TS 23.501.
• If the consumer is NEF, it may include Event ID(s) supported by AFs, the S-NSSAI and DNN corresponding to the untrusted AF served by the NEF, Application Identifier(s) supported by AFs, range(s) of External Identifiers, or range(s) of External Group Identifiers, or the domain names served by the NEF. It may also include an indication whether the untrusted AF supports mapping between UE IP address (IPv4 address or IPv6 prefix) and external UE ID (i.e. GPSI). If the consumer is local NEF, it may include parameters of list of supported TAI or list of supported DNAI additionally.
• If the consumer is a NSACF, it includes the S-NSSAI(s) of the PLMN or SNPN where the NSACF is located, the NSAC Service Area Identifier(s) n and NSACF service capabilities. Details about NSAC Service Area Identifier and NSACF service capabilities are described in clause 6.3.22 of TS 23.501.
• Notification endpoint for default subscription for each type of notification that the NF is interested in receiving.
• Endpoint Address(es) of instance(s) of supported service(s).
• NF capacity information.
• NF priority information.
• If consumer is NF, SCP domain the NF belongs to.
• If the consumer is SCP, it may include:
  • SCP domain(s) the SCP belongs to.
  • Remote PLMNs reachable through SCP.
  • Endpoint addresses or Address Domain(s) (e.g. IP Address or FQDN ranges) accessible via the SCP.
  • NF sets of NFs served by the SCP.
  • If the consumer NF is MB-SMF, it may include MB-SMF service area and the MBS Session ID(s), Area Session ID(s), the corresponding MBS service area(s) if available, as specified in TS 23.247.
• If the consumer is DCCF, the request may include DCCF Serving Area information, NF type of the NF data source, NF Set ID of the NF data sources, support for relocation of data subscription. Details about DCCF discovery and selection are described in clause 6.3.19 of TS 23.501.
• If the consumer is EASDF, it may include S-NSSAI, DNN, N6 IP address of the PSA UPF, location as per NF profile and DNAI (if exists).
• For ON-SNPN, if the consumer is AMF, Capability to support SNPN Onboarding, or, if the consumer is SMF, Capability to support User Plane Remote Provisioning.
• If the consumer is NEF, it may include the support for UAS NF functionality, the capability to support Multi-member AF session with required QoS and the capability to support member UE selection assistance functionality.
• If the consumer is UPF and UPF can expose NAT information, it may include the range of IP addresses the NAT uses towards the DN (e.g. public IP addresses). This IP address range may be on a per IP domain, DNN and S-NSSAI.
• If the consumer is DCSF, it may include an IMS domain name or a list of IMS domain names it serves, IMPU range of calling identity or called identity it serves, or IMPI range it serves.
• If the consumer is MF, it includes the data channel media capabilities it supports. It may also include MF location information as specified in TS 23.228.
• If the consumer is MRF or MRFP, it includes the list of supported IMS media services (as defined in TS 23.228).

  Outputs, Required: Outputs, Optional: See clause 5.21.2.1 of TS 23.501, the AMF registers itself to NRF.

Service operation name: Description: Inputs, Required: Inputs, Optional: Outputs, Required: Outputs, Optional: See clause 5.21.2.1 of TS 23.501, the AMF adds or updates the associated GUAMI(s).

Service operation name: Description: Inputs, Required: Inputs, Optional: Outputs, Required: Outputs, Optional: See clause 5.21.2.2 of TS 23.501, the AMF deregister itself from NRF.

Service operation name: Description:

• Newly registered NF along with its NF services.
• Updated NF profile.
• Deregistered NF.

Inputs, Required: Inputs, Optional: Outputs, Required: Outputs, Optional:

Service operation name: Description:

• Newly registered NF along with its NF services.
• Updated NF profile.
• Deregistered NF.

Inputs, Required: Inputs, Optional: Outputs, Required: Outputs, Optional:

Service Operation name: Description: Inputs, Required: Inputs, Optional: Outputs, Required: Outputs, Optional:

Service description: This service also enables an SCP to discover SCPs.

Service operation name: Description: Inputs, Required: If the NF service consumer intends to discover an NF service producer providing all the standardized services, it provides a wildcard NF service name. Inputs, Optional:

• S-NSSAI and the associated NSI ID (if available), DNN, target NF/NF service PLMN ID (or realm in the case of network specific identifier type SUCI/SUPI, see clause 4.17.5a), NRF to be used to select NFs/services within HPLMN or Credentials Holder, Serving PLMN ID (or PLMN ID and NID in the case of SNPN, see clause 4.17.5a), the NF service consumer ID, preferred target NF location, TAI.
• FQDN for the S5/S8 interface of the SMF+PGW-C, to discover the N11/N16 interface of the SMF+PGW-C in the case of EPS to 5GS mobility.
• If the target NF stores Data Set(s) (e.g. UDR, BSF): SUPI, GPSI, IMPI, IMPU, Data Set Identifier(s). (UE) IPv4 address, IP domain or (UE) IPv6 Prefix.
• If the target NF is UDM or AUSF, the request may include the UE's Routing Indicator, or the UE's Routing Indicator and Home Network Public Key identifier.
• If the target UDM or NF is AUSF, the request may include the UE's HNI: PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN. Optionally, some NFs may additionally include a Home Network Identifier in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using a DCS with AAA Server.
• If the target NF is NSSAAF, the request may include Home Network Identifier in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using credentials from a DCS with AAA Server.
• If the target NF is AMF and the consumer NF is MB-SMF for broadcast service, the request includes TAI(s) (see clause 7.3 of TS 23.247).
• If the target NF is AMF and the consumer NF is other than MB-SMF, the request may include:
• AMF region, AMF Set, GUAMI and Target TAI(s).
• If the target NF is UDR or UDM or AUSF or PCF or BSF, the request may include UDR Group ID or UDM Group ID or AUSF Group ID or PCF Group ID or BSF Group ID respectively.
• If the target NF is UDM, the request may include SUPI, GPSI, Internal Group ID and External Group ID.
• If the target NF is UPF, the request may include SMF Area Identity, UE IPv4 Address/IPv6 Prefix, supported ATSSS steering functionality, the supported UPF event exposure service and the supported Event IDs that can be subscribed. And if UPF can expose NAT information, the UE IPv4 address/IPv6 Prefix seen by the DN (e.g. a Public IP address).
• If the target NF is CHF, the request may include SUPI or GPSI as specified in TS 32.290.
• If the target NF is PCF or SMF, the request may include the MA-PDU Session capability to indicate that a NF instance supporting MA-PDU session capability is requested.
• If the target NF is PCF, the request may include the DNN replacement capability to indicate that a NF instance supporting DNN replacement capability is preferred.
• If the target NF is PCF or SMF, the request may include the slice replacement capability to indicate that a NF instance supporting slice replacement capability is preferred.
• If the target NF is PCF, the request may include the 5G ProSe Capability as specified in TS 23.304.
• If the target NF is PCF, the request may include the V2X capability as specified in TS 23.287.
• If the target NF is PCF, the request may include the A2X capability as specified in TS 23.256.
• If the target NF is PCF, the request may include the URSP delivery in EPS capability.
• If the target NF is PCF, the request may include the Ranging/SL Positioning Capability as specified in TS 23.586.
• If the target NF is NWDAF, the request may include:
  • Analytics ID(s) (possibly per service).
  • TAI(s).
  • Analytics aggregation capability and/or Analytics metadata provisioning capability.
  • A Real-Time Communication Indication per Analytics ID, NF Set ID and NF Type of the NF data sources.
  • Roaming exchange capability if data/analytics exchange between PLMNs is needed.
  • The S-NSSAI(s), Area(s) of Interest of the Trained ML Model required and NF consumer information when the target is an NWDAF containing MTLF.
  • Required FL capability type (i.e. FL server, FL client, if available) and Time period of interest when the target is an NWDAF containing MTLF with FL capability. When the target is an NWDAF containing MTLF with FL client capability, NF Set ID(s) of data source and NF type(s) where data can be collected as input for local model training may be included.
  • If the target NF is NWDAF containing MTLF with ML Model Accuracy checking capability, it includes ML Model Accuracy checking capability for ML model Accuracy Monitoring (see clause 5.2 of TS 23.288).
  • If the target NF is NWDAF containing AnLF with Analytics Accuracy checking capability, it includes Analytics Accuracy checking capability for Analytics Accuracy Monitoring (see clause 5.2 of TS 23.288).
  Details about NWDAF discovery and selection are described in clause 6.3.13 of TS 23.501.
• If target NF is ADRF, the request may include:
  • Data and analytics storage and retrieval capability.
  • ML model storage and retrieval capability.
  Details about ADRF discovery and selection are described in clause 6.3.20 of TS 23.501.
• If the target NF is HSS, the request may include IMPI and/or IMPU and/or HSS Group ID.
• If the NF service consumer needs to discover NF service producer instance(s) within an NF instance, the request includes the target NF Instance ID and NF Service Set ID of the producer.
• If the NF service consumer needs to discover NF service producer instance(s) in an equivalent NF Service Set within an NF Set, the request includes the identification of the equivalent NF service Set and NF Set ID of producer.
• If the NF service consumer needs to discover NF service producer instance(s) in the NF Set, the request includes the target NF Set ID of the producer.
• If the target NF is SMF, the request may include:
  • the UE location (TAI); or
  • TAI list.
• If the target NF is P-CSCF, the request may include UE location information, UE IP address/IP prefix, Access Type.
• If the target NF is NEF, the request may include Event ID(s) provided by AF and optional AF identification as described in clause 6.2.2.3 of TS 23.288. When the consumer is an AF, the request may include an External Identifier, External Group Identifier, or a domain name. If the target NF is local NEF, the request may include the parameters of list of supported TAI or list of supported DNAI additionally.
• If the target NF is SMF, the request may include the Control Plane CIoT 5GS Optimisation Indication or User Plane CIoT 5GS Optimisation Indication.
• If the target NF is a NSACF, the request may include the S-NSSAI(s) of the PLMN or SNPN where the NSACF is located , the NSAC Service Area Identifier and NSACF service capability. Details about NSACF discovery and selection are described in clause 6.3.22 of TS 23.501.
• If the target NF is SCP, the request may include information about:
  • SCP domain(s).
  • Remote PLMN reachable through SCP.
  • Endpoint addresses or Address Domain(s) (e.g. IP Address or FQDN ranges) accessible via the SCP.
  • NF sets of NFs served by the SCP.
• If the target NF is MB-SMF, the request may include UE location (i.e. TAI), MBS Session ID and Area Session ID. Details about MB-SMF discovery and selection are described in TS 23.247.
• If the target NF is 5G DDNMF, the request may include SUPI, IP Address or FQDN of 5G DDNMF.
• If the target NF is DCCF, the request may include TAI(s), NF type of the NF data sources, NF Set ID of the NF data sources, support for relocation of data subscription. Details about DCCF discovery and selection are described in clause 6.3.19 of TS 23.501.
• If the target NF is EASDF, the request may include S-NSSAI, DNN, N6 IP address of the PSA UPF, location as per NF profile and DNAI(if exist). Details about EASDF discovery and selection are described in clause 6.3.23 of TS 23.501.
• If the target NF is AMF, the request may include the support of SNPN Onboarding to indicate whether the target NF instance supports SNPN Onboarding or not.
• If the target NF is SMF, the request may include the support of User Plane Remote Provisioning to indicate whether the target NF instance supports User Plane Remote Provisioning or not as described in clause 5.30.2.10.4.3 of TS 23.501.
• If the target NF is NEF, the request may include the support of UAS NF functionality, the capability to support Multi-member AF session with required QoS and the capability to support member UE selection assistance functionality.
• If the target NF is NSSAAF, the request may include SUPI or Internal Group ID.
• If the target NF is DCSF, the request may include IMPU of calling party, SIP URI or Tel URI of called party.
• If the target NF is MF, the request may include the list of required data channel media capabilities or MF location information as specified in TS 23.228.
• If the target NF is MRF or MRFP, it includes the list of required IMS media services (as defined in TS 23.228).

Outputs, Required: Endpoint Address(es) may be a list of IP addresses or an FQDN for the NF service instance. Outputs, Optional:

• NF load information.
• NF capacity information.
• NF priority information.
• If the target NF stores Data Set(s) (e.g. UDR): Range(s) of SUPIs, range(s) of GPSIs, range(s) of external group identifiers, Data Set Identifier(s). If the target NF is BSF or P-CSCF: Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes, Range(s) of SUPIs, range(s) of GPSIs.
• If the target NF is UDM, UDR, PCF, BSF or AUSF, they can include UDM Group ID, UDR Group ID, PCF Group ID, BSF Group ID, AUSF Group ID respectively.
• If the target NF is HSS, it can include HSS Group ID.
• For UDM and AUSF, Routing Indicator, or Routing Indicator and Home Network Public Key identifier.
• If the target NF is AMF, it includes list of GUAMI(s). In addition, it may include list of GUAMI(s) for which it can serve as backup for failure/maintenance.
• If the target NF is CHF, it includes primary CHF instance and the secondary CHF instance pair(s), if configured in CHF instance profile.
• For the UPF Management: UPF Provisioning Information as defined in clause 4.17.6.
• S-NSSAI(s) and the associated NSI ID(s) (if available).
• Information about the location of the target NF (operator specific information, e.g. geographical location, data centre).
• TAI(s).
• PLMN ID.
• If the target is PCF or SMF, it includes the MA-PDU Session capability to indicate if the NF instance supports MA-PDU session or not.
• If the target is PCF, it includes the DNN replacement capability to indicate if the NF instance supports DNN replacement or not.
• If the target NF is NWDAF, it may include:
  • Analytics ID(s) (possibly per service).
  • NF Set ID and NF Type of the NF data sources, if available, NWDAF Serving Area information.
  • Analytics aggregation capability and/ or Analytics metadata provisioning capability, if such capability is provided by the NWDAF.
  • Supported Analytics Delay per Analytics ID.
  • If the target NF is NWDAF, it may also include the ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator per Analytics ID(s), if available (see clause 5.2 of TS 23.288).
  • If the target NF is NWDAF with FL capability, it may also include FL capability information per analytics ID containing FL capability type (i.e. FL server and/or FL client, if available) and Time interval supporting FL, if available (see clause 5.2 of TS 23.288).
  Details about NWDAF specific information are described in clause 6.3.13 of TS 23.501.
• If the target is a trusted AF, it includes one or multiple combination(s) of the S-NSSAI and DNN corresponding to the AF. In addition, it may include supported Application Id(s), Event ID(s) supported by the AF and Internal-Group Identifier.
• NF Set ID.
• NF Service Set ID.
• If the target NF is SMF, it may include the SMF(s) Service Area.
• If the target NF is P-CSCF, it includes P-CSCF FQDN(s) or IP address(es) and optional Access Type(s) associated with each P-CSCF.
• If the target NF is NEF, it may include Event ID(s) provided by AF and/or it includes one or multiple combination(s) of the S-NSSAI and DNN corresponding to the untrusted AF served by the NEF.
• SCP domain the NF belongs to.
• If the target is SCP:
  • SCP domain(s).
  • Remote PLMNs reachable through SCP.
  • Endpoint addresses or Address Domain(s) (e.g. IP Address or FQDN ranges) accessible via the SCP.
  • NF sets of NFs served by the SCP.
• If the target NF is 5G DDNMF, it may include IP Address or FQDN of 5G DDNMF.
• If the target NF is MB-SMF, it may include the MBS Session ID(s), Area Session ID(s), corresponding MBS service area(s) as described in TS 23.247.
• If the target NF is DCCF, it includes DCCF serving area information, NF type of the NF data sources, NF Set ID of the NF data sources, support for relocation of data subscription. Details about DCCF specific information are described in clause 6.3.19 of TS 23.501.

See clause 4.17.4 and 4.17.5 for details on the usage of this service operation.

This service provides OAuth2 2.0 Access Tokens for NF to NF authorization as defined in TS 33.501.

See TS 33.501.

Service Description:

Service operation name: Description: Inputs, Required: Inputs, Optional: Outputs, Required: Outputs, Optional: