SmContextCreateData

6.1.6.2.2

Information within Create SM Context Request

SmContextCreatedData

6.1.6.2.3

Information within Create SM Context Response

SmContextUpdateData

6.1.6.2.4

Information within Update SM Context Request

SmContextUpdatedData

6.1.6.2.5

Information within Update SM Context Response

SmContextReleaseData

6.1.6.2.6

Information within Release SM Context Request

SmContextRetrieveData

6.1.6.2.7

Information within Retrieve SM Context Request

SmContextStatusNotification

6.1.6.2.8

Information within Notify SM Context Status Request

PduSessionCreateData

6.1.6.2.9

Information within Create Request

PduSessionCreatedData

6.1.6.2.10

Information within Create Response

HsmfUpdateData

6.1.6.2.11

Information within Update Request towards H-SMF, or from I-SMF to SMF

HsmfUpdatedData

6.1.6.2.12

Information within Update Response from H-SMF, or from SMF to I-SMF

ReleaseData

6.1.6.2.13

Information within Release Request

HsmfUpdateError

6.1.6.2.14

Error within Update Response from H-SMF

VsmfUpdateData

6.1.6.2.15

Information within Update Request towards V-SMF, or from SMF to I-SMF

VsmfUpdatedData

6.1.6.2.16

Information within Update Response from V-SMF, or from I-SMF to SMF

StatusNotification

6.1.6.2.17

Information within Notify Status Request

QosFlowItem

6.1.6.2.18

Individual QoS flow

QosFlowSetupItem

6.1.6.2.19

Individual QoS flow to setup

QosFlowAddModifyRequestItem

6.1.6.2.20

Individual QoS flow requested to be created or modified

QosFlowReleaseRequestItem

6.1.6.2.21

Individual QoS flow requested to be released

QosFlowProfile

6.1.6.2.22

QoS flow profile

GbrQosFlowInformation

6.1.6.2.23

GBR QoS flow information

QosFlowNotifyItem

6.1.6.2.24

Notification related to a QoS flow

SmContextRetrievedData

6.1.6.2.27

Information within Retrieve SM Context Response

TunnelInfo

6.1.6.2.28

Tunnel Information

StatusInfo

6.1.6.2.29

Status of SM context or of PDU session

VsmfUpdateError

6.1.6.2.30

Error within Update Response from V-SMF

EpsPdnCnxInfo

6.1.6.2.31

EPS PDN Connection Information from H-SMF to V-SMF

EpsBearerInfo

6.1.6.2.32

EPS Bearer Information from H-SMF to V-SMF

PduSessionNotifyItem

6.1.6.2.33

Notification related to a PDU session

EbiArpMapping

6.1.6.2.34

EBI to ARP mapping

SmContextCreateError

6.1.6.2.35

Error within Create SM Context Response

SmContextUpdateError

6.1.6.2.36

Error within Update SM Context Response

PduSessionCreateError

6.1.6.2.37

Error within Create Response

MmeCapabilities

6.1.6.2.38

MME capabilities

SmContext

6.1.6.2.39

Complete SM Context

ExemptionInd

6.1.6.2.40

Exemption Indication

PsaInformation

6.1.6.2.41

PSA Information

DnaiInformation

6.1.6.2.42

DNAI Information

N4Information

6.1.6.2.43

N4 Information

IndirectDataForwardingTunnelInfo

6.1.6.2.44

Indirect Data Forwarding Tunnel Information

SmContextReleasedData

6.1.6.2.45

Information within Release SM Context Response

ReleasedData

6.1.6.2.46

Information within Release Response

SendMoDataReqData

6.1.6.2.47

Information within Send MO Data Request

CnAssistedRanPara

6.1.6.2.48

SMF derived CN assisted RAN parameters tuning

UlclBpInformation

6.1.6.2.49

UL CL or BP Information

TransferMoDataReqData

6.1.6.2.50

Information within Transfer MO Data Request

TransferMtDataReqData

6.1.6.2.51

Information within Transfer MT Data Request

TransferMtDataError

6.1.6.2.52

Transfer MT Data Error Response

TransferMtDataAddInfo

6.1.6.2.53

Transfer MT Data Error Response Additional Information

VplmnQos

6.1.6.2.54

VPLMN QoS

DdnFailureSubs

6.1.6.2.55

DDN Failure Subscription

RetrieveData

6.1.6.2.56

Information within Retrieve Request

RetrievedData

6.1.6.2.57

Information within Retrieve Response

SecurityResult

6.1.6.2.58

Security Result

UpSecurityInfo

6.1.6.2.59

User Plane Security Information

DdnFailureSubInfo

6.1.6.2.60

DDN Failure Subscription Information

AlternativeQosProfile

6.1.6.2.61

Alternative QoS Profile

ProblemDetailsAddInfo

6.1.6.2.62

Problem Details Additional Information

ExtProblemDetails

6.1.6.2.63

Extended Problem Details

QosMonitoringInfo

6.1.6.2.64

QoS Monitoring Information

IpAddress

6.1.6.2.65

IP Address

RedundantPduSessionInformation

6.1.6.2.66

Redundant PDU Session Information

QosFlowTunnel

6.1.6.2.67

Tunnel Information per QoS Flow

AnchorSmfFeatures

6.1.6.2.71

Anchor SMF supported features

Teid

6.1.6.3.2

GTP Tunnel Endpoint Identifier

ProcedureTransactionId

6.1.6.3.2

Procedure Transaction Identifier

EpsPdnCnxContainer

6.1.6.3.2

UE EPS PDN Connection container from SMF to AMF

EpsBearerId

6.1.6.3.2

EPS Bearer Id

EpsBearerContainer

6.1.6.3.2

EPS Bearer container from SMF to AMF

EpsBearerContextStatus

6.1.6.3.2

EPS Bearer context status

DrbId

6.1.6.3.2

Data Radio Bearer Identifier

UpCnxState

6.1.6.3.3

User Plane Connection State

HoState

6.1.6.3.4

Handover State

RequestType

6.1.6.3.5

Request Type in Create (SM context) service operation.

RequestIndication

6.1.6.3.6

Request Indication in Update (SM context) service operation.

NotificationCause

6.1.6.3.7

Cause for generating a notification

Cause

6.1.6.3.8

Cause information

ResourceStatus

6.1.6.3.9

Status of SM context or PDU session resource

DnnSelectionMode

6.1.6.3.10

DNN Selection Mode

EpsInterworkingIndication

6.1.6.3.11

EPS Interworking Indication

N2SmInfoType

6.1.6.3.12

N2 SM Information Type

MaxIntegrityProtectedDataRate

6.1.6.3.13

Maximum Integrity Protected Data Rate

MaReleaseIndication

6.1.6.3.14

Multi-Access PDU session release Indication

SmContextType

6.1.6.3.15

Type of SM Context information

PsaIndication

6.1.6.3.16

Indication of whether a PSA is inserted or removed

N4MessageType

6.1.6.3.17

N4 Message Type

QosFlowAccessType

6.1.6.3.18

Access type associated with the QoS Flow

UnavailableAccessIndication

6.1.6.3.19

Indicates the access type of a MA PDU session that is unavailable

ProtectionResult

6.1.6.3.20

Protection Result of the security policy indicated as "preferred"

QosMonitoringReq

6.1.6.3.21

Indicates to measure UL, or DL, or both UL/DL delays, or to stop on-going measurements.

Rsn

6.1.6.3.22

Redundancy Sequence Number

Uint32

3GPP TS 29.571 [13]

Unsigned 32-bit integers

Ipv4Addr

3GPP TS 29.571 [13]

IPv4 Address

Ipv6Prefix

3GPP TS 29.571 [13]

IPv6 Prefix

Uri

3GPP TS 29.571 [13]

Uniform Resource Identifier

Supi

3GPP TS 29.571 [13]

Subscription Permanent Identifier

Pei

3GPP TS 29.571 [13]

Permanent Equipment Identifier

Gpsi

3GPP TS 29.571 [13]

General Public Subscription Identifier

AccessType

3GPP TS 29.571 [13]

Access Type (3GPP or non-3GPP access)

SupportedFeatures

3GPP TS 29.571 [13]

Supported features

Qfi

3GPP TS 29.571 [13]

QoS Flow Identifier

PduSessionId

3GPP TS 29.571 [13]

PDU Session Identifier

PduSessionType

3GPP TS 29.571 [13]

PDU Session Type

Ambr

3GPP TS 29.571 [13]

PDU Session Aggregate Maximum Bit Rate

5Qi

3GPP TS 29.571 [13]

5G QoS Identifier

Arp

3GPP TS 29.571 [13]

Allocation and Retention Priority

ReflectiveQoSAttribute

3GPP TS 29.571 [13]

Reflective QoS Attribute

Dynamic5Qi

3GPP TS 29.571 [13]

QoS characteristics for a 5QI that is neither standardized nor pre-configured.

NonDynamic5Qi

3GPP TS 29.571 [13]

QoS characteristics that replace the default QoS characteristics for a standardized or pre-configured 5QI.

PacketLossRate

3GPP TS 29.571 [13]

Packet Loss Rate

NotificationControl

3GPP TS 29.571 [13]

Notification Control

Dnn

3GPP TS 29.571 [13]

Data Network Name

Snssai

3GPP TS 29.571 [13]

Single Network Slice Selection Assistance Information

NfInstanceId

3GPP TS 29.571 [13]

NF Instance Identifier

UserLocation

3GPP TS 29.571 [13]

User Location

TimeZone

3GPP TS 29.571 [13]

Time Zone

ProblemDetails

3GPP TS 29.571 [13]

Error description

UpSecurity

3GPP TS 29.571 [13]

User Plane Security Policy Enforcement information

RefToBinaryData

3GPP TS 29.571 [13]

Cross-Reference to binary data encoded within a binary body part in an HTTP multipart message.

Guami

3GPP TS 29.571 [13]

Globally Unique AMF ID

BackupAmfInfo

3GPP TS 29.571 [13]

Backup AMF Information

PresenceState

3GPP TS 29.571 [13]

Indicates the UE presence in or out of a LADN service area

TraceData

3GPP TS 29.571 [13]

Trace control and configuration parameters

PlmnId

3GPP TS 29.571 [13]

PLMN Identity

RatType

3GPP TS 29.571 [13]

RAT Type

NgApCause

3GPP TS 29.571 [13]

NGAP Cause

5GMmCause

3GPP TS 29.571 [13]

5G MM Cause

DurationSec

3GPP TS 29.571 [13]

Duration in units of seconds

AdditionalQosFlowInfo

3GPP TS 29.571 [13]

Additional QoS Flow Information

NfGroupId

3GPP TS 29.571 [13]

Network Function Group Id

SecondaryRatUsageReport

3GPP TS 29.571 [13]

Secondary RAT Usage Report

SecondaryRatUsageInfo

3GPP TS 29.571 [13]

Secondary RAT Usage Information

Dnai

3GPP TS 29.571 [13]

Data Network Access Identifier

PlmnIdNid

3GPP TS 29.571 [13]

PLMN Identity and, for SNPN, Network Identity

SmallDataRateStatus

3GPP TS 29.571 [13]

Small Data Rate Control Status

ApnRateStatus

3GPP TS 29.571 [13]

APN Rate Control Status

StationaryIndication

3GPP TS 29.571 [13]

Stationary Indication

ScheduledCommunicationTime

3GPP TS 29.571 [13]

Scheduled Communication Time

ScheduledCommunicationType

3GPP TS 29.571 [13]

Scheduled Communication Type

TrafficProfile

3GPP TS 29.571 [13]

Traffic Profile

BatteryIndication

3GPP TS 29.571 [13]

Battery Indication

NfSetId

3GPP TS 29.571 [13]

NF Set Identifier

MoExpDataCounter

3GPP TS 29.571 [13]

MO Exception Data Counter

DddTrafficDescriptor

3GPP TS 29.571 [13]

Traffic Descriptor

NfServiceSetId

3GPP TS 29.571 [13]

NF Service Set ID

RedirectResponse

3GPP TS 29.571 [13]

Response body of the redirect response message

ServiceName

3GPP TS 29.510 [19]

Service Name

WAgfInfo

3GPP TS 29.510 [19]

Information about N3 terminations at the W-AGF

TngfInfo

3GPP TS 29.510 [19]

Information about N3 terminations at the TNGF

TwifInfo

3GPP TS 29.510 [19]

Information about N3 terminations at the TWIF

ChargingInformation

3GPP TS 29.512 [30]

CHF addresses

NgRanTargetId

3GPP TS 29.518 [20]

NG-RAN Target Id

SbiBindingLevel

3GPP TS 29.518 [20]

SBI Binding Level

IpIndex

3GPP TS 29.519 [38]

Information that identifies which IP pool or external server is used to allocate the IP address.

RoamingChargingProfile

3GPP TS 32.291 [26]

Roaming Charging Profile

supi

Supi

C

0..1

This IE shall be present, except if the UE is emergency registered and UICCless.

When present, it shall contain the subscriber permanent identify.

unauthenticatedSupi

boolean

C

0..1

This IE shall be present if the SUPI is present in the message but is not authenticated and is for an emergency registered UE.

When present, it shall be set as follows:

– true: unauthenticated SUPI;

– false (default): authenticated SUPI.

pei

Pei

C

0..1

This IE shall be present if the UE is emergency registered and it is either UIClless or the SUPI is not authenticated.

For all other cases, this IE shall be present if it is available.

When present, it shall contain the permanent equipment identifier.

gpsi

Gpsi

C

0..1

This IE shall be present if it is available. When present, it shall contain the user’s GPSI.

pduSessionId

PduSessionId

C

0..1

This IE shall be present, except during an EPS to 5GS Idle mode mobility or handover using the N26 interface.

When present, it shall contain the PDU Session ID.

dnn

Dnn

C

0..1

This IE shall be present, except during an EPS to 5GS Idle mode mobility or handover using the N26 interface.

When present, it shall contain the requested DNN; the DNN shall be the full DNN (i.e. with both the Network Identifier and Operator Identifier) for a HR PDU session, and it should be the full DNN in LBO and non-roaming scenarios. If the Operator Identifier is absent, the serving core network operator shall be assumed.

selectedDnn

Dnn

C

0..1

This IE shall be present, if another DNN other than the UE requested DNN is selected for this PDU session.

When present, it shall contain the selected DNN. The DNN shall be the full DNN (i.e. with both the Network Identifier and Operator Identifier) for a HR PDU session, and it should be the full DNN in LBO and non-roaming scenarios. If the Operator Identifier is absent, the serving core network operator shall be assumed.

sNssai

Snssai

C

0..1

This IE shall be present during the PDU session establishment procedure. In this case, it shall contain the requested S-NSSAI for the serving PLMN. This corresponds to an S-NSSAI from the allowed NSSAI.

This IE shall also be present during an EPS to 5GS idle mode mobility or handover with I-SMF/V-SMF involved using the N26 interface. In this case, it shall contain the S-NSSAI configured in the AMF for EPS interworking.

hplmnSnssai

Snssai

C

0..1

This IE shall be present for a roaming PDU session, except during an EPS to 5GS idle mode mobility or handover using the N26 interface.

When present, it shall contain the requested S-NSSAI for the HPLMN. This corresponds to an S-NSSAI from the Mapping Of Allowed NSSAI corresponding to the SNSSAI value included in the sNssai IE.

servingNfId

NfInstanceId

M

1

This IE shall contain the identifier of the serving NF (e.g. serving AMF).

guami

Guami

C

0..1

This IE shall contain the serving AMF’s GUAMI.

It shall be included if the NF service consumer is an AMF.

serviceName

ServiceName

O

0..1

When present, this IE shall contain the name of the AMF service to which SM context status notifications are to be sent (see clause 6.5.2.2 of 3GPP TS 29.500 [4]). This IE may be included if the NF service consumer is an AMF.

servingNetwork

PlmnIdNid

M

1

This IE shall contain the serving core network operator PLMN ID and, for an SNPN, the NID that together with the PLMN ID identifies the SNPN.

requestType

RequestType

C

0..1

This IE shall be present if the request relates to an existing PDU session or an existing emergency PDU session, except during an EPS to 5GS idle mode mobility or handover using the N26 interface. It may be present otherwise.

When present, it shall indicate whether the request refers to a new PDU session or emergency PDU session, or to an existing PDU session or emergency PDU session.

For request sent from UE, this IE shall be set based on the Request type IE received (see clause 9.11.3.47 of 3GPP TS 24.501 [7]).

n1SmMsg

RefToBinaryData

C

0..1

This IE shall be present and reference the N1 SM Message binary data (see clause 6.1.6.4.2), except during an EPS to 5GS Idle mode mobility or handover using N26.

anType

AccessType

M

1

This IE shall indicate the Access Network Type to which the PDU session is to be associated.

additionalAnType

AccessType

C

0..1

This IE shall indicate the additional Access Network Type to which the PDU session is to be associated.

This IE shall be present if a MA-PDU session is requested and the UE is registered over both 3GPP access and Non-3GPP access.

MAPDU

ratType

RatType

C

0..1

This IE shall be present and indicate the RAT Type used by the UE, if available.

presenceInLadn

PresenceState

C

0..1

This IE shall be present if the DNN corresponds to a LADN. When present, it shall be set to "IN" or "OUT" to indicate that the UE is in or out of the LADN service area.

ueLocation

UserLocation

C

0..1

This IE shall contain the UE location information (see clause 5.2.3.4), if it is available. (NOTE 1).

ueTimeZone

TimeZone

C

0..1

This IE shall contain the UE Time Zone, if it is available.

addUeLocation

UserLocation

O

0..1

Additional UE location.

This IE may be present, if anType indicates a non-3GPP access and valid 3GPP access user location information is available.

When present, it shall contain:

– the last known 3GPP access user location (see clause 5.2.3.4); and

– the timestamp, if available, indicating the UTC time when the addUeLocation information was acquired.

(NOTE 1)

smContextStatusUri

Uri

M

1

This IE shall include the callback URI to receive notification of SM context status.

hSmfUri

Uri

C

0..1

This IE shall be present in HR roaming scenarios, including Indirect Communication with Delegated Discovery, if the AMF and V-SMF do not support the ACSCR feature.

This IE shall be present in HR roaming scenarios during a PDU session establishment procedure and EPS to 5GS mobility procedures, if the AMF and V-SMF support the ACSCR feature.

When present, it shall contain the API URI of the Nsmf_PDUSession service of the selected H-SMF. The API URI shall be formatted as specified in clause 6.1.1.

(NOTE 3)

hSmfId

NfInstanceId

O

0..1

