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.12  UDR Services
5.2.12.1  General
The following Data Set Identifiers shall be considered in this release: Subscription Data, Policy Data, Application data and Data for Exposure. The corresponding Data Subset Identifiers and Data (Sub)Key(s) are defined in Table 5.2.12.2.1-1.
The set of Data Set Identifiers shall be extensible to cater for new identifiers as well as for operator specific identifiers and related data to be consumed.
The following table illustrates the UDR Services.
NF service
Service Operations
Operation Semantics
Example Consumer(s)

Data Management (DM)
Query
Request/Response
UDM, PCF, NEF
Create
Request/Response
NEF
Delete
Request/Response
NEF
Update
Request/Response
UDM, PCF, NEF
Subscribe
Subscribe/Notify
UDM, PCF, NEF
Unsubscribe
Subscribe/Notify
UDM, PCF, NEF
Notify
Subscribe/Notify
UDM, PCF, NEF
GroupIDmap
Query
Request/Response
NRF, SCP

The following table shows the Exposure data that may be stored in the UDR along with a time stamp using Data Management (DM) Service:
NOTE:
When the data in Table 5.2.12.1-2 need to be monitored in real time, they should be monitored directly at the originating NF (e.g. registration state changes may be monitored via the Namf_EventExposure service) and not use the stored information from UDR if it is not the latest. It is expected that such dynamically changing information (e.g. UE reachability status) is used for statistical purpose and analytics.
Category
Information
Description
Data key
Data Sub key

Access and mobility information
UE location
Gives the Location or the last known location of a UE (e.g. Tai, Cell Id… both 3GPP and non-3GPP access location)
SUPI or GPSI
UE time zone
Current time zone for the UE
SUPI or GPSI
UE Access type
3GPP access or non-3GPP access
SUPI or GPSI
UE RAT type
Determined as defined in TS 23.501, clause 5.3.2.3.
The values are defined in TS 29.571
SUPI or GPSI
UE registration state
Registered or Deregistered
SUPI or GPSI
UE connectivity state
IDLE or CONNECTED
SUPI or GPSI
UE reachability status
It indicates if the UE is reachable for sending either SMS or downlink data to the UE, which is detected when the UE transitions to CM-CONNECTED state or when the UE will become reachable for paging, e.g., Periodic Registration Update timer
SUPI or GPSI
UE SMS over NAS service status
SMS over NAS supported or not in the UE
SUPI or GPSI
UE Roaming status
It indicates UE's current roaming status (the serving PLMN and/or whether the UE is in its HPLMN)
SUPI or GPSI
UE Current PLMN
Current PLMN for the UE
SUPI or GPSI
Session management information
UE IP address
UE IP address
SUPI or GPSI
PDU session ID or DNN
PDU session status
Active / released
SUPI or GPSI
PDU session ID or DNN or UE IP address
DNAI
DNAI
SUPI or GPSI
PDU session ID or DNN or UE IP address
N6 traffic routing information
N6 traffic routing information
SUPI or GPSI
PDU session ID or DNN or UE IP address

Up
5.2.12.2  Nudr_DataManagement (DM) serviceWord-p. 525
5.2.12.2.1  General
The operations defined for Nudr_DM service use following set of parameters defined in this clause:
  • Data Set Identifier:. uniquely identifies the requested set of data within the UDR (see clause 4.2.5).
  • Data Subset Identifier: it uniquely identifies the data subset within each Data Set Identifier. As specified in the procedures in clause 4. e.g. subscription data can consist of subsets particularised for specific procedures like mobility, session, etc.
  • Data Keys defined in Table 5.2.12.2.1-1
For Nudr_DM_Subscribe and Nudr_DM_Notify operations:
  • The Target of Event Reporting is made up of a Data Key and possibly a Data Sub Key both defined in Table 5.2.12.2.1-1. When a Data Sub Key is defined in the table but not present in the Nudr_DM_Subscribe this means that all values of the Data Sub Key are targeted.
  • The Data Set Identifier plus (if present) the (set of) Data Subset Identifier(s) corresponds to a (set of) Event ID(s) as defined in clause 4.15.1
An NF Service Consumer may include an indicator when it invokes Nudr_DM Query/Create/Update service operation to subscribe the changes of the data, to avoid a separate Nudr_DM_Subscribe service operation.
Depending on the use case, it is possible to use a Data Key and/or one or multiple Data sub keys to further identify the corresponding data, as defined in Table 5.2.12.2.1-1 below.
Data Set
Data Subset
Data Key
Data Sub Key

