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 38.331  Word version:  18.2.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.2.2.4…   5.3…   5.3.3…   5.3.5…   5.3.5.5…   5.3.5.6…   5.3.5.7…   5.3.5.13…   5.3.5.17…   5.3.6…   5.3.8…   5.3.13…   5.3.14…   5.4…   5.5…   5.5.3…   5.5.4…   5.5.4.15…   5.5.4.23…   5.5.5…   5.5a…   5.7…   5.7.4…   5.7.8…   5.7.12…   5.8…   5.8.9…   5.8.9.2…   5.8.9.8…   5.8.10…   5.8.11…   5.9…   5.10…   6…   6.2.2…   6-2-2-23…   6-2-2-27…   6-2-2-43…   6-2-2-47…   6.3…   6.3.2…   6-3-2-27…   6-3-2-49…   6-3-2-73…   6-3-2-95…   6-3-2-108…   6-3-2-134…   6-3-2-162…   6-3-2-188…   6-3-2-213…   6-3-2-243…   6-3-2-271…   6-3-2-297…   6-3-2-341…   6.3.3…   6-3-3-25…   6-3-3-51…   6.3.4…   6.3.5…   6-3-5-25…   6.3.6…   6.4…   7…   9…   11…   A…   A.4…   B… 
5.7.4 UE Assistance Information  5.7.4.1 General  5.7.4.2 Initiation  5.7.4.3 Actions related to transmission of UEAssistanceInformation message  5.7.4.3a Setting the contents of OverheatingAssistance IE  5.7.4.4 Relaxed measurement criterion for a stationary (e)RedCap UE  5.7.5 Failure information  5.7.5.1 General  5.7.5.2 Initiation  5.7.5.3 Actions related to transmission of FailureInformation message  5.7.6 DL message segment transfer  5.7.6.1 General  5.7.6.2 Initiation  5.7.6.3 Reception of DLDedicatedMessageSegment by the UE  5.7.7 UL message segment transfer  5.7.7.1 General  5.7.7.2 Initiation  5.7.7.3 Actions related to transmission of ULDedicatedMessageSegment message 
...

 

5.7.4  UE Assistance Information  p. 313

5.7.4.1  General  p. 313

Reproduction of 3GPP TS 38.331, Fig. 5.7.4.1-1: UE Assistance Information
Figure 5.7.4.1-1: UE Assistance Information
Up
The purpose of this procedure is for the UE to inform the network of:
  • its delay budget report carrying desired increment/decrement in the connected mode DRX cycle length, or;
  • its overheating assistance information, or;
  • its IDC assistance information, or;
  • its preference on DRX parameters for power saving, or;
  • its preference on the maximum aggregated bandwidth for power saving, or;
  • its preference on the maximum number of secondary component carriers for power saving, or;
  • its preference on the maximum number of MIMO layers for power saving, or;
  • its preference on the minimum scheduling offset for cross-slot scheduling for power saving, or;
  • its preference on the RRC state, or;
  • configured grant assistance information for NR sidelink communication, or;
  • its preference in being provisioned with reference time information, or;
  • its preference for FR2 UL gap, or;
  • its preference to transition out of RRC_CONNECTED state for MUSIM operation, or;
  • its preference on the MUSIM gaps, or;
  • its preference on the MUSIM gap priority, or;
  • its preference on the MUSIM temporary capability restriction, or;
  • its relaxation state for RLM measurements, or;
  • its relaxation state for BFD measurements, or;
  • availability of data and/or signalling mapped to radio bearers which are not configured for SDT, or;
  • its preference for the SCG to be deactivated, or;
  • availability of uplink data to transmit for a DRB for which there is no MCG RLC bearer while the SCG is deactivated, or;
  • change of its fulfilment status for RRM measurement relaxation criterion, or;
  • service link (specified in TS 38.300) propagation delay difference between serving cell and neighbour cell(s); or
  • its preference on multi-Rx operation for FR2; or
  • availability of flight path information for Aerial UE operation; or
  • UL traffic information, or;
  • the information of the relay UE(s) with which it connects via a non-3GPP connection for MP, or;
  • configured grant assistance information for NR sidelink positioning.
Up

5.7.4.2  Initiation  p. 314

