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.27 Type: SmContextRetrievedData  6.1.6.2.28 Type: TunnelInfo  6.1.6.2.29 Type: StatusInfo  6.1.6.2.30 Type: VsmfUpdateError  6.1.6.2.31 Type: EpsPdnCnxInfo  6.1.6.2.32 Type: EpsBearerInfo  6.1.6.2.33 Type: PduSessionNotifyItem  6.1.6.2.34 Type: EbiArpMapping  6.1.6.2.35 Type: SmContextCreateError  6.1.6.2.36 Type: SmContextUpdateError  6.1.6.2.37 Type: PduSessionCreateError  6.1.6.2.38 Type: MmeCapabilities  6.1.6.2.39 Type: SmContext 
...

 

6.1.6.2.27  Type: SmContextRetrievedData  p. 230
Attribute name Data type P Cardi­nality Description Applica­bility
ueEpsPdnConnectionEpsPdnCnxContainerM1This IE shall contain an MME/SGSN UE EPS PDN Connection including the mapped EPS bearer context(s), if the SM context type was not present in the request or if it was present and indicated a request to retrieve the UE EPS PDN Connection.
This IE shall be set to an empty string if the SM context type was present in the request and indicated a request to retrieve the complete SM context or the AF Coordination Information.
smContextSmContextC0..1This IE shall be present if the SM context type was present in the request and indicated a request to retrieve the complete SM context. DTSSA
smallDataRateStatusSmallDataRateStatusC0..1 This IE shall be present during N26 based Interworking Procedures, if in the request the smContextType is set to "EPS_PDN_CONNECTION" and if the status is available (see clauses 4.11.1.1 and 4.11.1.3.2 in TS 23.502).
When present, it shall indicate the small data rate control status for the PDU session.		CIOT
apnRateStatusApnRateStatusC0..1 This IE shall be present during N26 based Interworking Procedures, if in the request the smContextType is set to "EPS_PDN_CONNECTION" and if the status is available (see clauses 4.11.1.1 and 4.11.1.3.2 in TS 23.502).
When present, it shall indicate the APN rate control status for the PDN connection (APN rates are shared by all PDN connections of the UE to this APN).		CIOT
dlDataWaitingIndbooleanC0..1This IE shall be present, if the SM context type was not present in the request or if it was present and indicated a request to retrieve the UE EPS PDN Connection, and if downlink data buffered in the SMF/UPF needs to be forwarded to EPS (see clause 4.11.1.3.2A of TS 23.502).
When present, it shall be set as follows:
  • true: DL data needs to be sent to the UE;
  • false (default): no DL data needs to be sent to the UE.
CIOT
afCoordinationInfoAfCoordinationInfoC0..1This IE shall be present if the SM context type was present in the request and indicated a request to retrieve the AF Coordination Information.EnEDGE
Up
6.1.6.2.28  Type: TunnelInfo  p. 231
Attribute name Data type P Cardi­nality Description Applica­bility
ipv4AddrIpv4AddrC0..1When present, this IE shall contain the GTP tunnel IPv4 address.
At least one of the ipv4Addr or ipv6Addr shall be present. Both may be present.
ipv6AddrIpv6AddrC0..1When present, this IE shall contain the GTP tunnel IPv6 address.
At least one of the ipv4Addr or ipv6Addr shall be present. Both may be present.
gtpTeidTeidM1This IE shall contain the 4-octet GTP tunnel endpoint identifier.
If both ipv4Addr and ipv6Addr are present, the TEID shall be shared by both addresses.
anTypeAccessTypeC0..1This IE shall be present over N16a/N16 in MA PDU session scenarios, to indicate the access type associated to the N9 tunnel.MAPDU
Up
6.1.6.2.29  Type: StatusInfo  p. 231
Attribute name Data type P Cardi­nality Description Applica­bility
resourceStatusResourceStatusM1This IE shall indicate the status of the SM context or PDU session resource.
causeCauseO0..1When present, this IE shall indicate the cause for the resource status change.
remoteErrorbooleanO0..1This IE may be present in the SM context Status Notification sent from the V-SMF or I-SMF to the AMF.
When present, this IE shall indicate whether the cause indicated in the cause IE is originated by the remote entity or by the entity sending the message, as follows:
  • true: the error is originated by the remote entity (i.e. H-SMF or SMF for a PDU session with an I-SMF).
  • false: the error is originated by the entity sending the message (i.e. V-SMF/I-SMF).
