7 Network Function Services and descriptions

23.5013GPPRelease 18System architecture for the 5G System (5GS)TS

7.1 Network Function Service Framework

7.1.1 General

Service Framework functionalities include e.g. service registration/de-registration, consumer authorization, service discovery, and inter service communication, which include selection and message passing. Four communication options are listed in Annex E and can all co-exist within one and the same network.

An NF service is one type of capability exposed by an NF (NF Service Producer) to other authorized NF (NF Service Consumer) through a service-based interface. A Network Function may expose one or more NF services. Following are criteria for specifying NF services:

– NF services are derived from the system procedures that describe end-to-end functionality, where applicable (see TS 23.502 [3], Annex B drafting rules). Services may also be defined based on information flows from other 3GPP specifications.

– System procedures can be described by a sequence of NF service invocations.

NF services may communicate directly between NF Service consumers and NF Service Producers, or indirectly via an SCP. Direct and Indirect Communication are illustrated in Figure 7.1.1-1. For more information, see Annex E and clauses 6.3.1 and 7.1.2. Whether a NF Service Consumer (e.g. in the case of requests or subscriptions) or NF Service Producer (e.g. in the case of notifications) uses Direct Communication or Indirect Communication by using an SCP is based on the local configuration of the NF Service Consumer/NF Service Producer. An NF may not use SCP for all its communication based on the local configuration.

NOTE: The SCP can be deployed in a distributed manner.

In Direct Communication, the NF Service consumer performs discovery of the target NF Service producer by local configuration or via NRF. The NF Service consumer communicates with the target NF Service producer directly.

In Indirect Communication, the NF Service consumer communicates with the target NF Service producer via a SCP. The NF Service consumer may be configured to perform discovery of the target NF Service producer directly, or delegate the discovery of the target NF Service Producer to the SCP used for Indirect Communication. In the latter case, the SCP uses the parameters provided by NF Service consumer to perform discovery and/or selection of the target NF Service producer. The SCP address may be locally configured in NF Service consumer.

Figure 7.1.1-1: NF/NF service inter communication

7.1.2 NF Service Consumer – NF Service Producer interactions

The end-to-end interaction between two Network Functions (Consumer and Producer) within this NF service framework follows two mechanisms, irrespective of whether Direct Communication or Indirect Communication is used:

– "Request-response": A Control Plane NF_B (NF Service Producer) is requested by another Control Plane NF_A (NF Service Consumer) to provide a certain NF service, which either performs an action or provides information or both. NF_B provides an NF service based on the request by NF_A. In order to fulfil the request, NF_B may in turn consume NF services from other NFs. In Request-response mechanism, communication is one to one between two NFs (consumer and producer) and a one-time response from the producer to a request from the consumer is expected within a certain timeframe. The NF Service Producer may also add a Binding Indication (see clause 6.3.1.0) in the Response, which may be used by the NF Service Consumer to select suitable NF service producer instance(s) for subsequent requests. For indirect communication, the NF Service Consumer copies the Binding Indication into the Routing Binding indication, that is included in subsequent requests, to be used by the SCP to discover a suitable NF service producer instance(s).

Figure 7.1.2-1: "Request-response" NF Service illustration

– "Subscribe-Notify": A Control Plane NF_A (NF Service Consumer) subscribes to NF Service offered by another Control Plane NF_B (NF Service Producer). Multiple Control Plane NFs may subscribe to the same Control Plane NF Service. NF_B notifies the results of this NF service to the interested NF(s) that subscribed to this NF service. The subscription request shall include the notification endpoint, i.e. Notification Target Address) and a Notification Correlation ID (e.g. the notification URL) of the NF Service Consumer to which the event notification from the NF Service Producer should be sent to.

NOTE 1: The notification endpoint URL can contain both the notification endpoint and the Notification Correlation ID.

The NF Service Consumer may add a Binding Indication (see clause 6.3.1.0) in the subscribe request, which may be used by the NF Service Producer to discover a suitable notification endpoint. For indirect communication, the NF Service Producer copies the Binding Indication into the Routing Binding Indication, that is included in the response, to be used by the SCP to discover a suitable notification target. The NF Service Producer may also add a Binding Indication (see clause 6.3.1.0) in the subscribe response, which may be used by the NF Service Consumer (or SCP) to select suitable NF service producer instance(s) or NF producer service instance. In addition, the subscription request may include notification request for periodic updates or notification triggered through certain events (e.g. the information requested gets changed, reaches certain threshold etc.). The subscription for notification can be done through one of the following ways:

– Explicit subscription: A separate request/response exchange between the NF Service Consumer and the NF Service Producer; or

– Implicit subscription: The subscription for notification is included as part of another NF service operation of the same NF Service; or

– Default notification endpoint: Registration of a notification endpoint for each type of notification the NF consumer is interested to receive, as a NF service parameter with the NRF during the NF and NF service Registration procedure as specified in clause 4.17.1 of TS 23.502 [3].

The NF Service Consumer may also add a Binding Indication (see clause 6.3.1.0) in the response to the notification request, which may be used by the NF Service Producer to discover a suitable notification endpoint. For indirect communication, the NF Service Producer copies the Binding Indication into the Routing Binding indication that is included in subsequent notification requests. The binding indication is then used by the SCP to discover a suitable notification target.

Figure 7.1.2-2: "Subscribe-Notify" NF Service illustration 1

A Control Plane NF_A may also subscribe to NF Service offered by Control Plane NF_B on behalf of Control Plane NF_C, i.e. it requests the NF Service Producer to send the event notification to another consumer(s). In this case, NF_A includes the notification endpoint, i.e. Notification Target Address) and a Notification Correlation ID, of the NF_C in the subscription request. NF_A may also additionally include the notification endpoint and a Notification Correlation ID of NF A associated with subscription change related Event ID(s), e.g. Subscription Correlation ID Change, in the subscription request, so that NF_A can receive the notification of the subscription change related event. The NF_A may add Binding Indication (see clause 6.3.1.0) in the subscribe request.

Figure 7.1.2-3: "Subscribe-Notify" NF Service illustration 2

Routing of the messages for the NF interaction mechanisms above may be direct, as shown in the figures 7.1.2-1 to 7.1.2-3, or indirect. In the case of Indirect Communication, an SCP is employed by the NF service consumer. The SCP routes messages between NF service consumers and NF service producers based on the Routing Binding Indication if available, and may do discovery and associated selection of the NF service producer on behalf of a NF service consumer. Figure 7.1.2-4 shows the principle for a request-response interaction and figure 7.1.2-5 shows an example of a subscribe-notify interaction.

Figure 7.1.2-4: Request response using Indirect Communication

Figure 7.1.2-5: Subscribe-Notify using Indirect Communication

NOTE: The subscribe request and notify request can be routed by different SCPs.

7.1.3 Network Function Service discovery

A Control Plane Network function (NF) within the 5G Core network may expose its capabilities as services via its service based interface, which can be re-used by Control Plane CN NFs.

The NF service discovery enables a CN NF or SCP to discover NF instance(s) that provide the expected NF service(s). The NF service discovery is implemented via the NF discovery functionality.

For more detail NF discovery refer to clause 6.3.1.

7.1.4 Network Function Service Authorization

NF service authorization shall ensure the NF Service Consumer is authorized to access the NF service provided by the NF Service Provider, according to e.g. the policy of NF, the policy from the serving operator, the inter-operator agreement.

Service authorization information shall be configured as one of the components in NF profile of the NF Service Producer. It shall include the NF type (s) and NF realms/origins allowed to consume NF Service(s) of NF Service Producer.

Due to roaming agreements and operator policies, a NF Service Consumer shall be authorised based on UE/subscriber/roaming information and NF type, the Service authorization may entail two steps:

– Check whether the NF Service Consumer is permitted to discover the requested NF Service Producer instance during the NF service discovery procedure. This is performed on a per NF granularity by NRF.

NOTE 1: When NF discovery is performed based on local configuration, it is assumed that locally configured NFs are authorized.

– Check whether the NF Service Consumer is permitted to access the requested NF Service Producer for consuming the NF service, with a request type granularity. This is performed on a per UE, subscription or roaming agreements granularity. This type of NF Service authorization shall be embedded in the related NF service logic.

NOTE 2: The security of the connection between NF Service Consumer and NF Service Producer is specified in TS 33.501 [29].

NOTE 3: It is expected that an NF authorization framework exists in order to perform consumer NF authorization considering UE, subscription or roaming agreements granularity. This authorization is assumed to be performed without configuration of the NRF regarding UE, subscription or roaming information.