Subscription Data (see clause 5.2.3.3.1)
Access and Mobility Subscription data
SUPI
Serving PLMN ID and optionally NID
SMF Selection Subscription data
SUPI
Serving PLMN ID and optionally NID
UE context in SMF data
SUPI
PDU Session ID or DNN
SMS Management Subscription data
SUPI
Serving PLMN ID and optionally NID
SMS Subscription data
SUPI
Serving PLMN ID and optionally NID
Session Management Subscription data
SUPI
S-NSSAI
DNN
Serving PLMN ID and optionally NID
Slice Selection Subscription data
SUPI
Serving PLMN ID and optionally NID
Group Data
Internal Group Identifier or External Group Identifier
Identifier translation
GPSI
SUPI
Application Port ID
Intersystem continuity Context
SUPI
DNN
LCS privacy
SUPI
LCS mobile origination
SUPI
UE reachability
SUPI
Group Identifier Translation
Internal Group Identifier or External Group Identifier
UE Context in AMF data
SUPI
UE context in SMSF data
SUPI

Application data
Packet Flow Descriptions (PFDs)
Application ID
AF traffic influence request information (See clause 5.6.7 and clause 6.3.7.2 in TS 23.501).
AF transaction internal ID
S-NSSAI and DNN and/or Internal Group Identifier or SUPI
Background Data Transfer
Internal Group Identifier or SUPI (NOTE 3)
Service specific information (See clause 4.15.6.7)
S-NSSAI and DNN or Internal Group Identifier or SUPI

Policy Data
UE context policy control data (See clause 6.2.1.3 in TS 23.503)
SUPI
PDU Session policy control data
SUPI (See clause 6.2.1.3 in TS 23.503)
S-NSSAI
DNN
Policy Set Entry data (See clause 6.2.1.3 in TS 23.503)
SUPI (for the UDR in HPLMN)
PLMN ID (for the UDR in VPLMN)
Remaining allowed Usage data (See clause 6.2.1.3 in TS 23.503)
SUPI
S-NSSAI
DNN
Sponsored data connectivity profiles (See clause 6.2.1.6 in TS 23.503)
Sponsor Identity
Background Data Transfer data (See clause 6.2.1.6 in TS 23.503)
Background Data Transfer Reference ID. (NOTE 2)
None. (NOTE 1)

Exposure Data (see clause 5.2.12.1)
Access and Mobility Information
SUPI or GPSI
PDU Session ID or UE IP address or DNN
Session Management information
SUPI or GPSI
PDU Session ID or UE IP address or DNN

NOTE 1:
Retrieval of the stored Background Data Transfer References for all ASP identifiers in the UDR requires Data Subset but no Data Key or Data Subkey(s).
NOTE 2:
Update of a Background Data Transfer Reference in the UDR requires a Data key to refer to a Background Data Transfer Reference as input data.
NOTE 3:
The Background Data Transfer includes the Background Data Reference ID and the ASP id that requests to apply the the Background Data Reference ID to the UE(s).

