Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 29.502  Word version:  18.6.0

Top   Top   Up   Prev   Next

 

6.1.6.2.5  Type: SmContextUpdatedDatap. 165
Attribute name Data type P Cardi­nality Description Applica­bility
upCnxStateUpCnxStateC0..1This 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.
hoStateHoStateC0..1This 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.
releaseEbiListarray(EpsBearerId)C1..NThis IE shall be present if the SMF determines that some EBIs are not needed. When present, it shall contain the EBIs to be released.
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.
modifiedEbiListarray(EbiArpMapping)C1..NThis 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.
n1SmMsgRefToBinaryDataC0..1This 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).
n2SmInfoRefToBinaryDataC0..1This 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).
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.
epsBearerSetuparray(EpsBearerContainer)C1..NThis 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.
dataForwardingbooleanC0..1This 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 or 5.2.2.3.21.
n3DlForwardingTnlListarray (IndirectDataForwardingTunnelInfo)C1..NThis 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
n3UlForwardingTnlListarray (IndirectDataForwardingTunnelInfo)C1..NThis 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
n9UlForwardingTunnelTunnelInfoC0..1This IE shall be present in the following case:
  • simultaneous change of Branching Points or UL CLs controlled by different I-SMFs, if uplink data forwarding tunnel is requested to be established from target BP / UL CL to source BP / UL CL (see clause 4.23.9.5 of TS 23.502).
When present, it shall carry the N9 uplink data forwarding tunnel info of the source BP / UL CL.
N9FSC
causeCauseC0..1This 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).
maAcceptedIndbooleanC0..1This 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 TS 23.502).
When present, it shall be set as follows:
  • true: MA PDU session
  • false (default): single access PDU session
MAPDU
supportedFeaturesSupportedFeaturesC0..1This 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.
forwardingFTeidBytesC0..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 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 TS 29.274 (starting from octet 1).
CIOT
forwardingBearerContextsarray(ForwardingBearerContainer)C1..NThis 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 TS 23.502), 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
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)
When present, it shall contain the selected SMF NF Instance Id.
DTSSA
selectedOldSmfIdNfInstanceIdC0..1This 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
interPlmnApiRootUriC0..1This IE should be present if the information has changed. When present, it shall contain the apiRoot of the SM context to be used in inter-PLMN signalling request targeting the SM context.
anchorSmfFeaturesAnchorSmfFeaturesO0..1This 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.
Up
6.1.6.2.6  Type: SmContextReleaseDatap. 168
Attribute name Data type P Cardi­nality Description Applica­bility
causeCauseC0..1This 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.
ngApCauseNgApCauseC0..1This IE shall be present, if the information is available. When present, this IE shall indicate the NGAP cause for the requested SM context release.
5gMmCauseValue5GMmCauseC0..1This 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.
ueLocationUserLocationC0..1This IE shall be present, if available.
When present, it shall contain the UE location information (see clause 5.2.3.4). See NOTE.
ueTimeZoneTimeZoneC0..1This IE shall be present, if available.
When present, it shall contain the UE Time Zone information.
addUeLocationUserLocationO0..1Additional 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.
vsmfReleaseOnlybooleanC0..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.
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.
ismfReleaseOnlybooleanC0..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.
Up
6.1.6.2.7  Type: SmContextRetrieveDatap. 171
Attribute name Data type P Cardi­nality Description Applica­bility
targetMmeCapMmeCapabilitiesC0..1This IE shall be present if it is available. When present, it shall contain the target MME capabilities.
smContextTypeSmContextTypeC0..1This 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 TS 23.502).
This IE shall also be present if this is a request to retrieve the AF Coordination Information during the change of SSC mode 3 PDU Session Anchor with multiple PDU Sessions, if the runtime coordination between old SMF and AF is enabled (see clause 4.3.5.2 of TS 23.502).
DTSSA, CTXTR EnEDGE
servingNetworkPlmnIdC0..1This 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 or insertion.
This IE shall also be present during the procedure with an I-SMF insertion.
When present, this IE shall contain the serving core network operator PLMN ID of the NF Service Consumer (i.e. new V-SMF or new I-SMF).
DTSSA
notToTransferEbiListarray(EpsBearerId)C1..NThis 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 TS 23.502. When present, it shall contain the EBI list not to be transferred.
ranUnchangedIndbooleanC0..1This 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 or I-SMF selection per DNAI, 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
hrsboSupportIndbooleanC0..1This IE shall be present if the procedure is triggered by a new V-SMF which supports the HR-SBO feature.
When present, it shall be set as follows:
  • true: HR-SBO is supported;
  • false (default): HR-SBO is not supported.