7.1.5 Network Function and Network Function Service registration and de-registration

For the NRF to properly maintain the information of available NF instances and their supported services, each NF instance informs the NRF of the list of NF services that it supports.

NOTE: The NF informs the appropriate NRF based on configuration.

The NF instance may make this information available to NRF when the NF instance becomes operative for the first time (registration operation) or upon individual NF service instance activation/de-activation within the NF instance (update operation) e.g. triggered after a scaling operation. The NF instance while registering the list of NF services it supports, for each NF service, may provide a notification endpoint information for each type of notification service that the NF service is prepared to consume, to the NRF during the NF instance registration. The NF instance may also update or delete the NF service related parameters (e.g. to delete the notification endpoint information). Alternatively, another authorised entity (such as an OA&M function) may inform the NRF on behalf of an NF instance triggered by an NF service instance lifecycle event (register or de-registration operation depending on instance instantiation, termination, activation, or de-activation). Registration with the NRF includes capacity and configuration information at time of instantiation.

The NF instance may also de-registers from the NRF when it is about to gracefully shut down or disconnect from the network in a controlled way. If an NF instance become unavailable or unreachable due to unplanned errors (e.g. NF crashes or there are network issues), an authorised entity shall de-register the NF instance with the NRF.

7.2 Network Function Services

7.2.1 General

In the context of this specification, an NF service is offering a capability to authorised consumers.

Network Functions may offer different capabilities and thus, different NF services to distinct consumers. Each of the NF services offered by a Network Function shall be self-contained, reusable and use management schemes independently of other NF services offered by the same Network Function (e.g. for scaling, healing, etc).

The discovery of the NF instance and NF service instance is specified in clause 6.3.1.

NOTE 1: There can be dependencies between NF services within the same Network Function due to sharing some common resources, e.g. context data. This does not preclude that NF services offered by a single Network Function are managed independently of each other.

Figure 7.2.1-1: Network Function and NF Service

Each NF service shall be accessible by means of an interface. An interface may consist of one or several operations.

Figure 7.2.1-2: Network Function, NF Service and NF Service Operation

System procedures, as specified in TS 23.502 [3] can be built by invocation of a number of NF services. The following figure shows an illustrative example on how a procedure can be built; it is not expected that system procedures depict the details of the NF Services within each Network Function.

Figure 7.2.1-3: System Procedures and NF Services

NOTE 2: The SCP can be used for indirect communication between NF/NF service instances. For simplicity the SCP is not shown in the procedure.

The following clauses provide for each NF the NF services it exposes through its service based interfaces.

7.2.2 AMF Services

The following NF services are specified for AMF:

Table 7.2.2-1: NF Services provided by AMF

Service Name	Description	Reference in TS 23.502 [3] or indicated other TS
Namf_Communication	Enables an NF consumer to communicate with the UE and/or the AN through the AMF. This service enables SMF to request EBI allocation to support interworking with EPS. This service also supports PWS functionality as described in TS 23.041 [46].	5.2.2.2
Namf_EventExposure	Enables other NF consumers to subscribe or get notified of the mobility related events and statistics.	5.2.2.3
Namf_MT	Enables an NF consumer to make sure UE is reachable.	5.2.2.4
Namf_Location	Enables an NF consumer to request location information for a target UE.	5.2.2.5
Namf_MBSBroadcast	Enables the NF consumer to communicate with the NG-RAN for broadcast communication.	TS 23.247 [129]
Namf_MBSCommunication	Enables NF consumer to communicate with the NG-RAN for multicast communication.	TS 23.247 [129]

7.2.3 SMF Services

The following NF services are specified for SMF:

Table 7.2.3-1: NF Services provided by SMF

Service Name	Description	Reference in TS 23.502 [3]
Nsmf_PDUSession	This service manages the PDU Sessions and uses the policy and charging rules received from the PCF. The service operations exposed by this NF service allows the consumer NFs to handle the PDU Sessions.	5.2.8.2
Nsmf_EventExposure	This service exposes the events happening on the PDU Sessions to the consumer NFs.	5.2.8.3
Nsmf_NIDD	This service is used for NIDD transfer between SMF and another NF.	5.2.8.4