The content of the UDR storage for (Data Set Id= Application Data, Data Subset Id = AF TrafficInfluence request information) is specified in TS 23.501, clause 5.6.7, Table 5.6.7-1. This information is written by the NEF and read by the PCF(s). PCF(s) may also subscribe to changes onto this information.
Up
5.2.12.2.2  Nudr_DM_Query service operationWord-p. 529
Service operation name:
Nudr_DM_Query.
Description:
NF service consumer requests a set of data from UDR.
Inputs, Required:
Data Set Identifier, Data Key(s).
Inputs, Optional:
Data Subset Identifier(s), Data Sub Key(s) (for each Data Subset, see clause 5.2.12.2.1).
Outputs, Required:
Requested data.
Outputs, Optional:
None.
5.2.12.2.3  Nudr_DM_Create service operation
Service operation name:
Nudr_DM_Create.
Description:
NF service consumer intends to insert a new data record into the UDR, e.g. a NF service consumer intends to insert a new application data record into the UDR.
Inputs, Required:
Data Set Identifier, Data Key(s).
Inputs, Optional:
Data Subset Identifier(s), Data Sub Key(s) (for each Data Subset, see clause 5.2.12.2.1).
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.12.2.4  Nudr_DM_Delete service operation
Service operation name:
Nudr_DM_Delete.
Description:
NF service consumer intends to delete user data stored in the UDR, e.g. a NF service consumer intends to delete an application data record.
Inputs, Required:
Data Set Identifier, Data Key(s).
Inputs, Optional:
Data Subset Identifier(s), Data Sub Key(s) (for each Data Subset, see clause 5.2.12.2.1).
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.12.2.5  Nudr_DM_Update service operation
Service operation name:
Nudr_DM_Update.
Description:
NF service consumer intends to update stored data in the UDR.
Inputs, Required:
Data Set Identifier, Data Key(s), Data.
Inputs, Optional:
Data Subset Identifier(s), Data Sub Key(s) (for each Data Subset, see clause 5.2.12.2.1).
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.12.2.6  Nudr_DM_Subscribe service operationWord-p. 530
Service operation name:
Nudr_DM_Subscribe.
Description:
NF service consumer performs the subscription to notification to data modified in the UDR. The events can be changes on existing data, addition of data.
Inputs, Required:
Data Set Identifier as defined in clause 5.2.12.2.1, Notification Target Address (+ Notification Correlation ID), Event Reporting Information defined in Table 4.15.1-1.
Inputs, Optional:
Target of Event Reporting as defined in clause 5.2.12.2.1, Data Subset Identifier(s) as defined in clause 5.2.12.2.1, Data Key(s), Subscription Correlation ID (in the case of modification of the event subscription).
Outputs, Required:
When the subscription is accepted: Subscription Correlation ID.
Outputs, Optional:
None.
5.2.12.2.7  Nudr_DM_Unsubscribe service operation
Service operation name:
Nudr_DM_Unsubscribe
Description:
NF service consumer performs the un-subscription to notification to data modified in the UDR. The events can be changes on existing data, addition of data.
Inputs, Required:
Subscription Correlation ID.
Inputs, Optional:
None.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.12.2.8  Nudr_DM_Notify service operation
Service operation name:
Nudr_DM_Notify.
Description:
UDR notifies NF service consumer(s) about modification of data, when data in the UDR is added, modified or deleted, and an NF needs to be informed about this, due to a previous subscription to notifications procedure or due to a local configuration policy in the UDR.
Inputs, Required:
Notification Correlation Information, Data Set Identifier as defined in clause 5.2.12.2.1, Target of Event Reporting as defined in clause 5.2.12.2, Updated Data.
Inputs, Optional:
Data Subset Identifier as defined in clause 5.2.12.2.1.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.12.3  Nudr_GroupIDmap service [R16]
5.2.12.3.1  General
The Nudr_GroupIDmap service allows an NF consumer to retrieve a NF group ID corresponding to a subscriber identifier.
5.2.12.3.2  Nudr_GroupIDmap_query service operationWord-p. 531
Service operation name:
Nudr_GroupIDmap_query
Description:
Provides towards the invoking NF the NF Group ID corresponding to the supplied subscriber identifier.
Inputs, Required:
  • NF Type (e.g. HSS).
  • Subscriber Identifier.
  • Subscriber Identifier Type (at least one of {IMPI, IMPU, SUPI, GPSI}).
Inputs, Optional:
None.
Outputs, Required:
NF Group ID.
Outputs, Optional:
None.
5.2.13  BSF Services
5.2.13.1  General
The following table shows the BSF Services and Service Operations:
Service Name
Service Operations
Operation Semantics
Example Consumer(s)

Nbsf_management
Register
Request/Response
PCF
Deregister
Request/Response
PCF
Discovery
Request/Response
NEF, AF, NWDAF
Update
Request/Response
PCF

5.2.13.2  Nbsf_Management service
5.2.13.2.1  General
The Nbsf provides the Nbsf Management Register, Nbsf Management Remove and the Nbsf Management Discovery service operations.
5.2.13.2.2  Nbsf_Management_Register service operation
Service operation name:
Nbsf_Management_Register
Description:
Registers the tuple (UE address(es), SUPI, GPSI, DNN, S-NSSAI, PCF address(es), PCF instance id, PCF Set ID) for a PDU Session.
Inputs, Required:
UE address(es), PCF address(es).
UE address can contain IP address/prefix or MAC address as defined in TS 23.501. It can optionally refer to Frame Routes. W-5GAN specific UE IP address information is specified in TS 23.316.
Frame Routes are defined in Table 5.2.3.3.1-1.
Inputs, Optional:
DNN, SUPI, GPSI, S-NSSAI, PCF instance ID and PCF Set ID, level of Binding (see clause 6.3.1.0 of TS 23.501).
Outputs, Required:
Result indication, Binding Identifier for a PDU Session.
Outputs, Optional:
None.
Up
5.2.13.2.3  Nbsf_Management_Deregister service operationWord-p. 532
Service operation name:
Nbsf_Management_Deregister
Description:
Removes the binding information for a PDU Session.
Inputs, Required:
Binding Identifier for a PDU Session.
W-5GAN specific UE IP address information are specified in TS 23.316.
Inputs, Optional:
Outputs, Required:
Result indication.
Outputs, Optional:
None.
5.2.13.2.4  Nbsf_Management_Discovery service operation
Service operation name:
Nbsf_Management discovery
Description:
Discovers the PCF and PCF set selected for the tuple (UE address(es), SUPI, GPSI, DNN, S-NSSAI).
Inputs, Required:
UE address (i.e. IP address or MAC address), DNN [Conditional], S-NSSAI [Conditional].
Inputs, Optional:
SUPI, GPSI.
Outputs, Required:
PCF address(es), PCF instance ID [Conditional, if available] and PCF Set ID [Conditional, if available], level of Binding [Conditional, if available] (see clause 6.3.1.0 of TS 23.501).
Outputs, Optional:
None.
5.2.13.2.5  Nbsf_Management_Update service operation [R16]
Service operation name:
Nbsf_Management_Update
Description:
Replaces the list of UE address(es) for a PDU Session.
Inputs, Required:
Binding Identifier for the PDU Session.
UE address can contain IP address/prefix or Ethernet address as defined in TS 23.501.
Inputs, Optional:
UE address(es), PCF id.
Outputs, Required:
Result indication.
Outputs, Optional:
None.
5.2.14  UDSF Services
5.2.14.1  General
The following table illustrates the UDSF Services.
NF service
Service Operations
Operation Semantics
Example Consumer(s)

