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.3.5.17 MP configuration  5.3.5.17.1 Introduction  5.3.5.17.2 Configuration of SL indirect path  5.3.5.17.2.1 General  5.3.5.17.2.2 SL indirect path specific configuration  5.3.5.17.2.3 T421 expiry (Indirect path addition/change failure)  5.3.5.17.3 Configuration of N3C indirect path  5.3.5.17.3.1 General  5.3.5.17.3.2 N3C remote UE configuration  5.3.5.17.3.2a N3C Indirect path addition/change failure  5.3.5.17.3.3 N3C relay UE configuration  5.3.5.17.3.4 Bearer mapping management on N3C indirect path  5.3.5.17.3.4.1 Bearer mapping release  5.3.5.17.3.4.2 Bearer mapping addition and modification  5.3.5.18 LTM configuration and execution  5.3.5.18.1 LTM configuration  5.3.5.18.2 LTM candidate configuration release  5.3.5.18.3 LTM candidate configuration addition/modification  5.3.5.18.6 LTM cell switch execution  5.3.5.18.7 LTM configuration release  5.3.5.19 T348 expiry 
...

 

5.3.5.17  MP configuration  p. 160

5.3.5.17.1  Introduction  p. 160
In case of MP, a MP remote UE is configured with one direct path (i.e. MCG) and one indirect path. The MP remote UE connects to network on the direct path using NR Uu, and connects to network on the indirect path via a MP relay UE.
On indirect path, for the hop between the MP remote UE and the MP relay UE, when the MP remote UE connects to a L2 U2N Relay UE, i.e. the MP remote UE is acting as a L2 U2N Remote UE, the network provides the configuration of SL indirect path to the MP remote UE and the L2 U2N Relay UE as specified in clause 5.3.5.17.2; when the MP remote UE connects to a N3C relay UE using non-3GPP connection, the network provides the configuration of N3C indirect path to the MP remote UE and the N3C relay UE as specified in clause 5.3.5.17.3.
Up
5.3.5.17.2  Configuration of SL indirect path  p. 160
5.3.5.17.2.1  General  p. 160
For SL indirect path:
Up
5.3.5.17.2.2  SL indirect path specific configuration  p. 160
The L2 U2N Remote UE shall:
1 >
if sl-IndirectPathAddChange is set to setup:
2 >
consider the UE indicated by the sl-IndirectPathRelayUE-Identity to be the (target) L2 U2N Relay UE and indicate to upper layer to trigger the PC5 unicast link establishment with the L2 U2N Relay UE;
2 >
start timer T421 for the corresponding L2 U2N Relay UE with the timer value set to T421;
2 >
indicate to upper layer (to trigger the PC5 unicast link release) with the source L2 U2N Relay UE in case of SL indirect path change (i.e. a new L2 U2N Relay UE is indicated via sl-IndirectPathRelayUE-Identity);
1 >
else if sl-IndirectPathAddChange is set to release:
2 >
consider the SL indirect path is released and release the corresponding configurations;
2 >
indicate to upper layer (to trigger the PC5 unicast link release) with the L2 U2N Relay UE.
Up
5.3.5.17.2.3  T421 expiry (Indirect path addition/change failure)  p. 160
The UE shall:
1 >
if T421 expires; or
1 >
if the (target) L2 U2N Relay UE (i.e., the UE indicated by sl-IndirectPathRelayUE-Identity in the received sl-IndirectPathAddChange) changes its serving PCell to a different cell from the target cell (i.e. the cell indicated by sl-IndirectPathCellIdentity in the received sl-IndirectPathAddChange) before path addition or change:
2 >
if MCG transmission is not suspended:
3 >
initiate the indirect path failure information procedure as specified in clause 5.7.3c to report indirect path addition/change failure;
2 >
else:
3 >
initiate the connection re-establishment procedure as specified in clause 5.3.7;
Up
5.3.5.17.3  Configuration of N3C indirect path  p. 161
5.3.5.17.3.1  General  p. 161
For N3C indirect path,
  • the N3C remote UE is provided with N3C indirect path configuration including relay UE identification as specified in clause 5.3.5.17.3.2;
  • the N3C relay UE is provided with N3C indirect path configuration including bearer mapping configurations as specified in clause 5.3.5.17.3.4, as well as Uu Relay RLC channel configuration as specified in clause 5.3.5.5.12 and clause 5.3.5.5.13.
