Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.502  Word version:   16.4.0

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…   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.4…   4.16…   4.16.4…   4.16.8…   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…   A…   E…   F…

 

5.2.7  NRF ServicesWord-p. 504
5.2.7.1  General
The following table shows the NRF Services and Service Operations:
Service Name
Service Operations
Operation Semantics
Example Consumer(s)

Nnrf_NFManagement
NFRegister
Request/Response
AMF, SMF, UDM, AUSF, NEF, PCF, SMSF, NSSF, UPF, BSF, CHF, NWDAF, P-CSCF, HSS, UDR
NFUpdate
Request/Response
AMF, SMF, UDM, AUSF, NEF, PCF, SMSF, NSSF, UPF, BSF, CHF, NWDAF, P-CSCF, HSS, UDR
NFDeregister
Request/Response
AMF, SMF, UDM, AUSF, NEF, PCF, SMSF, NSSF, UPF, BSF, CHF, NWDAF, P-CSCF, HSS, UDR
NFStatusSubscribe
Subscribe/Notify
AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, CHF, NRF, NWDAF, I-CSCF, S-CSCF, IMS-AS, SCP, UDM
NFStatusNotify
AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, CHF, NWDAF, I-CSCF, S-CSCF, IMS-AS, SCP, UDM
NFStatusUnSubscribe
AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, CHF, NRF, NWDAF, I-CSCF, S-CSCF, IMS-AS, SCP, UDM
Nnrf_NFDiscovery
Request
Request/Response
AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, CHF, NRF, NWDAF, I-CSCF, S-CSCF, IMS-AS, SCP, UDM, AF (NOTE 2)
Nnrf_AccessToken
Get
Request/Response
AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, UDM, NWDAF, I-CSCF, S-CSCF, IMS-AS, HSS

NOTE 1:
HSS_IMS services are defined in TS 23.228.
NOTE 2:
The AF is a trusted AF by an operator.

Up
5.2.7.2  Nnrf_NFManagement service
5.2.7.2.1  General
5.2.7.2.2  Nnrf_NFManagement_NFRegister service operation
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.
NOTE 1:
for the UPF, the addressing information within the NF profile corresponds to the N4 interface.
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 (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes.
  • NOTE 2:
    Range of SUPI(s) is limited in this release to a SUPI type of IMSI as defined in TS 23.003.
  • If the consumer is UDM, UDR, PCF or AUSF, they can include UDM Group ID, UDR Group ID, PCF Group ID, AUSF Group ID respectively.
  • For UDM and AUSF, Routing Indicator.
  • 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 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).
  • Information about the location of the NF consumer (operator specific information, e.g. geographical location, data center).
  • 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 NWDAF, it includes Analytics ID(s) and NWDAF Serving Area information. Details about NWDAF specific information are described in clause 6.3.13 of TS 23.501.
  • If the consumer is NEF, it may include range(s) of External Identifiers, or range(s) of External Group Identifiers, or the domain names served by the NEF.
  • 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.
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. 505
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. 506
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 operation
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:
NF type (if NF status of a specific NF type is to be monitored), NF instance ID (if NF status of a specific NF instance is to be monitored), NF service (if NF status for NF which exposes a given NF service is to be monitored).
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.
  • 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).
  • S-NSSAI(s) and the associated NSI ID(s) (if available).
  • For NWDAF, Consumer may include Analytics ID(s) and TAI(s). 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.
Outputs, Required:
When the subscription is accepted: Subscription Correlation ID (required for management of this subscription).
Outputs, Optional:
None.
NOTE:
Alternatively, other means such as OA&M can also be used to subscribe for NF status.
Up
5.2.7.2.6  Nnrf_NFManagement_NFStatusNotify service operation
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:
NF instance ID, NF Status, NF services (if the notification is for newly registered NF), new NF profile (if the notification is for updated NF profile).
Inputs, Optional:
  • If the 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). For BSF: Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes.
  • NOTE:
    Range of SUPI(s) is limited in this release to a SUPI type of IMSI as defined in TS 23.003.
  • If the NF is UDM, UDR or AUSF, they can include UDM Group ID, UDR Group ID, AUSF Group ID.
  • For UDM and AUSF, Routing Indicator.
  • For the UPF Management defined in clause 4.17.6: UPF Provisioning Information as defined in that clause.
  • For AMF, list of GUAMI(s) may be included. In addition, it may include list of GUAMI(s) for which it can serve as backup for failure/maintenance.
  • S-NSSAI(s) and the associated NSI ID(s) (if available).
  • Information about the location of the NF (operator specific information, e.g. geographical location, data center).
  • TAI(s).
  • If the NF is NWDAF, it includes Analytics ID(s) and NWDAF Serving Area information. Details about NWDAF specific information are described in clause 6.3.13 of TS 23.501.
  • NF Set ID.
  • NF Service Set ID.
  • If the NF is NEF, it may include Event ID(s) provided by AF.