Unstructured
Query
Request/Response
Any NF
Data
Create
Request/Response
Any NF
Management
Delete
Request/Response
Any NF
Update
Request/Response
Any NF

NOTE:
Nudsf is different compared to other service-based interfaces due to dynamic data access performance requirements.
5.2.14.2  Nudsf_UnstructuredDataManagement serviceWord-p. 533
5.2.14.2.1  General
5.2.14.2.2  Nudsf_UnstructuredDataManagement_Query service operation
Service operation name:
Nudsf_UnstructuredDataManagement_Query.
Description:
NF service consumer intends to query data from UDSF.
Inputs, Required:
Data Identifier.
Data Identifier uniquely identifies the data to be retrieved from the UDSF
Inputs, Optional:
None.
Outputs, Required:
Requested data.
Outputs, Optional:
None.
5.2.14.2.3  Nudsf_UnstructuredDataManagement_Create service operation
Service operation name:
Nudsf_UnstructuredDataManagement_Create.
Description:
NF service consumer intends to insert a new user data record into the UDSF, e.g. AMF stores the context for registered UE(s) in the UDSF.
Inputs, Required:
Data Identifier, Data.
Data Identifier uniquely identifies the data, which is created in the UDSF.
Inputs, Optional:
None
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.14.2.4  Nudsf_UnstructuredDataManagement_Delete service operation
Service operation name:
Nudsf_UnstructuredDataManagement_Delete.
Description:
NF service consumer intends to delete user data stored in the UDSF, e.g. when AMF deletes the context for unregistered UE(s) in the UDSF.
Inputs, Required:
Data Identifier.
Inputs, Optional:
None.
Data Identifier uniquely identifies the data to be deleted within the UDSF.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.14.2.5  Nudsf_UnstructuredDataManagement_Update service operation
Service operation name:
Nudsf_UnstructuredDataManagement_Update.
Description:
NF service consumer intends to update stored data in the UDSF.
Inputs, Required:
Data Identifier, Data.
Data Identifier uniquely identifies the data, which is updated in the UDSF.
Inputs, Optional:
None.
Outputs, Required:
Result.
Outputs, Optional:
None.
5.2.15  LMF ServicesWord-p. 534
LMF services are defined in clause 8.3 of TS 23.273.
5.2.16  NSSF Services
5.2.16.1  General
The following table illustrates the NSSF Services.
Service Name
Service Operations
Operation Semantics
Example Consumer(s)

Nnssf_NSSelection
Get
Request/Response
AMF, NSSF in a different PLMN, SMF
Nnssf_NSSAIAvailability
Update
Request/Response
AMF
Subscribe
Subscribe/Notify
AMF
Unsubscribe
AMF
Notify
AMF
Delete
Request/Response
AMF

NOTE:
The SMF uses the Nnssf_NSSelection_Get service operation during EPS interworking.
5.2.16.2  Nnssf_NSSelection service
5.2.16.2.1  Nnssf_NSSelection_Get service operation
Service operation name:
Nnssf_NSSelection_Get
Description:
This service operation enables Network Slice selection in both the Serving PLMN and HPLMN. It also enables the NSSF to provide to the AMF the Allowed NSSAI and the Configured NSSAI for the Serving PLMN.
It may be invoked during Registration procedure, during inter-PLMN mobility procedure, during PDU Session Establishment procedure or during UE Configuration Update procedure. When invoked during Registration procedure it may possibly trigger AMF re-allocation. When invoked during PDU Session Establishment procedure it may be invoked in the VPLMN or in the HPLMN. When invoked during UE Configuration Update procedure or inter-PLMN mobility procedure it may be invoked in the Serving PLMN.
NOTE 1:
The list of events, which trigger invoking of the Nnssf_NSSelection_Get service operation, is not exhaustive.
Inputs, Required:
None.
Inputs, Conditional Required:
If this service operation is invoked during Registration procedure for Network Slice selection or UE Configuration Update procedure, then the following inputs are required:
  • Subscribed S-NSSAI(s) with the indication if marked as default S-NSSAI, PLMN ID of the SUPI, TAI, NF type of the NF service consumer, Requester ID.