Up
5.3.5.17.3.2  N3C remote UE configuration  p. 161
The N3C remote UE shall:
1 >
if n3c-IndirectPathAddChange is set to setup:
2 >
consider the non-3GPP connection with the relay UE indicated by the n3c-RelayIdentification to be used for the N3C indirect path;
2 >
consider the source non-3GPP connection is not to be used in case of N3C indirect path change (i.e. a new relay UE is indicated by the n3c-RelayIdentification);
1 >
else if n3c-IndirectPathAddChange is set to release:
2 >
consider the indirect path is not to be used and release the corresponding configuration.
Up
5.3.5.17.3.2a  N3C Indirect path addition/change failure  p. 161
5.3.5.17.3.3  N3C relay UE configuration  p. 161
The N3C relay UE shall:
1 >
if n3c-IndirectPathConfigRelay is set to setup:
2 >
if n3c-MappingToReleaseList is included:
3 >
perform N3C bearer mapping release as specified in clause 5.3.5.17.3.4.1;
2 >
if n3c-MappingToAddModList is included:
3 >
perform N3C bearer mapping addition/modification as specified in clause 5.3.5.17.3.4.2;
1 >
else if n3c-IndirectPathConfigRelay is set to release:
2 >
consider the indirect path with the remote UE is released and release the corresponding configuration.
Up
5.3.5.17.3.4  Bearer mapping management on N3C indirect path  p. 162
5.3.5.17.3.4.1  Bearer mapping release  p. 162
The UE shall:
1 >
if the release is triggered by reception of n3c-IndirectPathConfigRelay set to release:
2 >
for all configured SL-RemoteUE-RB-Identity value:
3 >
release n3c-RLC-ChannelUu and n3c-RemoteUE-RB-Identity;
1 >
else if the release is triggered by reception of the n3c-MappingToReleaseList:
2 >
for each SL-RemoteUE-RB-Identity value included in n3c-MappingToReleaseList:
3 >
release the corresponding n3c-RLC-ChannelUu and n3c-RemoteUE-RB-Identity;
5.3.5.17.3.4.2  Bearer mapping addition and modification  p. 162
The UE shall:
1 >
for each n3c-RemoteUE-RB-Identity value included in the n3c-MappingToAddModList that is not part of the current UE configuration:
2 >
associate the remote UE's RB indicated in n3c-RemoteUE-RB-Identity to the Uu RLC channel indicated in n3c-RLC-ChannelUu;
1 >
for the n3c-RemoteUE-RB-Identity value included in the n3c-MappingToAddModList that is part of the current UE configuration:
2 >
update the associated Uu RLC channel to the one indicated in n3c-RLC-ChannelUu.

5.3.5.18  LTM configuration and execution  p. 162

5.3.5.18.1  LTM configuration  p. 162
The network configures the UE with one or more LTM candidate configurations within the LTM-Config IE.
In NR-DC, the UE may receive two independent ltm-Config:
  • an ltm-Config associated with the MCG that is included within an RRCReconfiguration message received via SRB1; and
  • an ltm-Config associated with the SCG that is included within an RRCReconfiguration message either received via SRB3, or, alternatively, embedded in an RRCReconfiguration message received via SRB1.
In case the UE receives two independent ltm-Config:
  • the UE maintains two independent VarLTM-Config, one associated with each ltm-Config;
  • the UE maintains two independent VarLTM-ServingCellNoResetID, one associated with each ltm-Config;
  • the UE maintains two independent VarLTM-ServingCellUE-MeasuredTA-ID, one associated with each ltm-Config;
  • the UE independently performs all the procedures in clause 5.3.5.18 for each ltm-Config and the associated VarLTM-Config, VarLTM-ServingCellNoResetID, and VarLTM-ServingCellUE-MeasuredTA-ID unless explicitly stated otherwise.
