Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.502  Word version:   16.4.0

Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.3…   4.3.2.2…   4.3.2.2.2   4.3.2.2.3…   4.3.3   4.3.4   4.3.5…   4.3.5.2…   4.3.5.4…   4.3.5.6…   4.3.6…   4.4…   4.5…   4.9…   4.9.1.3…   4.9.2…   4.11…   4.11.1.2.2…   4.11.1.3…   4.11.1.4…   4.11.1.5…   4.11.2   4.11.3…   4.12…   4.12.6…   4.12a   4.12b   4.13…   4.13.4…   4.13.6…   4.14…   4.15…   4.15.4…   4.16…   4.16.4…   4.16.8…   4.17…   4.17.9…   4.18…   4.19…   4.23…   4.23.7…   4.23.9…   4.23.11…   4.24   4.25   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   A…   E…   F…

 

5.2.8  SMF Services
5.2.8.1  General
The following table shows the SMF Services and SMF Service Operations.
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, I-SMF, SMF
ContextPush
Request/Response
SMF
SendMOData
Request/Response
AMF
Nsmf_EventExposure
Subscribe
Subscribe/Notify
NEF, AMF, NWDAF
Unsubscribe
NEF, AMF, NWDAF
Notify
NEF, AMF, NWDAF
AppRelocationInfo
AF
Nsmf_NIDD
Delivery
Request/Response
NEF

Up
5.2.8.2  Nsmf_PDUSession ServiceWord-p. 511
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 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:
  • (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;
  • 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.
Up
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 PGW-C+SMF.
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).
Input, Optional:
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 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), 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.
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, Reflective QoS Timer, Always-on PDU Session Granted, information provided by H-SMF related to charging in home routed scenario (see TS 32.255), 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.
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.
Up
5.2.8.2.3  Nsmf_PDUSession_Update service operationWord-p. 512
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 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 invokded 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), 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).
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).
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.
Up
5.2.8.2.4  Nsmf_PDUSession_Release service operationWord-p. 513
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.
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.
Up
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).
Input, Optional:
PEI, S-NSSAI(s), PDU Session Id, N1 SM container, UE location information, UE Time Zone, AN type, H-SMF identifier/address, 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, DNN Selection Mode, UE PDN Connection Context, GPSI, UE presence in LADN service area, 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 or UDM Group ID for the UE, EPS Bearer Status. Target ID (for EPS to 5GS handover), "Invoke NEF" flag, additional following three 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. MA PDU request indication, MA PDU Network-Upgrade Allowed indication, Indication on whether the UE is registered in both accesses.
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).
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.
Up
5.2.8.2.6  Nsmf_PDUSession_UpdateSMContext service operationWord-p. 514
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, 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, Subscription to DDN Failure Notification, NEF Correlation ID, MO Exception Data Counter, access for MA PDU Session Release.
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.
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.
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:
The N2 SM information is not interpreted by the AMF.
See clauses 4.22.6.3 and 4.22.10.2 for detailed usage of this service operation for ATSSS.
Up
5.2.8.2.7  Nsmf_PDUSession_ReleaseSMContext service operationWord-p. 515
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.
Up
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). 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.
Output, Required:
Result Indication.
Output, Optional:
None.
Up
5.2.8.2.9  Nsmf_PDUSession_StatusNotify service operationWord-p. 516
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).
Input, Required:
Status information.
Input, Optional:
Cause, Small Data Rate Control Status, APN Rate Control Status.
Output, Required:
Result Indication.
Output, Optional:
None.
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 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.
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 requrested, e.g. PDN Connection Context, 5G SM Context or both. 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.
Field
Description

SUPI
SUPI (Subscription Permanent Identifier) is the subscriber's permanent identity in 5GS.
Trace Requirements (does not apply to V-SMF)
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.
Fowarding 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.
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
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

Up
5.2.8.2.11  Nsmf_PDUSession_ContextPush service operation [R16]Word-p. 517
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.
Up
5.2.8.2.12  Nsmf_PDUSession_SendMOData service operation [R16]Word-p. 518
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.
5.2.8.3  Nsmf_EventExposure Service
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 as specified in TS 23.288;
  • 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.
    NOTE 1:
    UP path change notification, DNAI and N6 traffic routing information are further described in TS 23.501, clause 5.6.7.
  • QoS Monitoring for URLLC: the event notification may contain the QoS Monitoring report as described in clause 5.33.3.2 of TS 23.501.
  • Change of Access Type; The event notification contains the new Access Type for the PDU Session.
  • PLMN change; The event notification contains the new PLMN Identifier 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 when a new QoS flow is established within a PDU session and contains:
    • If the Target of Event Reporting is a 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 DNN, S-NSSAI corresponding to the PDU session are also sent.
    • If the Target of Event Reporting is a SUPI, both the allocated QFI and either one of the following (Application Identifier or IP Packet Filter Set or Ethernet Packet Filter Set) for each PDU session ID established for this SUPI. The DNN, S-NSSAI corresponding to each PDU session are also sent.
    • If the Target of Event Reporting is an Internal-Group-Id or any UE, multiple instances of the tuple (allocated QFI and either one of the following (Application Identifier or IP Packet Filter Set or Ethernet Packet Filter Set). PDU session ID, SUPI). The DNN, S-NSSAI corresponding to each PDU session are also sent.
When the consumer NF is the NWDAF, the event QFI allocation is used to collect data for Observed Service Experience analytics and UE communication analytics as specified in TS 23.288.
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.
Event ID for SMF exposure
Event Filter (List of Parameter Values to Match)

DNAI Change
None
PDU Session Release
None
PDU Session Establishment
QoS Monitoring for URLLC
None
QFI allocation
None

The target of SMF event reporting may correspond to a PDU Session ID, an UE ID (SUPI) an Internal Group Identifier or an indication that any UE is targeted (on a specific DNN).
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 2:
Acknowledgement to a UP path change event notification is further described in TS 23.501, clause 5.6.7.
Up
5.2.8.3.2  Nsmf_EventExposure_Notify service operationWord-p. 520
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 (SUPI and if available GPSI), PDU Session ID, time stamp.
Input, Optional:
Event specific parameter list as described in clause 5.2.8.3.1.
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).
Up
5.2.8.3.2A  Nsmf_EventExposure_AppRelocationInfo service operation [R16]
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 Corrrelation 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.
Output Required: None.
Output, Optional:
None.
See clause 4.3.6.3 for details on usage of this service operation toward Application Function.
Up
5.2.8.3.3  Nsmf_EventExposure_Subscribe service operationWord-p. 521
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.
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 with this subscription.
Up
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.
5.2.8.4  Nsmf_NIDD Service [R16]
5.2.8.4.1  General
This service is used for NIDD transfer between SMF and another NF. See clause 4.25.5.
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.

Up   Top   ToC