This IE shall be present and set to true for a HR PDU session, or for a PDU session with an I-SMF, when the cause indicated in the cause IE is originated by the remote entity.
cnAssistedRanParaCnAssistedRanParaC0..1 This attribute shall be present when the cause value is "CN_ASSISTED_RAN_PARAMETER_TUNING".
When present, this IE shall include the SMF derived CN assisted RAN parameters tuning. 		CARPT
anTypeAccessTypeC0..1This IE shall indicate the access type of PDU session.HOFAIL
Up
6.1.6.2.30  Type: VsmfUpdateError  p. 232
Attribute name Data type P Cardi­nality Description Applica­bility
errorExtProblemDetailsM1 More information on the error shall be provided in the "cause" attribute of the "ProblemDetails" structure.
ptiProcedureTransactionIdC0..1This IE shall be present if available. When present, it shall contain the PTI value received from the UE.
n1smCausestringC0..1This IE shall be present if available.
When present, it shall contain the 5GSM cause received from 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.
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).
failedToAssignEbiListarray(Arp)C1..NThis IE shall be present if the AMF failed to assign the requested EBIs.
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.
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.
recoveryTimeDateTimeO0..1Timestamp (in UTC) when the V-SMF or I-SMF service instance was (re)started (see clause 6.3 of TS 23.527).
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
retryAfterUintegerO0..1This IE may be included if received from the AMF within an error response, e.g., during N1N2MessageTransfer service operation when UE is not responding to paging.
When present, this IE indicates the period in number of seconds. The NF consumer, i.e. the (H-)SMF, should not send new update request to the V-SMF/I-SMF during the indicated period.
NOTE:
This IE is sent as a separate IE rather than within the n1SmInfoFromUE 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 Command Reject message.
Up
6.1.6.2.31  Type: EpsPdnCnxInfo  p. 234
Attribute name Data type P Cardi­nality Description
pgwS8cFteidBytesM1Base64-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).
pgwNodeNameBytesC0..1Base64-encoded characters, encoding the PGW FQDN IE as specified in Figure 8.66-1 of TS 29.274 (starting from octet 1). It shall be present, if it is available
pgwChangeInfoBytesO0..1Base64-encoded characters, encoding the PGW Change Info IE as specified in Table 8.145-1 of TS 29.274 (starting from octet 1). See clause 31.5 of TS 23.007.
linkedBearerIdEpsBearerIdC0..1An implementation complying with this version of the specification shall include this attribute and set it to the default bearer ID associated with the PDU session moved to EPS.
Up
6.1.6.2.32  Type: EpsBearerInfo  p. 234
Attribute name Data type P Cardi­nality Description
ebiEpsBearerIdM1EPS Bearer ID
pgwS8uFteidBytesM1Base64-encoded characters, encoding the PGW S8 F-TEID for User Plane as specified in Figure 8.22-1 of TS 29.274 (starting from octet 1).
bearerLevelQoSBytesM1Base64-encoded characters, encoding the Bearer QoS IE as specified in Figure 8.15-1 of TS 29.274 (starting from octet 1).
Up
6.1.6.2.33  Type: PduSessionNotifyItem  p. 234
Attribute name Data type P Cardi­nality Description
notificationCauseNotificationCauseM1
6.1.6.2.34  Type: EbiArpMapping  p. 235
Attribute name Data type P Cardi­nality Description
epsBearerIdEpsBearerIdM1This IE shall contain the EPS bearer identities.
arpArpM1This IE shall contain the ARP corresponding to the EBI.
Up
6.1.6.2.35  Type: SmContextCreateError  p. 235
Attribute name Data type P Cardi­nality Description
errorExtProblemDetailsM1 More information on the error shall be provided in the "cause" attribute of the "ProblemDetails" structure.
n1SmMsgRefToBinaryDataC0..1This IE shall be present, if an N1 SM information is received in the request and the SMF is able to return N1 SM information to the UE.
When present, it 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 returned to the NG-RAN during Xn based handover procedure with I-SMF/V-SMF insertion, change or removal.
When present, it shall reference the N2 SM Message 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.
recoveryTimeDateTimeO0..1Timestamp (in UTC) when the SMF service instance was (re)started (see clause 6.3 of TS 23.527).
Up
6.1.6.2.36  Type: SmContextUpdateError  p. 236
Attribute name Data type P Cardi­nality Description
errorExtProblemDetailsM1 More information on the error shall be provided in the "cause" attribute of the "ProblemDetails" structure.
n1SmMsgRefToBinaryDataC0..1This IE shall be present, if N1 SM Information needs to be returned to the UE.
When present, it 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 returned to the NG-RAN.
When present, it shall reference the N2 SM Message 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.
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 and 5.2.2.3.16.
recoveryTimeDateTimeO0..1Timestamp (in UTC) when the SMF service instance was (re)started (see clause 6.3 of TS 23.527).
Up
6.1.6.2.37  Type: PduSessionCreateError  p. 237
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.
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". (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..1When present, this IE shall contain the timestamp (in UTC) of the event 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 may 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 Establishment Reject message.
Up
6.1.6.2.38  Type: MmeCapabilities  p. 238
Attribute name Data type P Cardi­nality Description
nonIpSupportedbooleanC0..1This IE shall be present if non-IP PDN type is supported. It may be present otherwise. When present, this IE shall be set as follows:
  • true: non-IP PDN type is supported;
  • false (default): non-IP PDN type is not supported.