7.2.4 PCF Services

The following NF services are specified for PCF:

Table 7.2.4-1: NF Services provided by PCF

Service Name	Description	Reference in TS 23.502 [3] or indicated other TS
Npcf_AMPolicyControl	This PCF service provides Access Control, network selection and Mobility Management related policies, UE Route Selection Policies to the NF consumers.	5.2.5.2
Npcf_SMPolicyControl	This PCF service provides session related policies to the NF consumers.	5.2.5.4
Npcf_PolicyAuthorization	This PCF service authorises an AF request and creates policies as requested by the authorised AF for the PDU Session to which the AF session is bound to. This service allows the NF consumer to subscribe/unsubscribe to the notification of Access Type and RAT type, PLMN identifier, access network information, usage report etc.	5.2.5.3
Npcf_BDTPolicyControl	This PCF service provides background data transfer policy negotiation and optionally notification for the renegotiation to the NF consumers.	5.2.5.5
Npcf_UEPolicyControl	This PCF service provides the management of UE Policy Association to the NF consumers.	5.2.5.6
Npcf_EventExposure	This PCF service provide the support for event exposure.	5.2.5.7
Npcf_AMPolicyAuthorization	The PCF authorises an AF request and uses it as input for deciding access and mobility management related policies for a UE.	5.2.5.8
Npcf_MBSPolicyControl	The PCF service provides MBS session related policies towards the MB-SMF.	TS 23.247 [129]
Npcf_MBSPolicyAuthorization	This service authorizes an AF / NEF / MBSF request for an MBS service and t creates policies as requested by the authorized AF for the MBS Service.	TS 23.247 [129]
Npcf_PDTQPolicyControl	This PCF service provides negotiation for Planned Data Transfer with QoS requirements policy and optionally notification for the renegotiation to the NF consumers.	5.2.5.9

7.2.5 UDM Services

The following NF services are specified for UDM:

Table 7.2.5-1: NF Services provided by UDM

Service Name	Description	Reference in TS 23.502 [3]
Nudm_UECM	1. Provide the NF consumer of the information related to UE’s transaction information, e.g. UE’s serving NF identifier, UE status, etc. 2. Allow the NF consumer to register and deregister its information for the serving UE in the UDM. 3. Allow the NF consumer to update some UE context information in the UDM.	5.2.3.2
Nudm_SDM	1. Allow NF consumer to retrieve user subscription data when necessary. 2. Provide updated user subscriber data to the subscribed NF consumer.	5.2.3.3
Nudm_UEAuthentication	1. Provide updated authentication related subscriber data to the subscribed NF consumer. 2. For AKA based authentication, this operation can be also used to recover from security context synchronization failure situations. 3. Used for being informed about the result of an authentication procedure with a UE.	5.2.3.4
Nudm_EventExposure	1. Allow NF consumer to subscribe to receive an event. 2. Provide monitoring indication of the event to the subscribed NF consumer.	5.2.3.5
Nudm_ParameterProvision	1. To provision information which can be used for the UE in 5GS.	5.2.3.6
Nudm_NIDDAuthorisation	1. To authorise an NIDD configuration request for the received External Group Identifier or GPSI.	5.2.3.7
Nudm_ ServiceSpecificAuthorisation	1. To authorise for a specific service configuration.	5.2.3.8
Nudm_ReportSMDeliveryStatus	1. To report the SM-Delivery Status to UDM.	5.2.3.9

7.2.6 NRF Services

The following NF services are specified for NRF:

Table 7.2.6-1: NF Services provided by NRF

Service Name	Description	Reference in TS 23.502 [3]
Nnrf_NFManagement	Provides support for register, deregister and update service to NF, NF services, SCP. Provide NF service consumers and SCP with notifications of newly registered/updated/deregistered NF along with its NF services. Also Provide SCP with notifications of newly registered/updated/deregistered SCP.	5.2.7.2
Nnrf_NFDiscovery	Enables one NF service consumer or SCP to discover a set of NF instances with specific NF service or a target NF type. Also enables one NF service consumer or SCP to discover a specific NF service. Also enables a SCP to discover a next hop SCP.	5.2.7.3
Nnrf_AccessToken	Provides OAuth2 2.0 Access Tokens for NF to NF authorization as defined in TS 33.501 [29].	5.2.7.4

