Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 29.502  Word version:  18.5.0

Top   Top   Up   Prev   Next
1…   5…   5.2.2…   5.2.2.2.4…   5.2.2.3…   5.2.2.3.2…   5.2.2.3.3…   5.2.2.3.6…   5.2.2.3.8…   5.2.2.3.10…   5.2.2.3.17…   5.2.2.3.23…   5.2.2.4…   5.2.2.8…   5.2.2.8.2…   5.2.2.8.2.7…   5.2.2.8.2.12…   5.2.2.8.2.20…   5.2.2.8.3…   5.2.2.8.3.6…   5.2.2.9…   5.2.3…   6…   6.1.2…   6.1.3…   6.1.3.3…   6.1.3.5…   6.1.3.6…   6.1.3.7…   6.1.4…   6.1.6…   6.1.6.2…   6.1.6.2.5…   6.1.6.2.11…   6.1.6.2.18…   6.1.6.2.27…   6.1.6.2.40…   6.1.6.2.54…   6.1.6.2.65…   6.1.6.3…   6.1.6.4…   6.1.7…   A…   B…   C… 
6.1.6.2 Structured data types  6.1.6.2.1 Introduction  6.1.6.2.2 Type: SmContextCreateData  6.1.6.2.3 Type: SmContextCreatedData  6.1.6.2.4 Type: SmContextUpdateData 
...

 

6.1.6.2  Structured data types  p. 137

6.1.6.2.1  Introduction  p. 137
This clause defines the structures to be used in resource representations.
6.1.6.2.2  Type: SmContextCreateData  p. 138
Attribute name Data type P Cardi­nality Description Applica­bility
supiSupiC0..1This IE shall be present, except if the UE is emergency registered and UICCless.
When present, it shall contain the subscriber permanent identify.
unauthenticatedSupibooleanC0..1This 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.
roamingUeIndbooleanO0..1This IE may be present, when the requestType IE indicates that the request refers to an emergency PDU session and the supi IE is present.
When present, this IE shall indicate whether the UE is a roaming UE or not:
  • true: the UE is a roaming UE.
  • false: the UE is a non-roaming UE.
peiPeiC0..1This 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.
gpsiGpsiC0..1This IE shall be present if it is available. When present, it shall contain the user's GPSI.
pduSessionIdPduSessionIdC0..1This 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.
dnnDnnC0..1This 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.
selectedDnnDnnC0..1This 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.
sNssaiSnssaiC0..1This 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.
altSnssaiSnssaiC0..1This IE shall be present during the PDU session establishment procedure if the NF service consumer supports the network slice replacement, and the network slice indicated in the sNssai IE is requested to be replaced. In this case, the NF service consumer shall send the S-NSSAI and the alternative S-NSSAI. See clause 5.15.19 of TS 23.501.NSRP
hplmnSnssaiSnssaiC0..1This 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.
altHplmnSnssaiSnssaiC0..1This IE shall be present for HR PDU session during the PDU session establishment procedure if the NF service consumer supports the network slice replacement, and the network slice indicated in the hplmnSnssai IE is requested to be replaced. In this case, the NF service consumer shall send the HPLMN S-NSSAI and the alternative HPLMN S-NSSAI. See clause 5.15.19 of TS 23.501.NSRP
servingNfIdNfInstanceIdM1This IE shall contain the identifier of the serving NF (e.g. serving AMF).
guamiGuamiC0..1This IE shall contain the serving AMF's GUAMI.
It shall be included if the NF service consumer is an AMF.
serviceNameServiceNameO0..1When 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 TS 29.500). This IE may be included if the NF service consumer is an AMF.
servingNetworkPlmnIdNidM1This 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.
requestTypeRequestTypeC0..1This IE shall be present if the Request type IE is received from the UE for a single access PDU session and if the request refers to an existing PDU session or an existing emergency PDU session. The requestType IE shall not be included for a MA-PDU session establishment request. 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 TS 24.501).
n1SmMsgRefToBinaryDataC0..1This 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.
anTypeAccessTypeM1This IE shall indicate the Access Network Type to which the PDU session is to be associated.
additionalAnTypeAccessTypeC0..1This 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
ratTypeRatTypeC0..1This IE shall be present and indicate the RAT Type used by the UE, if available.
presenceInLadnPresenceStateC0..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.
perLadnDnnSnssaiIndbooleanC0..1This IE shall be present, if the AMF enforces the LADN Service Area per LADN DNN and S-NSSAI (see clause 4.3.2.2.1 of TS 23.502).
When present, it shall indicate that the PDU Session is subject to LADN per LADN DNN and S-NSSAI and be set as follows:
  • True: the PDU Session is subject to LADN per LADN DNN and S-NSSAI.
  • False (default): the PDU Session is not subject to LADN per LADN DNN and S-NSSAI.