If this service operation is invoked to derive the S-NSSAI for the serving PLMN (as described in clause 4.11.1.3.3), the following inputs are required:
  • S-NSSAIs for the HPLMN associated with established PDN connection, PLMN ID of the SUPI, NF type of the NF service consumer, Requester ID.
If this service operation is invoked by target AMF during inter-PLMN mobility procedure, the following inputs are required:
  • S-NSSAIs for the HPLMN, PLMN ID of the SUPI, TAI.
If this service operation is invoked during PDN Connection Establishment in the Serving PLMN in EPS by a PGW-C+SMF, the following inputs are required:
  • Subscribed S-NSSAIs for the UE, PLMN ID of the SUPI, NF type of the NF service consumer, Requester ID.
If this service operation is invoked during PDU Session Establishment procedure in the Serving PLMN then the following inputs are required:
  • S-NSSAI, non-roaming/LBO roaming/HR roaming indication, PLMN ID of the SUPI, TAI, NF type of the NF service consumer, Requester ID.
Inputs, Optional:
If this service operation is invoked during Registration procedure for Network Slice selection or UE Configuration Update procedure, then the following inputs are provided if available:
  • Requested NSSAI, Mapping Of Requested NSSAI, Default Configured NSSAI Indication, Allowed NSSAI for current Access Type, Allowed NSSAI for the other Access Type, and the corresponding Mapping Of Allowed NSSAIs for current Access Type and other Access Type.
If this service operation is invoked during PDU Session Establishment procedure, then the following input is optional:
  • HPLMN S-NSSAI that maps to the S-NSSAI from the Allowed NSSAI of the Serving PLMN.
Outputs, Conditional Required:
If this service operation is invoked during Registration procedure for Network Slice selection or UE Configuration Update procedure, then one or more of the following outputs are required:
  • Allowed NSSAI, Configured NSSAI; Target AMF Set or, based on configuration, the list of candidate AMF(s).
If this service operation is invoked during inter-PLMN mobility procedure, then one or more of the following outputs are required:
  • Allowed NSSAI.
If this service operation is invoked to derive the S-NSSAI for the serving PLMN (as described in clause 4.11.1.3.3), the following output is required:
  • S-NSSAIs for the HPLMN associated with established PDN connection, Mapping of S-NSSAIs associated with established PDN connection in the Serving PLMN.
If this service operation is invoked during PDN Connection Establishment in the Serving PLMN in EPS by a PGW-C+SMF, the following outputs are required:
  • Subscribed S-NSSAIs for the UE, Mapping of S-NSSAIs associated with the subscribed S-NSSAIs for the UE in the Serving PLMN.
If this service operation is invoked during PDU Session Establishment procedure then the following outputs are required:
  • The NRF to be used to select NFs/services within the selected Network Slice instance.
Outputs, conditional Optional:
If this service operation is invoked during UE Registration procedure or UE Configuration Update procedure, then one or more of the following outputs are optional:
  • Mapping Of Allowed NSSAI, Mapping Of Configured NSSAI, NSI ID(s) associated with the Network Slice instances of the Allowed NSSAI, NRF(s) to be used to select NFs/services within the selected Network Slice instance(s) and NRF to be used to determine the list of candidate AMF(s) from the AMF Set, rejected S-NSSAI with cause of rejection.
If this service operation is invoked during inter-PLMN mobility procedure, then the following output is optional:
  • Mapping Of Allowed NSSAI.
If this service operation is invoked during PDU Session Establishment procedure, then the following output is optional:
  • NSI ID associated with the S-NSSAI provided in the input.