ethernetSupportedbooleanC0..1This IE shall be present if Ethernet PDN type is supported. It may be present otherwise. When present, this IE shall be set as follows:
  • true: Ethernet PDN type is supported;
  • false (default): Ethernet PDN type is not supported.
upipSupportedbooleanC0..1This IE shall be present if the MME supports User Plane Integrity Protection with EPS. 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.
NOTE:
The AMF should know the MME capability to support, or not, non-IP PDN type, Ethernet PDN type and User Plane Integrity Protection, through local configuration. Note however that the actual EPS support of User Plane Integrity Protection may depend on the target E-UTRAN coverage.
Up
6.1.6.2.39  Type: SmContext |R16|  p. 239
Attribute name Data type P Cardi­nality Description Applica­bility
pduSessionIdPduSessionIdM1This IE shall contain the PDU Session ID.
dnnDnnM1This IE shall contain the UE requested DNN of the PDU session.
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.
sNssaiSnssaiM1This IE shall contain the S-NSSAI for the serving PLMN.
altSnssaiSnssaiC0..1This IE shall be present if the network slice for the serving PLMN (as indicated in the sNssai IE) was replaced by an alternative S-NSSAI.
When present, this IE shall indicate the alternative S-NSSAI for the serving PLMN.
See clause 5.15.19 of TS 23.501.		NSRP
hplmnSnssaiSnssaiC0..1This IE shall be present for a HR PDU session.
When present, it shall contain the S-NSSAI for the HPLMN.
altHplmnSnssaiSnssaiC0..1This IE shall be present if the network slice for the HPLMN (as indicated in the hplmnSnssai IE) was replaced by an alternative S-NSSAI for the HPLMN.
When present, this IE shall indicate the alternative S-NSSAI for the HPLMN.
See clause 5.15.19 of TS 23.501.		NSRP
pduSessionTypePduSessionTypeM1This IE shall indicate the PDU session type.
gpsiGpsiC0..1This IE shall be present if it is available. When present, it shall contain the user's GPSI.
hSmfUriUriC0..1This IE shall be present in HR roaming scenarios. When present, it shall contain the API URI of the Nsmf_PDUSession service of the H-SMF. The API URI shall be formatted as specified in clause 6.1.1.
smfUriUriC0..1This IE shall be present for a PDU session with an I-SMF. When present, it shall contain the API URI of the Nsmf_PDUSession service of the SMF. The API URI shall be formatted as specified in clause 6.1.1.
pduSessionRefUriC0..1This IE shall be present for a HR PDU session or a PDU session with an I-SMF.
When present, this IE shall include the absolute URI of the PDU Session in H-SMF or SMF, including apiRoot (see clause 6.1.3.6.2)
interPlmnApiRootUriC0..1This IE shall be present, if available.
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 2)
intraPlmnApiRootUriC0..1This IE shall be present, if available.
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 2)
pcfIdNfInstanceIdO0..1When present, this IE shall contain the identifier of:
  • the H-PCF selected by the AMF (for UE Policy), for a HR PDU session; or
  • the V-PCF selected by the AMF (for Access and Mobility Policy), for a PDU session in LBO roaming scenarios; or
  • the PCF selected by the AMF (for Access and Mobility Policy and/or UE Policy), for a PDU session in non-roaming scenarios.
