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.0.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.12 IAB Other Information  5.7.12.1 General  5.7.12.2 Initiation  5.7.12.3 Actions related to transmission of IABOtherInformation message  5.7.13 RLM/BFD relaxation  5.7.13.1 Relaxed measurement criterion for low mobility  5.7.13.2 Relaxed measurement criterion for good serving cell quality  5.7.14 UE Positioning Assistance Information  5.7.14.1 General  5.7.14.2 Initiation  5.7.14.3 Actions related to transmission of UEPositioningAssistanceInfo message  5.7.16 Application layer measurement reporting  5.7.16.1 General  5.7.16.2 Initiation  5.7.17 Derivation of pathloss reference for TA validation of SRS for Positioning transmission and CG-SDT in RRC_INACTIVE  5.7.18 Actions for SRS for Positioning transmission in RRC_INACTIVE in a Validity Area  5.7.19 Satellite switch with re-synchronization in RRC_CONNECTED 
...

 

5.7.12  IAB Other Information  p. 348

5.7.12.1  General  p. 348

Reproduction of 3GPP TS 38.331, Fig. 5.7.12.1-1: IAB Other Information procedure
Figure 5.7.12.1-1: IAB Other Information procedure
Up
The IAB Other Information procedure is used by IAB-MT to request the IAB-donor-CU to allocate IP address or inform the IAB-donor-CU of the IP address for the collocated IAB-DU.

5.7.12.2  Initiation  p. 348

Upon initiation of the procedure, the IAB-MT shall:
1 >
initiate transmission of the IABOtherInformation message in accordance with clause 5.7.12.3;

5.7.12.3  Actions related to transmission of IABOtherInformation message  p. 348

The IAB-MT shall set the contents of IABOtherInformation message as follows:
1 >
if the procedure is used to request IP addresses:
2 >
if IPv4 addresses are requested:
3 >
set the iab-IPv4-AddressNumReq to the number of IPv4 addresses requested per specific usage;
2 >
if IPv6 addresses or IPv6 address prefixes are requested:
3 >
if IPv6 addresses are requested:
4 >
set the iab-IPv6-AddressNumReq to the number of IPv6 addresses requested per specific usage;
3 >
else if IPv6 address prefixes are requested:
4 >
set the iab-IPv6-AddressPrefixReq to true per specific usage;
1 >
if the procedure is used to report IP addresses:
2 >
if IPv4 addresses are reported:
3 >
include iPv4-Address in iab-IPv4-AddressReport, and for each IP address included:
4 >
if IPv4 addresses are used for F1-C traffic:
5 >
include these addresses in f1-C-Traffic-IP-Address.
4 >
if IPv4 addresses are used for F1-U traffic:
5 >
include these addresses in f1-U-Traffic-IP-Address.
4 >
if IPv4 address are used for non-F1 traffic:
5 >
include these addresses in non-f1-Traffic-IP-Address.
4 >
if IPv4 addresses are used for all traffic:
5 >
include these addresses in all-Traffic-IAB-IP-Address.
2 >
if IPv6 addresses or IPv6 address prefixes are reported:
3 >
if IPv6 addresses are reported:
4 >
include iPv6-Address in iab-IPv6-AddressReport, and for each IP address included;
5 >
if IPv6 addresses are used for F1-C traffic:
6 >
include these addresses in f1-C-Traffic-IP-Address.
5 >
if IPv6 addresses are used for F1-U traffic:
6 >
include these addresses in f1-U-Traffic-IP-Address.
5 >
if IPv6 addresses are used for non-F1 traffic:
6 >
include these addresses in non-f1-Traffic-IP-Address.
5 >
if IPv6 addresses are used for all traffic:
6 >
include these addresses in all-Traffic-IAB-IP-Address.
3 >
else if IPv6 address prefixes are reported:
4 >
include these iPv6-Prefix in iab-IPv6-PrefixReport, and for each IP address prefix included;
5 >
if this IPv6 address prefix is used for F1-C traffic:
6 >
include this prefix in f1-C-Traffic-IP-Address.
5 >
if this IPv6 address prefix is used for F1-U traffic:
6 >
include this prefix in f1-U-Traffic-IP-Address.
5 >
if this IPv6 address prefix is used for non-F1 traffic:
6 >
include this prefix in non-f1-Traffic-IP-Address.
5 >
if this IPv6 address prefix is used for all traffic:
6 >
include this prefix in all-Traffic-IAB-IP-Address.
1 >
if the IAB-MT is in (NG)EN-DC, or
1 >
if the IAB-MT is in NR-DC and the IAB Other Information procedure is towards the IAB-donor-CU in the SN:
2 >
if SRB3 is configured:
3 >
submit the IABOtherInformation message via SRB3 to lower layers for transmission;
2 >
else if the IAB-MT is in (NG)EN-DC:
3 >
submit the IABOtherInformation message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331;
2 >
else:
3 >
submit the IABOtherInformation message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3;
1 >
else:
2 >
submit the IABOtherInformation message to lower layers for transmission.
Up

