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.7.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.11 Type: HsmfUpdateData  6.1.6.2.12 Type: HsmfUpdatedData  6.1.6.2.13 Type: ReleaseData  6.1.6.2.14 Type: HsmfUpdateError  6.1.6.2.15 Type: VsmfUpdateData  6.1.6.2.16 Type: VsmfUpdatedData  6.1.6.2.17 Type: StatusNotification 
...

 

6.1.6.2.11  Type: HsmfUpdateData  p. 198
Attribute name Data type P Cardi­nality Description Applica­bility
requestIndicationRequestIndicationM1This IE shall indicate the request type.
peiPeiC0..1This IE shall be present if it is available and has not been provided earlier to the H-SMF or SMF.
When present, this IE shall contain the permanent equipment identifier.
vcnTunnelInfoTunnelInfoC1 This IE shall be present if:
  • the N9 tunnel information on the visited CN side provided earlier to the H-SMF has changed; or
  • during an EPS to 5GS handover execution using N26 interface.
When present, this IE shall contain the new N9 tunnel information on the visited CN side.
icnTunnelInfoTunnelInfoC0..1 This IE shall be present if:
  • the N9 tunnel information of the I-UPF for DL traffic provided earlier by the I-SMF to the SMF has changed; or
  • during an EPS to 5GS handover execution using N26 interface with I-SMF insertion.
When present, this IE shall contain the new N9 tunnel information of the I-UPF.		DTSSA
additionalCnTunnelInfoTunnelInfoC0..1This IE shall be present if additional N9 tunnel information provided earlier has changed, or if the UE requests to establish resources for a MA PDU session over the other access.
When present, it shall contain additional N9 tunnel information of the UPF controlled by the V-SMF or I-SMF.		MAPDU
servingNetworkPlmnIdNidC0..1This IE shall contain the serving core network operator PLMN ID, and, for an SNPN, the NID that together with the PLMN ID identifies the SNPN, if the serving network has changed.
anTypeAccessTypeC0..1This IE shall be present if the Access Network Type provided earlier to the H-SMF or SMF has changed, e.g. during a handover of the PDU session between 3GPP access and untrusted non-3GPP access (see clause 5.2.2.8.2.5).
When present, this IE shall indicate the new Access Network Type to which the PDU session is to be associated.
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
ratTypeRatTypeC0..1This IE shall be present and indicate the RAT Type used by the UE, if available, upon a change of RAT Type.
ueLocationUserLocationC0..1This IE shall be present if it is available, the UE Location has changed and needs to be reported to the H-SMF or SMF.
When present, this IE shall contain:
  • the new UE location information (see clause 5.2.3.4); and
  • the timestamp, if available, indicating the UTC time when the UeLocation information was acquired.
(NOTE 1)
ueTimeZoneTimeZoneC0..1This IE shall be present if it is available, the UE Time Zone has changed and needs to be reported to the H-SMF or SMF.
When present, this IE shall contain the new UE Time Zone.
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)
pauseChargingbooleanC0..1This IE shall be present if the H-SMF or SMF enabled the use of Pause Pause of Charging for the PDU session during the PDU session establishment and Pause of Charging needs to be started or stopped (see clause 4.4.4 of TS 23.502).
When present, it shall be set as follows:
  • true: to Start Pause of Charging;
  • false: to Stop Pause of Charging.
ptiProcedureTransactionIdC0..1This IE shall be present if the requestIndication indicates a UE requested PDU session modification or release. When present, it shall contain the PTI value received from the UE.
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).
(NOTE 5)
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).
qosFlowsRelNotifyListarray(QosFlowItem)C1..NThis IE shall be present if QoS flows have been released.
This IE shall also be present if QoS flow(s) have been rejected by the RAN or rejected by the V-SMF, during PDU session establishment procedure.
qosFlowsVsmfRejectedListarray(Qfi)O1..NThis IE may be present from V-SMF to H-SMF when qosFlowsRelNotifyList is present.
When present, this IE shall include the QFIs of the QoS flows that were rejected by the V-SMF.
When the H-SMF subsequently send N1 Message to the UE to remove the QoS rules and QoS Flow level QoS parameters associated with the rejected QoS Flow(s) as indicated in the qosFlowsRelNotifyList IE, the H-SMF should exclude the V-SMF rejected QoS flow(s). If all the rejected QoS flow(s) were rejected by the V-SMF, the H-SMF should skip the subsequent N1 message update to the UE.
qosFlowsNotifyListarray(QosFlowNotifyItem)C1..NThis IE shall be present if the QoS targets for GBR QoS flow(s) are not fulfilled anymore or when they are fulfilled again. For each GBR QoS flow indicated as not fulfilled anymore, the V-SMF/I-SMF may also indicate an alternative QoS profile which the NG-RAN currently fulfils in the currentQosProfileIndex IE or indicate that the NG-RAN cannot even fulfil the lowest alternative QoS profile.
NotifyListarray(PduSessionNotifyItem)C1..N Description of notifications related to the PDU session. This IE shall be present if the NG-RAN has established user plane resources for the PDU session that do not fulfil the User Plane Security Enforcement with a value Preferred, or when the user plane security enforcement is fulfilled again.
When present, this IE shall include the notification cause "UP_SEC_NOT_FULFILLED" if at least one of the UP integrity protection or UP ciphering security enforcement is not fulfilled.
If the securityResult IE is present in the message, it provides additional details on the security enforcement results.
(NOTE 4)
epsBearerIdarray(EpsBearerId)C0..NThis IE shall be present during an EPS to 5GS handover execution using the N26 interface.
When present, it shall contain the list of EPS bearer Id(s) successfully handed over to 5GS. The array shall be empty if no resource was successfully allocated in 5GS for any PDU session.
hoPreparationIndicationbooleanC0..1This IE shall be present during an EPS to 5GS handover preparation and handover execution using the N26 interface or during N2 handover execution with I-SMF insertion.
When present, it shall be set as follows:
  • true: an EPS to 5GS handover preparation or N2 handover preparation with I-SMF is in progress; the PGW-C/SMF shall not switch the DL user plane of the PDU session yet.
  • false: there is no on-going EPS to 5GS handover preparation or N2 handover preparation with I-SMF in progress. If a handover preparation was in progress, the handover has been completed. The PGW-C/SMF shall switch the DL user plane of the PDU session using the N9 tunnel information that has been received in the vcnTunnelInfo or icnTunnelInfo.