This IE may be present when hSmfUri is present.

If present, this IE shall carry the NF instance ID of the selected H-SMF. (NOTE 2)

smfUri

Uri

C

0..1

This IE shall be present for a PDU session with an I-SMF, including Indirect Communication with Delegated Discovery, if the AMF and I-SMF do not support the ACSCR feature.

This IE shall be present for a PDU session with an I-SMF during a PDU session establishment procedure and EPS to 5GS mobility procedures, if the AMF and I-SMF support the ACSCR feature.

When present, it shall contain the API URI of the Nsmf_PDUSession service of the selected SMF. The API URI shall be formatted as specified in clause 6.1.1.

(NOTE 3)

DTSSA

smfId

NfInstanceId

O

0..1

This IE may be present when smfUri is present.

If present, this IE shall carry the NF instance ID of the selected SMF. (NOTE 2)

DTSSA

oldPduSessionId

PduSessionId

C

0..1

This IE shall be present if this information is received from the UE.

When present, it shall contain the old PDU Session ID received from the UE. See clauses 4.3.2.2.1 and 4.3.5.2 of 3GPP TS 23.502 [3].

pduSessionsActivateList

array(PduSessionId)

C

1..N

This IE shall be present, during an EPS to 5GS Idle mode mobility using the N26 interface, if the UE indicated PDU session(s) to be activated in the Registration Request.

When present, it shall indicate all the PDU session(s) requested to be re-activated by the UE.

ueEpsPdnConnection

EpsPdnCnxContainer

C

0..1

This IE shall be present, during an EPS to 5GS Idle mode mobility or handover using the N26 interface.

When present, it shall contain an MME/SGSN UE EPS PDN connection including the EPS bearer context(s).

hoState

HoState

C

0..1

This IE shall be present during an EPS to 5GS handover using N26 interface, to request the preparation of a handover of the PDU session.

When present, it shall be set as specified in clause 5.2.2.2.3.

additionalHsmfUri

array(Uri)

O

1..N

This IE may be present in HR roaming scenarios. When present, it shall contain an array of API URI of the Nsmf_PDUSession service of the additional H-SMFs discovered by the AMF for the given DNN, hplmnSnssai and for this PDU session. If provided, the V-SMF shall use these additional H-SMF(s) if the V-SMF is not able to receive any response from the H-SMF identified by hSmfUri.

The API URI shall be formatted as specified in clause 6.1.1.

additionalHsmfId

array(NfInstanceId)

O

1..N

This IE may be present when additionalHsmfUri is present.

If present, this IE shall carry the NF instance ID(s) of H-SMF(s) as stated in additionalHsmfUri IE, in exactly the same order. (NOTE 2)

additionalSmfUri

array(Uri)

O

1..N

This IE may be present for a PDU session with an I-SMF. When present, it shall contain an array of API URI of the Nsmf_PDUSession service of the additional SMFs discovered by the AMF for the given DNN, Snssai and for this PDU session. If provided, the I-SMF shall use these additional SMF(s) if the I-SMF is not able to receive any response from the SMF identified by smfUri.

The API URI shall be formatted as specified in clause 6.1.1.

DTSSA

additionalSmfId

array(NfInstanceId)

O

1..N

This IE may be present when additionalSmfUri is present.

If present, this IE shall carry the NF instance ID(s) of SMF(s) as stated in additionalSmfUri IE, in exactly the same order. (NOTE 2)

DTSSA

pcfId

NfInstanceId

O

0..1

When present, this IE shall contain the identifier of:

– the H-PCF selected by the AMF (for UE Policy), for a HR PDU session; or

– the V-PCF selected by the AMF (for Access and Mobility Policy), for a PDU session in LBO roaming scenarios; or

– the PCF selected by the AMF (for Access and Mobility Policy and/or UE Policy), for a PDU session in non-roaming scenarios.

pcfGroupId

NfGroupId

O

0..1

This IE may be present in non-roaming and HR roaming scenarios.

When present, this IE shall contain the identity of the (home) PCF group serving the UE for Access and Mobility Policy and/or UE Policy.

pcfSetId

NfSetId

O

0..1

This IE may be present if pcfId IE is present.

When present, this IE shall contain the NF Set ID of the PCF indicated by the pcfId IE.

nrfUri

Uri

O

0..1

This IE may be present to indicate the NRF to use for PCF selection within the same network slice instance. When present, the SMF shall use the NRF URI to select the PCF.

supportedFeatures

SupportedFeatures

C

0..1

This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported.

selMode

DnnSelectionMode

C

0..1

This IE shall be present if it is available. When present, it shall be set to:

– "VERIFIED", if the requested DNN provided by UE or the selected DNN provided by the network corresponds to an explicitly subscribed DNN; or

– "UE_DNN_NOT_VERIFIED", if the requested DNN provided by UE corresponds to the usage of a wildcard subscription; or

– "NW_DNN_NOT_VERIFIED", if the selected DNN provided by the network corresponds to the usage of a wildcard subscription.

If both the requested DNN (i.e. dnn IE) and selected DNN (i.e. selected Dnn IE) are present, the selMode shall be related to the selected DNN.

backupAmfInfo

array(BackupAmfInfo)

C

1..N

This IE shall be included if the NF service consumer is an AMF and the AMF supports the AMF management without UDSF for the following cases:

– First interaction with SMF.

– Modification of the BackupAmfInfo.

traceData

TraceData

C

0..1

This IE shall be included if trace is required to be activated (see 3GPP TS 32.422 [22]).

udmGroupId

NfGroupId

O

0..1

When present, it shall indicate the identity of the UDM group serving the UE.

routingIndicator

string

O

0..1

When present, it shall indicate the Routing Indicator of the UE.

epsInterworkingInd

EpsInterworkingIndication

O

0..1

The AMF may provide the indication when a PGW-C+SMF is selected to serve the PDU Session.

When present, this IE shall indicate whether the PDU session may possibly be moved to EPS and whether N26 interface to be used during EPS interworking procedures.

The AMF may derive the value of the indication from different sources, like UE 5GMM capabilities (e.g. "S1 mode supported"), UE subscription data (e.g. "Core Network Type Restriction to EPC" and "Interworking with EPS Indication" for the DNN) and configurations.

indirectForwardingFlag

boolean

C

0..1

The AMF shall include this indication during N26 based Handover procedure from EPS to 5GS (see 3GPP TS 23.502 [3], clause 4.11.1.2.2), to inform the SMF of the applicability or non-applicability of indirect data forwarding.

When present, it shall be set as follows:

– True: indirect data forwarding is applicable

– False: indirect data forwarding is not applicable

directForwardingFlag

boolean

C

0..1

The AMF shall include this indication during N26 based Handover procedure from EPS to 5GS (see 3GPP TS 23.502 [3], clause 4.11.1.2.2), to inform the SMF of the applicability or non-applicability of direct data forwarding.

When present, it shall be set as follows:

– True: direct data forwarding is applicable

– False: direct data forwarding is not applicable

targetId

NgRanTargetId

C

0..1

This IE shall be present in the following cases:

– during an EPS to 5GS handover preparation using the N26 interface, when the hoState IE is set to the value "PREPARING";

– during N2 based handover procedure with I-SMF or V-SMF insertion/change/removal, when hostate IE is set to the value "PREPARING".

When present, it shall contain the Target ID identifying the target RAN Node ID and TAI. In case of EPS to 5GS handover, the TAI is received in the Forward Relocation Request from the Source MME.

epsBearerCtxStatus

EpsBearerContextStatus

C

0..1

This IE shall be present during an EPS to 5GS idle mode mobility using the N26 interface, if received in the Registration Request from the UE.

When present, it shall be set to the value received from the UE.

cpCiotEnabled

boolean

C

0..1

This IE shall be present with the value "True", if

– the NF service consumer (e.g. the AMF) has verified that the CIOT feature is supported by the SMF (and for a home-routed session, that it is also supported by the H-SMF); and

– Control Plane CIoT 5GS Optimisation is enabled for the PDU session

(see 3GPP TS 23.502 [3], clauses 4.3.2.2.1 and 4.3.2.2.2).

When present, it shall be set as follows:

– True: Control Plane CIoT 5GS Optimisation is enabled.

– False (default): Control Plane CIoT 5GS Optimisation is not enabled.

CIOT

cpOnlyInd

boolean

C

0..1

This IE shall be present with the value "True", if the PDU session shall only use Control Plane CIoT 5GS Optimisation (see clause 5.31.4.1 of 3GPP TS 23.501 [2]).

When present, it shall be set as follows:

– True: the PDU session shall only use Control Plane CIoT 5GS Optimisation

– False (default): the PDU session is not constrained to only use Control Plane CIoT 5GS Optimisation.

CIOT

invokeNef

boolean

C

0..1

This IE shall be present with the value "True", if Control Plane CIoT 5GS Optimisation is enabled and data delivery via NEF is selected for the PDU session (see 3GPP TS 23.502 [3], clause 4.3.2.2.2).

When present, it shall be set as follows:

– True: Data delivery via NEF is selected.

– False (default): Data delivery via NEF is not selected.

CIOT

maRequestInd

boolean

C

0..1

This IE shall be present if a MA-PDU session is requested to be established.

When present, it shall be set as follows:

– True: a MA-PDU session is requested

– False (default): a MA-PDU session is not requested

MAPDU

maNwUpgradeInd

boolean

C

0..1

This IE shall only be present if the PDU session is allowed to be upgraded to MA PDU session (see clause 4.22.3 of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– True: the PDU session is allowed to be upgraded to MA PDU session

– False (default): the PDU session is not allowed to be upgraded to MA PDU session

When maRequestInd is present and set to "true", this IE shall not be present.

MAPDU

n2SmInfo

RefToBinaryData

C

0..1

This IE shall be present if N2 SM Information needs to be sent to the I-SMF.

DTSSA

n2SmInfoType

N2SmInfoType

C

0..1

This IE shall be present if "n2SmInfo" attribute is present.

When present, this IE shall indicate the NG AP IE type for the NG AP SMF related IE container carried in "n2SmInfo" attribute.

DTSSA

n2SmInfoExt1

RefToBinaryData

C

0..1

This IE shall be present if more than one N2 SM Information has been received from the AN.

When present, this IE shall reference the N2 SM Information binary data (see clause 6.1.6.4.3).

DTSSA

n2SmInfoTypeExt1

N2SmInfoType

C

0..1

This IE shall be present if "n2SmInfoExt1" attribute is present.

When present, this IE shall indicate the NG AP IE type for the NG AP SMF related IE container carried in "n2SmInfoExt1" attribute.

DTSSA

smContextRef

Uri

C

0..1

This IE shall be present during an I-SMF or V-SMF insertion if available and during an I-SMF or V-SMF change or removal.

When present, this IE shall contain the URI of the SM Context resource in the SMF or of the SM context resource in the source I-SMF or V-SMF during an I-SMF or V-SMF insertion or during an I-SMF or V-SMF change/removal respectively. The URI shall be an absolute URI, including apiRoot (see clause 6.1.3.3.2).

DTSSA

smContextSmfId

NfInstanceId

O

0..1

This IE may be present if smContextRef is present.

When present, this IE shall carry the NF instance ID of the SMF which hosts the SM Context resource identified by smContextRef IE. (NOTE 2)

DTSSA

smContextSmfSetId

NfSetId

C

0..1

This IE shall be present, if available.

When present, this IE shall contain the NF Set ID of the old V-SMF or the old I-SMF or the SMF as identified by the smContextSmfId.

DTSSA

smContextSmfServiceSetId

NfServiceSetId

C

0..1

This IE shall be present, if available.

When present, this IE shall contain the NF Service Set ID of the PDUSession service instance (for this SmContext) in the old V-SMF or the old I-SMF or the SMF.

DTSSA

smContextSmfBinding

SbiBindingLevel

C

0..1

This IE shall be present, if available.

When present, this IE shall contain the SBI binding level of the SM context resource.

DTSSA

upCnxState

UpCnxState

C

0..1

This IE shall be present to request the activation of the user plane connection of the PDU session, in the following cases:

– during Service Request procedure with an I-SMF insertion / change / removal, or with a V-SMF change (see clause 5.2.2.2.6);

– during Registration procedure with an I-SMF insertion / change / removal, or with a V-SMF insertion / change / removal (see clause 5.2.2.2.7), if this PDU session is requested to be activated by the UE.

DTSSA

smallDataRateStatus

SmallDataRateStatus

C

0..1

This IE shall be present if the small data rate control status is available in AMF, see clause 5.31.14.3 of 3GPP TS 23.501 [2] and clause 4.3.2.2.1 of 3GPP TS 23.502 [3].

CIOT

apnRateStatus

ApnRateStatus

C

0..1

This IE shall be present if the APN rate control status is available in AMF, see clause 4.7.7.3 in 3GPP TS 23.401 [33] and clause 5.2.8.2.5 in 3GPP TS 23.502 [3].

CIOT

extendedNasSmTimerInd

boolean

C

0..1

This IE shall be present with the value "True" if the UE supports CE mode B and use of CE mode B is not restricted according to the Enhanced Coverage Restriction information in the UE context in the AMF.

When present, it shall indicate whether extended NAS SM timers shall be used for the UE as specified in 3GPP TS 24.501 [7], as follows:

– True: extended NAS SM timers shall be used

– False (default): normal NAS SM timers shall be used.

CIOT

dlDataWaitingInd

boolean

C

0..1

This IE shall be present during an EPS to 5GS Idle mode mobility using N26 interface with data forwarding (see clause 4.11.1.3.3A of 3GPP TS 23.502 [3]), if the same indication is received from the MME in the Context Response message.

When present, it shall be set as follows:

– true: DL data needs to be sent to the UE;

– false (default): no DL data needs to be sent to the UE.

CIOT

ddnFailureSubs

DdnFailureSubs

C

0..1

This IE shall be present to subscribe the notification of the DDN Failure if the Availability after DDN failure event is subscribed by the UDM, see clause 4.15.3.2.7 of 3GPP TS 23.502 [3].

CIOT

smfTransferInd

boolean

C

0..1

This IE shall be present during an SMF Context Transfer procedure, LBO or no Roaming, no I-SMF.

When present, it shall be set as follows:

– True: SMF Context Transfer

– False (default): Not an SMF Context Transfer

CTXTR

oldSmfId

NfInstanceId

C

0..1

This IE shall be present if smfTransferInd is set to true.

When present, it shall indicate old SMF instance identifier.

CTXTR

oldSmContextRef

Uri

C

0..1

This IE shall be present if smfTransferInd is set to true.

When present, this IE shall contain the identifier of the SM Context resource in the old SMF.

CTXTR

wAgfInfo

WAgfInfo

C

0..1

This IE shall be present, if received from the W-AGF. When present, it shall contain information about the N3 terminations of the W-AGF. The SMF may use this information when selecting the UPF.

tngfInfo

tngfInfo

C

0..1

This IE shall be present, if received from the TNGF. When present, it shall contain information about the N3 terminations of the TNGF. The SMF may use this information when selecting the UPF.

twifInfo

twifInfo

C

0..1

This IE shall be present, if received from the TWIF. When present, it shall contain information about the N3 terminations of the TWIF. The SMF may use this information when selecting the UPF.

ranUnchangedInd

boolean

C

0..1

This IE shall be present if the NG-RAN is not changed in case the I-SMF/V-SMF change or insertion during CM-CONNECTED registration procedure after EPS to 5GS handover (see clause 5.2.2.2.7).

When present, it shall be set as follows:

– true: NG-RAN is not changed;

– false: NG-RAN is changed.

DTSSA

NOTE 1: In shared networks, when the message is sent from the VPLMN to the HPLMN, the PLMN ID that is communicated in this IE shall be that of the selected Core Network Operator.
In shared networks, when the AMF and SMF pertain to the same PLMN, the Primary PLMN ID shall be communicated in the ECGI or NCGI to the SMF. The Core Network Operator PLMN ID shall be communicated in the TAI and the Serving Network.

NOTE 2: If the SMF is aware that Oauth is enabled for the indicated next hop SMF, e.g. received a "401 Unauthorized" response code from next hop SMF, the SMF shall use the NF instance Identifier to acquire the access token for the Nsmf_PduSession service on the indicated SMF.

NOTE 3: The smfUri and hSmfUri attributes need not be included in Create SM Context request in procedures other than PDU session establishment procedure and EPS to 5GS mobility procedures if the NF Service Consumer (e.g. AMF) and I-SMF/V-SMF support the "ACSCR" feature. See clause 6.1.8.

hsmfUri

Uri

C

0..1

This IE shall be present in HR roaming scenarios if the additionalHsmfUri IE was received in the request and the V-SMF established the PDU session towards an alternative SMF listed in the additionalHsmfUri IE. When present, it shall contain the API URI of the H-SMF towards which the PDU session was established. The API URI shall be formatted as specified in clause 6.1.1.

smfUri

Uri

C

0..1

This IE shall be present for a PDU session with an I-SMF, if the additionalSmfUri IE was received in the request and the I-SMF established the PDU session towards an alternative SMF listed in the additionalSmfUri IE. When present, it shall contain the API URI of the SMF towards which the PDU session was established. The API URI shall be formatted as specified in clause 6.1.1.

DTSSA

pduSessionId

PduSessionId

C

0..1

This IE shall be present, during an EPS to 5GS Idle mode mobility or handover using the N26 interface.

When present, it shall be set to the PDU Session ID.

sNssai

Snssai

C

0..1

This IE shall be present during an EPS to 5GS Idle mode mobility or handover using the N26 interface.

When present, it shall contain the S-NSSAI assigned to the PDU session.

In Home-Routed roaming case, this IE shall contain the S-NSSAI for home PLMN.

upCnxState

UpCnxState

C

0..1

This IE shall be present if the SMF was requested to activate the user plane connection of the PDU session in the corresponding request.

When present, it shall be set as specified in clauses 5.2.2.2.2, 5.2.2.2.6 or 5.2.2.2.7.

n2SmInfo

RefToBinaryData

C

0..1

This IE shall be present if N2 SM Information needs to be sent to the AN.

n2SmInfoType

N2SmInfoType

C

0..1

This IE shall be present if "n2SmInfo" attribute is present.

When present, this IE shall indicate the NG AP IE type for the NG AP SMF related IE container carried in "n2SmInfo" attribute.

allocatedEbiList

array(EbiArpMapping)

C

1..N

This IE shall be present if the consumer NF is an AMF and Inter-system mobility happens. When present, it shall contain an array of EBI to ARP mappings currently allocated to the PDU session.

hoState

HoState

C

0..1

This IE shall be present if the SMF was requested to prepare an EPS to 5GS handover for the PDU session in the corresponding request.

When present, it shall be set as specified in clause 5.2.2.2.3.

gpsi

Gpsi

C

0..1

This IE shall be present if no GPSI IE is provided in the request, e.g. for a PDU session moved from another access or another system, and the SMF knows that a GPSI is already associated with the PDU session (or a GPSI is received from h-SMF for a HR PDU session).

When present, it shall contain the user’s GPSI associated with the PDU session.

smfServiceInstanceId

string

O

0..1

When present, this IE shall contain the serviceInstanceId of the SMF PDUSession service instance serving the SM Context, i.e. of:

– the I-SMF, for a PDU session with I-SMF;

– the V-SMF, for a HR PDU session; or

– the SMF, for a non-roaming or an LBO roaming PDU session without I-SMF.

This IE may be used by the AMF to identify PDU session contexts affected by a failure or restart of the SMF service instance (see clause 6.2 of 3GPP TS 23.527 [24]).

recoveryTime

DateTime

O

0..1

Timestamp when the SMF service instance serving the PDU session was (re)started (see clause 6.3 of 3GPP TS 23.527 [24]).

supportedFeatures

SupportedFeatures

C

0..1

This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported.

selectedSmfId

NfInstanceId

C

0..1

This IE shall be present if a new (h)SMF is selected e.g. by the new I/V-SMF, or a SCP between the new I/V-SMF and the (h)SMF. (NOTE)

When present, it shall contain the selected SMF NF Instance Id.

DTSSA

selectedOldSmfId

NfInstanceId

C

0..1

This IE shall be present if another old I/V-SMF(as alternative to the old I/V-SMF) is selected, e.g. by the new I/V-SMF, anchor SMF or a SCP between the new I/V-SMF and the old I/V-SMF. (NOTE)

When present, it shall contain the selected old I/V-SMF NF Instance Id.

DTSSA

NOTE: During an SmContext Creation procedure, e.g. for I-SMF insertion or I-SMF change procedure, when the new I/V-SMF attempts to contact the old I/V-SMF or (h)SMF by invoking Nsmf_PDUSession_Context Request, if a new (h)SMF and/or another old I/V-SMF has been re-selected (since the old I/V-SMF or the (h)SMF is not reachable) by the new I-/V-SMF or a SCP, the selected old I-/V-SMF and/or (h)SMF shall be returned to the AMF, in order to perform potential subsequent operations on the SMF hosting the resource, e.g. to release the SM Context on old I-/V-SMF, or to create SM Context on SMF when the I/V-SMF needs to be removed.

pei

Pei

C

0..1

This IE shall be present if it is available and has not been provided earlier to the SMF.

When present, this IE shall contain the permanent equipment identifier.

servingNfId

NfInstanceId

C

0..1

This IE shall be present upon inter-AMF change or mobility, or upon a N2 handover execution with AMF change.

When present, it shall contain the identifier of the serving NF (e.g. AMF).

smContextStatusUri

Uri

C

0..1

This IE shall be present if the servingNfId IE is present. It may be present otherwise.

When present, this IE shall include the callback URI to receive notification of SM context status.

guami

Guami

C

0..1

This IE shall be present if the servingNfId of AMF is present.

When present, it shall contain the serving AMF’s GUAMI.

servingNetwork

PlmnIdNid

C

0..1

This IE shall be present if the servingNfId IE is present.

When present, it shall contain the serving core network operator PLMN ID and, for an SNPN, the NID that together with the PLMN ID identifies the SNPN.

backupAmfInfo

array(BackupAmfInfo)

C

1..N

This IE shall be included for the modification of the BackupAmfInfo if the NF service consumer is an AMF and the AMF supports the AMF management without UDSF.

For deleting the backupAmfInfo, it shall contain the Null value.

anType

AccessType

C

0..1

This IE shall be present upon a change of the Access Network Type associated to the PDU session, e.g. during a handover of the PDU session between 3GPP access and untrusted non-3GPP access (see clause 5.2.2.3.5.2).

When present, this IE shall indicate the Access Network Type to which the PDU session is to be associated.

additionalAnType

AccessType

C

0..1

This IE shall indicate the additional Access Network Type to which the PDU session is to be associated.

This IE shall be present when the UE requests to establish resources for MA PDU session over the other access.

MAPDU

anTypeToReactivate

AccessType

C

0..1

This IE shall indicate the Access Network Type for which the UP connection is requested to be re-activated, for a MA PDU session.

MAPDU

ratType

RatType

C

0..1

This IE shall be present and indicate the RAT Type used by the UE, if available, upon a change of RAT Type.

presenceInLadn

PresenceState

C

0..1

This IE shall be present during a Service Request procedure (see clause 5.2.2.3.2.2) ), an Xn handover (see clause 5.2.2.3.3) or a N2 handover execution (see clause 5.2.2.3.4.3), if the DNN of the PDU session corresponds to a LADN. When present, it shall be set to "IN" or "OUT" to indicate that the UE is in or out of the LADN service area.

