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

Content for  TS 29.502  Word version:  18.5.0

Top   Top   Up   Prev   Next
1…   5…   5.2.2…   5.2.2.2.4…   5.2.2.3…   5.2.2.3.2…   5.2.2.3.3…   5.2.2.3.6…   5.2.2.3.8…   5.2.2.3.10…   5.2.2.3.17…   5.2.2.3.23…   5.2.2.4…   5.2.2.8…   5.2.2.8.2…   5.2.2.8.2.7…   5.2.2.8.2.12…   5.2.2.8.2.20…   5.2.2.8.3…   5.2.2.8.3.6…   5.2.2.9…   5.2.3…   6…   6.1.2…   6.1.3…   6.1.3.3…   6.1.3.5…   6.1.3.6…   6.1.3.7…   6.1.4…   6.1.6…   6.1.6.2…   6.1.6.2.5…   6.1.6.2.11…   6.1.6.2.18…   6.1.6.2.27…   6.1.6.2.40…   6.1.6.2.54…   6.1.6.2.65…   6.1.6.3…   6.1.6.4…   6.1.7…   A…   B…   C… 
6.1.6.2.40 Type: ExemptionInd  6.1.6.2.41 Type: PsaInformation  6.1.6.2.42 Type: DnaiInformation  6.1.6.2.43 Type: N4Information  6.1.6.2.44 Type: IndirectDataForwardingTunnelInfo  6.1.6.2.45 Type: SmContextReleasedData  6.1.6.2.46 Type: ReleasedData  6.1.6.2.47 Type: SendMoDataReqData  6.1.6.2.48 Type: CnAssistedRanPara  6.1.6.2.49 Type: UlclBpInformation  6.1.6.2.50 Type: TransferMoDataReqData  6.1.6.2.51 Type: TransferMtDataReqData  6.1.6.2.52 Type: TransferMtDataError  6.1.6.2.53 Type: TransferMtDataAddInfo 
...

 

6.1.6.2.40  Type: ExemptionInd |R16|  p. 243
The ExemptionInd indicates that the included NAS SM message was exempted from one or more NAS SM congestion control, e.g. DNN, and/or S-NSSAI based congestion control, activated in the AMF.
Attribute name Data type P Cardi­nality Description
dnnCongestionbooleanC0..1This IE shall be present and set to Yes if the included NAS Session Management message was exempted from the DNN based congestion activated in the AMF.
  • true: Yes
  • false (default): No
snssaiCongestionbooleanC0..1This IE shall be present and set to Yes if the included NAS Session Management message was exempted from the S-NSSAI only based congestion activated in the AMF.
  • true: Yes
  • false (default): No
snssaiDnnCongestionbooleanC0..1This IE shall be present and set to Yes if the included NAS Session Management message was exempted from the S-NSSAI and DNN based congestion activated in the AMF.
  • true: Yes
  • false (default): No
Up
6.1.6.2.41  Type: PsaInformation |R16|  p. 243
Attribute name Data type P Cardi­nality Description
psaIndPsaIndicationM1This IE shall indicate, for a PDU session with an I-SMF, if a PSA and UL CL or BP, or only a PSA is inserted or removed by the I-SMF.
dnaiListarray(Dnai)M1..NThis IE shall indicate the DNAI(s) supported by the PSA that is inserted or removed.
ueIpv6PrefixIpv6PrefixC0..1This IE shall be present if a PSA and UL CL or BP is inserted or removed, and IPv6 multi-homing applies to the PDU session.
psaUpfIdNfInstanceIdC0..1This IE shall be present if a PSA UPF is inserted by the I-SMF. When present, it shall contain the identifier of the PSA UPF.
Up
6.1.6.2.42  Type: DnaiInformation |R16|  p. 244
Attribute name Data type P Cardi­nality Description
dnaiDnaiM1
noDnaiChangeIndbooleanC0..1This IE shall be sent by the SMF to the I-SMF during the insertion of a PSA and BP/UL CL controlled by I-SMF.
When present, it shall be set as follows:
  • true: DNAI shall not be changed;
  • false: DNAI may be changed.