The UE shall perform the following actions based on the received LTM-Config IE:
1 >
if the received LTM-Config includes ltm-ReferenceConfiguration set to setup:
2 >
if the current VarLTM-Config includes an ltm-ReferenceConfiguration:
3 >
replace the ltm-ReferenceConfiguration value within VarLTM-Config with the received ltm-ReferenceConfiguration;
2 >
else:
3 >
store the received ltm-ReferenceConfiguration in VarLTM-Config;
1 >
else (the received LTM-Config includes ltm-ReferenceConfiguration set to release):
2 >
remove ltm-ReferenceConfiguration in VarLTM-Config;
1 >
if the received LTM-Config includes ltm-ServingCellNoResetID:
2 >
if the current VarLTM-ServingCellNoResetID includes an ltm-ServingCellNoResetID:
3 >
replace the ltm-ServingCellNoResetID value within VarLTM-ServingCellNoResetID with the received ltm-ServingCellNoResetID;
2 >
else:
3 >
store the received ltm-ServingCellNoResetID in VarLTM-ServingCellNoResetID;
1 >
if the received LTM-Config includes ltm-ServingCellUE-MeasuredTA-ID:
2 >
if the current VarLTM-ServingCellUE-MeasuredTA-ID includes an ltm-ServingCellUE-MeasuredTA-ID:
3 >
replace the ltm-ServingCellUE-MeasuredTA-ID value within VarLTM-ServingCellUE-MeasuredTA-ID with the received ltm-ServingCellUE-MeasuredTA-ID;
2 >
else:
3 >
store the received ltm-ServingCellUE-MeasuredTA-ID in VarLTM-ServingCellUE-MeasuredTA-ID;
1 >
if the received LTM-Config includes ltm-CSI-ResourceConfigToReleaseList:
2 >
perform the LTM CSI resource configuration release as specified in clause 5.3.5.18.4;
1 >
if the received LTM-Config includes ltm-CSI-ResourceConfigToAddModList:
2 >
perform the LTM CSI resource configuration addition or modification as specified in clause 5.3.5.18.5;
1 >
if the received LTM-Config includes the ltm-CandidateToReleaseList:
2 >
perform the LTM candidate configuration release as specified in clause 5.3.5.18.2;
1 >
if the received LTM-Config includes the ltm-CandidateToAddModList:
2 >
perform the LTM candidate configuration addition or modification as specified in clause 5.3.5.18.3.
Up
5.3.5.18.2  LTM candidate configuration release  p. 163
The UE shall:
1 >
for each ltm-CandidateId value included in the ltm-CandidateToReleaseList for which there is an entry in ltm-CandidateList in VarLTM-Config:
2 >
remove the entry related to LTM-Candidate from VarLTM-Config.
5.3.5.18.3  LTM candidate configuration addition/modification  p. 163
The UE shall:
1 >
for each ltm-CandidateId value in the ltm-CandidateToAddModList:
2 >
if the current VarLTM-Config includes an LTM-Candidate with the ltm-CandidateId value:
3 >
replace the LTM-Candidate within VarLTM-Config in accordance with the received LTM-Candidate;
2 >
else:
3 >
add the received LTM-Candidate to VarLTM-Config;
2 >
if the received LTM-Candidate includes ltm-DL-OrJointTCI-StateToReleaseList:
3 >
for each tci-StateId in the ltm-DL-OrJointTCI-StateToReleaseList:
4 >
if the current VarLTM-Config includes a CandidateTCI-State within an LTM-Candidate with the ltm-CandidateId value that is associated with the tci-StateId value:
5 >
remove the entry related to CandidateTCI-State within the LTM-Candidate from VarLTM-Config.
2 >
if the received LTM-Candidate includes ltm-DL-OrJointTCI-StateToAddModList:
3 >
for each tci-StateId in the ltm-DL-OrJointTCI-StateToAddModList:
4 >
if the current VarLTM-Config includes a CandidateTCI-State within an LTM-Candidate with the ltm-CandidateId value that is associated with the tci-StateId value:
5 >
replace the entry related to CandidateTCI-State within the LTM-Candidate from VarLTM-Config.
4 >
else:
5 >
add the received CandidateTCI-State within LTM-Candidate to VarLTM-Config;
2 >
if the received LTM-Candidate includes ltm-UL-TCI-StatesToReleaseList:
3 >
for each tci-StateId in the ltm-UL-TCI-StatesToReleaseList:
4 >
if the current VarLTM-Config includes an CandidateTCI-UL-State within an LTM-Candidate with the ltm-CandidateId value that is associated with the tci-StateId value:
5 >
remove the entry related to CandidateTCI-UL-State within the LTM-Candidate from VarLTM-Config.
2 >
if the received LTM-Candidate includes ltm-UL-TCI-StatesToAddModList:
3 >
for each tci-StateId in the ltm-UL-TCI-StatesToAddModList:
4 >
if the current VarLTM-Config includes an CandidateTCI-UL-State within an LTM-Candidate with the ltm-CandidateId value that is associated with the tci-StateId value:
5 >
replace the entry related to CandidateTCI-UL-State within the LTM-Candidate from VarLTM-Config.
4 >
else:
5 >
add the received CandidateTCI-UL-State within LTM-Candidate to VarLTM-Config.
2 >
if the received LTM-Candidate includes ltm-nzp-CSI-RS-ResourceToReleaseList:
3 >
for each nzp-CSI-RS-ResourceId in the ltm-nzp-CSI-RS-ResourceToReleaseList:
4 >
if the current VarLTM-Config includes an NZP-CSI-RS-Resource within an LTM-Candidate with the ltm-CandidateId value that is associated with the nzp-CSI-RS-ResourceId value:
5 >
remove the entry related to NZP-CSI-RS-Resource within the LTM-Candidate from VarLTM-Config.
2 >
if the received LTM-Candidate includes ltm-nzp-CSI-RS-ResourceToAddModList:
3 >
for each nzp-CSI-RS-ResourceId in the ltm-nzp-CSI-RS-ResourceToReleaseList:
4 >
if the current VarLTM-Config includes an NZP-CSI-RS-Resource within an LTM-Candidate with the ltm-CandidateId value that is associated with the nzp-CSI-RS-ResourceId value:
5 >
replace the entry related to NZP-CSI-RS-Resource within the LTM-Candidate from VarLTM-Config.
4 >
else:
5 >
add the received NZP-CSI-RS-Resource within LTM-Candidate to VarLTM-Config.
2 >
if the received LTM-Candidate includes ltm-nzp-CSI-RS-ResourceSetToReleaseList:
3 >
for each nzp-CSI-RS-ResourceSetId in the ltm-nzp-CSI-RS-ResourceSetToReleaseList:
4 >
if the current VarLTM-Config includes an NZP-CSI-RS-ResourceSet within an LTM-Candidate with the ltm-CandidateId value that is associated with the nzp-CSI-RS-ResourceSetId value:
5 >
remove the entry related to NZP-CSI-RS-ResourceSet within the LTM-Candidate from VarLTM-Config.
2 >
if the received LTM-Candidate includes ltm-nzp-CSI-RS-ResourceSetToAddModList:
3 >
for each nzp-CSI-RS-ResourceSetId in the ltm-nzp-CSI-RS-ResourceSetToReleaseList:
4 >
if the current VarLTM-Config includes an NZP-CSI-RS-ResourceSet within an LTM-Candidate with the ltm-CandidateId value that is associated with the nzp-CSI-RS-ResourceSetId value:
5 >
replace the entry related to NZP-CSI-RS-ResourceSet within the LTM-Candidate from VarLTM-Config.
4 >
else:
5 >
add the received NZP-CSI-RS-ResourceSet within LTM-Candidate to VarLTM-Config.
2 >
if the received LTM-Candidate includes pathlossReferenceRS-ToReleaseList:
3 >
for each pathlossReferenceRS-Id in the pathlossReferenceRS-ToReleaseList:
4 >
if the current VarLTM-Config includes an PathlossReferenceRS within an LTM-Candidate with the ltm-CandidateId value that is associated with the pathlossReferenceRS-Id value:
5 >
remove the entry related to PathlossReferenceRS within the LTM-Candidate from VarLTM-Config.
2 >
if the received LTM-Candidate includes pathlossReferenceRS-ToAddModList:
3 >
for each pathlossReferenceRS-Id in the pathlossReferenceRS-ToAddModList:
4 >
if the current VarLTM-Config includes an PathlossReferenceRS within an LTM-Candidate with the ltm-CandidateId value that is associated with the pathlossReferenceRS-Id value:
5 >
replace the entry related to PathlossReferenceRS within the LTM-Candidate from VarLTM-Config.
4 >
else:
5 >
add the received PathlossReferenceRS within LTM-Candidate to VarLTM-Config.
2 >
if the LTM-Candidate with the received ltm-CandidateId value includes ltm-UE-MeasuredTA-ID:
3 >
if the value of ltm-UE-MeasuredTA-ID is equal to the value of ltm-ServingCellUE-MeasuredTA-ID within VarLTM-ServingCellUE-MeasuredTA-ID:
4 >
inform lower layers that UE is configured with UE-based TA measurements if an LTM cell switch is executed for this LTM candidate configuration;
Up
5.3.5.18.4  Void
5.3.5.18.5  Void
5.3.5.18.6  LTM cell switch execution  p. 164
Upon the indication by lower layers that an LTM cell switch procedure is triggered, or upon performing LTM cell switch following cell selection performed while timer T311 was running, as specified in clause 5.3.7.3, the UE shall:
1 >
release/clear all current dedicated radio configuration associated with the cell group for which the LTM cell switch procedure is triggered except for the following:
  • the logicalChannelIdentity and logicalChannelIdentityExt of RLC bearers configured in RLC-BearerConfig and the associated RLC entities, their state variables, buffers, and timers;
  • the UE variables VarLTM-Config, VarLTM-ServingCellNoResetID, and VarLTM-ServingCellUE-MeasuredTA-ID.