5.7.13  RLM/BFD relaxation  p. 350

In case both low mobility criterion and good serving cell criterion are configured for RLM/BFD relaxation, the UE is allowed to perform RLM and/or BFD relaxation according to requirements specified in TS 38.133 when both relaxed measurement criterion for low mobility and relaxed measurement criterion for good serving cell quality are met.
In case only the good serving cell quality criterion is configured for RLM/BFD relaxation, the UE is allowed to perform RLM and/or BFD relaxation according to requirements specified in TS 38.133 when the relaxed measurement criterion for good serving cell quality is met.
Up

5.7.13.1  Relaxed measurement criterion for low mobility  p. 350

The relaxed measurement criterion for UE with low mobility in RRC_CONNECTED is fulfilled when:
  • (SS-RSRPRef - SS-RSRP) <SSearchDeltaP-Connected,
Where:
  • SS-RSRP = current L3 RSRP measurement of the SpCell based on SSB (dB).
  • SS-RSRPRef = reference L3 RSRP measurement of the SpCell based on SSB (dB), set as follows:
  • After receiving low mobility criterion configuration, or
  • After MAC of the CG successfully completes a Random Access procedure after applying a reconfigurationWithSync in spCellConfig of the CG while low mobility criterion is configured, or
  • If (SS-RSRP - SS-RSRPRef) > 0, or
  • If the relaxed measurement criterion has not been met for TSearchDeltaP-Connected:
    • The UE shall set the value of SS-RSRPRef to the current SS-RSRP value of the SpCell.
Up

5.7.13.2  Relaxed measurement criterion for good serving cell quality  p. 350

The relaxed measurement criterion of good serving cell quality for RLM is fulfilled when the downlink radio link quality on the configured RLM-RS resource is evaluated to be better than the threshold Qin+XdB, wherein
  • Qin is specified in clause 8.1 of TS 38.133.
  • X is the parameter offset in goodServingCellEvaluationRLM for the evaluated serving cell.
    The relaxed measurement criterion of good serving cell quality for BFD is fulfilled when the downlink radio link quality on the configured BFD-RS resource is evaluated to be better than the threshold Qin+XdB, wherein
  • Qin is specified in clause 8.1 of TS 38.133.
  • X is the parameter offset in goodServingCellEvaluationBFD for the evaluated serving cell.
Up

5.7.14  UE Positioning Assistance Information  p. 350

5.7.14.1  General  p. 350

Reproduction of 3GPP TS 38.331, Fig. 5.7.14.1-1: UE Positioning Assistance Information procedure
Figure 5.7.14.1-1: UE Positioning Assistance Information procedure
Up
The UE Positioning Assistance Information procedure is used by UE to report the UE Positioning Assistance Information. The UE reports the association between SRS resources for positioning and the UE Tx TEG ID as defined in TS 38.305.

5.7.14.2  Initiation  p. 351

A UE capable of providing the association between SRS resource for positioning and UE Tx TEG ID in RRC_CONNECTED may initiate the procedure upon being configured to provide this association information.
Upon initiation of the procedure, the UE shall:
1 >
initiate transmission of the UEPositioningAssistanceInfo message in accordance with clause 5.7.14.3 to provide the association.

5.7.14.3  Actions related to transmission of UEPositioningAssistanceInfo message  p. 351