ueLocationUserLocationC0..1This IE shall contain the UE location information (see clause 5.2.3.4), if it is available. (NOTE 1).
ueTimeZoneTimeZoneC0..1This IE shall contain the UE Time Zone, if it is available.
addUeLocationUserLocationO0..1Additional 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)
smContextStatusUriUriM1This IE shall include the callback URI to receive notification of SM context status.
hSmfUriUriC0..1This 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 8)
hSmfIdNfInstanceIdO0..1This 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)
smfUriUriC0..1This 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 8)		DTSSA
smfIdNfInstanceIdO0..1This 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
oldPduSessionIdPduSessionIdC0..1This 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 TS 23.502.
pduSessionsActivateListarray(PduSessionId)C1..NThis 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.
ueEpsPdnConnectionEpsPdnCnxContainerC0..1This 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).
hoStateHoStateC0..1This IE shall be present during an EPS to 5GS handover using N26 interface or during a N2 handover with I-SMF insertion/change/removal procedure, to request the preparation of a handover of the PDU session.
When present, it shall be set as specified in clauses 5.2.2.2.3 or 5.2.2.2.5.
additionalHsmfUriarray(Uri)O1..NThis 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.
additionalHsmfIdarray(NfInstanceId)O1..NThis 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)
additionalSmfUriarray(Uri)O1..NThis 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
additionalSmfIdarray(NfInstanceId)O1..NThis 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
pcfIdNfInstanceIdO0..1When 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.
pcfGroupIdNfGroupIdO0..1This 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.
pcfSetIdNfSetIdO0..1This 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.
nrfUriUriO0..1This 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.
supportedFeaturesSupportedFeaturesC0..1This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported.
selModeDnnelectionModeC0..1This 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.
backupAmfInfoarray(BackupAmfInfo)C1..NThis 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.
traceDataTraceDataC0..1This IE shall be included if trace is required to be activated (see TS 32.422).
udmGroupIdNfGroupIdO0..1When present, it shall indicate the identity of the UDM group serving the UE.
routingIndicatorstringO0..1When present, it shall indicate the Routing Indicator of the UE.
hNwPubKeyIdintegerO0..1When present, it shall indicate the Home Network Public Key Identifier of the UE. (NOTE 3)
epsInterworkingIndEpsInterworkingIndicationO0..1The 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.
indirectForwardingFlagbooleanC0..1The AMF shall include this indication during N26 based Handover procedure from EPS to 5GS (see clause 4.11.1.2.2 of TS 23.502), 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
directForwardingFlagbooleanC0..1The AMF shall include this indication during N26 based Handover procedure from EPS to 5GS (see clause 4.11.1.2.2 of TS 23.502), 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
targetIdNgRanTargetIdC0..1This 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.
epsBearerCtxStatusEpsBearerContextStatusC0..1This 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.
cpCiotEnabledbooleanC0..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 clauses 4.3.2.2.1 and 4.3.2.2.2 of TS 23.502). 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
cpOnlyIndbooleanC0..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 TS 23.501).
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
invokeNefbooleanC0..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 clause 4.3.2.2.2 of TS 23.502).
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
maRequestIndbooleanC0..1This 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 requested4
MAPDU
maNwUpgradeIndbooleanC0..1This IE shall only be present if the PDU session is allowed to be upgraded to MA PDU session (see clause 4.22.3 of TS 23.502).
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
n3gPathSwitchSupportIndbooleanC0..1This IE shall be present if AMF supports non-3GPP access path switching while maintaining two N2 connections for non-3GPP access, the selected SMF supports non-3GPP path switching and if the UE supports non-3GPP access path switching for a MA-PDU session.
When present, it shall be set as follows:
  • true: non-3GPP access path switching is supported
  • false (default): non-3GPP access path switching is not supported