It shall be set to "true" during an EPS to 5GS handover preparation using the N26 interface.
It shall be set to "false" during an EPS to 5GS handover execution using the N26 interface or during N2 handover execution with I-SMF insertion.
revokeEbiListarray(EpsBearerId)C1..NThis IE shall be present to request the H-SMF or 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.
causeCauseC0..1This IE shall be present and set as specified in clause 5.2.2.8.2.6 during P-CSCF restoration procedure, clause 5.2.2.8.2.3 during 5G-AN requested PDU session resource release procedure and clause 5.2.2.3.26 during AMF requested PDU Session Release due to Network Slice instance not available.
When present, this IE shall indicate the NF Service Consumer cause of the requested modification.
ngApCauseNgApCauseC0..1The V-SMF or I-SMF shall include this IE if it received it from the 5G-AN and, for a HR PDU session, if this information is permitted to be sent to the H-SMF operator according to the V-SMF operator's policy. When present, this IE shall indicate the NGAP cause for the requested modification.
5gMmCauseValue5GMmCauseC0..1The V-SMF or I-SMF shall include this IE if it received it from the AMF and, for a HR PDU session, if this information is permitted to be sent to the H-SMF operator according to the V-SMF operator's policy.
alwaysOnRequestedbooleanC0..1This IE shall be present and set to true if the UE requests to change the PDU session to an always-on PDU session and this is allowed by local policy in the V-SMF or I-SMF. When present, it shall be set as follows:
  • true: request for an always-on PDU session
  • false (default): not a request for an always-on PDU session