ueLocation

UserLocation

C

0..1

This IE shall be present if it is available and if it needs to be reported to the SMF (e.g. the user location has changed or the user plane of the PDU session is deactivated).

When present, this IE shall contain:

– the UE location information (see clause 5.2.3.4); and

– the timestamp, if available, indicating the UTC time when the UeLocation information was acquired.

(NOTE 1)

ueTimeZone

TimeZone

C

0..1

This IE shall be present if it is available, the UE Time Zone has changed and needs to be reported to the SMF.

When present, this IE shall contain the UE Time Zone.

addUeLocation

UserLocation

O

0..1

Additional UE location.

This IE may be present, if anType indicates a non-3GPP access and a valid 3GPP access user location information is available.

When present, it shall contain:

– the last known 3GPP access user location (see clause 5.2.3.4); and

– the timestamp, if available, indicating the UTC time when the addUeLocation information was acquired.

(NOTE 1)

upCnxState

UpCnxState

C

0..1

This IE shall be present to request the activation or the deactivation of the user plane connection of the PDU session.

When present, it shall be set as specified in clauses 5.2.2.3.2, 5.2.2.3.15 and 5.2.2.3.16.

hoState

HoState

C

0..1

This IE shall be present to request the preparation, execution or cancellation of a handover of the PDU session.

When present, it shall be set as specified in clause 5.2.2.3.4.

toBeSwitched

boolean

C

0..1

This IE shall be present during an Xn Handover (see clause 5.2.2.3.3) to request to switch the PDU session to a new downlink N3 tunnel endpoint.

When present, it shall be set as follows:

– true: request to switch to the PDU session.

– false (default): no request to switch the PDU session.

failedToBeSwitched

boolean

C

0..1

This IE shall be present during an Xn Handover (see clause 5.2.2.3.3) if the PDU session failed to be setup in the target RAN.

When present, it shall be to true to indicate that the PDU session failed to be setup in the target RAN.

n1SmMsg

RefToBinaryData

C

0..1

This IE shall be present if N1 SM Information has been received from the UE.

When present, this IE shall reference the N1 SM Message binary data (see clause 6.1.6.4.2).

n2SmInfo

RefToBinaryData

C

0..1

This IE shall be present if N2 SM Information has been received from the AN.

When present, this IE shall reference the N2 SM Information binary data (see clause 6.1.6.4.3).

n2SmInfoType

N2SmInfoType

C

0..1

This IE shall be present if "n2SmInfo" attribute is present.

When present, this IE shall indicate the NG AP IE type for the NG AP SMF related IE container carried in "n2SmInfo" attribute.

targetId

NgRanTargetId

C

0..1

This IE shall be present during a N2 handover preparation, when the hoState IE is set to the value "PREPARING".

When present, it shall contain the Target ID identifying the target RAN Node ID and TAI received in the Handover Required from the Source RAN.

targetServingNfId

NfInstanceId

C

0..1

This IE shall be present during a N2 handover preparation with AMF change, when the hoState IE is set to the value "PREPARING".

When present, it shall contain the identifier of the target serving NF (e.g. AMF).

dataForwarding

boolean

C

0..1

This IE shall be present and set as specified in clause 5.2.2.3.9 during a 5GS to EPS handover, or as specified in 5.2.2.3.13 during a N2 based handover with I-SMF insertion/change/removal.

When present, it shall be set as follows:

– true: setup the direct or indirect data forwarding tunnels;

– false (default): data forwarding tunnels are not required to be setup (see clause 5.2.2.3.9).

n9ForwardingTunnel

TunnelInfo

C

0..1

This IE shall be present in the following case:

– UE triggered Service Request with I-SMF change/removal, if requesting to forward buffered downlink data packets at I-UPF (See clause 4.23.4 of 3GPP TS 23.502 [3]).

When present, it shall carry the N9 forwarding tunnel info of I-UPF.

DTSSA

n9DlForwardingTnlList

array (IndirectDataForwardingTunnelInfo)

C

1..N

This IE shall be present in the following case:

– N2 based handover with I-SMF insertion/change/removal, if downlink indirect data forwarding tunnels are requested to be established between target I-UPF and source I-UPF / source UPF (see clause 4.23.7 and 4.23.11 of 3GPP TS 23.502 [3]).

When present, it shall carry the list of N9 downlink indirect data forwarding tunnel(s) info of I-UPF.

DTSSA

n9UlForwardingTnlList

array (IndirectDataForwardingTunnelInfo)

C

1..N

This IE shall be present in the following case:

– N2 based handover with I-SMF insertion/change/removal, if uplink indirect data forwarding tunnels are requested to be established between target I-UPF and source I-UPF / source UPF (see clause 4.23.7 and 4.23.11 of 3GPP TS 23.502 [3]).

When present, it shall carry the list of N9 uplink indirect data forwarding tunnel(s) info of I-UPF.

DTSSA

epsBearerSetup

array(EpsBearerContainer)

C

0..N

This IE shall be present during a 5GS to EPS handover using the N26 interface.

When present, it shall include the EPS bearer context(s) successfully setup in EPS. The array shall be empty if no resource was successfully allocated in EPS for any PDU session.

revokeEbiList

array(EpsBearerId)

C

1..N

This IE shall be present to request the SMF to revoke some EBIs (see clause 4.11.1.4.1 of 3GPP TS 23.502 [3]). When present, it shall contain the EBIs to revoke.

release

boolean

C

0..1

This IE shall be used to indicate a network initiated PDU session release is requested.

This IE shall be present and set as specified in clause 5.2.2.3.10 during P-CSCF restoration procedure, in clause 5.2.2.3.11 during AMF requested PDU Session Release due to duplicated PDU Session Id, in clause 5.2.2.3.12 during AMF requested PDU Session Release due to slice not available, and in clause 5.2.2.3.17 during AMF requested PDU Session Release due to Network Slice-Specific Authentication and Authorization failure or revocation.

When present, it shall be set as follows:

– true: PDU session release is required;

– false (default): PDU session release is not required.

cause

Cause

O

0..1

When present, this IE shall indicate the cause for the requested modification, e.g. the NF Service Consumer cause for requesting to deactivate the user plane connection of the PDU session.

ngApCause

NgApCause

C

0..1

This IE shall be present, if the information is available. When present, this IE shall indicate the cause for the requested modification, e.g. the NGAP cause for requesting to deactivate the user plane connection of the PDU session.

5gMmCauseValue

5GMmCause

C

0..1

This IE shall be included if the AMF received a 5GMM cause code from the UE during any network initiated PDU session modification or release procedure. (e.g 5GMM Status message in response to a Downlink NAS Transport message carrying 5GSM payload).

sNssai

Snssai

C

0..1

This IE shall be present and sent to the V-SMF, during an EPS to 5GS mobility registration using the N26 interface, if the S-NSSAI for the serving PLMN derived from the S-NSSAI of the home PLMN differs from the S-NSSAI provided in the Create SM Context Request.

When present, it shall contain the S-NSSAI for the serving PLMN.

traceData

TraceData

C

0..1

This IE shall be included if trace is required to be activated, modified or deactivated (see 3GPP TS 32.422 [22]).

For trace modification, it shall contain a complete replacement of trace data.

For trace deactivation, it shall contain the Null value.

epsInterworkingInd

EpsInterworkingIndication

O

0..1

This IE may be present if the indication has been provided during the PDU session creation, and its value has changed after session creation or last update.

When present, this IE shall indicate whether the PDU session may possibly be moved to EPS and whether N26 interface to be used during EPS interworking procedures.

anTypeCanBeChanged

boolean

C

0..1

This IE shall be present and set to true to indicate that the Access Network Type associated to the PDU session can be changed (see clause 5.2.2.3.2.4), during a Service Request procedure (see clause 4.2.3.2 of 3GPP TS 23.502 [3])), in response to paging or NAS notification indicating non-3GPP access, when the PDU Session for which the UE was paged or notified is in the List Of Allowed PDU Sessions provided by the UE, and the AMF received N2 SM Information only or N1 SM Container and N2 SM Information from the SMF in step 3a of clause 4.2.3.3 of 3GPP TS 23.502 [3].

When present, it shall be set as follows:

– true: the access type of the PDU session can be changed.

– false (default): the access type of the PDU session cannot be changed.

n2SmInfoExt1

RefToBinaryData

C

0..1

This IE shall be present if more than one N2 SM Information has been received from the AN.

When present, this IE shall reference the N2 SM Information binary data (see clause 6.1.6.4.3).

n2SmInfoTypeExt1

N2SmInfoType

C

0..1

This IE shall be present if "n2SmInfoExt1" attribute is present.

When present, this IE shall indicate the NG AP IE type for the NG AP SMF related IE container carried in "n2SmInfoExt1" attribute.

maReleaseInd

MaReleaseIndication

C

0..1

This IE shall be present if one access of a MA PDU session is requested to be released, in the following cases:

– when UE/AMF initiates MA PDU session release over one access; or

– when UE deregisters from one access.

When present, it indicates the access to be released.

MAPDU

maNwUpgradeInd

boolean

C

0..1

This IE shall be present if the PDU session is allowed to be upgraded to MA PDU session (see clause 6.4.2.2 of 3GPP TS 24.501 [7]).

When present, it shall be set as follows:

– true: the PDU session is allowed to be upgraded to MA PDU session

– false (default): the PDU session is not allowed to be upgraded to MA PDU session

MAPDU

maRequestInd

boolean

C

0..1