N3GPS
n2SmInfoRefToBinaryDataC0..1This IE shall be present if N2 SM Information needs to be sent to the I-SMF.DTSSA
n2SmInfoTypeN2SmInfoTypeC0..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
n2SmInfoExt1RefToBinaryDataC0..1This 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
n2SmInfoTypeExt1N2SmInfoTypeC0..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
smContextRefUriC0..1This 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).
(NOTE 6)		DTSSA
smContextSmfPlmnIdPlmnIdNidC0..1This IE shall be present during an inter-PLMN mobility procedure if the smContextRef IE is present. It may be present otherwise, if the smContextRef IE is present.
When present, this IE shall carry the PLMN ID of the SMF which hosts the SM Context resource identified by smContextRef IE. For an SNPN, the NID together with the PLMN ID shall identify the SNPN.
(NOTE 7)		DTSSA
smContextSmfIdNfInstanceIdO0..1This 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
smContextSmfSetIdNfSetIdC0..1This 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
smContextSmfServiceSetIdNfServiceSetIdC0..1This 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
smContextSmfBindingSbiBindingLevelC0..1This IE shall be present, if available.
When present, this IE shall contain the SBI binding level of the SM context resource.		DTSSA
upCnxStateUpCnxStateC0..1This 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
smallDataRateStatusSmallDataRateStatusC0..1This IE shall be present if the small data rate control status is available in AMF, see clause 5.31.14.3 of TS 23.501 and clause 4.3.2.2.1 of TS 23.502.CIOT
apnRateStatusApnRateStatusC0..1This IE shall be present if the APN rate control status is available in AMF, see clause 4.7.7.3 in TS 23.401 and clause 5.2.8.2.5 in TS 23.502.CIOT
extendedNasSmTimerIndbooleanC0..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 TS 24.501, as follows:
  • True: extended NAS SM timers shall be used
  • False (default): normal NAS SM timers shall be used.
CIOT
dlDataWaitingIndbooleanC0..1This 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 TS 23.502), 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
ddnFailureSubsDdnFailureSubsC0..1This 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 TS 23.502.CIOT
smfTransferIndbooleanC0..1This 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
oldSmfIdNfInstanceIdC0..1This IE shall be present if smfTransferInd is set to true.
When present, it shall indicate old SMF instance identifier.		CTXTR
oldSmContextRefUriC0..1This 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.
This IE shall also be present, without smfTransferInd set, if this information was received earlier in Notify SM Context Status, see clause 4.3.5.2 of TS 23.502.		CTXTR EnEDGE
wAgfInfoWAgfInfoC0..1This 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.
tngfInfotngfInfoC0..1This 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.
twifInfotwifInfoC0..1This 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.
ranUnchangedIndbooleanC0..1This IE shall be present if the NG-RAN is not changed in case of I-SMF/V-SMF change or insertion during CM-CONNECTED registration procedure after EPS to 5GS handover (see clause 5.2.2.2.7) or I-SMF/V-SMF selection per DNAI (see clause 5.2.2.2.12).
When present, it shall be set as follows:
  • true: NG-RAN is not changed;
  • false: NG-RAN is changed.
DTSSA
samePcfSelectionIndbooleanC0..1This IE shall be present, if the AMF received the PCF Selection Assistance info from the UDM indicating that the same PCF is required. (NOTE 4)
When present, it shall be set as follows:
  • True: the SMF is indicated to select the same PCF instance for the PDU session.
  • False (default): the SMF is not indicated to select the same PCF instance for the PDU session.