pcfGroupIdNfGroupIdO0..1This IE may be present in non-roaming and HR roaming scenarios.
When present, this IE shall contain the identity of the (home) PCF group serving the UE for Access and Mobility Policy and/or UE Policy.
pcfSetIdNfSetIdO0..1This IE may be present if the pcfId IE is present.
When present, it shall contain the NF Set ID of the PCF indicated by the pcfId IE.
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 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.
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 1)
sessionAmbrAmbrM1This IE shall contain the Session AMBR granted to the PDU session.
qosFlowsListarray(QosFlowSetupItem)M1..NThis IE shall contain the set of QoS flow(s) established for the PDU session. It shall contain at least the Qos flow associated to the default Qos rule.
The qosRules attribute of each QosFlowSetupItem shall be set to an empty string.
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.
pduSessionSmfSetIdNfSetIdC0..1This IE shall be present, if available.
When present, this IE shall contain the NF Set ID of the home SMF as identified by hSmfInstanceId, or the SMF as identified by the smfInstanceId.
pduSessionSmfServiceSetIdNfServicevSetIdC0..1This IE shall be present, if available.
When present, this IE shall contain the NF Service Set ID of the PDUSession service instance (for this PDU session) in the home SMF or the SMF.
pduSessionSmfBindingSbiBindingLevelC0..1This IE shall be present, if available.
When present, this IE shall contain the SBI binding level of the PDU session resource in the home SMF or the SMF.
enablePauseChargingbooleanC0..1This IE shall be present for a HR PDU session, if available.
When present, it shall indicate whether the use of Pause of Charging is enabled 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 a UE IPv4 address to the PDU session.
ueIpv6PrefixIpv6PrefixC0..1This IE shall be present if a UE IPv6 prefix to the PDU session.
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.
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.
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.
alwaysOnGrantedbooleanC0..1This IE shall be present if available. When present, it shall indicate whether this is an always On PDU session and it shall be set as follows:
  • true: always-on PDU session granted.
  • false (default): always-on PDU session not granted.