7.2.7 AUSF Services

The following NF services are specified for AUSF:

Table 7.2.7-1: NF Services provided by AUSF

Service Name	Description	Reference in TS 23.502 [3]
Nausf UEauthentication	The AUSF provides UE authentication service to requester NF. For AKA based authentication, this operation can also be used to recover from security context synchronization failure situations.	5.2.10.2
Nausf_SoRProtection	The AUSF provides protection of Steering of Roaming information service to the requester NF.	5.2.10.3

7.2.8 NEF Services

The following NF services are specified for NEF:

Table 7.2.8-1: NF Services provided by NEF

Service Name	Description	Reference in TS 23.502 [3] or other TS
Nnef_EventExposure	Provides support for event exposure.	5.2.6.2
Nnef_PFDManagement	Provides support for PFDs management.	5.2.6.3
Nnef_ParameterProvision	Provides support to provision information which can be used for the UE in 5GS.	5.2.6.4
Nnef_Trigger	Provides support for device triggering.	5.2.6.5
Nnef_BDTPNegotiation	Provides support for background data transfer policy negotiation and optionally notification for the renegotiation.	5.2.6.6
Nnef_TrafficInfluence	Provide the ability to influence traffic routing.	5.2.6.7
Nnef_ChargeableParty	Requests to become the chargeable party for a data session for a UE.	5.2.6.8
Nnef_AFsessionWithQoS	Requests the network to provide a specific QoS for an AS session.	5.2.6.9
Nnef_MSISDN-less_MO_SMS	Used by the NEF to send MSISDN-less MO SM to the AF.	5.2.6.10
Nnef_ServiceParameter	Provides support to provision service specific information.	5.2.6.11
Nnef_APISupportCapability	Provides support for awareness on availability or expected level of a service API.	5.2.6.12
Nnef_NIDDConfiguration	Used for configuring necessary information for data delivery via the NIDD API.	5.2.6.13
Nnef_NIDD	Used for NEF anchored MO and MT unstructured data transport.	5.2.6.14
Nnef_SMContext	Provides the capability to create, update or release the SMF-NEF Connection.	5.2.6.15
Nnef_AnalyticsExposure	Provides support for exposure of network analytics.	5.2.6.16
Nnef_UCMFProvisioning	Provides the ability to configure the UCMF with dictionary entries consisting of UE manufacturer-assigned UE Radio Capability IDs, the corresponding UE radio capabilities, the corresponding UE Radio Capability for Paging and the (list of) associated IMEI/TAC value(s) via the NEF. The UE radio capabilities the NEF provides for a UE radio Capability ID can be in TS 36.331 [51] format, TS 38.331 [28] format or both formats. Also used for deletion (e.g. as no longer used) or update (e.g. to add or remove a (list of) IMEI/TAC value(s) associated to an entry) of dictionary entries in the UCMF.	5.2.6.17
Nnef_ECRestriction	Provides support for queuing status of enhanced coverage restriction, or enable/disable enhanced coverage restriction per individual UEs.	5.2.6.18
Nnef_ApplyPolicy	Provides the capability to apply a previously negotiated Background Data Transfer Policy to a UE or a group of UEs.	5.2.6.19
Nnef_Location	Provides the capability to deliver UE location to AF.	5.2.6.21
Nnef_AMInfluence	Provides the ability to influence access and mobility management related policies for one or multiple UEs.	5.2.6.22
Nnef_AMPolicyAuthorization	Provides the ability to provide inputs that can be used by the PCF for deciding access and mobility management related policies.	5.2.6.23
Nnef_AKMA	AKMA Application Key derivation service.	TS 33.535 [124]
Nnef_Authentication	This service enables the consumer to authenticate and authorize the Service Level Device Identity as described in TS 23.256 [136].	TS 23.256 [136]
Nnef_TimeSynchronization	Provides the ability to support for (g)PTP or 5G access stratum based time synchronization service.	5.2.6.25
Nnef_EASDeployment	EAS deployment service.	5.2.6.26
Nnef_UEId	UE Identifier service, which supports to retrieve AF specific UE Identifier based on UE address.	5.2.6.27
Nnef_MBSTMGI	Allows AF to request allocation/deallocation of TMGI(s) for MBS Session.	TS 23.247 [129]
Nnef_MBSSession	Allows AF to create, update and delete MBS Session.	TS 23.247 [129]
Nnef_ASTI	Provides the ability to influence 5G access stratum based time distribution configuration.	5.2.6.28
Nnef_SMService	Used for SBI-based MO SM transmit through NEF for MSISDN-less MO SMS.	5.2.6.29
Nnef_PDTQPolicyNegotiation	Provides support for negotiation for Planned Data Transfer with QoS requirements policy and optionally notification for the renegotiation.	5.2.6.30