targetDnaiDnaiC0..1 This IE shall be present, if this information was received earlier in Notify SM Context Status. I-SMF or SMF shall use this information for I-UPF / L-PSA / PSA selection, see clauses 4.3.5.1, 4.3.5.2 or 4.23.5.4 of TS 23.502. V-SMF shall use this information for V-UPF selection, see clause 6.7.3.2 of TS 23.548.EnEDGE
HR-SBO
nrfManagementUriUriC0..1If included, this IE shall contain the API URI of the NFManagement Service (see clause 6.1.1 of TS 29.510) of the NRF or hNRF.
It shall be present during the PDU session establishment procedure with an I-SMF/V-SMF or mobility procedure with I-SMF/V-SMF insertion/change, if it is returned from the NSSF or hNSSF (see clause 6.1.6.2.7 of TS 29.531).
nrfDiscoveryUriUriC0..1If included, this IE shall contain the API URI of the NFDiscovery Service (see clause 6.2.1 of TS 29.510) of the NRF or hNRF.
It shall be present during the PDU session establishment procedure with an I-SMF/V-SMF or mobility procedure with I-SMF/V-SMF insertion/change, if it is returned from the NSSF or hNSSF (see clause 6.1.6.2.7 of TS 29.531).
nrfAccessTokenUriUriC0..1If included, this IE shall contain the API URI of the Access Token Service (see clause 6.3.2 of TS 29.510) of the NRF or hNRF.
It shall be present during the PDU session establishment procedure with an I-SMF/V-SMF or mobility procedure with I-SMF/V-SMF insertion/change, if it is returned from the NSSF or hNSSF (see clause 6.1.6.2.7 of TS 29.531).
nrfOauth2Requiredmap(boolean)C1..NThis IE should be present if the nrfUri IE, nrfManagementUri IE or nrfDiscoveryUri IE is present and if the information is available.
When present, this IE shall indicate whether the NRF requires Oauth2-based authorization for accessing its services. The key of the map shall be the name of an NRF service, e.g. "nnrf-nfm" or "nnrf-disc".
The value of each entry of the map shall be encoded as follows:
  • true: OAuth2 based authorization is required.
  • false: OAuth2 based authorization is not required.
The absence of this IE means that no indication is available about the usage of Oauth2 for authorization of NRF services.
smfBindingInfostringC0..1This IE shall be present, if available.
When present, this IE shall contain the Binding indications of the SM context resource and shall be set to the value of the 3gpp-Sbi-Binding header defined in clause 5.2.3.2.6 of TS 29.500, without the header name.		DTSSA
pvsInfoarray(ServerAddressingInfo)C1..NThis IE shall be present, if the AMF received this information from AUSF during User Plane Remote Provisioning of UEs procedure (see clause 5.30.2.10.4 of TS 23.501).
When present, this IE shall contain the remote Provisioning Server(s) information.		ENPN
onboardingIndbooleanC0..1This IE shall be present, if the UE is registered for onboarding in an SNPN (see clause 5.30.2.10.4 in TS 23.501 and clause 4.2.2.2.4 in TS 23.502).
  • false (default): The UE is not registered in an SNPN for the purpose of onboarding;
  • true: The UE has registered in the SNPN for the purpose of onboarding.
ENPN
oldPduSessionRefUriC0..1This IE shall be present if this information was received earlier in Notify SM Context Status, see clause 4.3.5.2 of TS 23.502.
When present, this IE shall contain the URI of the PDU session resource in the old SMF. The URI shall be an absolute URI, including apiRoot (see clause 6.1.3.6.2).		EnEDGE
smPolicyNotifyIndbooleanO0..1When present, this IE shall indicate whether the SM Policy Association Establishment and Termination events shall be reported for the PDU session by the PCF for the SM Policy to the PCF for the UE:
  • true: SM Policy Association Establishment and Termination events shall be reported
  • false (default): SM Policy Association Establishment and Termination events is not required (NOTE 5)
SPAE
pcfUeCallbackInfoPcfUeCallbackInfoC0..1This IE shall be present when the smPolicyNotifyInd IE is present with value true.
When present, this IE shall contain the callback information of the PCF for the UE to receive SM Policy Association Establishment and Termination events notification from the PCF for the SM Policy. (NOTE 5)		SPAE
satelliteBackhaulCatSatelliteBackhaulCategoryO0..1This IE may be present if the AMF supports the 5GSAT feature and the AMF is aware that there is a satellite backhaul towards the 5G AN serving the UE.
When present, this IE shall indicate the category of the satellite backhaul used towards the 5G AN serving the UE.		5GSAT
upipSupportedbooleanC0..1This IE shall be present during the PDU session establishment procedure, if the UE supports User Plane Integrity Protection with EPS and if the AMF supports the related functionality. It may be present otherwise. When present, this IE shall be set as follows:
  • true: User Plane Integrity Protection with EPS is supported;
  • false (default): User Plane Integrity Protection with EPS is not supported.
UPIPE
disasterRoamingIndbooleanO0..1This IE may be set when the UE is registered for Disaster Roaming service. When present, this IE shall be set as follows:
  • true: the UE is registered for Disaster Roaming service
  • false (default): the UE is not registered for Disaster Roaming service