A UE capable of providing delay budget report in RRC_CONNECTED may initiate the procedure in several cases, including upon being configured to provide delay budget report and upon change of delay budget preference.
A UE capable of providing overheating assistance information in RRC_CONNECTED may initiate the procedure if it was configured to do so, upon detecting internal overheating, or upon detecting that it is no longer experiencing an overheating condition.
A UE capable of providing IDC assistance information in RRC_CONNECTED may initiate the procedure if it was configured to do so, upon detecting IDC problem if the UE did not transmit an IDC assistance information since it was configured to provide IDC indications, or upon change of IDC problem information.
A UE capable of providing its preference on DRX parameters of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a preference on DRX parameters and upon change of its preference on DRX parameters.
A UE capable of providing its preference on the maximum aggregated bandwidth of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a maximum aggregated bandwidth preference and upon change of its maximum aggregated bandwidth preference.
A UE capable of providing its preference on the maximum number of secondary component carriers of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a maximum number of secondary component carriers preference and upon change of its maximum number of secondary component carriers preference.
A UE capable of providing its preference on the maximum number of MIMO layers of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a maximum number of MIMO layers preference and upon change of its maximum number of MIMO layers preference.
A UE capable of providing its preference on the minimum scheduling offset for cross-slot scheduling of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a minimum scheduling offset preference and upon change of its minimum scheduling offset preference.
A UE capable of providing assistance information to transition out of RRC_CONNECTED state may initiate the procedure if it was configured to do so, upon determining that it prefers to transition out of RRC_CONNECTED state, or upon change of its preferred RRC state.
A UE capable of providing configured grant assistance information for NR sidelink communication in RRC_CONNECTED may initiate the procedure in several cases, including upon being configured to provide traffic pattern information and upon change of traffic patterns.
A UE capable of providing an indication of its preference in being provisioned with reference time information may initiate the procedure upon being configured to provide this indication, or if it was configured to provide this indication and upon change of its preference.
A UE capable of providing an indication of its preference in FR2 UL gap may initiate the procedure if it was configured to do so, upon detecting the need of FR2 UL gap activation/deactivation.
A UE capable of providing MUSIM assistance information for gap preference may initiate the procedure if it was configured to do so, upon determining it needs the gaps, or upon change of the gap preference information.
A UE capable of providing MUSIM assistance information for gap priority preference may initiate the procedure if it was configured to do so, upon determining it has gap priority preference information.
A UE capable of providing MUSIM assistance information for leave indication may initiate the procedure if it was configured to do so upon determining that it needs to leave RRC_CONNECTED state.
A UE capable of providing MUSIM assistance information for temporary capability restriction may initiate the procedure if it was configured to do so, upon determining it has temporary capability restriction or upon determining the removal of the capability restriction.
A UE capable of relaxing its RLM measurements of a cell group in RRC_CONNECTED state shall initiate the procedure for providing an indication of its relaxation state for RLM measurements upon being configured to do so, and upon change of its relaxation state for RLM measurements in RRC_CONNECTED state.
A UE capable of relaxing its BFD measurements in serving cells of a cell group in RRC_CONNECTED shall initiate the procedure for providing an indication of its relaxation state for BFD measurements upon being configured to do so, and upon change of its relaxation state for BFD measurements in RRC_CONNECTED state.
A UE capable of SDT initiates this procedure when data and/or signalling mapped to radio bearers that are not configured for SDT becomes available during SDT (i.e. while SDT procedure is ongoing).
A UE capable of providing its preference for SCG deactivation may initiate the procedure if it was configured to do so, upon determining that it prefers or does no more prefer the SCG to be deactivated.
A UE that has uplink data to transmit for a DRB for which there is no MCG RLC bearer while the SCG is deactivated shall initiate the procedure.
A UE capable of providing an indication of fulfilment of the RRM measurement relaxation criterion in connected mode may initiate the procedure if it was configured to do so, upon change of its fulfilment status for RRM measurement relaxation criterion for connected mode.
A UE capable of providing service link propagation delay difference between serving cell and neighbour cell(s) shall initiate the procedure upon being configured to do so, and upon determining that service link propagation delay difference between serving cell and a neighbour cell has changed more than threshPropDelayDiff compared with the last reported value.
A UE capable of providing an indication of its preference on multi-Rx operation for FR2 may initiate the procedure if it was configured to do so, upon detecting having a preference on multi-Rx operation for FR2 and upon change of its preference on multi-Rx operation for FR2.
A UE capable of indicating the availability of flight path information may initiate the procedure, if it was configured to do so, upon determining that an initial or updated flight path information is available.
A UE capable of providing UL traffic information shall initiate the procedure when the information is available upon being configured to do so, and upon change of UL traffic information.
A UE capable of N3C remote UE operation initiates the procedure upon being configured to report relay UE information on the available non-3GPP connection(s), and upon change of its available non-3GPP connection(s).
A UE capable of providing configured grant assistance information including SL-PRS transmission periodicity and priority for NR sidelink positioning in RRC_CONNECTED may initiate the procedure.
Upon initiating the procedure, the UE shall:
1 >
if configured to provide delay budget report:
2 >
if the UE did not transmit a UEAssistanceInformation message with delayBudgetReport since it was configured to provide delay budget report; or
2 >
if the current delay budget is different from the one indicated in the last transmission of the UEAssistanceInformation message including delayBudgetReport and timer T342 is not running:
3 >
start or restart timer T342 with the timer value set to the delayBudgetReportingProhibitTimer;
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide a delay budget report;
1 >
if configured to provide overheating assistance information:
2 >
if the overheating condition has been detected and T345 is not running; or
2 >
if the current overheating assistance information is different from the one indicated in the last transmission of the UEAssistanceInformation message including overheatingAssistance and timer T345 is not running:
3 >
start timer T345 with the timer value set to the overheatingIndicationProhibitTimer;
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide overheating assistance information;
1 >
if configured to provide IDC assistance information based on candidateServingFreqListNR included in idc-AssistanceConfig of a cell group:
2 >
if the UE did not transmit a UEAssistanceInformation message with idc-Assistance since it was configured to provide IDC assistance information:
3 >
if on one or more frequencies included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself; or
3 >
if on one or more supported UL CA or NR-DC combination comprising of carrier frequencies included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself:
4 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide IDC assistance information;
2 >
else if the current idc-Assistance information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information;
1 >
if configured to provide IDC assistance information based on idc-FDM-AssistanceConfig included in idc-AssistanceConfig of a cell group:
2 >
if the UE did not transmit a UEAssistanceInformation message with idc-FDM-Assistance since it was configured to provide IDC assistance information:
3 >
if on one or more frequency ranges included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself; or
3 >
if on one or more supported UL CA or NR-DC combination comprising of frequency ranges included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself:
4 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information;
2 >
else if the current idc-FDM-Assistance information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information;
1 >
if configured to provide IDC assistance information based on idc-TDM-AssistanceConfig included in idc-AssistanceConfig of a cell group:
2 >
if the UE did not transmit a UEAssistanceInformation message with idc-TDM-Assistance since it was configured to provide IDC assistance information:
3 >
if on one or more frequencies included in candidateServingFreqListNR or frequency ranges included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself; or
3 >
if on one or more supported UL CA or NR-DC combination comprising of carrier frequencies included in candidateServingFreqListNR or frequency ranges included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself:
4 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information;
2 >
else if the current idc-TDM-Assistance information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide IDC assistance information;
1 >
if configured to provide its preference on DRX parameters of a cell group for power saving:
2 >
if the UE has a preference on DRX parameters of the cell group and the UE did not transmit a UEAssistanceInformation message with drx-Preference for the cell group since it was configured to provide its preference on DRX parameters of the cell group for power saving; or
2 >
if the current drx-Preference information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including drx-Preference for the cell group and timer T346a associated with the cell group is not running:
3 >
start the timer T346a with the timer value set to the drx-PreferenceProhibitTimer of the cell group;
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide the current drx-Preference;
1 >
if configured to provide its preference on the maximum aggregated bandwidth of a cell group for power saving:
2 >
if the UE has a preference on the maximum aggregated bandwidth of the cell group and the UE did not transmit a UEAssistanceInformation message with maxBW-Preference and/or maxBW-PreferenceFR2-2 for the cell group since it was configured to provide its preference on the maximum aggregated bandwidth of the cell group for power saving; or
2 >
if the current maxBW-Preference information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including maxBW-Preference and/or maxBW-PreferenceFR2-2for the cell group and timer T346b associated with the cell group is not running:
3 >
start the timer T346b with the timer value set to the maxBW-PreferenceProhibitTimer of the cell group;
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide the current maxBW-Preference and/or maxBW-PreferenceFR2-2;
1 >
if configured to provide its preference on the maximum number of secondary component carriers of a cell group for power saving:
2 >
if the UE has a preference on the maximum number of secondary component carriers of the cell group and the UE did not transmit a UEAssistanceInformation message with maxCC-Preference for the cell group since it was configured to provide its preference on the maximum number of secondary component carriers of the cell group for power saving; or
2 >
if the current maxCC-Preference information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including maxCC-Preference for the cell group and timer T346c associated with the cell group is not running:
3 >
start the timer T346c with the timer value set to the maxCC-PreferenceProhibitTimer of the cell group;
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide the current maxCC-Preference;
1 >
if configured to provide its preference on the maximum number of MIMO layers of a cell group for power saving:
2 >
if the UE has a preference on the maximum number of MIMO layers of the cell group and the UE did not transmit a UEAssistanceInformation message with maxMIMO-LayerPreference and/or maxMIMO-LayerPreferenceFR2-2 for the cell group since it was configured to provide its preference on the maximum number of MIMO layers of the cell group for power saving; or
2 >
if the current maxMIMO-LayerPreference information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including maxMIMO-LayerPreference and/or maxMIMO-LayerPreferenceFR2-2 for the cell group and timer T346d associated with the cell group is not running:
3 >
start the timer T346d with the timer value set to the maxMIMO-LayerPreferenceProhibitTimer of the cell group;
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide the current maxMIMO-LayerPreference and/or maxMIMO-LayerPreferenceFR2-2;
1 >
if configured to provide its preference on the minimum scheduling offset for cross-slot scheduling of a cell group for power saving:
2 >
if the UE has a preference on the minimum scheduling offset for cross-slot scheduling of the cell group and the UE did not transmit a UEAssistanceInformation message with minSchedulingOffsetPreference and/or minSchedulingOffsetPreferenceExt for the cell group since it was configured to provide its preference on the minimum scheduling offset for cross-slot scheduling of the cell group for power saving; or
2 >
if the current minSchedulingOffsetPreference and/or minSchedulingOffsetPreferenceExt information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including minSchedulingOffsetPreference and/or minSchedulingOffsetPreferenceExt for the cell group and timer T346e associated with the cell group is not running:
3 >
start the timer T346e with the timer value set to the minSchedulingOffsetPreferenceProhibitTimer of the cell group;
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide the current minSchedulingOffsetPreference and/or minSchedulingOffsetPreferenceExt;
1 >
if configured to provide its release preference and timer T346f is not running:
2 >
if the UE determines that it would prefer to transition out of RRC_CONNECTED state; or
2 >
if the UE is configured with connectedReporting and the UE determines that it would prefer to revert an earlier indication to transition out of RRC_CONNECTED state:
3 >
start timer T346f with the timer value set to the releasePreferenceProhibitTimer;
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide the release preference;
1 >
if configured to provide configured grant assistance information for NR sidelink communication:
2 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide configured grant assistance information for NR sidelink communication;
1 >
if configured to provide preference in being provisioned with reference time information:
2 >
if the UE did not transmit a UEAssistanceInformation message with referenceTimeInfoPreference since it was configured to provide preference; or
2 >
if the UE's preference changed from the last time UE initiated transmission of the UEAssistanceInformation message including referenceTimeInfoPreference:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide preference in being provisioned with reference time information.
1 >
if configured to provide its preference on FR2 UL gap:
2 >
if the UE did not transmit a UEAssistanceInformation message with ul-GapFR2-Preference since it was configured to provide its preference on FR2 UL gap information:
3 >
if the UE has a preference on FR2 UL gap activation/deactivation:
4 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide FR2 UL gap preference;
2 >
else if the current FR2 UL gap preference is different from the one indicated in the last transmission of the UEAssistanceInformation message:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide FR2 UL gap preference.
1 >
if configured to provide MUSIM assistance information for leaving RRC_CONNECTED:
2 >
if the UE needs to leave RRC_CONNECTED state and the timer T346g is not running:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide MUSIM assistance information for leaving RRC_CONNECTED;
3 >
start the timer T346g with the timer value set to the musim-LeaveWithoutResponseTimer;
1 >
if configured to provide MUSIM assistance information for gap preference:
2 >
if the UE has a preference on the MUSIM gap(s) and the UE did not transmit a UEAssistanceInformation message with musim-GapPreferenceList since it was configured to provide MUSIM assistance information for gap preference; or
2 >
if the current musim-GapPreferenceList is different from the one indicated in the last transmission of the UEAssistanceInformation message including musim-GapPreferenceList and the timer T346h is not running:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide the current musim-GapPreferenceList;
3 >
start or restart the timer T346h with the timer value set to the musim-GapProhibitTimer.
1 >
if configured to provide MUSIM assistance information for gap priority preference:
2 >
if the UE has a preference on the MUSIM gap(s) priority and the UE did not transmit a UEAssistanceInformation message with musim-GapPriorityPreferenceList since it was configured to provide MUSIM assistance information for gap priority preference; or
2 >
if the current musim-GapPriorityPreferenceList is different from the one indicated in the last transmission of the UEAssistanceInformation message including musim-GapPriorityPreferenceList and the timer T346h is not running:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the musim-GapPriorityPreferenceList;
3 >
start or restart the timer T346h with the timer value set to the musim-GapProhibitTimer.
1 >
if configured to provide MUSIM assistance information for temporary capability restriction:
2 >
if the UE has temporary capability restriction on the current configuration and timer T348 is not running:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current musim-Cell-SCG-ToRelease and/or musim-CellToAffectList;
3 >
start the timer T348 with the timer value set to the musim-WaitTimer.
2 >
if the UE has temporary capability restriction on the current band(s) or combination(s) of bands and the UE did not transmit a UEAssistanceInformation message with musim-AffectedBandsList and/or musim-AvoidedBandsList since it was configured to provide MUSIM assistance information for temporary capability restriction; or
2 >
if the current musim-AffectedBandsList and/or musim-AvoidedBandsList is different from the one indicated in the last transmission of the UEAssistanceInformation message including musim-CapRestriction and timer T346n is not running:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current musim-AffectedBandsList and/or musim-AvoidedBandsList;
3 >
start the timer T346n with the timer value set to the musim-ProhibitTimer.
2 >
if the UE has a preference on the measurement gap requirement information and the UE did not transmit a UEAssistanceInformation message with measurement gap requirement information or RRCReconfigurationComplete message or RRCResumeComplete message with measurement gap requirement information since it was configured to provide its preference on the measurement gap requirement information for MUSIM; or
2 >
if the current musim-NeedForGapsInfoNR is different from the one indicated in the last transmission of the UEAssistanceInformation message or RRCReconfigurationComplete message or RRCResumeComplete message including musim-CapRestriction to provide the needForGapsInfoNR for the measurement gap requirement of NR target bands:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current musim-NeedForGapsInfoNR;
1 >
if configured to provide the relaxation state of RLM measurements of a cell group and RLM measurement of the cell group is not stopped:
2 >
if the UE did not transmit a UEAssistanceInformation message with rlm-MeasRelaxationState since it was configured to provide the relaxation state of RLM measurements for the cell group; or
2 >
if the relaxation state of RLM measurements for the cell group is currently different from the relaxation state reported in the last transmission of the UEAssistanceInformation message including rlm-MeasRelaxationState of the cell group and timer T346j associated with the cell group is not running:
3 >
start timer T346j with the timer value set to the rlm-RelaxtionReportingProhibitTimer;
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide the relaxation state of RLM measurements of the cell group;
1 >
if configured to provide the relaxation state of BFD measurements of serving cells of a cell group and BFD measurement of the cell group is not stopped:
2 >
if the UE did not transmit a UEAssistanceInformation message with bfd-MeasRelaxationState since it was configured to provide the relaxation state of BFD measurements for the cell group; or
2 >
if the relaxation state of BFD measurements in any serving cell of the cell group is currently different from the relaxation state reported in the last transmission of the UEAssistanceInformation message including bfd-MeasRelaxationState of the cell group and timer T346k associated with the cell group is not running:
3 >
start timer T346k with the timer value set to the bfd-RelaxtionReportingProhibitTimer;
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide the relaxation state of BFD measurements of serving cells of the cell group.
1 >
if data and/or signalling mapped to radio bearers not configured for SDT becomes available during SDT (i.e. while SDT procedure is ongoing):
2 >
if the UE did not transmit a UEAssistanceInformation message with nonSDT-DataIndication since the initiation of the current resume procedure for SDT:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide nonSDT-DataIndication.
1 >
if configured to provide its preference for SCG deactivation and timer T346i is not running;
2 >
if the UE prefers the SCG to be deactivated and did not transmit a UEAssistanceInformation message with scg-DeactivationPreference since it was configured to provide its SCG deactivation preference; or
2 >
if the UE preference for SCG deactivation is different from the last indicated scg-DeactivationPreference:
3 >
start timer T346i with the timer value set to the scg-DeactivationPreferenceProhibitTimer;
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide the UE preference for SCG deactivation;
1 >
if the SCG is deactivated, and,
1 >
the UE has uplink data to send for an SCG RLC entity while the UE previously did not have any uplink data to send for any SCG RLC entity:
2 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to indicate that the UE has uplink data to send for a DRB whose DRB-Identity is not included in any RLC-BearerConfig in the CellGroupConfig associated with the MCG.
1 >
if configured to send indications of RRM measurement relaxation criterion fulfilment:
2 >
if the criterion in clause 5.7.4.4 is met for a period of TSearchDeltaP-StationaryConnected:
3 >
if the UE did not transmit a UEAssistanceInformation message with rrm-MeasRelaxationFulfilment as true since it was configured to provide indications of RRM measurement relaxation criterion fulfilment; or
3 >
the last UEAssistanceInformation message indicated the criterion in clause 5.7.4.4 is not fulfilled with rrm-MeasRelaxationFulfilment as false:
4 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to indicate that the criterion for RRM measurement relaxation for connected mode is fulfilled;
2 >
else:
3 >
if the last UEAssistanceInformation message indicated fulfilment of the criterion in clause 5.7.4.4 with rrm-MeasRelaxationFulfilment as true:
4 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to indicate that the criterion for RRM measurement relaxation for connected mode is not fulfilled.
1 >
if configured to provide service link propagation delay difference between serving cell and neighbour cell(s);
2 >
if the UE did not transmit a UEAssistanceInformation message with propagationDelayDifference since it was configured to provide service link propagation delay difference between serving cell and neighbour cell(s); or
2 >
for any neighbour cell in neighCellInfoList, if the service link propagation delay difference between serving cell and the neighbour cell has changed more than threshPropDelayDiff since the last transmission of the UEAssistanceInformation message including propagationDelayDifference:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with clause 5.7.4.3 to provide service link propagation delay difference between serving cell and each neighbour cell included in the neighCellInfoList;
1 >
if configured to provide its preference for multi-Rx operation and timer T440 is not running;
2 >
if the UE has a preference on multi-Rx operation for FR2 and did not transmit a UEAssistanceInformation message with multiRx-PreferenceFR2 since it was configured to provide its preference on multi-Rx operation; or
2 >
if the UE has a different preference on multi-Rx operation for FR2 from the last indicated multiRx-PreferenceFR2:
3 >
start timer T440 with the timer value set to the multiRx-PreferenceReportingConfigFR2ProhibitTimer;
3 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the UE preference for multi-Rx operation for FR2.
1 >
if configured to indicate the availability of flight path information and the UE has flight path information available:
2 >
if the UE had not previously provided a flight path information since last entering RRC_CONNECTED state; or
2 >
if at least one waypoint was not previously provided; or
2 >
if at least one upcoming waypoint that was previously provided is being removed; or
2 >
if flightPathUpdateDistanceThr is configured and for at least one waypoint, the 3D distance between the previously provided location and the new location is more than or equal to the distance threshold configured by flightPathUpdateDistanceThr; or
2 >
if flightPathUpdateTimeThr is configured and for at least one waypoint, the timestamp was not previously provided but is now available, or the time between the previously provided timestamp and the new timestamp, if available, is more than or equal to the time threshold configured by flightPathUpdateTimeThr:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to indicate the availability of flight path information;
1 >
if configured to provide UL traffic information:
2 >
if the UE did not transmit a UEAssistanceInformation message with ul-TrafficInfo since it was configured to provide UL traffic information; or
2 >
if UL traffic information included in the previous UEAssistanceInformation has changed since the last transmission of the UEAssistanceInformation message containing ul-TrafficInfo for at least one QoS flow for which timer T346x is not running:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide UL traffic information.
1 >
if configured to report relay UE information with non-3GPP connection(s);
2 >
if the UE did not transmit a UEAssistanceInformation message with n3c-relayUE-InfoList since it was configured to report available relay UE information with non-3GPP connection(s); or
2 >
if the UE has new available non-3GPP conection(s); or
2 >
if the non-3GPP connection(s) with the reported relay UE(s) is not available:
3 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to report relay UE information with non-3GPP connection(s) included in the n3c-relayUE-InfoList;
1 >
if configured to provide configured grant assistance information for NR sidelink positioning:
2 >
initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide configured grant assistance information for NR sidelink positioning;
Up