storedOffloadIdsarray(OffloadIdentifier)C1...NThe IE shall be present when the target V-SMF has a list of the stored offload identifiers for the HPLMN of the PDU session from previous procedures (for the same or different PDU sessions) with the HPLMN.
When present, this IE shall contain the list of offload identifiers known by the target V-SMF for the HPLMN of the PDU session. (NOTE)
HR-SBO
NOTE:
The stored VPLMN Offload identifiers shall be included in any subsequent request message to the source V-SMF for other HR-PDU sessions.
Up
6.1.6.2.8  Type: SmContextStatusNotificationp. 174
Attribute name Data type P Cardi­nality Description Applica­bility
statusInfoStatusInfoM1This IE shall contain status information about the SM context.
smallDataRateStatusSmallDataRateStatusC0..1This 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
apnRateStatusApnRateStatusC0..1This 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
ddnFailureStatusbooleanC0..1This IE shall be present if the DDN Failure shall be reported (see clause 5.2.8.2.8 of TS 23.502).
When present, it shall be set as follows:
  • true: DDN failure detected
  • false (default): DDN failure is not detected
CIOT
notifyCorrelationIdsForddnFailurearray(string)C1..NThis 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
newIntermediateSmfIdNfInstanceIdC0..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
newSmfIdNfInstanceIdC0..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
newSmfSetIdNfSetIdC0..1This 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
oldSmfIdNfInstanceIdC0..1This 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
oldSmContextRefUriC0..1This 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.
This IE may also be present if resourceStatus in statusInfo is "UNCHANGED", the SMF selection during PDU Session re-establishment for SSC mode 3 is needed and the runtime coordination between old SMF and AF is enabled. When present, this IE shall contain the URI of the SM Context resource in the old SMF with the structure: {apiRoot}/nsmf-pdusession/v1/sm-contexts/{smContextRef}.
CTXTR EnEDGE
altAnchorSmfUriUriC0..1This 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
altAnchorSmfIdNfInstanceIdC0..1This 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
targetDnaiInfoTargetDnaiInfoC0..1This IE shall be present if the I-SMF selection or removal for the current PDU session, or SMF selection during PDU Session re-establishment for SSC mode 2/3 is needed, or if it is received from the SMF in Notify Status. When present, this IE shall include the target DNAI Information.EnEDGE
oldPduSessionRefUriC0..1 This IE shall be present if resourceStatus in statusInfo is "UNCHANGED", the SMF selection during PDU Session re-establishment for SSC mode 3 is needed and the runtime coordination between old SMF and AF is enabled.
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
interPlmnApiRootUriC0..1 This IE should be present if the information has changed and, within the statusInfo IE, the resourceStatus IE is set to "UPDATED" and the cause IE set to "CHANGED_INTERMEDIATE_SMF".
When present, it shall contain the apiRoot of the SM context to be used in inter-PLMN signalling request targeting the SM context.
targetDnaiDnaiC0..1This IE shall be present if it is received from H-SMF in Update Request (see clause 6.7.3.2 of TS 23.548).
When present, this IE shall include the target DNAI.
HR-SBO
NOTE:
If resourceStatus in statusInfo is "TRANSFERRED", at least one of newSmfId and newSmfSetId shall be included.
Up
6.1.6.2.9  Type: PduSessionCreateDatap. 178
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.
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.
pduSessionIdPduSessionIdC0..1This IE shall contain the PDU Session ID, except during an EPS to 5GS Idle mode mobility or handover using the N26 interface.
dnnDnnM1This 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.
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, except during an EPS to 5GS idle mode mobility or handover using the N26 interface.
When present, it shall contain:
  • the HPLMN S-NSSAI for a HR PDU session, which is mapped from the requested S-NSSAI by the VPLMN; or
  • the requested S-NSSAI in the serving PLMN for a PDU session with an I-SMF.
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 an LBO PDU session with an I-SMF, except during an EPS to 5GS idle mode mobility or handover using the N26 interface.
When present, it shall contain the HPLMN S-NSSAI of the LBO PDU session, which is mapped from the requested S-NSSAI by the VPLMN.
DTSSA
vsmfIdNfInstanceIdC0..1This IE shall be present for a HR PDU session. When present, it shall contain the identifier of the V-SMF.
ismfIdNfInstanceIdC0..1This IE shall be present for a PDU session with an I-SMF. When present, it shall contain the identifier of the I-SMF.DTSSA
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 AMF, this IE shall be set based on the requestType received.
epsBearerIdarray(EpsBearerId)C1..NThis 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.
pgwS8cFteidBytesC0..1This 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 TS 29.274 (starting from octet 1), received from the MME.
vsmfPduSessionUriUriC0..1This 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.
ismfPduSessionUriUriC0..1This 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
vcnTunnelInfoTunnelInfoC0..1 This IE shall be present for a HR PDU session, except for:
  • an 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 DL N9 tunnel CN information of the visited CN side, i.e. V-UPF.