anchorSmfOauth2RequiredbooleanO0..1When present, this IE shall indicate whether the H-SMF or SMF for a PDU session with an I-SMF requires Oauth2-based authorization for accessing its Nsmf_PDUSession service.
  • true: OAuth2 based authorization is required.
  • false: OAuth2 based authorization is not required.
The absence of this IE means that no indication is available about the usage of Oauth2 for authorization of the anchor SMF's Nsmf_PDUSession service.
(NOTE 2)
smContextSmfOauth2RequiredbooleanO0..1This IE may be present during an I-SMF insertion, change or removal. This IE may be present when V-SMF changes within the same PLMN.
When present, this IE shall indicate whether the SMF hosting the SM Context requires Oauth2-based authorization for accessing its Nsmf_PDUSession service.
  • true: OAuth2 based authorization is required.
  • false: OAuth2 based authorization is not required.
The absence of this IE means that no indication is available about the usage of Oauth2 for authorization of the Nsmf_PDUSession service on the SMF hosting the SM Context.
(NOTE 2)
geoSatelliteIdGeoSatelliteIdO0..1The AMF may include this IE during a PDU Session Establishment procedure (see clause 4.3.2.2.1 of TS 23.502).
When present, this IE shall contain a GEO satellite ID.		5GSATB
hrsboAllowedIndbooleanO0..1This IE may be present in HR roaming scenarios.
When present, this IE shall Indicate whether Session Breakout for HR Session in VPLMN is allowed:
  • true: Allowed.
  • false (default): Not allowed.