7.2.8A Void

7.2.9 SMSF Services

The following NF services are specified for SMSF:

Table 7.2.9-1: NF Services provided by SMSF

Service Name	Description	Reference in TS 23.502 [3]
Nsmsf_SMService	This service allows AMF to authorize SMS and activate SMS for the served user on SMSF. Additionally, this service allows downlink SMS message transmit from consumer NF to SMSF.	5.2.9.2

7.2.10 UDR Services

The following NF services are specified for UDR:

Table 7.2.10-1: NF Services provided by UDR

Service Name	Description	Reference in TS 23.502 [3]
Nudr_DM	Allows NF consumers to retrieve, create, update, subscribe for change notifications, unsubscribe for change notifications and delete data stored in the UDR, based on the set of data applicable to the consumer. This service may also be used to manage operator specific data.	5.2.12.2
Nudr_GroupIDmap	Allows NF consumers to retrieve a NF group ID corresponding to a subscriber identifier.	5.2.12.9

7.2.11 5G-EIR Services

The following NF services are specified for 5G-EIR:

Table 7.2.11-1: NF Services provided by 5G-EIR

Service Name	Description	Reference in TS 23.502 [3]
N5g-eir_Equipment Identity Check	This service enables the 5G-EIR to check the PEI and check whether the PEI is in the prohibited list or not.	5.2.4.2

7.2.12 NWDAF Services

The following NF services are specified for NWDAF:

Table 7.2.12-1: NF Services provided by NWDAF

Service Name	Description	Reference in TS 23.288 [86]
Nnwdaf_AnalyticsSubscription	This service enables the NF service consumers to subscribe/unsubscribe for different type of analytics from NWDAF.	7.2
Nnwdaf_AnalyticsInfo	This service enables the NF service consumers to request and get different type of analytics information from NWDAF or enables NWDAF to request transfer of analytics context from another NWDAF.	7.3
Nnwdaf_DataManagement	This service enables the NF service consumer to subscribe/unsubscribe and fetch data from NWDAF.	7.4
Nnwdaf_MLModelProvision	This service enables the consumer to receive a notification when an ML model matching the subscription parameters becomes available in NWDAF containing MTLF.	7.5
Nnwdaf_MLModelInfo	This service enables the consumer to request and get ML Model Information from NWDAF containing MTLF.	7.6

7.2.13 UDSF Services

The following NF services are specified for UDSF:

Table 7.2.13-1: NF Services provided by UDSF

Service Name	Description	Reference in TS 23.502 [3]
Nudsf_UnstructuredDataManagement	Allows NF consumers to retrieve, create, update, and delete data stored in the UDSF.	5.2.14.2
Nudsf_Timer	Allows NF consumers to start, stop, update, and search timers in UDSF. NF consumers may be notified about timer expiry.	5.2.14.3

7.2.14 NSSF Services

The following NF services are specified for NSSF:

Table 7.2.14-1: NF Services provided by NSSF

Service Name	Description	Reference in TS 23.502 [3]
Nnssf_NSSelection	Provides the requested Network Slice information to the Requester.	5.2.16.2
Nnssf_NSSAIAvailability	Provides NF consumer on the availability of S-NSSAIs on a per TA basis.	5.2.16.3

7.2.15 BSF Services

The following NF services are specified for BSF as described in TS 23.503 [45]:

Table 7.2.15-1: NF Services provided by BSF

Service Name	Description	Reference in TS 23.502 [3]
Nbsf_Management	Allows a PCF to register/deregister itself and to be discoverable by NF service consumers (NOTE 1).	5.2.13.2
NOTE 1: There may be both PCF for a PDU Session and PCF for a UE. Each of them may separately and independently register itself at the BSF. Each of them may separately and independently be discovered by a consumer of the BSF.

7.2.16 LMF Services