Outputs, Required:
None.
Outputs, Optional:
None.
Up
5.2.7.2.7Void
5.2.7.3  Nnrf_NFDiscovery serviceWord-p. 507
5.2.7.3.1  General
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. 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.
5.2.7.3.2  Nnrf_NFDiscovery_Request service operation
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, NRF to be used to select NFs/services within HPLMN, Serving PLMN ID, the NF service consumer ID, preferred target NF location, TAI.
  • NOTE 1:
    For network slicing the NF service consumer ID is a required input.
  • FQDN for the S5/S8 interface of the PGW-C+SMF, to discover the N11/N16 interface of the PGW-C+SMF in the case of EPS to 5GS mobility.
  • If the target NF stores Data Set(s) (e.g., UDR, BSF): SUPI, IMPI, IMPU, Data Set Identifier(s). (UE) IPv4 address, IP domain or (UE) IPv6 Prefix.
  • NOTE 2:
    If the request includes a subscriber identifier the NRF may need to use the association between the supplied subscriber identifier and the appropriate NF Group ID as described in TS 23.501, clause 6.3.1 to determine the applicable set of NF instances for the response.
    NOTE 3:
    The (UE) IPv4 address or (UE) IPv6 Prefix is provided for BSF discovery: in that case the NRF looks up for a match within one of the Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes provided by BSF(s) as part of the invocation of Nnrf_NFManagement_NFRegister operation. The NRF is not meant to store individual (UE) IPv4 addresses or (UE) IPv6 prefixes.
  • If the target NF is UDM or AUSF, the request may include the UE's Routing Indicator.
  • If the target NF is AMF, the request may include AMF region, AMF Set, GUAMI and Target TAI.
  • If the target NF is UDR or UDM or AUSF or PCF, the request may include UDR Group ID or UDM Group ID or AUSF Group ID or PCF Group ID respectively.
  • NOTE 4:
    It is assumed that the corresponding NF service consumer is either configured with the corresponding Group ID or it received it via earlier Discovery output.
  • 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
    NOTE 5:
    The (UE) IPv4 address or (UE) IPv6 Prefix is provided for UPF discovery: in that case the NRF looks up for a match within one of the Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes provided by UPF as part of the invocation of Nnrf_NFManagement_NFRegister operation. The NRF is not meant to store individual (UE) IPv4 addresses or (UE) IPv6 prefixes.
    NOTE 6:
    Discovering UPF at PDU Session Establishment time and creating the N4 association assumes full connectivity between SMF and UPFs.
  • 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 NWDAF, the request may include Analytics ID(s) and TAI(s). 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.
  • NOTE 7:
    TS 29.510 specifies the mechanism to identify equivalent NF Service Sets.
  • 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).
  • 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 TS 23.288, clause 6.2.2.3. 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 SMF, the request may include the Contorl Plane CIoT 5GS Optimisation Indication or User Plane CIoT 5GS Optimisation Indication.
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, 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.
  • NOTE 8:
    Range of SUPI(s) is limited in this release to a SUPI type of IMSI as defined in TS 23.003.
  • If the target NF is UDM, UDR, PCF or AUSF, they can include UDM Group ID, UDR Group ID, PCF Group ID, AUSF Group ID respectively.
  • If the target NF is HSS, it can include HSS Group ID.
  • For UDM and AUSF, Routing Indicator.
  • 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).
  • 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 center).
  • 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) and NWDAF Serving Area information. Details about NWDAF specific information are described in clause 6.3.13 of TS 23.501.
  • NF Set ID.
  • NF Service Set ID.
  • If the target NF is SMF, it may include the SMF(s) Service Area.
  • NOTE 9:
    If no SMF Service Area is provided, the AMF assumes that a SMF can serve the whole PLMN.
  • 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.
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. 510
5.2.7.4.1  General
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 Operation
See TS 33.501.

Up   Top   ToC