HR-SBO
estabRejectionIndbooleanO0..1This IE may be present with the value true if the AMF has determined that the PDU Session Establishment shall be rejected, e.g. according to the ODB configuration of the UE retrieved from the UDM.
Presence of this IE with the value false shall be prohibited. 		PSER
estabvRejectionCauseEstablishmentRejectionCauseC0..1This IE shall be included if the estabRejectionInd is present with the value true.
When present, this IE shall indicate the cause of the PDU session establishment rejection. 		PSER
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. when the anchorSmfOauth2Required IE and/or the smContextSmfOauth2Required IE are received with the value true or when 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:
If present, this attribute shall be used together with routingIndicator. This attribute is only used by the HPLMN in roaming scenarios.
NOTE 4:
If present, this attribute shall be used together with the PCF ID received from the AMF for selecting the same PCF instance for the PDU session.
NOTE 5:
If the AMF has received the callback information of the PCF for the UE together with the information of the PDU sessions (i.e. Slice and DNN combination) that are applicable for notification of SM Policy Association events, the AMF shall identify whether the non-roaming or local breakout PDU session to be created is applicable for SM Policy Association events, i.e, whether the slice and DNN combination of the PDU session is listed in the received PDU session information from the PCF for the UE. If the PDU session is applicable for notification of SM Policy Association events, the AMF shall include the smPolicyNotifyInd IE with the value "true" and the callback information of the PCF for the UE in the request. The SMF shall forward the callback information of the PCF for the UE to the PCF for SM Policy during SM Policy Association Establishment. See clause 4.3.2.2.1 of TS 23.502.
NOTE 6:
See NOTE 2 of Table 6.1.6.2.3-1.
NOTE 7:
If the PLMN ID of the SMF holding the SM context received in smContextSmfPlmnId attribute is different from the PLMN ID of the target V-SMF/I-SMF/anchor SMF, the target V-SMF/I-SMF/anchor SMF shall retrieve the SM Context from the SMF via the SEPP. In this case, the smContextSmfPlmnId attribute may also be used for the discovery and selection of the local SEPP.
NOTE 8:
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.
Up
6.1.6.2.3  Type: SmContextCreatedData  p. 152
Attribute name Data type P Cardi­nality Description Applica­bility
hsmfUriUriC0..1This 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.
smfUriUriC0..1This 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
pduSessionIdPduSessionIdC0..1This 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.
sNssaiSnssaiC0..1This 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.
additionalSnssaiSnssaiC0..1This IE shall be present during an EPS to 5GS Idle mode mobility or handover using the N26 interface for LBO roaming case.
When present, this IE shall indicate the associated S-NSSAI in HPLMN for the PDU Session.
upCnxStateUpCnxStateC0..1This 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.
n2SmInfoRefToBinaryDataC0..1This IE shall be present if N2 SM Information needs to be sent to the AN.
n2SmInfoTypeN2SmInfoTypeC0..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.
allocatedEbiListarray(EbiArpMapping)C1..NThis 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.
hoStateHoStateC0..1This 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.
gpsiGpsiC0..1This 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.
smfServiceInstanceIdstringO0..1When 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 TS 23.527).
recoveryTimeDateTimeO0..1Timestamp (in UTC) when the SMF service instance serving the PDU session was (re)started (see clause 6.3 of TS 23.527).
supportedFeaturesSupportedFeaturesC0..1This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported.
selectedSmfIdNfInstanceIdC0..1This 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 1)
When present, it shall contain the selected SMF NF Instance Id. 		DTSSA
selectedOldSmfIdNfInstanceIdC0..1This 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 1)
When present, it shall contain the selected old I/V-SMF NF Instance Id. 		DTSSA
interPlmnApiRootUriC0..1This IE should be present if the PDU session may be subject to inter-PLMN mobility and different SM context URIs shall be used for intra-PLMN and inter-PLMN signaling requests targeting the SM context.
When present, it shall contain the apiRoot of the SM context to be used in inter-PLMN signalling request targeting the SM context.
(NOTE 2)
udmGroupIdNfGroupIdO0..1This IE may be present during an EPS to 5GS handover using the N26 interface procedure. When present, it shall indicate the identity of the UDM group serving the UE.
pcfGroupIdNfGroupIdO0..1This IE may be present during an EPS to 5GS handover using the N26 interface procedure.
When present, this IE shall contain the identity of the (home) PCF group serving the PDU session for Session Management policy.
NOTE 1:
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.
NOTE 2:
The SM Context URI returned in the Location header in the Create SM Context response shall contain an URI suitable for use in intra-PLMN signaling requests targeting the SM Context. During an inter-PLMN mobility, the target AMF shall replace the apiRoot of the smContextRef with the interPlmnApiRoot if available and send the resulting smContextRef in the Create SM Context request towards the target V-SMF, I-SMF or anchor SMF.
Up
6.1.6.2.4  Type: SmContextUpdateData  p. 155
Attribute name Data type P Cardi­nality Description Applica­bility
peiPeiC0..1This 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.
servingNfIdNfInstanceIdC0..1This 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).
smContextStatusUriUriC0..1This 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.
guamiGuamiC0..1This IE shall be present if the servingNfId of AMF is present.
When present, it shall contain the serving AMF's GUAMI.
servingNetworkPlmnIdNidC0..1This 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.
backupAmfInfoarray(BackupAmfInfo)C1..NThis 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.
anTypeAccessTypeC0..1This 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.
additionalAnTypeAccessTypeC0..1This 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
anTypeToReactivateAccessTypeC0..1This IE shall indicate the Access Network Type for which the UP connection is requested to be re-activated, for a MA PDU session.MAPDU
ratTypeRatTypeC0..1This IE shall be present and indicate the RAT Type used by the UE, if available, upon a change of RAT Type.
presenceInLadnPresenceStateC0..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.
ueLocationUserLocationC0..1This 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)
ueTimeZoneTimeZoneC0..1This 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.
addUeLocationUserLocationO0..1Additional 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)
upCnxStateUpCnxStateC0..1This 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.
hoStateHoStateC0..1This 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.
toBeSwitchedbooleanC0..1This 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.
failedToBeSwitchedbooleanC0..1This 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.
n1SmMsgRefToBinaryDataC0..1This 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).
n2SmInfoRefToBinaryDataC0..1This 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).
n2SmInfoTypeN2SmInfoTypeC0..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.
targetIdNgRanTargetIdC0..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.
targetServingNfIdNfInstanceIdC0..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).
dataForwardingbooleanC0..1This 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, or as specified in clause 5.2.2.3.21 during N9 Forwarding Tunnel establishment between Branching Points or UL CLs controlled by different I-SMFs.
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.
n9ForwardingTunnelTunnelInfoC0..1This 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 TS 23.502). When present, it shall carry the N9 forwarding tunnel info of I-UPF.
DTSSA
n9DlForwardingTnlListarray (IndirectDataForwardingTunnelInfo)C1..NThis 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 TS 23.502).
When present, it shall carry the list of N9 downlink indirect data forwarding tunnel(s) info of I-UPF.		DTSSA
n9UlForwardingTnlListarray (IndirectDataForwardingTunnelInfo)C1..NThis 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 TS 23.502).
When present, it shall carry the list of N9 uplink indirect data forwarding tunnel(s) info of I-UPF.		DTSSA
n9DlForwardingTunnelTunnelInfoC0..1This IE shall be present in the following case:
  • simultaneous change of Branching Points or UL CLs controlled by different I-SMFs, if downlink data forwarding tunnel is requested to be established from source BP / UL CL to target BP / UL CL (see clause 4.23.9.5 of TS 23.502).