Up
5.2.16.3  Nnssf_NSSAIAvailability serviceWord-p. 536
5.2.16.3.1  General
Service description: This service enables to update the AMFs and the NSSF on the availability of S-NSSAIs on a per TA basis.
5.2.16.3.2  Nnssf_NSSAIAvailability_Update service operation
Service operation name:
Nnssf_NSSAIAvailability_Update
Description:
This service operation enables the AMF to update the NSSF with the S-NSSAIs the AMF supports per TA, and get the availability of the S-NSSAIs per TA for the S-NSSAIs the AMF supports.
Inputs, Required:
Supported S-NSSAIs per TAI.
The supported S-NSSAIs per TAI, is a list of TAIs and for each TAI the S-NSSAIs supported by the AMF.
Inputs, Optional:
None.
Outputs, Required:
A list of TAIs and, for each TAI, the S-NSSAIs supported by the AMF and 5G-AN, and authorized by the NSSF for the TAI.
Outputs, Optional:
For each TAI, a list of S-NSSAIs restricted per PLMN for the TAI.
Up
5.2.16.3.3  Nnssf_NSSAIAvailability_Notify service operation
Service operation name:
Nnssf_NSSAIAvailability_Notify
Description:
This service operation enables the NSSF to update the AMF with any S-NSSAIs restricted per TA and, if needed, subsequently lift any restriction per TA.
Inputs, Required:
SubscriptionId, a list of TAIs and the S-NSSAIs for which the status is changed (restricted/unrestricted) per each TAI.
Inputs, Optional:
None.
Outputs, Required:
None.
Outputs, Optional:
None.
5.2.16.3.4  Nnssf_NSSAIAvailability_Subscribe service operation
Service operation name:
Nnssf_NSSAIAvailability_Subscribe
Description:
This service operation enables a NF Service Consumer (e.g. AMF) to subscribe to a notification of any changes in status of the NSSAI availability information (e.g. S-NSSAIs available per TA and the restricted S-NSSAI(s) per PLMN in that TA in the serving PLMN of the UE) upon this is updated by another AMF.
Inputs, Required:
Callback URI of the NF Service Consumer, list of TAIs supported by the NF service consumer, event to be subscribed.
Inputs, Optional:
Expiry time.
Outputs, Required:
SubscriptionID,
Outputs, Conditional Required:
Expiry time (if present in the request, may be included in the response based on operator's policy and taking into account the expiry time present in the request (i.e. should be less than or equal to that value); if not present in the request, may be included in the response based on operator's policy. Whatever the case, if not included in the response, this means that the subscription is valid without an expiry time).
Outputs, Optional:
A list of TAIs and, for each TAI, the S-NSSAIs supported by the AMF and 5G-AN, and authorized by the NSSF for the TAI, and a list of S-NSSAIs restricted per PLMN for the TAI.
Up
5.2.16.3.5  Nnssf_NSSAIAvailability_Unsubscribe service operationWord-p. 537
Service operation name:
Nnssf_NSSAIAvailability_Unsubscribe
Description:
This service operation enables a NF Service Consumer (e.g. AMF) to unsubscribe to a notification of any previously subscribed changes to the NSSAI availability information.
Inputs, Required:
SubscriptionId.
Inputs, Optional:
None.
Outputs, Required:
None.
Outputs, Optional:
None.
5.2.16.3.6  Nnssf_NSSAIAvailability_Delete service operation
Service operation name:
Nnssf_NSSAIAvailability_Delete
Description:
This service operation enables a NF service consumer (e.g. AMF) to delete the NSSAI availability information stored for the NF service consumer in the NSSF.
Inputs, Required:
NfId.
Inputs, Optional:
None.
Outputs, Required:
None.
Outputs, Optional:
None.
5.2.17  CHF Spending Limit Control Service
5.2.17.1  General
The following table illustrates the CHF Services defined in this specification. The other services of CHF are defined in clause 6.2 of TS 32.290.
Service Name
Service Operations
Operation Semantics
Example Consumer(s)

Nchf_SpendingLimitControl
Subscribe
Subscribe/Notify
PCF
Unsubscribe
PCF
Notify
PCF

5.2.17.2  Nchf_SpendingLimitControl serviceWord-p. 538
5.2.17.2.1  General
Service description: This service enables transfer of policy counter status information relating to subscriber spending limits from CHF to the NF consumer.
5.2.17.2.2  Nchf_SpendingLimitControl Subscribe service operation
Service operation name:
Nchf_SpendingLimitControl_Subscribe
Description:
Subscribe to notification of changes in the status of the policy counters available at the CHF and retrieval of the status of the policy counters for which subscription is accepted by CHF.
Inputs, Required:
SUPI (for the Initial Spending Limit request), SubscriptionCorrelationId (for the Intermediate Spending Limit report), Event Id "policy counter status change", Event Filter Information "List of policy counter identifier (s)".
Inputs, Optional:
Notification Correlation Target (required for the Initial Spending Limit request), Event Filter Information "List of policy counter identifier (s)", Event Reporting Information (continuous reporting).
Outputs, Required:
Status of the requested subscribed policy counters to the subscriber in the Event Information.
Outputs, Optional:
Pending policy counter statuses and their activation times, for all policy counter(s) available for this subscriber. If list of policy counter identifier(s) was provided, the CHF returns only the pending policy counter statuses and their activation times, per required policy counter identifier in the Event Information, SubscriptionCorrelationId.
Up
5.2.17.2.3  Nchf_SpendingLimitControl Unsubscribe service operation
Service operation name:
Nchf_SpendingLimitControl_Unsubscribe
Description:
Cancel the subscription to status changes for all the policy counters available at the CHF.
Inputs, Required:
SubscriptionCorrelationId.
Inputs, Optional:
None.
Outputs, Required:
Success or Failure.
Outputs, Optional:
None.
5.2.17.2.4  Nchf_SpendingLimitControl Notify service operation
Service operation name:
Nchf_SpendingLimitControl_Notify
Description:
Notify the change of the status of the subscribed policy counters available at the CHF. Alternatively, it can be used by the CHF to provide one or more pending statuses for a subscribed policy counter together with the time they have to be applied. Alternatively, it is also used by the CHF to notify the removal of a subscriber from the CHF system, so that the NF consumer can terminate the subscriptions of all the policy counters of the subscriber.
Inputs, Required:
Notification Target Address, SUPI.
Inputs, Optional:
policy counter status as Event Information, Pending policy counter statuses and their activation times as Event Information. Subscriber removal from the CHF system as Event Information.
Outputs, Required:
Success or Failure.
Outputs, Optional:
None.
Up
5.2.18  UCMF Services [R16]Word-p. 539
5.2.18.1  General
The following table illustrates the UCMF Services.
Service Name
Service Operations
Operation Semantics
Example Consumer(s)