upSecurityUpSecurityO0..1When present, this IE shall indicate the security policy for integrity protection and encryption for the user plane of the PDU session.
hSmfServiceInstanceIdstringO0..1This IE may be present for a HR PDU session.
When present, this IE shall contain the serviceInstanceId of the H-SMF service instance serving the 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..1This IE may be present for a PDU session with an I-SMF.
When present, this IE shall contain the serviceInstanceId of the SMF service instance serving the PDU session.
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).
recoveryTimeDateTimeO0..1This IE may be present if available.
When present, this IE shall indicate the timestamp (in UTC) when the H-SMF or SMF service instance serving the PDU session was (re)started (see clause 6.3 of TS 23.527).
forwardingIndbooleanC0..1This IE shall be present, when downlink data packets are buffered at I-UPF. The SMF or I-SMF shall use this IE to inform the NF service consumer that a forwarding tunnel is needed for receiving the buffered downlink data packets, as specified in clause 4.23.4 of TS 23.502.
When present, this IE shall be set as follows:
  • true: a forwarding tunnel is needed for sending buffered downlink data packets;
  • false (default): forwarding tunnel is not needed
psaTunnelInfoTunnelInfoC0..1This IE shall be present if available.
When present, this IE shall contain the N9 tunnel information of PDU Session Anchor UPF controlled by SMF or H-SMF.
chargingIdstringC0..1This IE shall be present for a HR PDU session, in scenarios with a V-SMF insertion/change/removal.
When present, it shall contain the Charging ID of the PDU session (see 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..1This IE shall be present if available for a HR PDU session, in scenarios with a V-SMF insertion/change/removal.
When present, it shall contain the String based Charging ID of the PDU session (see TS 32.255).		SCID
chargingInfoChargingInformationC0..1This IE shall be present for a HR PDU session, if available and if the NF Service Consumer requesting the SM Context pertains to the same PLMN (i.e. if the Retrieve SM Context Request does not contain the servingNetwork attribute set to a different PLMN ID).
When present, it shall contain the addresses of the V-CHF used for the PDU session.
roamingChargingProfileRoamingChargingProfileC0..1This IE shall be present for a HR PDU session, if available and if the NF Service Consumer requesting the SM Context pertains to the same PLMN (i.e. if the Retrieve SM Context Request does not contain the servingNetwork attribute set to a different PLMN ID).
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).
nefExtBufSupportIndbooleanC0..1 This IE shall be present with value "true", if the anchor NEF has indicated support of Extended Buffering for mobile terminated data during SMF-NEF connection establishment.
When present, this IE shall be set as following:
  • true: Extended Buffering supported by NEF
  • false (default): Extended Buffering not supported by NEF