5.7.4.3  Actions related to transmission of UEAssistanceInformation message  p. 323

The UE shall set the contents of the UEAssistanceInformation message as follows:
1 >
if transmission of the UEAssistanceInformation message is initiated to provide a delay budget report according to clause 5.7.4.2 or 5.3.5.3;
2 >
set delayBudgetReport to type1 according to a desired value;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide overheating assistance information according to clause 5.7.4.2 or 5.3.5.3;
2 >
if the UE experiences internal overheating:
3 >
if the UE prefers to temporarily reduce the number of maximum secondary component carriers:
4 >
include reducedMaxCCs in the OverheatingAssistance IE;
4 >
set reducedCCsDL to the number of maximum SCells the UE prefers to be temporarily configured in downlink;
4 >
set reducedCCsUL to the number of maximum SCells the UE prefers to be temporarily configured in uplink;
3 >
if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR1:
4 >
include reducedMaxBW-FR1 in the OverheatingAssistance IE;
4 >
set reducedBW-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR1;
4 >
set reducedBW-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR1;
3 >
if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-1:
4 >
include reducedMaxBW-FR2 in the OverheatingAssistance IE;
4 >
set reducedBW-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-1;
4 >
set reducedBW-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-1;
3 >
if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-2:
4 >
include reducedMaxBW-FR2-2 in the OverheatingAssistance IE;
4 >
set reducedBW-FR2-2-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-2;
4 >
set reducedBW-FR2-2-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-2;
3 >
if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR1:
4 >
include reducedMaxMIMO-LayersFR1 in the OverheatingAssistance IE;
4 >
set reducedMIMO-LayersFR1-DL to the number of maximum MIMO layers of each serving cell operating on FR1 the UE prefers to be temporarily configured in downlink;
4 >
set reducedMIMO-LayersFR1-UL to the number of maximum MIMO layers of each serving cell operating on FR1 the UE prefers to be temporarily configured in uplink;
3 >
if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-1:
4 >
include reducedMaxMIMO-LayersFR2 in the OverheatingAssistance IE;
4 >
set reducedMIMO-LayersFR2-DL to the number of maximum MIMO layers of each serving cell operating on FR2-1 the UE prefers to be temporarily configured in downlink;
4 >
set reducedMIMO-LayersFR2-UL to the number of maximum MIMO layers of each serving cell operating on FR2-1 the UE prefers to be temporarily configured in uplink;
3 >
if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-2:
4 >
include reducedMaxMIMO-LayersFR2-2 in the OverheatingAssistance IE;
4 >
set reducedMIMO-LayersFR2-2-DL to the number of maximum MIMO layers of each serving cell operating on FR2 the UE prefers to be temporarily configured in downlink;
4 >
set reducedMIMO-LayersFR2-2-UL to the number of maximum MIMO layers of each serving cell operating on FR2 the UE prefers to be temporarily configured in uplink;
2 >
else (if the UE no longer experiences an overheating condition):
3 >
do not include reducedMaxCCs, reducedMaxBW-FR1, reducedMaxBW-FR2, reducedMaxBW-FR2-2, reducedMaxMIMO-LayersFR1, reducedMaxMIMO-LayersFR2 or reducedMaxMIMO-LayersFR2-2 in OverheatingAssistance IE;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide IDC assistance information according to clause 5.7.4.2 or 5.3.5.3:
2 >
if there is at least one carrier frequency included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself:
3 >
include the field affectedCarrierFreqList with an entry for each affected carrier frequency included in candidateServingFreqListNR;
3 >
for each carrier frequency included in the field affectedCarrierFreqList, include interferenceDirection and set it accordingly;
2 >
if there is at least one supported UL CA or NR-DC combination comprising of carrier frequencies included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself:
3 >
include victimSystemType for each UL CA or NR-DC combination included in affectedCarrierFreqCombList;
3 >
if the UE sets victimSystemType to wlan or bluetooth:
4 >
include affectedCarrierFreqCombList with an entry for each supported UL CA combination comprising of carrier frequencies included in candidateServingFreqListNR, that is affected by IDC problems;
3 >
else:
4 >
optionally include affectedCarrierFreqCombList with an entry for each supported UL CA or NR-DC combination comprising of carrier frequencies included in candidateServingFreqListNR, that is affected by IDC problems;
2 >
if there is at least one affected frequency range overlapping with one candidate frequency range included in candidateServingFreqRangeListNR, and the center frequency of the affected frequency range is within the candidate frequency range included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself:
3 >
include the field affectedCarrierFreqRangeList with an entry for each affected frequency range;
3 >
for each affected frequency range included in the field affectedCarrierFreqRangeList, include centerFreq and affectedBandwidth;
3 >
for each affected frequency range included in the field affectedCarrierFreqRangeList, include interferenceDirection and optionally victimSystemType, and set it accordingly;
2 >
if there is at least one supported UL CA or NR-DC combinations comprising of candidate frequency ranges included in candidateServingFreqRangeListNR, and each affected frequency range in the UL CA or NR-DC combination overlapping with one candidate frequency range included in candidateServingFreqRangeListNR, and the center frequency of the affected frequency range is within the candidate frequency range included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself:
3 >
include the field affectedCarrierFreqRangeCombList with an entry for each supported UL CA or NR-DC combination comprising of frequency ranges that is affected by IDC problems;
3 >
for each affected frequency range included in the field affectedCarrierFreqRangeCombList, include centerFreq and affectedBandwidth;
3 >
for each UL CA or NR-DC combination included in the field affectedCarrierFreqRangeCombList, include interferenceDirection and optionally victimSystemType, and set it accordingly;
2 >
if there is at least one candidate carrier frequency included in candidateServingFreqListNR or candidate frequency range included in candidateServingFreqRangeListNR or one supported UL CA or NR-DC combination comprising of candidate carrier frequencies included in candidateServingFreqListNR or candidate frequency ranges included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself, and affectedCarrierFreqList or affectedCarrierFreqCombList or affectedCarrierFreqRangeList or affectedCarrierFreqRangeCombList is included, and idc-TDM-AssistanceConfig is set to setup:
3 >
include Time Domain Multiplexing (TDM) based assistance information as indicated by idc-TDM-Assistance that could be used to resolve the IDC problems;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide drx-Preference of a cell group for power saving according to clause 5.7.4.2 or 5.3.5.3:
2 >
include drx-Preference in the UEAssistanceInformation message;
2 >
if the UE has a preference on DRX parameters for the cell group:
3 >
if the UE has a preference for the long DRX cycle:
4 >
include preferredDRX-LongCycle in the DRX-Preference IE and set it to the preferred value;
3 >
if the UE has a preference for the DRX inactivity timer:
4 >
include preferredDRX-InactivityTimer in the DRX-Preference IE and set it to the preferred value;
3 >
if the UE has a preference for the short DRX cycle:
4 >
include preferredDRX-ShortCycle in the DRX-Preference IE and set it to the preferred value;
3 >
if the UE has a preference for the short DRX timer:
4 >
include preferredDRX-ShortCycleTimer in the DRX-Preference IE and set it to the preferred value;
2 >
else (if the UE has no preference on DRX parameters for the cell group):
3 >
do not include preferredDRX-LongCycle, preferredDRX-InactivityTimer, preferredDRX-ShortCycle and preferredDRX-ShortCycleTimer in the DRX-Preference IE;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide maxBW-Preference of a cell group for power saving according to clause 5.7.4.2 or 5.3.5.3:
2 >
include maxBW-Preference in the UEAssistanceInformation message;
2 >
if the UE has a preference on the maximum aggregated bandwidth for the cell group:
3 >
if the UE prefers to reduce the maximum aggregated bandwidth of FR1:
4 >
include reducedMaxBW-FR1 in the MaxBW-Preference IE;
4 >
set reducedBW-DL to the maximum aggregated bandwidth the UE desires to have configured across all downlink carriers of FR1 in the cell group;
4 >
set reducedBW-UL to the maximum aggregated bandwidth the UE desires to have configured across all uplink carriers of FR1 in the cell group;
3 >
if the UE prefers to reduce the maximum aggregated bandwidth of FR2-1:
4 >
include reducedMaxBW-FR2 in the MaxBW-Preference IE;
4 >
set reducedBW-DL to the maximum aggregated bandwidth the UE desires to have configured across all downlink carriers of FR2-1 in the cell group;
4 >
set reducedBW-UL to the maximum aggregated bandwidth the UE desires to have configured across all uplink carriers of FR2-1 in the cell group;
2 >
else (if the UE has no preference on the maximum aggregated bandwidth for the cell group):
3 >
do not include reducedMaxBW-FR1 and reducedMaxBW-FR2 in the MaxBW-Preference IE;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide maxBW-PreferenceFR2-2 of a cell group for power saving according to clause 5.7.4.2 or 5.3.5.3:
2 >
include maxBW-PreferenceFR2-2 in the UEAssistanceInformation message;
3 >
if the UE prefers to reduce the maximum aggregated bandwidth of FR2-2:
4 >
include reducedMaxBW-FR2-2 in the MaxBW-PreferenceFR2-2 IE;
4 >
set reducedBW-FR2-2-DL to the maximum aggregated bandwidth the UE desires to have configured across all downlink carriers of FR2-2 in the cell group;
4 >
set reducedBW-FR2-2-UL to the maximum aggregated bandwidth the UE desires to have configured across all uplink carriers of FR2-2 in the cell group;
2 >
else (if the UE has no preference on the maximum aggregated bandwidth for the cell group):
3 >
do not include reducedMaxBW-FR2-2 in the MaxBW-PreferenceFR2-2 IE;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide maxCC-Preference of a cell group for power saving according to clause 5.7.4.2 or 5.3.5.3:
2 >
include maxCC-Preference in the UEAssistanceInformation message;
2 >
if the UE has a preference on the maximum number of secondary component carriers for the cell group:
3 >
include reducedMaxCCs in the MaxCC-Preference IE;
3 >
set reducedCCsDL to the number of maximum SCells the UE desires to have configured in downlink in the cell group;
3 >
set reducedCCsUL to the number of maximum SCells the UE desires to have configured in uplink in the cell group;
2 >
else (if the UE has no preference on the maximum number of secondary component carriers for the cell group):
3 >
do not include reducedMaxCCs in the MaxCC-Preference IE;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide maxMIMO-LayerPreference of a cell group for power saving according to clause 5.7.4.2 or 5.3.5.3:
2 >
include maxMIMO-LayerPreference in the UEAssistanceInformation message;
2 >
if the UE has a preference on the maximum number of MIMO layers for the cell group:
3 >
if the UE prefers to reduce the number of maximum MIMO layers of each serving cell operating on FR1:
4 >
include reducedMaxMIMO-LayersFR1 in the MaxMIMO-LayerPreference IE;
4 >
set reducedMIMO-LayersFR1-DL to the preferred maximum number of downlink MIMO layers of each BWP of each FR1 serving cell that the UE operates on in the cell group;
4 >
set reducedMIMO-LayersFR1-UL to the preferred maximum number of uplink MIMO layers of each FR1 serving cell that the UE operates on in the cell group;
3 >
if the UE prefers to reduce the number of maximum MIMO layers of each serving cell operating on FR2-1:
4 >
include reducedMaxMIMO-LayersFR2 in the MaxMIMO-LayerPreference IE;
4 >
set reducedMIMO-LayersFR2-DL to the preferred maximum number of downlink MIMO layers of each BWP of each FR2-1 serving cell that the UE operates on in the cell group;
4 >
set reducedMIMO-LayersFR2-UL to the preferred maximum number of uplink MIMO layers of each FR2-1 serving cell that the UE operates on in the cell group;
2 >
else (if the UE has no preference on the maximum number of MIMO layers for the cell group):
3 >
do not include reducedMaxMIMO-LayersFR1 and reducedMaxMIMO-LayersFR2 in the MaxMIMO-LayerPreference IE;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide maxMIMO LayerPreferenceFR2 2 of a cell group for power saving according to clause 5.7.4.2 or 5.3.5.3:
2 >
include maxMIMO-LayerPreferenceFR2-2 in the UEAssistanceInformation message;
2 >
if the UE has a preference on the maximum number of MIMO layers for the cell group for FR2-2:
3 >
if the UE prefers to reduce the number of maximum MIMO layers of each serving cell operating on FR2 2:
4 >
include reducedMaxMIMO-LayersFR2-2 in the MaxMIMO-LayerPreferenceFR2 2 IE;
4 >
set reducedMIMO-LayersFR2-2-DL to the preferred maximum number of downlink MIMO layers of each BWP of each FR2-2 serving cell that the UE operates on in the cell group;
4 >
set reducedMIMO-LayersFR2-2-UL to the preferred maximum number of uplink MIMO layers of each FR2-2 serving cell that the UE operates on in the cell group;
2 >
else (if the UE has no preference on the maximum number of MIMO layers for the cell group):
3 >
do not include reducedMaxMIMO-LayersFR2-2 in the MaxMIMO-LayerPreferenceFR2-2 IE;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide minSchedulingOffsetPreference of a cell group for power saving according to clause 5.7.4.2 or 5.3.5.3:
2 >
include minSchedulingOffsetPreference in the UEAssistanceInformation message;
2 >
if the UE has a preference on the minimum scheduling offset for cross-slot scheduling for the cell group:
3 >
if the UE has a preference for the value of K0 (clause 5.1.2.1 of TS 38.214) for cross-slot scheduling with 15 kHz SCS:
4 >
include preferredK0-SCS-15kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K0;
3 >
if the UE has a preference for the value of K0 for cross-slot scheduling with 30 kHz SCS:
4 >
include preferredK0-SCS-30kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K0;
3 >
if the UE has a preference for the value of K0 for cross-slot scheduling with 60 kHz SCS:
4 >
include preferredK0-SCS-60kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K0;
3 >
if the UE has a preference for the value of K0 for cross-slot scheduling with 120 kHz SCS:
4 >
include preferredK0-SCS-120kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K0;
3 >
if the UE has a preference for the value of K2 (clause 6.1.2.1 of TS 38.214) for cross-slot scheduling with 15 kHz SCS:
4 >
include preferredK2-SCS-15kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K2;
3 >
if the UE has a preference for the value of K2 for cross-slot scheduling with 30 kHz SCS:
4 >
include preferredK2-SCS-30kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K2;
3 >
if the UE has a preference for the value of K2 for cross-slot scheduling with 60 kHz SCS:
4 >
include preferredK2-SCS-60kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K2;
3 >
if the UE has a preference for the value of K2 for cross-slot scheduling with 120 kHz SCS:
4 >
include preferredK2-SCS-120kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K2;
2 >
else (if the UE has no preference on the minimum scheduling offset for cross-slot scheduling for the cell group):
3 >
do not include preferredK0 and preferredK2 in the MinSchedulingOffsetPreference IE;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide minSchedulingOffsetPreferenceExt of a cell group for power saving according to clause 5.7.4.2 or 5.3.5.3:
2 >
include minSchedulingOffsetPreferenceExt in the UEAssistanceInformation message;
2 >
if the UE has a preference on the minimum scheduling offset for cross-slot scheduling for the cell group for FR2-2:
3 >
include minSchedulingOffsetPreferenceExt in the UEAssistanceInformation message;
4 >
if the UE has a preference for the value of K0 (clause 5.1.2.1 of TS 38.214) for cross-slot scheduling with 480 kHz SCS:
5 >
include preferredK0-SCS-480kHz in the minSchedulingOffsetPreferenceExt IE and set it to the desired value of K0;
4 >
if the UE has a preference for the value of K0 for cross-slot scheduling with 960 kHz SCS:
5 >
include preferredK0-SCS-960kHz in the minSchedulingOffsetPreferenceExt IE and set it to the desired value of K0;
4 >
if the UE has a preference for the value of K2 for cross-slot scheduling with 480 kHz SCS:
5 >
include preferredK2-SCS-480kHz in the minSchedulingOffsetPreferenceExt IE and set it to the desired value of K2;
4 >
if the UE has a preference for the value of K2 for cross-slot scheduling with 960 kHz SCS:
5 >
include preferredK2-SCS-960kHz in the minSchedulingOffsetPreferenceExt IE and set it to the desired value of K2;
3 >
else (if the UE has no preference on the minimum scheduling offset for cross-slot scheduling for the cell group):
4 >
do not include preferredK0 and preferredK2 in the minSchedulingOffsetPreferenceExt IE;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide a release preference according to clause 5.7.4.2 or 5.3.5.3:
2 >
include releasePreference in the UEAssistanceInformation message;
2 >
set preferredRRC-State to the desired RRC state on transmission of the UEAssistanceInformation message;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide an indication of preference in being provisioned with reference time information according to clause 5.7.4.2 or 5.3.5.3:
2 >
if the UE has a preference in being provisioned with reference time information:
3 >
set referenceTimeInfoPreference to true;
2 >
else:
3 >
set referenceTimeInfoPreference to false.
1 >
if transmission of the UEAssistanceInformation message is initiated to provide preference on FR2 UL gap according to clause 5.7.4.2 or 5.3.5.3:
2 >
if the UE has a preference for FR2 UL gap configuration:
3 >
set ul-GapFR2-PatternPreference to the preferred FR2 UL gap pattern;
2 >
else (if the UE has no preference for the FR2 UL gap configuration):
3 >
do not include ul-GapFR2-PatternPreference in the UL-GapFR2-Preference IE.
1 >
if transmission of the UEAssistanceInformation message is initiated to provide MUSIM assistance information according to clause 5.7.4.2 or 5.3.5.3:
2 >
if the UE has a preference for MUSIM periodic gap(s):
3 >
include musim-GapPreferenceList with an entry for each periodic gap the UE prefers to be configured;
4 >
set musim-GapLength and musim-GapRepetitionAndOffset in the musim-GapInfo IE to the values of the length and the repetition/offset of the gap(s), respectively, the UE prefers to be configured with;
2 >
if the UE has a preference for MUSIM aperiodic gap:
3 >
include the field musim-GapPreferenceList, with one entry for the aperiodic gap the UE prefers to be configured;
4 >
include musim-GapLength in the musim-GapInfo IE and set it to the values of the length of the gap the UE prefers to be configured with;
4 >
optionally include musim-Starting-SFN-AndSubframe in the musim-GapInfo IE and set it to the starting SFN/subframe of the gap the UE prefers to be configured with;
2 >
if the UE has no longer preference for the periodic/aperiodic gaps:
3 >
do not include musim-GapPreferenceList in the musim-Assistance IE;
2 >
if UE has a preference to leave RRC_CONNECTED state:
3 >
set musim-PreferredRRC-State to the preferred RRC state.
2 >
if UE has a preference for MUSIM gap priority:
3 >
include the musim-GapPriorityPreferenceList the UE prefers to be configured;
3 >
if the UE has preference to keep all collided MUSIM gaps for periodic MUSIM gap(s):
4 >
include the musim-GapKeep;
2 >
if UE has a preference for temporary capability restriction:
3 >
if UE has a preference for serving cell(s) and/or SCG to be released:
4 >
include the musim-Cell-SCG-ToRelease;
5 >
set musim-CellToRelease to include the serving cell(s) the UE prefers to be released;
5 >
set scg-ReleasePreference to scgReleasePreferred if the UE prefers the SCG to be released;
3 >
if UE has a preference to indicate the serving cells:
4 >
include the musim-CellToAffectList the UE prefers to be configured;
5 >
include the musim-ServCellIndex and the musim-MIMO-Layers-DL/ musim-MIMO-Layers-UL/ musim-SupportedBandwidth-DL/ musim-SupportedBandwidth-UL for the corresponding serving cell;
3 >
if UE has a preference to indicate the maximum number of CCs:
4 >
include the musim-capabilityRestricted for the corresponding musim-MaxCC the UE prefers to be configured;
5 >
include the the musim-MaxCC-DL/ musim-MaxCC-UL for the corresponding maximum number of CCs;
3 >
if UE has a preference to indicate band(s) and/or combination(s) of bands with capabilities restricted which comprise of the band(s) that is/are indicated in musim-CandidateBandList:
4 >
include the musim-AffectededBandCombList the UE prefer to be configured with capabilities restricted;
5 >
include the bandEntryIndex for each band for each band or each band of the combination(s) for which capabilities are restricted;
5 >
include the musim-CapabilityRestricted for the corresponding band(s) or bands of the combination(s);
3 >
if UE has a preference to indicate band(s) and/or combination(s) of bands to be avoided which comprise of band(s) that is indicated in musim-CandidateBandList:
4 >
include the musim-AvoidedBandsList the UE prefers not to be configured;
5 >
include the bandEntryIndex for each band or each band of the combination(s) to be avoided;
3 >
if UE has a preference for measurement gap requirement:
4 >
include the musim-NeedForGapsInfoNR to provide the measurement gap requirement information from the requestedTargetBandFilterNR-r16 of NeedForGapsConfigNR configuration in RRCResume message or RRCReconfiguration message of NR target bands the UE prefer to be configured;
2 >
if the UE has no longer preference for temporary capability restriction:
3 >
do not include the corresponding temporary capability restriction preference in the musim-CapRestriction in the musim-Assistance IE;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide the relaxation state of RLM measurements of a cell group according to clause 5.7.4.2:
2 >
if the UE performs RLM measurement relaxation on the cell group according to TS 38.133:
3 >
set the rlm-MeasRelaxationState to true;
2 >
else:
3 >
set the rlm-MeasRelaxationState to false;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide the relaxation state of BFD measurements of a cell group:
2 >
for each serving cell of the cell group:
3 >
if the UE performs BFD measurement relaxation on this serving cell according to TS 38.133:
4 >
set the n-th bit of bfd-MeasRelaxationState to '1', where n is equal to the servCellIndex value + 1 of the serving cell;
3 >
else:
4 >
set the n-th bit of bfd-MeasRelaxationState to '0', where n is equal to the servCellIndex value + 1 of the serving cell.
1 >
if transmission of the UEAssistanceInformation message is initiated to indicate availability of data mapped to radio bearers not configured for SDT according to clause 5.7.4.2:
2 >
include the nonSDT-DataIndication in the UEAssistanceInformation message;
2 >
include and set the resumeCause according to the information received from the upper layers, if provided.
1 >
if transmission of the UEAssistanceInformation message is initiated to provide an indication of preference for SCG deactivation according to clause 5.7.4.2:
2 >
include scg-DeactivationPreference in the UEAssistanceInformation message;
2 >
set the scg-DeactivationPreference to scgDeactivationPreferred if the UE prefers the SCG to be deactivated, otherwise set it to noPreference;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide an indication that the UE has uplink data related to a deactivated SCG according to clause 5.7.4.2:
2 >
include uplinkData in the UEAssistanceInformation message.
1 >
if transmission of the UEAssistanceInformation message is initiated to provide an indication about whether the criterion for RRM relaxation for connected mode is fulfilled or not fulfilled:
2 >
if the criterion for RRM measurement relaxation for connected mode is fulfilled:
3 >
set the rrm-MeasRelaxationFulfilment to true;
2 >
else:
3 >
set the rrm-MeasRelaxationFulfilment to false.
1 >
if transmission of the UEAssistanceInformation message is initiated to provide the service link propagation delay difference between serving cell and neighbour cell(s) according to clause 5.7.4.2;
2 >
include the propagationDelayDifference for each neighbour cell in the neighCellInfoList;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide preference on multi-Rx operation for FR2 according to clause 5.7.4.2:
2 >
if the UE has a preference for not operating on multi-Rx (i.e. not supporting simultaneous reception with different QCL-typeD) for FR2:
3 >
set multiRx-PreferenceFR2 to the preferred multi-Rx operation for FR2;
2 >
else (if the UE has the preference for operating on multi-Rx for FR2):
3 >
not include multiRx-PreferenceFR2.
1 >
if transmission of the UEAssistanceInformation message is initiated to indicate the availability of flight path information according to clause 5.7.4.2 or clause 5.3.5.3;
2 >
include the flightPathInfoAvailable;
1 >
if transmission of the UEAssistanceInformation message is initiated to provide UL traffic information according to clause 5.7.4.2:
2 >
for each PDU session for which the UE intends to provide UL traffic information in this UEAssistanceInformation message:
3 >
set pdu-SessionID to the value of the concerned PDU session ID;
3 >
for each QoS flow of this PDU session for which timer T346x is not running and for which the UE intends to provide UL traffic information in this UEAssistanceInformation message:
4 >
start timer T346x associated to this QoS flow with the timer value set to the value of ul-TrafficInfoProhibitTimer;
4 >
set qfi to the value of the concerned QFI;
4 >
if the jitter range measurement is available; and
4 >
if the UE did not provide jitter range since it was configured to provide UL traffic information, or if the measured jitter range has changed since the last transmission of the UEAssistanceInformation message containing jitterRange:
5 >
set jitterRange to the latest measured value of the jitter range;
4 >
if the burst arrival time measurement is available; and
4 >
if the UE did not provide burst arrival time since it was configured to provide UL traffic information, or if the measured burst arrival time has changed since the last transmission of the UEAssistanceInformation message containing burstArrivalTime:
5 >
set burstArrivalTime to the latest measured value of the burst arrival time;
4 >
if the traffic periodicity measurement is available; and
4 >
if the UE did not provide traffic periodicity since it was configured to provide UL traffic information, or if the measured traffic periodicity has changed since the last transmission of the UEAssistanceInformation message containing trafficPeriodicity:
5 >
set trafficPeriodicity to the latest measured value of the traffic periodicity;
4 >
if the UE did not provide pduSetIdentification since it was configured to provide UL traffic information, or if the information previously provided in pduSetIdentification has changed since the last transmission of the UEAssistanceInformation message containing pduSetIdentification:
5 >
if the UE is able to identify PDU Set related information for the QoS flow:
6 >
set pduSetIdentification to true;
5 >
else:
6 >
set pduSetIdentification to false.
1 >
if transmission of the UEAssistanceInformation message is initiated to report relay UE information with non-3GPP connection(s) according to clause 5.7.4.2:
2 >
include n3c-relayUE-InfoList in the UEAssistanceInformation message;
The UE shall set the contents of the UEAssistanceInformation message for configured grant assistance information for NR sidelink communication or NR sidelink positioning:
1 >
if configured to provide configured grant assistance information for NR sidelink communication or NR sidelink positioning:
2 >
include the sl-UE-AssistanceInformationNR;
The UE shall:
1 >
if the procedure was triggered to provide configured grant assistance information for NR sidelink communication by an NR RRCReconfiguration message that was embedded within an E-UTRA RRCConnectionReconfiguration:
2 >
submit the UEAssistanceInformation to lower layers via SRB1, embedded in E-UTRA RRC message ULInformationTransferIRAT as specified in clause 5.6.28 of TS 36.331;
1 >
else if the procedure was triggered to provide UE preference for SCG deactivation or to indicate that the UE with a deactivate SCG has uplink data to send on a DRB for which there is no MCG RLC bearer:
2 >
submit the UEAssistanceInformation via SRB1 to lower layers for transmission;
1 >
else if the UE is in (NG)EN-DC:
2 >
if SRB3 is configured and the SCG is not deactivated:
3 >
submit the UEAssistanceInformation message via SRB3 to lower layers for transmission;
2 >
else:
3 >
submit the UEAssistanceInformation message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331.
1 >
else if the UE is in NR-DC:
2 >
if the UE assistance configuration that triggered this UE assistance information is associated with the SCG:
3 >
if SRB3 is configured and the SCG is not deactivated:
4 >
submit the UEAssistanceInformation message via SRB3 to lower layers for transmission;
3 >
else:
4 >
submit the UEAssistanceInformation message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3;
2 >
else:
3 >
submit the UEAssistanceInformation message via SRB1 to lower layers for transmission;
1 >
else:
2 >
submit the UEAssistanceInformation message to lower layers for transmission.
1 >
if the procedure was triggered to provide configured grant assistance information for NR sidelink positioning:
2 >
submit the UEAssistanceInformation to lower layers via SRB1.
Up

