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:  17.6.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.6…   5.3.8…   5.3.13…   5.3.14…   5.4…   5.5…   5.5.3…   5.5.4…   5.5.5…   5.5a…   5.7…   5.7.4…   5.7.8…   5.8…   5.8.9…   5.8.10…   5.8.11…   5.9…   6…   6.2.2…   6-2-2-25…   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.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.5a Logged Measurements  5.5a.1 Logged Measurement Configuration  5.5a.1.1 General  5.5a.1.2 Initiation  5.5a.1.3 Reception of the LoggedMeasurementConfiguration by the UE  5.5a.1.4 T330 expiry  5.5a.2 Release of Logged Measurement Configuration  5.5a.2.1 General  5.5a.2.2 Initiation  5.5a.3 Measurements logging  5.5a.3.1 General  5.5a.3.2 Initiation  5.6 UE capabilities  5.6.1 UE capability transfer  5.6.1.1 General  5.6.1.2 Initiation  5.6.1.3 Reception of the UECapabilityEnquiry by the UE  5.6.1.4 Setting band combinations, feature set combinations and feature sets supported by the UE 
...

 

5.5a  Logged Measurements  p. 222

5.5a.1  Logged Measurement Configuration  p. 222

5.5a.1.1  General  p. 222

Reproduction of 3GPP TS 38.331, Fig. 5.5a.1.1-1: Logged measurement configuration
Figure 5.5a.1.1-1: Logged measurement configuration
Up
The purpose of this procedure is to configure the UE to perform logging of measurement results while in RRC_IDLE and RRC_INACTIVE. The procedure applies to logged measurements capable UEs that are in RRC_CONNECTED.

5.5a.1.2  Initiation  p. 222

NG-RAN initiates the logged measurement configuration procedure to UE in RRC_CONNECTED by sending the LoggedMeasurementConfiguration message.

5.5a.1.3  Reception of the LoggedMeasurementConfiguration by the UE  p. 222

Upon receiving the LoggedMeasurementConfiguration message the UE shall:
1 >
discard the logged measurement configuration as well as the logged measurement information as specified in clause 5.5a.2;
1 >
store the received loggingDuration, reportType and areaConfiguration, if included, in VarLogMeasConfig;
1 >
if the LoggedMeasurementConfiguration message includes plmn-IdentityList:
2 >
set plmn-IdentityList in VarLogMeasReport to include the RPLMN as well as the PLMNs included in plmn-IdentityList;
1 >
else:
2 >
set plmn-IdentityList in VarLogMeasReport to include the RPLMN;
1 >
store the received absoluteTimeInfo, traceReference, traceRecordingSessionRef, and tce-Id in VarLogMeasReport;
1 >
store the received bt-NameList, if included, in VarLogMeasConfig;
1 >
store the received wlan-NameList, if included, in VarLogMeasConfig;
1 >
store the received sensor-NameList, if included, in VarLogMeasConfig;
1 >
start timer T330 with the timer value set to the loggingDuration;
1 >
store the received sigLoggedMeasType, if included, in VarLogMeasReport;
1 >
store the received earlyMeasIndication, if included, in VarLogMeasConfig;
Up

5.5a.1.4  T330 expiry  p. 223

Upon expiry of T330 the UE shall:
1 >
release VarLogMeasConfig;
The UE is allowed to discard stored logged measurements, i.e. to release VarLogMeasReport, 48 hours after T330 expiry.

5.5a.2  Release of Logged Measurement Configuration  p. 223

5.5a.2.1  General  p. 223

The purpose of this procedure is to release the logged measurement configuration as well as the logged measurement information.

5.5a.2.2  Initiation  p. 223

The UE shall initiate the procedure upon receiving a logged measurement configuration in same or another RAT. The UE shall also initiate the procedure upon power off or upon deregistration.
The UE shall:
1 >
stop timer T330, if running;
1 >
if stored, discard the logged measurement configuration as well as the logged measurement information, i.e. release the UE variables VarLogMeasConfig and VarLogMeasReport.

5.5a.3  Measurements logging  p. 223

5.5a.3.1  General  p. 223

This procedure specifies the logging of available measurements by a UE in RRC_IDLE and RRC_INACTIVE that has a logged measurement configuration. The actual process of logging within the UE, takes place in RRC IDLE state could continue in RRC INACTIVE state or vice versa.

5.5a.3.2  Initiation  p. 223

