Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 37.340  Word version:  17.3.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.3…   5…   7…   8…   9   10…   10.2…   10.2.2…   10.3…   10.3.2   10.4…   10.5…   10.5.2   10.6   10.7…   10.8…   10.9…   10.10…   10.11…   10.12…   10.12.2   10.13…   10.14…   10.15   10.16…   10.17…   10.18…   10.19…   11…   A   B…

 

11  Service related aspectsp. 109

11.1  Roaming and Access Restrictionsp. 109

The principles for conveying roaming and access restriction info for EN-DC are described in TS 36.300.
For MR-DC with 5GC, SCG (re)selection at the SN is based on roaming and access restriction information in SN. If roaming and access restriction information is not available at the SN, the SN shall consider that there is no restriction for SCG (re)selection. Therefore, MN needs to convey the up-to-date roaming and access restriction information to SN via XnAP messages.
Up

11.2  Support of Network Sharingp. 109

E-UTRAN and NG-RAN aspects of network sharing are specified in TS 36.300 and TS 38.300.

11.3  ARPI/SPID Handling from MN |R16|p. 109

Usage of the Subscriber Profile ID for RAT/Frequency Priority (SPID) and the Additional RRM Policy Index (ARPI) in E-UTRAN is specified in TS 36.300 and applies to EN-DC. Therefore, the MN needs to convey the up-to-date ARPI/SPID information to the SN via X2AP messages.

12  X2/Xn Interface related aspectsp. 109

Stage 2 specification for X2-C procedures for EN-DC is contained in TS 36.300.
Xn-C procedures for MR-DC with 5GC are specified in TS 38.423.
X2-U procedures for EN-DC and Xn-U procedures for MR-DC with 5GC are specified in TS 38.425.

13  Other aspectsp. 110

13.1  Interference avoidance for in-device coexistencep. 110

In-Device Coexistence (IDC) solution as described in TS 36.300 is extended to address EN-DC operation. Only FDM solution, where the list of NR carriers suffering from IDC problems is signalled in IDC indication, is supported in this version of the specifications. The requirement on RRM/RLM/CSI measurements in different phases of IDC interference defined in TS 36.300 is applicable except that for NR serving cell, the requirements in TS 38.133 and TS 38.101-1, TS 38.101-2, TS 38.101-3 apply.
Up

13.2  Sidelink |R16|p. 110

NR Sidelink Communication, V2X Sidelink Communication and NR Sidelink Discovery cannot be configured in MR-DC in this release.

13.3  SCG UE history information |R17|p. 110

The MN stores and correlates the UE History Information from MN and SN(s) as long as the UE stays in MR-DC, forwards UE History Information and optional UE History Information from the UE to its connected SNs. The resulting information is then used by SN for dual-connectivity operation. The SN is in charge of collecting SCG UE history information and providing the collected information to the MN.
If the UE stays in a PSCell for a duration exceeding the maximum value of the Time Stay parameter, the SN may store the PSCell information with consecutive entries using the same PSCell identity. The total stay time in this PSCell is the sum of stay time for all consecutive PSCell with the same identity.
The SN shall provide the collected SCG UE history information, if available, to the MN in the following procedures:
  • the SN Release, and SN initiated SN Change procedures
  • the MN initiated SN Modification procedure if requested by the MN in this procedure
  • the SN initiated SN modification procedure upon PSCell change if subscribed in the SN Addition procedure
When the target NG-RAN node receives the SCG UHI from the source NG-RAN node via Handover Request message for CHO, the target NG-RAN node updates the time UE stayed in cell of the latest PSCell entry (i.e. the source PSCell) when the UE successfully accesses to a candidate cell of the target NG-RAN node. The updated value of the time UE stayed in the source PSCell is equal to the value received from the source NG-RAN node during the Handover Preparation plus the time from receiving Handover Request message from the source NG-RAN node to receiving RRC Reconfiguration Complete message from the UE.
Up

Up   Top   ToC