Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.502  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.3…   4.3.2.2.2   4.3.2.2.3…   4.3.3…   4.3.4…   4.3.5…   4.3.5.2…   4.3.5.4…   4.3.5.6…   4.3.6…   4.4…   4.5…   4.9…   4.9.1.3…   4.9.2…   4.11…   4.11.1.2.2…   4.11.1.3…   4.11.1.4…   4.11.1.5…   4.11.2…   4.11.3…   4.12…   4.12.6…   4.12a…   4.12b…   4.13…   4.13.4…   4.13.6…   4.14…   4.15…   4.15.3.2.5…   4.15.4…   4.15.6.7…   4.15.7…   4.16…   4.16.4…   4.16.8…   4.16.11…   4.17…   4.17.9…   4.18…   4.19…   4.23…   4.23.7…   4.23.9…   4.23.11…   4.24…   4.25…   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   5.2.18…   A…   E…   F…

 

5.2.7  NRF ServicesWord‑p. 631

5.2.7.1  GeneralWord‑p. 631

The following table shows the NRF Services and Service Operations:
NF service Service Operations Operation Semantics Example Consumer(s)
Nnrf_NFManagementNFRegisterRequest/ResponseAMF, SMF, UDM, AUSF, NEF, PCF, SMSF, NSSF, UPF, BSF, CHF, NWDAF, P-CSCF, HSS, UDR, SCP, 5G DDNMF, DCCF, NSACF, MB-SMF, AF (NOTE 2), TSCTSF, EASDF, MFAF, ADRF
NFUpdateRequest/ResponseAMF, SMF, UDM, AUSF, NEF, PCF, SMSF, NSSF, UPF, BSF, CHF, NWDAF, P-CSCF, HSS, UDR, SCP, 5G DDNMF, DCCF, NSACF, MB-SMF, TSCTSF, EASDF, MFAF, ADRF
NFDeregisterRequest/ResponseAMF, SMF, UDM, AUSF, NEF, PCF, SMSF, NSSF, UPF, BSF, CHF, NWDAF, P-CSCF, HSS, UDR, SCP, 5G DDNMF, DCCF, NSACF, MB-SMF, TSCTSF, EASDF, MFAF, ADRF
NFStatusSubscribeSubscribe/NotifyAMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, CHF, NRF, NWDAF, I-CSCF, S-CSCF, IMS-AS, SCP, UDM, TSCTSF, DCCF
NFStatusNotifyAMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, CHF, NWDAF, I-CSCF, S-CSCF, IMS-AS, SCP, UDM, TSCTSF, DCCF
NFStatusUnSubscribeAMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, CHF, NRF, NWDAF, I-CSCF, S-CSCF, IMS-AS, SCP, UDM, TSCTSF, DCCF
Nnrf_NFDiscoveryRequestRequest/ResponseAMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, CHF, NRF, NWDAF, I-CSCF, S-CSCF, IMS-AS, SCP, UDM, AF (NOTE 2), DCCF, MBSF, 5G DDNMF, TSCTSF
Nnrf_AccessTokenGetRequest/ResponseAMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, UDM, NWDAF, I-CSCF, S-CSCF, IMS-AS, HSS, DCCF
Nnrf_BootstrappingGetRequest/ResponseNRF, any NF or SCP
 
Up

5.2.7.2  Nnrf_NFManagement serviceWord‑p. 631