icnTunnelInfoTunnelInfoC0..1 This IE shall be present for a PDU session involving an I-SMF, except for:
  • an EPS to 5GS handover using N26 interface with I-SMF insertion; 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 DL N9 tunnel CN information of the I-UPF controlled by the I-SMF.
DTSSA
n9ForwardingTunnelInfoTunnelInfoC0..1This 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 TS 23.502).
When present, this IE shall contain the N9 tunnel information of the I-UPF controlled by the I-SMF.
DTSSA
additionalCnTunnelInfoTunnelInfoC0..1This 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 DL N9 tunnel CN information of the UPF controlled by the V-SMF or I-SMF.
MAPDU
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.
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 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)
gpsiGpsiC0..1This IE shall be present if it is available. When present, it shall contain the user's GPSI.
n1SmInfoFromUeRefToBinaryDataC0..1This 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).
unknownN1SmInfoRefToBinaryDataC0..1This 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).
supportedFeaturesSupportedFeaturesC0..1This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported.
hPcfIdNfInstanceIdO0..1This 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).
pcfIdNfInstanceIdO0..1This 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
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..1When 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.
hoPreparationIndicationbooleanC0..1This 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.
selModeDnnSelectionModeC0..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.
alwaysOnRequestedbooleanC0..1This 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
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 2)
epsInterworkingIndEpsInterworkingIndicationO0..1This 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 or EPC/ePDG and whether N26 interface to be used during EPS interworking procedures.
vSmfServiceInstanceIdstringO0..1When 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 TS 23.527).
iSmfServiceInstanceIdstringO0..1When 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 TS 23.527).
DTSSA
recoveryTimeDateTimeO0..1Timestamp (in UTC) when the V-SMF or I-SMF service instance serving the PDU session was (re)started (see clause 6.3 of TS 23.527).
roamingChargingProfileRoamingChargingProfileO0..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 TS 32.255).
chargingIdstringO0..1 Charging ID (see clauses 5.1.9.1 of TS 32.255).
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 4)
smfChargingIdSmfChargingIdC0..1String based Charging ID (see TS 32.255).
This IE shall be present when the chargingId IE is present and the "SCID" feature is supported by both SMFs.
When present, this IE shall encode the String based Charging ID of the PDU session and the base Charging ID segment shall be idential to the value carried in the chargingId IE.
SCID
oldPduSessionIdPduSessionIdC0..1This 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 TS 23.502.
epsBearerCtxStatusEpsBearerContextStatusC0..1This 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.
amfNfIdNfInstanceIdC0..1This 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.
guamiGuamiC0..1This IE shall be present if the amfNfId is present.
When present, it shall contain the serving AMF's GUAMI.
maxIntegrityProtectedDataRateUlMaxIntegrityProtectedDataRateC0..1This 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.
maxIntegrityProtectedDataRateDlMaxIntegrityProtectedDataRateC0..1This 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.
cpCiotEnabledbooleanC0..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 clause 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 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
maRequestIndbooleanC0..1This 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
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
dnaiListarray(Dnai)C1..NThis 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 TS 23.502).
When present, it shall include the list of DNAIs supported by the I-SMF.
DTSSA
presenceInLadnPresenceStateC0..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
secondaryRatUsageInfoarray(SecondaryRatUsageInfo)O1..NThis IE may be present to report usage data for a secondary RAT for QoS flows and/or the whole PDU session.DTSSA
smallDataRateStatusSmallDataRateStatusC0..1This IE shall be present if the small data rate control status is received from AMF, see clause 5.31.14.3 of TS 23.501 and clause 4.3.2.2.2 of TS 23.502.CIOT
apnRateStatusApnRateStatusC0..1This 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 TS 23.401 and clause 4.11.5.3 in TS 23.502.CIOT
dlServingPlmnRateCtlintegerC0..1This 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 TS 23.501. Minimum: 10
CIOT
upSecurityInfoUpSecurityInfoC0..1This 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 TS 38.413.
DTSSA
vplmnQosVplmnQosC0..1This 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
oldSmContextRefUriC0..1This IE shall be present, if it is received in the Create SM Context request.
When present, this IE shall contain the identifier of the SM Context resource in the old SMF.
EnEDGE
redundantPduSessionInfoRedundantPduSessionInformationC0..1This IE shall be present for a PDU session with an I-SMF, if an RSN and/or PDU Session Pair ID was received from the UE.DCE2ER
oldPduSessionRefUriC0..1This IE shall be present, if it is received in the Create SM Context request.
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
smPolicyNotifyIndbooleanC0..1This IE shall be included by I-SMF to SMF, if received from AMF.
When 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 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 V-SMF/I-SMF supports the 5GSAT feature and the satelliteBackhaulCat IE has been received from the AMF.
When present, this IE shall indicate the value received from the AMF.
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
upCnxStateUpCnxStateC0..1This 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 TS 23.502).
When present, this IE shall be set as specified in clause 5.2.2.7.6.
disasterRoamingIndbooleanO0..1This IE may be set during the PDU session establishment or a V-SMF insertion procedure when the V-SMF is indicated by the AMF that 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
hrsboInfoHrsboInfoFromVplmnC0..1This IE shall be present in HR roaming scenarios if the V-SMF requests HR SBO authorization.
When present, this IE shall Include the information for HR-SBO.
HR-SBO
ecsAddrConfigInfosarray(EcsAddrConfigInfo)C1..NThis IE shall be included by V-SMF to SMF, if received from NEF.
When present, this IE shall contain the ECS Address Configuration Information Parameters. See TS 23.548.
HR-SBO
pduSetSupportIndbooleanC0..1This IE shall be included by I-SMF to SMF for a PDU session with an I-SMF if the NG-RAN has indicated it supports the PDU Set based handling during a Xn based inter NG-RAN handover with the I-SMF insertion.
When present, this IE shall indicate whether the PDU Set based handling is supported by the NG-RAN:
  • true: the PDU Set based handling is supported
  • false(default): the PDU Set based handling is not supported