Nucmf_Provisioning
Create
Request/Response
AF, NEF
Delete
Request/Response
AF, NEF
Update
Request/Response
AF, NEF
Nucmf_UECapabilityManagement
Resolve
Request/Response
AMF
Assign
Request/Response
AMF
Subscribe
Subscribe/Notify
AMF
Unsubscribe
Subscribe/Notify
AMF
Notify
Subscribe/Notify
AMF

5.2.18.2  Nucmf_Provisioning service
5.2.18.2.1  Nucmf_Provisioning_Create service operation
Service operation name:
Nucmf_Provisioning_Create
Description:
The consumer creates a UCMF dictionary entry (or more entries) for a Manufacturer-assigned UE Radio Capability ID(s). For each UE Radio Capability ID provided, a UE radio access capability set and the related UE model(s) IMEI/TAC value(s) the UE radio capability ID applies to is provided.
Inputs (required):
(list of) [UE Radio Capability ID(s), set(s) of UE radio access capability set, (list of) Type Allocation Code(s) value(s)].
Inputs (optional):
None.
Outputs (required):
None.
Outputs (optional):
None.
5.2.18.2.2  Nucmf_Provisioning_Delete service operation
Service operation name:
Nucmf_Provisioning_Delete
Description:
The consumer deletes a UCMF dictionary entry(s) for a Manufacturer-assigned UE Radio Capability ID(s). The consumer provides a (list of) UE radio capability ID value(s) to be deleted or it may provide the IMEI/TAC values for which the associated UE radio capability ID entries shall be no longer used.
Inputs (required):
UE Radio Capability ID(s) of the UCMF dictionary entry(s) to be deleted or Type Allocation Code(s) that no longer use associated UE radio Capability ID(s).
Inputs (optional):
None.
Outputs (required):
None.
Outputs (optional):
None.
5.2.18.2.3  Nucmf_Provisioning_Update service operation
Service operation name:
Nucmf_Provisioning_Update
Description:
The consumer updates the list of IMEI/TAC values a UCMF dictionary entry (or a list of entries) applies to for a Manufacturer-assigned UE Radio Capability ID. For each UE Radio Capability ID provided, (a list of) UE model(s) IMEI/TAC value(s) to be added or removed to the related UCMF entry is provided.
Inputs (required):
Update Type (one of "Add IMEI/TAC Values" or "Remove IMEI/TAC Values") and:
  • If Update Type is "Add IMEI/TAC Values", the (list of) UE Radio Capability ID(s) of the UCMF dictionary entry(ies) to be updated and the related additional (list of) Type Allocation Code(s); or
  • If Update Type is "Remove IMEI/TAC Values", the (list of) UE Radio Capability ID(s) of the UCMF dictionary entry(ies) to be updated and the related (list of) Type Allocation Code(s) to be removed.