5.7.4.3a  Setting the contents of OverheatingAssistance IE  p. 334

The UE shall set the contents of OverheatingAssistance IE if initiated to provide overheating assistance indication for SCG in (NG)EN-DC according to clause 5.6.10.3 of TS 36.331:
1 >
if the UE prefers to temporarily reduce the number of maximum secondary component carriers for SCG:
2 >
include reducedMaxCCs in the OverheatingAssistance IE;
2 >
set reducedCCsDL to the number of maximum SCells of the SCG the UE prefers to be temporarily configured in downlink;
2 >
set reducedCCsUL to the number of maximum SCells of the SCG the UE prefers to be temporarily configured in uplink;
1 >
if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR1 for SCG:
2 >
include reducedMaxBW-FR1 in the OverheatingAssistance IE;
2 >
set reducedBW-FR1-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR1 of the SCG;
2 >
set reducedBW-FR1-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR1 of the SCG;
1 >
if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-1 for SCG:
2 >
include reducedMaxBW-FR2 in the OverheatingAssistance IE;
2 >
set reducedBW-FR2-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-1 of the SCG;
2 >
set reducedBW-FR2-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-1 of the SCG;
1 >
if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-2 for SCG:
2 >
include reducedMaxBW-FR2-2 in the OverheatingAssistance IE;
2 >
set reducedBW-FR2-2-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-2 of the SCG;
2 >
set reducedBW-FR2-2-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-2 of the SCG;
1 >
if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR1 for SCG:
2 >
include reducedMaxMIMO-LayersFR1 in the OverheatingAssistance IE;
2 >
set reducedMIMO-LayersFR1-DL to the number of maximum MIMO layers of each serving cell operating on FR1 of the SCG the UE prefers to be temporarily configured in downlink;
2 >
set reducedMIMO-LayersFR1-UL to the number of maximum MIMO layers of each serving cell operating on FR1 of the SCG the UE prefers to be temporarily configured in uplink;
1 >
if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-1 for SCG:
2 >
include reducedMaxMIMO-LayersFR2 in the OverheatingAssistance IE;
2 >
set reducedMIMO-LayersFR2-DL to the number of maximum MIMO layers of each serving cell operating on FR2-1 of the SCG the UE prefers to be temporarily configured in downlink;
2 >
set reducedMIMO-LayersFR2-UL to the number of maximum MIMO layers of each serving cell operating on FR2-1 of the SCG the UE prefers to be temporarily configured in uplink;
1 >
if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-2 for SCG:
2 >
include reducedMaxMIMO-LayersFR2-2 in the OverheatingAssistance IE;
2 >
set reducedMIMO-LayersFR2-2-DL to the number of maximum MIMO layers of each serving cell operating on FR2-2 of the SCG the UE prefers to be temporarily configured in downlink;
2 >
set reducedMIMO-LayersFR2-2-UL to the number of maximum MIMO layers of each serving cell operating on FR2-2 of the SCG the UE prefers to be temporarily configured in uplink;
Up