While T330 is running and SDT procedure is not ongoing, the UE shall:
1 >
if measurement logging is suspended:
2 >
if during the last logging interval the IDC problems detected by the UE is resolved, resume measurement logging;
1 >
if not suspended, perform the logging in accordance with the following:
2 >
if the reportType is set to periodical in the VarLogMeasConfig:
3 >
if the UE is in any cell selection state (as specified in TS 38.304):
4 >
perform the logging at regular time intervals, as defined by the loggingInterval in the VarLogMeasConfig;
3 >
if the UE is in camped normally state on an NR cell and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:
4 >
if areaConfiguration is not included in VarLogMeasConfig; or
4 >
if the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig:
5 >
perform the logging at regular time intervals, as defined by the loggingInterval in the VarLogMeasConfig;
2 >
else if the reportType is set to eventTriggered, and eventType is set to outOfCoverage:
3 >
perform the logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig only when the UE is in any cell selection state;
3 >
upon transition from any cell selection state to camped normally state in NR:
4 >
if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport; and
4 >
if areaConfiguration is not included in VarLogMeasConfig or if the current camping cell is part of the area indicated by areaConfig of areaConfiguration in VarLogMeasConfig:
5 >
perform the logging;
2 >
else if the reportType is set to eventTriggered and eventType is set to eventL1:
3 >
if the UE is in camped normally state on an NR cell and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:
4 >
if areaConfiguration is not included in VarLogMeasConfig; or
4 >
if the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig;
5 >
perform the logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig only when the conditions indicated by the eventL1 are met;
2 >
when performing the logging:
3 >
if InterFreqTargetInfo is configured and if the UE detected IDC problems on at least one of the frequencies included in InterFreqTargetInfo or any inter-RAT frequency during the last logging interval, or
3 >
if InterFreqTargetInfo is not configured and if the UE detected IDC problems during the last logging interval:
4 >
if measResultServingCell in the VarLogMeasReport is not empty:
5 >
include inDeviceCoexDetected;
5 >
suspend measurement logging from the next logging interval;
4 >
else:
5 >
suspend measurement logging;
3 >
set the relativeTimeStamp to indicate the elapsed time since the moment at which the logged measurement configuration was received;
3 >
if location information became available during the last logging interval, set the content of the locationInfo as in clause 5.3.3.7:
3 >
if the UE is in any cell selection state (as specified in TS 38.304):
4 >
set anyCellSelectionDetected to indicate the detection of no suitable or no acceptable cell found;
4 >
if the reportType is set to eventTriggered in the VarLogMeasConfig; and
4 >
if the RPLMN at the time of entering the any cell selection state is included in plmn-IdentityList stored in VarLogMeasReport; and
4 >
if areaConfiguration is not included in VarLogMeasConfig or if the last suitable cell that the UE was camping on is part of the area indicated by areaConfig of areaConfiguration in VarLogMeasConfig:
5 >
set the servCellIdentity to indicate global cell identity of the last suitable cell that the UE was camping on;
5 >
set the measResultServingCell to include the quantities of the last suitable cell the UE was camping on;
4 >
else if the reportType is set to periodical in the VarLogMeasConfig:
5 >
set the servCellIdentity to indicate global cell identity of the last logged cell that the UE was camping on;
5 >
set the measResultServingCell to include the quantities of the last logged cell the UE was camping on;
3 >
else:
4 >
set the servCellIdentity to indicate global cell identity of the cell the UE is camping on;
4 >
set the measResultServingCell to include the quantities of the cell the UE is camping on;
3 >
if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-selection, to include measurements of neighbouring cell that became available during the last logging interval and according to the following:
4 >
include measurement results for at most 6 neighbouring cells on the NR serving frequency and for at most 3 cells per NR neighbouring frequency and for the NR neighbouring frequencies in accordance with the following:
5 >
if interFreqTargetInfo is included in VarLogMeasConfig:
6 >
if earlyMeasIndication is included in VarLogMeasConfig;
7 >
include measurement results for NR neighbouring frequencies that are included in both interFreqTargetInfo and either in measIdleCarrierListNR (within the VarMeasIdleConfig) or SIB4;
6 >
else:
7 >
include measurement results for NR neighbouring frequencies that are included in both interFreqTargetInfo and SIB4;
5 >
else:
6 >
if earlyMeasIndication is included in VarLogMeasConfig;
7 >
include measurement results for NR neighbouring frequencies that are included in either measIdleCarrierListNR (within the VarMeasIdleConfig) or SIB4;
6 >
else:
7 >
include measurement results for NR neighbouring frequencies that are included in SIB4;
4 >
include measurement results for at most 3 neighbours per inter-RAT frequency in accordance with the following:
5 >
if earlyMeasIndication is included in VarLogMeasConfig:
6 >
include measurement results for inter-RAT neighbouring frequencies that are included in either measIdleCarrierListEUTRA (within the VarMeasIdleConfig) or SIB5;
5 >
else:
6 >
include measurement results for inter-RAT frequencies that are included in SIB5;
4 >
for each neighbour cell included, include the optional fields that are available;
2 >
when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330, as specified in clause 5.5a.1.4.
Up