When present, it shall carry the N9 downlink data forwarding tunnel info of the target BP / UL CL.		N9FSC
n9InactivityTimerDurationSecO0..1When present, this IE shall indicate an inactivity detection timer, in seconds, that the I-SMF may use to set the N9 forwarding tunnel inactive traffic detection timer in Branching Point or UL CL as specified in clause 4.23.9.5 of TS 23.502.N9FSC
epsBearerSetuparray(EpsBearerContainer)C0..NThis 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.
revokeEbiListarray (EpsBearerId)C1..NThis IE shall be present to request the SMF to revoke some EBIs (see clause 4.11.1.4.1 of TS 23.502). When present, it shall contain the EBIs to revoke.
releasebooleanC0..1This 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, in clause 5.2.2.3.17 during AMF requested PDU Session Release due to Network Slice-Specific Authentication and Authorization failure or revocation, in clause 5.2.2.3.19 during AMF requested PDU Session Release due to Control Plane Only indication associated with PDU Session is not applicable any longer, in clause 5.2.2.3.20 during AMF requested PDU Session Release due to ODB changes, and in clause 5.2.2.3.27 during AMF requested PDU Session Release due to MBSR not authorized.
When present, it shall be set as follows:
  • true: PDU session release is required;
  • false (default): PDU session release is not required.
causeCauseO0..1When 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.
ngApCauseNgApCauseC0..1This 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.
5gMmCauseValue5GMmCauseC0..1This 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).
sNssaiSnssaiC0..1This 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.
traceDataTraceDataC0..1This IE shall be included if trace is required to be activated, modified or deactivated (see TS 32.422).
For trace modification, it shall contain a complete replacement of trace data.
For trace deactivation, it shall contain the Null value.
epsInterworkingIndEpsInterworkingIndicationO0..1This IE may be present if 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.
anTypeCanBeChangedbooleanC0..1This 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 TS 23.502)), 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 TS 23.502.
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.
n2SmInfoExt1RefToBinaryDataC0..1This 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).
n2SmInfoTypeExt1N2SmInfoTypeC0..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.
maReleaseIndMaReleaseIndicationC0..1This 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
maNwUpgradeIndbooleanC0..1This IE shall be present if the PDU session is allowed to be upgraded to MA PDU session (see clause 6.4.2.2 of TS 24.501).
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
maRequestIndbooleanC0..1This IE shall be present if a MA-PDU session is requested to be established (see clause 4.22.6.3 of TS 23.502).
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
n3gPathSwitchmExecutionIndbooleanO0..1 This IE may be present and set to true if the AMF receives the indication "Non-3GPP access path switching while using old AN resources" in the registration request message from the UE and if the SMF supports non-3GPP path switching, so to request the SMF to add a new non-3GPP access path (while also keeping the existing one) during a UE requested non-3GPP access switching for a MA-PDU session. N3GPS
exemptionIndExemptionIndC0..1This IE shall be present if the AMF has exempted the NAS message from a NAS SM congestion control activated in the AMF.
supportedFeaturesSupportedFeaturesC0..1This 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.
moExpDataCounterMoExpDataCounterC0..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
extendedNasSmTimerIndbooleanC0..1This 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 TS 24.501, as follows:
  • True: extended NAS SM timers shall be used
  • False: normal NAS SM timers shall be used.