5.7.4.4  Relaxed measurement criterion for a stationary (e)RedCap UE  p. 336

The relaxed measurement criterion for a stationary UE is met when:
  • (SS-RSRPRefStationaryConnected - SS-RSRP) < SSearchDeltaP-StationaryConnected,
Where:
  • SS-RSRP = current L3 RSRP measurement of the PCell based on SSB (dB).
  • SS-RSRPRefStationaryConnected = reference SS-RSRP value of the PCell (dB), set as follows:
    • at the end of RRC reconfiguration procedure as specified in clause 5.3.5.3, when rrm-MeasRelaxationReportingConfig is included in the RRCReconfiguration message; or
    • after MAC successfully completes a Random Access procedure after applying a reconfigurationWithSync in spCellConfig while stationary criterion is configured; or
    • if (SS-RSRP - SS-RSRPRefStationaryConnected) > 0; or
    • if the relaxed measurement criterion has not been met for TSearchDeltaP-StationaryConnected:
      • UE shall set the value of SS-RSRPRefStationaryConnected to the current SS-RSRP value of the serving cell.
Up

5.7.4a  Void

5.7.5  Failure information  p. 336

5.7.5.1  General  p. 336

Reproduction of 3GPP TS 38.331, Fig. 5.7.5.1-1: Failure information
Figure 5.7.5.1-1: Failure information
Up
The purpose of this procedure is to inform the network about a failure detected by the UE.