ecnMarkingCongestionInfoStatusarray(EcnMarkingCongestionInfoStatus)C1..NThis IE shall be present when the V/I-SMF receives the ECN Marking or Congestion Monitoring Reporting Status during an I/V-SMF insertion procedure, e.g. for an Xn based handover.
When present, this IE shall contain a list of QoS flows with status for QoS monitoring for congestion information or for ECN marking for L4S.
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:
If present, this attribute shall be used together with routingIndicator. This attribute is only used by the HPLMN in roaming scenarios.
NOTE 3:
If the smPolicyNotifyInd IE is received with the value "true", 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 4:
Usage of Charging ID with Uint32 value for roaming scenarios may lead to Charging ID collision between SMFs.
Up
6.1.6.2.10  Type: PduSessionCreatedDatap. 188
Attribute name Data type P Cardi­nality Description Applica­bility
pduSessionTypePduSessionTypeM1This IE shall indicate the selected PDU type.
sscModestringM1This 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 TS 24.501.
Pattern: "^[0-7]$"
Example: SSC mode 3 shall be encoded as "3".
(NOTE 1).
hcnTunnelInfoTunnelInfoC0..1This 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 UL N9 tunnel CN information of the home CN side, i.e. H-UPF.
cnTunnelInfoTunnelInfoC0..1This 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 UL N9 tunnel CN information of the PSA UPF.
DTSSA
additionalCnTunnelInfoTunnelInfoC0..1This 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 UL N9 tunnel CN information of the UPF controlled by the H-SMF or SMF.
MAPDU
sessionAmbrAmbrC0..1This 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.
qosFlowsSetupListarray(QosFlowSetupItem)C1..NThis 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)
hSmfInstanceIdNfInstanceIdC0..1This IE shall be present for a HR PDU session. When present, it shall contain the identifier of the home SMF.
smfInstanceIdNfInstanceIdC0..1This IE shall be present for a PDU session with an I-SMF. When present, it shall contain the identifier of the SMF. DTSSA
pduSessionIdPduSessionIdC0..1This 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.
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 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.
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.
enablePauseChargingbooleanC0..1This 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 TS 23.502).
When present, it shall be set as follows:
  • true: enable Pause of Charging;
  • false (default): disable Pause of Charging.