This IE shall be present if a MA-PDU session is requested to be established (see clause 4.22.6.3 of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– true: a MA-PDU session is requested

– false (default): a MA-PDU session is not requested

MAPDU

exemptionInd

ExemptionInd

C

0..1

This IE shall be present if the AMF has exempted the NAS message from a NAS SM congestion control activated in the AMF.

supportedFeatures

SupportedFeatures

C

0..1

This IE shall be present if the servingNfId or the targetServingNfId is present (i.e. during a change of AMF) and at least one optional feature defined in clause 6.1.8 is supported by the new AMF.

If this IE is absent when the servingNfId or the targetServingNfId is present, the new serving AMF or the target AMF respectively shall be considered as not supporting any optional feature.

moExpDataCounter

MoExpDataCounter

C

0..1

This IE shall be included if the UE has accessed the network by using "MO exception data" RRC establishment cause and when the AMF decides to send a non-zero value to the SMF.

(NOTE 2)

When present, this IE shall contain the MO Exception Data Counter.

CIOT

extendedNasSmTimerInd

boolean

C

0..1

This IE shall be present if the UE supports CE mode B and use of CE mode B changes from restricted to unrestricted or vice versa in the Enhanced Coverage Restriction information in the UE context in the AMF.

When present, it shall indicate whether extended NAS SM timers shall be used for the UE as specified in 3GPP TS 24.501 [7], as follows:

– True: extended NAS SM timers shall be used

– False: normal NAS SM timers shall be used.

CIOT

forwardingFTeid

Bytes

C

0..1

This IE shall be present during a 5GS to EPS Idle mode mobility using N26 interface with data forwarding (see clause 4.11.1.3.2A of 3GPP TS 23.502 [3]), if the Forwarding F-TEID IE is present in the Context Acknowledge message received from the MME.

When present, it shall contain Base64-encoded characters, encoding the Forwarding F-TEID in the Context Acknowledge message, as specified in Figure 8.22-1 of 3GPP TS 29.274 [16] (starting from octet 1).

CIOT

forwardingBearerContexts

array(ForwardingBearerContainer)

C

1..N

This IE shall be present during a 5GS to EPS Idle mode mobility using N26 interface with data forwarding (see clause 4.11.1.3.2A of 3GPP TS 23.502 [3]), if the Bearer Contexts IE is present in the Context Acknowledge message received from the MME.

When present, it shall contain the Bearer Contexts in the Context Acknowledge message.

CIOT

ddnFailureSubs

DdnFailureSubs

C

0..1

This IE shall be present to subscribe or unsubscribe to the notification of the DDN Failure if the Availability after DDN failure event is subscribed/unsubscribed by the UDM, see clause 4.15.3.2.7 of 3GPP TS 23.502 [3].

This IE shall also be present if it is required to add, modify or remove DDN failure subscriptions. If it is present and the FailureSubsInd indicates notification of DDN failure is subscribed, the content of the received ddnFailureSubs shall overwrite any ddnFailureSubs received earlier.

CIOT

skipN2PduSessionResRelInd

boolean

O

0..1

This IE may be present when the release IE is present with value "true".

When present, this IE shall indicate whether N2 message shall be skipped for the PDU session RAN resources release, if the UP connection is active:

– true: N2 message shall be skipped.

– false (default): N2 message shall not be skipped.

NOTE 1: In shared networks, when the message is sent from the VPLMN to the HPLMN, the PLMN ID that is communicated in this IE shall be that of the selected Core Network Operator.
In shared networks, when the AMF and SMF pertain to the same PLMN, the Primary PLMN ID shall be communicated in the ECGI or NCGI to the SMF. The Core Network Operator PLMN ID shall be communicated in the TAI and the Serving Network.

NOTE 2: The AMF increments the MO Exception Data Counter when the UE establishes/resumes RRC with "MO Exception Data" RRC cause. The AMF may defer sending the moExpDataCounter attribute to the SMF based on local configuration. The AMF resets the MO Exception Data Counter when receiving successful response from the SMF. The SMF however keeps incrementing the counter locally.

upCnxState

UpCnxState

C

0..1

This IE shall be present if the SMF was requested to activate or deactivate the user plane connection of the PDU session in the corresponding request.

When present, it shall be set as specified in clauses 5.2.2.3.2, 5.2.2.3.15 and 5.2.2.3.16.

hoState

HoState

C

0..1

This IE shall be present if the SMF was requested to prepare, execute or cancel a handover for the PDU session in the corresponding request.

When present, it shall be set as specified in clause 5.2.2.3.4.

releaseEbiList

array(EpsBearerId)

C

1..N

This IE shall be present if the SMF determines that some EBIs are not needed. When present, it shall contain the EBIs to be released.

allocatedEbiList

array(EbiArpMapping)

C

1..N

This IE shall be present if the consumer NF is an AMF and Inter-system mobility happens. When present, it shall contain an array of EBI to ARP mappings currently allocated to the PDU session.

modifiedEbiList

array(EbiArpMapping)

C

1..N

This IE shall be present if a PDU session modification procedure resulted in the change of ARP for a QoS flow that was already allocated an EBI.

n1SmMsg

RefToBinaryData

C

0..1

This IE shall be present if N1 SM Information needs to be sent to the UE.

When present, this IE shall reference the N1 SM Message binary data (see clause 6.1.6.4.2).

n2SmInfo

RefToBinaryData

C

0..1

This IE shall be present if N2 SM Information needs to be sent to the AN.

When present, this IE shall reference the N2 SM Information binary data (see clause 6.1.6.4.3).

n2SmInfoType

N2SmInfoType

C

0..1

This IE shall be present if "n2SmInfo" attribute is present.

When present, this IE shall indicate the NG AP IE type for the NG AP SMF related IE container carried in "n2SmInfo" attribute.

epsBearerSetup

array(EpsBearerContainer)

C

1..N

This IE shall be present during an EPS to 5GS handover using the N26 interface.

When present, it shall include the EPS bearer context(s) successfully handed over to 5GS.

dataForwarding

boolean

C

0..1

This IE shall be present if it was present in the corresponding request.

When present, it shall be set as specified in clause 5.2.2.3.9.

n3DlForwardingTnlList

array (IndirectDataForwardingTunnelInfo)

C

1..N

This IE shall be present if indirect data forwarding is requested and N9 downlink indirect data forwarding tunnels info is included in the corresponding request.

When present, it shall carry the list of N3 downlink indirect data forwarding tunnels info of source I-UPF or source UPF.

DTSSA

n3UlForwardingTnlList

array (IndirectDataForwardingTunnelInfo)

C

1..N

This IE shall be present if indirect data forwarding is requested and N9 uplink indirect data forwarding tunnels info is included in the corresponding request.

When present, it shall carry the list of N3 uplink indirect data forwarding tunnels info of source I-UPF or source UPF.

DTSSA

cause

Cause

C

0..1

This IE shall be present if the activation of the User Plane connection failed due to insufficient resources (see clause 5.2.2.3.2.2).

maAcceptedInd

boolean

C

0..1

This IE shall be present if a request to modify a single access PDU session into a MA PDU session was accepted (see clause 4.22.6.3 of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– true: MA PDU session

– false (default): single access PDU session

MAPDU

supportedFeatures

SupportedFeatures

C

0..1

This IE shall be present if the supportedFeatures IE was received in the request and at least one optional feature defined in clause 6.1.8 is supported by the updated SM context resource.

forwardingFTeid

Bytes

C

0..1

This IE shall be present during an EPS to 5GS Idle mode mobility using N26 interface with data forwarding (see clause 4.11.1.3.3A of 3GPP TS 23.502 [3]), if the Forwarding F-TEID IE shall be sent to the MME in the Context Acknowledge message.

When present, it shall contain Base64-encoded characters, encoding the Forwarding F-TEID to be sent in the Context Acknowledge message, as specified in Figure 8.22-1 of 3GPP TS 29.274 [16] (starting from octet 1).

CIOT

forwardingBearerContexts

array(ForwardingBearerContainer)

C

1..N

This IE shall be present during an EOS to 5GS Idle mode mobility using N26 interface with data forwarding (see clause 4.11.1.3.3A of 3GPP TS 23.502 [3]), if the Bearer Contexts IE shall be sent to the MME in the Context Acknowledge message.

When present, it shall contain the Bearer Contexts to be sent in the Context Acknowledge message.

CIOT

selectedSmfId

NfInstanceId

C

0..1

This IE shall be present if a new (h)SMF is selected e.g. by the new I/V-SMF, or a SCP between the new I/V-SMF and the (h)SMF. (NOTE)

When present, it shall contain the selected SMF NF Instance Id.

DTSSA

selectedOldSmfId

NfInstanceId

C

0..1

This IE shall be present if if another old I/V-SMF(as alternative to the old I/V-SMF) is selected, e.g. by the new I/V-SMF or a SCP between the new I/V-SMF and the old I/V-SMF. (NOTE)

When present, it shall contain the selected old I/V-SMF NF Instance Id.

DTSSA

anchorSmfFeatures

AnchorSmfFeatures

O

0..1

This IE may be present to indicate a list of features supported by the (H-)SMF to the AMF.

NOTE: During an SmContext Update procedure, if a new (h)SMF and/or another old I/V-SMF has been re-selected (since the old I/V-SMF or the (h)SMF is not reachable) by the new I-/V-SMF or a SCP, the selected old I-/V-SMF and/or (h)SMF shall be returned to the AMF, in order to perform potential subsequent operations on the SMF hosting the resource, e.g. to release the SM Context on old I-/V-SMF, or to create SM Context on SMF when the I/V-SMF needs to be removed.

cause

Cause

C

0..1

This IE shall be present, if the information is available. When present, this IE shall indicate the NF Service Consumer cause for the requested SM context release.

ngApCause

NgApCause

C

0..1

This IE shall be present, if the information is available. When present, this IE shall indicate the NGAP cause for the requested SM context release.

5gMmCauseValue

5GMmCause

C

0..1

This IE shall be included if the PDU session is released by the AMF due to any 5GMM failure. When present, this IE shall contain the 5GMM cause code value received from the UE.

ueLocation

UserLocation

C

0..1

This IE shall be present, if available.

When present, it shall contain the UE location information (see clause 5.2.3.4). See NOTE.

ueTimeZone

TimeZone

C

0..1

This IE shall be present, if available.

When present, it shall containthe UE Time Zone information.

addUeLocation

UserLocation

O

0..1

Additional UE location.

This IE may be present, if anType previously reported is a non-3GPP access and a valid 3GPP access user location information is available.

When present, it shall contain:

– the last known 3GPP access user location (see clause 5.2.3.4); and

– the timestamp, if available, indicating the UTC time when the addUeLocation information was acquired.

See NOTE.

vsmfReleaseOnly

boolean

C

0..1

This IE shall be present and set to "true" during a 5GS to EPS Idle mode mobility or handover, for a Home Routed PDU session associated with 3GPP access and with assigned EBI(s), or during Registration, UE Triggered Service Request, Inter NG-RAN node Xn based handover and N2 based handover procedures with V-SMF change or removal.

When present, it shall be set as follows:

– true: release the SM context and PDU session in the V-SMF only;

– false (default): release the SM context and PDU session in V-SMF and H-SMF.

n2SmInfo

RefToBinaryData

C

0..1

This IE shall be present if N2 SM Information has been received from the AN.

When present, this IE shall reference the N2 SM Information binary data (see clause 6.1.6.4.3).

n2SmInfoType

N2SmInfoType

C

0..1

This IE shall be present if "n2SmInfo" attribute is present.

When present, this IE shall indicate the NG AP IE type for the NG AP SMF related IE container carried in "n2SmInfo" attribute.

ismfReleaseOnly

boolean

C

0..1

This IE shall be present and set to "true" during a 5GS to EPS Idle mode mobility or handover with I-SMF removal, or during Registration, UE Triggered Service Request, Inter NG-RAN node Xn based handover and N2 based handover with I-SMF change or removal.

When present, it shall be set as follows:

– true: only release the SM context of the PDU session in the I-SMF;

– false (default): release the SM context and PDU session in I-SMF and SMF.

DTSSA

NOTE: In shared networks, when the message is sent from the VPLMN to the HPLMN, the PLMN ID that is communicated in this IE shall be that of the selected Core Network Operator.
In shared networks, when the AMF and SMF pertain to the same PLMN, the Primary PLMN ID shall be communicated in the ECGI or NCGI to the SMF. The Core Network Operator PLMN ID shall be communicated in the TAI and the Serving Network.

targetMmeCap

MmeCapabilities

C

0..1

This IE shall be present if it is available. When present, it shall contain the target MME capabilities.

smContextType

SmContextType

C

0..1

This IE shall be present if this is a request to retrieve the complete SM context, during scenarios with an I-SMF or V-SMF insertion/change/removal, or during SMF Context Transfer procedure for LBO or non-roaming PDU session without I-SMF (see clause 4.26.5.3 of 3GPP TS 23.502 [3]).

DTSSA, CTXTR

servingNetwork

PlmnId

C

0..1

This IE shall be present when the procedure is triggered by a new V-SMF, if the new V-SMF supports inter-PLMN V-SMF change. When present, this IE shall contain the serving core network operator PLMN ID of the NF Service Consumer (i.e. new V-SMF).

DTSSA

notToTransferEbiList

array(EpsBearerId)

C

1..N

This IE shall be present, if the SM context type IE is absent or indicate a request to retrieve the EPS PDN connection, and the AMF determines that certain EPS bearers shall not to be transferred to EPS during a 5GS to EPS mobility procedure, as specified in clause 4.11.1 of 3GPP TS 23.502 [3]. When present, it shall contain the EBI list not to be transferred.

ranUnchangedInd

boolean

C

0..1

This IE shall be present if AN Tunnel is required, in scenario of I-SMF/V-SMF change/insertion during registration procedure after EPS to 5GS handover, when UE is in CM-CONNECTED state (see clause 5.2.2.6.1).

When present, it shall be set as follows:

– true: NG-RAN is not changed and the tunnel information is required;

– false (default):NG-RAN is changed and the tunnel information is not required.

DTSSA

statusInfo

StatusInfo

M

1

This IE shall contain status information about the SM context.

smallDataRateStatus

SmallDataRateStatus

C

0..1

This IE shall be present, if the NF Service Consumer has indicated support of CIoT and if the status is available.

When present, it shall indicate the current small data rate control status for the PDU session.

CIOT

apnRateStatus

ApnRateStatus

C

0..1

This IE shall be present, if the NF Service Consumer has indicated support of CIoT and if the status is available.

When present, it shall indicate the current APN rate control status for the PDN connection (APN rates are shared by all PDN connections of the UE to this APN).

CIOT

ddnFailureStatus

boolean

C

0..1

This IE shall be present if the DDN Failure shall be reported (see clause 5.2.8.2.8 of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– true: DDN failure detected

– false (default): DDN failure is not detected

CIOT

notifyCorrelationIdsForddnFailure

array(string)

C

1..N

This IE shall be present if the DDN Failure shall be reported.

When present, it shall contain the notification correlation Id(s) of the DDN failure subscriptions for which a DDN failure has been detected. This parameter can be useful if the NF service consumer has multiple subscriptions for the same PDU session.

CIOT

newIntermediateSmfId

NfInstanceId

C

0..1

This IE may be present for a PDU session with an I-SMF or V-SMF, if the resourceStatus attribute in statusInfo is set to "UPDATED" and the cause in statusInfo is set to "CHANGED_INTERMEDIATE_SMF".

When present, it shall include the NF instance identifier of the new intermediate SMF when it is changed within an SMF set.

ES3XX

newSmfId

NfInstanceId

C

0..1

This IE may be present if resourceStatus in statusInfo is set to "TRANSFERRED".

When present, it shall include:

– the new I-SMF instance identifier if

the cause in statusInfo is "ISMF_CONTEXT_TRANSFER";

– the new SMF instance identifier if the cause in statusInfo is "SMF_CONTEXT_TRANSFER".

This IE may also be present if the resourceStatus attribute in statusInfo is set to "UPDATED". When present, it shall include the NF instance identifier of the new H-SMF or SMF (for a PDU session with an I-SMF) handling the PDU session, when it is changed within an SMF set, if the cause in statusInfo is "CHANGED_ANCHOR_SMF".

CTXTR

ES3XX

newSmfSetId

NfSetId

C

0..1

This IE may be present if resourceStatus in statusInfo is:

– TRANSFERRED

When present, it shall include:

– The new I-SMF set identifier if cause in statusInfo is "ISMF_SERVICE_CONTEXT_TRANSFER";

– The new SMF set identifier if cause in statusInfo is "SMF_SERVICE_CONTEXT_TRANSFER".

CTXTR

oldSmfId

NfInstanceId

C

0..1

This IE shall be present if resourceStatus in statusInfo is:

– TRANSFERRED

When present, it shall include:

– The old I-SMF instance identifier if cause in statusInfo is "ISMF_CONTEXT_TRANSFER";

– The old SMF instance identifier if cause in statusInfo is "SMF_CONTEXT_TRANSFER".

CTXTR

oldSmContextRef

Uri

C

0..1

This IE may be present if resourceStatus in statusInfo is:

– TRANSFERRED

When present, this IE shall include the identifier of the SM Context resource in the old I-SMF or SMF.

CTXTR

altAnchorSmfUri

Uri

C

0..1

This IE shall be present if resourceStatus in statusInfo is:

– ALT_ANCHOR_SMF

When present, it shall contain the API URI of the alternative (H-)SMF towards which the PDU session is established.

AASN

altAnchorSmfId

NfInstanceId

C

0..1

This IE may be present if resourceStatus in statusInfo is:

– ALT_ANCHOR_SMF

When present, it shall contain the NF Instance Id of the alternative (H-)SMF towards which the PDU session is established.

AASN

NOTE: If resourceStatus in statusInfo is "TRANSFERRED", at least one of newSmfId and newSmfSetId shall be included.

supi

Supi

C

0..1

This IE shall be present, except if the UE is emergency registered and UICCless.

When present, it shall contain the subscriber permanent identify.

unauthenticatedSupi

boolean

C

0..1

This IE shall be present if the SUPI is present in the message but is not authenticated and is for an emergency registered UE.

When present, it shall be set as follows:

– true: unauthenticated SUPI;

– false (default): authenticated SUPI.

pei

Pei

C

0..1

This IE shall be present if the UE is emergency registered and it is either UIClless or the SUPI is not authenticated.

For all other cases, this IE shall be present if it is available.

When present, it shall contain the permanent equipment identifier.

pduSessionId

PduSessionId

C

0..1

This IE shall contain the PDU Session ID, except during an EPS to 5GS Idle mode mobility or handover using the N26 interface.

dnn

Dnn

M

1

This IE shall contain the requested DNN. The DNN shall be the full DNN (i.e. with both the Network Identifier and Operator Identifier) for a HR PDU session, and it should be the full DNN in LBO and non-roaming scenarios. If the Operator Identifier is absent, the serving core network operator shall be assumed.

selectedDnn

Dnn

C

0..1

This IE shall be present, if another DNN other than the UE requested DNN is selected for this PDU session.

When present, it shall contain the selected DNN. The DNN shall be the full DNN (i.e. with both the Network Identifier and Operator Identifier) for a HR PDU session, and it should be the full DNN in LBO and non-roaming scenarios. If the Operator Identifier is absent, the serving core network operator shall be assumed.

sNssai

Snssai

C

0..1

This IE shall be present, except during an EPS to 5GS idle mode mobility or handover using the N26 interface.

When present, it shall contain:

– the requested S-NSSAI mapped to the HPLMN S-NSSAI by the VPLMN for a HR PDU session; or

– the requested S-NSSAI in the serving PLMN for a PDU session with an I-SMF.

vsmfId

NfInstanceId

C

0..1

This IE shall be present for a HR PDU session. When present, it shall contain the identifier of the V-SMF.

ismfId

NfInstanceId

C

0..1

This IE shall be present for a PDU session with an I-SMF. When present, it shall contain the identifier of the I-SMF.

DTSSA

servingNetwork

PlmnIdNid

M

1

This IE shall contain the serving core network operator PLMN ID and, for an SNPN, the NID that together with the PLMN ID identifies the SNPN.

requestType

RequestType

C

0..1

This IE shall be present if the request relates to an existing PDU session or an existing emergency PDU session, except during an EPS to 5GS idle mode mobility or handover using the N26 interface. It may be present otherwise.

When present, it shall indicate whether the request refers to a new PDU session or emergency PDU session, or to an existing PDU session or emergency PDU session.

For request sent from AMF, this IE shall be set based on the requestType received.

epsBearerId

array(EpsBearerId)

C

1..N

This IE shall be present during an EPS to 5GS Idle mode mobility or handover preparation using the N26 interface.

When present, it shall contain the list of EPS bearer Id(s) received from the MME.

pgwS8cFteid

Bytes

C

0..1

This IE shall be present during an EPS to 5GS Idle mode mobility or handover preparation using the N26 interface.

When present, it shall contain Base64-encoded characters, encoding the PGW S8 F-TEID for Control Plane as specified in Figure 8.22-1 of 3GPP TS 29.274 [16] (starting from octet 1), received from the MME.

vsmfPduSessionUri

Uri

C

0..1

This IE shall be present for a HR PDU session. When present, it shall include the callback URI representing the PDU session in the V-SMF.

ismfPduSessionUri

Uri

C

0..1

This IE shall be present for a PDU session with an I-SMF. When present, it shall include the callback URI representing the PDU session in the I-SMF.

DTSSA

vcnTunnelInfo

TunnelInfo

C

0..1

This IE shall be present for a HR PDU session, except for EPS to 5GS handover using N26 interface and when Control Plane CIoT 5GS Optimisation is enabled and data delivery via NEF is selected for this PDU session.

When present, this IE shall contain the N9 tunnel information of the visited CN side, i.e. V-UPF.

icnTunnelInfo

TunnelInfo

C

0..1

This IE shall be present for a PDU session involving an I-SMF, except when Control Plane CIoT 5GS Optimisation is enabled and data delivery via NEF is selected for this PDU session.

When present, this IE shall contain the N9 tunnel information of the I-UPF controlled by the I-SMF.

DTSSA

n9ForwardingTunnelInfo

TunnelInfo

C

0..1

This IE shall be present during Service Request procedures with I-SMF insertion, if buffered DL data is available at the I-UPF that is controlled by the SMF (see clause 4.23.4 in 3GPP TS 23.502 [3]).

When present, this IE shall contain the N9 tunnel information of the I-UPF controlled by the I-SMF.

DTSSA

additionalCnTunnelInfo

TunnelInfo

C

0..1

This IE shall be present if a MA PDU session is requested or if the PDU session is allowed to be upgraded to a MA PDU session, and the UE is registered over both 3GPP access and Non-3GPP access.

When present, it shall contain additional N9 tunnel information of the UPF controlled by the V-SMF or I-SMF.

MAPDU

anType

AccessType

M

1

This IE shall indicate the Access Network Type to which the PDU session is to be associated.

additionalAnType

AccessType

C

0..1

This IE shall indicate the additional Access Network Type to which the PDU session is to be associated.

This IE shall be present if a MA-PDU session is requested and the UE is registered over both 3GPP access and Non-3GPP access.

MAPDU

ratType

RatType

C

0..1

This IE shall be present and indicate the RAT Type used by the UE, if available.

ueLocation

UserLocation

C

0..1

This IE shall contain the UE location information (see clause 5.2.3.4), if it is available. See NOTE 1.

ueTimeZone

TimeZone

C

0..1

This IE shall contain the UE Time Zone, if it is available.

addUeLocation

UserLocation

O

0..1

Additional UE location.

This IE may be present, if anType indicates a non-3GPP access and a valid 3GPP access user location information is available.

When present, it shall contain:

– the last known 3GPP access user location (see clause 5.2.3.4); and

– the timestamp, if available, indicating the UTC time when the addUeLocation information was acquired.

See NOTE 1.

gpsi

Gpsi

C

0..1

This IE shall be present if it is available. When present, it shall contain the user’s GPSI.

n1SmInfoFromUe

RefToBinaryData

C

0..1

This IE shall be present if the V-SMF or I-SMF has received known N1 SM information from the UE that does not need to be interpreted by the V-SMF or I-SMF. When present, this IE shall reference the n1SmInfoFromUe binary data (see clause 6.1.6.4.4).

unknownN1SmInfo

RefToBinaryData

C

0..1

This IE shall be present if the V-SMF or I-SMF has received unknown N1 SM information from the UE. When present, this IE shall reference the unknownN1SmInfo binary data (see clause 6.1.6.4.4).

supportedFeatures

SupportedFeatures

C

0..1

This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported.

hPcfId

NfInstanceId

O

0..1

This IE may be used by V-SMF to indicate the home PCF selected by the AMF for the UE to the H-SMF, for a HR PDU session.

When present, this IE shall contain the identifier of the H-PCF selected by the AMF for the UE (for UE Policy Control).

pcfId

NfInstanceId

O

0..1

This IE may be used by I-SMF to indicate the (V-)PCF selected by the AMF for the UE to the SMF, for a PDU session with an I-SMF.

When present, this IE shall contain the identifier of the PCF (for Access and Mobility Policy Control and/or UE Policy Control) in non-roaming scenarios, or the V-PCF (for Access and Mobility Policy Control) in LBO roaming scenarios.

DTSSA

pcfGroupId

NfGroupId

O

0..1

This IE may be present in non-roaming and HR roaming scenarios.

When present, this IE shall contain the identity of the (home) PCF group serving the UE for Access and Mobility Policy and/or UE Policy.

pcfSetId

NfSetId

O

0..1

When present, it shall contain the NF Set ID of the H-PCF indicated by the hPcfId IE or the (V-)PCF indicated by the pcfId IE.

hoPreparationIndication

boolean

C

0..1

This IE shall be present during an EPS to 5GS handover preparation using the N26 interface or during N2 handover preparation with I-SMF insertion.

When present, it shall be set as follows:

– true: an EPS to 5GS handover preparation or N2 handover preparation with I-SMF is in progress; the PGW-C/SMF shall not switch the DL user plane of the PDU session yet.

– false: there is no on-going EPS to 5GS handover preparation or N2 handover preparation with I-SMF in progress. If a handover preparation was in progress, the handover has been completed. The PGW-C/SMF shall switch the DL user plane of the PDU session using the N9 tunnel information that has been received in the vcnTunnelInfo or icnTunnelInfo.

It shall be set to "true" during an EPS to 5GS handover preparation using the N26 interface or during N2 handover preparation with I-SMF insertion.

selMode

DnnSelectionMode

C

0..1

This IE shall be present if it is available. When present, it shall be set to:

– "VERIFIED", if the requested DNN provided by UE or the selected DNN provided by the network corresponds to an explicitly subscribed DNN; or

– "UE_DNN_NOT_VERIFIED", if the requested DNN provided by UE corresponds to the usage of a wildcard subscription; or

– "NW_DNN_NOT_VERIFIED", if the selected DNN provided by the network corresponds to the usage of a wildcard subscription.

If both the requested DNN (i.e. dnn IE) and selected DNN (i.e. selected Dnn IE) are present, the selMode shall be related to the selected DNN.

alwaysOnRequested

boolean

C

0..1

This IE shall be present and set to true if the UE requests to setup an always-on PDU session and this is allowed by local policy in the V-SMF or I-SMF.

When present, it shall be set as follows:

– true: request for an always-on PDU session

– false (default): not a request for an always-on PDU session

udmGroupId

NfGroupId

O

0..1

When present, it shall indicate the identity of the UDM group serving the UE.

routingIndicator

string

O

0..1

When present, it shall indicate the Routing Indicator of the UE.

epsInterworkingInd

EpsInterworkingIndication

O

0..1

This IE may be present if the indication has been received from AMF and is allowed to be forwarded to H-SMF by operator configuration.

When present, this IE shall indicate whether the PDU session may possibly be moved to EPS and whether N26 interface to be used during EPS interworking procedures.

vSmfServiceInstanceId

string

O

0..1

When present, this IE shall contain the serviceInstanceId of the V-SMF service instance serving the PDU session.

This IE may be used by the H-SMF to identify PDU sessions affected by a failure or restart of the V-SMF service (see clauses 6.2 and 6.3 of 3GPP TS 23.527 [24]).

iSmfServiceInstanceId

string

O

0..1

When present, this IE shall contain the serviceInstanceId of I-SMF service instance serving the PDU session.

This IE may be used by the SMF to identify PDU sessions affected by a failure or restart of the I-SMF service (see clauses 6.2 and 6.3 of 3GPP TS 23.527 [24]).

DTSSA

recoveryTime

DateTime

O

0..1

Timestamp when the V-SMF or I-SMF service instance serving the PDU session was (re)started (see clause 6.3 of 3GPP TS 23.527 [24]).

roamingChargingProfile

RoamingChargingProfile

O

0..1

Roaming Charging Profile applicable in the VPLMN (see clauses 5.1.9.1, 5.2.1.7 and 5.2.2.12.2 of 3GPP TS 32.255 [25]).

chargingId

string

O

0..1

Charging ID (see clauses 5.1.9.1 of 3GPP TS 32.255 [25]).

The string shall encode the Charging ID (32-bit unsigned integer value, with maximum value "4294967295") in decimal representation.

Pattern: ‘^(0|([1-9]{1}[0-9]{0,9}))$’

(NOTE 2)

oldPduSessionId

PduSessionId

C

0..1

This IE shall be present if this information is received from the UE and the same SMF is selected for SSC mode 3.

When present, it shall contain the old PDU Session ID received from the UE. See clauses 4.3.2.2.1 and 4.3.5.2 of 3GPP TS 23.502 [3].

epsBearerCtxStatus

EpsBearerContextStatus

C

0..1

This IE shall be present during an EPS to 5GS idle mode mobility using the N26 interface, if received in the Create SM Context request.

When present, it shall be set to the value received in the Create SM Context request.

amfNfId

NfInstanceId

C

0..1

This IE shall be present if it is received in the Create SM Context request, unless the PDU session is related to regulatory prioritized service.

When present, it shall contain the identifier of the serving AMF.

guami

Guami

C

0..1

This IE shall be present if the amfNfId is present.

When present, it shall contain the serving AMF’s GUAMI.

maxIntegrityProtectedDataRateUl

MaxIntegrityProtectedDataRate

C

0..1

This IE shall be present if it is available.

When present, it shall indicate the maximum integrity protected data rate supported by the UE for uplink.

maxIntegrityProtectedDataRateDl

MaxIntegrityProtectedDataRate

C

0..1

This IE shall be present if it is available.

When present, it shall indicate the maximum integrity protected data rate supported by the UE for downlink.

cpCiotEnabled

boolean

C

0..1

This IE shall be present with the value "True" if the "5gCiotCpEnabled" attribute is received with "True" value in SM Context Create request, indicating the Control Plane CIoT 5GS Optimisation is enabled for the PDU session (see 3GPP TS 23.502 [3], clause 4.3.2.2.2).

When present, it shall be set as follows:

– True: Control Plane CIoT 5GS Optimisation is enabled.

– False (default): Control Plane CIoT 5GS Optimisation is not enabled.

CIOT

cpOnlyInd

boolean

C

0..1

This IE shall be present with the value "True", if the PDU session shall only use Control Plane CIoT 5GS Optimisation (see clause 5.31.4.1 of 3GPP TS 23.501 [2]).

When present, it shall be set as follows:

– True: the PDU session shall only use Control Plane CIoT 5GS Optimisation

– False (default): the PDU session is not constrained to only use Control Plane CIoT 5GS Optimisation.

CIOT

invokeNef

boolean

C

0..1

This IE shall be present with value "True", if Control Plane CIoT 5GS Optimisation is enabled and data delivery via NEF is selected for the PDU session.

When present, it shall be set as follows:

– True: Data delivery via NEF is selected.

– False (default): Data delivery via NEF is not selected.

CIOT

maRequestInd

boolean

C

0..1

This IE shall be present if a MA-PDU session is requested to be established by the UE.

When present, it shall be set as follows:

– True: a MA-PDU session is requested

– False (default): a MA-PDU session is not requested

MAPDU

maNwUpgradeInd

boolean

C

0..1

This IE shall only be present if the PDU session is allowed to be upgraded to MA PDU session (see clause 4.22.3 of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– True: the PDU session is allowed to be upgraded to MA PDU session

– False (default): the PDU session is not allowed to be upgraded to MA PDU session

When maRequestInd is present and set to "true", this IE shall not be present.

MAPDU

dnaiList

array(Dnai)

C

1..N

This IE shall be present over N16a if an I-SMF is inserted into a PDU session during the following procedures: PDU session establishment, Registration, Service Request, Xn based handover, Inter NG-RAN node N2 based handover (see clause 4.23 of 3GPP TS 23.502 [3]).

When present, it shall include the list of DNAIs supported by the I-SMF.

DTSSA

presenceInLadn

PresenceState

C

0..1

This IE shall be present during Xn based handover with I-SMF insertion, if the DNN corresponds to a LADN.

When present, it shall be set to "IN" or "OUT" to indicate that the UE is in or out of the LADN service area.

DTSSA

secondaryRatUsageInfo

array(SecondaryRatUsageInfo)

O

1..N

This IE may be present to report usage data for a secondary RAT for QoS flows and/or the whole PDU session.

DTSSA

smallDataRateStatus

SmallDataRateStatus

C

0..1

This IE shall be present if the small data rate control status is received from AMF, see clause 5.31.14.3 of 3GPP TS 23.501 [2] and clause 4.3.2.2.2 of 3GPP TS 23.502 [3].

CIOT

apnRateStatus

ApnRateStatus

C

0..1

This IE shall be present, if the APN rate control status (APN rates are shared by all PDN connections of the UE to this APN) is received from the AMF, see clause 4.7.7.3 in 3GPP TS 23.401 [33] and clause 4.11.5.3 in 3GPP TS 23.502 [3].

CIOT

dlServingPlmnRateCtl

integer

C

0..1

This IE shall be present if Serving PLMN Rate Control for downlink data packets is enabled in the PLMN and Control Plane CIoT 5GS Optimisation is enabled for the PDU session.

When present, this IE shall contain the maximum allowed number of Downlink NAS Data PDUs per deci hour of the serving PLMN, as specified in clause 5.31.14.2 of 3GPP TS 23.501 [2].

Minimum: 10

CIOT

upSecurityInfo

UpSecurityInfo

C

0..1

This IE shall be present if received from NG-RAN during Xn handover procedure with I-SMF Insertion (see clause 5.2.2.7.5).

When present, this IE shall contain the User Plane Security Information associated to the PDU session. See clause 9.3.1.60 of 3GPP TS 38.413 [9].

DTSSA

vplmnQos

VplmnQos

C

0..1

This IE shall be present for a HR PDU session, if the V-SMF supports the VQOS feature and if VPLMN QoS constraints are required for the PDU session.

When present, this IE shall contain the QoS constraints from the VPLMN.

VQOS

upCnxState

UpCnxState

C

0..1

This IE shall be present to indicate that the User Plane resource for the PDU session is going to be established by the I-SMF/V-SMF, during a service request procedure with I-SMF/V-SMF insertion (see clause 4.23.4.3 of 3GPP TS 23.502 [3]).

When present, this IE shall be set as specified in clause 5.2.2.7.6.

NOTE 1: In shared networks, the PLMN ID that is communicated in this IE shall be that of the selected Core Network Operator.

NOTE 2: Usage of Charging ID with Uint32 value for roaming scenarios may lead to Charging ID collision between SMFs.

pduSessionType

PduSessionType

M

1

This IE shall indicate the selected PDU type.

sscMode

string

M

1

This IE shall indicate the SSC mode applicable to the PDU session.

When present, it shall be encoded as one character in hexadecimal representation, taking a value of "0" to "7", representing the 3 bits of the SSC mode value of the SSC mode IE specified in clause 9.11.4.16 of 3GPP TS 24.501 [7].

Pattern: "^[0-7]$"

Example: SSC mode 3 shall be encoded as "3".

(NOTE 1).

hcnTunnelInfo

TunnelInfo

C

0..1

This IE shall be present for a HR PDU session, except when Control Plane CIoT 5GS Optimisation is enabled and data delivery via NEF is selected for this PDU session.

When present, this IE shall contain the N9 tunnel information of the home CN side, i.e. H-UPF.

cnTunnelInfo

TunnelInfo

C

0..1

This IE shall be present for a PDU session involving an I-SMF, except when Control Plane CIoT 5GS Optimisation is enabled and data delivery via NEF is selected for this PDU session.

When present, this IE shall contain the N9 tunnel information of the SMF.

DTSSA

additionalCnTunnelInfo

TunnelInfo

C

0..1

This IE shall be present if a MA-PDU session is established for a UE registered over both 3GPP access and Non-3GPP access.

When present, it shall contain additional N9 tunnel information of the UPF controlled by the H-SMF or SMF.

MAPDU

sessionAmbr

Ambr

C

0..1

This IE shall be present, except when Control Plane CIoT 5GS Optimisation is enabled for the PDU session.

When present, this IE shall contain the Session AMBR granted to the PDU session.

qosFlowsSetupList

array(QosFlowSetupItem)

C

1..N

This IE shall be present, except when Control Plane CIoT 5GS Optimisation is enabled for the PDU session.

When present, this IE shall contain the full set of QoS flow(s) to establish for the PDU session. It shall contain at least the Qos flow associated to the default Qos rule.

In V-SMF/I-SMF insertion scenarios where no QoS Rule(s) associated to a QoS flow can or need to be sent to the UE, the qosRules attribute of the QosFlowSetupItem may be set to an empty string or to the latest QoS Rule(s) associated to the QoS flow. (NOTE 3)

hSmfInstanceId

NfInstanceId

C

0..1

This IE shall be present for a HR PDU session. When present, it shall contain the identifier of the home SMF.

smfInstanceId

NfInstanceId

C

0..1

This IE shall be present for a PDU session with an I-SMF. When present, it shall contain the identifier of the SMF.

DTSSA

pduSessionId

PduSessionId

C

0..1

This IE shall be present during an EPS to 5GS Idle mode mobility or handover preparation using the N26 interface.

When present, it shall be set to the PDU Session ID.

sNssai

Snssai

C

0..1

This IE shall be present during an EPS to 5GS Idle mode mobility or handover using the N26 interface.

When present, it shall contain:

– the S-NSSAI assigned to the PDU session in the Home PLMN, for a HR PDU session;

– the S-NSSAI assigned to the PDU session in the serving PLMN, for a PDU session with an I-SMF. The Snssai shall overwrite the S-NSSAI earlier stored in I-SMF, if they are different.

enablePauseCharging

boolean

C

0..1

This IE shall be present, based on operator’s policy, to enable the use of Pause of Charging for the PDU session (see clause 4.4.4 of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– true: enable Pause of Charging;

– false (default): disable Pause of Charging.

ueIpv4Address

Ipv4Addr

C

0..1

This IE shall be present if the SMF assigns a UE IPv4 address to the PDU session.

ueIpv6Prefix

Ipv6Prefix

C

0..1

This IE shall be present if the SMF assigns a UE IPv6 prefix to the PDU session.

n1SmInfoToUe

RefToBinaryData

C

0..1

This IE shall be present if the SMF needs to send N1 SM information to the UE that does not need to be interpreted by the V-SMF or I-SMF. When present, this IE shall reference the n1SmInfoToUe binary data (see clause 6.1.6.4.4).

epsPdnCnxInfo

EpsPdnCnxInfo

C

0..1

This IE shall be present if the PDU session may be moved to EPS during its lifetime.

epsBearerInfo

array(EpsBearerInfo)

C

1..N

This IE shall be present if the PDU session may be moved to EPS during its lifetime.

supportedFeatures

SupportedFeatures

C

0..1

This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported.

maxIntegrityProtectedDataRate

MaxIntegrityProtectedDataRate

C

0..1

This IE shall be present if the upSecurity IE is present and indicates that integrity protection is preferred or required.

When present, it shall indicate the maximum integrity protected data rate for uplink.

If the maxIntegrityProtectedDataRateDl IE is absent, this IE applies to both uplink and downlink.

(NOTE 6)

maxIntegrityProtectedDataRateDl

MaxIntegrityProtectedDataRate

C

0..1

This IE may be present if the upSecurity IE is present and indicates that integrity protection is preferred or required.

When present, it shall indicate the maximum integrity protected data rate for downlink.

(NOTE 6)

alwaysOnGranted

boolean

C

0..1

This IE shall be present if the alwaysOnRequested IE was received in the request or if the SMF determines, based on local policy, that the PDU session needs to be established as an always-on PDU session.

When present, it shall be set as follows:

– true: always-on PDU session granted.

– false (default): always-on PDU session not granted.

gpsi

Gpsi

C

0..1

This IE shall be present if no GPSI IE is provided in the request, e.g. for a PDU session moved from another access or another system, and the SMF knows that a GPSI is already associated with the PDU session.

When present, it shall contain the user’s GPSI associated with the PDU session.

upSecurity

UpSecurity

O

0..1

When present, this IE shall indicate the security policy for integrity protection and encryption for the user plane of the PDU session.

If this IE is present, it shall not indicate that integrity protection is preferred or required, if the maxIntegrityProtectedDataRate IE is not present (e.g. if UE Integrity Protection Maximum Data Rate is not available in the SMF).

(NOTE 6)

roamingChargingProfile

RoamingChargingProfile

O

0..1

Roaming Charging Profile selected by the HPLMN (see clauses 5.1.9.1, 5.2.1.7 and 5.2.2.12.2 of 3GPP TS 32.255 [25]).

hSmfServiceInstanceId

string

O

0..1

When present, this IE shall contain the serviceInstanceId of the H-SMF service instance serving the PDU session, for a HR PDU session.

This IE may be used by the V-SMF to identify PDU sessions affected by a failure or restart of the H-SMF service (see clause 6.2 of 3GPP TS 23.527 [24]).

smfServiceInstanceId

string

O

0..1

When present, this IE shall contain the serviceInstanceId of the SMF service instance serving the PDU session, for a PDU session with an I-SMF.

This IE may be used by the I-SMF to identify PDU sessions affected by a failure or restart of the SMF service (see clause 6.2 of 3GPP TS 23.527 [24]).

DTSSA

recoveryTime

DateTime

O

0..1

Timestamp when the SMF service instance serving the PDU session was (re)started (see clause 6.3 of 3GPP TS 23.527 [24]).

dnaiList

array(Dnai)

C

1..N

This IE shall be present over N16a, if available and an I-SMF has been inserted into a PDU session, during the following procedures: PDU session establishment, Registration, Service Request, Xn based handover, Inter NG-RAN node N2 based handover (see clause 4.23 of 3GPP TS 23.502 [3]).

When present, it shall include the list of DNAIs of interest for the PDU session for local traffic steering at the I-SMF.

DTSSA

ipv6MultiHomingInd

boolean

C

0..1

This IE shall be present over N16a, if available and an I-SMF has been inserted into the PDU session during the following procedures: PDU session establishment, Registration, Service Request, Xn based handover, Inter NG-RAN node N2 based handover (see clause 4.23 of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– true: IPv6 multi-homing is permitted.

– false (default): IPv6 multi-homing is not allowed.

DTSSA

maAcceptedInd

boolean

C

0..1

This IE shall be present if a request to establish a MA PDU session was accepted or if a single access PDU session was upgraded into a MA PDU session (see clauses 4.22.2 and 4.22.3 of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– true: MA PDU session

– false (default): single access PDU session

MAPDU

homeProvidedChargingId

string

O

0..1

When present, this IE shall contain the Home provided Charging ID (see 3GPP TS 32.255 [25]).

This IE shall be present during an EPS to 5GS Idle mode mobility or Handover of a HR PDU session. (NOTE 5)

The string shall encode the Charging ID (32-bit unsigned integer value, with maximum value "4294967295") in decimal representation.

Pattern: ‘^(0|([1-9]{1}[0-9]{0,9}))$’

(NOTE 7)

nefExtBufSupportInd

boolean

C

0..1

This IE shall be present with value "true", if NEF has indicated Extended Buffering Support for mobile terminated data in SMF-NEF connection establishment response.

When present, this IE shall be set as following:

– true: Extended Buffering supported by NEF

– false (default): Extended Buffering not supported by NEF

CIOT

smallDataRateControlEnabled

boolean

C

0..1

This IE shall be present and set to "true" if small data rate control is applicable on the PDU session.

When present, it shall be set as follows:

– true: small data rate control is applicable.

– false (default): small data rate control is not applicable.

CIOT

ueIpv6InterfaceId

string

C

0..1

This IE shall be present if the H-SMF/SMF has assigned IPv6 interface identifier to the UE during the PDU session establishment for the Home-routed Roaming scenario or for a PDU session with an I-SMF.

When present, it shall encode the UE IPv6 Interface Identifier to be used by the UE for its link-local address configuration with 16 hexadecimal digits.

Pattern: "^[A-Fa-f0-9]{16}$"

ipv6Index

IpIndex

C

0..1

This IE shall be present if IPv6 Index has been received from PCF during SM Policy Creation. (NOTE 4)

DTSSA

dnAaaAddress

IpAddress

O

0..1

When present, this IE shall contain the address of DN-AAA server for UE IP Address allocation that has been received from UDM. (NOTE 4).

DTSSA

redundantPduSessionInfo

RedundantPduSessionInformation

C

0..1

This IE shall be present for a PDU session with an I-SMF, if Dual Connectivity based end to end Redundant User Plane Paths shall apply as specified in clause 5.33.2.1 of 3GPP TS 23.501 [2].

DCE2ER

NOTE 1: This IE contains information that the V-SMF or I-SMF only needs to transfer to the UE (without interpretation). It is sent as a separate IE rather than within the n1SmInfoToUE binary data because the Selected SSC mode IE is defined as a "V" IE (i.e. without a Type field) in the NAS PDU Session Establishment Accept message.

NOTE 2: In scenarios with a V-SMF/I-SMF insertion, the V-SMF/I-SMF may receive in the Create Response some IEs it has already received during the earlier SM context retrieval from the SMF (e.g. due to the condition of presence of IEs in the Create Response). In such a case, the V-SMF/I-SMF shall overwrite the IEs earlier received with the new IEs received in the Create Response.

NOTE 3: The V-SMF/I-SMF shall ignore any QoS Rule(s) associated to a QoS flow received in PduSessionCreatedData during V-SMF/I-SMF insertion scenarios where no QoS Rule(s) can be sent to the UE, i.e. during Registration, Inter NG-RAN node N2 based handover, and EPS to 5GS Idle mode mobility/handover using N26 interface procedures with V-SMF/I-SMF insertion, or during Service Request and Xn based handover procedures with I-SMF insertion. In such scenarios, the (H-)SMF shall initiate a subsequent PDU session modification procedure if it needs to change the QoS Rules associated to the QoS flows.

NOTE 4: The I-SMF may use IPv6 index to assist in selecting how the IPv6 prefix is to be allocated for local PSA when IPv6 multi-homing is applied for the PDU session. If the IPv6 index indicates UE IP address allocation should be performed towards DN-AAA server, the DN-AAA server address may be included from the SMF to the I-SMF.

NOTE 5: The chargingId IE in SmContext (see clause 6.1.6.2.39) shall be set to the value received in the homeProvidedChargingId IE during an EPS to 5GS Idle mode mobility or Handover of a HR PDU session.

NOTE 6: During inter-system mobility from EPS to 5GS, the UE Integrity Protection Maximum Data Rate is not available at the SMF during PDU Session Creation. The UE will provide UE Integrity Protection Maximum Data Rate to the network within a subsequent UE triggered PDU session modification procedure, as specified in clause 4.3.3.2 of 3GPP TS 23.502 [3].

NOTE 7: Usage of Charging ID with Uint32 value for roaming scenarios may lead to Charging ID collision between SMFs.

requestIndication

RequestIndication

M

1

This IE shall indicate the request type.

pei

Pei

C

0..1

This IE shall be present if it is available and has not been provided earlier to the H-SMF or SMF.

When present, this IE shall contain the permanent equipment identifier.

vcnTunnelInfo

TunnelInfo

C

1

This IE shall be present if the N9 tunnel information on the visited CN side provided earlier to the H-SMF has changed.

When present, this IE shall contain the new N9 tunnel information on the visited CN side.

icnTunnelInfo

TunnelInfo

C

0..1

This IE shall be present if the N9 tunnel information of the I-UPF for DL traffic provided earlier by the I-SMF to the SMF has changed.

When present, this IE shall contain the new N9 tunnel information of the I-UPF.

DTSSA

additionalCnTunnelInfo

TunnelInfo

C

0..1

This IE shall be present if additional N9 tunnel information provided earlier has changed, or if the UE requests to establish resources for a MA PDU session over the other access.

When present, it shall contain additional N9 tunnel information of the UPF controlled by the V-SMF or I-SMF.

MAPDU

servingNetwork

PlmnIdNid

C

0..1

This IE shall contain the serving core network operator PLMN ID, and, for an SNPN, the NID that together with the PLMN ID identifies the SNPN, if the serving network has changed.

anType

AccessType

C

0..1

This IE shall be present if the Access Network Type provided earlier to the H-SMF or SMF has changed, e.g. during a handover of the PDU session between 3GPP access and untrusted non-3GPP access (see clause 5.2.2.8.2.5).

When present, this IE shall indicate the new Access Network Type to which the PDU session is to be associated.

additionalAnType

AccessType

C

0..1

This IE shall indicate the additional Access Network Type to which the PDU session is to be associated.

This IE shall be present when the UE requests to establish resources for MA PDU session over the other access.

MAPDU

ratType

RatType

C

0..1

This IE shall be present and indicate the RAT Type used by the UE, if available, upon a change of RAT Type.

ueLocation

UserLocation

C

0..1

This IE shall be present if it is available, the UE Location has changed and needs to be reported to the H-SMF or SMF.

When present, this IE shall contain:

– the new UE location information (see clause 5.2.3.4); and

– the timestamp, if available, indicating the UTC time when the UeLocation information was acquired.

(NOTE 1)

ueTimeZone

TimeZone

C

0..1

This IE shall be present if it is available, the UE Time Zone has changed and needs to be reported to the H-SMF or SMF.

When present, this IE shall contain the new UE Time Zone.

addUeLocation

UserLocation

O

0..1

Additional UE location.

This IE may be present, if anType indicates a non-3GPP access and a valid 3GPP access user location information is available.

When present, it shall contain:

– the last known 3GPP access user location (see clause 5.2.3.4); and

– the timestamp, if available, indicating the UTC time when the addUeLocation information was acquired.

(NOTE 1)

pauseCharging

boolean

C

0..1

This IE shall be present if the H-SMF or SMF enabled the use of Pause Pause of Charging for the PDU session during the PDU session establishment and

Pause of Charging needs to be started or stopped (see clause 4.4.4 of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– true: to Start Pause of Charging;

– false: to Stop Pause of Charging.

pti

ProcedureTransactionId

C

0..1

This IE shall be present if the requestIndication indicates a UE requested PDU session modification or release. When present, it shall contain the PTI value received from the UE.

n1SmInfoFromUe

RefToBinaryData

C

0..1

This IE shall be present if the V-SMF or I-SMF has received known N1 SM information from the UE that does not need to be interpreted by the V-SMF or I-SMF. When present, this IE shall reference the n1SmInfoFromUe binary data (see clause 6.1.6.4.4).

unknownN1SmInfo

RefToBinaryData

C

0..1

This IE shall be present if the V-SMF or I-SMF has received unknown N1 SM information from the UE. When present, this IE shall reference the unknownN1SmInfo binary data (see clause 6.1.6.4.4).

qosFlowsRelNotifyList

array(QosFlowItem)

C

1..N

This IE shall be present if QoS flows have been released.

qosFlowsNotifyList

array(QosFlowNotifyItem)

C

1..N

This IE shall be present if the QoS targets for GBR QoS flow(s) are not fulfilled anymore or when they are fulfilled again. For each GBR QoS flow indicated as not fulfilled anymore, the V-SMF/I-SMF may also indicate an alternative QoS profile which the NG-RAN currently fulfils in the currentQosProfileIndex IE or indicate that the NG-RAN cannot even fulfil the lowest alternative QoS profile.

NotifyList

array(PduSessionNotifyItem)

C

1..N

Description of notifications related to the PDU session. This IE shall be present if the NG-RAN has established user plane resources for the PDU session that do not fulfil the User Plane Security Enforcement with a value Preferred, or when the user plane security enforcement is fulfilled again.

When present, this IE shall include the notification cause "UP_SEC_NOT_FULFILLED" if at least one of the UP integrity protection or UP ciphering security enforcement is not fulfilled.

If the securityResult IE is present in the message, it provides additional details on the security enforcement results.

epsBearerId

array(EpsBearerId)

C

0..N

This IE shall be present during an EPS to 5GS handover execution using the N26 interface.

When present, it shall contain the list of EPS bearer Id(s) successfully handed over to 5GS. The array shall be empty if no resource was successfully allocated in 5GS for any PDU session.

hoPreparationIndication

boolean

C

0..1

This IE shall be present during an EPS to 5GS handover preparation and handover execution using the N26 interface or during N2 handover execution with I-SMF insertion.

When present, it shall be set as follows:

– true: an EPS to 5GS handover preparation or N2 handover preparation with I-SMF is in progress; the PGW-C/SMF shall not switch the DL user plane of the PDU session yet.

– false: there is no on-going EPS to 5GS handover preparation or N2 handover preparation with I-SMF in progress. If a handover preparation was in progress, the handover has been completed. The PGW-C/SMF shall switch the DL user plane of the PDU session using the N9 tunnel information that has been received in the vcnTunnelInfo or icnTunnelInfo.

It shall be set to "true" during an EPS to 5GS handover preparation using the N26 interface.

It shall be set to "false" during an EPS to 5GS handover execution using the N26 interface or during N2 handover execution with I-SMF insertion.

revokeEbiList

array(EpsBearerId)

C

1..N

This IE shall be present to request the H-SMF or SMF to revoke some EBIs (see clause 4.11.1.4.1 of 3GPP TS 23.502 [3]). When present, it shall contain the EBIs to revoke.

cause

Cause

C

0..1

This IE shall be present and set as specified in clause 5.2.2.8.2.6 during P-CSCF restoration procedure and clause 5.2.2.8.2.3 during 5G-AN requested PDU session resource release procedure.

When present, this IE shall indicate the NF Service Consumer cause of the requested modification.

ngApCause

NgApCause

C

0..1

The V-SMF or I-SMF shall include this IE if it received it from the 5G-AN and, for a HR PDU session, if this information is permitted to be sent to the H-SMF operator according to the V-SMF operator’s policy. When present, this IE shall indicate the NGAP cause for the requested modification.

5gMmCauseValue

5GMmCause

C

0..1

The V-SMF or I-SMF shall include this IE if it received it from the AMF and, for a HR PDU session, if this information is permitted to be sent to the H-SMF operator according to the V-SMF operator’s policy.

alwaysOnRequested

boolean

C

0..1

This IE shall be present and set to true if the UE requests to change the PDU session to an always-on PDU session and this is allowed by local policy in the V-SMF or I-SMF.

When present, it shall be set as follows:

– true: request for an always-on PDU session

– false (default): not a request for an always-on PDU session

epsInterworkingInd

EpsInterworkingIndication

O

0..1

This IE may be present if the indication has been received from AMF and, for a HR PDU session, it is allowed to be forwarded to H-SMF by operator configuration.

When present, this IE shall indicate whether the PDU session may possibly be moved to EPS and whether N26 interface to be used during EPS interworking procedures.

secondaryRatUsageReport

array(SecondaryRatUsageReport)

O

1..N

This IE may be present to report usage data for a secondary RAT for QoS flows.

(NOTE 2)

secondaryRatUsageInfo

array(SecondaryRatUsageInfo)

O

1..N

This IE may be present to report usage data for a secondary RAT for QoS flows and/or the whole PDU session.

anTypeCanBeChanged

boolean

C

0..1

This IE shall be present and set to true to indicate that the Access Network Type associated to the PDU session can be changed (see clause 5.2.2.8.2.2), during a Service Request procedure (see clauses 4.2.3.2 and 4.3.3.3 of 3GPP TS 23.502 [3])), in response to paging or NAS notification indicating non-3GPP access, when the PDU Session for which the UE was paged or notified is in the List Of Allowed PDU Sessions provided by the UE, and the AMF received N2 SM Information only or N1 SM Container and N2 SM Information from the SMF in step 3a of clause 4.2.3.3 of 3GPP TS 23.502 [3].

When present, it shall be set as follows:

– true: the access type of the PDU session can be changed.

– false (default): the access type of the PDU session cannot be changed.

maReleaseInd

MaReleaseIndication

C

0..1

This IE shall be present if a MA PDU session is requested to be released over a single access, in the following cases:

– when UE/AMF/V-SMF initiates MA PDU session release over one access; or

– when UE deregisters from one access.

When present, it shall indicate the access to be released.

MAPDU

maNwUpgradeInd

boolean

C

0..1

This IE shall be present if the PDU session is allowed to be upgraded to MA PDU session (see clause 6.4.2.2 of 3GPP TS 24.501 [7]).

When present, it shall be set as follows:

– true: the PDU session is allowed to be upgraded to MA PDU session

– false (default): the PDU session is not allowed to be upgraded to MA PDU session

MAPDU

maRequestInd

boolean

C

0..1

This IE shall be present if a MA-PDU session is requested to be established (see clause 4.22.6.3 of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– true: a MA-PDU session is requested

– false (default): a MA-PDU session is not requested

MAPDU

unavailableAccesslnd

UnavailableAccessIndication

C

0..1

This IE shall be present if an access of a MA-PDU session is unavailable (see clause 4.22.7 of 3GPP TS 23.502 [3]).

When present, it shall indicate the access that is unavailable.

MAPDU

psaInfo

array(PsaInformation)

C

1..N

This IE shall be present, for a PDU session with an I-SMF, if one or more PSAs UPF are inserted and/or removed by the I-SMF.

DTSSA

ulclBpInfo

UlclBpInformation

C

0..1

This IE shall be present, for a PDU session with an I-SMF, if an UL CL or BP UPF separate from the local PSA is inserted.

DTSSA

n4Info

N4Information

O

0..1

This IE may be present if the I-SMF needs to send N4 information (e.g. traffic usage reporting) to the SMF for traffic offloaded at a PSA controlled by an I-SMF.

DTSSA

n4InfoExt1

N4Information

O

0..1

This IE may be present if the I-SMF needs to send additional N4 information (e.g. traffic usage reporting) to the SMF for traffic offloaded at a PSA controlled by an I-SMF.

DTSSA

n4InfoExt2

N4Information

O

0..1

This IE may be present if the I-SMF needs to send additional N4 information to the SMF (e.g. during a change of PSA).

DTSSA

presenceInLadn

PresenceState

C

0..1

This IE shall be present during Xn based handover with I-SMF change, if the DNN corresponds to a LADN.

When present, it shall be set to "IN" or "OUT" to indicate that the UE is in or out of the LADN service area.

DTSSA

vsmfPduSessionUri

Uri

C

0..1

This IE shall be present during any procedure when the V-SMF has changed, as specified in clause 4.23.4.3 of 3GPP TS 23.502 [3].

When present, it shall include the callback URI representing the PDU session in the new V-SMF.

DTSSA

ismfPduSessionUri

Uri

C

0..1

This IE shall be present during any procedure when the I-SMF has changed, as specified in clause 4.23.4.3 of 3GPP TS 23.502 [3].

When present, it shall include the callback URI representing the PDU session in the new I-SMF.

DTSSA

vsmfId

NfInstanceId

C

0..1

This IE shall be present during any procedure when the V-SMF has changed, as specified in clause 4.23.4.3 of 3GPP TS 23.502 [3].

When present, it shall contain the identifier of the new V-SMF.

DTSSA

ismfId

NfInstanceId

C

0..1

This IE shall be present during any procedure when the I-SMF has changed, as specified in clause 4.23.4.3 of 3GPP TS 23.502 [3].

When present, it shall contain the identifier of the new I-SMF.

DTSSA

vSmfServiceInstanceId

string

O

0..1

This IE may be present during any procedure when the V-SMF has changed, as specified in clause 4.23.4.3 of 3GPP TS 23.502 [3].

When present, this IE shall contain the serviceInstanceId of the new V-SMF service instance serving the PDU session.

This IE may be used by the H-SMF to identify PDU sessions affected by a failure or restart of the V-SMF service (see clauses 6.2 and 6.3 of 3GPP TS 23.527 [24]).

DTSSA

iSmfServiceInstanceId

string

O

0..1

This IE may be present during any procedure when the I-SMF has changed, as specified in clause 4.23.4.3 of 3GPP TS 23.502 [3].

When present, this IE shall contain the serviceInstanceId of the new I-SMF service instance serving the PDU session.

This IE may be used by the SMF to identify PDU sessions affected by a failure or restart of the I-SMF service (see clauses 6.2 and 6.3 of 3GPP TS 23.527 [24]).

DTSSA

dlServingPlmnRateCtl

integer

C

0..1

The IE shall be present when the Serving PLMN Rate Control for Downlink data packets has changed since last update to the H-SMF (for HR PDU session) or SMF (for PDU sessions with an I-SMF).

When present, this IE shall contain the maximum allowed number of Downlink NAS Data PDUs per deci hour of the serving PLMN, as specified in clause 5.31.14.2 of 3GPP TS 23.501 [2]. If Serving PLMN Rate Control is disabled, the IE shall be set to null value.

Minimum: 10

CIOT

dnaiList

array(Dnai)

C

1..N

This IE shall be present over N16a during UE Triggered Service Request procedure with I-SMF change, Xn based handover and Inter NG-RAN node N2 based handover with I-SMF change (see clauses 4.23.4.3, 4.23.11.3 and 4.23.7.3.3 in 3GPP TS 23.502 [3]).

When present, it shall include the list of DNAIs supported by the new I-SMF.

DTSSA

supportedFeatures

SupportedFeatures

C

0..1

This IE shall be present if the vsmfId or the ismfId is present (i.e. during a change of V-SMF or I-SMF) and at least one optional feature defined in clause 6.1.8 is supported by the new V-SMF or I-SMF.

If this IE is absent when the vsmfId or the ismfId is present, the new V-SMF or I-SMF respectively shall be considered as not supporting any optional feature.

roamingChargingProfile

RoamingChargingProfile

O

0..1

This IE may be present during an inter-PLMN V-SMF change. When present, it shall contain the Roaming Charging Profile applicable in the VPLMN (see clauses 5.1.9.1, 5.2.1.7 and 5.2.2.12.2 of 3GPP TS 32.255 [25]).

moExpDataCounter

MoExpDataCounter

C

0..1

This IE shall be present if received from AMF.

When present, this IE shall contain the MO Exception Data Counter.

CIOT

vplmnQos

VplmnQos

O

0..1

When present, this IE shall contain the VPLMN QoS to be applied to the QoS flow with default QoS of the PDU Session.

VQOS

securityResult

SecurityResult

C

0..1

This IE shall be present if received from NG-RAN.

When present, this IE shall contain the Security Result associated to the PDU session. See clause 9.3.1.59 of 3GPP TS 38.413 [9].

upSecurityInfo

UpSecurityInfo

C

0..1

This IE shall be present if received from NG-RAN during Xn handover procedure (see clause 5.2.2.8.2.16).

When present, this IE shall contain the User Plane Security Information associated to the PDU session. See clause 9.3.1.60 of 3GPP TS 38.413 [9].

amfNfId

NfInstanceId

C

0..1

This IE shall be present if it is received in the Update SM Context request.

When present, it shall contain the identifier of the serving AMF.

guami

Guami

C

0..1

This IE shall be present if the amfNfId is present.

When present, it shall contain the serving AMF’s GUAMI.

maxIntegrityProtectedDataRateUl

MaxIntegrityProtectedDataRate

C

0..1

This IE shall be present if received from the UE during PDU session modification procedure, see clause 4.3.3.2 of 3GPP TS 23.502 [3].

When present, it shall indicate the maximum integrity protected data rate supported by the UE for uplink.

maxIntegrityProtectedDataRateDl

MaxIntegrityProtectedDataRate

C

0..1

This IE shall be present if received from the UE during PDU session modification procedure, see clause 4.3.3.2 of 3GPP TS 23.502 [3].

When present, it shall indicate the maximum integrity protected data rate supported by the UE for downlink.

upCnxState

UpCnxState

C

0..1

This IE shall be present to indicate the User Plane resource establishment status in the I-SMF/V-SMF, if an Update or Create request is required to be sent to the (H-)SMF before the User Plane resource for the PDU session is established during a service request procedure for a PDU session with an I-SMF/V-SMF (see clause 4.23.4.2 and clause 4.23.4.3 of 3GPP TS 23.502 [3]).

When present, this IE shall be set as specified in clause 5.2.2.8.2.23.

NOTE 1: In shared networks, the PLMN ID that is communicated in this IE shall be that of the selected Core Network Operator.

NOTE 2: An SMF complying with this version of the specification should report secondary RAT usage using the secondaryRatUsageInfo attribute that replaces the secondaryRatUsageReport attribute.

n1SmInfoToUe

RefToBinaryData

C

0..1

This IE shall be present if the H-SMF/SMF needs to send N1 SM information to the UE that does not need to be interpreted by the V-SMF/I-SMF. When present, this IE shall reference the n1SmInfoToUe binary data (see clause 6.1.6.4.4).

n4Info

N4Information

O

0..1

This IE may be present if the SMF needs to send N4 response information to the I-SMF (e.g. related with traffic usage reporting).

DTSSA

n4InfoExt1

N4Information

O

0..1

This IE may be present if the SMF needs to send additional N4 response information to the I-SMF(e.g. related with traffic usage reporting).

DTSSA

n4InfoExt2

N4Information

O

0..1

This IE may be present if the SMF needs to send additional N4 response information to the I-SMF (e.g. related with traffic usage reporting).

DTSSA

dnaiList

array(Dnai)

C

1..N

This IE shall be present over N16a during UE Triggered Service Request procedure with I-SMF change, Xn based handover and Inter NG-RAN node N2 based handover with I-SMF change (see clauses 4.23.4.3, 4.23.11.3 and 4.23.7.3.3 in 3GPP TS 23.502 [3]).

When present, it shall include the DNAI(s) of interest for this PDU Session.

DTSSA

supportedFeatures

SupportedFeatures

C

0..1

This IE shall be present if the supportedFeatures IE was received in the request and at least one optional feature defined in clause 6.1.8 is supported by the updated PDU session resource.

roamingChargingProfile

RoamingChargingProfile

O

0..1

This IE may be present during an inter-PLMN V-SMF change. When present, it shall contain the Roaming Charging Profile selected by the HPLMN (see clauses 5.1.9.1, 5.2.1.7 and 5.2.2.12.2 of 3GPP TS 32.255 [25]).

ipv6MultiHomingInd

boolean

C

0..1

This IE shall be present over N16a, if available and an I-SMF has been changed during the following procedures: Registration, Service Request, Xn based handover, Inter NG-RAN node N2 based handover (see clause 4.23 of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– true: IPv6 multi-homing is permitted.

– false (default): IPv6 multi-homing is not allowed.

DTSSA

upSecurity

UpSecurity

C

0..1

This IE shall be present if the "upSecurityInfo" IE was received in the request (i.e. during an Xn handover), and there is a mismatch between security policy received and stored (see clause 5.2.2.8.2.16).

When present, this IE shall indicate the security policy for integrity protection and encryption for the user plane of the PDU session.

This IE may be present during a handover from non-3GPP access to 3GPP access, to indicate the security policy for integrity protection and encryption for the user plane of the PDU session in the target access type.

This IE may be present when UE Integrity Protection Maximum Data Rate was received in the request, during a UE triggered PDU session modification procedure.

(NOTE 1, NOTE 2)

maxIntegrityProtectedDataRateUl

MaxIntegrityProtectedDataRate

C

0..1

This IE shall be present if the upSecurity IE is present and indicates that integrity protection is preferred or required.

When present, it shall indicate the maximum integrity protected data rate supported by the UE for uplink.

(NOTE 1)

maxIntegrityProtectedDataRateDl

MaxIntegrityProtectedDataRate

C

0..1

This IE shall be present if the upSecurity IE is present and indicates that integrity protection is preferred or required.

When present, it shall indicate the maximum integrity protected data rate supported by the UE for downlink.

(NOTE 1)

qosFlowsSetupList

array(QosFlowSetupItem)

C

1..N

This IE shall be present during a handover between 3GPP and non-3GPP accesses.

When present, it shall contain the set of QoS flow(s) to establish for the PDU session for the target access type.

(NOTE 1)

sessionAmbr

Ambr

C

0..1

This IE shall be present during a handover between 3GPP and non-3GPP accesses.

When present, this IE shall contain the Session AMBR authorized for the PDU session for the target access type.

(NOTE 1)

epsPdnCnxInfo

EpsPdnCnxInfo

C

0..1

This IE shall be present during a handover from non-3GPP access to 3GPP access, if the PDU session may be moved to EPS during its lifetime.

(NOTE 1)

The IE shall also be included when the EPS PDN Connection Context Information of the PDU session is changed, e.g. due to reselection of anchor SMF.

epsBearerInfo

array(EpsBearerInfo)

C

1..N

This IE shall be present during a handover from non-3GPP access to 3GPP access, if the PDU session may be moved to EPS during its lifetime.

When present, it shall include the complete epsBearerInfo IE(s) for all EBIs.

(NOTE 1)

pti

ProcedureTransactionId

C

0..1

This IE shall be present during a handover between 3GPP and non-3GPP accesses.

When present, it shall contain the PTI value received in the corresponding request.

NOTE 1: During a handover between 3GPP and non-3GPP accesses, the V-SMF or I-SMF shall delete any corresponding information received earlier for the source access type and use the new information received for the target access type.

NOTE 2: During inter-system mobility from EPS to 5GS, the UE Integrity Protection Maximum Data Rate is not available at the SMF during PDU Session Creation. The UE will provide UE Integrity Protection Maximum Data Rate to the network within a subsequent UE triggered PDU session modification procedure, as specified in clause 4.3.3.2 of 3GPP TS 23.502 [3].

cause

Cause

C

0..1

This IE shall be present, if the information is available. When present, this IE shall indicate the NF Service Consumer cause for the requested PDU session release.

ngApCause

NgApCause

C

0..1

This IE shall be present, if the information is available and if this information is permitted to be sent to the H-SMF operator according to the V-SMF operator’s policy. When present, this IE shall indicate the NGAP cause for the requested PDU session release.

5gMmCauseValue

5GMmCause

C

0..1

The V-SMF shall include this IE if it received it from the AMF and if this information is permitted to be sent to the H-SMF operator according to the V-SMF operator’s policy.

ueLocation

UserLocation

C

0..1

This IE shall be present, if available.

When present, it shall contain the UE location information (see clause 5.2.3.4).

ueTimeZone

TimeZone

C

0..1

This IE shall be present, if available.

When present, it shall contain the UE Time Zone.

addUeLocation

UserLocation

O

0..1

Additional UE location.

This IE may be present, if anType previously reported is a non-3GPP access and a valid 3GPP access user location information is available.

When present, it shall contain:

– the last known 3GPP access user location (see clause 5.2.3.4); and

– the timestamp, if available, indicating the UTC time when the addUeLocation information was acquired.

secondaryRatUsageReport

array(SecondaryRatUsageReport)

O

1..N

This IE may be present to report usage data for a secondary RAT for QoS flows.

(NOTE)

secondaryRatUsageInfo

array(SecondaryRatUsageInfo)

O

1..N

This IE may be present to report usage data for a secondary RAT for QoS flows and/or the whole PDU session.

n4Info

N4Information

O

0..1

This IE may be present if the I-SMF needs to send N4 information (e.g. traffic usage reporting) to the SMF for traffic offloaded at a PSA controlled by an I-SMF.

DTSSA

n4InfoExt1

N4Information

O

0..1

This IE may be present if the I-SMF needs to send additional N4 information (e.g. traffic usage reporting) to the SMF for traffic offloaded at a PSA controlled by an I-SMF.

DTSSA

n4InfoExt2

N4Information

O

0..1

This IE may be present if the I-SMF needs to send additional N4 information (e.g. traffic usage reporting) to the SMF for traffic offloaded at a PSA controlled by an I-SMF.

DTSSA

NOTE: An SMF complying with this version of the specification should report secondary RAT usage using the secondaryRatUsageInfo attribute that replaces the secondaryRatUsageReport attribute.

error

ProblemDetails

M

1

More information on the error shall be provided in the "cause" attribute of the "ProblemDetails" structure.

pti

ProcedureTransactionId

C

0..1

This IE shall be present if this is a response sent to a UE requested PDU session modification. When present, it shall contain the PTI value received in the corresponding request.

n1smCause

string

C

0..1

This IE shall be present if the request included n1SmInfoFromUe.

When present, it shall contain the 5GSM cause the H-SMF proposes the V-SMF to return to the UE. It shall be encoded as two characters in hexadecimal representation with each character taking a value of "0" to "9" or "A" to "F", and represent the cause value of the 5GSM cause IE specified in clause 9.11.4.2 of 3GPP TS 24.501 [7].

Pattern: "^[A-F0-9]{2}$"

Example: the cause "Invalid mandatory information" shall be encoded as "60".

See NOTE.

n1SmInfoToUe

RefToBinaryData

C

0..1

This IE shall be present if the H-SMF needs to send N1 SM information to the UE that does not need to be interpreted by the V-SMF. When present, this IE shall reference the n1SmInfoToUe binary data (see clause 6.1.6.4.4).

backOffTimer

DurationSec

O

0..1

When present, this IE shall indicate a Back-off timer value, in seconds, that the V-SMF may use when rejecting the NAS message towards the UE.

recoveryTime

DateTime

O

0..1

Timestamp when the H-SMF service instance was (re)started (see clause 6.3 of 3GPP TS 23.527 [24]).

NOTE: This IE contains information that the V-SMF shall transfer to the UE without interpretation. It is sent as a separate IE rather than within the n1SmInfoToUE binary data because the 5GSM cause IE is defined as a "V" IE (i.e. without a Type field) in the NAS PDU Session Modification Reject message.

requestIndication

RequestIndication

M

1

This IE shall indicate the request type.

sessionAmbr

Ambr

C

1

This IE shall be present if the Session AMBR authorized for the PDU session is modified. When present, it shall contain the new Session AMBR authorized for the PDU session.

qosFlowsAddModRequestList

array(QosFlowAddModifyRequestItem)

C

1..N

This IE shall be present if QoS flows are requested to be established or modified.

qosFlowsRelRequestList

array(QosFlowReleaseRequestItem)

C

1..N

This IE shall be present if QoS flows are requested to be released.

epsBearerInfo

array(EpsBearerInfo)

C

1..N

This IE shall be present if the PDU session may be moved to EPS during its lifetime and the ePSBearerInfo has changed.

When present, it shall only include epsBearerInfo IE(s) for new EBI or for EBIs for which the epsBearerInfo has changed. The complete epsBearerInfo shall be provided for an EBI that is included (i.e. the epsBearerInfo newly received for a given EBI replaces any epsBearerInfo previously received for this EBI).

assignEbiList

array(Arp)

C

1..N

This IE shall be present if the H-SMF requests EBIs to be assigned.

revokeEbiList

array(EpsBearerId)

C

1..N

This IE shall be present if the H-SMF/SMF requests the V-SMF/I-SMF to revoke some EBI(s). When present, it shall contain the EBIs to revoke.

modifiedEbiList

array(EbiArpMapping)

C

1..N

This IE shall be present if a PDU session modification procedure resulted in the change of ARP for a QoS flow that was already allocated an EBI.

pti

ProcedureTransactionId

C

0..1

This IE shall be present if the request is sent in response to a UE requested PDU session modification or release. When present, it shall contain the PTI value received in the corresponding request.

n1SmInfoToUe

RefToBinaryData

C

0..1

This IE shall be present if the H-SMF/SMF needs to send N1 SM information to the UE that does not need to be interpreted by the V-SMF/I-SMF. When present, this IE shall reference the n1SmInfoToUe binary data (see clause 6.1.6.4.4).

alwaysOnGranted

boolean

C

0..1

This IE shall be present if:

– an alwaysOnRequested IE was received in an earlier V-SMF/I-SMF initiated Update request to change the PDU session to an always-on PDU session; or

– the H-SMF/SMF determines, based on local policy, that the PDU session needs to be established as an always-on PDU session.

When present, it shall be set as follows:

– true: always-on PDU session granted.

– false (default): always-on PDU session not granted.

hsmfPduSessionUri

Uri

C

0..1

This IE shall be included if:

– an Update Request is sent to the V-SMF/I-SMF before the Create Response (e.g. for EPS bearer ID allocation as specified in clause 4.11.1.4.1 of 3GPP TS 23.502 [3], or for Secondary authorization/authentication as specified in clause 4.3.2.3 of 3GPP TS 23.502 [3]), and

– the H-SMF PDU Session Resource URI has not been previously provided to the V-SMF/I-SMF.

This IE shall not be included otherwise.

When present, this IE shall include the URI representing the PDU session resource in the H-SMF.

supportedFeatures

SupportedFeatures

C

0..1

This IE shall be present if "hsmfPduSessionUri" IE is present and at least one optional feature defined in clause 6.1.8 is supported.

cause

Cause

O

0..1

When present, this IE shall indicate the cause for the requested modification.

n1smCause

string

O

0..1

When present, this IE shall contain the 5GSM cause the H-SMF proposes the V-SMF/I-SMF to send to the UE. It shall be encoded as two characters in hexadecimal representation with each character taking a value of "0" to "9" or "A" to "F", and represent the cause value of the 5GSM cause IE specified in clause 9.11.4.2 of 3GPP TS 24.501 [7].

Example: the cause "Invalid mandatory information" shall be encoded as "60".

See NOTE.

backOffTimer

DurationSec

O

0..1

When present, this IE shall indicate a Back-off timer value, in seconds, that the V-SMF/I-SMF may use when sending the NAS message (PDU Session Release Command) towards the UE.

maReleaseInd

MaReleaseIndication

C

0..1

This IE shall be present if one access of a MA PDU session is to be released, when H-SMF or SMF initiates MA PDU session release over one access.

When present, it shall indicate the access requested to be released.

MAPDU

maAcceptedInd

boolean

C

0..1

This IE shall be present if a request to modify a single access PDU session into a MA PDU session was accepted (see clause 4.22.6.3 of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– true: MA PDU session

– false (default): single access PDU session

MAPDU

additionalCnTunnelInfo

TunnelInfo

C

0..1

This IE shall be present for a MA-PDU session if the UE requested to establish resources for a MA PDU session over the other access.

When present, it shall contain additional N9 tunnel information of the UPF controlled by the H-SMF or SMF.

MAPDU

dnaiList

array(Dnai)

C

0..N

This IE shall be present if received from PCF during I-SMF Related Procedures with PCF (see clause 4.23.6.2 in 3GPP TS 23.502 [3]).

When present, the IE shall include a list of DNAI(s) the SMF deems relevant for the PDU Session.

DTSSA

n4Info

N4Information

O

0..1

This IE may be present if the SMF needs to send N4 information to the I-SMF for the control of traffic offloaded at a PSA controlled by an I-SMF.

DTSSA

n4InfoExt1

N4Information

O

0..1

This IE may be present if the SMF needs to send additional N4 information to the I-SMF for the control of traffic offloaded at a PSA controlled by an I-SMF.

DTSSA

n4InfoExt2

N4Information

O

0..1

This IE may be present if the SMF needs to send additional N4 information to the I-SMF for the control of traffic offloaded at a PSA controlled by an I-SMF (e.g. during a change of PSA).

DTSSA

smallDataRateControlEnabled

boolean

C

0..1

This IE shall be present if the applicability of small data rate control on the PDU session changes.

When present, it shall be set as follows:

– true: small data rate control is applicable.

– false: small data rate control is not applicable.

CIOT

qosMonitoringInfo

QosMonitoringInfo

C

0..1

This IE may be present if QoS monitoring has been activated for at least one QoS flow of the PDU session (see the qosMonitoringReq attribute in clause 6.1.6.2.22).

DTSSA

epsPdnCnxInfo

EpsPdnCnxInfo

C

0..1

The IE shall be present when the EPS PDN Connection Context Information of the PDU session is changed, e.g. due to change of anchor SMF.

NOTE: This IE contains information that the V-SMF shall transfer to the UE without interpretation. It is sent as a separate IE rather than within the n1SmInfoToUE binary data because the 5GSM cause IE is defined as a "V" IE (i.e. without a Type field) in the NAS PDU Session Release Command message.

qosFlowsAddModList

array(QosFlowItem)

C

1..N

This IE shall be present if QoS flows have been successfully established or modified. For each GBR QoS flow, the V-SMF/I-SMF may also indicate an alternative QoS profile which the NG-RAN currently fulfils in the currentQosProfileIndex IE or indicate that the NG-RAN cannot even fulfil the lowest alternative QoS profile.

qosFlowsRelList

array(QosFlowItem)

C

1..N

This IE shall be present if QoS flows have been successfully released.

qosFlowsFailedtoAddModList

array(QosFlowItem)

C

1..N

This IE shall be present if QoS flows failed to be established or modified.

qosFlowsFailedtoRelList

array(QosFlowItem)

C

1..N

This IE shall be present if QoS flows failed to be released.

n1SmInfoFromUe

RefToBinaryData

C

0..1

This IE shall be present if the V-SMF/I-SMF has received known N1 SM information from the UE that does not need to be interpreted by the V-SMF/I-SMF. When present, this IE shall reference the n1SmInfoFromUe binary data (see clause 6.1.6.4.4).

unknownN1SmInfo

RefToBinaryData

C

0..1

This IE shall be present if the V-SMF/I-SMF has received unknown N1 SM information from the UE. When present, this IE shall reference the unknownN1SmInfo binary data (see clause 6.1.6.4.4).

ueLocation

UserLocation

C

0..1

This IE shall be present if it is available and QoS flows have been successfully established, modified or released.

When present, this IE shall contain the UE location information (see clause 5.2.3.4).

ueTimeZone

TimeZone

C

0..1

This IE shall be present if it is available and QoS flows have been successfully established, modified or released.

When present, this IE shall contain the new UE Time Zone.

addUeLocation

UserLocation

O

0..1

Additional UE location.

This IE may be present, if anType previously reported is a non-3GPP access and a valid 3GPP access user location information is available.

When present, it shall contain:

– the last known 3GPP access user location (see clause 5.2.3.4); and

– the timestamp, if available, indicating the UTC time when the addUeLocation information was acquired.

assignedEbiList

array(EbiArpMapping)

C

1..N

This IE shall be present if the AMF assigned the requested EBI(s). When present, it shall contain the EBIs that were successfully assigned.

failedToAssignEbiList

array(Arp)

C

1..N

This IE shall be present if the AMF failed to assign EBIs for a set of ARPs.

releasedEbiList

array(EpsBearerId)

C

1..N

This IE shall be present if the NF Service Consumer requested the revoke EBI(s) or if the AMF revoked already assigned EBI(s) for this PDU session towards the V-SMF. This IE shall contain the list of EBI(s) released for this PDU session at the AMF.

secondaryRatUsageReport

array(SecondaryRatUsageReport)

O

1..N

This IE may be present to report usage data for a secondary RAT for QoS flows.

(NOTE)

secondaryRatUsageInfo

array(SecondaryRatUsageInfo)

O

1..N

This IE may be present to report usage data for a secondary RAT for QoS flows and/or the whole PDU session.

n4Info

N4Information

O

0..1

This IE may be present if the I-SMF needs to send N4 response information to the SMF for the control of traffic offloaded at a PSA controlled by an I-SMF.

DTSSA

n4InfoExt1

N4Information

O

0..1

This IE may be present if the I-SMF needs to send additional N4 response information to the SMF for the control of traffic offloaded at a PSA controlled by an I-SMF.

DTSSA

n4InfoExt2

N4Information

O

0..1

This IE may be present if the I-SMF needs to send additional N4 response information to the SMF for the control of traffic offloaded at a PSA controlled by an I-SMF (e.g. during a change of PSA).

DTSSA

NOTE: An SMF complying with this version of the specification should report secondary RAT usage using the secondaryRatUsageInfo attribute that replaces the secondaryRatUsageReport attribute.

statusInfo

StatusInfo

M

1

This IE shall contain status information about the PDU session.

smallDataRateStatus

SmallDataRateStatus

C

0..1

This IE shall be present, if the NF Service Consumer has indicated support of CIoT and if the status is available.

When present, it shall indicate the current small data rate control status for the PDU session.

CIOT

apnRateStatus

ApnRateStatus

C

0..1

This IE shall be present, if the NF Service Consumer has indicated support of CIoT and if the status is available.

When present, it shall indicate the current APN rate control status for the PDN connection (APN rates are shared by all PDN connections of the UE to this APN).

CIOT

newSmfId

NfInstanceId

C

0..1

This IE may be present if the resourceStatus attribute in statusInfo is set to "UPDATED" and the cause IE in statusInfo is set to "CHANGED_ANCHOR_SMF".

When present, it shall include the NF instance identifier of the new H-SMF or SMF (for a PDU session with an I-SMF) handling the PDU session, when it is changed within an SMF set.

ES3XX

epsPdnCnxInfo

EpsPdnCnxInfo

C

0..1

This IE shall be present when the EPS PDN Connection Context Information of the PDU session is changed, e.g. due to change of anchor SMF.

When present, this IE shall include the EPS PDN Connection Context Information of the PDU session on the new anchor SMF.

ES3XX

qfi

Qfi

M

1

This IE shall contain the QoS Flow Identifier.

cause

Cause

O

0..1

When present, this IE shall contain cause information.

currentQosProfileIndex

Integer

C

0..1

When present, this IE shall indicate the index of the currently fulfilled alternative QoS profile. This IE shall not be present if the nullQoSProfileIndex IE is present.

nullQoSProfileIndex

boolean

C

0..1

This IE shall be present and set to "true" if the NG-RAN cannot even fulfil the lowest alternative QoS profile. This IE shall not be present if the currentQosProfileIndex IE is present.

qfi

Qfi

M

1

This IE shall contain the QoS Flow Identifier.

qosRules

Bytes

M

1

This IE shall contain the QoS Rule(s) associated to the QoS flow to be sent to the UE. It shall be encoded as the Qos rules IE specified in clause 9.11.4.13 of 3GPP TS 24.501 [7] (starting from octet 4).

ebi

EpsBearerId

C

0..1

This IE shall be included when an EPS Bearer ID is allocated for the QoS Flow for interworking with EPS. When present, this IE shall contain the allocated EPS Bearer ID.

qosFlowDescription

Bytes

O

0..1

When present, this IE shall contain the description of the QoS Flow level Qos parameters to be sent to the UE. It shall be encoded as the Qos flow descriptions IE specified in clause 9.11.4.12 of 3GPP TS 24.501 [7] (starting from octet 1), encoding one single Qos flow description for the QoS flow to be set up.

qosFlowProfile

QosFlowProfile

O

0..1

When present, this IE shall contain the description of the QoS Flow level Qos parameters.

associatedAnType

QosFlowAccessType

O

0..1

This IE may be present if the QoS Flow belongs to MA PDU session.

When present, this IE shall contain the indicated access type associated with the QoS Flow.

MAPDU

defaultQosRuleInd

boolean

C

0..1

This IE shall be present if available.

When present, it shall be set as follows:

– true: QoS Flow is associated with the default QoS Rule.

– false: QoS Flow is not associated with the default QoS Rule.

(NOTE)

NOTE: Anchor SMF implementations complying with earlier versions of the specification may not support setting this Indication. If the attribute is absent, the I-SMF or V-SMF can determine whether the QoS Rule is the default QoS Rule by decoding the available qosRules IE. The absence of the attribute shall not be interpreted as meaning that the QoS flow is not associated with the default QoS Rule.

qfi

Qfi

M

1

This IE shall contain the QoS Flow Identifier.

ebi

EpsBearerId

C

0..1

This IE shall be included when the EPS Bearer ID associated with a QoS Flow is modified. When present, this IE shall contain the EPS Bearer ID.

qosRules

Bytes

O

0..1

When present, this IE shall contain the QoS Rule(s) to be sent to the UE. It shall be encoded as the Qos rules IE specified in clause 9.11.4.13 of 3GPP TS 24.501 [7] (starting from octet 4).

qosFlowDescription

Bytes

O

0..1

When present, this IE shall contain the description of the QoS Flow level Qos parameters to be sent to the UE. It shall be encoded as the Qos flow descriptions IE specified in clause 9.11.4.12 of 3GPP TS 24.501 [7] (starting from octet 1), encoding one single Qos flow description for the QoS flow to be added or modified.

qosFlowProfile

QosFlowProfile

O

0..1

When present, this IE shall contain the description of the QoS Flow level QoS parameters.

When modifying a QoS flow, the IE shall only contain the QoS Flow profile’s attributes which are modified.

associatedAnType

QosFlowAccessType

O

0..1

This IE may be present if the QoS Flow belongs to MA PDU session.

When present, this IE shall contain the indicated access type associated with the QoS Flow.

MAPDU

qfi

Qfi

M

1

This IE shall contain the QoS Flow Identifier.

qosRules

Bytes

O

0..1

When present, this IE shall contain the QoS Rule(s) to be sent to the UE. It shall be encoded as the Qos rules IE specified in clause 9.11.4.13 of 3GPP TS 24.501 [7] (starting from octet 4).

qosFlowDescription

Bytes

O

0..1

When present, this IE shall contain the description of the QoS Flow level Qos parameters to be sent to the UE. It shall be encoded as the Qos flow descriptions IE specified in clause 9.11.4.12 of 3GPP TS 24.501 [7] (starting from octet 1), encoding one single Qos flow description for the QoS flow to be released.

5qi

5Qi

M

1

This IE shall contain the 5G QoS Identifier (5QI) of the QoS flow.

nonDynamic5Qi

NonDynamic5Qi

C

0..1

When present, this IE shall indicate the QoS Characteristics for a standardized or pre-configured 5QI for downlink and uplink.

See NOTE 1.

dynamic5Qi

Dynamic5Qi

C

0..1

When present, this IE shall indicate the QoS Characteristics for a Non-standardised or not pre-configured 5QI for downlink and uplink.

See NOTE 1.

arp

Arp

C

0..1

This IE shall be present when establishing a QoS flow; it may be present when modifying a QoS flow.

When present, this IE shall contain the Allocation and Retention Priority (ARP) assigned to the QoS flow.

gbrQosFlowInfo

GbrQosFlowInformation

C

0..1

This IE shall be present when establishing a GBR QoS flow or if the GBR QoS flow information is modified.

rqa

ReflectiveQoSAttribute

O

0..1

This IE may be present for a non-GBR QoS flow and it shall be ignored otherwise. When present, it shall indicate whether certain traffic on this QoS flow may be subject to Reflective QoS.

additionalQosFlowInfo

AdditionalQosFlowInfo

O

0..1

This IE may be present for a non-GBR QoS flow. When present, this IE indicates that traffic for this QoS flow is likely to appear more often than traffic for other flows established for the PDU session. See clause 9.3.1.12 of 3GPP TS 38.413 [9].

qosMonitoringReq

QosMonitoringReq

O

0..1

This IE may be present to indicate the measurement of UL, or DL, or both UL/DL delays for the associated QoS flow. This IE may also be used to indicate the stop of corresponding measurement, by setting the value to "NONE". See clause 9.3.1.12 of 3GPP TS 38.413 [9].

qosRepPeriod

DurationSec

O

0..1

This IE should be present if QoS monitoring is required.

When present, this IE shall indicate the reporting period. See clause 4.23.5.3 of 3GPP TS 23.502 [3].

NOTE 1: Either the nonDynamic5Qi IE or the dynamic5Qi IE may be present when establishing a QoS flow. Either the nonDynamic5Qi IE or the dynamic5Qi IE may be present when modifying a QoS flow; when present, the received nonDynamic5Qi IE or dynamic5Qi IE shall replace any value received previously for this IE.

maxFbrDl

BitRate

M

1

This IE shall contain the Maximum Bit Rate in Downlink. See 3GPP TS 23.501 [2].

maxFbrUl

BitRate

M

1

This IE shall contain the Maximum Bit Rate in Uplink. See 3GPP TS 23.501 [2].

guaFbrDl

BitRate

M

1

This IE shall contain the Guaranteed Bit Rate in Downlink. See 3GPP TS 23.501 [2].

guaFbrUl

BitRate

M

1

This IE shall contain the Guaranteed Bit Rate in Uplink. See 3GPP TS 23.501 [2].

notifControl

NotificationControl

O

0..1

When present, this IE shall indicate whether notifications are requested from the RAN when the GFBR can no longer (or again) be fulfilled for a QoS flow during the lifetime of the QoS flow. See 3GPP TS 23.501 [2].

maxPacketLossRateDl

PacketLossRate

O

0..1

When present, this IE shall indicate the maximum rate for lost packets that can be tolerated in the downlink direction. See 3GPP TS 23.501 [2].

maxPacketLossRateUl

PacketLossRate

O

0..1

When present, this IE shall indicate the maximum rate for lost packets that can be tolerated in the Uplink direction. See 3GPP TS 23.501 [2].

alternativeQosProfileList

array(AlternativeQosProfile)

O

0..N

When present, this IE shall indicate alternative QoS profiles for the QoS flow. An empty array shall be interpreted as a request to delete any list of alternative QoS profiles associated with this QoS flow.

qfi

Qfi

M

1

This IE shall contain the QoS Flow Identifier.

notificationCause

NotificationCause

M

1

currentQosProfileIndex

Integer

C

0..1

When present, this IE shall indicate the index of the currently fulfilled alternative QoS profile. This IE shall not be present if the nullQoSProfileIndex IE is present.

nullQoSProfileIndex

boolean

C

0..1

This IE shall be present and set to "true" if the NG-RAN cannot even fulfil the lowest alternative QoS profile. This IE shall not be present if the currentQosProfileIndex IE is present.

ueEpsPdnConnection

EpsPdnCnxContainer

M

1

This IE shall contain an MME/SGSN UE EPS PDN Connection including the mapped EPS bearer context(s), if the SM context type was not present in the request or if it was present and indicated a request to retrieve the UE EPS PDN Connection.

This IE shall be set to an empty string if the SM context type was present in the request and indicated a request to retrieve the complete SM context.

smContext

SmContext

C

0..1

This IE shall be present if the SM context type was present in the request and indicated a request to retrieve the complete SM context.

DTSSA

smallDataRateStatus

SmallDataRateStatus

C

0..1

This IE shall be present during N26 based Interworking Procedures, if in the request the smContextType is set to "EPS_PDN_CONNECTION" and if the status is available (see clauses 4.11.1.1 and 4.11.1.3.2 in 3GPP TS 23.502 [3]).

When present, it shall indicate the small data rate control status for the PDU session.

CIOT

apnRateStatus

ApnRateStatus

C

0..1

This IE shall be present during N26 based Interworking Procedures, if in the request the smContextType is set to "EPS_PDN_CONNECTION" and if the status is available (see clauses 4.11.1.1 and 4.11.1.3.2 in 3GPP TS 23.502 [3]).

When present, it shall indicate the APN rate control status for the PDN connection (APN rates are shared by all PDN connections of the UE to this APN).

CIOT

dlDataWaitingInd

boolean

C

0..1

This IE shall be present, if the SM context type was not present in the request or if it was present and indicated a request to retrieve the UE EPS PDN Connection, and if downlink data buffered in the SMF/UPF needs to be forwarded to EPS (see clause 4.11.1.3.2A of 3GPP TS 23.502 [3]).

When present, it shall be set as follows:

– true: DL data needs to be sent to the UE;

– false (default): no DL data needs to be sent to the UE.

CIOT

ipv4Addr

Ipv4Addr

C

0..1

When present, this IE shall contain the GTP tunnel IPv4 address.

At least one of the ipv4Addr or ipv6Addr shall be present. Both may be present.

ipv6Addr

Ipv6Addr

C

0..1

When present, this IE shall contain the GTP tunnel IPv6 address.

At least one of the ipv4Addr or ipv6Addr shall be present. Both may be present.