hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10.2.1 General | Service Description: the AUSF provides UE authentication service to the requester NF. For AKA based authentication, this operation can be also used to recover from synchronization failure situations. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10.2.2 Nausf_UEAuthentication_Authenticate service operation | See TS 33.501 [15]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10.2.3 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10.3 Nausf_SoRProtection service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10.3.1 General | Service Description: The AUSF provides the Steering of Roaming information protection service to the requester NF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10.3.2 Nausf_SoRProtection Protect service operation | See TS 33.501 [15]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10.4 Nausf_UPUProtection service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10.4.1 General | Service Description: The AUSF provides the UE Parameters Update protection service to the requester NF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10.4.2 Nausf_UPUProtection Protect service operation | See TS 33.501 [15]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10.5 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.11 NWDAF Services | The NWDAF services are defined in TS 23.288 [50]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.11.1 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.11.2 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.11.3 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.12 UDR Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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.
Table 5.2.12.1-1: NF services provided by UDR
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
UDM, PCF, NEF
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.
Table 5.2.12.1-2: Exposure data stored in the UDR
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 clause 5.3.2.3 of TS 23.501 [2].
The values are defined in TS 29.571 [70]
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
UE IP address
UE IP address
SUPI or GPSI
PDU session ID or DNN
information
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
DNAI mapping information
DNAI
DNAI mapping information
DNN and/or S-NSSAI |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.12.2 Nudr_DataManagement (DM) service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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.
Table 5.2.12.2.1-1: Data keys
Data Set
Data Subset
Data Key
Data Sub Key
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
Subscription Data (see clause 5.2.3.3.1)
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
(NOTE 5)
Internal Group Identifier or
External Group Identifier
-
Identifier translation
GPSI
SUPI
Application Port ID, MTC Provider Information, AF Identifier
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 SMSF data
SUPI
-
V2X Subscription data
SUPI
-
A2X Subscription data
SUPI
-
ProSe Subscription data
SUPI
-
Ranging/SL Positioning subscription data
SUPI
-
User consent
SUPI
Purpose
ECS Address Configuration Information (See Table 4.15.6.3d-1)
SUPI, Internal group identifier or external group identifier or any UE
DNN, S-NSSAI, (Serving) PLMN ID (NOTE 7)
MBS Subscription data
(see clause 6.4.3 of TS 23.247 [78])
SUPI
-
Ranging/Sidelink Positioning Subscription data
SUPI
-
Ranging/Sidelink Positioning privacy
SUPI
-
Operator Determined Barring data (see clause 2.3 of TS 23.015 [90] and TS 29.505 [91])
SUPI
-
Shared data
Shared Data ID
-
Application data
Packet Flow Descriptions (PFDs) (NOTE 11)
Application Identifier
AF traffic influence request information for traffic routing
AF transaction internal ID
(See clause 5.6.7 and clause 6.3.7.2 of TS 23.501 [2])
For non-roaming and LBO:
S-NSSAI and DNN , accompanied with Internal Group Identifier(s) and/or Subscriber Category(s) or SUPI or "any UE" indication
For HR-SBO:
HPLMN S-NSSAI and DNN and either: HPLMN ID and IP address, or SUPI, or "any UE" indication and HPLMN ID.
(NOTE 4) (NOTE 6) (NOTE 12)
AF traffic influence request information for service function chaining
AF transaction internal ID
(See clause 5.6.16 and clause 6.3.7.2 of TS 23.501 [2])
S-NSSAI and DNN
and
Internal Group Identifier or SUPI or "any UE" indication (NOTE 4)
AF traffic influence request information for Handling of Payload Headers
AF transaction internal ID
(See clause 5.6.17 and clause 6.3.7.2 of TS 23.501 [2])
S-NSSAI and DNN
and
Internal Group Identifier or SUPI or "any UE" indication (NOTE 4)
Background Data Transfer
(NOTE 3)
Internal Group Identifier or SUPI
Service specific information (See clause 4.15.6.7)
S-NSSAI and DNN
or
Internal Group Identifier or SUPI or "any UE" indication (NOTE 4) or "PLMN ID(s) of inbound roamer"
UE ID mapping information (See clause 4.3.5 of TS 23.586 [88])
GPSI or Application Layer ID
EAS Deployment Information
(See clause 7.1 of TS 23.548 [74])
DNN and/or S-NSSAI
Application Identifier and/or Internal Group Identifier
ECS Address Configuration Information (See Table 4.15.6.3d-1)
(NOTE 13)
DNN, S-NSSAI and "any UE" indication
AM influence information (See clause 4.15.6.9.3)
AF transaction internal ID
S-NSSAI and DNN
and/or
Internal Group Identifier or SUPI or "any UE" indication or any inbound roaming UEs (NOTE 4, NOTE 8)
AF request for QoS information (See clause 4.15.6.14)
AF transaction internal ID
S-NSSAI and DNN
and/or
Internal Group Identifier or SUPI or "any UE" indication (NOTE 4)
Non-3GPP Device Identifier Information (clause 5.52 of TS 23.501 [2])
SUPI
Non-3GPP Device Identifier
IPTV Configuration Data (see clause 7.7.1.1.4 in TS 23.316 [53])
S-NSSAI and DNN
and/or
Internal Group Identifier or SUPI
Policy Data
UE context policy control data
(See clause 6.2.1.3 of TS 23.503 [20])
SUPI
PDU Session policy control data
SUPI
S-NSSAI
(See clause 6.2.1.3 of TS 23.503 [20])
DNN
Policy Set Entry data
(See clause 6.2.1.3 of TS 23.503 [20])
SUPI (for the UDR in HPLMN)
PLMN ID (for the UDR in VPLMN)
Remaining allowed Usage data
SUPI
S-NSSAI
(See clause 6.2.1.3 of TS 23.503 [20])
DNN
Sponsored data connectivity profiles (See clause 6.2.1.6 of TS 23.503 [20])
Sponsor Identity
Background Data Transfer data
(See clause 6.2.1.6 of TS 23.503 [20])
Background Data Transfer Reference ID. (NOTE 2)
None. (NOTE 1)
Network Slice Specific Control Data
(See clause 6.2.1.3 of TS 23.503 [20])
S-NSSAI
5G VN Group Specific Control Data (See clause 6.2.1.3 of TS 23.503 [20])
S-NSSAI and DNN
and/or
Internal Group Identifier
Operator Specific Data
SUPI or GPSI
Planned Data Transfer with QoS requirements data
(See clause 6.2.1.6 of TS 23.503 [20])
PDTQ Reference ID. (NOTE 10)
None. (NOTE 9)
Exposure Data
Access and Mobility Information
SUPI or GPSI
PDU Session ID or
(see clause 5.2.12.1)
Session Management information
SUPI or GPSI
UE IP address or DNN
DNAI mapping information
DNN and/or S-NSSAI
NOTE 1: Retrieval of the stored Background Data Transfer data 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 data in the UDR requires a Data key to refer to a Background Data Transfer data as input data.
NOTE 3: The Background Data Transfer includes the Background Data Reference ID and the ASP Identifier that requests to apply the Background Data Reference ID to the UE(s). Furthermore, the Background Data Transfer includes the relevant information received from the AF as defined in clause 6.1.2.4 of TS 23.503 [20].
NOTE 4: When the Data Key targets "any UE", then the request to UDR applies on Application data that applies on all subscribers of the PLMN. For encoding, see TS 29.519 [82].
NOTE 5: Group Data includes 5G VN group configuration, DNN and S-NSSAI specific Group Parameters and any other data related to a group stored in the UDR.
NOTE 6: If a list of Internal Group IDs is used, the AF traffic influence request information request applies to the UEs that belong to every one of these groups, i.e. a single UE needs to be a member of every group in the list of Internal Group IDs.
NOTE 7: When the Data Key targets "PLMN ID", then the request to UDR applies on subscription data about subscribers roaming in this PLMN.
NOTE 8: In LBO roaming scenarios, when the AF request targets "any inbound roaming UEs", the AM influence information applies to the roaming subscribers from a PLMN or from any PLMN.
NOTE 9: Retrieval of the stored Planned Data Transfer with QoS requirements data for all ASP identifiers in the UDR requires Data Subset but no Data Key or Data Subkey(s).
NOTE 10: Update of a Planned Data Transfer with QoS requirements data in the UDR requires a Data key to refer to a Planned Data Transfer with QoS requirements data as input data.
NOTE 11: Each PFD (as defined in TS 23.503 [20]) may be complimented with a source NF type which indicates the type of NF that has generated the PFD (i.e. AF or NWDAF). Absence of a source NF type indicates that the AF is the source of the PFD.
NOTE 12: Further information about HR-SBO case and how these keys are used, see clause 4.3.6.1.
NOTE 13: The ECS Address Configuration Information as part of application data is used for HR roaming case as defined in clause 6.5.2.6 of TS 23.548 [74].
The content of the UDR storage for (Data Set Id= Application Data, Data Subset Id = AF TrafficInfluence request information) is specified in Table 5.6.7-1 of TS 23.501 [2], in Table 5.6.16.2-1 of TS 23.501 [2] and in Table 5.6.17.2-1 of TS 23.501 [2]. This information is written by the NEF and read by the PCF(s). PCF(s) may also subscribe to changes onto this information.
Wireline access specific subscription data parameters are specified in TS 23.316 [53]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.12.2.2 Nudr_DM_Query service operation | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.12.2.6 Nudr_DM_Subscribe service operation | 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).
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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.12.3 Nudr_GroupIDmap service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.12.3.2 Nudr_GroupIDmap_query service operation | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.13 BSF Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.13.1 General | The following table shows the BSF Services and Service Operations:
Table 5.2.13.1-1: NF services provided by the BSF
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, TSCTSF
Update
Request/Response
PCF
Subscsribe
Subscribe/Notify
NEF, PCF, AF, TSCTSF, 5G DDNMF
Unsubscribe
Subscribe/Notify
NEF, PCF, AF, TSCTSF, 5G DDNMF
Notify
Subscribe/Notify
NEF, PCF, AF, TSCTSF, 5G DDNMF |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.13.2 Nbsf_Management service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.13.2.1 General | The Nbsf provides the Nbsf_Management_Register, the Nbsf_Management_Deregister and the Nbsf_Management_Discovery services, the Nbsf_Management_Update, the Nbsf_Management_Subscribe, the Nbsf_Management_Unsubscribe and the Nbsf_Management_Notify operations. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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, MBS session ID, DNN, S-NSSAI, PCF address(es), PCF instance id, PCF Set ID, level of Binding) for a PDU Session or for a UE.
NOTE 1: In some cases only subset of these parameters may be registered (e.g. UE address(es) will be registered only if PCF registration is for a PDU Session and for MBS sessions SUPI and GPSI are also not available).
Inputs, Required: [Required, if PCF registration is for a PDU Session], UE address(es), PCF address(es), DNN [Required, if PCF registration is for a PDU Session], S-NSSAI [Required, if PCF registration is for a PDU Session], MBS session ID as defined in TS 23.247 [78] [Required, if PCF registration is for a MBS Session].
UE address can contain IP address/prefix or MAC address as defined in TS 23.501 [2]. It can optionally include Framed Route information. W-5GAN specific UE IP address information is specified in TS 23.316 [53].
Framed Route information is defined in Table 5.2.3.3.1-1.
NOTE 2: For support of time sensitive communication and time synchronization (as described in clause 5.28.3.2 of TS 23.501 [2]) the UE address contains the DS-TT port MAC address for Ethernet type PDU Session.
Inputs, Conditional: SUPI [Required, if PCF registration is for a UE or required by the local policy in PCF if the registration is for a PDU session, otherwise it is optional].
NOTE 3: The PCF can be configured to always provide a SUPI to the BSF, e.g. to support UE ID retrieval from the BSF.
Inputs, Optional: GPSI, PCF instance ID and PCF Set ID, level of Binding (see clause 6.3.1.0 of TS 23.501 [2]).
NOTE 4: DNN and S-NSSAI are not applicable when the PCF registration is for a UE.
NOTE 5: It is up to stage3 to ensure an unambiguous error proof way for the BSF to differentiate between PCF for the PDU Session and PCF for the UE. This may or may not require providing the BSF additional parameter(s) when a PCF registers itself with the BSF.
Outputs, Required: Result indication, Binding Identifier for a PDU Session, or for a UE, or for an MBS session.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.13.2.3 Nbsf_Management_Deregister service operation | Service Operation name: Nbsf_Management_Deregister
Description: Removes the binding information for a PDU Session or for a UE.
Inputs, Required: Binding Identifier for a PDU Session, or for a UE, or for an MBS session.
W-5GAN specific UE IP address information are specified in TS 23.316 [53].
Inputs, Optional:
Outputs, Required: Result indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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 a PDU Session identified by the tuple (UE address(es), SUPI, GPSI, DNN, S-NSSAI), or discovers the PCF and PCF set selected for the UE identified by the tuple (SUPI, GPSI). This operation may also be used to determine the SUPI from the tuple (UE address, DNN, S-NSSAI).
Inputs, Required: UE address (i.e. IP address or MAC address), [Required, for a PDU Session and for a UE], DNN [Conditional], S-NSSAI [Conditional], if the target PCF is for a PDU Session, MBS session ID as defined in TS 23.247 [78], [Required, for an MBS Session].
SUPI and/or GPSI, if the target PCF is for a UE.
NOTE: For support of time sensitive communication and time synchronization (as described in clause 5.28.3.2 of TS 23.501 [2]) the UE address contains the DS-TT port MAC address for Ethernet type PDU Session.
Inputs, Optional: If the target PCF is for a PDU Session, 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 [2]).
Outputs, Optional: SUPI, if available. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.13.2.5 Nbsf_Management_Update service operation | Service Operation name: Nbsf_Management_Update
Description: Replaces the list of UE address(es) for a PDU Session or replace PCF id or PCF address(es) for a PDU Session or for a UE..
NOTE 1: For example, PCF-2 may update its PCF id when level of binding is NF Instance and PCF-1 fails and PCF-2 is the new NF Instance handling the PDU Session or the UE.
Inputs, Required: Binding Identifier for the PDU Session.
UE address can contain IP address/prefix or Ethernet address as defined in TS 23.501 [2].
NOTE 2: For support of time sensitive communication and time synchronization (as described in clause 5.28.3.2 of TS 23.501 [2]) the UE address contains the DS-TT port MAC address for Ethernet type PDU Session.
Inputs, Optional: UE address(es), PCF id, PCF address(es).
Outputs, Required: Result indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.13.2.6 Nbsf_Management_Subscribe service operation | Service Operation name: Nbsf_Management_Subscribe
Description: NEF, AF, TSCTSF or PCF for the UE can subscribe to be notified of newly registered or deregistered PCF for the PDU Session. In addition, NEF or AF can subscribe to be notified of newly registered or deregistered PCF for the UE.
NOTE 1: If BSF has already the requested information at the time of the subscription, it will accept the subscription request and will immediately provide the results in the Outputs parameters.
Inputs, Required: SUPI, DNN(s) [Required, if PCF subscription is for a PDU Session], S-NSSAI(s) [Required, if PCF subscription is for a PDU Session], callback URI.
Inputs, Optional: GPSI, indication of registration/deregistration per (DNN, S-NSSAI).
Indication of registration/deregistration per (DNN, S-NSSAI) indicates to the BSF to report when the first SM policy association is established and when the last SM policy association is terminated to the same (DNN, S-NSSAI) combination.
NOTE 2: It is up to stage3 to ensure an unambiguous error proof way for the BSF to differentiate between PCF for the PDU Session and PCF for the UE. This may or may not require providing the BSF additional input parameter(s).
Outputs, Required: When the subscription is accepted: Subscription Correlation ID.
Outputs, Conditional: One or more instance per (DNN, S-NSSAI) of (UE address(es) [If available], PCF address(es) [If available], PCF instance ID [If available], PCF Set ID [If available], level of Binding [If available] (see clause 6.3.1.0 of TS 23.501 [2])) or notification of registration/deregistration per (DNN, S-NSSAI).
NOTE 3: The parameter UE address(es) is not applicable in the case of PCF for the UE. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.13.2.7 Nbsf_Management_Unsubscribe service operation | Service Operation name: Nbsf_Management_Unsubscribe
Description: NEF, AF, TSCTSF or PCF for the UE can undo a previous subscription.
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.13.2.8 Nbsf_Management_Notify service operation | Service Operation name: Nbsf_Management_Notify
Description: BSF can notify NEF, AF, TSCTSF or PCF for the UE of newly registered PCF for the PDU Session or of deregistered PCF for the PDU Session.
Inputs, Required: Notification Correlation Information, One or more instance per (DNN, S-NSSAI) of (UE address(es) [Required, if PCF notification is for a PDU Session], 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 [2]) or notification of registration/deregistration per (DNN, S-NSSAI).
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14 UDSF Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.1 General | The following table illustrates the UDSF Services.
Table 5.2.14-1: NF Services provided by UDSF
NF service
Service Operations
Operation Semantics
Example Consumer(s)
UnstructuredData
Query
Request/Response
Any NF
Management
Create
Request/Response
Any NF
Delete
Request/Response
Any NF
Update
Request/Response
Any NF
Subscribe
Subscribe/Notify
Any NF
Unsubscribe
Subscribe/Notify
Any NF
Notify
Subscribe/Notify
Any NF
Nudsf_Timer
Start
Request/Response
Any NF
Stop
Request/Response
Any NF
Update
Request/Response
Any NF
Search
Request/Response
Any NF
Notify
Subscribe/Notify
Any NF
NOTE: Nudsf is different compared to other service-based interfaces due to dynamic data access performance requirements. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.2 Nudsf_UnstructuredDataManagement service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.2.1 General | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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: Validity time, Notification Endpoint.
Validity time tells for how long the created data is valid. When validity time has expired, NF service consumer is notified and data is removed.
Outputs, Required: Result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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: Validity time.
Validity time tells for how long the created data is valid. When validity time has expired, NF service consumer is notified and data is removed.
Outputs, Required: Result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.2.6 Nudsf_UnstructuredDataManagement_Subscribe | Service operation name: Nudsf_UnstructuredDataManagement_Subscribe
Description: NF service consumer subscribes to notifications of data change in the UDSF.
Inputs, Required: Identity of data to be monitored, Notification endpoint.
Inputs, Optional: None.
Outputs, Required: Subscription ID.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.2.7 Nudsf_UnstructuredDataManagement_Unsubscribe | Service operation name: Nudsf_UnstructuredDataManagement_Unsubscribe
Description: NF service consumer un-subscribes to notifications of data change in the UDSF.
Inputs, Required: Subscription ID.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.2.8 Nudsf_UnstructuredDataManagement_Notify | Service operation name: Nudsf_UnstructuredDataManagement_Notify
Description: NF is notifications of data change or if validity time for created data has expired in the UDSF.
Inputs, Required: Data Identifier, Data.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.3 Nudsf_Timer service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.3.1 General | Any NF may use the UDSF to run timer(s), search for timer(s) and get notifications on expiry. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.3.2 Nudsf_Timer_Start service operation | Service operation name: Nudsf_Timer_Start
Description: NF service consumer starts a timer in the UDSF.
Inputs, Required: Timer ID, Time of expiry.
Inputs, Optional: Notification Endpoint, Associated data.
Associated data is data that can be used by the consumer to identify for what purpose the timer is for, e.g. a subscription that has timed out.
Outputs, Required: Result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.3.3 Nudsf_Timer_Update service operation | Service operation name: Nudsf_Timer_Update
Description: NF service consumer updates a timer in the UDSF.
Inputs, Required: Timer Identity.
Inputs, Optional: Notification Endpoint, Associated data, Time of expiry.
Associated data is data that can be used by the consumer to identify for what purpose the timer is for, e.g. a subscription that has timed out.
Outputs, Required: Result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.3.4 Nudsf_Timer_Notify service operation | Service operation name: Nudsf_Timer_Notify
Description: The UDSF notifies the NF service consumer about a timer expiry.
Inputs, Required: Timer Identity.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.3.5 Nudsf_Timer_Stop service operation | Service operation name: Nudsf_Timer_Stop
Description: NF service consumer intends to stop timer(s) in the UDSF.
Inputs, Required: Timer Identity/Identities.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.14.3.6 Nudsf_Timer_Search service operation | Service operation name: Nudsf_Timer_Search
Description: NF service consumer intends to search and retrieve timers matching a filter in the UDSF.
Inputs, Required: Search filter (see TS 29.598 [85]).
Inputs, Optional: Filter.
Outputs, Required: Result.
Outputs, Optional: Timer Identity/Identities. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.15 LMF Services | LMF services are defined in clause 8.3 of TS 23.273 [51]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.16 NSSF Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.16.1 General | The following table illustrates the NSSF Services.
Table 5.2.16.1-1: NF Services provided by NSSF
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Nnssf_NSSelection
Get
Request/Response
AMF, NSSF in a different PLMN, SMF, NWDAF
Nnssf_NSSAIAvailability
Update
Request/Response
AMF
Subscribe
Subscribe/Notify
AMF, NSSF
Unsubscribe
AMF, NSSF
Notify
AMF, NSSF
Delete
Request/Response
AMF
NOTE: The SMF uses the Nnssf_NSSelection_Get service operation during EPS interworking. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.16.2 Nnssf_NSSelection service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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 allows also to provide the NSAG information which is applicable (clause 5.15.14 of TS 23.501 [2]).
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; if invoked in the VPLMN it returns the hNRF selected by the hNSSF and if applicable, the value of the HPLMN NSI ID. 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.
NOTE 2: The NSSF can determine the serving network and Access Type from the TAI, as described in TS 29.571 [70].
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 during Registration procedure to get the slice mapping information in the case of Indirect Network Sharing as specified in clause 5.18.5 of TS 23.501 [2], then the following inputs are required:
- HPLMN S-NSSAIs, PLMN ID of the SUPI.
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 SMF+PGW-C, 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, NSSRG Information, UE support of subscription-based restrictions to simultaneous registration of network slice feature Indication, UDM indication to provide all subscribed S-NSSAIs for UEs not indicating support of subscription-based restrictions to simultaneous registration of network slices, 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, Rejected S-NSSAI(s) for RA, UE support of NSAG Information.
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 Registration procedure to get the slice mapping information in the case of Indirect Network Sharing as specified in clause 5.18.5 of TS 23.501 [2], then the following outputs are required:
- HPLMN S-NSSAIs, Mapping of HPLMN S-NSSAIs in the hosting operator's network.
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 SMF+PGW-C, 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, Target NSSAI, the NSAG information (defined in clause 5.15.14 of TS 23.501 [2]).
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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.16.3 Nnssf_NSSAIAvailability service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.16.3.1 General | Service description: This service enables to update the AMFs and the NSSF on the availability of S-NSSAIs and NSAGs on a per TA basis. This service also enables updates for Network Slice Replacement and Network Slice Instance Replacement to the NF Service Consumer (e.g. AMF or NSSF in the VPLMN) when the NSSF determines that an S-NSSAI has to be replaced with an Alternative S-NSSAI or a Network Slice instance is replaced as described in clause 5.15.19 [2].
NOTE: The NSSF can determine the serving network and Access Type from the TAI, as described in TS 29.571 [70].
When this service is used by the NSSF for Network Slice Replacement, i.e. to provide to the NF Service Consumer an Alternative S-NSSAI to the S-NSSAI to be replaced, the following cases are possible:
- in non-roaming and in roaming case, NSSF in the Serving PLMN provides to the AMF the Alternative S-NSSAI of the Serving PLMN; or
- in roaming case, the NSSF in the HPLMN provides to the NSSF in the VPLMN the Alternative HPLMN S-NSSAI; and the NSSF in the VPLMN provides to the AMF the Alternative HPLMN S-NSSAI.
Following NSSF event subscriptions are supported:
- NSSAI availability status change;
- Network Slice Replacement (see clause 5.15.19 of TS 23.501 [2]);
- Network Slice Instance Replacement (see clause 5.15.20 of TS 23.501 [2]). |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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 and optionally NSI IDs 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: Supported NSAGs per TAI.
The supported NSAGs per TAI is a list of TAIs and for each TAI the NSAGs and for each NSAG the associated S-NSSAIs supported by the AMF.
Outputs, Required: A list of TAIs and for each TAI, the S-NSSAIs and optionally NSI IDs supported by the AMF and 5G-AN and authorized by the NSSF for the TAI.
Outputs, Conditional Required: A list of TAIs and for each TAI, the NSAGs authorized by the NSSF for the TAI.
If the NSSF has NSAG information, it should provide the authorized NSAGs per TAI. This is a list of TAIs and for each TAI the NSAGs and for each of the NSAGs the associated S-NSSAIs.
NOTE: This NSAG information can include additional NSAG - S-NSSAIs associations (e.g. NSAG information obtained from other AMFs).
Outputs, Optional: For each TAI, a list of S-NSSAIs restricted per PLMN for the TAI. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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 a NF Service Consumer (e.g. AMF) with any S-NSSAIs restricted per validity time, or per TA and if needed subsequently lift any restriction per TA. This service operation also enables the NSSF to notify to the NF Service Consumer (e.g. AMF or NSSF in the VPLMN) that an S-NSSAI has to be replaced by an Alternative S-NSSAI or a Network Slice instance should be replaced.
Inputs, Required: Subscription Correlation ID.
Inputs, Conditional Required:
If this service operation is invoked by subscription for changes in the status of the NSSAI availability information, then the following inputs are required:
- a list of TAIs and the S-NSSAIs for which the status is changed (restricted/unrestricted) per each TAI.
If this service operation is invoked by subscription for event notification for Network Slice Replacement, then the following inputs are required:
- For replacement of an S-NSSAI of the serving PLMN: an Alternative S-NSSAI and the corresponding mapping to the S-NSSAI to be replaced.
- For replacement of an HPLMN S-NSSAI: an Alternative S-NSSAI and the corresponding mapping to the S-NSSAIs of the HPLMN, PLMN ID.
- For termination of the Network Slice replacement:
1) indication to stop the Network Slice replacement for new UEs; or
2) indication to terminate the Network Slice replacement and move back the UEs and PDU Sessions from the Alternative S-NSSAI to the S-NSSAI.
If this service operation is invoked by subscription for event notification for Network Slice Instance Replacement, then the following inputs are required:
- The S-NSSAI(s) and NSI ID(s) for which the status is changed (e.g. congested or no longer available).
If this service operation is invoked by subscription for event notification for update of slice validity time, then the following inputs are required:
- The S-NSSAI(s) and associated validity time for each S-NSSAI.
Inputs, Optional:
- NSI IDs in the S-NSSAI for which the status is changed (restricted/unrestricted) per each TAI.
If this service operation is invoked by subscription for event notification for Network Slice Replacement or Network Slice Instance Replacement, then the following inputs are optionally provided with the Alternative S-NSSAI:
- For replacement due to congestion: congestion mitigation information which includes information that the Network Slice replacement applies 1) for a percentage and/or 2) for new UEs registering to the Network Slice.
NOTE: If the AMF does not receive any congestion mitigation information the AMF executes the replacement until the NSSF notifies the AMF to either stop the replacement or to terminate the replacement and move back the UEs and PDU Sessions from the Alternative S-NSSAI to the S-NSSAI as the S-NSSAI is available again for all the UEs.
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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-NSSAI validity time, S-NSSAIs and optionally NSI IDs available per TA and the restricted S-NSSAI(s) and optionally NSI IDs per PLMN in that TA in the serving PLMN of the UE) upon this is updated by another AMF. This service also enables the NF Service Consumer (e.g. AMF or NSSF in the VPLMN) to subscribe to a notification of Network Slice Replacement and Network Slice Instance Replacement.
Inputs, Required: Callback URI of the NF Service Consumer:
Inputs, Conditional Required:
If this service operation is invoked to subscribe for changes in status of the NSSAI availability information, then the following inputs are required:
- list of TAIs supported by the NF service consumer, event to be subscribed.
If this service operation is invoked to subscribe for changes in status of the NSSAI validity time information, then the following inputs are required:
- The S-NSSAIs, event to be subscribed.
If this service operation is invoked to subscribe to a notification for Network Slice Replacement, then the following inputs are required:
- for the S-NSSAI of the serving PLMN: set of S-NSSAIs served by the NF Service Consumer that may be replaced, NF type of the NF Service Consumer (e.g. AMF), Requester ID, event to be subscribed.
- for HPLMN S-NSSAI: S-NSSAIs for the HPLMN, NF type of the NF Service Consumer (e.g. AMF or NSSF), Requester ID and PLMN ID, event to be subscribed.
If this service operation is invoked to subscribe to a notification when the Network Slice instance is congested or no longer available, then the following inputs are required:
- The S-NSSAIs, NSI IDs, event to be subscribed.
Inputs, Optional: Expiry time.
Outputs, Required: Subscription Correlation ID.
Outputs, Conditional Required:
If this service operation is invoked to subscribe for changes in status of the NSSAI availability information, then the following outputs are 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:
If this service operation is invoked to subscribe for changes in status of the NSSAI availability information, then the following outputs are optional:
- A list of TAIs and for each TAI, the S-NSSAIs and optionally NSI IDs supported by the AMF and 5G-AN and authorized by the NSSF for the TAI and a list of S-NSSAIs and optionally NSI IDs restricted per PLMN for the TAI. The NSSS indicates to the AMF that the S-NSSAI(s) are not available in the corresponding TAIs. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.16.3.5 Nnssf_NSSAIAvailability_Unsubscribe service operation | 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. This service operation also enables the NF Service Consumer (e.g. AMF, NSSF) to unsubscribe to a notification for Network Slice Replacement or for Network Slice Instance Replacement.
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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: NF ID.
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.16.4 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.17 CHF Spending Limit Control Service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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 [42].
Tale 5.2.17.1-1: CHF Services
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Nchf_SpendingLimitControl
Subscribe
Subscribe/Notify
PCF
Unsubscribe
PCF
Notify
PCF |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.17.2 Nchf_SpendingLimitControl service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.18 UCMF Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.18.1 General | The following table illustrates the UCMF Services.
Table 5.2.18.1-1: NF services provided by UCMF
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 |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.18.2 Nucmf_Provisioning service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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 the following inputs are provided:
a) a UE radio access capability set with respective coding format or the UE radio access capability set in both TS 36.331 [16] and TS 38.331 [12] coding formats and each RATs' UE Radio Capability for Paging; and
b) the related UE model(s) IMEI/TAC value(s) the UE radio capability ID applies to.
Inputs, Required: (list of) [UE Radio Capability ID(s), set(s) of UE radio access capability set and UE Radio Capability for Paging and respective Coding format(s), (list of) IMEI/TAC value(s)].
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None.
The Coding format(s) indicates the format of the respective UE radio access capabilities as defined in TS 36.331 [16] or TS 38.331 [12]. The UCMF dictionary entry shall not contain UTRAN radio capabilities. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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 IMEI/TAC that no longer use associated UE radio Capability ID(s).
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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) IMEI/TAC(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) IMEI/TAC(s) to be removed.
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.18.3 Nucmf_UECapabilityManagement Service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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 and one or more UE Radio Capability for Paging corresponding to a specific UE Radio Capability ID (either Manufacturer-assigned or PLMN-assigned) and Coding Format.
Inputs, Required: UE Radio Capability ID, Coding format, one or more UE Radio Capability for Paging.
Inputs, Optional: None.
Outputs, Required: UE Radio Access Capability, UE Radio Capability for Paging.
Outputs, Optional: None.
The Coding format indicates the format as defined in TS 36.331 [16] or TS 38.331 [12] of the UE Radio Access Capability expected by the NF in output. When the Coding Format is TS 36.331 [16], the UCMF shall provide the UE Radio Capability for Paging for E-UTRA. When the Coding Format is TS 38.331 [12], the UCMF shall provide the UE Radio Capability for Paging for NR and if the PLMN supports E-UTRA connected to 5GC, shall provide the UE Radio Capability for Paging for E-UTRA. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.18.3.2 Nucmf_UECapabilityManagement_Assign service operation | Service or service operation name: Nucmf_UECapabilityManagement_Assign
Description: The NF consumer sends to the UCMF:
- the UE Radio Access Capability (and its Coding Format); or
- the UE Radio Access Capability and UE Radio Capability for Paging in both TS 36.331 [16] and TS 38.331 [12] coding formats;
and obtains a PLMN-assigned UE Radio Capability ID in return.
Inputs, Required: UE Radio Access Capability(s), UE Radio Capability for Paging(s), Coding format(s), IMEI/TAC.
Inputs, Optional: One or more UE Radio Capability for Paging.
Outputs, Required: UE Radio Capability ID.
Outputs, Optional: None.
The AMF does not send NB-IoT Radio Access Capability to the UCMF.
The Coding format indicates the format of the UE Radio Access Capability as defined in TS 36.331 [16] or TS 38.331 [12]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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 and provides the coding format in which UE Radio Access Capability is expected by NF. The UCMF shall check the requested consumer is authorized to subscribe to requested updates.
Inputs, Required: Coding format.
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None.
The Coding format indicates the format of the UE Radio Access Capability as defined in TS 36.331 [16] or TS 38.331 [12]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.18.3.4 Nucmf_UECapabilityManagement_Unsubscribe service operation | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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 [13] and clause 5.4.4.1a of the present document. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.19 AF Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.19.1 General | The following table illustrates the AF Services.
Table 5.2.19.1-1: Services provided by AF
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 [50]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.19.2 Naf_EventExposure service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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 [50].
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):
- Service Experience information, as defined in clause 6.4.2 of TS 23.288 [50].
- Performance Data information, as defined in clauses 6.4.2 and clause 6.14.2 of TS 23.288 [50].
- Collective Behaviour information, as defined in clause 6.5.2 of TS 23.288 [50].
- UE Mobility information, as defined in clause 6.7.2.2 of TS 23.288 [50].
- UE Communication information, as defined in clause 6.7.3.2 of TS 23.288 [50].
- Exceptions information, as defined in clause 6.7.5.2 of TS 23.288 [50].
- User Data Congestion information, as defined in clause 6.8.2 of TS 23.288 [50].
- UE Data volume Dispersion information, as defined in clause 6.10.2 of TS 23.288 [50].
- DN Performance information, as defined in clause 6.14.2 of TS 23.288 [50].
- Global Navigation Satellite System (GNSS) UE location as defined in clause 6.17.2 of TS 23.288 [50].
- E2E data volume transfer time information, as defined in clause 6.18.2 of TS 23.288 [50].
- Relative Proximity information, as defined in clause 6.19.2 of TS 23.288 [50].
- Signalling Storm information, as defined in clause 6.22.2 of TS 23.288 [50].
Event Filters are used to specify the conditions to match for notifying the event (i.e. "List of Parameter values to match"). If there are no conditions to match for a specific Event ID, then the Event Filter is not provided. The following table provides some examples on how the conditions to match for event reporting can be specified for various Event IDs for AF exposure.
Table 5.2.19.2.1-1: Example of Event Filters for AF exposure events
Event ID for AF exposure
Event Filter (List of Parameter Values to Match)
Exceptions information
<Parameter Type = Exception ID, Value = Exception ID1>
Service Experience information
<Parameter Type = TAI, Value = TAI1>
Service Experience information
<Parameter Type = geographical area,
Value = civic address1 or shape1>
Collective Behaviour information
<Parameter Type = collective attribute,
Value = collective value1>
Collective Behaviour information
<Parameter Type = data processing type,
Value = data processing type1> |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.19.2.2 Naf_EventExposure_Subscribe service operation | 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 (either UE ID(s), or UE IPv4 address(es), or UE IPv6 prefix(es), or Internal/External Group Identifier, or indication that any UE is targeted, or GPSI range), (set of) Event ID(s), Notification Target Address (+ Notification Correlation ID) and Event Reporting Information as defined in Table 4.15.1-1.
NOTE 1: UE ID includes GPSI or SUPI.
Input, Optional: NF ID, Event Filter(s) associated with each Event ID, (set of) External Application Identifier(s), Subscription Correlation ID (in the case of modification of the existing subscription), Expiry time.
NOTE 2: 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, Expiry time (required if the subscription can be expired based on the local policy).
Output, Optional: First corresponding event report is included, if corresponding information is available (see clause 4.15.1). |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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 ID(s) (either external UE ID(s), or Internal/External Group Identifier, or UE IP v4 address(es) or UE IP v6 prefix(es), or GPSI range, time stamp.
NOTE: UE ID includes GPSI or SUPI.
Input, Optional: Event specific parameter list.
Output, Required: None.
Output, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.19.3 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.20 NSSAAF services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.20.1 General | The following table illustrates the NSSAAF Services.
Table 5.2.20-1: List of NSSAAF Services
Service Name
Service Operations
Operation Semantics
Example Consumer(s)
Nnssaaf_NSSAA
Authenticate
Request/Response
AMF
Re-AuthenticationNotification
Notify
AMF
RevocationNotification
Notify
AMF
Nnssaaf_AIW
Authenticate
Request/Response
AUSF |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.20.2 Nnssaaf_NSSAA service |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.