The UE shall set the contents of the UEPositioningAssistanceInfo message as follows:
1 >
if ue-TxTEG-RequestUL-TDOA-Config in RRCReconfiguration message is configured with periodicReporting:
2 >
for all the association changes store ue-TxTEG-Association corresponding to each ue-TxTEG-ID with nr-TimeStamp;
2 >
include the results in ue-TxTEG-AssociationList in the UEPositioningAssistanceInfo message on expiry of each configured period;
2 >
optionally include one ue-TxTEG-TimingErrorMarginValue for each UEPositioningAssistanceInfo message;
1 >
else if ue-TxTEG-RequestUL-TDOA-Config in RRCReconfiguration message is configured with oneShot:
2 >
identify the ue-TxTEG-Association corresponding to each ue-TxTEG-ID with nr-TimeStamp;
2 >
include the results in ue-TxTEG-AssociationList in the UEPositioningAssistanceInfo message only one time;
2 >
optionally include one ue-TxTEG-TimingErrorMarginValue for each UEPositioningAssistanceInfo message.
The UE shall submit the UEPositioningAssistanceInfo message to lower layers for transmission.
Up

5.7.15  Void

5.7.16  Application layer measurement reporting  p. 351

5.7.16.1  General  p. 351

Reproduction of 3GPP TS 38.331, Fig. 5.7.16.1-1: Application layer measurement reporting
Figure 5.7.16.1-1: Application layer measurement reporting
Up
The purpose of this procedure is to send application layer measurement reports to the network.

5.7.16.2  Initiation  p. 351

A UE capable of application layer measurement reporting in RRC_CONNECTED may initiate the procedure when configured with application layer measurement, i.e. when appLayerMeasConfig and SRB4 and/or SRB5 have been configured by the network.
Upon initiating the procedure, the UE shall:
1 >
for each measConfigAppLayerId received from upper layers:
2 >
if the UE AS has received application layer measurement report container from upper layers which has not been transmitted; and
2 >
if the application layer measurement reporting has not been suspended for the measConfigAppLayerId associated with the application layer measurement report container according to clause 5.3.5.13d:
3 >
set the measReportAppLayerContainer in the MeasurementReportAppLayer message to the received value in the application layer measurement report container;
2 >
set the measConfigAppLayerId in the MeasurementReportAppLayer message to the value of the measConfigAppLayerId received together with application layer measurement report information;
2 >
if session start or stop information has been received from upper layers for the measConfigAppLayerId:
3 >
set the appLayerSessionStatus in the MeasurementReportAppLayer message to the received value of session start or stop information;
2 >
if reportingSRB and ran-VisibleReportingSRB are different for the measConfigAppLayerId:
3 >
include measReportAppLayerContainer and appLayerSessionStatus in a different MeasurementReportAppLayer message than ran-VisibleMeasurements;
2 >
if RAN visible application layer measurement report has been received from upper layers:
3 >
for each appLayerBufferLevel value in the received RAN visible application layer measurement report:
4 >
set the appLayerBufferLevel values in the appLayerBufferLevelList in the MeasurementReportAppLayer message to the buffer level values received from the upper layer in the order with the first appLayerBufferLevel value set to the newest received buffer level value, the second appLayerBufferLevel value set to the second newest received buffer level value, and so on until all the buffer level values received from the upper layer have been assigned or the maximum number of values have been set according to appLayerBufferLevel, if configured;
3 >
set the playoutDelayForMediaStartup in the MeasurementReportAppLayer message to the received value of playout delay for media startup in the RAN visible application layer measurement report, if any;
3 >
for each PDU session ID value indicated in the received RAN visible application layer measurement report, if any:
4 >
set the PDU-SessionID in the pdu-SessionIdList in the MeasurementReportAppLayer message to the indicated PDU session ID value;
4 >
for each QoS Flow ID value indicated in the received RAN visible application layer measurement report associated with the PDU Session ID, if any:
5 >
set the QFI associated with the PDU session ID to the indicated QoS Flow ID value.
1 >
for each stored application layer measurement configuration with configforRRC-IdleInactive set to true and for which appLayerIdleInactiveConfig has not been transmitted since the UE entered RRC_CONNECTED:
2 >
set the parameters in appLayerIdleInactiveConfig in the MeasurementReportAppLayer message to the values stored in the UE variable VarAppLayerIdleConfig;
1 >
for each encoded MeasurementReportAppLayer message generated above:
2 >
if reportingSRB or ran-VisibleReportingSRB are not configured:
3 >
if the encoded RRC message is larger than the maximum supported size of one PDCP SDU specified in TS 38.323:
4 >
if the RRC message segmentation is enabled based on the field rrc-SegAllowed received in appLayerMeasConfig:
5 >
initiate the UL message segment transfer procedure as specified in clause 5.7.7;
4 >
else:
5 >
discard the RRC message;
3 >
else:
4 >
submit the MeasurementReportAppLayer message to lower layers for transmission.
2 >
else if reportingSRB or ran-VisibleReportingSRB are configured:
3 >
if the encoded RRC message is larger than the maximum supported size of one PDCP SDU specified in TS 38.323:
4 >
if the RRC message segmentation is enabled based on the field rrc-SegAllowedSRB4 received in appLayerMeasConfig and the reportingSRB is SRB4; or
4 >
if the RRC message segmentation is enabled based on the field rrc-SegAllowedSRB5 received in appLayerMeasConfig and the reportingSRB is SRB5:
5 >
initiate the UL message segment transfer procedure as specified in clause 5.7.7 via the SRB indicated in the field reportingSRB in MeasConfigAppLayer;
4 >
else:
5 >
discard the RRC message;
3 >
else:
4 >
submit the MeasurementReportAppLayer message to lower layers for transmission via the SRB indicated in the field reportingSRB or, if different from reportingSRB, ran-VisibleReportingSRB in MeasConfigAppLayer upon which the procedure ends.
Up