ipv6IndexIpIndexC0..1This IE shall be present during I-SMF change scenarios, if IPv6 Index has previously been received by old I-SMF.
dnAaaAddressIpAddressO0..1When present, this IE shall contain the address of DN-AAA server for UE IP Address allocation previously received by old I-SMF.
redundantPduSessionInfoRedundantPduSessionInformationC0..1This IE shall be present for a PDU session with an I-SMF, if this information has been received previously from the UE, the anchor SMF or the old I-SMF.
ranTunnelInfoQosFlowTunnelC0..1 This IE shall be present if the ranUnchangedInd IE is set to "true" in the SM context retrieve request.
When present, this IE shall contain the N2 tunnel information of NG-RAN with associated QoS flows (see "DL QoS Flow per TNL Information" in clause 9.3.4.2 of TS 38.413).
addRanTunnelInfoarray(QosFlowTunnel)C1..N This IE shall be present if the ranUnchangedInd IE is set to "true" in the SM context retrieve request.
When present, this IE shall contain the additional N2 tunnel information of NG-RAN together with associated QoS flows for split PDU session (see "Additional DL QoS Flow per TNL Information" in clause 9.3.4.2 of TS 38.413).
redRanTunnelInfoQosFlowTunnelC0..1 This IE shall be present if the ranUnchangedInd IE is set to "true" in the SM context retrieve request.
When present, this IE shall contain the additional N2 tunnel information of NG-RAN together with associated QoS flows for Redundant QoS Flow(s) (see "Redundant DL QoS Flow per TNL Information" in clause 9.3.4.2 of TS 38.413).
addRedRanTunnelInfoarray(QosFlowTunnel)C1..N This IE shall be present if the ranUnchangedInd IE is set to "true" in the SM context retrieve request.
When present, this IE shall contain the additional N2 tunnel information of NG-RAN together with associated QoS flows for Redundant QoS Flow(s) with split PDU session (see "Additional Redundant DL QoS Flow per TNL Information" in clause 9.3.4.2 of TS 38.413).
nspuSupportIndbooleanC0..1 This IE shall be present and set to "true" if the enablePauseCharging in the SmContext data type 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.
smfBindingInfostringC0..1This IE shall be present, if available.
When present, this IE shall contain the Binding indications of the PDU session resource in the home SMF or the SMF and shall be set to the value of the 3gpp-Sbi-Binding header defined in clause 5.2.3.2.6 of TS 29.500, without the header name.
satelliteBackhaulCatSatelliteBackhaulCategoryO0..1When present, this IE shall indicate the satellite backhaul category information last signalled towards the anchor SMF, if any.
sscModestringC0..1This IE shall be present, if available.
When present, this IE shall indicate the SSC mode applicable to the PDU session.
When present, it shall be encoded as one character in hexadecimal representation, taking a value of "0" to "7", representing the 3 bits of the SSC mode value of the SSC mode IE specified in clause 9.11.4.16 of TS 24.501.
Pattern: "^[0-7]$"
Example: SSC mode 3 shall be encoded as "3".
dlsetSupportIndbooleanC0..1 This IE shall be present and set to "true" if the (H-)SMF supports the "DLSET" feature as specified in clause 6.1.8.
When present, it shall be set as follows:
  • true: the (H-)SMF supports the "DLSET" feature.
  • false: the (H-)SMF does not support the "DLSET" feature
n9fscSupportIndbooleanC0..1 This IE shall be present and set to "true" if the SMF supports the "N9FSC" feature as specified in clause 6.1.8.
When present, it shall be set as follows:
  • true: "N9FSC" feature is supported.
anchorSmfOauth2RequiredbooleanO0..1This IE may be present when the NF consumer (i.e. new I-SMF or new V-SMF) and the NF producer (i.e. the old I-SMF, V-SMF or SMF) belong to the same PLMN.
When present, this IE shall indicate whether the H-SMF or SMF for a PDU session with an I-SMF requires Oauth2-based authorization for accessing its Nsmf_PDUSession service.
  • true: OAuth2 based authorization is required.
  • false: OAuth2 based authorization is not required.
The absence of this IE means that no indication is available about the usage of Oauth2 for authorization of the anchor SMF's Nsmf_PDUSession service. (NOTE 3)
fullDnaiListarray(Dnai)O1..NThis IE may be present to contain the full list of DNAIs of interest for PDU session, including DNAIs that may not be supported by the (source) I-SMF and excluding the ones supported by the Anchor SMF.DTSSA-Ext1
hrsboAuthResultbooleanC0..1This IE shall be present for a HR PDU session, during a V-SMF change within the same PLMN (i.e. if the Retrieve SM Context Request does not contain the servingNetwork attribute set to a different PLMN ID), if HR-SBO was authorized by the H-SMF and the request indicates that the new V-SMF supports HR-SBO.
When present, it shall Indicate whether HR-SBO request is authorized
  • true: authorized.
  • false: Not authorized.