CIOT
forwardingFTeidBytesC0..1This 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 TS 23.502), 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 TS 29.274 (starting from octet 1).		CIOT
forwardingBearerContextsarray(ForwardingBearerContainer)C1..NThis 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 TS 23.502), 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
ddnFailureSubsDdnFailureSubsC0..1This 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 TS 23.502.
This IE shall also be present if it is required to add, modify or remove DDN failure subscriptions. If it is present and the included dnnFailureSubsInd indicates notification of DDN failure is subscribed, the content of the received ddnFailureSubs shall overwrite any ddnFailureSubs received earlier.		CIOT
skipN2PduSessionResRelIndbooleanO0..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.
secondaryRatUsageDataReportContainerarray(SecondaryRatUsageDataReportContainer)C1..NThe IE shall be present during an EPS to 5GS handover procedure, if one or more instance of Secondary RAT Usage Data Report IE(s) are present and applicable to the PDU session.
When present, it shall contain Base64-encoded characters, encoding the Secondary RAT Usage Data Report in the Forward Relocation Complete Acknowledge message, as specified in Figure 8.132-1 of TS 29.274 (starting from octet 1).
smPolicyNotifyIndbooleanO0..1When present, this IE shall indicate that the SM Policy Association Establishment and Termination events shall be reported for the PDU session by the PCF for the SM Policy to the PCF for the UE:
  • true: SM Policy Association Establishment and Termination events shall be reported
(NOTE 3) 		SPAE
pcfUeCallbackInfoPcfUeCallbackInfoC0..1This IE shall be present when the smPolicyNotifyInd IE is present with value true.
When present, this IE shall contain the callback information of the PCF for the UE to receive SM Policy Association Establishment and Termination events notification from the PCF for the SM Policy. (NOTE 3)		SPAE
satelliteBackhaulCatSatelliteBackhaulCategoryO0..1This IE may be present if the AMF and the SMF supports the 5GSAT feature and the AMF is aware that:
  • there is a change of the satellite backhaul category; or
  • the UE is newly served by a 5G-AN without any satellite backhaul and a satellite backhaul category had been signalled to the SMF; or
  • the UE is newly served by a 5G-AN with a satellite backhaul and no satellite backhaul category had been signalled to the SMF; or
  • there is a satellite backhaul towards the 5G AN serving the UE, but it does not know whether a satellite backhaul category had been signalled to the SMF (e.g. upon Inter-AMF mobility).
When present, this IE shall indicate the category of the satellite backhaul used towards the new 5G AN serving the UE, or that there is no longer any satellite backhaul towards the new 5G AN serving the UE. 		5GSAT
cnBasedMtbooleanO0..1 When present, this IE shall indicate to the SMF that UE is in RRC_INACTIVE mode with eDRX and CN Based MT handling is applied for the PDU session, i.e. the user plane connection is suspended and the UPF is requested to buffer subsequent DL Data and send a report upon subsequent DL data arrival, the SMF will then invoke the AMF EnableUEReachability service, see also clauses 4.8.1.1a and 4.8.2.2b of TS 23.502.
  • true: CN Based MT handling is to be applied.
geoSatelliteIdGeoSatelliteIdC0..1The AMF shall include this attribute when the Geo satellite ID changes.
When present, this IE shall contain a GEO satellite ID.		5GSATB
altSnssaiSnssaiC0..1This IE shall be present when the PDU Session is to be transferred to an alternative S-NSSAI.
When present, this IE shall indicate the alternative network slice to be used by the PDU session.
See clause 5.15.19 of TS 23.501.		NSRP
altHplmnSnssaiSnssaiC0..1This IE shall be present for HR PDU session when the PDU Session is to be transferred to an alternative S-NSSAI in HPLMN.
When present, this IE shall indicate the alternative network slice to be used by the PDU session in the HPLMN.
See clause 5.15.19 of TS 23.501.		NSRP
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.
NOTE 3:
If the AMF has received the callback information of the PCF for the UE together with the information of the PDU sessions (i.e. Slice and DNN combination) that are applicable for notification of SM Policy Association events, the AMF shall identify whether any ongoing non-roaming or local breakout PDU session is applicable for SM Policy Association events, i.e, whether the slice and DNN combination of the PDU session is listed in the received PDU session information from the PCF for the UE. If the PDU session is applicable for notification of SM Policy Association events , the AMF shall invoke Update SM context service operation for the PDU session and include the smPolicyNotifyInd IE with the value "true" and the callback information of the PCF for the UE in the request. The SMF shall forward the callback information of the PCF for the UE to the PCF for SM Policy if exists via SM Policy Association Modification. See clause 4.3.3.2 of TS 23.502. The AMF needs not update the SMF if the subscription to the SM Policy Association events for the PDU session is cancelled by the PCF for UE.
Up

Up   Top   ToC