ueIpv4AddressIpv4AddrC0..1This IE shall be present if the SMF assigns a UE IPv4 address to the PDU session.
ueIpv6PrefixIpv6PrefixC0..1This IE shall be present if the SMF assigns a UE IPv6 prefix to the PDU session.
n1SmInfoToUeRefToBinaryDataC0..1This 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).
epsPdnCnxInfoEpsPdnCnxInfoC0..1This IE shall be present if the PDU session may be moved to EPS during its lifetime.
epsBearerInfoarray(EpsBearerInfo)C1..NThis IE shall be present if the PDU session may be moved to EPS during its lifetime.
supportedFeaturesSupportedFeaturesC0..1This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported.
maxIntegrityProtectedDataRateMaxIntegrityProtectedDataRateC0..1This 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)
maxIntegrityProtectedDataRateDlMaxIntegrityProtectedDataRateC0..1This 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)
alwaysOnGrantedbooleanC0..1This 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.
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.
When present, it shall contain the user's GPSI associated with the PDU session.
upSecurityUpSecurityO0..1When 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)
roamingChargingProfileRoamingChargingProfileO0..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 TS 32.255).
hSmfServiceInstanceIdstringO0..1When 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 TS 23.527).
smfServiceInstanceIdstringO0..1When 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 TS 23.527).
DTSSA
recoveryTimeDateTimeO0..1Timestamp (in UTC) when the SMF service instance serving the PDU session was (re)started (see clause 6.3 of TS 23.527).
dnaiListarray(Dnai)C1..NThis 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 TS 23.502).
When present, it shall include the list of DNAIs of interest for the PDU session for local traffic steering at the I-SMF.
If the I-SMF and the SMF support the DTSSA-Ext1 feature, when present, this IE should include the full list of DNAIs of interest for PDU session, including DNAIs that may not be supported by the I-SMF and excluding the ones supported by the Anchor SMF.
DTSSA DTSSA-Ext1
ipv6MultiHomingIndbooleanC0..1This 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 TS 23.502).
When present, it shall be set as follows:
  • true: IPv6 multi-homing is permitted.
  • false (default): IPv6 multi-homing is not allowed.
DTSSA
maAcceptedIndbooleanC0..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 TS 23.502).
When present, it shall be set as follows:
  • true: MA PDU session
  • false (default): single access PDU session
