hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.33.3 Nnef_AF_request_for_QoS_Notify service operation | Service operation name: Nnef_AF_request_for_QoS Notify
Description: NEF reports the QoS Flow level event(s) to the consumer.
Inputs, Required: Reports of the events as defined in clause 6.1.3.18 of TS 23.503 [20].
Inputs, Optional: When the event report is for QoS Monitoring, includes Packet delay for UL, DL, or round trip of the single UP path or two UP paths in the case of redundant transmission, as defined in clause 5.33.3.2 of TS 23.501 [2].
Outputs, Required: None.
Output (optional): None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.33.4 Nnef_AF_request_for_QoS_Revoke service operation | Service operation name: Nnef_AF_request_for_QoS Revoke
Description: The consumer requests the network to revoke the Service Requirement(s) and/or additional Alternative Service Requirement(s) for a UE or a group of UEs.
Inputs, Required: Transaction Reference ID.
Inputs, Optional: None.
Outputs, Required: Transaction Reference ID, result.
Output (optional): None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.33.5 Nnef_AF_request_for_QoS_Update service operation | Service operation name: Nnef_AF_request_for_QoS Update
Description: The consumer requests the network to update the Service Requirement(s) and/or additional Alternative Service Requirement(s) for a UE or a group of UEs.
Inputs, Required: Transaction Reference ID.
Inputs, Optional: Flow description information (as described in clause 6.1.3.6 of TS 23.503 [20]), QoS reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503 [20], time period, traffic volume, Alternative Service Requirements (containing one or more QoS reference parameters or Requested Alternative QoS Parameter Sets in a prioritized order), QoS parameter(s) to be measured, Reporting frequency, Target of reporting and optional an indication of direct event notification as described in clause 6.1.3.21 of TS 23.503 [20], traffic characteristics as described in clause 6.1.3.23 or 6.1.3.23a of TS 23.503 [20].
Outputs, Required: Result.
Output (optional): None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.34 Nnef_DNAIMapping service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.34.1 General | The service is allowing AF and NWDAF to obtain DNAI. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.34.2 Nnef_DNAIMapping_Subscribe service operation | Service operation name: Nnef_DNAIMapping_Subscribe
Description: This service operation is used by the consumer to subscribe for DNAI information by providing specific information of AF and NWDAF.
Inputs, Required: EAS address information i.e. IP address/IP address range or FQDN.
Inputs, Optional: DNN, S-NSSAI, AF identifier, Event Reporting Information defined in Table 4.15.1-1.
NOTE: If consumer wants, one-time reporting can be done by setting the Event Reporting Information as follows: event reporting mode to maximum number of reports, maximum number of reports=1 and Immediate reporting flag set.
Outputs, Required: When the subscription is accepted and not one-time reporting: Subscription Correlation ID, Expiry time (required if the subscription can be expired based on the operator's policy).
Outputs, Optional: DNAI, if available. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.34.3 Nnef_DNAIMapping_Unsubscribe service operation | Service operation name: Nnef_DNAIMapping_Unsubscribe
Description: The NF consumer terminates a subscription.
Inputs, Required: if not one-time reporting, Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: Operation execution result indication result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.34.4 Nnef_DNAIMapping_UpdateNotify service operation | Service operation name: Nnef_DNAIMapping_UpdateNotify
Description: This service operation is used by the NEF to notify NF consumer about the update of DNAI - EAS address(es) mapping information.
Inputs, Required: One or more pairs of DNAI(s) and EAS address(es).
Inputs, Optional: Cause.
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.35 Nnef TrafficInfluenceData service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.35.1 General | This service is used by SMF in VPLMN to subscribe AF traffic influence request information from the AF via the NEF in VPLMN. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.35.2 Nnef_TrafficInfluenceData_Subscribe service operation | Service operation name: Nnef_TrafficInfluenceData_Subscribe
Description: The NF consumer subscribes for the notifications of AF traffic influence request information.
Inputs, Required: Data Set Identifier (i.e. Application data), Data Subset Identifier (i.e. AF traffic influence request information), Data Key(s), Notification Target Address, Event Reporting Information defined in Table 4.15.1-1.
Inputs, Optional: None.
Outputs, Required: When the subscription is accepted: Subscription Correlation ID.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.35.3 Nnef_TrafficInfluenceData_Unsubscribe service operation | Service operation name: Nnef_TrafficInfluenceData_Unsubscribe
Description: Provided by the NEF for NF consumers to explicitly unsubscribe the notification of AF traffic influence request information.
Inputs, Required: Subscription Correlation ID (reference of the subscription).
Inputs, Optional: None.
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.35.4 Nnef_TrafficInfluenceData_Notify service operation | Service operation name: Nnef_TrafficInfluenceData_Notify
Description: NEF notifies NF consumer(s) about AF traffic influence request information, when receives notification of AF traffic influence request information from UDR.
Inputs, Required: Notification Correlation ID, Data Set Identifier as defined in clause 5.2.12.2.1, Target of Event Reporting as defined in clause 5.2.12.2, AF traffic influence request information.
Inputs, Optional: None.
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.36 Nnef_UEAddress service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.36.1 General | See clauses 6.2.8.2.4.3 and 6.2.8.2.4.5 of TS 23.288 [50]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.36.2 Nnef_UEAddress_Get service operation | Service operation name: Nnef_UEAddress_Get
Description: Get the UE IP address (i.e. IPv4 address or IPv6 prefix).
Inputs, Required: GPSI, AF Identifier.
Inputs, Optional: None.
Outputs, Required: Result, UE address (i.e. IPv4 address or IPv6 prefix).
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.36.3 Nnef_UEAddress_Subscribe service operation | Service operation name: Nnef_UEAddress_Subscribe
Description: The NF consumer subscribes for the immediate notifications of the NATed UE public IP address and Port number corresponding to UE private IP address. See clause 6.2.8.2.4.5 of TS 23.288 [50].
Inputs, Required: UE (private) IP address, AF Identifier, IP address of remote end, Notification Correlation ID.
Inputs, Optional: IP domain, Port number of remote end.
Outputs, Required: When the subscription is accepted: Subscription Correlation ID.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.36.4 Nnef_UEAddress_UnSubscribe service operation | Service operation name: Nnef_UEAddress_UnSubscribe
Description: Provided by the NEF for NF consumers to explicitly unsubscribe the notification of NATed UE public IP address and Port number.
Inputs, Required: Subscription Correlation ID (reference of the subscription).
Inputs, Optional: None.
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.36.5 Nnef_UEAddress_Notify service operation | Service operation name: Nnef_UEAddress_Notify
Description: NEF notifies NF consumer(s) about NATed UE public IP address and Port number, when receives notification from UPF. See clause 6.2.8.2.4.5 of TS 23.288 [50].
Inputs, Required: Notification Correlation ID, NATed UE public IP address and Port number.
Inputs, Optional: None.
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.37 Nnef_ECSAddress service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.37.1 General | Service description: The ECS Address service in the V-NEF provides functions for ECS Address Configuration Information provision for a group of UE or any UE from AF and for subscribing and retrieving ECS Address Configuration Information and providing ECS Address Configuration Information to the V-SMF to support. For related procedures see clauses 6.5.2.6.2 and 6.5.2.6.3 of TS 23.548 [74].
This procedure is defined only for the support of HR-SBO. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.37.2 Nnef_ECSAddress_Create service operation | Service operation name: Nnef_ECSAddress_Create
Description: The NF consumer requests to create ECS Address Configuration Information.
Inputs, Required: ECS Address Configuration Information.
Inputs, Optional: AF-service-identifier, AF Transaction Id, DNN, S-NSSAI.
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.37.3 Nnef_ECSAddress_Update service operation | Service operation name: Nnef_ECSAddress_Update
Description: The NF consumer requests to update ECS Address Configuration Information.
Inputs, Required: ECS Address Configuration Information.
Inputs, Optional: AF-service-identifier, AF Transaction Id, DNN, S-NSSAI.
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.37.4 Nnef_ECSAddress_Delete service operation | Service operation name: Nnef_ECSAddress_Delete
Description: The NF consumer requests to delete ECS Address Configuration Information.
Inputs, Required: Either:
- AF-identifier;
- S-NSSAI and DNN;
- ECS Address Configuration Information;
- AF Transaction Id.
The AF Transaction Id identifies the NF Service Consumer request for ECS Address Configuration Information to be deleted.
Inputs, Optional: None.
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.37.5 Nnef_ECSAddress_Subscribe service operation | Service operation name: Nnef_ECSAddress_Subscribe
Description: Provided by the NEF for NF consumers to explicitly subscribe the notification of changes of ECS Address Configuration Information.
Inputs, Required: Event ID, Notification Target Address (+Notification Correlation ID).
Inputs, Optional: list of (DNN, S-NSSAI).
Outputs, Required: Result Indication. When the subscription is accepted: Subscription Correlation ID (reference of the subscription).
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.37.6 Nnef_ECSAddress_Unsubscribe service operation | Service operation name: Nnef_ECSAddress_Unsubscribe
Description: Provided by the NEF for NF consumers to explicitly unsubscribe the notification of changes of ECS Address Configuration Information.
Inputs, Required: Subscription Correlation ID (reference of the subscription).
Inputs, Optional: None.
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.37.7 Nnef_ECSAddress_Notify service operation | Service operation name: Nnef_ECSAddress_Notify
Description: Provides subscribed event information, e.g. updated ECS Address Configuration Information to the NF Consumer.
Inputs, Required: Event ID, Notification Correlation ID, ECS Address Configuration Information.
Inputs, Optional: None.
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.38 Void | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.39 Nnef_ImsEventExposure service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.39.1 General | Service description: This service enables the NF to subscribe for a specific IMS event and be notified about subscribed IMS event. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.39.2 Nnef_ImsEventExposure (ImsEE) service | 5.2.6.39.2.1 Nnef_ImsEE_Subscribe service operation
Service operation name: Nnef_ImsEE_Subscribe
Description: The NF consumer subscribes for a specific IMS event.
Inputs, Required: Event-ID(s) representing the event of interest, Event Reporting Information as defined in Table 4.15.1-1.
Inputs, Optional: List one or more IMS Public Subscriber identity, Event Filters, Notification Target address, Notification Correlation Information, Expiry time, Subscription Correlation ID (in the case of modification of the event subscription), AF Identifier.
IMS Public subscriber identity entry is only present for subscriber specific IMS events.
NOTE: The semantics of the Event ID and Event Filters are transparent to the NEF.
Outputs, Required: When the subscription is accepted: Subscription Correlation ID, Expiry time (required if the subscription can expire based on the operator's policy).
Outputs, Optional: First corresponding event report is included, if available (see clause 4.15.1).
5.2.6.39.2.2 Nnef_ImsEE_Unsubscribe service operation
Service operation name: Nnef_ImsEE_Unsubscribe
Description: The NF consumer unsubscribe the notification of Event.
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None.
5.2.6.39.2.3 Nnef_ImsEE_Notify service operation
Service operation name: Nnef_ImsEE_Notify
Description: This service operation is used by the NEF to report to the NF consumer received information by the NEF in a Notify Request from the IMS AS that detected the event previously subscribed.
Inputs, Required: Event ID, time stamp, Notification Correlation ID.
Inputs, Optional: Notification Correlation Information, Event information (defined on a per Event ID basis).
Outputs, Required: Operation execution result indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.40 Nnef_ImsSessionManagement service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.40.1 General | The service provides the capability to create and release an IMS session with standalone data channel media and modify data channel media in a specific IMS session.
NOTE: In this Release only session management of IMS data channel is specified. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.40.2 Nnef_ImsSessionManagement_Create service operation | Service operation name: Nnef_ImsSessionManagement_Create
Description: This service enables the consumer NF to create an IMS session with the requested media (e.g. standalone data channel media).
NOTE: Only data channel media is supported in this Release.
Inputs, Required: Calling ID, Called ID, Media information set.
Calling ID: It is the public identity of calling IMS Subscriber or the identity of the consumer NF, e.g. DC AS.
Called ID: It is the public identity of called IMS Subscriber.
Media information set: Includes a set of media information indicating how the media used in the created session. Each media information contains:
- Media Correlation ID: It identifies the media component to be created. It is allocated by the consumer NF.
- Media Type: It indicates the media type used in the created session, e.g. Data Channel.
- Media Parameter set: It indicates the related media parameters. For different media, it contains different parameters:
- When the Media Type is Data Channel, it includes:
- DC Type: indicates the Data Channel Type (ADC or BDC);
- When DC Type is ADC:
- ADC Type: the ADC type (P2A, P2P, P2A2P);
- App Binding Information;
- Target ID(s): the public identity(ies) of the IMS Subscriber the DC is targeted;
NOTE: For P2P ADC, the Calling ID and Called ID of the session are used as the Target IDs.
- If PA2 or P2A2P is selected, the MDC2 media endpoint address(es) of the application layer is included.
- When DC Type is BDC;
- Target ID: the public identity of the IMS Subscriber the DC is targeted;
- the MDC1 media endpoint address.
Inputs, Optional: Notification Target Address and Notification Correlation ID.
If the request includes a Notification Target Address, the request creates an implicit subscription to be notified for the events in Table AA.2.4.4.5-1 of TS 23.228 [55].
Outputs, Required: Result indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.40.3 Nnef_ImsSessionManagement_Update service operation | Service operation name: Nnef_ImsSessionManagement_Update
Description: This service operation enables the consumer NF to modify the data channel media in a specific IMS session, such as adding or removing bootstrap data channel(s) or application data channel(s), modify media parameters for the targeted data channel(s).
Inputs, Required: Session ID, Media operation set.
Session ID: It is the identity of session that this request targeted to.
Media operation set: Includes a set of media operations commands indicating how to modify the media used in the specific session. Each media operation command contains:
- Media Correlation ID: It identifies the media component to be created.
- Operation Type: It indicates adding, updating or removing the corresponding media.
- Media Type: It indicates the type of operated media (e.g. Data Channel).
- Media Parameter set: It indicates the related media parameters. For different media, it contains different parameters:
- When the Media Type is Data Channel, it includes:
- DC Type: indicates the Data Channel Type (ADC or BDC);
- When DC Type is ADC:
- ADC Type: the ADC type (P2A, P2P, P2A2P);
- App Binding Information;
- Target ID: the public identity of the IMS Subscriber the DC is targeted;
- If P2A or P2A2P is selected, if the Operation Type indicates adding or updating the media, the MDC2 media endpoint address of the application layer is indicated.
- When DC Type is BDC:
- Target ID: the public identity of the IMS Subscriber the DC is targeted
- if the Operation Type indicates adding or updating the media, the MDC1 media endpoint address.
Inputs, Optional: Notification Target Address and Notification Correlation ID.
If the request includes a Notification Target Address, the request creates an implicit subscription to be notified for the events in Table AA.2.4.4.5-1 of TS 23.228 [55].
Outputs, Required: Result indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.40.4 Nnef_ImsSessionManagement_Delete service operation | Service operation name: Nnef_ImsSessionManagement_Delete
Description: This service operation enables the consumer NF to release the specific IMS session.
Inputs, Required: Session ID.
Inputs, Optional: None.
Outputs, Required: Result indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.40.5 Nnef_ImsSessionManagement_Notify service operation | Service operation name: Nnef_ImsSessionManagement_Notify
Description: Provides the subscribed event information to the NF Consumer.
Inputs, Required: Event ID as described in Table AA.2.4.4.5-1 of TS 23.228 [55], Notification Correlation ID.
Inputs, Optional: Session ID, Media resource information
The Session ID is included if available. The Session ID may not be available e.g. when session establishment failure is reported.
Media resource information set includes entries corresponding to each media. Each entry in the set includes the Media correlation ID and DC Media Specification. The DC Media Specification shall exist only with media type "DC" and contains additional media resource information, e.g. remote media address for MDC2 interface.
Outputs, Required: Result indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.41 Nnef_ImsParameterProvision service (ImsPP) | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.41.1 General | This service is for allowing third party to provision information which can be used for an IMS user in the IMS (e.g. RCD server address, RCD URL or RCD information for a single IMPU or wildcard IMPU as described in clause AF.2.2.6 of TS 23.228 [55]). |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.41.2 Nnef_ImsPP_Update service operation | Service operation name: Nnef_ImsPP_Update
Description: This service operation is used by the AF to update the IMS user related information (e.g. RCD server address, RCD URL or RCD information) for the target IMPU.
Inputs, Required: AF Identifier, Transaction Reference ID(s).
Inputs, Optional: Public User Identity, updated RCD properties as defined in clause AF.2.2.1 of TS 23.228 [55]).
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.41.3 Nnef_ImsPP_Create service operation | Service operation name: Nnef_ImsPP_Create
Description: This service operation is used by the AF to create the IMS user related information (e.g. RCD server address, RCD URL or RCD information) for the target IMPU.
Inputs, Required: AF Identifier, Transaction Reference ID(s).
Inputs, Optional: Public User Identity, RCD properties as defined in clause AF.2.2.1 of TS 23.228 [55]).
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.6.41.4 Nnef_ImsPP_Delete service operation | Service operation name: Nnef_ImsPP_Delete
Description: This service operation is used by the AF to delete the provisioned IMS user related information (e.g. RCD server address, RCD URL or RCD information) for the target IMPU.
Inputs, Required: AF Identifier, Transaction Reference ID(s).
Inputs, Optional: None.
Outputs, Required: Result Indication.
Outputs, Optional: None.
5.2.6A Void |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7 NRF Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.1 General | The following table shows the NRF Services and Service Operations:
Table 5.2.7.1-1: NF services provided by the NRF
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Nnrf_NFManagement
NFRegister
Request/Response
AMF, SMF, UDM, AUSF, NEF, PCF, SMSF, NSSF, UPF, BSF, CHF, NWDAF, P-CSCF, HSS, UDR, SCP, 5G DDNMF, DCCF, NSACF, MB-SMF, AF (NOTE 2), TSCTSF, EASDF, MFAF, ADRF, DCSF, MF, MRF, MRFP, IMS AS.
NFUpdate
Request/Response
AMF, SMF, UDM, AUSF, NEF, PCF, SMSF, NSSF, UPF, BSF, CHF, NWDAF, P-CSCF, HSS, UDR, SCP, 5G DDNMF, DCCF, NSACF, MB-SMF, TSCTSF, EASDF, MFAF, ADRF, DCSF, MF, MRF, MRFP, IMS AS.
NFDeregister
Request/Response
AMF, SMF, UDM, AUSF, NEF, PCF, SMSF, NSSF, UPF, BSF, CHF, NWDAF, P-CSCF, HSS, UDR, SCP, 5G DDNMF, DCCF, NSACF, MB-SMF, TSCTSF, EASDF, MFAF, ADRF, DCSF, MF, MRF, MRFP, IMS AS.
NFStatusSubscribe
Subscribe/Notify
AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, CHF, NRF, NWDAF, I-CSCF, S-CSCF, IMS-AS, SCP, UDM, TSCTSF, DCCF
NFStatusNotify
AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, CHF, NWDAF, I-CSCF, S-CSCF, IMS-AS, SCP, UDM, TSCTSF, DCCF
NFStatusUnSubscribe
AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, CHF, NRF, NWDAF, I-CSCF, S-CSCF, IMS-AS, SCP, UDM, TSCTSF, DCCF
Nnrf_NFDiscovery
Request
Request/Response
AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, CHF, NRF, NWDAF, I-CSCF, S-CSCF, IMS-AS, SCP, UDM, AF (NOTE 2), DCCF, MBSF, 5G DDNMF, TSCTSF, MRF
Nnrf_AccessToken
Get
Request/Response
AMF, SMF, PCF, NEF, NSSF, SMSF, AUSF, UDM, NWDAF, I-CSCF, S-CSCF, IMS-AS, HSS, DCCF
Nnrf_Bootstrapping
Get
Request/Response
NRF, any NF or SCP
NOTE 1: HSS_IMS services are defined in TS 23.228 [55].
NOTE 2: The AF is a trusted AF by an operator. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.2 Nnrf_NFManagement service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.2.1 General | Service description: This service enables one NF to manage its NF profile in NRF (i.e. register, update, deregister). This service also allows a consumer NF or SCP to subscribe in NRF to receive notifications regarding changes in the NF profile of other NFs. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.2.2 Nnrf_NFManagement_NFRegister service operation | Service Operation name: Nnrf_NFManagement_NFRegister.
Description: Registers the consumer NF in the NRF by providing the NF profile of the consumer NF to NRF and NRF marks the consumer NF available.
Inputs, Required: NF type, NF instance ID, FQDN or IP address of NF, Names of supported NF services (if applicable) and PLMN ID e.g. if NF needs to be discovered by other PLMNs/SNPNs.
NOTE 1: for the UPF, the addressing information within the NF profile corresponds to the N4 interface.
NOTE 2: For the purpose of the Nnrf_NFManagement service, the SCP is treated by the NRF in the same way as NFs. Specifically, the SCP is designated with a specific NF type and NF instance ID. However, the SCP does not support services and related NF profile parameters do not apply (e.g. NF Set ID, NF service set ID, Endpoint Address(es) of instance(s) of supported service(s)), see clause 6.2.6.3 of TS 23.501 [2].
Inputs, Optional:
- If the consumer NF stores Data Set(s) (e.g. UDR): Range(s) of SUPIs, range(s) of GPSIs, range(s) of external group identifiers, Data Set Identifier(s).
- If the consumer is BSF: Range(s) of SUPIs, range(s) of GPSIs, Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes, IP domain list as described in clause 6.1.6.2.21 of TS 29.510 [37], Range(s) of SUPIs, range(s) of GPSIs.
NOTE 3: Range of SUPI(s) is limited in this release to a SUPI type of IMSI as defined in TS 23.003 [33].
- If the consumer is UDM, UDR, PCF, BSF or AUSF, they can include UDM Group ID, UDR Group ID, PCF Group ID, BSF Group ID, AUSF Group ID respectively.
- For UDM and AUSF, Routing Indicator, or Routing Indicator and Home Network Public Key identifier; Home Network Identifier: PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN. Optionally, some NFs may additionally include a Home Network Identifier (including the identification of the CH with AAA Server or DCS with AAA Server) in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using a DCS with AAA Server.
- For NSSAAF, Home Network Identifier in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using credentials from a DCS with AAA Server.
- If the consumer is AMF, it includes list of GUAMI(s). In addition, AMF may include list of GUAMI(s) for which it can serve as backup for failure/maintenance.
- If the consumer is CHF, it may include Range(s) of SUPIs, Range(s) of GPSIs, optionally CHF group ID, or Range(s) of PLMNs as defined in TS 32.290 [42].
- If the consumer is CHF, primary CHF instance and the secondary CHF instance pair. If the CHF does not provide NF set ID or NF Service Set ID, it shall provide a primary CHF instance and the secondary CHF instance pair and otherwise it may do so.
- If the consumer is P-CSCF, the P-CSCF IP address(es) to be provided to the UE by SMF.
- If the consumer is HSS, IMPI range, IMPU range, HSS Group ID (as defined in TS 23.228 [55]) can be used as optional input parameters.
- For the UPF Management: UPF Provisioning Information as defined in clause 4.17.6.
- S-NSSAI(s) and the associated NSI ID(s) (if available).
- DNN(s) if the consumer is PCF or BSF. DNN(s) per S-NSSAI if the consumer is SMF, UPF or TSCTSF.
- If the consumer is a trusted AF it may include one or multiple combination(s) of S-NSSAI and DNN corresponding to the AF. In addition, it may include supported Application Id(s), Event ID(s) and Internal-Group Identifier. It may include an indication whether it supports mapping between UE IP address (IPv4 address or IPv6 prefix) and UE ID (i.e. SUPI). If acting as a VFL server or VFL client, it may include the VFL capability information per analytics ID and other related parameters as defined in clause 5.5 of TS 23.288 [50].
- Information about the location or serving scope of the NF consumer (operator specific information, e.g. geographical location, data centre).
- TAI(s).
- NF Set ID.
- NF Service Set ID.
- If the consumer is PCF or SMF, it includes the MA PDU Session capability to indicate if the NF instance supports MA PDU session or not.
- If the consumer is PCF, it includes the DNN replacement capability to indicate if the NF instance supports DNN replacement or not.
- If the consumer is PCF or SMF, it includes the slice replacement capability to indicate if the NF instance supports slice replacement or not.
- If the consumer is PCF, it may include the 5G ProSe Capability as specified in TS 23.304 [77].
- If the consumer is PCF, it may include the V2X capability as specified in TS 23.287 [73].
- If the consumer is PCF, it may include the A2X capability as specified in TS 23.256 [80].
- If the consumer is PCF, it may include the Ranging/SL Positioning Capability as specified in TS 23.586 [88].
- If the consumer is PCF, it may include the indication of PCF support of URSP delivery in EPS.
- If the consumer is NWDAF, it may include:
- Analytics ID(s) (possibly per service).
- NWDAF Serving Area information and Supported Analytics Delay per Analytics ID(s) (if available).
- Analytics aggregation capability and/ or Analytics metadata provisioning capability if such capability is provided by the NWDAF.
- Roaming exchange capability if such capability is provided by NWDAF.
- If the consumer is NWDAF containing MTLF, it may also include the ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator per Analytics ID(s), if available (see clause 5.2 of TS 23.288 [50]).
- If the consumer is NWDAF containing MTLF and it supports the ML model training for LMF-based AI/ML positioning, it includes the LMF-based AI/ML positioning indication.
- If the consumer is NWDAF containing MTLF with Horizontal Federated Learning (HFL) capability, it includes FL capability information per analytics ID containing FL capability type (i.e. FL client and/or FL server, if available) and Time interval supporting FL, if available (see clause 5.2 of TS 23.288 [50]).
- If the consumer is NWDAF containing MTLF with Vertical Federated Learning (VFL) capability, it includes VFL capability information per supported Analytics ID and other related parameters as defined in clause 5.2 of TS 23.288 [50].
- If the consumer is NWDAF containing MTLF with ML Model Accuracy checking capability, it includes ML Model Accuracy checking capability for ML model accuracy monitoring (see clause 5.2 of TS 23.288 [50]).
- If the consumer is NWDAF containing AnLF with Analytics Accuracy checking capability, it includes Analytics Accuracy checking capability for Analytics Accuracy Monitoring (see clause 5.2 of TS 23.288 [50]).
- It may also include NF Set ID and NF Type of the NF data sources, if data management service is available.
Details about NWDAF specific information are described in clause 6.3.13 of TS 23.501 [2].
- If the consumer is ADRF, it may include:
- Data and analytics storage and retrieval capability if available.
- ML model storage and retrieval capability if available.
Details about ADRF specific information are described in clause 6.3.20 of TS 23.501 [2].
- If the consumer is NEF, it may include Event ID(s) supported by AFs, the S-NSSAI and DNN corresponding to the untrusted AF served by the NEF, Application Identifier(s) supported by AFs, range(s) of External Identifiers, or range(s) of External Group Identifiers, or the domain names served by the NEF. It may also include an indication whether the untrusted AF supports mapping between UE IP address (IPv4 address or IPv6 prefix) and external UE ID (i.e. GPSI). If the consumer is local NEF, it may include parameters of list of supported TAI or list of supported DNAI additionally. For an untrusted AF reachable through the NEF, which is capable to act as VFL client or VFL server, the NEF may also include untrusted AF's VFL capability information per Analytics ID and other related parameters as defined in clause 6.2H.2.1.2 of TS 23.288 [50].
- If the consumer is a NSACF, it includes the S-NSSAI(s) of the PLMN or SNPN where the NSACF is located, the NSAC Service Area Identifier(s) n and NSACF service capabilities. Details about NSAC Service Area Identifier and NSACF service capabilities are described in clause 6.3.22 of TS 23.501 [2].
- Notification endpoint for default subscription for each type of notification that the NF is interested in receiving.
- Endpoint Address(es) of instance(s) of supported service(s).
- NF capacity information.
- NF priority information.
- If consumer is NF, SCP domain the NF belongs to.
- If the consumer is SCP, it may include:
- SCP domain(s) the SCP belongs to.
- Remote PLMNs reachable through SCP.
- Endpoint addresses or Address Domain(s) (e.g. IP Address or FQDN ranges) accessible via the SCP.
- NF sets of NFs served by the SCP.
- If the consumer NF is MB-SMF, it may include MB-SMF service area and the MBS Session ID(s), Area Session ID(s), the corresponding MBS service area(s) if available, as specified in TS 23.247 [78].
- If the consumer is DCCF, the request may include DCCF Serving Area information, NF type of the NF data source, NF Set ID of the NF data sources, support for relocation of data subscription. Details about DCCF discovery and selection are described in clause 6.3.19 of TS 23.501 [2].
- If the consumer is EASDF, it may include S-NSSAI, DNN, N6 IP address of the PSA UPF, Supported DNS security protocols of EASDF, location as per NF profile and DNAI (if exists).
- For ON-SNPN, if the consumer is AMF, Capability to support SNPN Onboarding, or, if the consumer is SMF, Capability to support User Plane Remote Provisioning.
- If the consumer is NEF, it may include the support for UAS NF functionality, the capability to support Multi-member AF session with required QoS and the capability to support member UE selection assistance functionality.
- If the consumer is UPF and UPF can expose NAT information, it may include the range of IP addresses the NAT uses towards the DN (e.g. public IP addresses). This IP address range may be on a per IP domain, DNN and S-NSSAI.
- If the consumer is UPF, it may include the supported protocol to be used to measure N6 delay for the connection between the UPF and the measurement endpoint in the DN (as defined in clause 5.8.2.23 of TS 23.501 [2]).
- If the consumer is DCSF, it may include an IMS domain name or a list of IMS domain names it serves, IMPU range of calling identity or called identity it serves, or IMPI range it serves.
- If the consumer is MF, it includes the data channel media capabilities it supports. It may also include MF location information as specified in TS 23.228 [55].
- If the consumer is MRF or MRFP, it includes the list of supported IMS media services (as defined in TS 23.228 [55]).
- If the consumer is IMS AS, it may include the list of supported IMS DC events.
- If the consumer is SMF, it may include the capability of supporting Local Offloading Management.
- If the consumer is SMF and SMF supports Local Offloading Management, it may include supported Local Offloading Management service areas.
Outputs, Required: Result indication.
Outputs, Optional: None.
See clause 5.21.2.1 of TS 23.501 [2], the AMF registers itself to NRF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.2.3 Nnrf_NFManagement_NFUpdate service operation | Service Operation name: Nnrf_NFManagement_NFUpdate.
Description: Provides the updated NF profile of NF consumer to NRF.
Inputs, Required: NF instance ID.
Inputs, Optional: If replacing the full NF profile, the full NF profile shall be provided. If updating parts of the NF profile, the NF profile elements that needs to be updated shall be provided.
Outputs, Required: Result indication.
Outputs, Optional: None.
See clause 5.21.2.1 of TS 23.501 [2], the AMF adds or updates the associated GUAMI(s). |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.2.4 Nnrf_NFManagement_NFDeregister service operation | Service Operation name: Nnrf_NFManagement_NFDeregister
Description: Inform the unavailability of NF consumer to NRF.
Inputs, Required: NF Instance ID, Reason indication.
Inputs, Optional: None.
Outputs, Required: Result indication.
Outputs, Optional: None.
See clause 5.21.2.2 of TS 23.501 [2], the AMF deregister itself from NRF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.2.5 Nnrf_NFManagement_NFStatusSubscribe service operation | Service Operation name: Nnrf_NFManagement_NFStatusSubscribe.
Description: Consumer can subscribe to be notified of the following:
- Newly registered NF along with its NF services.
- Updated NF profile.
- Deregistered NF.
Inputs, Required: callback URI.
Inputs, Optional:
- PLMN ID of the target NF/NF service, in the case of the subscription to the status of NF/NF service instance(s) in home PLMN from the serving PLMN, or PLMN ID and NID in the case of SNPN (see clause 5.30.2.9.3 of TS 23.501 [2]).
- Home Network Identifier: PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN. Optionally, some NFs may additionally include a Home Network Identifier (including the identification of the CH with AAA Server or DCS with AAA Server) in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using a DCS with AAA Server.
- Validity Time, in case to indicate the time instant after which the subscription becomes invalid.
- For updated NF profile subscription, conditions that trigger a notification from NRF. Includes monitored attributes in the NF profile (changes trigger a notification) or unmonitored attributes in the NF profile (changes do not trigger a notification).
- The following parameters are mutually exclusive:
- NF Type (if NF status of a specific NF type is to be monitored).
- NF Instance ID or NF Instance ID list (if NF status of a specific NF instance or a list of NF instance is to be monitored).
- NF Service name (if NF status for NF which exposes a given NF service is to be monitored).
- NF Set (if NF status of a set of NF Instances belonging to a certain NF Set is to be monitored).
- NF Service Set (if the status of a set of NF Service Instances belonging to a certain NF Service Set is to be monitored).
- NF Group (if the NF status of NF Instances identified by a NF (UDM, AUSF, PCF, BSF, CHF, HSS or UDR) Group Identity is to be monitored).
- NF load status information, capacity and priority information of NF and NF Services, etc as described in Table 6.22.2-2 and Table 6.22.2-5 of TS 23.288 [50].
- SCP Domain (if the status of NF or SCP instances belonging to a certain SCP domain is to be monitored).
- For the UPF Management defined in clause 4.17.6: UPF Provisioning Information as defined in that clause.
- For AMF, the consumer may include list of GUAMI(s), or AMF Set or AMF Region, or TAIs.
- For SMF, the consumer may include list of TAIs.
- S-NSSAI(s) and the associated NSI ID(s) (if available).
- For NWDAF, the consumer may include:
- Analytics ID(s) (possibly per service).
- TAI(s).
- NF Set ID, NF Type of NF data sources.
- Analytics aggregation capability and/or Analytics metadata provisioning capability.
- ML Model Accuracy checking capability.
- Analytics Accuracy checking capability.
- Roaming exchange capability.
- For NWDAF containing MTLF, the consumer may also include the ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator per Analytics ID(s), if available (see clause 5.2 of TS 23.288 [50]).
- For NWDAF containing MTLF that supports the ML model training for LMF-based AI/ML positioning, the consumer (i.e. LMF) may also include the LMF-based AI/ML positioning indication (indicating that the NWDAF containing MTLF supports ML model training for LMF-based AI/ML positioning).
- For NWDAF containing MTLF with Horizontal Federated Learning (HFL) capability, the consumer may include FL capability type (i.e. FL client and/or FL server, if available), Time Period of Interest, if available (see clause 5.2 of TS 23.288 [50]).
- For NWDAF containing MTLF with Vertical Federated Learning (VFL) capability, the consumer may include VFL capability information per Analytics ID and other related parameters as defined in clause 5.2 of TS 23.288 [50].
Details about NWDAF discovery and selection are described in clause 6.3.13 of TS 23.501 [2].
- For ADRF, the consumer may include:
- Data and analytics storage and retrieval capability.
- ML model storage and retrieval capability.
- For NEF, the consumer may include Event ID(s) provided by AF. The request may also include the required AF's VFL capability type (i.e. VFL client and/or VFL server, if available) and other related parameters as defined in clause 6.2H.2.1 of TS 23.288 [50].
- For DCCF, the consumer may include:
- TAI(s).
- NF type of the NF data sources.
- NF Set ID of the NF data sources.
- Support for relocation of data subscription.
Details about NWDAF discovery and selection are described in clause 6.3.19 of TS 23.501 [2].
- For trusted AF as VFL client or VFL server, the consumer may include VFL capability information per analytics ID and other related parameters as defined in clause 5.5 of TS 23.288 [50].
Outputs, Required: When the subscription is accepted: Subscription Correlation ID (required for management of this subscription), Validity Time.
Outputs, Optional: None.
NOTE: Alternatively, other means such as OA&M can also be used to subscribe for NF status. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.2.6 Nnrf_NFManagement_NFStatusNotify service operation | Service Operation name: Nnrf_NFManagement_NFStatusNotify.
Description: NRF notifies subscribed consumers of the following:
- Newly registered NF along with its NF services.
- Updated NF profile.
- Deregistered NF.
Inputs, Required: Notification Event type; NF instance ID; for newly registered NF, NF profile; for updated NF, NF profile or NF profile changes.
NOTE: See clause 6.1.6.3.6 of TS 29.510 [37] for the detailed use of Notification Event type.
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.2.7 Nnrf_NFManagement_NFStatusUnsubscribe service operation | Service Operation name: Nnrf_NFManagement_NFStatusUnsubscribe
Description: Consumer can unsubscribe from being notified of newly registered NF along with its NF services and other events types described in the Nnrf_NFManagement_NFStatusSubscribe service operation (see clause 5.2.7.2.5).
Inputs, Required: Subscription Correlation ID.
Inputs, Optional: None.
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
NOTE: Alternatively, other means such as OA&M can also be used to unsubscribe for NF status. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.3 Nnrf_NFDiscovery service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.3.1 General | Service description: This service enables one NF or SCP to discover a set of NF instances with specific NF service or a target NF type or one or more SCPs. The service also enables one NF service or SCP to discover a specific NF service. The service operations defined below allow the NF/NF services or SCP to communicate with NRF.
This service also enables an SCP to discover SCPs.
NOTE: For the purpose of the Nnrf_NFDiscovery service, the SCP is treated in the same way as NFs. It is designated with a specific NF type. However, the SCP does not support services. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.3.2 Nnrf_NFDiscovery_Request service operation | Service operation name: Nnrf_NFDiscovery_Request
Description: provides the IP address or FQDN of the expected NF instance(s) and if present in NF profile, the Endpoint Address(es) of NF service instance(s) to the NF service consumer or SCP.
Inputs, Required: one or more target NF service Name(s), NF type of the target NF, NF type of the NF service consumer.
If the NF service consumer intends to discover an NF service producer providing all the standardized services, it provides a wildcard NF service name.
Inputs, Optional:
- S-NSSAI and the associated NSI ID (if available), DNN, target NF/NF service PLMN ID (or realm in the case of network specific identifier type SUCI/SUPI, see clause 4.17.5a), NRF to be used to select NFs/services within HPLMN or Credentials Holder, Serving PLMN ID (or PLMN ID and NID in the case of SNPN, see clause 4.17.5a), the NF service consumer ID, preferred target NF location, TAI.
NOTE 1: For network slicing the NF service consumer ID is a required input.
- FQDN for the S5/S8 interface of the SMF+PGW-C, to discover the N11/N16 interface of the SMF+PGW-C in the case of EPS to 5GS mobility.
- If the target NF stores Data Set(s) (e.g. UDR, BSF): SUPI, GPSI, IMPI, IMPU, Data Set Identifier(s). (UE) IPv4 address, IP domain or (UE) IPv6 Prefix.
NOTE 2: GPSI is relevant for BSF.
NOTE 3: If the request includes a subscriber identifier the NRF may need to use the association between the supplied subscriber identifier and the appropriate NF Group ID as described in clause 6.3.1 of TS 23.501 [2] to determine the applicable set of NF instances for the response.
NOTE 4: The (UE) IPv4 address or (UE) IPv6 Prefix is provided for BSF discovery: in that case the NRF looks up for a match within one of the Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes provided by BSF(s) as part of the invocation of Nnrf_NFManagement_NFRegister operation. The NRF is not meant to store individual (UE) IPv4 addresses or (UE) IPv6 prefixes.
- If the target NF is UDM or AUSF, the request may include the UE's Routing Indicator, or the UE's Routing Indicator and Home Network Public Key identifier.
- If the target UDM or NF is AUSF, the request may include the UE's HNI: PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN. Optionally, some NFs may additionally include a Home Network Identifier in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using a DCS with AAA Server.
- If the target NF is NSSAAF, the request may include Home Network Identifier in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using credentials from a DCS with AAA Server.
- If the target NF is AMF and the consumer NF is MB-SMF for broadcast service, the request includes TAI(s) (see clause 7.3 of TS 23.247 [78]).
- If the target NF is AMF and the consumer NF is other than MB-SMF, the request may include:
- AMF region, AMF Set, GUAMI and Target TAI(s).
- If the target NF is UDR or UDM or AUSF or PCF or BSF, the request may include UDR Group ID or UDM Group ID or AUSF Group ID or PCF Group ID or BSF Group ID respectively.
NOTE 5: It is assumed that the corresponding NF service consumer is either configured with the corresponding Group ID or it received it via earlier Discovery output.
- If the target NF is UDM, the request may include SUPI, GPSI, Internal Group ID and External Group ID.
- If the target NF is UPF, the request may include SMF Area Identity, UE IPv4 Address/IPv6 Prefix, supported ATSSS steering functionality, supported MoQ Relay functionality, the supported UPF event exposure service, the supported Event IDs that can be subscribed, supported operator configurable UPF capabilities, support of NAT information exposure functionality and support of IP or MAC filter-based packet detection functionality. And if UPF can expose NAT information, the UE IPv4 address/IPv6 Prefix seen by the DN (e.g. a Public IP address).
NOTE 6: If UE's IPv4 address or IPv6 Prefix is provided for UPF discovery, then the NRF looks up for a match within one of the Range(s) of IPv4 addresses or IPv6 prefixes provided by UPF in the NF profile at the invocation of Nnrf_NFManagement_NFRegister operation. The NRF is not meant to store the UE's individual IPv4 addresses or IPv6 prefixes.
NOTE 7: Discovering UPF at PDU Session Establishment time and creating the N4 association assumes full connectivity between SMF and UPFs.
- If the target NF is CHF, the request may include SUPI, GPSI or optionally CHF group ID as specified in TS 32.290 [42].
- If the target NF is PCF or SMF, the request may include the MA PDU Session capability to indicate that a NF instance supporting MA PDU session capability is requested.
- If the target NF is PCF, the request may include the DNN replacement capability to indicate that a NF instance supporting DNN replacement capability is preferred.
- If the target NF is PCF or SMF, the request may include the slice replacement capability to indicate that a NF instance supporting slice replacement capability is preferred.
- If the target NF is PCF, the request may include the 5G ProSe Capability as specified in TS 23.304 [77].
- If the target NF is PCF, the request may include the V2X capability as specified in TS 23.287 [73].
- If the target NF is PCF, the request may include the A2X capability as specified in TS 23.256 [80].
- If the target NF is PCF, the request may include the URSP delivery in EPS capability.
- If the target NF is PCF, the request may include the Ranging/SL Positioning Capability as specified in TS 23.586 [88].
- If the target NF is NWDAF, the request may include:
- Analytics ID(s) (possibly per service).
- TAI(s).
- Analytics aggregation capability and/or Analytics metadata provisioning capability.
- A Real-Time Communication Indication per Analytics ID, NF Set ID and NF Type of the NF data sources.
- Roaming exchange capability if data/analytics exchange between PLMNs is needed.
- The S-NSSAI(s), Area(s) of Interest of the Trained ML Model required and NF consumer information when the target is an NWDAF containing MTLF.
- LMF-based AI/ML positioning indication when the target is an NWDAF containing MTLF.
- For HFL, required FL capability type (i.e. FL server, FL client, if available) and Time period of interest when the target is an NWDAF containing MTLF with HFL capability. When the target is an NWDAF containing MTLF with HFL client capability, NF Set ID(s) of data source and NF type(s) where data can be collected as input for local model training may be included.
- Required VFL capability type (i.e. VFL server, VFL client, if available) and other related parameters as defined in clause 5.2 of TS 23.288 [50].
- If the target NF is NWDAF containing MTLF with ML Model Accuracy checking capability, it includes ML Model Accuracy checking capability for ML model Accuracy Monitoring (see clause 5.2 of TS 23.288 [50]).
- If the target NF is NWDAF containing AnLF with Analytics Accuracy checking capability, it includes Analytics Accuracy checking capability for Analytics Accuracy Monitoring (see clause 5.2 of TS 23.288 [50]).
Details about NWDAF discovery and selection are described in clause 6.3.13 of TS 23.501 [2].
NOTE 8: Analytics metadata provisioning capability is only applicable when NF service consumer is NWDAF.
NOTE 9: NF consumer information such as vendor ID is defined in stage 3.
- If target NF is ADRF, the request may include:
- Data and analytics storage and retrieval capability.
- ML model storage and retrieval capability.
Details about ADRF discovery and selection are described in clause 6.3.20 of TS 23.501 [2].
- If the target NF is HSS, the request may include IMPI and/or IMPU and/or HSS Group ID.
- If the NF service consumer needs to discover NF service producer instance(s) within an NF instance, the request includes the target NF Instance ID and NF Service Set ID of the producer.
- If the NF service consumer needs to discover NF service producer instance(s) in an equivalent NF Service Set within an NF Set, the request includes the identification of the equivalent NF service Set and NF Set ID of producer.
NOTE 10: TS 29.510 [37] specifies the mechanism to identify equivalent NF Service Sets.
- If the NF service consumer needs to discover NF service producer instance(s) in the NF Set, the request includes the target NF Set ID of the producer.
- If the target NF is SMF, the request may include:
- the UE location (TAI); or
- information about the location, serving scope of SMF (operator specific information, e.g. geographical location, data centre) or Local Offloading Management service area (if SMF supports Local Offloading Management) considering UE location; or
- TAI list.
- If the target NF is P-CSCF, the request may include UE location information, UE IP address/IP prefix, Access Type.
- If the target NF is NEF, the request may include Event ID(s) provided by AF and optional AF identification as described in clause 6.2.2.3 of TS 23.288 [50]. The request may also include required AF's VFL capability type (i.e. VFL server or VFL client, if available), optional Time Period of Interest, per Analytics ID, VFL interoperability indicator, per Analytics ID, optionally supported Feature IDs and Service Area. When the consumer is an AF, the request may include an External Identifier, External Group Identifier, or a domain name. If the target NF is local NEF, the request may include the parameters of list of supported TAI or list of supported DNAI additionally.
- If the target NF is SMF, the request may include the Control Plane CIoT 5GS Optimisation Indication or User Plane CIoT 5GS Optimisation Indication.
- If the target NF is a NSACF, the request may include the S-NSSAI(s) of the PLMN or SNPN where the NSACF is located , the NSAC Service Area Identifier and NSACF service capability. Details about NSACF discovery and selection are described in clause 6.3.22 of TS 23.501 [2].
- If the target NF is SCP, the request may include information about:
- SCP domain(s).
- Remote PLMN reachable through SCP.
- Endpoint addresses or Address Domain(s) (e.g. IP Address or FQDN ranges) accessible via the SCP.
- NF sets of NFs served by the SCP.
- If the target NF is MB-SMF, the request may include UE location (i.e. TAI), MBS Session ID and Area Session ID. Details about MB-SMF discovery and selection are described in TS 23.247 [78].
- If the target NF is 5G DDNMF, the request may include SUPI, IP Address or FQDN of 5G DDNMF.
- If the target NF is DCCF, the request may include TAI(s), NF type of the NF data sources, NF Set ID of the NF data sources, support for relocation of data subscription. Details about DCCF discovery and selection are described in clause 6.3.19 of TS 23.501 [2].
- If the target NF is EASDF, the request may include S-NSSAI, DNN, N6 IP address of the PSA UPF, Supported DNS security protocols, location as per NF profile and DNAI(if exist). Details about EASDF discovery and selection are described in clause 6.3.23 of TS 23.501 [2].
- If the target NF is AMF, the request may include the support of SNPN Onboarding to indicate whether the target NF instance supports SNPN Onboarding or not.
- If the target NF is SMF, the request may include the support of User Plane Remote Provisioning to indicate whether the target NF instance supports User Plane Remote Provisioning or not as described in clause 5.30.2.10.4.3 of TS 23.501 [2].
- If the target NF is NEF, the request may include the support of UAS NF functionality, the capability to support Multi-member AF session with required QoS and the capability to support member UE selection assistance functionality.
- If the target NF is NSSAAF, the request may include SUPI or Internal Group ID.
- If the target NF is DCSF, the request may include IMPU of calling party, SIP URI or Tel URI of called party.
- If the target NF is MF, the request may include the list of required data channel media capabilities or MF location information as specified in TS 23.228 [55].
- If the target NF is IMS AS, the request may include the list of supported IMS DC events.
- If the target NF is MRF or MRFP, it includes the list of required IMS media services (as defined in TS 23.228 [55]).
- If the target NF is trusted AF as VFL client or VFL server, the request may include VFL capability information per analytics ID and other related parameters as defined in clause 5.5 of TS 23.288 [50].
- If the target NF is in another PLMN or domain, the request may include an indication of "support of the indirect communication with delegated discovery with NF selection at target domain feature" and/or an indication of "support of indirect communication without delegated discovery with NF selection at target domain feature".
Outputs, Required:
- One of the following:
- A set of NF instance profiles; or
- an indication that "indirect communication with delegated discovery with NF selection at target domain is requested"; or
- an indication that "indirect communication without delegated discovery with NF selection at target domain is requested" together with a set of NF instance profiles;
- a validity period for the discovery result.
The set of NF instance profiles shall contain per NF Instance: NF type, NF instance ID, FQDN or IP address(es) of the NF instance and if applicable, a list of services instances, where each service instance has a service name, a NF service instance ID and optionally Endpoint Address(es)
Endpoint Address(es) may be a list of IP addresses or an FQDN for the NF service instance.
NOTE 11: SCPs does not have any service instances.
Outputs, Optional: Per NF instance, other information in the NF profile listed in clause 6.2.6 of TS 23.501 [2] related to the NF instance, such as:
- NF load information.
- NF capacity information.
- NF priority information.
- If the target NF stores Data Set(s) (e.g. UDR): Range(s) of SUPIs, range(s) of GPSIs, range(s) of external group identifiers, Data Set Identifier(s). If the target NF is BSF or P-CSCF: Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes, Range(s) of SUPIs, range(s) of GPSIs.
NOTE 12: Range of SUPI(s) is limited in this release to a SUPI type of IMSI as defined in TS 23.003 [33].
- If the target NF is UDM, UDR, PCF, BSF or AUSF, they can include UDM Group ID, UDR Group ID, PCF Group ID, BSF Group ID, AUSF Group ID respectively.
- If the target NF is HSS, it can include HSS Group ID.
- For UDM and AUSF, Routing Indicator, or Routing Indicator and Home Network Public Key identifier.
- If the target NF is AMF, it includes list of GUAMI(s). In addition, it may include list of GUAMI(s) for which it can serve as backup for failure/maintenance.
- If the target NF is CHF, it includes primary CHF instance and the secondary CHF instance pair(s), if configured in CHF instance profile.
- For the UPF Management: UPF Provisioning Information as defined in clause 4.17.6.
- S-NSSAI(s) and the associated NSI ID(s) (if available).
- Information about the location or serving scope of the target NF (operator specific information, e.g. geographical location, data centre).
- TAI(s).
- PLMN ID.
- If the target is PCF or SMF, it includes the MA PDU Session capability to indicate if the NF instance supports MA PDU session or not.
- If the target is PCF, it includes the DNN replacement capability to indicate if the NF instance supports DNN replacement or not.
- If the target NF is NWDAF, it may include:
- Analytics ID(s) (possibly per service).
- LMF-based AI/ML positioning indication (indicating that the NWDAF supports ML model training for LMF-based AI/ML positioning).
- NF Set ID and NF Type of the NF data sources, if available, NWDAF Serving Area information.
- Analytics aggregation capability and/or Analytics metadata provisioning capability, if such capability is provided by the NWDAF.
- Supported Analytics Delay per Analytics ID.
- If the target NF is NWDAF, it may also include the ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator per Analytics ID(s), if available (see clause 5.2 of TS 23.288 [50]).
- If the target NF is NWDAF with FL capability, it may also include FL capability information per analytics ID containing FL capability type (i.e. FL server and/or FL client, if available) and Time interval supporting FL, if available (see clause 5.2 of TS 23.288 [50]).
- If the target NF is NWDAF with the VFL capability, it may include VFL capability information per Analytics ID containing VFL capability type (i.e. VFL server, VFL client, or both, if available) and optional Time interval supporting VFL, if available. When the VFL capability type indicates VFL client, the NWDAF also includes the VFL interoperability indicator per Analytics ID and optionally supported Feature IDs (see clause 5.2 of TS 23.288 [50]).
Details about NWDAF specific information are described in clause 6.3.13 of TS 23.501 [2].
NOTE 13: The Supported Analytics Delay is provided for an Analytics ID only when the NRF had received Real-Time Communication Indication for this Analytics ID in the NWDAF discovery request.
- If the target is a trusted AF, it includes one or multiple combination(s) of the S-NSSAI and DNN corresponding to the AF. In addition, it may include supported Application Id(s), Event ID(s) supported by the AF and Internal-Group Identifier. If the target is a trusted AF as VFL server or VFL client, it may also include VFL capability information per Analytics ID and other related parameters as defined in clause 5.5 of TS 23.288 [50].
- NF Set ID.
- NF Service Set ID.
- If the target NF is SMF, it may include the SMF(s) Service Area and/or Local Offloading Management service area if SMF supports Local Offloading Management.
NOTE 14: If neither SMF Service Area nor serving scope of SMF is provided, the AMF assumes that the SMF can serve the whole PLMN. This does not apply to SMF(s) Local Offloading Management service area.
- If the target NF is SMF, it may include the capability of supporting Local Offloading Management.
- If the target NF is P-CSCF, it includes P-CSCF FQDN(s) or IP address(es) and optional Access Type(s) associated with each P-CSCF.
- If the target NF is NEF, it may include Event ID(s) provided by AF and/or it may include AF's VFL capability type (i.e. VFL client, if available) and optional Time Period of Interest, per Analytics ID, VFL interoperability indicator, per Analytics ID, optionally supported Feature IDs, Service Area and/or it includes one or multiple combination(s) of the S-NSSAI and DNN corresponding to the untrusted AF served by the NEF.
- SCP domain the NF belongs to.
NOTE 15: Only one SCP domain is registered in NF profile for an NF.
- If the target is SCP:
- SCP domain(s).
- Remote PLMNs reachable through SCP.
- Endpoint addresses or Address Domain(s) (e.g. IP Address or FQDN ranges) accessible via the SCP.
- NF sets of NFs served by the SCP.
- If the target NF is 5G DDNMF, it may include IP Address or FQDN of 5G DDNMF.
- If the target NF is MB-SMF, it may include the MBS Session ID(s), Area Session ID(s), corresponding MBS service area(s) as described in TS 23.247 [78].
- If the target NF is DCCF, it includes DCCF serving area information, NF type of the NF data sources, NF Set ID of the NF data sources, support for relocation of data subscription. Details about DCCF specific information are described in clause 6.3.19 of TS 23.501 [2].
- If an indication that "indirect communication with delegated discovery with NF selection at target domain is requested" or an "indication that "indirect communication without delegated discovery with NF selection at target domain is requested" is provided, optionally:
- an indication that the reply applies to all NF types; and/or
- the address of an SCP where to send the request.
See clause 4.17.4 and 4.17.5 for details on the usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.4 Nnrf_AccessToken_service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.4.1 General | This service provides OAuth2 2.0 Access Tokens for NF to NF authorization as defined in TS 33.501 [15]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.4.2 Nnrf_AccessToken_Get Service Operation | See TS 33.501 [15]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.5 Nnrf_Bootstrapping service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.5.1 General | Service Description: The Nnrf_Bootstrapping service lets NF Service Consumers of the NRF know about the services endpoints it supports, the NRF Instance ID and NRF Set ID if the NRF is part of an NRF set, by using a version-independent URI endpoint that does not need to be discovered by using a Discovery service |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.7.5.2 Nnrf_Bootstrapping_Get service operation | Service operation name: Nnrf_Bootstrapping_Get
Description: Get the NRF service instances, their addresses and associated data.
Inputs, Required: None.
Inputs, Optional: None.
Outputs, Required: NRF service instances and their endpoint addresses.
Outputs, Optional: NF Set ID, NFR instance ID, Oath2 requirement for authorization, NFR status. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8 SMF Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.1 General | The following table shows the SMF Services and SMF Service Operations.
Table 5.2.8.1-1: NF services provided by the SMF
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Nsmf_PDUSession
Create
Request/Response
V-SMF/I-SMF
Update
Request/Response
V-SMF/I-SMF, H-SMF
Release
Request/Response
V-SMF/I-SMF
CreateSMContext
Request/Response
AMF
UpdateSMContext
Request/Response
AMF
ReleaseSMContext
Request/Response
AMF
SMContextStatusNotify
Subscribe/Notify
AMF
StatusNotify
Subscribe/Notify
V-SMF/I-SMF
ContextRequest
Request/Response
AMF, V-SMF/I-SMF, SMF
ContextPush
Request/Response
SMF
SendMOData
Request/Response
AMF
TransferMOData
Request/Response
V-SMF/I-SMF
TransferMTData
Request/Response
SMF, H-SMF
Nsmf_EventExposure
Subscribe
Subscribe/Notify
NEF, AMF, NWDAF, SMF, EIF
Unsubscribe
NEF, AMF, NWDAF, SMF, EIF
Notify
NEF, AMF, NWDAF, EIF
AppRelocationInfo
AF
Nsmf_NIDD
Delivery
Request/Response
NEF
Nsmf_TrafficCorrelation
Notify
Subscribe/Notify
NEF |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2 Nsmf_PDUSession Service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.1 General | Service description: This service operates on the PDU Sessions. The following are the key functionalities of this NF service:
- (between AMF and SMF) Creation / Deletion / Modification of AMF-SMF interactions for PDU Sessions;
The resource handled between AMF and SMF via Create / Update / Release SM context operations corresponds to the AMF-SMF association for a PDU Session;
When the AMF has got no association with an SMF to support a PDU Session, the AMF creates such association via the Nsmf_PDUSession_CreateSMContext operation. The context created is identified via the SM Context ID. Otherwise (e.g. at hand-over between 3GPP and Non 3GPP access) the AMF uses the Nsmf_PDUSession_UpdateSMContext operation.
NOTE 1: In TS 29.502 [36] SM Context ID is referred to as smContextRef for N11 and pduSessionRef and pduSessionUri for N16.
When the UE is handed-over from an (old) AMF towards another (new) AMF, the old AMF provides the new AMF with the SMF addressing information corresponding to the AMF-SMF association related with each PDU Session of that UE. The new AMF can thus further act upon the association with the SMF via Nsmf_PDUSession_UpdateSMContext and Nsmf_PDUSession_ReleaseSMContext operations. This may take place:
- at inter AMF change due to AMF planned maintenance or due to AMF failure described in clause 5.21.2 of TS 23.501 [2];
- at inter AMF mobility in CM-CONNECTED state described in clause 4.9.1.3;
- at inter AMF mobility in CM-IDLE state described in clause 4.2.2.2.
- (between AMF and SMF) Passing MO Small Data from AMF to SMF in clause 4.24.1.
- (between V-SMF and H-SMF) Creation / Deletion / Modification of PDU Sessions;
- (between V-SMF/I-SMF and (H-)SMF) Transferring MO Small Data from V-SMF/I-SMF to (H-)SMF in clause 4.25.4.
- (between V-SMF/I-SMF and (H-)SMF) Transferring MT Small Data from (H-)SMF to V-SMF/I-SMF in clause 4.24.5.
Even though the V-SMF creates the PDU Session resource onto the H-SMF, each of the V-SMF and of the H-SMF needs to be able to modify a PDU Session and/or to ask for PDU Session Release. Thus, at Nsmf_PDUSession_Create, V-SMF informs the H-SMF about addressing information for its corresponding PDU Session resource, allowing H-SMF to use later on the Nsmf_PDUSession_Update and Nsmf_PDUSession_Release and Nsmf_PDUSession_StatusNotify operations.
NOTE 2: The PDU Session resource in V-SMF is created when the AMF requests to create SM context of this PDU Session
NOTE 3: H-SMF also informs the consumer (V-SMF) about addressing information about its PDU Session resource, but this is part of normal resource creation operation in REST and not specific to this service. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.2 Nsmf_PDUSession_Create service operation | Service operation name: Nsmf_PDUSession_Create.
Description: Create a new PDU Session in the H-SMF or SMF or create an association with an existing PDN connection in the home SMF+PGW-C.
Input, Required: SUPI, V-SMF ID or I-SMF ID, V-SMF SM Context ID or I-SMF SM Context ID, DNN, V-CN Tunnel Info or I-UPF Tunnel Info, addressing information allowing the H-SMF to request the V-SMF to issue further operations about the PDU Session or addressing information allowing the SMF to request the I-SMF to issue further operations about the PDU Session, Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.18 of TS 23.501 [2]).
Input, Optional: S-NSSAI, Alternative S-NSSAI, PCO, Requested PDU Session Type, 5GSM Core Network Capability, Requested SSC mode, PDU Session ID, Number Of Packet Filters, UE location information, subscription get notified of PDU Session status change, PEI, GPSI, AN type, PCF ID, PCF Group ID, DNN Selection Mode, UE's Routing Indicator optionally with Home Network Public Key identifier or UDM Group ID for the UE, Always-on PDU Session Requested, Control Plane CIoT 5GS Optimisation Indication, information provided by V-SMF related to charging in home routed scenario (see TS 32.255 [45]), AMF ID, EPS Bearer Status, extended NAS-SM timer indication, DNAI list supported by I-SMF (from I-SMF to SMF), HO Preparation Indication. MA PDU request indication, MA PDU Network-Upgrade Allowed indication, Indication on whether the UE is registered in both accesses; QoS constraints from the VPLMN (as defined in clause 5.7.1.11 of TS 23.501 [2]), Satellite backhaul category, Request for notification of SM Policy Association establishment and termination, PCF binding information, Disaster Roaming service indication, HR-SBO request indication, VPLMN EASDF/Local DNS Server/Resolver IP address, DNS security information of VPLMN EASDF/Local DNS Server/Resolver, [ECS Address Configuration Information associated with PLMN ID of visited network], Indication of UE supports non-3GPP access path switching, [URSP rule enforcement reports], NG RAN QoS monitoring capability (as defined in clause 5.45.1 of TS 23.501 [2]), EASDF IP address (from I-SMF to SMF), DNS security information of EASDF (from I-SMF to SMF), Local Offloading Management support indication (from I-SMF to SMF), Local Offloading Management allowed indication (from I-SMF to SMF).
Output, Required: Result Indication and if success a SM Context ID and in addition: QFI(s), QoS Profile(s), Session-AMBR, QoS Rule(s), QoS Flow level QoS parameters if any for the QoS Flow(s) associated with the QoS rule(s), H-CN Tunnel Info or PSA UPF Tunnel Info, Enable pause of charging indication, Selected PDU Session Type and SSC mode.
Output, Optional: PDU Session ID, S-NSSAI, Cause, PCO, UE IP address, IPv6 Prefix allocated to the PDU Session, information needed by V-SMF in the case of EPS interworking such as the PDN Connection Type, EPS bearer context(s), linked EBI, Reflective QoS Timer, Always-on PDU Session Granted, information provided by H-SMF related to charging in home routed scenario (see TS 32.255 [45]), DNAI(s) of interest for this PDU Session (from SMF to I-SMF), indication of multi-homing support (from SMF to I-SMF). MA PDU session Accepted indication, Indication on whether Small Data Rate Control applies or not, HR-SBO authorization result, VPLMN Specific Offloading Information for HR-SBO, Offload Identifier(s), HPLMN DNS Server address, Local DNS Server/Resolver address in VPLMN, HPLMN address information (e.g. H-UPF IP address on N6), AF traffic influence information (from H-SMF to V-SMF in case AF interacts with HPLMN to influence HR-SBO session at VPLMN), Internal Group Identifier(s). Local Offloading Management allowed indication (from SMF to I-SMF), Local Offloading Management information (from SMF to I-SMF), Offload Identifier(s) (from SMF to I-SMF), PSA UPF IP address on N6 (from SMF to I-SMF when Local Offloading Management applies), DNS server address (from SMF to I-SMF when Local Offloading Management applies), user plane latency requirement, indication of considering N6 delay.
The V-SMF SM Context ID in the Input provides addressing information allocated by the V-SMF (to be used for service operations towards the V-SMF for this PDU Session).
The I-SMF SM Context ID in the Input provides addressing information allocated by the I-SMF (to be used for service operations towards the I-SMF for this PDU Session).
See clause 4.3.2.2.2 clause 4.11.1.2.2 clause 4.11.1.3.3 and clause 4.24 for details on the usage of this service operation.
See clauses 4.22.2.2 and 4.22.3 for detailed usage of this service operation for ATSSS.
See clause 6.7 of TS 23.548 [74] for HR-SBO request indication, HR-SBO authorization result, VPLMN EASDF address, VPLMN Specific Offloading Information for HR-SBO, Offload Identifier(s), HPLMN DNS Server address, HPLMN address information.
See clause 6.5.2.6 of TS 23.548 [74] for details on the EAS Configuration Address Information provisioning in roaming.
See clause 6.10 of TS 23.548 [74] for detailed usage on Local Offloading Management support indication, Local Offloading Management allowed indication, PSA UPF IP address on N6 and DNS server address information. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.3 Nsmf_PDUSession_Update service operation | Service operation name: Nsmf_PDUSession_Update.
Description: Update the established PDU Session.
This service operation is invoked by the V-SMF towards the H-SMF in the case of UE or serving network requested PDU Session Modification in order for the V-SMF to transfer the PDU Session Modification request. It can also be invoked by the V-SMF to indicate to the H-SMF that the access type of the PDU session can be changed. This service operation is also invoked by the V-SMF to insert or remove UL CL or BP controlled by the V-SMF.
This service operation is invoked by the I-SMF towards the SMF in the case of UE or serving network requested PDU Session Modification in order for the I-SMF to transfer the PDU Session Modification request. It can also be invoked by the I-SMF to indicate to the SMF that the access type of the PDU session can be changed. This service operation is also invoked by the I-SMF towards the SMF to insert or remove ULCL or BP controlled by the I-SMF or to report usage offloaded via UL CL or BP controlled by I-SMF.
This service operation is invoked by the H-SMF towards the V-SMF for both UE initiated and HPLMN initiated PDU Session Modification and PDU Session Release cases in order to have the SM PDU Session Modification request or SM PDU Session Release request sent to the UE. It can also be invoked by the H-SMF towards the V-SMF to release the 5GC and 5G-AN resources in e.g. handover from 5GC-N3IWF to EPS and from 5GS to EPC/ePDG, wherein the UE is not notified.
This service operation is invoked by the SMF towards the I-SMF for both UE initiated and SMF/PCF initiated PDU Session Modification and PDU Session Release cases in order to have the SM PDU Session Modification request or SM PDU Session Release request sent to the UE. It can also be invoked by the SMF towards the I-SMF to release the 5GC and 5G-AN resources in e.g. handover from 5GC-N3IWF to EPS and from 5GS to EPC/ePDG, wherein the UE is not notified. This service operation is also invoked by the SMF towards the I-SMF to provide updated N4 information or updated DNAI list of interest for this PDU Session when SMF receives updated PCC rules.
This service operation is invoked by the V-SMF or I-SMF and the H-SMF or SMF in the case of PDU Session Establishment authentication/authorization by a DN-AAA Server defined in clause 4.3.2.3: it is used to carry DN Request Container information between the DN-AAA Server and the UE.
Input, Required: SM Context ID.
Input, Optional: UE location information (ULI), UE Time Zone, AN type, indication of PDU Session Release, H-SMF SM Context ID (from H-SMF to V-SMF) or SMF SM Context ID (from SMF to I-SMF), QoS Rule and QoS Flow level QoS parameters if any for the QoS Flow associated with the QoS rule (from H-SMF to V-SMF or from SMF to I-SMF), EPS bearer context(s) and Linked EBI (from H-SMF to V-SMF or from SMF to I-SMF), N9 Tunnel Info (from V-SMF to H-SMF or from I-SMF to SMF), Information requested by UE for e.g. QoS (from V-SMF to H-SMF or from I-SMF to SMF), 5GSM Core Network Capability, Information necessary for V-SMF or I-SMF to build SM Message towards the UE (from H-SMF to V-SMF or from SMF to I-SMF), Trigger PDU release indication (V-SMF to H-SMF or from I-SMF to SMF), Start Pause of Charging indication, Stop Pause of Charging indication, DN Request Container information, indication that the UE shall not be notified, EBI Allocation Parameters (ARP list), Secondary RAT usage data, indication that the access type of the PDU session can be changed (V-SMF to H-SMF or from I-SMF to SMF) or from SMF to I-SMF), extended NAS-SM timer indication, DNAI list supported by I-SMF (from I-SMF to SMF), indication of multi-homing support (from SMF to I-SMF), indication of ULCL or BP insertion (from I-SMF to SMF), indication of ULCL or BP removal (from I-SMF to SMF), IPv6 prefix @local PSA (from I-SMF to SMF), DNAI(s) supported by local PSA (from I-SMF to SMF), Tunnel info of ULCL or BP (from I-SMF to SMF), N4 information (from I-SMF to SMF or from SMF to I-SMF), Handover Complete Indication, Relocation Cancel Indication. MA PDU request indication, MA PDU Network-Upgrade Allowed indication, Indication on whether the UE is registered in both accesses, MA PDU session Accepted indication, access for MA PDU Session Release, access type for GBR QoS flow, Indication of access unavailability (with access type), QoS Monitoring Indication (from SMF to I-SMF), QoS Monitoring reporting frequency(from SMF to I-SMF), QoS monitoring policy (from SMF to I-SMF), QoS Monitoring Result from (I-SMF to SMF), Request for notification of SM Policy Association establishment and termination, PCF binding information, Satellite backhaul category, N9 forwarding tunnel to support the EAS session continuity required (from SMF to I-SMF), traffic filter for N9 forwarding (from SMF to I-SMF), value of the timer to detect the end of activity on the N9 forwarding tunnel to support the EAS session continuity (from SMF to I-SMF), EAS rediscovery indication, EAS information to be refreshed for EAS re-discovery, ECS Address Configuration Information, Alternative HPLMN S-NSSAI, HR-SBO authorization result, VPLMN Specific Offloading Information for HR-SBO, Offload Identifier(s), HPLMN address information, VPLMN EASDF/Local DNS Server/Resolver IP address, DNS security information of V-EASDF/Local DNS Server/Resolver, DNS Server address provided by HPLMN, AF traffic influence information (from H-SMF to V-SMF in case AF interacts with HPLMN to influence HR-SBO session at VPLMN), Local Offloading Management information (from SMF to I-SMF), Offload Identifier(s) (from SMF to I-SMF), EASDF IP address (from I-SMF to SMF), DNS security information of EASDF (from I-SMF to SMF), Local Offloading Management support indication (from I-SMF to SMF), Local Offloading Management allowed indication (from I-SMF to SMF), Indication of UE supports non-3GPP access path switching, [URSP rule enforcement reports], NG RAN QoS monitoring capability (as defined in clause 5.45.1 of TS 23.501 [2], user plane latency requirement (from SMF to I-SMF), indication of considering N6 delay (from SMF to I-SMF).
Output, Required: Result indication, <ARP, Cause> pair.
Output, Optional: UE location information, AN Type, SM information from UE (from V-SMF to H-SMF or from I-SMF to SMF), list of Rejected QoS Flows (from V-SMF to H-SMF or from I-SMF to SMF), a list of <ARP, EBI> pair, Secondary RAT Usage Data, DNAI(s) of interest for this PDU Session (from SMF to I-SMF), N4 Information (from SMF to I-SMF), QFI(s), QoS Profile(s), Session-AMBR, QoS Rule(s), QoS Flow level QoS parameters if any for the QoS Flow(s) associated with the QoS rule(s), EPS bearer context(s), linked EBI, DNAI(s) of interest for this PDU Session, HR-SBO authorization result, VPLMN Specific Offloading Information for HR-SBO, Offload Identifier(s), HPLMN address information, DNS Server address provided by HPLMN (e.g. Local DNS Server/Resolver address in VPLMN), Internal Group Identifier(s), Local Offloading Management allowed indication (from SMF to I-SMF), PSA UPF IP address on N6 (from SMF to I-SMF when Local Offloading Management applies), DNS server address (from SMF to I-SMF when Local Offloading Management applies), Local Offloading Management allowed indication (from SMF to I-SMF).
The H-SMF SM Context ID in the Input provides addressing information allocated by the H-SMF (to be used for service operations towards the H-SMF for this PDU Session).
The SMF SM Context ID in the Input provides addressing information allocated by the SMF (to be used for service operations towards the SMF for this PDU Session).
See clause 4.3.3.3 for an example usage of this service operation.
See clauses 4.22.6.3, 4.22.7, 4.22.8.3 and 4.22.10.3 for detailed usage of this service operation for ATSSS.
See clause 6.7.3 of TS 23.548 [74] for detailed usage of this service for EAS re-discovery.
See clause 6.10 of TS 23.548 [74] for detailed usage on Local Offloading Management support indication, Local Offloading Management allowed indication, PSA UPF IP address on N6 and DNS server address information. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.4 Nsmf_PDUSession_Release service operation | Service operation name: Nsmf_PDUSession_Release.
Description: It causes the immediate and unconditional deletion of the resources associated with the PDU Session. This service operation is used by V-SMF to request the H-SMF or used by I-SMF to request the SMF to release the resources related to a PDU Session for the serving network initiated PDU release case (e.g. implicit De-registration of UE in the serving network).
Input, Required: SM Context ID.
Input, Optional: Secondary RAT Usage Data, N4 information.
Output, Required: Result Indication.
Output, Optional: Small Data Rate Control Status, APN Rate Control Status.
See clause 4.3.4.3 for an example usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.5 Nsmf_PDUSession_CreateSMContext service operation | Service operation name: Nsmf_PDUSession_CreateSMContext.
Description: It creates an AMF-SMF association to support a PDU Session.
Input, Required: SUPI or PEI, DNN, AMF ID (AMF Instance ID), RAT Type, Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.18 of TS 23.501 [2]).
Input, Optional: PEI, S-NSSAI(s), Alternative S-NSSAI, Slice Area Restriction indication, PDU Session ID, N1 SM container, UE location information, UE Time Zone, AN type, H-SMF identifier/address, H-SMF set ID, list of alternative H-SMF(s) if available, old PDU Session ID (if the AMF also received an old PDU Session ID from the UE as specified in clause 4.3.5.2), Subscription For PDU Session Status Notification, Subscription for DDN Failure Notification, NEF Correlation ID, indication that the SUPI has not been authenticated, PCF ID, PCF Group ID, Same PCF Selection Indication, DNN Selection Mode, UE PDN Connection Context, GPSI, UE presence in LADN service area, indication that "the PDU Session is subject to LADN per LADN DNN and S-NSSAI", GUAMI, backup AMF(s) (if NF Type is AMF), Trace Requirements, Control Plane CIoT 5GS Optimisation indication, Small Data Rate Control Status, APN Rate Control Status. Backup AMF(s) sent only once by the AMF to the SMF in its first interaction with the SMF, UE's Routing Indicator optionally with Home Network Public Key identifier or UDM Group ID for the UE, EPS Interworking indication, EPS Bearer Status. Target ID (for EPS to 5GS handover), "Invoke NEF" flag, target DNAI, additional following for SM context transfer: SMF transfer indication, Old SMF ID, SM context ID in old SMF (see clause 4.26.5.3), HO Preparation Indication, indication of no NG-RAN change. MA PDU request indication, MA PDU Network-Upgrade Allowed indication, Indication on whether the UE is registered in both accesses, Satellite backhaul category, Satellite ID, PVS FQDN(s) and/or PVS IP address(es) and Onboarding Indication in the case of ON-SNPN, Disaster Roaming service indication, HR-SBO allowed indication, Local Offloading Management allowed indication, Indication of UE supports non-3GPP access path switching, NG RAN QoS monitoring capability (as defined in clause 5.45.1 of TS 23.501 [2].
NOTE: Satellite ID was named GEO Satellite ID in earlier Releases of this specification.
Output, Required: Result Indication and if successful SM Context ID.
Output, Optional: Cause, PDU Session ID, N2 SM information, N1 SM container, S-NSSAI(s), PDU Session Priority.
When the PDU Session is for Emergency services for a UE without USIM, the AMF provides the PEI and not the SUPI as identifier of the UE. When the PDU Session is for Emergency services of an unauthenticated UE with an USIM, the AMF shall provide both the SUPI and the PEI and shall provide an indication that the SUPI has not been authenticated.
See clause 4.3.2.2.1 clause 4.3.2.2.2 clause 4.11.1.2.2 and clause 4.11.1.3.3 for details on the usage of this service operation.
See clauses 4.22.2.1 and 4.22.3 for detailed usage of this service operation for ATSSS.
See clause 6.7 of TS 23.548 [74] for HR-SBO allowed indication.
See clause 6.10 of TS 23.548 [74] for Local Offloading Management allowed indication. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.6 Nsmf_PDUSession_UpdateSMContext service operation | Service operation name: Nsmf_PDUSession_UpdateSMContext.
Description: It allows to update the AMF-SMF association to support a PDU Session and/or to provide SMF with N1/N2 SM information received from the UE or from the AN, or allows to establish forwarding tunnel between UPFs controlled by different SMFs (e.g. by UPF controlled by old I-SMF and UPF controlled by new I-SMF).
Input, Required: SM Context ID.
Input, Optional: N1 SM container received from the UE, N2 SM information received from the AN (e.g. N3 addressing information, notification indicating that the QoS targets cannot be fulfilled for a QFI, Secondary RAT Usage Data), Operation Type (e.g. UP activate, UP deactivate, UP To Be Switched), Serving GW Address(es) and Serving GW DL TEID(s) for data forwarding during HO from 5GS to EPS, UE location information, AN type, UE Time Zone, H-SMF identifier/address, EPS Interworking indication, EBI(s) to be revoked, PDU Session(s) to be re-activated, Direct Forwarding Flag, ARP list, S-NSSAI, Data Forwarding Tunnel (setup/release), UE presence in LADN service area, Target ID, Target AMF ID, GUAMI, backup AMF(s) (if NF Type is AMF), Indication of Access Type can be changed, RAT Type. Backup AMF(s) sent only once by the AMF to the SMF in its first interaction with the SMF. Release indication and release cause, forwarding tunnel information, Handover Complete Indication, Relocation Cancel Indication. MA PDU request indication, MA PDU Network-Upgrade Allowed indication, Indication on whether the UE is registered in both accesses, access on which signalling was received, Subscription to DDN Failure Notification, NEF Correlation ID, MO Exception Data Counter, access for MA PDU Session Release, list of NWDAF IDs and corresponding Analytics ID(s), Satellite backhaul category, Satellite ID, N9 forwarding tunnel to support the EAS session continuity required, target UL CL tunnel info for N9 forwarding tunnel to support the EAS session continuity, value of the timer to detect the end of activity on the N9 forwarding tunnel to support the EAS session continuity, CN based MT handling indication, Alternative S-NSSAI, Indication of UE supporting non-3GPP access path switching, Indication of non-3GPP access path switching while using old AN resources, Slice Area Restriction indication, NG RAN QoS monitoring capability (as defined in clause 5.45.1 of TS 23.501 [2], Local Offloading Management allowed indication.
NOTE 1: Satellite ID was named GEO Satellite ID in earlier Releases of this specification.
Output, Required: Result Indication.
Output, Optional: PDU Session ID, Cause, released EBI list, allocated EBI information, N2 SM information (e.g. QFI, UE location information, notification indication indicating that the QoS targets cannot be fulfilled), N1 SM container to be transferred to the AN/UE, type of N2 SM information. MA PDU session Accepted indication, list of NWDAF IDs and corresponding Analytics ID(s), source UL CL tunnel info for N9 forwarding tunnel info to support the EAS session continuity, PDU Session Priority.
See clause 4.3.3.2 and clause 4.3.3.3 for an example usage of this service operation.
See clause 4.9.1.2.2 for the usage of the "UP To Be Switched" Operation Type.
For the use of the "EBI(s) to be revoked" information, see clause 4.11.1.4.1.
For the use of the "Direct Forwarding Flag", see clause 4.11.1.2.2.2.
For the use of the "Indication of Access Type can be changed", see clause 4.2.3.2.
For the use of "release indication and release cause", see clause 4.3.4.2.
For the use of the "forwarding tunnel information", see clause 4.23.4.3.
For the use of the "Local Offloading Management allowed indication", see clause 6.10 of TS 23.548 [74].
If the consumer NF is AMF and the SMF determines that some EBIs are not needed, the SMF will put the EBIs back in the released EBI list.
If the consumer NF is AMF and Inter-system mobility happens, the SMF sends allocated EBI information to AMF.
If the ARP of QoS flow is changed, the SMF uses this operation to update EBI-ARP information in the AMF.
If the AMF does not have PDU Session ID, the PDU Session ID is not required for Input and is required for Output.
If consumer NF is AMF and SMF includes N2 SM information in the Output, the SMF indicates type of N2 SM information.
The Small Data Rate Control Status is included if a PDU Session is being released and the UPF or NEF provided Small Data Rate Control Status for the AMF to store. APN Rate Control Status is included if a PDU Session is being released and the UPF or NEF provided APN Rate Control Status for the AMF to store.
NOTE 2: The N2 SM information is not interpreted by the AMF.
See clauses 4.22.6.3, 4.22.9 and 4.22.10.2 for detailed usage of this service operation for ATSSS. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.7 Nsmf_PDUSession_ReleaseSMContext service operation | Service operation name: Nsmf_PDUSession_ReleaseSMContext.
Description: It allows to release the AMF-SMF association for a certain PDU Session because the PDU Session has been released.
Input, Required: SM Context ID.
Input, Optional: UE location information, AN type, UE Time Zone, N2 SM Info (Secondary RAT Usage Data), V-SMF only, I-SMF only.
Output, Required: Result Indication.
Output, Optional: Cause, Small Data Rate Control Status, APN Rate Control Status.
See clause 4.3.4.2 and clause 4.3.4.3 for an example usage of this service.
If the consumer NF is AMF and the PDU Session indicated by the PDU Session ID had been assigned some EBIs, the AMF locally determines that the corresponding EBI(s) are released.
For the use of the "V-SMF only" indication, see clause 4.11.1.2.
For the use of the "I-SMF only" indication, see clause 4.23.7.3. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.8 Nsmf_PDUSession_SMContextStatusNotify service operation | Service operation name: Nsmf_PDUSession_SMContextStatusNotify.
Description: This service operation is used by the SMF to notify its consumers about the status of an SM context related to a PDU Session (e.g. PDU Session Release due to local reasons within the SMF, PDU Session handover to a different system or access type, SMF context transfer, triggering I-SMF selection for the PDU Session). The SMF may use this service operation to update the SMF derived CN assisted RAN parameters tuning in the AMF. The SMF may report the DDN Failure with NEF Correlation ID to the AMF.
Input, Required: Status information.
Input, Optional: Cause, SMF derived CN assisted RAN parameters tuning, New SMF ID for SM Context Transfer (see clause 4.26.5.3) or SMF set ID, Small Data Rate Control Status, APN Rate Control Status, DDN Failure detected in (I-/V-)SMF, target DNAI information, list of NWDAF IDs and corresponding Analytics ID(s).
Output, Required: Result Indication.
Output, Optional: None.
The target DNAI information indicates the target DNAI for the current PDU session or target DNAI for next PDU session. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.9 Nsmf_PDUSession_StatusNotify service operation | Service operation name: Nsmf_PDUSession_StatusNotify.
Description: This service operation is used by the SMF to notify its consumers about the status of a PDU Session (e.g. PDU Session is released due to local reasons within the H-SMF, PDU Session handover to a different system or access type, triggering I-SMF reselection for the PDU Session).
Input, Required: Status information.
Input, Optional: Cause, Small Data Rate Control Status, APN Rate Control Status, target DNAI information.
Output, Required: Result Indication.
Output, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.10 Nsmf_PDUSession_ContextRequest service operation | Service operation name: Nsmf_PDUSession_ContextRequest.
Description: This service operation is used by the NF Consumer to request for SM Context (e.g. during EPS IWK, HO, SM Context transfer indication), or during mobility procedure with I-SMF (or V-SMF) changes or may be triggered by OAM.
Input, Required: SM Context ID, SM context type.
Input, Optional: Target MME Capability, EBI list not to be transferred, PDU Session ID (include PDU Session ID when available), SMF transfer indication, indication of no NG-RAN change.
Output, Required: One of the following:
- SM Context Container.
- Endpoint where SM Context can be retrieved.
Output, Optional: Small Data Rate Control Status.
The SM context type indicates the type of SM context to be requested, e.g. PDN Connection Context, 5G SM Context or both. The SM context type may also indicate that only a specific part of 5G SM Context is requested, e.g. only the AF Coordination Information part. If the SM context type is PDN Connection Context, the SM Context included in the SM Context container is the PDN Connection Context. If the SM context type is all, the SM Context included in the SM Context container includes both the PDN Connection Context and the 5G SM Context.
Table 5.2.8.2.10-1 illustrates the SM Context that may be transferred between I-SMF(s) or between V-SMF(s) in home-routed roaming case.
Table 5.2.8.2.10-1: SM Context of a PDU Session transferred between I-SMF(s) or between V-SMF(s) or between I/V-SMF and (H-)SMF
Field
Description
SUPI
SUPI (Subscription Permanent Identifier) is the subscriber's permanent identity in 5GS.
Trace Requirements
Trace reference: Identifies a record or a collection of records for a particular trace.
Trace type: Indicates the type of trace
OMC identity: Identifies the OMC that shall receive the trace record(s).
S-NSSAI
The S-NSSAI of the PDU Session for the serving PLMN.
HPLMN S-NSSAI
The S-NSSAI of the PDU Session for the HPLMN (Home-Routed PDU Session)
Network Slice Instance id
The network Slice Instance information for the PDU Session
DNN
The associated DNN for the PDU Session.
AMF Information
The associated AMF instance identifier and GUAMI.
Access Type
The current access type for this PDU Session.
RAT Type
RAT Type for this PDU Session.
PDU Session ID
The identifier of the PDU Session.
H-SMF Information or SMF Information
The associated H-SMF identifier and H-SMF address for the HR PDU Session ( applies only for a V-SMF), or the SMF identifier and SMF address for PDU Session (applies for I-SMF).
Context ID of the PDU Session in H-SMF or Context ID of the PDU Session in SMF
The context ID of the PDU Session in H-SMF or in SMF.
Forwarding Indication
An indication on whether forwarding tunnel needs be established in order to forward buffered DL data.
Uplink Tunnel Info of UPF controlled by the SMF / H-SMF
The Tunnel Information to be used to send UL traffic towards the UPF controlled by the SMF / H-SMF that interfaces the UPF controlled by the I-SMF.
Tunnel Info of NG-RAN
The N3 Tunnel Information in the NG-RAN for the PDU Session. This information is transferred if the target I/V-SMF indicates no NG-RAN change.
Disaster Roaming
An indication that the UE is registered for Disaster Roaming service.
EAS information to be refreshed for EAS re-discovery
Identifies EAS(s) which needs to be refreshed corresponding to the old target DNAI if available. See details in clause 6.7.3 of TS 23.548 [74]. This applies only for a V-SMF (for V-SMF change case) or H-SMF (for V-SMF insertion case).
AF TI Container
Container to carry the AF Traffic Influence Information. This applies only for HR-SBO PDU session. See details in clause 6.7.3 of TS 23.548 [74].
Authorization Result for HR-SBO
Indicates whether HR-SBO is authorized. See details in clause 6.7.3 of TS 23.548 [74]. This applies only for a V-SMF (for V-SMF change within same PLMN case).
VPLMN Specific Offloading Information
Includes traffic description information authorized for HR-SBO in VPLMN and the corresponding policy for the traffic. See details in clause 6.7.3 of TS 23.548 [74] (for V-SMF change within same PLMN case).
Offload Identifier
Identifies a certain VPLMN Specific Offloading Information. A HPLMN ID is expected to be included in this Identifier, see details in clause 6.7.2 of TS 23.548 [74] (for V-SMF change within same PLMN case).
HPLMN address information
Identifies the address information in HPLMN (e.g. H-UPF IP address on N6). See details in clause 6.7.3 of TS 23.548 [74]. This applies for a V-SMF (for V-SMF change within the same PLMN case), H-SMF (for V-SMF insertion).
DNS Server address provided by HPLMN
Identifies the DNS Server provided by HPLMN to VPLMN for HR-SBO. See details in clause 6.7.3 of TS 23.548 [74]. This applies for a V-SMF (for V-SMF change within the same PLMN case), H-SMF (for V-SMF insertion).
AF Coordination Information:
Source DNAI
The DNAI from where the UE is moving.
UE IP address in Source DNAI
The UE IP address in the Source DNAI.
List of Notification Correlation IDs
Notification Correlation IDs for UP path change event as received in the PCC Rules
For each notification correlation ID: Uplink buffering indication
Uplink buffering indication as received from the AF for this notification correlation id during Early Notification.
For each QoS Flow in the PDU Session:
5G QoS Identifier (5QI)
Identifier for the authorized QoS parameters for the service data flow.
ARP
The Allocation and Retention Priority for the service data flow consisting of the priority level, the pre-emption capability and the pre-emption vulnerability.
GFBR
Guaranteed Flow Bit Rate (GFBR) - UL and DL.
MFBR
Maximum Flow Bit Rate (MFBR) - UL and DL.
Priority Level
Indicates a priority in scheduling resources among QoS Flows.
Averaging Window
Represents the duration over which the guaranteed and maximum bitrate shall be calculated.
Maximum Data Burst Volume
Denotes the largest amount of data that is required to be transferred within a period of 5G-AN PDB.
Reflective QoS Control
Indicates to apply reflective QoS for the SDF in the TFT.
QoS Notification Control (QNC)
Indicates whether notifications are requested from 3GPP RAN when the GFBR can no longer (or can again) be guaranteed for a QoS Flow during the lifetime of the QoS Flow.
Maximum Packet Loss Rate
Maximum Packet Loss Rate - UL and DL.
Mapped EPS Bearer Context for Each QFI to support interworking with EPS:
EPS Bearer Id
An EPS bearer identity uniquely identifies an EPS bearer for one UE accessing via E-UTRAN.
TI
The GERAN/UTRAN Transaction ID (if any) that is associated with the EPS Bearer ID which is part of the Bearer Context received from the MME.
BSS Container
The GERAN BSS Container (if any) that is associated with the EPS Bearer ID which is part of the Bearer Context received from the MME.
Mapped EPS Bearer QoS
ARP, GBR, MBR, QCI.
PGW-U tunnel Information
PGW-U S5/S8 GTP-U tunnel IP address and TEID information.
TFT
Traffic Flow Template. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.11 Nsmf_PDUSession_ContextPush service operation | Service operation name: Nsmf_PDUSession_ContextPushRequest
Description: This service operation is used by the SMF as Service Consumer to push one SM Context to a another SMF as NF Service Producer. It may be triggered by OAM.
Input, Required: One of the following:
- SM Context of identified PDU session.
- Endpoint where SM Context of identified PDU session can be retrieved.
The SM context includes SM context in I-SMF(or V-SMF) and SM context in SMF (or H-SMF) separately.
See Table 5.2.8.2.10-1 for single SM Context stored in I-SMF or V-SMF that may be transferred to another SMF instance.
Editor's note: The SM context stored in SMF(or H-SMF) is to be defined.
Output, Required: Result Indication.
Output, Optional: Cause.
See clause 4.26.2 for an example usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.12 Nsmf_PDUSession_SendMOData service operation | Service operation name: Nsmf_PDUSession_SendMOData
Description: When the AMF has received MO Small Data from the UE in NAS procedure, this service operation allows the AMF to send the MO Small Data to the SMF.
Input, Required: SM Context ID, N1 container received from the UE.
Input, Optional: AN type, MO Exception Data Counter.
Output, Required: Result Indication.
Output, Optional: Cause.
See clause 4.24.1 for an example usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.13 Nsmf_PDUSession_TransferMOData service operation | Service operation name: Nsmf_PDUSession_TransferMOData
Description: When the V-SMF/I-SMF has received MO Small Data from AMF, this service operation allows the V-SMF/I-SMF to forward the MO Small Data to the (H-)SMF.
Input, Required: SM Context ID, MO Small Data.
Input, Optional: MO Exception Data Counter.
Output, Required: Result Indication.
Output, Optional: Cause.
See clause 4.25.4 for an example usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.2.14 Nsmf_PDUSession_TransferMTData service operation | Service operation name: Nsmf_PDUSession_TransferMTData
Description: When the (H-)SMF has received MT Small Data from the NEF, this service operation allows the (H-)SMF to send the MT Small Data to the V-SMF/I-SMF.
Input, Required: SM Context ID, MT Small Data.
Input, Optional: None.
Output, Required: Result Indication.
Output, Optional: Cause, Estimated Maximum Wait time.
See clause 4.24.5 for an example usage of this service operation. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.3 Nsmf_EventExposure Service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.3.1 General | Service description: This service provides events related to PDU Sessions towards consumer NF. The service operations exposed by this service allow other NFs to subscribe and get notified of events happening on PDU Sessions. The following are the key functionalities of this NF service.
- Allow consumer NFs to Subscribe and unsubscribe for an Event ID on PDU Session(s);
- Allow the NWDAF to collect data for network data analytics from SMF as specified in TS 23.288 [50] and from UPF as specified in clause 4.15.4.5;
- Allow the EIF to collect data from SMF as specified in clause 5.51.2 of TS 23.501 [2];
- Notifying events on the PDU Session to the subscribed NFs; and
- Allow consumer NFs to acknowledge or respond to an event notification.
The following events can be subscribed by a NF consumer (Event ID is defined in clause 4.15.1):
- UE IP address / Prefix allocation/change: The event notification may contain a new UE IP address / Prefix or an indication of which UE IP address / Prefix has been released.
- PDU Session Establishment and/or PDU Session Release.
The event notification may contain following information:
- PDU Session Type.
- DNN.
- UE IP address/Prefix.
- UP path change: a notification corresponding to this event is sent when the UE IP address / Prefix and / or DNAI and /or the N6 traffic routing information has changed.
The event notification may contain following information:
- the type of notification ("EARLY" or "LATE").
- for both the source and target UP path between the UE and the DN, the corresponding information is provided when it has changed:
- DNAI.
- UE IP address / Prefix.
- N6 traffic routing information.
- Candidate DNAI(s) for the PDU Session.
- Change of common EAS.
NOTE 1: UP path change notification, DNAI and N6 traffic routing information are further described in clause 5.6.7 of TS 23.501 [2].
NOTE 2: The UP path change notification includes DNAI to represent the change of satellite identifier in case of UE-Satellite-UE (UE-SAT-UE) communication.
NOTE 3: DNAI value can be derived from the satellite identifier as per operator policy and implementation.
- QoS Monitoring: the event notification may contain the QoS Monitoring report for the QoS parameter(s) to be measured defined in clause 5.45 of TS 23.501 [2]. Implicit subscription of the PCF on behalf of the NEF/AF as part of setting PCC rule(s) may trigger SMF to send this event notification.
- Change of Access Type; The event notification contains the new Access Type for the PDU Session. For MA PDU Session the Change of Access Type may include two Access Type information that the user is currently using.
- Change of RAT Type; the event notification contains the new RAT Type for the PDU Session.
- PLMN change; The event notification contains the new PLMN Identifier for the PDU Session and may indicate:
- whether local traffic offload is possible, i.e. mobility of the PDU session either towards HPLMN or towards a VPLMN where HR-SBO is supported and allowed; and
- DNN and S-NSSAI of HPLMN.
- Change of Satellite backhaul category; The event notification contains the new Satellite backhaul category for the PDU session.
- Downlink data delivery status. The event notification contains the status of downlink data buffering in the core network including:
- First downlink packet per source of the downlink IP traffic in extended buffering and Estimated maximum wait time.
- First downlink packet per source of the downlink IP traffic discarded.
- First downlink packet per source of the downlink IP traffic transmitted after previous buffering and/or discarding of corresponding packet(s).
- QFI allocation: The event notification is sent whenever a new QoS Flow is established and contains:
- If the Target of Event Reporting is a PDU Session and the QoS Flow is associated with this PDU Session, both the allocated QFI and either one of the following (Application Identifier or IP Packet Filter Set or Ethernet Packet Filter Set). The 5QI or QoS parameters corresponding to the QoS Flow and the DNN, S-NSSAI corresponding to the PDU Session are also sent.
- If the Target of Event Reporting is a SUPI and the PDU Session is associated with this SUPI, both the allocated QFI and either one of the following (Application Identifier or IP Packet Filter Set or Ethernet Packet Filter Set). The 5QI or QoS parameters corresponding to the QoS Flow and the DNN, S-NSSAI corresponding to the PDU Session are also sent.
- If the Target of Event Reporting is an Internal-Group-Id and the PDU Session is associated with this Internal-Group-Id (i.e. the PDU Session belongs to a UE belonging to this Internal-Group-Id), both the allocated QFI and either one of the following (Application Identifier or IP Packet Filter Set or Ethernet Packet Filter Set). The 5QI or QoS parameters corresponding to the QoS Flow and the DNN, S-NSSAI, PDU Session ID, SUPI corresponding to the PDU Session are also sent.
- If the Target of Event Reporting is any UE, both the allocated QFI and either one of the following (Application Identifier or IP Packet Filter Set or Ethernet Packet Filter Set). The 5QI or QoS parameters corresponding to the QoS Flow and the DNN, S-NSSAI, PDU Session ID, SUPI corresponding to the PDU Session are also sent.
- QoS Flow change: The event notification is sent whenever application traffic is bound to an existing QoS Flow or the QoS parameters of the QoS Flow that the application traffic is bound are modified. The Target of Event Reporting may be SUPI, Internal-Group-Id, or any UE. Related event notifications contain parameters as specified for the QFI allocation event.
- QFI deallocation: The event notification is sent whenever the QoS Flow is released. The Target of Event Reporting may be SUPI, Internal-Group-Id, or any UE. Related event notifications contain parameters as specified for the QFI allocation event.
NOTE 4: When the consumer NF is the NWDAF, the QFI allocation, QoS Flow change, and QFI deallocation events are used to collect data for analytics as specified in TS 23.288 [50].
- Total number of Session Management transactions:
- The total number of Session Management transaction is used to collect the number of SM transactions of a SUPI or Internal Group ID, for example Dispersion Analytics as specified in TS 23.288 [50]. The transaction count is incremented when the NAS transactions from PDU Session Establishment, PDU Session Authentication, PDU Session Modification and PDU Session Release procedures is concluded. Only the periodic reporting mode applies.
- Information on PDU Session for WLAN (i.e. Access Type is Non-3GPP and RAT Type is TRUSTED_WLAN).
- User plane status information: The event notification contains:
- PDU Session ID.
- User Plane Inactivity Timer (as specified in TS 29.244 [69]).
- PDU Session status (activated, deactivated).
NOTE 5: When the consumer NF is the NWDAF, the event user plane status information is used to collect data for UE Communication analytics as specified in TS 23.288 [50].
- Session Management Congestion Control Experience for PDU Session: The event notification contains the data related to Session Management Congestion Control experience per PDU Session as described in TS 23.288 [50].
- UE session behaviour trends (see clause 4.15.4.3);
- UE communications trends (see clause 4.15.4.3);
- UP with redundant transmission: the event notification indicates if redundant transmission (see clause 5.33.2.2 of TS 23.501 [2]) has been activated or not for the PDU session;
- User Data Usage Measures (see clause 4.15.4.5): SMF conveys the subscription to UPF on behalf of the consumer. Consumer receives the events directly from UPF. For certain UE(s), the SMF conveys the subscription to I-SMF on behalf of the consumer, and the I-SMF conveys the subscription to UPF on behalf of SMF. Consumer receives the events directly from UPF; and
- User Data Usage Trends (see clause 4.15.4.5): SMF conveys the subscription to UPF on behalf of the consumer. Consumer receives the events directly from UPF. For certain UE(s), the SMF conveys the subscription to I-SMF on behalf of the consumer, and the I-SMF conveys the subscription to UPF on behalf of the SMF. Consumer receives the events directly from UPF.
- Service Signalling characteristics: The event notification includes Request type and number from NF, Number of receiving Session Report from UPFs, State transition information, Timer information, Unexpected operational status indicator, etc. from SMF for Signalling Storm Analytics as specified in clause 6.22.2 of TS 23.288 [50].
When the consumer NF is the NWDAF, the event Information on PDU Session for WLAN is used to collect data for WLAN performance analytics as specified in TS 23.288 [50].
When the consumer NF is the NWDAF, the event Session Management Congestion Control Experience for PDU Session is used to collect data for Session Management Congestion Control Experience analytics as specified in TS 23.288 [50].
When the consumer NF is the NWDAF, the events QoS Monitoring, User Data Usage Measures and User Data Usage Trends are used to collect data from UPF for analytics as specified in clause 4.15.4.5 and in TS 23.288 [50]. SMF conveys the subscription to UPF on behalf of the NWDAF or the SMF conveys the subscription to I-SMF on behalf of the NWDAF and the I-SMF conveys the subscription to UPF on behalf of SMF.
The consumer NF may request to subscribe the UPF exposure events (including event ID of exposed UPF event of QoS monitoring, User Data Usage Measures and User Data Usage Trends) via SMF indirectly by Nsmf_EventExposure. After receiving this subscription request, the SMF does a third-party subscription onto UPF on behalf of this consumer. The consumer should also provide the subscribed UPF event to SMF.
Event Filters are used to specify the conditions to match for notifying the events (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 as an example how the conditions to match for event reporting can be specified for various Event IDs for SMF exposure.
Table 5.2.8.3.1-1: Example of Event Filters for SMF exposure events
Event ID for SMF exposure
Event Filter (List of Parameter Values to Match)
DNAI Change
None
Candidate DNAI(s) has changed
None
PDU Session Release
<Parameter Type = S-NSSAI, Value = S-NSSAI1>
PDU Session Establishment
<Parameter Type = S-NSSAI, Value = S-NSSAI1>
QoS Monitoring
<Parameter Type = S-NSSAI, Value = S-NSSAI1>
<Parameter Type = DNN, Value = DNN1>
<Parameter Type = Application Identifier, Value = Application Identifier1>
<Parameter Type = AoI, value = AoI1>
<Parameter Type = UPF Id, value = UPF Id1>
<Parameter Type = DNAI, value = DNAI1>
QFI allocation
<Parameter Type = DNN, Value = DNN1>
<Parameter Type = S-NSSAI, Value = S-NSSAI1>
QFI allocation
<Parameter Type = Application Identifier, Value = Application Identifier1>
QoS Flow change
<Parameter Type = Application Identifier, Value = Application Identifier1>
QFI deallocation
<Parameter Type = DNN, Value = DNN1>
<Parameter Type = S-NSSAI, Value = S-NSSAI1>
Transaction Count
<Parameter Type = TAI, Value = TA1> (NOTE)
<Parameter Type = S-NSSAI, Value = S-NSSAI1>
User plane status information
<Parameter Type = Application Identifier, Value = Application Identifier1>
<Parameter Type = SUPI, Value = SUPI1>
Information on PDU Session for WLAN
<Parameter Type = Access Type, Value = Non-3GPP> && <Parameter Type = RAT Type, Value = TRUSTED_WLAN>
Session Management Congestion Control Experience for PDU Session
<Parameter Type = DNN, Value = DNN1>
<Parameter Type = S-NSSAI, Value = S-NSSAI1>
UP with redundant transmission
<Parameter Type = DNN, Value = DNN1>
User Data Usage Measures
<Parameter Type = S-NSSAI, Value = S-NSSAI1>
<Parameter Type = DNN, Value = DNN1>
<Parameter Type = Application Identifier, Value = Application Identifier1> (NOTE 2)
<Parameter Type = Flow Info, Value = Packet Filter Set1> (NOTE 2)
<Parameter Type = AoI, value = AoI1>
<Parameter Type = SSID/BSSID, Value = SSID/BSSID1>
User Data Usage Trends
<Parameter Type = S-NSSAI, Value = S-NSSAI1>
<Parameter Type = DNN, Value = DNN1>
<Parameter Type = Application Identifier, Value = Application Identifier1> (NOTE 2)
<Parameter Type = Flow Info, Value = Packet Filter Set1> (NOTE 2)
<Parameter Type = AoI, value = AoI1>
NOTE 1: Optionally the SMF can fetch the location information from the AMF but transaction information correlation at the location can also be achieved without it and through transaction information associated with the requested time period, which corresponds to the UE's time span at the location of interest.
NOTE 2: These Parameters are exclusive and only one of them can be provided.
The target of SMF event reporting may correspond to a PDU Session ID, an UE ID (SUPI), an Internal Group Identifier, an indication that any UE is targeted (e.g. on a specific DNN), or an indication that any PDU session is the target.
An SMF receiving Nsmf_EventExposure Subscription request to subscribe (e.g. to UPF event exposure) for "Any UE" does not consider PDU sessions for which it is acting as I-SMF when it selects the PDU session(s) it has to consider.
When acknowledgment is expected the SMF also provides Notification Correlation Information to the consumer NF in the event notification.
The consumer NF may provide the following event-specific information when acknowledging an event notification:
- For UP path change event:
- N6 traffic routing information related to the target DNAI.
NOTE 6: Acknowledgement to a UP path change event notification is further described in clause 5.6.7 of TS 23.501 [2]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.3.2 Nsmf_EventExposure_Notify service operation | Service operation name: Nsmf_EventExposure_Notify
Description: Report UE PDU Session related event(s) to the NF which has subscribed to the event report service.
Input Required: Event ID, Notification Correlation Information, UE ID(s) (SUPI(s) and if available GPSI(s)), PDU Session ID(s), time stamp.
SMF reports multiple PDU Sessions events when those happen at the same time and as indicated in the time stamp. The SMF reports the PDU Session ID, SUPI and if available GPSI(s) per each PDU Session event.
Input, Optional: Event specific parameter list as described in clause 5.2.8.3.1, capability of supporting EAS IP replacement in 5GC.
Output Required: Result Indication.
Output, Optional: Redirection information.
When the SMF detects the event subscribed by the NF consumer, the SMF reports the subscribed event together with the Notification Target Address (+ Notification Correlation ID) to the Event Receiving NF.
The optional event specific parameter list provides the values that matched for generating the event notification. The parameter values to match are specified during the event subscription (see clause 5.2.8.3.3).
See clause 4.3.6.3 for details on usage of this service operation toward Application Function.
If the NF consumer is AMF and the result of the service operation fails, the AMF shall set corresponding cause value in result indication which can be used by the SMF for further action. If the related UE is not served by the AMF and the AMF knows which AMF is serving the UE, the AMF provides redirection information which can be used by the SMF to resend UE related message to the AMF that serves the UE.
NOTE: In the case of UP plane path, as described in clause 4.3.6.2, this notification can be the result of an implicit subscription of the NEF/AF by the PCF as part of setting PCC rule(s) via the Npcf_SMPolicyControl service (see clause 5.2.5.4).
5.2.8.3.2A Nsmf_EventExposure_AppRelocationInfo service operation
Service operation name: Nsmf_EventExposure_AppRelocationInfo
Description: Acknowledge the notification from the SMF regarding UE PDU Session related event(s).
Input Required: Notification Correlation Information, cause code.
The Notification Correlation Information is provided by the SMF in the event notification.
Cause code indicates this acknowledgement is positive or negative.
Input, Optional: Event specific parameter list as described in clause 5.2.8.3.1, Indication that buffering of uplink traffic should start, Information for EAS IP Replacement in 5GC, flow description information.
NOTE: To support UE-Satellite-UE (UE-SAT-UE) communication, flow description information can carry IMS AGW IP address.
Output Required: None.
Output, Optional: None.
See clause 4.3.6.3 for details on usage of this service operation for example for the usage of the Indication that buffering of uplink traffic should start. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.3.3 Nsmf_EventExposure_Subscribe service operation | Service operation name: Nsmf_EventExposure_Subscribe.
Description: This service operation is used by an NF to subscribe or modify a subscription for event notifications on a specified PDU Session or for all PDU Sessions of one UE, group of UE(s) or any UE.
Input, Required: NF ID, Target of Event Reporting as defined in clause 5.2.8.3.1, (set of) Event ID(s) defined in clause 5.2.8.3.1, Notification Target Address (+ Notification Correlation ID), Event Reporting Information defined in Table 4.15.1-1.
Input, Optional: Event Filter(s) associated with each Event ID; Event Filter(s) are defined in clause 5.2.8.3.1, Subscription Correlation ID (in the case of modification of the event subscription), Expiry time, DNN, S-NSSAI, DNAI, UPFId, UPF event exposure information (Type of measurement, granularity of measurement, reporting suggestion information, Remaining data reporting indication, etc. associated with the UPF Event IDs as described in clause 4.15.4.5).
NOTE: The SMF is generally meant to determine the UPF to contact for a subscription related to UPF event exposure. UPF ID is only provided to indicate a UP Path as defined in Table 6.4.1-1 of TS 23.288 [50], i.e. when the NWDAF has received the target UPF as part of statistics of observed service experience on an UP path involving that UPF.
Output, Required: When the subscription is accepted: Subscription Correlation ID (required for management of this subscription), Expiry time (required if the subscription can be expired based on the operator's policy).
Output, Optional: First corresponding event report is included, if available (see clause 4.15.1).
Notification Target Address (+ Notification Correlation ID) is used to correlate Notifications sent by SMF or UPF with this subscription. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.3.4 Nsmf_EventExposure_UnSubscribe service operation | Service operation name: Nsmf_EventExposure_UnSubscribe.
Description: This service operation is used by an NF to unsubscribe event notifications.
Input, Required: Subscription Correlation ID.
Input, Optional: None.
Output, Required: None.
Output, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.4 Nsmf_NIDD Service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.4.1 General | This service is used for NIDD transfer between SMF and another NF. See clause 4.25.5. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.4.2 Nsmf_NIDD_Delivery service operation | Service operation name: Nsmf_NIDD_Delivery
Description: This service operation is used by the NF consumer to deliver the unstructured data between NF consumer and SMF to support NIDD via NEF.
Inputs Required: User Identity, PDU Session ID, unstructured data, Reliable Data Service Configuration (Optional).
Inputs, Optional: None.
Outputs Required: Cause.
Outputs, Optional: Extended Buffering Time. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.5 Nsmf_TrafficCorrelation service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.5.1 General | Service description: This service allows SMF to notify NF Consumer (NEF) about 5GC determined information for a set of UEs identified by Traffic Correlation ID.
NOTE: The NEF stores this in the UDR together with AF requests to influence traffic routing information. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.8.5.2 Nsmf_TrafficCorrelation_Notify service operation | Service operation name: Nsmf_TrafficCorrelation_Notify
Description: The NF notifies with 5GC determined information.
Inputs, Required: SMF ID, number of PDU sessions for the traffic correlation ID, traffic correlation ID.
Inputs, Optional: EAS ID, DNAI(s).
NOTE At least one of EAS ID or DNAI(s) needs to be included in the Input.
Outputs, Required: Result Indication.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.9 SMSF Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.9.1 General | The following table illustrates the SMSF Services.
Table 5.2.9.1-1: List of SMSF Services
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Nsmsf_SMService
Activate
Request/Response
AMF
Deactivate
Request/Response
AMF
UplinkSMS
Request/Response
AMF
MtForwardSm
Request/Response
SMS-GMSC, IP-SM-GW, SMS Router |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.9.2 Nsmsf_SMService service | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.9.2.1 General | This service allows AMF to authorize SMS and activate SMS for the served user on SMSF. This service allows downlink SMS message transmit from consumer NF to SMSF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.9.2.2 Nsmsf_SMService_Activate service operation | Service operation name: Nsmsf_SMService_Activate.
Description: Authorize whether the specified UE is allowed to activate SMS service, or add connectivity for SMS over new Access Type.
Concurrent use: None.
Inputs, Required: SUPI, NF ID, RAT Type.
Inputs, Optional: GPSI, Time Zone, one or more Access Type(s), GUAMI, backup AMF(s) (if NF Type is AMF). Backup AMF(s) sent only once by the AMF to the SMSF in its first interaction with the SMSF, UE's Routing Indicator optionally with Home Network Public Key identifier or UDM Group ID for the UE.
Outputs, Required: SMS service activation result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.9.2.3 Nsmsf_SMService_Deactivate service operation | Service operation name: Nsmsf_SMService_Deactivate.
Description: Remove SMS service authorization from SMSF for a given service user, or with Access Type included, remove connectivity for SMS over the affected Access Type.
Concurrent use: None.
Inputs, Required: SUPI.
Inputs, Optional: Access Type.
Outputs, Required: SMS service deactivation result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.9.2.4 Nsmsf_SMService_UplinkSMS service operation | Service operation name: Nsmsf_SMService_UplinkSMS.
Description: transmit uplink SMS message from consumer NF to SMSF.
Concurrent use: None.
Inputs, Required: SUPI, SMS payload.
Inputs, Optional: GPSI, UE Time Zone, UE Location Information (ULI).
Outputs, Required: SMS message transmission result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.9.2.5 Nsmsf_SMService_MtForwardSm service operation | Service operation name: Nsmsf_SMService_MtForwardSm.
Description: Transmit downlink SMS message from consumer NF to SMSF.
Inputs, Required: GPSI, SMS payload.
Inputs, Optional: None.
Outputs, Required: SMS message transmission result.
Outputs, Optional: None. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10 AUSF Services | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10.1 General | The following table illustrates the AUSF Services.
Table 5.2.10.1-1: List of AUSF Services
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Nausf_UEAuthentication
Authenticate
Request/Response
AMF
Nausf_SoRProtection
Protect
Request/Response
UDM
Nausf_UPUProtection
Protect
Request/Response
UDM |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 5.2.10.2 Nausf_UEAuthentication service |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.