5.7.5.2  Initiation  p. 336

A UE initiates the procedure when there is a need inform the network about a failure detected by the UE. In particular, the UE initiates the procedure when the following condition is met:
1 >
upon detecting failure for an RLC bearer, in accordance with clause 5.3.10.3;
1 >
upon detecting DAPS handover failure, in accordance with clause 5.3.5.8.3;
Upon initiating the procedure, the UE shall:
1 >
initiate transmission of the FailureInformation message as specified in clause 5.7.5.3;
Up

5.7.5.3  Actions related to transmission of FailureInformation message  p. 336

The UE shall:
1 >
if initiated to provide RLC failure information, set FailureInfoRLC-Bearer as follows:
2 >
set logicalChannelIdentity to the logical channel identity of the failing RLC bearer;
2 >
set cellGroupId to the cell group identity of the failing RLC bearer;
2 >
set the failureType as rlc-failure;
1 >
if initiated to provide DAPS failure information, set FailureInfoDAPS as follows:
2 >
set the failureType as daps-failure;
1 >
if used to inform the network about a failure for an MCG RLC bearer or DAPS failure information:
2 >
submit the FailureInformation message to lower layers for transmission via SRB1;
1 >
else if used to inform the network about a failure for an SCG RLC bearer:
2 >
if SRB3 is configured;
3 >
submit the FailureInformation message to lower layers for transmission via SRB3;
2 >
else;
3 >
if the UE is in (NG)EN-DC:
4 >
submit the FailureInformation message via E-UTRA SRB1 embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331.
3 >
else if the UE is in NR-DC:
4 >
submit the FailureInformation message via SRB1 embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3.
Up