epsInterworkingIndEpsInterworkingIndicationO0..1This IE may be present if the indication has been received from AMF and, for a HR PDU session, it is allowed to be forwarded to H-SMF by operator configuration.
When present, this IE shall indicate whether the PDU session may possibly be moved to EPS or EPC/ePDG and whether N26 interface to be used during EPS interworking procedures.
secondaryRatUsageReportarray(SecondaryRatUsageReport)O1..NThis IE may be present to report usage data for a secondary RAT for QoS flows.
(NOTE 2)
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.
anTypeCanBeChangedbooleanC0..1 This IE shall be present and set to true to indicate that the Access Network Type associated to the PDU session can be changed (see clause 5.2.2.8.2.2), during a Service Request procedure (see clauses 4.2.3.2 and 4.3.3.3 of 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.
maReleaseIndMaReleaseIndicationC0..1This IE shall be present if a MA PDU session is requested to be released over a single access, in the following cases:
  • when UE/AMF/V-SMF initiates MA PDU session release over one access; or
  • when UE deregisters from one access.
When present, it shall indicate the access to be released.		MAPDU
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
unavailableAccesslndUnavailableAccessIndicationC0..1This IE shall be present if an access of a MA-PDU session is unavailable (see clause 4.22.7 of TS 23.502).
When present, it shall indicate the access that is unavailable.		MAPDU
psaInfoarray(PsaInformation)C1..NThis IE shall be present, for a PDU session with an I-SMF, if one or more PSAs UPF are inserted and/or removed by the I-SMF.DTSSA
ulclBpInfoUlclBpInformationC0..1This IE shall be present, for a PDU session with an I-SMF, if an UL CL or BP UPF separate from the local PSA is inserted.DTSSA
n4InfoN4InformationO0..1This IE may be present if the I-SMF needs to send N4 information (e.g. traffic usage reporting) to the SMF for traffic offloaded at a PSA controlled by an I-SMF.DTSSA
n4InfoExt1N4InformationO0..1This IE may be present if the I-SMF needs to send additional N4 information (e.g. traffic usage reporting) to the SMF for traffic offloaded at a PSA controlled by an I-SMF.DTSSA
n4InfoExt2N4InformationO0..1This IE may be present if the I-SMF needs to send additional N4 information to the SMF (e.g. during a change of PSA).DTSSA
presenceInLadnPresenceStateC0..1This IE shall be present during Xn based handover with I-SMF change, if the DNN corresponds to a LADN.
When present, it shall be set to "IN" or "OUT" to indicate that the UE is in or out of the LADN service area. 		DTSSA
vsmfPduSessionUriUriC0..1This IE shall be present during any procedure when the V-SMF has changed, as specified in clause 4.23.4.3 of TS 23.502.
When present, it shall include the callback URI representing the PDU session in the new V-SMF.		DTSSA
ismfPduSessionUriUriC0..1This IE shall be present during any procedure when the I-SMF has changed, as specified in clause 4.23.4.3 of TS 23.502.
When present, it shall include the callback URI representing the PDU session in the new I-SMF.		DTSSA
vsmfIdNfInstanceIdC0..1This IE shall be present during any procedure when the V-SMF has changed, as specified in clause 4.23.4.3 of TS 23.502.
When present, it shall contain the identifier of the new V-SMF.		DTSSA
ismfIdNfInstanceIdC0..1This IE shall be present during any procedure when the I-SMF has changed, as specified in clause 4.23.4.3 of TS 23.502.
When present, it shall contain the identifier of the new I-SMF.		DTSSA
vSmfServiceInstanceIdstringO0..1This IE may be present during any procedure when the V-SMF has changed, as specified in clause 4.23.4.3 of TS 23.502.
When present, this IE shall contain the serviceInstanceId of the new V-SMF service instance serving the PDU session.
This IE may be used by the H-SMF to identify PDU sessions affected by a failure or restart of the V-SMF service (see clauses 6.2 and 6.3 of TS 23.527).		DTSSA
iSmfServiceInstanceIdstringO0..1This IE may be present during any procedure when the I-SMF has changed, as specified in clause 4.23.4.3 of TS 23.502.
When present, this IE shall contain the serviceInstanceId of the new I-SMF service instance serving the PDU session.
This IE may be used by the SMF to identify PDU sessions affected by a failure or restart of the I-SMF service (see clauses 6.2 and 6.3 of TS 23.527).		DTSSA
dlServingPlmnRateCtlintegerC0..1The IE shall be present when the Serving PLMN Rate Control for Downlink data packets has changed since last update to the H-SMF (for HR PDU session) or SMF (for PDU sessions with an I-SMF).
When present, this IE shall contain the maximum allowed number of Downlink NAS Data PDUs per deci hour of the serving PLMN, as specified in clause 5.31.14.2 of TS 23.501. If Serving PLMN Rate Control is disabled, the IE shall be set to null value.
Minimum: 10		CIOT
dnaiListarray(Dnai)C1..N This IE shall be present over N16a during UE Triggered Service Request procedure with I-SMF change, Xn based handover and Inter NG-RAN node N2 based handover with I-SMF change (see clauses 4.23.4.3, 4.23.11.3 and 4.23.7.3.3 in TS 23.502).
When present, it shall include the list of DNAIs supported by the new I-SMF.		DTSSA
supportedFeaturesSupportedFeaturesC0..1This IE shall be present if the vsmfId or the ismfId is present (i.e. during a change of V-SMF or I-SMF) and at least one optional feature defined in clause 6.1.8 is supported by the new V-SMF or I-SMF.
If this IE is absent when the vsmfId or the ismfId is present, the new V-SMF or I-SMF respectively shall be considered as not supporting any optional feature.
roamingChargingProfileRoamingChargingProfileO0..1 This IE may be present during an inter-PLMN V-SMF change (including the inter-PLMN mobility from HPLMN with I-SMF to VPLMN). When present, it shall contain the Roaming Charging Profile applicable in the VPLMN (see clauses 5.1.9.1, 5.2.1.7 and 5.2.2.12.2 of TS 32.255).
moExpDataCounterMoExpDataCounterC0..1This IE shall be present if received from AMF.
When present, this IE shall contain the MO Exception Data Counter.		CIOT
vplmnQosVplmnQosO0..1When present, this IE shall contain the VPLMN QoS to be applied to the QoS flow with default QoS of the PDU Session.VQOS
securityResultSecurityResultC0..1This IE shall be present if received from NG-RAN.
When present, this IE shall contain the Security Result associated to the PDU session. See clause 9.3.1.59 of TS 38.413.
upSecurityInfoUpSecurityInfoC0..1This IE shall be present if received from NG-RAN during Xn handover procedure (see clause 5.2.2.8.2.16).
When present, this IE shall contain the User Plane Security Information associated to the PDU session. See clause 9.3.1.60 of TS 38.413.
amfNfIdNfInstanceIdC0..1This IE shall be present if it is received in the Update SM Context request.
When present, it shall contain the identifier of the serving AMF.
guamiGuamiC0..1This IE shall be present if the amfNfId is present.
When present, it shall contain the serving AMF's GUAMI
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.
The V-/I-SMF may determine to pass or not the information to the (H-)SMF based on operator policy; if the V-/I-SMF determines to pass the information, the V-/I-SMF shall transparently forward this information to the (H-)SMF.
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).
smPolicyNotifyIndbooleanC0..1This IE shall be included by I-SMF to SMF, if it is received from AMF and it is not previously provided to the SMF.
When 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
satelliteBackhaulCatSatelliteBackhaulCategoryC0..1This IE shall be present if the V-SMF/I-SMF and the anchor SMF supports the 5GSAT feature and:
  • the satelliteBackhaulCat IE has been received from the AMF and there is a change of the satelliteBackhaulCat IE compared to what has been signalled earlier to the (H-)SMF (as determined from the SmContext); or
  • upon inter-AMF mobility (when a target AMF is taking over the control of the PDU session), the new AMF does not include the satelliteBackhaulCat IE and a satellite backhaul category had been signalled to the SMF (as determined from the SmContext).
When present, this IE shall indicate the value received from the AMF or, in the latter case, the value "NON_SATELLITE" to indicate that there is no longer any satellite backhaul towards the new 5G AN serving the UE. 		5GSAT
maxIntegrityProtectedDataRateUlMaxIntegrityProtectedDataRateC0..1This IE shall be present if received from the UE during PDU session modification procedure, see clause 4.3.3.2 of TS 23.502.
When present, it shall indicate the maximum integrity protected data rate supported by the UE for uplink.
(NOTE 5)
maxIntegrityProtectedDataRateDlMaxIntegrityProtectedDataRateC0..1This IE shall be present if received from the UE during PDU session modification procedure, see clause 4.3.3.2 of TS 23.502.
When present, it shall indicate the maximum integrity protected data rate supported by the UE for downlink.
(NOTE 5)
upCnxStateUpCnxStateC0..1 This IE shall be present to indicate the User Plane resource establishment status in the I-SMF/V-SMF, if an Update or Create request is required to be sent to the (H-)SMF before the User Plane resource for the PDU session is established during a service request procedure for a PDU session with an I-SMF/V-SMF (see clause 4.23.4.2 and clause 4.23.4.3 of TS 23.502).
When present, this IE shall be set as specified in clause 5.2.2.8.2.23.
ecsAddrConfigInfosarray(EcsAddrConfigInfo)C1..NThis IE shall be sent if the information is modified by the NEF.
When present, this IE shall replace any earlier received ECS Address Configuration Information Parameters in SMF.		HR-SBO
hrsboInfoHrsboInfoFromVplmnC0..1This IE shall be present in the following scenarios, for a HR PDU session, if the new V-SMF requests HR SBO authorization:
  • V-SMF insertion (i.e. H-PLMN to V-PLMN mobility); and
  • Inter-PLMN V-SMF change (i.e. mobility between different V-PLMNs).