5.7.17  Derivation of pathloss reference for TA validation of SRS for Positioning transmission and CG-SDT in RRC_INACTIVE  p. 353

Upon request from lower layer for pathloss reference derivation for TA validation for SRS for Positioning transmission or CG-SDT in RRC_INACTIVE, the UE shall:
1 >
acquire SIB2, if stored version is invalid;
1 >
if nrofSS-BlocksToAverage or absThreshSS-BlocksConsolidation is not present or if absThreshSS-BlocksConsolidation is present and the highest beam measurement quantity value is below or equal to absThreshSS-BlocksConsolidation:
2 >
derive the downlink pathloss reference RSRP for TA validation as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215;
1 >
else:
2 >
derive the downlink pathloss reference RSRP for TA validation as the linear average of the power values of up to nrofSS-BlocksToAverage of the highest beam measurement quantity values above absThreshSS-BlocksConsolidation, where each beam measurement quantity is described in TS 38.215.
Up

5.7.18  Actions for SRS for Positioning transmission in RRC_INACTIVE in a Validity Area  p. 354

The UE may be configured or preconfigured with SRS for Positioning in a validity area defined by group of cells. There can be multiple preconfigured SRS for positioning that can be configured to UE where each preconfiguration belongs to different validity area. For each validity area, the UE is preconfigured with only one SRS for positioning configuration. For non-preconfigured SRS for positioning, only one validity area is configured.
When the UE is (pre)configured to transmit SRS for positioning in a validity area, the UE shall:
1 >
if the RS in spatialRelationInfoPos cannot be accurately measured:
2 >
suspend the transmission of the SRS for positioning resource and monitor the configured RS;
2 >
if the UE determines that RS in spatialRelationInfoPos being accurately measured:
3 >
resume the SRS transmission.
The UE releases the (pre)configured SRS for positioning with validity area upon receiving RRCRelease message with the indication to release the (pre)configuration.
Up

5.7.19  Satellite switch with re-synchronization in RRC_CONNECTED  p. 354

The UE shall:
1 >
stop timer T430 if running;
1 >
inform lower layers that UL synchronisation is lost due to satellite switch with re-synchronization;
1 >
start re-synchronising to the DL of the SpCell served by the satellite indicated by ntn-Config in SatSwitchWithReSync;
1 >
start timer T430 with the timer value set to ntn-UlSyncValidityDuration from the subframe indicated by epochTime in ntn-Config in SatSwitchWithReSync;
1 >
inform lower layers when UL synchronisation is obtained.
Up

Up   Top   ToC