5.7.6  DL message segment transfer  p. 337

5.7.6.1  General  p. 337

Reproduction of 3GPP TS 38.331, Fig. 5.7.6.1-1: DL message segment transfer
Figure 5.7.6.1-1: DL message segment transfer
Up
The purpose of this procedure is to transfer segments of DL DCCH messages from the network to the UE.

5.7.6.2  Initiation  p. 337

The network initiates the DL Dedicated Message Segment transfer procedure whenever the encoded RRC message PDU exceeds the maximum PDCP SDU size. The network initiates the DL Dedicated Message Segment transfer procedure by sending the DLDedicatedMessageSegment message.

5.7.6.3  Reception of DLDedicatedMessageSegment by the UE  p. 337

Upon receiving DLDedicatedMessageSegment message, the UE shall:
1 >
store the segment included in rrc-MessageSegmentContainer;
1 >
if all segments of the message have been received:
2 >
assemble the message from the received segments and process the message according to clause 5.3.5.3 for the RRCReconfiguration message or clause 5.3.13.4 for the RRCResume message;
2 >
discard all segments.
Up

5.7.7  UL message segment transfer  p. 338

5.7.7.1  General  p. 338

Reproduction of 3GPP TS 38.331, Fig. 5.7.7.1-1: UL message segment transfer
Figure 5.7.7.1-1: UL message segment transfer
Up
The purpose of this procedure is to transfer segments of UL DCCH messages from UE to a NG-RAN in RRC_CONNECTED.