noLocalPsaChangeIndbooleanC0..1This IE shall be sent by the SMF to the I-SMF during the insertion of a PSA and BP/UL CL controlled by I-SMF.
When present, it shall be set as follows:
  • true: local PSA shall not be changed;
  • false: local PSA may be changed.
Up
6.1.6.2.43  Type: N4Information |R16|  p. 244
Attribute name Data type P Cardi­nality Description Applica­bility
n4MessageTypeN4MessageTypeM1This IE shall indicate the PFCP message signalled in the n4MessagePayload.
n4MessagePayloadRefToBinaryDataM1This IE shall reference the N4 Message Payload binary data (for the n4Info attribute) or the N4 Information extension binary data (for the n4InfoExt1, n4InfoExt2 and n4InfoExt3 attributes), see clause 6.1.6.4.5.
n4DnaiInfoDnaiInformationC0..1This IE shall be present if the N4 information relates to a PSA. When present, it shall indicate the DNAI related to the N4 Information. If this IE is not present, this indicates N4 information relates to an UL CL or BP.
psaUpfIdNfInstanceIdO0..1This IE may be sent by SMF to I-SMF if multiple local PSAs are inserted for the PDU session. When present, it shall contain the identifier of the PSA UPF for which the N4 information applies.
ulClBpIdNfInstanceIdO0..1When present, it shall contain the identifier of the UL CL/BP for which the N4 information applies.
n9UlPdrIdListarray(Uint16)C1..N This IE shall be sent by the anchor SMF to the (new) I-SMF 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, if EAS session continuity upon UL CL relocation is required.
When present, it shall contain the list of Rule IDs of the UL PDR(s) included in the N4Information to establish the UL N9 data forwarding in the target Branching Point or UL CL towards the old Branching Point or UL CL.		N9FSC
Up
6.1.6.2.44  Type: IndirectDataForwardingTunnelInfo |R16|  p. 245
Attribute name Data type P Cardi­nality Description
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.
drbIdDrbIdC0..1This IE shall be present if this is an indirect data forwarding tunnel for a specific Data Radio Bearer (see clause 9.3.1.77 of TS 38.413).
This IE shall not present if the additionalTnlNb IE is present. (NOTE)
additionalTnlNbAdditionalTnlNbC0..1This IE shall be present if this is an additional indirect data forwarding tunnel for multi-connectivity.
When present, it shall be set to the value 1 to 3 to indicate whether this is the first, second or third additional indirect data forwarding tunnel for multi-connectivity.
This IE shall not present if the drbId IE is present. (NOTE)
NOTE:
If neither the drbId IE nor the additionalTnlNb IE is present, the tunnel information shall correspond to the PDU session level indirect data forwarding tunnel (i.e. DL Forwarding UP TNL Information IE or UL Forwarding UP TNL Information IE of the Handover Request Acknowledge Transfer IE of clause 9.3.4.11 of TS 38.413).
Up
6.1.6.2.45  Type: SmContextReleasedData |R16|  p. 245
Attribute name Data type P Cardi­nality Description Applica­bility
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
Up
6.1.6.2.46  Type: ReleasedData |R16|  p. 246
Attribute name Data type P Cardi­nality Description Applica­bility
smallDataRateStatusSmallDataRateStatusC0..1This IE shall be present, if the NF Service Consumer has indicated support of CIoT and if 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
n4InfoN4InformationO0..1This IE may be present if the SMF needs to send N4 information (e.g. acknowledgement of traffic usage reporting) to the I-SMF for traffic offloaded at a PSA controlled by an I-SMF. DTSSA
n4InfoExt1N4InformationO0..1This IE may be present if the SMF needs to send additional N4 information (e.g. acknowledgement of traffic usage reporting) to the I-SMF for traffic offloaded at a PSA controlled by an I-SMF. DTSSA
n4InfoExt2N4InformationO0..1This IE may be present if the SMF needs to send additional N4 information (e.g. acknowledgement of traffic usage reporting) to the I-SMF for traffic offloaded at a PSA controlled by an I-SMF. DTSSA
Up
6.1.6.2.47  Type: SendMoDataReqData |R16|  p. 246
Attribute name Data type P Cardi­nality Description Applica­bility
moDataRefToBinaryDataM1This IE shall reference the mobile originated data (see clause 6.1.6.4.6).CIOT
moExpDataCounterMoExpDataCounterC0..1 This IE shall be included if the UE has accessed the network by using "MO exception data" RRC establishment cause and when the AMF decides to send a non-zero value to the SMF. (NOTE)
When present, this IE shall contain the MO Exception Data Counter.		CIOT
ueLocationUserLocationO0..1When present, this IE shall contain the user location.CIOT
NOTE:
The AMF increments the MO Exception Data Counter when the UE establishes/resumes RRC with "MO Exception Data" RRC cause. The AMF may defer sending the moExpDataCounter attribute to the SMF based on local configuration. The AMF resets the MO Exception Data Counter when receiving successful response from the SMF. The SMF however keeps incrementing the counter locally.
Up
6.1.6.2.48  Type: CnAssistedRanPara |R16|  p. 247
Attribute name Data type P Cardi­nality Description
stationaryIndicationStationaryIndicationO0..1Identifies whether the UE is stationary or mobile (see clause 4.15.6.3 of TS 23.502).
communicationDurationTimeDurationSecO0..1Indicates for how long the UE will normally stay in CM-Connected for data transmission (see clause 4.15.6.3 of TS 23.502).
periodicTimeDurationSecO0..1Identifies interval time of periodic communication (see clause 4.15.6.3 of TS 23.502).
scheduledCommunicationTimeScheduledCommunicationTimeO0..1Identifies time and day of the week when the UE is available for communication (see clause 4.15.6.3 of TS 23.502).
scheduledCommunicationTypeScheduledCommunicationTypeO0..1Indicates that the Scheduled Communication Type (see clause 4.15.6.3 of TS 23.502). (NOTE 2)
trafficProfileTrafficProfileO0..1Identifies the type of data transmission: single packet transmission (UL or DL), dual packet transmission (UL with subsequent DL or DL with subsequent UL), and multiple packets transmission (see clause 4.15.6.3 of TS 23.502).
batteryIndicationBatteryIndicationO0..1Indicates the power consumption type(s) of the UE (see clause 4.15.6.3 of TS 23.502).
NOTE 1:
At least one of optional parameters above shall be present.
NOTE 2:
The value of attribute "scheduledCommunicationType" shall be used together with the value of "scheduledCommunicationTime".
Up
6.1.6.2.49  Type: UlclBpInformation |R16|  p. 247
Attribute name Data type P Cardi­nality Description
ulclBpUpfIdNfInstanceIdC0..1This IE shall be present if an UL CL or BP UPF separate from the local PSA is inserted by the I-SMF. When present, it shall contain the identifier of the UL CL or BP UPF.
Up
6.1.6.2.50  Type: TransferMoDataReqData |R16|  p. 247
Attribute name Data type P Cardi­nality Description Applica­bility
moDataRefToBinaryDataM1This IE shall reference the mobile originated data (see clause 6.1.6.4.6).CIOT
moExpDataCounterMoExpDataCounterC0..1This IE shall be present if received from AMF.
When present, this IE shall contain the MO Exception Data Counter.		CIOT
ueLocationUserLocationO0..1When present, this IE shall contain the user location.CIOT
Up
6.1.6.2.51  Type: TransferMtDataReqData |R16|  p. 248
Attribute name Data type P Cardi­nality Description Applica­bility
mtDataRefToBinaryDataM1This IE shall reference the mobile terminated data (see clause 6.1.6.4.7).CIOT
Up
6.1.6.2.52  Type: TransferMtDataError |R16|  p. 248
Data type Cardinality Description Applicability
ExtProblemDetails1Detail information of the problem
TransferMtDataAddInfo1Additional information to be returned in error response.
Up
6.1.6.2.53  Type: TransferMtDataAddInfo |R16|  p. 248
Attribute name Data type P Cardi­nality Description Applica­bility
maxWaitingTimeDurationSecC0..1This IE shall be present if available.
When present, this IE shall contain the estimated maximum wait time (see clause 4.25.5 of TS 23.502).		CIOT
Up

Up   Top   ToC