This IE shall also be present, for a HR PDU session, if the HR-SBO information signaled earlier by the V-SMF to the H-SMF needs to be changed, e.g. to signal a new V-EASDF IP address or the EAS IP Replacement capability of the new V-SMF upon a change of V-SMF.
When present, this IE shall Include the information for HR-SBO as defined in clause 6.1.6.2.72. 		HR-SBO
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
nsReplTerminIndbooleanC0..1This IE shall be present for a notification of termination of Network Slice Replacement, if the PDU Session is associated with the Alternative S-NSSAI and the replaced S-NSSAI is available again. The SMF shall transfer the PDU Session to the replaced S-NSSAI.
When present, it shall be set as follows:
  • true: the network slice replacement is terminated
The presence of this IE with false value shall be prohibited.
See clause 5.15.19 of TS 23.501.		NSRP
disasterRoamingIndbooleanO0..1This IE may be set if the V-SMF is indicated by the AMF that the UE is registered for Disaster Roaming service during a V-SMF change procedure. (NOTE 6)
When present, this IE shall be set as follows:
  • true: the UE is registered for Disaster Roaming service
pduSetSupportIndbooleanC0..1This IE shall be included by I-SMF/V-SMF to SMF/H-SMF for a PDU session with an I-SMF or a Home-Routed PDU session if the support of the PDU Set based handling in the NG-RAN has been changed and during a V-SMF change.
(NOTE 7)
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: 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, e.g. during an PDU Session Establishment procedure.
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:
An SMF complying with this version of the specification should report secondary RAT usage using the secondaryRatUsageInfo attribute that replaces the secondaryRatUsageReport attribute.
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 if exists via SM Policy Association Modification. See clause 4.3.3.2 of TS 23.502.
NOTE 4:
The attribute name does not follow the naming conventions specified in TS 29.501. The attribute name is kept though as defined in the current specification for backward compatibility reason.
NOTE 5:
The maxIntegrityProtectedDataRateUl and maxIntegrityProtectedDataRateDl IEs shall be ignored by the H-SMF or SMF if the Integrity protection maximum data rate in n1SmInfoFromUe IE is received.
NOTE 6:
The H-SMF shall determine that the UE is not registered for Disaster Roaming service if the disasterRoamingInd is not present during a V-SMF change procedure.
NOTE 7:
The (H-)SMF shall consider the PDU Set based handling is not supported if the pduSetSupportInd IE is absent during a V-SMF change.
Up
6.1.6.2.12  Type: HsmfUpdatedData  p. 209
Attribute name Data type P Cardi­nality Description Applica­bility
n1SmInfoToUeRefToBinaryDataC0..1This IE shall be present if the H-SMF/SMF needs to send N1 SM information to the UE that does not need to be interpreted by the V-SMF/I-SMF. When present, this IE shall reference the n1SmInfoToUe binary data (see clause 6.1.6.4.4).
n4InfoN4InformationO0..1This IE may be present if the SMF needs to send N4 response information to the I-SMF (e.g. related with traffic usage reporting).DTSSA
n4InfoExt1N4InformationO0..1This IE may be present if the SMF needs to send additional N4 response information to the I-SMF(e.g. related with traffic usage reporting).DTSSA
n4InfoExt2N4InformationO0..1This IE may be present if the SMF needs to send additional N4 response information to the I-SMF (e.g. related with traffic usage reporting).DTSSA
dnaiListarray(Dnai)C1..N This IE shall be present over N16a during UE Triggered Service Request procedure with I-SMF change, Xn based handover and Inter NG-RAN node N2 based handover with I-SMF change (see clauses 4.23.4.3, 4.23.11.3 and 4.23.7.3.3 in TS 23.502).
When present, it shall include the DNAI(s) of interest for this PDU Session.
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
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 PDU session resource.
roamingChargingProfileRoamingChargingProfileO0..1 This IE may be present during an inter-PLMN V-SMF change (including the inter-PLMN mobility from HPLMN with I-SMF to VPLMN). When present, it shall contain the Roaming Charging Profile selected by the HPLMN (see clauses 5.1.9.1, 5.2.1.7 and 5.2.2.12.2 of TS 32.255).
homeProvidedChargingIdstringC0..1When present, this IE shall contain the Home provided Charging ID (see TS 32.255).
This IE shall be present during a HPLMN to VPLMN mobility of a PDU session with I-SMF in HPLMN.
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 3, NOTE 4)		DTSSA
homeProvidedSmfChargingIdSmfChargingIdC0..1When present, this IE shall contain the Home provided String based Charging ID (see TS 32.255).
This IE shall be present during a HPLMN to VPLMN mobility of a PDU session with I-SMF in HPLMN, if both the V-SMF and the H-SMF support the "SCID" feature. This IE shall also be included when the V-SMF changes, if the new V-SMF supports the "SCID" feature.
(NOTE 5)		DTSSA, SCID
ipv6MultiHomingIndbooleanC0..1This IE shall be present over N16a, if available and an I-SMF has been changed during the following procedures: Registration, Service Request, Xn based handover, Inter NG-RAN node N2 based handover (see clause 4.23 of 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
upSecurityUpSecurityC0..1 This IE shall be present if the "upSecurityInfo" IE was received in the request (i.e. during an Xn handover), and there is a mismatch between security policy received and stored (see clause 5.2.2.8.2.16).
When present, this IE shall indicate the security policy for integrity protection and encryption for the user plane of the PDU session.
This IE may be present during a handover from non-3GPP access to 3GPP access, to indicate the security policy for integrity protection and encryption for the user plane of the PDU session in the target access type.
This IE may be present when UE Integrity Protection Maximum Data Rate was received in the request, during a UE triggered PDU session modification procedure.
(NOTE 1, NOTE 2)
maxIntegrityProtectedDataRateUlMaxIntegrityProtectedDataRateC0..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 supported by the UE for uplink.
(NOTE 1)
maxIntegrityProtectedDataRateDlMaxIntegrityProtectedDataRateC0..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 supported by the UE for downlink.
(NOTE 1)
qosFlowsSetupListarray(QosFlowSetupItem)C1..NThis IE shall be present during a handover between 3GPP and non-3GPP accesses.
When present, it shall contain the set of QoS flow(s) to establish for the PDU session for the target access type.
(NOTE 1)
sessionAmbrAmbrC0..1This IE shall be present during a handover between 3GPP and non-3GPP accesses.
When present, this IE shall contain the Session AMBR authorized for the PDU session for the target access type.
(NOTE 1)
epsPdnCnxInfoEpsPdnCnxInfoC0..1This IE shall be present during a handover from non-3GPP access to 3GPP access, if the PDU session may be moved to EPS during its lifetime.
(NOTE 1)
The IE shall also be included when the EPS PDN Connection Context Information of the PDU session is changed, e.g. due to reselection of anchor SMF.
epsBearerInfoarray(EpsBearerInfo)C1..NThis IE shall be present during a handover from non-3GPP access to 3GPP access, if the PDU session may be moved to EPS during its lifetime.
When present, it shall include the complete epsBearerInfo IE(s) for all EBIs.
(NOTE 1)
ptiProcedureTransactionIdC0..1This IE shall be present during a handover between 3GPP and non-3GPP accesses.
When present, it shall contain the PTI value received in the corresponding request.
interPlmnApiRootUriC0..1This IE should be present if the information has changed. 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.
intraPlmnApiRootUriC0..1This IE should be present if the information has changed. 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.
hrsboInfoHrsboInfoFromHplmnC0..1This IE shall be present in the following scenarios if the H-SMF supports the HR-SBO feature and if it receives a request for HR-SBO authorization in the Update request:
  • V-SMF insertion (i.e. H-PLMN to V-PLMN mobility); and
  • Inter-PLMN V-SMF change (i.e. mobility between different V-PLMNs).
This IE shall also be present, for a HR PDU session, if the HR-SBO information signaled earlier by the H-SMF to the V-SMF needs to be changed, e.g. to signal a new Home DNS Server address.
When present, this IE shall Include the information for HR-SBO as defined in clause 6.1.6.2.73.
The absence of this IE in an Update response when the Update request includes a request for HR SBO authorization shall be interpreted as indicating that HR-SBO is not allowed. 		HR-SBO
NOTE 1:
During a handover between 3GPP and non-3GPP accesses, the V-SMF or I-SMF shall delete any corresponding information received earlier for the source access type and use the new information received for the target access type.
NOTE 2:
During inter-system mobility from EPS to 5GS, the UE Integrity Protection Maximum Data Rate is not available at the SMF during PDU Session Creation. The UE will provide UE Integrity Protection Maximum Data Rate to the network within a subsequent UE triggered PDU session modification procedure, as specified in clause 4.3.3.2 of TS 23.502.
NOTE 3:
The chargingId IE in SmContext (see clause 6.1.6.2.39) shall be set to the value received in the homeProvidedChargingId IE during a HPLMN to VPLMN mobility of a PDU session with I-SMF in HPLMN.
NOTE 4:
Usage of Charging ID with Uint32 value for roaming scenarios may lead to Charging ID collision between SMFs.
NOTE 5:
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
6.1.6.2.13  Type: ReleaseData  p. 213
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 PDU session release.
ngApCauseNgApCauseC0..1The V-SMF or I-SMF shall include this IE, if it is available and, for a HR PDU session, if this information is permitted to be sent to the H-SMF operator according to the V-SMF operator's policy. When present, this IE shall indicate the NGAP cause for the requested PDU session release.
5gMmCauseValue5GMmCauseC0..1The V-SMF or I-SMF shall include this IE if it received it from the AMF and, for a HR PDU session, if this information is permitted to be sent to the H-SMF operator according to the V-SMF operator's policy.
ueLocationUserLocationC0..1This IE shall be present, if available.
When present, it shall contain the UE location information (see clause 5.2.3.4).
ueTimeZoneTimeZoneC0..1This IE shall be present, if available.
When present, it shall contain the UE Time Zone.
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.
secondaryRatUsageReportarray(SecondaryRatUsageReport)O1..NThis IE may be present to report usage data for a secondary RAT for QoS flows.
(NOTE)
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.
n4InfoN4InformationO0..1This IE may be present if the I-SMF needs to send N4 information (e.g. traffic usage reporting) to the SMF for traffic offloaded at a PSA controlled by an I-SMF.DTSSA
n4InfoExt1N4InformationO0..1This IE may be present if the I-SMF needs to send additional N4 information (e.g. traffic usage reporting) to the SMF for traffic offloaded at a PSA controlled by an I-SMF.DTSSA
n4InfoExt2N4InformationO0..1This IE may be present if the I-SMF needs to send additional N4 information (e.g. traffic usage reporting) to the SMF for traffic offloaded at a PSA controlled by an I-SMF.DTSSA
NOTE:
An SMF complying with this version of the specification should report secondary RAT usage using the secondaryRatUsageInfo attribute that replaces the secondaryRatUsageReport attribute.
Up
6.1.6.2.14  Type: HsmfUpdateError  p. 214
Attribute name Data type P Cardi­nality Description
errorProblemDetailsM1 More information on the error shall be provided in the "cause" attribute of the "ProblemDetails" structure.
ptiProcedureTransactionIdC0..1This IE shall be present if this is a response sent to a UE requested PDU session modification. When present, it shall contain the PTI value received in the corresponding request.
n1smCausestringC0..1This IE shall be present if the request included n1SmInfoFromUe. When present, it shall contain the 5GSM cause the H-SMF or SMF proposes the V-SMF or I-SMF to return to the UE. It shall be encoded as two characters in hexadecimal representation with each character taking a value of "0" to "9" or "A" to "F", and represent the cause value of the 5GSM cause IE specified in clause 9.11.4.2 of TS 24.501.
Pattern: "^[A-F0-9]{2}$"
Example: the cause "Invalid mandatory information" shall be encoded as "60".
See NOTE.
n1SmInfoToUeRefToBinaryDataC0..1This IE shall be present if the H-SMF or 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).
backOffTimerDurationSecO0..1When present, this IE shall indicate a Back-off timer value, in seconds, that the V-SMF or I-SMF may use when rejecting the NAS message towards the UE.
recoveryTimeDateTimeO0..1Timestamp (in UTC) when the H-SMF or SMF service instance was (re)started (see clause 6.3 of TS 23.527).
NOTE:
This IE contains information that the V-SMF or I-SMF shall transfer to the UE without interpretation. It is sent as a separate IE rather than within the n1SmInfoToUE binary data because the 5GSM cause IE is defined as a "V" IE (i.e. without a Type field) in the NAS PDU Session Modification Reject message.
Up
6.1.6.2.15  Type: VsmfUpdateData  p. 215
Attribute name Data type P Cardi­nality Description Applica­bility
requestIndicationRequestIndicationM1This IE shall indicate the request type.
sessionAmbrAmbrC1This IE shall be present if the Session AMBR authorized for the PDU session is modified. When present, it shall contain the new Session AMBR authorized for the PDU session.
qosFlowsAddModRequestListarray(QosFlowAddModifyRequestItem)C1..NThis IE shall be present if QoS flows are requested to be established or modified.
qosFlowsRelRequestListarray(QosFlowReleaseRequestItem)C1..NThis IE shall be present if QoS flows are requested to be released.
epsBearerInfoarray(EpsBearerInfo)C1..NThis IE shall be present if the PDU session may be moved to EPS during its lifetime and the ePSBearerInfo has changed.
When present, it shall only include epsBearerInfo IE(s) for new EBI or for EBIs for which the epsBearerInfo has changed. The complete epsBearerInfo shall be provided for an EBI that is included (i.e. the epsBearerInfo newly received for a given EBI replaces any epsBearerInfo previously received for this EBI).
assignEbiListarray(Arp)C1..NThis IE shall be present if the H-SMF requests EBIs to be assigned.
revokeEbiListarray(EpsBearerId)C1..NThis IE shall be present if the H-SMF/SMF requests the V-SMF/I-SMF to revoke some EBI(s). When present, it shall contain the EBIs to revoke.
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.
ptiProcedureTransactionIdC0..1This IE shall be present if the request is sent in response to a UE requested PDU session modification or release. When present, it shall contain the PTI value received in the corresponding request.
n1SmInfoToUeRefToBinaryDataC0..1This IE shall be present if the H-SMF/SMF needs to send N1 SM information to the UE that does not need to be interpreted by the V-SMF/I-SMF. When present, this IE shall reference the n1SmInfoToUe binary data (see clause 6.1.6.4.4).
alwaysOnGrantedbooleanC0..1This IE shall be present if:
  • an alwaysOnRequested IE was received in an earlier V-SMF/I-SMF initiated Update request to change the PDU session to an always-on PDU session; or
  • the H-SMF/SMF determines, based on local policy, that the PDU session needs to be established as an always-on PDU session.