HR-SBO
hDnsAddrIpAddressC0..1This IE shall be present for a HR PDU session, during a V-SMF change within the same PLMN (i.e. if the Retrieve SM Context Request does not contain the servingNetwork attribute set to a different PLMN ID), if available, HR-SBO was authorized by the H-SMF and the request indicates that the new V-SMF supports HR-SBO.
When present, this IE shall contain the DNS server address of HPLMN. 		HR-SBO
hPlmnAddrIpAddressC0..1This IE shall be present for a HR PDU session, during a V-SMF change within the same PLMN (i.e. if the Retrieve SM Context Request does not contain the servingNetwork attribute set to a different PLMN ID), if available, HR-SBO was authorized by the H-SMF and the request indicates that the new V-SMF supports HR-SBO.
When present, this IE shall contain the HPLMN address information (e.g. H-UPF IP address on N6). The new V-SMF may configure the new V-EASDF to build EDNS Client Subnet option based on this HPLMN address information for target FQDN of DNS queries which are not authorized for HR-SBO. 		HR-SBO
vplmnOffloadingInfoListarray(VplmnOffloadingInfo)C1..NThis IE shall be present for a HR PDU session, during a V-SMF change within the same PLMN (i.e. if the Retrieve SM Context Request does not contain the servingNetwork attribute set to a different PLMN ID), if available, HR-SBO was authorized by the H-SMF and the request indicates that the new V-SMF supports HR-SBO.
When present, it shall contain the list of V-PLMN Offloading policies that apply to the PDU session and whose offload identifiers are not yet known by the target V-SMF.
(NOTE 5) 		HR-SBO
offloadIdsarray(OffloadIdentifier)C1...NThis IE shall be present for a HR PDU session, during a V-SMF change within the same PLMN (i.e. if the Retrieve SM Context Request does not contain the servingNetwork attribute set to a different PLMN ID), if available, HR-SBO was authorized by the H-SMF and the request indicates that the new V-SMF supports HR-SBO, and if the offloadIds are part of the storedOffloadIds included in the the Retrieve SM Context Request.
When present, this IE shall contain a list of offload identifiers that apply to the PDU session and that are already known by the target V-SMF. (NOTE 5)		HR-SBO
easInfoToRefreshEasInfoToRefreshC0..1This IE shall be present for a HR PDU session, during a V-SMF change within the same PLMN (i.e. if the Retrieve SM Context Request does not contain the servingNetwork attribute set to a different PLMN ID), if available, HR-SBO was authorized by the H-SMF and the request indicates that the new V-SMF supports HR-SBO.
When present, it shall contain the EAS information to be refreshed for EAS re-discovery.		HR-SBO
targetDnaiDnaiC0..1This IE shall be present, for a HR PDU session, if it is received from H-SMF in AF triggered EAS re-discovery and edge relocation via interacting with HPLMN (see clause 6.7.3.2 of TS 23.548).
When present, this IE shall contain the target DNAI.		HR-SBO
trafficInfluInfoTrafficInfluenceInfoC0..1This IE shall be present for a HR PDU session, during a V-SMF change within the same PLMN (i.e. if the Retrieve SM Context Request does not contain the servingNetwork attribute set to a different PLMN ID), if available, HR-SBO was authorized by the H-SMF and the request indicates that the new V-SMF supports HR-SBO. When present, it shall contain the traffic influence information applicable at the VPLMN for the HR-SBO PDU session.HR-SBO
pendingUpdateInfoListarray(PendingUpdateInfo)O1..NThis IE should be included by the old V-SMF/I-SMF if received from the (H-)SMF.
When 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:
If present, this attribute shall be used together with routingIndicator. This attribute is only used by the HPLMN in roaming scenarios.
NOTE 2:
See NOTE 7 of Table 6.1.6.2.10-1.
NOTE 3:
If the anchorSmfOauth2Required IE was received in SmContextCreateData from the AMF, this IE shall be ignored by the new I-SMF or V-SMF.
NOTE 4:
Usage of Charging ID with Uint32 value for roaming scenarios may lead to Charging ID collision between SMFs.
NOTE 5:
The same offloadId should not appear in both the vplmnOffloadingInfoList and offloadIds attributes. Both vplmnOffloadingInfoList and offloadIds attributes may be present when multiple offload identifers apply to the PDU session and some of them are already known by the target V-SMF while others are not yet known by the target V-SMF.
Up

Up   Top   ToC