Inputs (optional):
None.
Outputs (required):
None.
Outputs (optional):
None.
Up
5.2.18.3  Nucmf_UECapabilityManagement ServiceWord-p. 540
5.2.18.3.1  Nucmf_UECapabilityManagement Resolve service operation
Service operation name:
Nucmf_UECapabilityManagement_Resolve
Description:
Consumer NF gets the UE Radio Access Capability corresponding to a specific UE Radio Capability ID (either Manufacturer-assigned or PLMN-assigned).
Inputs, Required:
UE Radio Capability ID.
Inputs, Optional:
None.
Outputs, Required:
UE Radio Access Capability.
Outputs, Optional:
None.
5.2.18.3.2  Nucmf_UECapabilityManagement_Assign service operation
Service or Service operation name:
Nucmf_UECapabilityManagement_Assign
Description:
The NF consumer sends the UE Radio Access Capability in the UCMF and obtains a PLMN-assigned UE Radio Capability ID in return.
Inputs, Required:
UE Radio Access Capability, Type Allocation Code.
Inputs, Optional:
None.
Outputs, Required:
UE Radio Capability ID.
Outputs, Optional:
None.
The AMF sends the UE Radio Access Capability other than NB-IoT Radio Access Capability to the UCMF.
5.2.18.3.3  Nucmf_UECapabilityManagement_Subscribe service operation
Service operation name:
Nucmf_UECapabilityManagement_Subscribe
Description:
The NF consumer subscribes for updates to UCMF dictionary entries. The UCMF shall check the requested consumer is authorized to subscribe to requested updates.
Inputs, Required:
None.
Inputs, Optional:
None.
Outputs, Required:
None.
Outputs, Optional:
None.
5.2.18.3.4  Nucmf_UECapabilityManagement_Unsubscribe service operationWord-p. 541
Service operation name:
Nucmf_UECapabilityManagement_Unsubscribe
Description:
The NF consumer unsubscribes from updates to UCMF dictionary entries.
Inputs, Required:
None.
Inputs, Optional:
None.
Outputs, Required:
None.
Outputs, Optional:
None.
5.2.18.3.5  Nucmf_UECapabilityManagement_Notify service operation
Service operation name:
Nucmf_UECapabilityManagement_Notify
Description:
Producer NF provides notifications about changes in UCMF to subscribed consumer NF.
Inputs, Required:
Notification Type ("creation", "deletion", "Added IMEI/TAC in Manufacturer Assigned operation requested list", "Removed IMEI/TAC from Manufacturer Assigned operation requested list", "Removed UE Radio Capability ID from Manufacturer Assigned operation requuested list").
Inputs, Optional:
If Notification Type is set to "creation": One or more UCMF dictionary entries, each UCMF dictionary entry consisting of a UE Radio Capability ID and the corresponding UE Radio Access Capability. If Notification Type is set to "deletion": One or more UE Radio Capability IDs. If Notification Type is set to "Added IMEI/TAC in Manufacturer Assigned operation requested list" or "Removed IMEI/TAC from Manufacturer Assigned operation requested list", one or more IMEI/TACs, if Notification type is "Removed UE Radio Capability ID from Manufacturer Assigned operation requested list, one or more PLMN assigned UE radio Capability IDs.
Outputs, Required:
None.
Outputs, Optional:
None.
The Manufacturer Assigned operation requested list is defined in clause 5.11.3a of TS 23.401 and clause 5.4.4.1a of TS 23.501.
Up
5.2.19  AF Services [R16]
5.2.19.1  General
The following table illustrates the AF Services.
Service Name
Service Operations
Operation Semantics
Example Consumer(s)

Naf_EventExposure
Subscribe
Subscribe/Notify
NEF, NWDAF
Unsubscribe
NEF, NWDAF
Notify
NEF, NWDAF

NOTE:
In this release of the specification, Naf_EventExposure service is only used for analytics as described in TS 23.288.
5.2.19.2  Naf_EventExposure service
5.2.19.2.1  General
Service description: This service enables consumer NF to subscribe and get notified of events.
The events can be subscribed by a NF consumer are described in TS 23.288.
The following service operations are defined for the Naf_EventExposure service:
  • Naf_EventExposure_Subscribe.
  • Naf_EventExposure_Unsubscribe.
  • Naf_EventExposure_Notify.
The following events can be subscribed by a NF consumer (Event ID is defined in clause 4.15.1):
Up
5.2.19.2.2  Naf_EventExposure_Subscribe service operationWord-p. 542
Service operation name:
Naf_EventExposure_Subscribe
Description:
The consumer NF subscribes the event to collect AF data for UE(s), group of UEs, or any UE, or updates the subscription which is already defined in AF.
Input, Required:
Target of Event Reporting: external UE ID(s), External Group Identifier, or indication that any UE is targeted, (set of) Event ID(s), Notification Target Address (+ Notification Correlation ID) and Event Reporting Information as defined in Table 4.15.1-1, Expiry time.
Input, Optional:
NF ID, Event Filter(s) associated with each Event ID, (set of) Application ID(s), Subscription Correlation ID (in the case of modification of the existing subscription).
NOTE:
In the case of untrusted AF, NEF ID is used as NF ID.
Output, Required:
Operation execution result indication. When the subscription is accepted: Subscription Correlation ID.
Output, Optional:
First corresponding event report is included, if corresponding information is available (see clause 4.15.1).
Up
5.2.19.2.3  Naf_EventExposure_Unsubscribe service operation
Service operation name:
Naf_EventExposure_Unsubscribe
Description:
The consumer NF unsubscribes for a specific event.
Input, Required:
Subscription Correlation ID.
Input, Optional:
None.
Output, Required:
Operation execution result indication.
Output, Optional:
None.
5.2.19.2.4  Naf_EventExposure_Notify service operation
Service operation name:
Naf_EventExposure_Notify
Description:
The AF provides the previously subscribed event information to the consumer NF which has subscribed to that event before.
Input, Required:
Notification Correlation Information, Event ID, corresponding UE(s) (external UE ID(s), External Group Identifier, or indication of any UE), time stamp.
Input, Optional:
Event specific parameter list.
Output, Required:
None.
Output, Optional:
None.

Up   Top   ToC