5.6  UE capabilities  p. 226

5.6.1  UE capability transfer  p. 226

5.6.1.1  General  p. 226

This clause describes how the UE compiles and transfers its UE capability information upon receiving a UECapabilityEnquiry from the network.
Reproduction of 3GPP TS 38.331, Fig. 5.6.1.1-1: UE capability transfer
Figure 5.6.1.1-1: UE capability transfer
Up

5.6.1.2  Initiation  p. 226

The network initiates the procedure to a UE in RRC_CONNECTED when it needs (additional) UE radio access capability information. The network should retrieve UE capabilities only after AS security activation. Network does not forward UE capabilities that were retrieved before AS security activation to the CN.

5.6.1.3  Reception of the UECapabilityEnquiry by the UE  p. 226

The UE shall set the contents of UECapabilityInformation message as follows:
1 >
if the ue-CapabilityRAT-RequestList contains a UE-CapabilityRAT-Request with rat-Type set to nr:
2 >
include in the ue-CapabilityRAT-ContainerList a UE-CapabilityRAT-Container of the type UE-NR-Capability and with the rat-Type set to nr;
2 >
include the supportedBandCombinationList, featureSets and featureSetCombinations as specified in clause 5.6.1.4;
1 >
if the ue-CapabilityRAT-RequestList contains a UE-CapabilityRAT-Request with rat-Type set to eutra-nr:
2 >
if the UE supports (NG)EN-DC or NE-DC:
3 >
include in the ue-CapabilityRAT-ContainerList a UE-CapabilityRAT-Container of the type UE-MRDC-Capability and with the rat-Type set to eutra-nr;
3 >
include the supportedBandCombinationList and featureSetCombinations as specified in clause 5.6.1.4;
1 >
if the ue-CapabilityRAT-RequestList contains a UE-CapabilityRAT-Request with rat-Type set to eutra:
2 >
if the UE supports E-UTRA:
3 >
include in the ue-CapabilityRAT-ContainerList a ue-CapabilityRAT-Container of the type UE-EUTRA-Capability associated with the terrestrial network and with the rat-Type set to eutra as specified in clause 5.6.3.3 of TS 36.331, according to the capabilityRequestFilter, if received;
1 >
if the ue-CapabilityRAT-RequestList contains a UE-CapabilityRAT-Request with rat-Type set to utra-fdd:
2 >
if the UE supports UTRA-FDD:
3 >
include the UE radio access capabilities for UTRA-FDD within a ue-CapabilityRAT-Container and with the rat-Type set to utra-fdd;
1 >
if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 38.323:
2 >
initiate the UL message segment transfer procedure as specified in clause 5.7.7;
1 >
else:
2 >
submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends.
Up

5.6.1.4  Setting band combinations, feature set combinations and feature sets supported by the UE  p. 227