The following NF services are specified for LMF:

Table 7.2.16-1: NF Services provided by LMF

Service Name	Description	Reference in TS 23.273 [87]
Nlmf_Location	This service enables an NF to request location determination for a target UE for the Immediate Location Request and to subscribe / get notified of the location determination for a Deferred Location Request. It allow NFs to request or subscribe the current geodetic and optionally civic location of a target UE.	8.3

7.2.16A GMLC Services

The following NF services are specified for GMLC:

Table 7.2.16A-1: NF Services provided by GMLC

Service Name	Description	Reference in TS 23.273 [87]
Ngmlc_Location	This service enables an NF to request location determination for a target UE.	8.4

7.2.17 CHF Services

The following NF services for spending limits and charging are specified for CHF.

Table 7.2.17-1: NF Services provided by CHF

Service Name	Description	Reference in TS 23.502 [3]
Nchf_SpendingLimitControl	This service enables transfer of policy counter status information relating to subscriber spending limits from CHF to NF consumer and described in TS 23.503 [45].	5.2.17
Nchf_Converged_Charging	This service enables converged online and offline charging, as described in TS 32.290 [67].	–
Nchf_OfflineOnlyCharging	This service enables only offline charging, as described in TS 32.290 [67].	–

7.2.18 UCMF Services

The following NF services are specified for UCMF:

Table 7.2.18-1: NF Services provided by UCMF

Service Name	Description	Reference in TS 23.502 [3]
Nucmf_Provisioning	Allows the NF consumer to provision a dictionary entry in the UCMF consisting of a Manufacturer-assigned UE Radio Capability ID, the corresponding UE Radio Capability for Paging and the corresponding UE radio capabilities and the (list of) associated IMEI/TAC value(s). The UE radio capabilities the NEF provides for a UE radio Capability ID can be in TS 36.331 [51] format, TS 38.331 [28] format or both formats. Also used for deletion (e.g. as no longer used) or update (e.g. to add or remove a (list of) IMEI/TAC value(s) associated to an entry) of dictionary entries in the UCMF.	5.2.18.2
Nucmf_UECapabilityManagement	Allows the NF consumer to resolve UE Radio Capability ID (either Manufacturer-assigned or PLMN-assigned) into the corresponding UE radio capabilities and the corresponding UE Radio Capability for Paging. The consumer shall indicate whether it requests a TS 36.331 [51] format or a TS 38.331 [28] format to be provided. Allows the NF consumer to obtain a PLMN-assigned UE Radio Capability ID for a specific UE radio capabilities. The consumer shall indicate whether the UE radio capabilities sent to UCMF are in TS 36.331 [51] format, TS 38.331 [28], or both. Allows the NF consumer to subscribe or unsubscribe for notifications of UCMF dictionary entries. Allows the NF consumer to be notified about creation and deletion of UCMF dictionary entries.	5.2.18.3

7.2.19 AF Services

The following NF services are specified for AF:

Table 7.2.19-1: NF Services provided by AF

Service Name	Description	Reference in TS 23.502 [3] or other TS
Naf_EventExposure	This service enables consumer NF(s) to subscribe or get notified of the event as described in TS 23.288 [86].	5.2.19.2
Naf_ProSe	This service is for ProSe services as described in TS 23.304 [128].	TS 23.304 [128]
Naf_Authentication	This service enables the consumer to authenticate and authorize the Service Level Device Identity as described in TS 23.256 [136].	TS 23.256 [136]

7.2.20 NSSAAF Services

The following NF services are specified for NSSAAF:

Table 7.2.20 -1: NF Services provided by NSSAAF

Service Name	Description	Reference in TS 23.502 [3]
Nnssaaf_NSSAA	The NSSAAF provides NSSAA service to the requester NF by relaying EAP messages towards a AAA-S or AAA-P and performing related protocol conversion as needed. It also provides notification to the current AMF where the UE is of the need to re-authenticate and re-authorize the UE or to revoke the UE authorization.	5.2.20.2
Nnssaaf_AIW	The NSSAAF provides AIW (AAA interworking) service to the requester NF by relaying EAP messages towards a AAA-S or AAA-P and performing related protocol conversion as needed.	5.2.20.3

7.2.21 DCCF Services

The following NF services are specified for DCCF:

Table 7.2.21-1: NF Services provided by DCCF

Service Name	Description	Reference in TS 23.288 [86]
Ndccf_DataManagement	This service enables a Data Consumer to request data, and have it delivered via a messaging framework or via the DCCF, while avoiding redundant requests to data sources.	8.2
Ndccf_ContextManagement	This service allows a network function to register/deregister the availability of data with the DCCF.	8.3

7.2.22 MFAF Services

The following NF services are specified for MFAF:

Table 7.2.22-1: NF Services provided by MFAF

Service Name	Description	Reference in TS 23.288 [86]
Nmfaf_3daDataManagement	This service allows a DCCF to request a messaging framework to provide collected data to consumers or notification endpoints according to processing and formatting instructions.	9.2
Nmfaf_3caDataManagement	This service allows a messaging framework to provide data to consumers or notification endpoints according to instructions received via the Nmfaf_3da_DataManagement service.	9.3

7.2.23 ADRF Services

The following NF services are specified for ADRF:

Table 7.2.23-1: NF Services provided by ADRF

Service Name	Description	Reference in TS 23.288 [86]
Nadrf_DataManagement	This service allows consumers to store, retrieve and delete data or analytics in an ADRF.	10.2

7.2.24 5G DDNMF Services

The 5G DDNMF supports the N5g-ddnmf service defined in clause 7.1 of TS 23.304 [128].

7.2.25 EASDF Services

The following NF services are specified for EASDF.

Table 7.2.25-1: NF Services provided by EASDF

Service Name	Description	Reference in TS 23.548 [130]
Neasdf_DNSContext	This service enables the consumer to create, update and delete DNS context in EASDF, or subscribe to DNS message reporting from EASDF. DNS contexts in EASDF include rules on how EASDF is to handle DNS messages.	7.1.2
Neasdf_BaselineDNSPattern	This service enables the consumer to create, update and delete BaselineDNSPattern in EASDF.	7.1.3

7.2.26 TSCTSF Services

The following NF services are specified for TSCTSF.

Table 7.2.26-1: NF Services provided by TSCTSF

Service Name	Description	Reference in TS 23.502 [3]
Ntsctsf_TimeSynchronization	Provides support for time synchronization service based on (g)PTP or 5G access stratum time distribution method as described in clause 5.27.1.8. Allows the NF consumer to subscribe for the UE and 5GC capabilities for (g)PTP or 5G access stratum based time synchronization service. Allows the NF consumer to configure the UEs and the 5GC for the (g)PTP based time synchronization service.	5.2.27.2
Ntsctsf_QoSand TSCAssistance	Allows the NF consumer to provide QoS parameters and information to create TSC Assistance Container.	5.2.27.3
Ntsctsf_ASTI	Provides support for time synchronization service based on 5G access stratum time distribution method as described in clause 5.27.1.8. Allows the NF consumer to configure the 5GC and RAN for 5G access stratum based time synchronization service for the UEs.	5.2.27.4

7.2.27 NSACF Services

The following NF services are specified for NSACF:

Table 7.2.27-1: NF Services provided by NSACF

Service Name	Description	Reference in TS 23.502 [3]
Nnsacf_NSAC	This service enables consumer NF to check the availability per network slice and update the number of UEs registered with a network slice or the number of PDU Sessions established on a network slice.	5.2.21.2
Nnsacf_SliceEventExposure	This service enables consumer NF(s) to subscribe and get notified of the event as described in clause 5.15.11.4.	5.2.21.4

7.2.28 MB-SMF Services

The following NF service is specified for MB-SMF.

Table 7.2.28-1: NF Services provided by MB-SMF

Service Name	Description	Reference in TS 23.247 [129]
Nmbsmf_TMGI	This service enables NF service consumer to allocate, refresh and deallocate TMGI(s).	9.1.2
Nmbsmf_MBSSession	This service enables the consumer to create, update and delete the MBS Session.	9.1.3

7.2.29 UPF Services

The following NF service is specified for UPF.

Table 7.2.29-1: NF Services provided by UPF

Service Name	Description	Reference in TS 23.502 [3]
Nupf_EventExposure	This service exposes UPF related information to the consumer NFs.	5.2.26.2

7.3 Exposure

Network exposure is described in clause 5.20 and in clause 4.15 of TS 23.502 [3].