5.7.7.2  Initiation  p. 338

A UE capable of UL RRC message segmentation in RRC_CONNECTED will initiate the procedure when the following conditions are met:
1 >
if the RRC message segmentation is enabled based on the field rrc-SegAllowed, rrc-SegAllowedSRB4 or rrc-SegAllowedSRB5 received, and
1 >
if the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 38.323;
Upon initiating the procedure, the UE shall:
1 >
initiate transmission of the ULDedicatedMessageSegment message as specified in clause 5.7.7.3;
Up

5.7.7.3  Actions related to transmission of ULDedicatedMessageSegment message  p. 338

The UE shall segment the encoded RRC PDU based on the maximum supported size of a PDCP SDU specified in TS 38.323. UE shall minimize the number of segments and set the contents of the ULDedicatedMessageSegment messages as follows:
1 >
For each new UL DCCH message, set the segmentNumber to 0 for the first message segment and increment the segmentNumber for each subsequent RRC message segment;
1 >
set rrc-MessageSegmentContainer to include the segment of the UL DCCH message corresponding to the segmentNumber;
1 >
if the segment included in the rrc-MessageSegmentContainer is the last segment of the UL DCCH message:
2 >
set the rrc-MessageSegmentType to lastSegment;
1 >
else:
2 >
set the rrc-MessageSegmentType to notLastSegment;
1 >
submit all the ULDedicatedMessageSegment messages generated for the segmented RRC message to lower layers for transmission in ascending order based on the segmentNumber, upon which the procedure ends.
Up

Up   Top   ToC