2 >
if the LTM cell switch is triggered on the MCG:
  • the MCG C-RNTI;
  • the AS security configurations associated with the master key;
  • for each SRB/DRB in current UE configuration which is using the master key:
    • keep the associated PDCP and SDAP entities, their state variables, buffers and timers;
    • release all fields related to the SRB/DRB configuration except for srb-Identity and drb-Identity;
2 >
else, if the LTM cell switch is triggered on the SCG:
  • the AS security configurations associated with the secondary key;
  • for each SRB/DRB in current UE configuration which is using the secondary key:
    • keep the associated PDCP and SDAP entities, their state variables, buffers and timers;
    • release all fields related to the SRB/DRB configuration except for srb-Identity and drb-Identity;
1 >
release/clear all current common radio configuration associated with the cell group for which the LTM cell switch procedure is triggered;
1 >
use the default values specified in clause 9.2.3 for timers T310, T311 and constants N310, N311 associate to cell group for which the LTM cell switch procedure is triggered;
1 >
if the value of field ltm-NoResetID contained within the LTM-Candidate IE in VarLTM-Config indicated by lower layers or for the selected cell in accordance with clause 5.3.7.3 is not equal to the value of ltm-ServingCellNoResetID within VarLTM-ServingCellNoResetID:
2 >
for each logicalChannelId and logicalChannelIdExt that is part of the current UE configuration for the cell group for which the LTM cell switch procedure is triggered:
3 >
after the end of this procedure, re-establish the corresponding RLC entity as specified in TS 38.322, after applying the LTM configuration in ltm-CandidateConfig within LTM-Candidate IE in VarLTM-Config;
2 >
for each drb-Identity value that is part of the current UE configuration:
3 >
if this DRB is an AM DRB:
4 >
after the end of this procedure, trigger the PDCP entity of this DRB to perform data recovery as specified in TS 38.323, after applying the LTM configuration in ltm-CandidateConfig within LTM-Candidate IE in VarLTM-Config;
2 >
replace the value of ltm-ServingCellNoResetID in VarLTM-ServingCellNoResetID with the value of ltm-NoResetID in the LTM-Candidate in VarLTM-Config indicated by lower layers or for the selected cell in accordance with clause 5.3.7.3;
1 >
if the LTM-Candidate IE in VarLTM-Config indicated by lower layers or for the selected cell in accordance with clause 5.3.7.3 contains the field ltm-UE-MeasuredTA-ID:
2 >
replace the value of ltm-ServingCellUE-MeasuredTA-ID in VarLTM-ServingCellUE-MeasuredTA-ID with the value received within ltm-UE-MeasuredTA-ID;
1 >
if ltm-ConfigComplete is not included within the LTM-Candidate IE in VarLTM-Config indicated by lower layers or for the selected cell in accordance with clause 5.3.7.3:
2 >
consider ltm-ReferenceConfiguration in VarLTM-Config, associated with the cell group for which the LTM cell switch procedure is triggered, to be the current UE configuration for the fields and configurations which have been released and to be released by the actions above in this procedure;
1 >
if the LTM cell switch is triggered by an indication from lower layers:
2 >
apply the RRCReconfiguration message in ltm-CandidateConfig within LTM-Candidate IE in VarLTM-Config identified by the LTM candidate configuration identity received from lower layers according to clause 5.3.5.3;
1 >
else (LTM cell switch triggered upon cell selection performed while timer T311 was running):
2 >
apply the RRCReconfiguration message in ltm-CandidateConfig within LTM-Candidate IE in VarLTM-Config related to the LTM candidate configuration identity for the selected cell (i.e., in accordance with clause 5.3.7.3) according to clause 5.3.5.3;
1 >
release the radio bearer(s) and the logical channel(s) that are part of the current UE configuration but not part of the LTM candidate configuration either indicated by lower layers or for the selected cell in accordance with clause 5.3.7.3, or the LTM reference configuration (in case the LTM candidate configuration does not include ltm-ConfigComplete).
Up
5.3.5.18.7  LTM configuration release  p. 166
For the cell group for which the LTM configuration release procedure is triggered, the UE shall:
1 >
remove all entries within VarLTM-ServingCellNoResetID;
1 >
remove the entry within VarLTM-ServingCellUE-MeasuredTA-ID;
1 >
release from current UE configuration all entries of ltm-CSI-ReportConfigToAddModList.
1 >
release ltm-Config;

5.3.5.19  T348 expiry  p. 167

The UE can apply the temporary UE capability restriction in accordance with the one indicated in the last transmission of the UEAssistanceInformation message including musim-CapRestriction, as specified in clause 5.7.4.3.

Up   Top   ToC