Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 38.300  Word version:  18.4.0

Top   Top   Up   Prev   Next
1…   4…   4.7…   5…   5.3…   5.4…   6…   6.2…   6.6…   7…   8…   9…   9.2.2…   9.2.2.5…   9.2.3…   9.2.3.2…   9.2.3.3…   9.2.4…   9.2.6…   9.3…   10…   11…   15…   15.5…   16…   16.2…   16.3…   16.4…   16.8…   16.9…   16.10…   16.12…   16.12.5…   16.12.6…   16.12.6.3   16.12.7   16.13…   16.14…   16.15…   16.18…   16.19…   16.21…   16.21.3…   17…   18…   19   20…   21…   A…   B…   C…   G…

 

20  Support for Multi-USIM devices |R17|p. 240

20.1  Generalp. 240

NG-RAN may support one or more of the following enhancements for MUSIM device operation:
  • Paging Collision Avoidance, as described in clause 20.2;
  • UE notification on Network Switching, as described in clause 20.3;
  • Temporary UE capability restriction and removal of restriction, as described in clause 20.4.
Up

20.2  Paging Collision Avoidancep. 240

The purpose of paging collision avoidance is to address the overlap of paging occasions on both USIMs when a MUSIM device (e.g. dual USIM device) is in RRC_IDLE/RRC_INACTIVE state in both the networks (e.g. Network A and Network B) associated with respective USIMs. Network A is NR and Network B is E-UTRA or NR.
A MUSIM device may determine potential paging collision on two networks and may trigger actions to prevent potential paging collision on NR network as specified in TS 23.501.
Up

20.3  UE notification on Network Switchingp. 241

For MUSIM operation, a MUSIM device in RRC_CONNECTED state in Network A may have to switch from Network A to Network B. Network A is NR and Network B can either be E-UTRA or NR. Before switching from Network A, a MUSIM device should notify Network A to either leave RRC_CONNECTED state, or be kept in RRC_CONNECTED state in Network A while temporarily switching to Network B.
When configured to do so, a MUSIM device can signal to the Network A a preference to leave RRC_CONNECTED state by using RRC (see TS 38.331) or NAS signalling (see TS 23.501). After sending a preference to leave RRC_CONNECTED state by using RRC signalling, if the MUSIM device does not receive an RRCRelease message from the Network A within a certain time period (configured by the Network A, see TS 38.331), the MUSIM device can enter RRC_IDLE state in Network A.
When configured to do so, a MUSIM device can signal to the Network A a preference to be temporarily switching to Network B while remaining in RRC_CONNECTED state in Network A. This is indicated by scheduling gaps preference. This preference can include information for setup or release of gap(s). The Network A can configure at most 4 gap patterns for MUSIM purpose: three periodic gaps and a single aperiodic gap. The Network A should always provide at least one of the requested gap pattern or no gaps. Network providing an alternative gap pattern instead of the one requested by the UE is not supported in this release.
When configured to do so, a MUSIM device can include priority of periodic gap(s) in addition to scheduling gaps preference, and the priority preference should be indicated for all periodic gap(s). If the MUSIM device indicates gap priority preference, it can also indicate its preference on using keep solution (defined in TS 38.133).
Up

20.4  Temporary UE capability restriction and removal of restriction |R18|p. 241

For MUSIM operation, a MUSIM device in RRC_CONNECTED state in Network A may indicate its preference on temporary UE capability restriction or removal of restriction via UE assistance information with Network A when the MUSIM device needs transmission or reception in Network B (e.g., including start/stop connection to Network B). Network A is NR and Network B can either be E-UTRA or NR. The MUSIM device may request a temporary capability restriction only after the Network signals via RRC that this is allowed.
When configured to do so, a MUSIM device can indicate one or more of the following temporary capability restriction or removal of restriction to the Network A:
  • A MUSIM device can explicitly request SCell(s) or SCG to be released;
  • A MUSIM device can indicate its preference on temporary maximum MIMO layers and/or supported channel bandwidth for specific serving cells for both UL/DL;
  • A MUSIM device can indicate its preference on the temporary maximum number of CCs per UL/DL;
  • A MUSIM device can indicate its preference on the concerned band(s) or band combination(s) (e.g. avoided and/or affected band(s) or band combination(s)) based on a band-filter list configured by network. For affected band(s) and band combination(s), this preference can include temporary maximum MIMO layers and/or supported channel bandwidth for both UL/DL;
  • A MUSIM device can indicate the measurement gap requirement changes.
When it is allowed by Network A in SIB1, a MUSIM device can indicate in RRCSetupComplete/RRCResumeComplete/RRCReestablishmentComplete message to the Network A that its capabilities are temporarily restricted due to ongoing transmission/reception in Network B. This indication allows Network A to know whether UE capabilities without restrictions can be used by Network A, or if Network A needs to configure the UE to indicate its temporary capability restrictions, as described above. When configured to do so, a MUSIM device can also indicate to the Network A there is no temporary capability restriction via UE assistance information.
When a MUSIM device is in RRC_CONNECTED state in both Network A and Network B, if Network B is NR, it is up to UE implementation to select which network to request temporary UE capability restriction; if Network B is E-UTRA, the request for temporary UE capability restriction can only be performed on Network A.
Up

Up   Top   ToC