When present, it shall be set as follows:
  • true: always-on PDU session granted.
  • false (default): always-on PDU session not granted.
hsmfPduSessionUriUriC0..1This IE shall be included if:
  • an Update Request is sent to the V-SMF/I-SMF before the Create Response (e.g. for EPS bearer ID allocation as specified in clause 4.11.1.4.1 of TS 23.502, or for Secondary authorization/authentication as specified in clause 4.3.2.3 of TS 23.502), and
  • the H-SMF PDU Session Resource URI has not been previously provided to the V-SMF/I-SMF.
This IE shall not be included otherwise.
When present, this IE shall include the URI representing the PDU session resource in the H-SMF.
newSmfIdNfInstanceIdC0..1This IE may be present if the anchor SMF has changed and the SMF Instance ID of the new anchor SMF has not been already signalled to the I-SMF or V-SMF. When present, it shall carry the NF instance identifier of the new anchor SMF handling the PDU session.
newSmfPduSessionUriUriC0..1This IE shall be present if the newSmfId is present.
When present, it shall carry the URI representing the updated PDU session resource in the new anchor SMF.
supportedFeaturesSupportedFeaturesC0..1 This IE shall be present if "hsmfPduSessionUri" IE is present and at least one optional feature defined in clause 6.1.8 is supported.
causeCauseO0..1When present, this IE shall indicate the cause for the requested modification.
n1smCausestringO0..1 When present, this IE shall contain the 5GSM cause the H-SMF proposes the V-SMF/I-SMF to send to the UE. It shall be encoded as two characters in hexadecimal representation with each character taking a value of "0" to "9" or "A" to "F", and represent the cause value of the 5GSM cause IE specified in clause 9.11.4.2 of TS 24.501.
Example: the cause "Invalid mandatory information" shall be encoded as "60".
See NOTE.
backOffTimerDurationSecO0..1When present, this IE shall indicate a Back-off timer value, in seconds, that the V-SMF/I-SMF may use when sending the NAS message (PDU Session Release Command) towards the UE.
maReleaseIndMaReleaseIndicationC0..1This IE shall be present if one access of a MA PDU session is to be released, when H-SMF or SMF initiates MA PDU session release over one access.
When present, it shall indicate the access requested to be released.		MAPDU
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
additionalCnTunnelInfoTunnelInfoC0..1This IE shall be present for a MA-PDU session if the UE requested to establish resources for a MA PDU session over the other access.
When present, it shall contain additional N9 tunnel information of the UPF controlled by the H-SMF or SMF.		MAPDU
dnaiListarray(Dnai)C0..NThis IE shall be present if received from PCF during I-SMF Related Procedures with PCF (see clause 4.23.6.2 in TS 23.502).
When present, the IE shall include a list of DNAI(s) the SMF deems relevant for the PDU Session.
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.
If this IE is not present, the I-SMF shall consider that the dnaiList has not changed. If there is no more DNAI of interest for the PDU session, the dnaiList attribute shall be present and be encoded as an empty array.		DTSSA
DTSSA-Ext1
n4InfoN4InformationO0..1This IE may be present if the SMF needs to send N4 information to the I-SMF for the control of traffic offloaded at a PSA/BP/ULCL controlled by an I-SMF.DTSSA
n4InfoExt1N4InformationO0..1This IE may be present if the SMF needs to send additional N4 information to the I-SMF for the control of traffic offloaded at a PSA/BP/ULCL controlled by an I-SMF.DTSSA
n4InfoExt2N4InformationO0..1This IE may be present if the SMF needs to send additional N4 information to the I-SMF for the control of traffic offloaded at a PSA/BP/ULCL controlled by an I-SMF (e.g. during a change of PSA).DTSSA
n4InfoExt3N4InformationO0..1This IE may be present if the SMF needs to send additional N4 information to the I-SMF for the control of traffic offloaded at a PSA/BP/ULCL controlled by an I-SMF (e.g. during simultaneous change of BP/ULCL and PSA).SCPBU
smallDataRateControlEnabledbooleanC0..1This IE shall be present if the applicability of small data rate control on the PDU session changes.
When present, it shall be set as follows:
  • true: small data rate control is applicable.
  • false: small data rate control is not applicable.