MAPDU
homeProvidedChargingIdstringO0..1When present, this IE shall contain the Home provided Charging ID (see TS 32.255). 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 8)
homeProvidedSmfChargingIdSmfChargingIdC0..1When present, this IE shall contain the Home provided String based Charging ID (see TS 32.255).
This IE shall be present during an EPS to 5GS Idle mode mobility or Handover of a HR PDU session, if both the V-SMF and the H-SMF support the "SCID" feature.
(NOTE 9)
SCID
nefExtBufSupportIndbooleanC0..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
smallDataRateControlEnabledbooleanC0..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
ueIpv6InterfaceIdstringC0..1This 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}$"
ipv6IndexIpIndexC0..1This IE shall be present if IPv6 Index has been received from PCF during SM Policy Creation. (NOTE 4)DTSSA
dnAaaAddressIpAddressO0..1When 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
redundantPduSessionInfoRedundantPduSessionInformationC0..1This 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 TS 23.501, regardless of whether the redundantPduSessionInfo IE was received or not in the request. If an RSN and/or PDU Session Pair ID was received from the UE, the same RSN and/or PDU Session Pair ID shall be returned in the response; additionally, if either the RSN or PDU Session Pair ID was not received from the UE, the anchor SMF shall determine and also return an RSN or PDU Session Pair ID respectively in the response.DCE2ER
nspuSupportIndbooleanC0..1 This IE shall be present and set to "true" if enablePauseCharging is set to "true" and if the (H-)SMF and PSA UPF support Notify Start Pause of Charging via user plane feature as specified in clause 5.30 of TS 29.244.
When present, it shall be set as follows:
  • true: Notify Start Pause of Charging via user plane feature is supported.
interPlmnApiRootUriC0..1This IE should be present if the PDU session may be subject to inter-PLMN mobility and different PDU session context URIs shall be used for intra-PLMN and inter-PLMN signaling requests targeting the PDU session context.
When present, it shall contain the apiRoot of the PDU session context to be used in inter-PLMN signalling request targeting the PDU session context.
(NOTE 7)
intraPlmnApiRootUriC0..1This IE should be present if the PDU session may be subject to inter-PLMN mobility and different PDU session context URIs shall be used for intra-PLMN and inter-PLMN signaling requests targeting the PDU session context.
When present, it shall contain the apiRoot of the PDU session context to be used in intra-PLMN signalling request targeting the PDU session context.
(NOTE 7)
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.
hrsboInfoHrsboInfoFromHplmnC0..1This IE shall be present in HR roaming scenarios if the H-SMF supports the HR-SBO feature and it receives a request for HR-SBO.
When present, this IE shall Include the information for HR-SBO.
The absence of this IE shall indicate that the HR-SBO is not allowed.
HR-SBO
pendingUpdateInfoListarrayv(PendingUpdateInfo)O1..NWhen present, this IE shall indicate the list of information that are not required to be updated in real-time to the (H-)SMF, i.e. the change of the listed information (e.g. UE location or Timezone) may be piggybacked in a subsequent essential update (e.g. to exchange the N1 message from the UE) to the (H-)SMF. The NF service consumer (i.e. I-SMF/V-SMF) should not trigger an Update to the (H-)SMF including only the change(s) of the listed information.
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 TS 23.502.
NOTE 7:
During an inter-PLMN mobility, after retrieving the SM context from the old V-SMF, I-SMF or anchor SMF, the target V-SMF or I-SMF shall replace the apiRoot of the pduSessionRef with the interPlmnApiRoot (if available) if the anchor SMF is not in the target PLMN, or with the intraPlmnApiRoot (if available) otherwise. The Operator Identifier in the DNN indicates the PLMN ID of the anchor SMF.
NOTE 8:
Usage of Charging ID with Uint32 value for roaming scenarios may lead to Charging ID collision between SMFs.
NOTE 9:
The smfChargingId IE in SmContext (see clause 6.1.6.2.39) shall be set to the value in the homeProvidedSmfChargingId IE if received from the H-SMF.
Up

Up   Top   ToC