5.2.7.2.1  GeneralWord‑p. 631
Service description:
This service enables one NF to manage its NF profile in NRF (i.e. register, update, deregister). This service also allows a consumer NF or SCP to subscribe in NRF to receive notifications regarding changes in the NF profile of other NFs.
5.2.7.2.2  Nnrf_NFManagement_NFRegister service operationWord‑p. 631
Service operation name:
Nnrf_NFManagement_NFRegister.
Description:
Registers the consumer NF in the NRF by providing the NF profile of the consumer NF to NRF and NRF marks the consumer NF available.
Inputs, Required:
NF type, NF instance ID, FQDN or IP address of NF, Names of supported NF services (if applicable) and PLMN ID e.g. if NF needs to be discovered by other PLMNs/SNPNs.
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, 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 NWDAF, it includes Analytics ID(s) (possibly per service), NWDAF Serving Area information and Supported Analytics Delay per Analytics ID(s) (if available). In addition, it includes Analytics aggregation capability and/ or Analytics metadata provisioning capability if such capability is provided by the 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), if available (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 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 NSACF, it includes S-NSSAI(s) of the NSACF located network and served by NSACF for which it manages the NSAC NSACF Serving Area information and NSACF service capabilities. Details about NSACF Service Area information 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. 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 includes the support for UAS NF functionality.
 
Outputs, Required:
Result indication.
Outputs, Optional:
None.
See clause 5.21.2.1 in TS 23.501, the AMF registers itself to NRF.
Up
5.2.7.2.3  Nnrf_NFManagement_NFUpdate service operationWord‑p. 634
Service operation name:
Nnrf_NFManagement_NFUpdate.
Description:
Provides the updated NF profile of NF consumer to NRF.
Inputs, Required:
NF instance ID.
Inputs, Optional:
If replacing the full NF profile, the full NF profile shall be provided. If updating parts of the NF profile, the NF profile elements that needs to be updated shall be provided.
Outputs, Required:
Result indication.
Outputs, Optional:
None.
See clause 5.21.2.1 in TS 23.501, the AMF adds or updates the associated GUAMI(s).
5.2.7.2.4  Nnrf_NFManagement_NFDeregister service operationWord‑p. 634
Service operation name:
Nnrf_NFManagement_NFDeregister
Description:
Inform the unavailability of NF consumer to NRF.
Inputs, Required:
NF Instance ID, Reason indication.
Inputs, Optional:
None.
Outputs, Required:
Result indication.
Outputs, Optional:
None.
See clause 5.21.2.2 in TS 23.501, the AMF deregister itself from NRF.
5.2.7.2.5  Nnrf_NFManagement_NFStatusSubscribe service operationWord‑p. 634
Service operation name:
Nnrf_NFManagement_NFStatusSubscribe.
Description:
Consumer can subscribe to be notified of the following:
  • Newly registered NF along with its NF services.
  • Updated NF profile.
  • Deregistered NF.
Inputs, Required:
callback URI.
Inputs, Optional:
  • PLMN ID of the target NF/NF service, in the case of the subscription to the status of NF/NF service instance(s) in home PLMN from the serving PLMN, or PLMN ID and NID in the case of SNPN (see clause 5.30.2.9.3 of TS 23.501).
  • 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.
  • Validity Time, in case to indicate the time instant after which the subscription becomes invalid.
  • For updated NF profile subscription, conditions that trigger a notification from NRF. Includes monitored attributes in the NF profile (changes trigger a notification) or unmonitored attributes in the NF profile (changes do not trigger a notification)
  • The following parameters are mutually exclusive:
    • NF Type (if NF status of a specific NF type is to be monitored).
    • NF Instance ID or NF Instance ID list (if NF status of a specific NF instance or a list of NF instance is to be monitored).
    • NF Service name (if NF status for NF which exposes a given NF service is to be monitored).
    • NF Set (if NF status of a set of NF Instances belonging to a certain NF Set is to be monitored).
    • NF Service Set (if the status of a set of NF Service Instances belonging to a certain NF Service Set is to be monitored).
    • NF Group (if the NF status of NF Instances identified by a NF (UDM, AUSF, PCF, BSF, CHF, HSS or UDR) Group Identity is to be monitored).
    • SCP Domain (if the status of NF or SCP instances belonging to a certain SCP domain is to be monitored).
    • For the UPF Management defined in clause 4.17.6: UPF Provisioning Information as defined in that clause.
    • For AMF, Consumer may include list of GUAMI(s), or AMF Set or AMF Region, or TAIs.
    • For SMF, Consumer may include list of TAIs.
    • S-NSSAI(s) and the associated NSI ID(s) (if available).
    • For NWDAF, Consumer may include Analytics ID(s) (possibly per service), TAI(s), NF Set ID and NF Type of NF data sources. If consumer is NWDAF, Consumer 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), if available (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.
    • For NEF, Consumer may include Event ID(s) provided by AF.
    • For DCCF, Consumer may include TAI(s), NF type of the NF data sources, NF Set ID of the NF data sources. Details about NWDAF discovery and selection are described in clause 6.3.19 of TS 23.501.
Outputs, Required:
When the subscription is accepted: Subscription Correlation ID (required for management of this subscription), Validity Time.
Outputs, Optional:
None.
Up
5.2.7.2.6  Nnrf_NFManagement_NFStatusNotify service operationWord‑p. 635
Service operation name:
Nnrf_NFManagement_NFStatusNotify.
Description:
NRF notifies subscribed consumers of the following:
  • Newly registered NF along with its NF services.
  • Updated NF profile.
  • Deregistered NF.
Inputs, Required:
Notification Event type; NF instance ID; for newly registered NF, NF profile; for updated NF, NF profile or NF profile changes.
Inputs, Optional:
None.
Outputs, Required:
None.
Outputs, Optional:
None.
5.2.7.2.7Void

5.2.7.3  Nnrf_NFDiscovery serviceWord‑p. 636

5.2.7.3.1  GeneralWord‑p. 636
Service description:
This service enables one NF or SCP to discover a set of NF instances with specific NF service or a target NF type or one or more SCPs. The service also enables one NF service or SCP to discover a specific NF service. The service operations defined below allow the NF/NF services or SCP to communicate with NRF.
This service also enables an SCP to discover SCPs.
Up
5.2.7.3.2  Nnrf_NFDiscovery_Request service operationWord‑p. 636
Service operation name:
Nnrf_NFDiscovery_Request
Description:
provides the IP address or FQDN of the expected NF instance(s) and, if present in NF profile, the Endpoint Address(es) of NF service instance(s) to the NF service consumer or SCP.
Inputs, Required:
one or more target NF service Name(s), NF type of the target NF, NF type of the NF service consumer.
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
  • 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, 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 NWDAF, the request may include Analytics ID(s) (possibly per service), TAI(s), Analytics aggregation capability, Analytics metadata provisioning capability, a Real-Time Communication Indication per Analytics ID, NF Set ID and NF Type of the NF data sources. The request may include the S-NSSAI(s) and Area(s) of Interest of the Trained ML Model required when the target is an NWDAF containing MTLF. Details about NWDAF discovery and selection are described in clause 6.3.13 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 NSACF, the request may include S-NSSAI(s) of the NSACF located network and served by NSACF, NSACF Serving Area information 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. 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.
  • If the target NF is NSSAAF, the request may include SUPI or Internal Group ID.
Outputs, Required:
A set of NF instances, a validity period for the discovery result, containing per NF Instance: NF type, NF instance ID, FQDN or IP address(es) of the NF instance and if applicable, a list of services instances, where each service instance has a service name, a NF service instance ID and optionally Endpoint Address(es)
Endpoint Address(es) may be a list of IP addresses or an FQDN for the NF service instance.
Outputs, Optional:
Per NF instance, other information in the NF profile listed in clause 6.2.6 in TS 23.501 related to the NF instance, such as:
  • 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 includes the Analytics ID(s) (possibly per service), NF Set ID and NF Type of the NF data sources, if available, NWDAF Serving Area information. In addition, it includes Analytics aggregation capability and/ or Analytics metadata provisioning capability, if such capability is provided by the NWDAF. It may include the Supported Analytics Delay per Analytics ID. If consumer 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), 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. 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.
Up

5.2.7.4  Nnrf_AccessToken_serviceWord‑p. 640

5.2.7.4.1  GeneralWord‑p. 640
This service provides OAuth2 2.0 Access Tokens for NF to NF authorization as defined in TS 33.501.
5.2.7.4.2  Nnrf_AccessToken_Get Service OperationWord‑p. 640
See TS 33.501.

5.2.7.5  Nnrf_Bootstrapping service |R17|Word‑p. 640

5.2.7.5.1  GeneralWord‑p. 640
Service Description:
The Nnrf_Bootstrapping service lets NF Service Consumers of the NRF know about the services endpoints it supports, the NRF Instance ID and NRF Set ID if the NRF is part of an NRF set, by using a version-independent URI endpoint that does not need to be discovered by using a Discovery service
5.2.7.5.2  Nnrf_Bootstrapping_Get service operationWord‑p. 640
Service operation name:
Nnrf_Bootstrapping_Get
Description:
Get the NRF service instances, their addresses and associated data.
Inputs, Required:
None.
Inputs, Optional:
None.
Outputs, Required:
NRF service instances and their endpoint addresses.
Outputs, Optional:
NF Set ID, NFR instance ID, Oath2 requirement for authorization, NFR status.

Up   Top   ToC