CIOT
qosMonitoringInfoQosMonitoringInfoC0..1This IE may be present if QoS monitoring has been activated for at least one QoS flow of the PDU session (see the qosMonitoringReq attribute in clause 6.1.6.2.22).DTSSA
epsPdnCnxInfoEpsPdnCnxInfoC0..1 This IE shall be present if the PDU session may be moved to EPS during its lifetime and the EpsInterworkingIndication is changed to "WITH_N26". The IE shall also be present when the EPS PDN Connection Context Information of the PDU session is changed, e.g. due to change of anchor SMF.
n9DataForwardingIndbooleanC0..1 This IE shall be present and set as specified in clauses 4.23.9.4 and 4.23.9.5 of TS 23.502 during simultaneous change of Branching Points or UL CLs controlled by I-SMF or controlled by different I-SMFs.
When present, it shall be set as follows:
  • true: setup N9 forwarding tunnels between Branching Points or UL CLs;
  • false (default): N9 forwarding tunnels between Branching Points or UL CLs are not required to be setup (see clauses 5.2.2.8.3.6 and 5.2.2.8.3.10).
N9FSC
n9InactivityTimerDurationSecO0..1 When 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 clauses 4.23.9.4 and 4.23.9.5 of TS 23.502.N9FSC
hrsboInfoHrsboInfoFromHplmnO0..1This IE may be present if the H-SMF and the V-SMF supports the HR-SBO feature and if the H-SMF needs to update the HR-SBO information towards the V-SMF, e.g. due to a change of the user subscription data or policy information.
When present, this IE shall include the complete information for HR-SBO as defined in clause 6.1.6.2.73 and the V-SMF shall replace any earlier received HR-SBO information by the new HR-SBO information.		HR-SBO
altHplmnSnssaiSnssaiC0..1This IE shall be present for a HR PDU session if the H-SMF determines to retain the PDU session for the alternative HPLMN S-NSSAI, during network slice replacement.
When present, this IE shall indicate the alternative HPLMN S-NSSAI to be used by the HR PDU session.
See clause 5.15.19 of TS 23.501.		NSRP
pduSessionRetainIndbooleanC0..1This IE shall be present and set to true, if the H-SMF determines to retain the PDU session for the alternative HPLMN S-NSSAI during network slice replacement.
When present with true value, this IE indicates the PDU session is retained for the alternative HPLMN S-NSSAI.
Present with false value shall be prohibited.
See clause 4.3.3.3 of TS 23.502.		NSRP
pendingUpdateInfoListarray(PendingUpdateInfo)O0..NWhen present, this IE shall indicate the updated 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.
When present, the NF service consumer (i.e. I-SMF/V-SMF) shall replace any pendingUpdateInfoList received earlier by the new information received in this IE.
NOTE:
This IE contains information that the V-SMF shall transfer to the UE without interpretation. It is sent as a separate IE rather than within the n1SmInfoToUE binary data because the 5GSM cause IE is defined as a "V" IE (i.e. without a Type field) in the NAS PDU Session Release Command message.
Up
6.1.6.2.16  Type: VsmfUpdatedData  p. 220
Attribute name Data type P Cardi­nality Description Applica­bility
qosFlowsAddModListarray(QosFlowItem)C1..NThis IE shall be present if QoS flows have been successfully established or modified. For each GBR QoS flow, the V-SMF/I-SMF may also indicate an alternative QoS profile which the NG-RAN currently fulfils in the currentQosProfileIndex IE or indicate that the NG-RAN cannot even fulfil the lowest alternative QoS profile.
qosFlowsRelListarray(QosFlowItem)C1..NThis IE shall be present if QoS flows have been successfully released.
qosFlowsFailedtoAddModListarray(QosFlowItem)C1..NThis IE shall be present if QoS flows failed to be established or modified.
qosFlowsVsmfRejectedAddModListarray(Qfi)O1..NThis IE may be present from V-SMF to H-SMF when the qosFlowsFailedtoAddModList IE is present.
When present, this IE shall include the QFIs of the QoS flows failed to be established or modified due to rejection by the V-SMF.
When the H-SMF subsequently send N1 Message to the UE to revert the update of QoS rules and QoS Flow level QoS parameters associated with the failed QoS Flow(s) indicated in the qosFlowsFailedtoAddModList IE, the H-SMF should exclude the QoS flow(s) that were failed to be established or modified due to rejection by the V-SMF. If all the failed QoS flow(s) were due to rejection by the V-SMF, the H-SMF should skip the subsequent N1 message update to the UE.
qosFlowsFailedtoRelListarray(QosFlowItem)C1..NThis IE shall be present if QoS flows failed to be released.
n1SmInfoFromUeRefToBinaryDataC0..1This IE shall be present if the V-SMF/I-SMF has received known N1 SM information from the UE that does not need to be interpreted by the V-SMF/I-SMF. When present, this IE shall reference the n1SmInfoFromUe binary data (see clause 6.1.6.4.4).
unknownN1SmInfoRefToBinaryDataC0..1This IE shall be present if the V-SMF/I-SMF has received unknown N1 SM information from the UE. When present, this IE shall reference the unknownN1SmInfo binary data (see clause 6.1.6.4.4).
ueLocationUserLocationC0..1This IE shall be present if it is available and QoS flows have been successfully established, modified or released.
When present, this IE shall contain the UE location information (see clause 5.2.3.4).
ueTimeZoneTimeZoneC0..1This IE shall be present if it is available and QoS flows have been successfully established, modified or released.
When present, this IE shall contain the new UE Time Zone.
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.
assignedEbiListarray(EbiArpMapping)C1..NThis IE shall be present if the AMF assigned the requested EBI(s). When present, it shall contain the EBIs that were successfully assigned.
failedToAssignEbiListarray(Arp)C1..NThis IE shall be present if the AMF failed to assign EBIs for a set of ARPs.
releasedEbiListarray(EpsBearerId)C1..NThis IE shall be present if the NF Service Consumer requested the revoke EBI(s) or if the AMF revoked already assigned EBI(s) for this PDU session towards the V-SMF. This IE shall contain the list of EBI(s) released for this PDU session at the AMF.
secondaryRatUsageReportarray(SecondaryRatUsageReport)O1..NThis IE may be present to report usage data for a secondary RAT for QoS flows.
(NOTE)
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.
n4InfoN4InformationO0..1This IE may be present if the I-SMF needs to send N4 response information to the SMF for the control of traffic offloaded at a PSA/BP/ULCL controlled by an I-SMF.DTSSA
n4InfoExt1N4InformationO0..1This IE may be present if the I-SMF needs to send additional N4 response information to the SMF for the control of traffic offloaded at a PSA/BP/ULCL controlled by an I-SMF.DTSSA
n4InfoExt2N4InformationO0..1This IE may be present if the I-SMF needs to send additional N4 response information to the SMF for the control of traffic offloaded at a PSA/BP/ULCL controlled by an I-SMF (e.g. during a change of PSA).DTSSA
n4InfoExt3N4InformationO0..1This IE may be present if the I-SMF needs to send additional N4 response information to the SMF for the control of traffic offloaded at a PSA/BP/ULCL controlled by an I-SMF (e.g. during simultaneous change of BP/ULCL and PSA).SCPBU
modifiedEbiListNotDeliveredbooleanC0..1This IE should be present with the value true when the modifiedEbiList IE was received in VsmfUpdateData in request but cannot be updated to the AMF, e.g., during (H-)SMF triggered PDU session modification procedure and the AMF doesn't support the EAEA feature.
When present, the IE shall be set as following:
  • true: the received modifiedEbiList was not delivered to the AMF.
  • false: the received modifiedEbiList was delivered to the AMF.