The UE invokes the procedures in this clause if the NR or E-UTRA network requests UE capabilities for nr, eutra-nr or eutra. This procedure is invoked once per requested rat-Type (see clause 5.6.1.3 for capability enquiry by the NR network; see clause 5.6.3.3 of TS 36.331 for capability enquiry by the E-UTRA network). The UE shall ensure that the feature set IDs are consistent across feature sets, feature set combinations and band combinations in all three UE capability containers that the network queries with the same fields with the same values, i.e. UE-CapabilityRequestFilterNR, UE-CapabilityRequestFilterCommon and fields in UECapabilityEnquiry message (i.e. requestedFreqBandsNR-MRDC, requestedCapabilityNR, eutra-nr-only flag, and requestedCapabilityCommon) as defined in TS 36.331, where applicable.
The UE shall:
1 >
compile a list of "candidate band combinations" according to the filter criteria in capabilityRequestFilterCommon (if included), only consisting of bands included in frequencyBandListFilter, and prioritized in the order of frequencyBandListFilter (i.e. first include band combinations containing the first-listed band, then include remaining band combinations containing the second-listed band, and so on), where for each band in the band combination, the parameters of the band do not exceed maxBandwidthRequestedDL, maxBandwidthRequestedUL, maxCarriersRequestedDL, maxCarriersRequestedUL, ca-BandwidthClassDL-EUTRA or ca-BandwidthClassUL-EUTRA, whichever are received;
1 >
for each band combination included in the list of "candidate band combinations":
2 >
if the network (E-UTRA) included the eutra-nr-only field, or
2 >
if the requested rat-Type is eutra:
3 >
remove the NR-only band combination from the list of "candidate band combinations";
2 >
if it is regarded as a fallback band combination with the same capabilities of another band combination included in the list of "candidate band combinations", and
2 >
if this fallback band combination is generated by releasing at least one SCell or uplink configuration of SCell or SUL according to TS 38.306:
3 >
remove the band combination from the list of "candidate band combinations";
1 >
if the requested rat-Type is nr:
2 >
include into supportedBandCombinationList as many NR-only band combinations as possible from the list of "candidate band combinations", starting from the first entry;
3 >
if srs-SwitchingTimeRequest is received:
4 >
if SRS carrier switching is supported;
5 >
include srs-SwitchingTimesListNR and srs-SwitchingAffectedBandsListNR for each band combination;
4 >
set srs-SwitchingTimeRequested to true;
2 >
include, into featureSetCombinations, the feature set combinations referenced from the supported band combinations as included in supportedBandCombinationList according to the previous;
2 >
compile a list of "candidate feature set combinations" referenced from the list of "candidate band combinations" excluding entries (rows in feature set combinations) with same or lower capabilities;
2 >
if uplinkTxSwitchRequest is received:
3 >
include into supportedBandCombinationList-UplinkTxSwitch as many NR-only band combinations that supported UL TX switching as possible from the list of "candidate band combinations", starting from the first entry;
4 >
if srs-SwitchingTimeRequest is received:
5 >
if SRS carrier switching is supported;
6 >
include srs-SwitchingTimesListNR and srs-SwitchingAffectedBandsListNR for each band combination;
5 >
set srs-SwitchingTimeRequested to true;
3 >
include, into featureSetCombinations, the feature set combinations referenced from the supported band combinations as included in supportedBandCombinationList-UplinkTxSwitch according to the previous;
2 >
if sidelinkRequest is received:
3 >
for a sidelink band combination the UE included in supportedBandCombinationListSidelinkEUTRA-NR, supportedBandCombinationListSL-RelayDiscovery or supportedBandCombinationListSL-NonRelayDiscovery:
4 >
if the UE supports partial sensing for a band of the sidelink band combination, include the partial sensing capabilities for the band using the sl-TransmissionMode2-PartialSensing-r17;
3 >
set sidelinkRequested to true;
2 >
include into featureSets the feature sets referenced from the "candidate feature set combinations" and may exclude the feature sets with the parameters that exceed any of maxBandwidthRequestedDL, maxBandwidthRequestedUL, maxCarriersRequestedDL or maxCarriersRequestedUL, whichever are received;
1 >
else, if the requested rat-Type is eutra-nr:
2 >
include into supportedBandCombinationList and/or supportedBandCombinationListNEDC-Only as many E-UTRA-NR band combinations as possible from the list of "candidate band combinations", starting from the first entry;
3 >
if srs-SwitchingTimeRequest is received:
4 >
if SRS carrier switching is supported;
5 >
include srs-SwitchingTimesListNR, srs-SwitchingTimesListEUTRA and srs-SwitchingAffectedBandsListNR for each band combination;
4 >
set srs-SwitchingTimeRequested to true;
2 >
include, into featureSetCombinations, the feature set combinations referenced from the supported band combinations as included in supportedBandCombinationList according to the previous;
2 >
if uplinkTxSwitchRequest is received:
3 >
include into supportedBandCombinationList-UplinkTxSwitch as many E-UTRA-NR band combinations that supported UL TX switching as possible from the list of "candidate band combinations", starting from the first entry;
4 >
if srs-SwitchingTimeRequest is received:
5 >
if SRS carrier switching is supported;
6 >
include srs-SwitchingTimesListNR, srs-SwitchingTimesListEUTRA and srs-SwitchingAffectedBandsListNR for each band combination;
5 >
set srs-SwitchingTimeRequested to true;
3 >
include, into featureSetCombinations, the feature set combinations referenced from the supported band combinations as included in supportedBandCombinationList-UplinkTxSwitch according to the previous;
1 >
else (if the requested rat-Type is eutra):
2 >
compile a list of "candidate feature set combinations" referenced from the list of "candidate band combinations" excluding entries (rows in feature set combinations) with same or lower capabilities;
2 >
include into featureSetsEUTRA (in the UE-EUTRA-Capability) the feature sets referenced from the "candidate feature set combinations" and may exclude the feature sets with the parameters that exceed ca-BandwidthClassDL-EUTRA or ca-BandwidthClassUL-EUTRA, whichever are received;
1 >
include the received frequencyBandListFilter in the field appliedFreqBandListFilter of the requested UE capability, except if the requested rat-Type is nr and the network included the eutra-nr-only field;
1 >
if the network included ue-CapabilityEnquiryExt:
2 >
include the received ue-CapabilityEnquiryExt in the field receivedFilters;
Up

5.6.1.5  Void

Up   Top   ToC