Absence of this IE means whether modifiedEbiList was delivered or not is unknown.
ecnMarkingCongestionInfoStatusarray(EcnMarkingCongestionInfoStatus)C1..NThis IE shall be present when the V/I-SMF receives the ECN Marking or Congestion Monitoring Reporting Status, e.g. during an PDU Session Modification procedure.
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.
pduSetSupportIndbooleanC0..1This IE shall be included when the V/I-SMF receives the PDU Set based Handling Indicator from NG-RAN, e.g. during an PDU Session Modification procedure.
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: the PDU Set based handling is not supported.
NOTE:
An SMF complying with this version of the specification should report secondary RAT usage using the secondaryRatUsageInfo attribute that replaces the secondaryRatUsageReport attribute.
Up
6.1.6.2.17  Type: StatusNotification  p. 223
Attribute name Data type P Cardi­nality Description Applica­bility
statusInfoStatusInfoM1This IE shall contain status information about the PDU session.
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
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.
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
newSmfIdNfInstanceIdC0..1 This IE may be present if the resourceStatus attribute in statusInfo is set to "UPDATED" and the cause IE in statusInfo is set to "CHANGED_ANCHOR_SMF". When present, it shall include the NF instance identifier of the new H-SMF or SMF (for a PDU session with an I-SMF) handling the PDU session, when it is changed within an SMF set. ES3XX
epsPdnCnxInfoEpsPdnCnxInfoC0..1This IE shall be present when the EPS PDN Connection Context Information of the PDU session is changed, e.g. due to change of anchor SMF.
When present, this IE shall include the EPS PDN Connection Context Information of the PDU session on the new anchor SMF. 		ES3XX
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_ANCHOR_SMF".
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.
intraPlmnApiRootUriC0..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_ANCHOR_SMF".
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.
Up

Up   Top   ToC