Reducing scheduling restrictions during dual subscriber identity module dual standby
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- NOKIA TECHNOLOGIES OY
- Filing Date
- 2026-02-05
- Publication Date
- 2026-08-07
Smart Images
Figure CN122534418A_ABST
Abstract
Description
Cross-references to related applications
[0001] This application claims priority and benefit to Indian Patent Application No. 202541010617, filed on February 7, 2025, the contents of which are incorporated herein by reference in their entirety. Technical Field
[0002] Various exemplary embodiments of this disclosure generally relate to the telecommunications field, and more specifically to methods, apparatus, devices, and computer-readable storage media for reducing scheduling constraints during Dual Subscriber Identity Module (SIM) Dual Standby (DSDS). Background Technology
[0003] DSDS has been implemented in various forms in a variety of products. Devices implementing DSDS can maintain two SIMs in a completely idle mode in parallel and have the ability to establish and maintain a connection mode on one SIM while maintaining an idle mode on the other SIM. Summary of the Invention
[0004] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to at least: receive a first Multi-Universal Subscriber Identity Module (MUSIM) gap configuration and a second MUSIM gap configuration from a second apparatus via the same configuration message, wherein the first subscriber identity module (SIM) of the first apparatus is connected to the second apparatus, the first MUSIM gap configuration is to be used for a first discontinuous intra-band carrier aggregation (CA) mode, and the second MUSIM gap configuration is to be used for a second discontinuous intra-band CA mode; and switch from the second discontinuous intra-band CA mode to the first discontinuous intra-band CA mode according to the first SIM, while data scheduling on the first SIM is restricted during idle mode process operation on the second SIM of the first apparatus, and fall back from the second MUSIM gap configuration to the first MUSIM gap configuration.
[0005] In a second aspect of this disclosure, a second device is provided. The second device includes at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second device to at least: send a first MUSIM gap configuration and a second MUSIM gap configuration to a first device via the same configuration message, the first device having a first subscriber identification module (SIM) connected to the second device.
[0006] In a third aspect of this disclosure, a method is provided. The method includes: receiving, by a first device, a first Multi-Universal Subscriber Identity Module (MUSIM) gap configuration and a second MUSIM gap configuration from a second device via the same configuration message, wherein a first subscriber identity module (SIM) of the first device is connected to the second device, the first MUSIM gap configuration being used for a first discontinuous intra-band carrier aggregation (CA) mode, and the second MUSIM gap configuration being used for a second discontinuous intra-band CA mode; and, according to the first SIM, transitioning from the second discontinuous intra-band CA mode to the first discontinuous intra-band CA mode, while data scheduling on the first SIM is restricted during idle mode procedure operation on the second SIM of the first device, falling back from the second MUSIM gap configuration to the first MUSIM gap configuration.
[0007] In a fourth aspect of this disclosure, a method is provided. The method includes: sending a first MUSIM gap configuration and a second MUSIM gap configuration to a first device having a first subscriber identification module (SIM) connected to a second device via the same configuration message.
[0008] In a fifth aspect of this disclosure, a first apparatus is provided. The first apparatus includes: means for receiving, via the same configuration message, a first Multi-Universal Subscriber Identity Module (MUSIM) gap configuration and a second MUSIM gap configuration from a second apparatus, the first MUSIM gap configuration being used for a first discontinuous intra-band carrier aggregation (CA) mode and the second MUSIM gap configuration being used for a second discontinuous intra-band CA mode; and means for switching from the second discontinuous intra-band CA mode to the first discontinuous intra-band CA mode according to the first SIM, and for falling back from the second MUSIM gap configuration to the first MUSIM gap configuration during idle mode procedure operation on the second SIM of the first apparatus while data scheduling on the first SIM is restricted.
[0009] In a sixth aspect of this disclosure, a second device is provided. The second device includes components for transmitting a first MUSIM gap configuration and a second MUSIM gap configuration to a first device via the same configuration message, the first device having a first subscriber identification module (SIM) connected to the second device.
[0010] In a seventh aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to at least execute the method according to a third aspect.
[0011] In an eighth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to at least execute the method according to the fourth aspect.
[0012] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description
[0013] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which example embodiments of the present disclosure may be implemented is shown; Figure 2 An example of a fragmented carrier is shown; Figure 3 The UE architecture for NC IB CA reception is shown; Figure 4 This illustrates the assumption that the same RX chain is used for activity switching between two SIMs, the connected mode on network A, and the idle mode on network B. Figure 5 This illustrates the need for measurement settings for different connectivity modes during various RRM state transitions when supporting fragmented carriers; Figure 6 The diagram illustrates the RRM state machine mode transitions of the UE's SIM1 when operating in a fragmented CA configuration and the associated RF configuration in each mode; Figure 7 An example of gapless use of SIM1 and SIM2 is shown; Figure 8 The diagram illustrates the use of SIM1 and SIM2 RF resources during the MUSIM interval; Figure 9 Signaling diagrams of communications according to some example embodiments of this disclosure are shown; Figure 10 Signaling diagrams of gapless communication according to some example embodiments of the present disclosure are shown; Figure 11 Signaling diagrams of communications with MUSIM gaps according to some example embodiments of the present disclosure are shown; Figure 12 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 13 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 14 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 15 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 16 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 17 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.
[0014] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation
[0015] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to help those skilled in the art to understand and implement this disclosure, without implying any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.
[0016] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.
[0017] References to "an embodiment," "an embodiment," "an example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment includes that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is to be noted that those skilled in the art will recognize, whether explicitly described or not, that such features, structures, or characteristics apply in conjunction with other embodiments.
[0018] It should be understood that although terms such as "first," "second," etc., may be used before names (or similar designations) to describe various elements herein, these elements should not be limited by these terms. These terms are used only to distinguish one element from another, and they do not restrict the order of the nouns (or similar designations). For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.
[0019] As used herein, “at least one of the following: ” and “at least one of ” and similar expressions, wherein the list of two or more elements is connected by “and” or “or”, means at least any one of these elements, or at least any two or more of these elements, or at least all of these elements.
[0020] As used herein, unless explicitly stated otherwise, the action “in response to A” does not indicate that the action is performed immediately after “A” occurs and may include one or more intervention steps.
[0021] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the terms “comprising,” “including,” “having,” “possessing,” “containing,” and / or “covering,” as used herein, specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.
[0022] As used in this application, the term "circuit" may refer to one or more or all of the following: (a) Hardware circuit implementation only (e.g., implemented with purely analog and / or digital circuits), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions) and (c) The operation requires software (e.g., firmware) for the operation of (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or parts thereof, but the software may be absent when the operation does not require the software.
[0023] This definition of "circuit" applies to all uses of the term in this application. As a further example, as used in this application, the term "circuit" also covers only hardware circuitry or processors (or processors), or portions of hardware circuitry or servers and their accompanying software and / or firmware implementations. For example, where applicable to certain claim elements, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.
[0024] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, sixth-generation (6G) communication protocols, and / or any other currently known or under development protocols. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, future types of communication technologies and systems that can implement this disclosure will inevitably emerge. The scope of this disclosure should not be considered limited to the systems described above.
[0025] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node (such as femtoseconds, picoseconds, non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment), low Earth orbit (LEO) satellites and geostationary Earth orbit (GEO) satellites, spacecraft network equipment, etc.). In some example embodiments, the Radio Access Network (RAN) separation architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves similarly to a UE toward its parent node, and the DU portion of the IAB node behaves similarly to a base station toward the next-hop IAB node.
[0026] The term "terminal device" refers to any end device with wireless communication capabilities. By way of example and not limitation, terminal device may also refer to communication equipment, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image acquisition terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless client devices (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Terminal equipment may also correspond to the mobile terminal (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal equipment," "communication equipment," "terminal," "user equipment," and "UE" are used interchangeably.
[0027] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network device, including resources in the time domain, frequency domain, spatial domain, code domain, or any other combination of time-domain, frequency-domain, spatial-domain, and / or code-domain resources used to implement communication. In the following, unless explicitly stated otherwise, resources in both the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. It should be noted that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.
[0028] Figure 1 An example communication environment 100 in which exemplary embodiments of the present disclosure may be implemented is shown. The communication environment 100 may include a first device 110 (e.g., a UE), a second device 120, and a third device 130 (e.g., a gNB), which may be collectively referred to as network devices. It is understood that the second device 120 and the third device 130 are not limited to separate cells, but may also cover the same cell 102. The second device 120 and the third device 130 may also be co-located, situated in the same location, or implemented in a single device.
[0029] The first device 110 can be served by cell 102 managed by the second device 120. That is, cell 102 can be considered as the serving cell of the first device 110. Within a certain coverage area, signals transmitted from the third device 130 can also be received by the first device 110, and the first device 110 can be considered as another connection between the first device 110 and the third device 130.
[0030] In some example embodiments, the link from the second device 120 or the third device 130 to the first device 110 is referred to as a downlink (DL), and the link from the first device 110 to the second device 120 or the third device 130 is referred to as an uplink (UL). In the DL, the second device 120 or the third device 130 is a transmitting (TX) device (or transmitter), and the first device 110 is a receiving (RX) device (or receiver). In the UL, the first device 110 is a TX device (or transmitter), and the second device 120 or the third device 130 is an RX device (or receiver).
[0031] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not impose any limitations. Communication environment 100 may include any suitable number of devices configured to implement the exemplary embodiments of this disclosure. Although not shown, it should be understood that one or more additional devices may be located in cell 102, and one or more additional cells may be deployed in communication environment 100. Note that although shown as a network device, the second device 120 may be another device besides a network device. Although shown as a terminal device, the first device 110 may be another device besides a terminal device.
[0032] In the following description, for illustrative purposes, some example embodiments are described in which the first device 110 operates as a UE and the second device 120 operates as a base station. However, in some example embodiments, the operations described in connection with the terminal device can be implemented at the network device or other device, and the operations described in connection with the network device can be implemented at the terminal device or other device.
[0033] In some example embodiments, the link from the second device 120 or the third device 130 to the first device 110 is referred to as a downlink (DL), and the link from the first device 110 to the second device 120 or the third device 130 is referred to as an uplink (UL). In the DL, the second device 120 or the third device 130 is a transmitting (TX) device (or transmitter), and the first device 110 is a receiving (RX) device (or receiver). In the UL, the first device 110 is a TX device (or transmitter), and the second device 120 or the third device 130 is an RX device (or receiver).
[0034] Communication in communication environment 100 can be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols, wireless local area network communication protocols (such as IEEE 802.11), and / or any other currently known or future-developed protocols. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.
[0035] Some of the proposed schemes involve assessing the feasibility of using a single Rx chain on fragmented in-band blocks in DL carrier aggregation (CA), while also investigating near-term and long-term issues and undesirable emissions impacts.
[0036] The following shows the scope of some of the proposed solutions: The purpose of this study is as follows: - Identify methods for reducing the number of UE Rx chains (e.g., 1 or 2) required for a single DL band with a frequency span ≤100 MHz, including two discontinuous component carriers (CCs) within the CA combination for inter-carrier cooperative positioning scenarios, considering: -Which radio frequency (RF) requirements can be adjusted for inter-carrier co-located base station (BS) scenarios, such as existing UE RF requirements, like adjacent channel selectivity (ACS); - The ability to semi-statically switch hardware resources (i.e., Rx chains) between frequency bands; - Up to 6 dB of DL power spectral density imbalance between two discontinuous CCs; -Impact on DL performance; - A component used by the UE to notify the network that it can support the new CA configuration with adjusted RF requirements.
[0037] Now for reference Figure 2 It shows an example of a fragmented carrier. Figure 2 The diagram shows several different fragmented carriers.
[0038] Figure 2Examples of the use of fragmented carriers are shown. For some of the schemes discussed, the fragmented carriers are not entirely new, as they are essentially non-contiguous in-band carrier aggregation (NC IB CA).
[0039] from Figure 2 As can be seen, the interference sources within the gap can be several channels, and even from more than one other operator. Some information about channel usage will be provided by inter-operator communication / coordination. However, such information is only general and does not provide any explicit information about instantaneous usage and power spectral density.
[0040] Now for reference Figure 3 It illustrates the UE architecture for NC IB CA reception.
[0041] like Figure 3 As shown, three hardware architectures are discussed for non-continuous in-band carrier aggregation reception.
[0042] Partially shared architectures consume two receive radio frequency (Rx RF) chains to receive two component carriers and are the method by which UEs implement support for NC IB CA in some discussed schemes, while fully shared architectures occupy only one Rx RF chain to receive two carriers. The study of fragmented carriers aims to identify ways to include fully shared architectures in the specification as supported receiver configurations for non-contiguous in-band carrier aggregation reception under the specific declaration of fragmented carrier aggregation.
[0043] Regarding the Multi-Universal Subscriber Identity Module (MUSIM) (which can also be referred to as Dual SIM Dual Standby (DSDS) or Dual SIM Dual Activity (DSDA)).
[0044] Dual Subscriber Identity Module (SIM), Dual Activity, DSDA: In this mode, the device can establish and maintain two active connections in parallel, one active connection for each SIM. These two connections operate independently; however, dual TX operations may, of course, affect across SIMs.
[0045] Dual SIM Dual Standby (DSDS): In DSDS, the device can maintain a completely idle mode in parallel on two SIMs, and has the ability to establish and maintain a connection on one SIM while maintaining an idle mode on the other. This mode comes in various forms in different products: -DSDS, Single Receive: In this mode, the device needs to prioritize each activity between SIMs. For example, if two SIMs want to listen for incoming paging simultaneously, this is physically impossible in a single-RX device, and therefore only one paging will be received. The prioritization scheme is proprietary to each device vendor.
[0046] -DSDS, Dual Receive: In this mode, the device can receive two SIMs in parallel, but only transmits to one SIM at a time, because the connection mode is only supported on one SIM at a time.
[0047] In some of the discussed schemes, the MUSIM device uses the same Rx for operation on two networks. In this approach, it is assumed that the UE is in Radio Resource Control (RRC) connected mode on one network (Network A) and in RRC idle mode on another network (Network B). Therefore, for the DSDS case, the MUSIM work item introduces a gap in connected mode. The gaps defined to support MUSIM operation are as follows:
[0048] In some of the proposed solutions, a connection mode on two SIM cards is also supported.
[0049] The added relevant signaling (e.g., parameters for the MUSIM gap related to one SIM in connected mode and another SIM in idle mode) is as follows:
[0050] The signaling introduced in some of the discussed schemes allows the UE to be configured with gaps that can be used for MUSIM measurements on Network B.
[0051] Now for reference Figure 4 It illustrates the activity switching between two SIM cards: connected mode on network A and idle mode on network B, assuming that the two SIM cards share the same receive chain.
[0052] However, when switching and tuning the RX chain, a MUSIM gap is required, during which data transmission will be interrupted.
[0053] Some of the proposed schemes have put forward specific RF configurations for supporting fragmented carriers, depending on the diversity and power of interference within the gap.
[0054] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.
[0055] Some of the discussed schemes describe signaling procedures that change between the main RF architecture (state 1 and state 3) in the fragmented CA study, while state 2 is protected in some other discussed schemes, offering more performance advantages compared to state 2 as expected in the study.
[0056] Several other schemes have been further added around fragmented CA, binding together various hardware (HW) states and configuration states, which switch between the number of RX chains and the configuration of wider analog filters.
[0057] Now for reference Figure 5 This demonstrates the need for measurement settings for different connectivity modes during various radio resource management (RRM) state transitions when supporting fragmented carriers. Figure 5 The RF configuration for a SIM in connected mode is also shown.
[0058] Some of the discussed schemes add aspects such as different measurement settings to be used with different receiver architectures, and alignment of these different measurement settings between the NW and UE via RRC configuration and / or fast Layer 2 (L2) signaling. This ensures an optimal trade-off between UE performance, UE RF HW capabilities, and available UE resources in various RRM state machine operating modes.
[0059] The exact RF configuration for saving RF resources through alternating use is not important; what is important is the existence of additional RF resources available from the RF configuration, regardless of whether they take the form of the scheme discussed in some parts.
[0060] The technical problem to be solved is for a UE with additional RF HW resources to process two SIM cards in parallel. When one of the two SIMs is in connected operation mode with a fragmented CA configuration and the other SIM is in idle mode, the MUSIM gap configuration required to maximize the use of available RF HW resources may differ when performing different idle mode procedures, given that the idle SIM operation can vary depending on its RF band.
[0061] For example, receiving a paging call may require a different MUSIM gap configuration compared to performing neighboring cell measurements. As an example, paging may utilize an additional RX chain that the device does not support in the frequency band used for neighboring cell measurements.
[0062] Meanwhile, for connected SIMs, depending on RF conditions and in-band interference measurements, the RRM state machine mode RF settings can vary depending on whether it is in fragmented CA or IB NC CA configuration.
[0063] However, the NW and UE cannot align the measurement gap setting configuration of the connected mode SIM with the MUSIM gap configuration of the idle mode SIM, so that the available RF resources during the fragmented CA RRM state machine mode of the connected SIM can be used for optimal performance on both SIMs.
[0064] A solution for determining the types of MUSIM gap configurations that the network must signal to a MUSIM UE with a receiver architecture (partially shared or fully shared) is desired. Furthermore, a solution for dynamically adapting the RF receiver configuration during DSDS dual-receive mode with fragmented carriers configured on connected SIMs is also desired.
[0065] Two aspects can be considered: the first aspect could involve the availability of the receiver chain, and the second aspect could involve the use of MIMO operating mode.
[0066] Depending on the availability or unavailability of RF resources, especially in fallback scenarios, a solution is also desired that allows MUSIM (DSDS) devices operating on connected SIMs with fragmented carrier configurations to signal to the NW that they need to switch to the appropriate MUSIM gap configuration.
[0067] According to some example embodiments of this disclosure, a solution is provided for reducing scheduling constraints during Dual Subscriber Identity Module Dual Standby (DSDS). In this solution, a first device 110 receives a first MUSIM gap configuration for a first discontinuous in-band CA mode from a second device 120 via a first RRC configuration message, wherein a first SIM of the first device is connected to the second device 120. If the first SIM transitions from the first discontinuous in-band CA mode to a second discontinuous in-band CA mode, the first device 110 sends a request for a second MUSIM gap configuration for the second discontinuous in-band CA mode. If the first device 110 receives the second MUSIM gap configuration from the second device 120 via a second RRC configuration, the first device 110 switches from the first MUSIM gap configuration to the second MUSIM gap configuration to support data scheduling on the first SIM during idle mode procedure operation on the second SIM of the first device 110.
[0068] In this way, the MUSIM measurement gap setting can be adapted to the RF settings of the MUSIM DSDS UE (i.e., the first device 110) in such a way that the idle SIM can utilize the available RF resources shared between SIM 1 (the first SIM) and SIM 2 (the second SIM) to perform the idle mode process in a manner with minimal or no gap.
[0069] In this disclosure, SIM1 of the first device 110 can be considered as a first SIM in connected mode. SIM2 of the first device 110 can be considered as a second SIM in idle mode. Network A can be considered as a network node controlling SIM1. Network A can be a network associated with the second device 120. Network B can be considered as a network node controlling SIM2. Network B can be a network associated with the third device 130.
[0070] This disclosure relates to the alignment of the current state of the UE's capabilities and the RF configuration of SIM1 in fragmented CA operations between the MUSIM DSDS UE and Network A. This alignment facilitates Network A's pre-configuration and / or scheduling of appropriate MUSIM gap modes for the UE's SIM2 operations with Network B. The MUSIM gap mode will reflect the supported RF configuration settings and ensures that when a setting change occurs, Network A knows when it happens and uses an appropriate pre-configured or reconfigured MUSIM gap configuration that maximizes the use of available RF HW resources during different idle mode procedures between SIM2 and Network B.
[0071] Now for reference Figure 6 This illustrates the RRM state machine mode transitions of the first device 110 and its associated RF configuration in each mode when operating in a fragmented CA configuration. When the first device 110's SIM1 enters mode 1, it needs to support one RX chain with 2L MIMO / diversity.
[0072] in other words, Figure 6 The diagram shows the RRM state machine transitions and measurement settings on SIM1 (connected mode), as well as the changes in MUSIM gap configurations associated with those different RF configurations.
[0073] Regarding the solution proposed in this disclosure, there are three aspects that have been considered: In the first aspect, the network should know whether the first device 110 supports handling different MUSIM gap settings during changes in the RF configuration due to changes in fragmented carrier conditions and / or MIMO rank. For fragmented carrier operation, the second device 120 may provide the first device 110 with the MUSIM gap settings per RF configuration supported by the UE, as indicated in the first aspect above.
[0074] In the second aspect, regarding fragmented carrier operation, when entering fragmented CA operation mode on SIM1, various types of MUSIM gap configurations can be received in different RRC messages.
[0075] In some embodiments, if the first device 110 is pre-configured with multiple MUSIM gap modes for each connection mode fragmented CA RF configuration on SIM1, the first device 110 will indicate its selected MUSIM gap mode from the pre-configured set via fast L2 / L1 signaling (such as MAC CE / Downlink Control Information (DCI) on the primary cell (PCell)), wherein a gapless MUSIM configuration is preferred and the RF configuration status on SIM1 is indicated.
[0076] In some embodiments, if the first device 110 is not pre-configured with multiple MUSIM gap patterns for fragmented CA RF configurations on SIM1, the first device 110 will request a MUSIM gap pattern with an indication of preference for gapless MUSIM configurations and the RF configuration status on SIM1 via L3 signaling (such as UE Assistance Information (UAI)). The network may provide the requested type of MUSIM gap pattern to the first device 110 in an RRC reconfiguration (L3) message. This is a slower method of adapting MUSIM gap configurations to RF configurations.
[0077] In the third aspect, when entering the non-fragmented CA (fallback) mode of CA operation on SIM1, multiple different types of MUSIM gap configurations can be received in a single RRC signaling.
[0078] In some embodiments, if the first device 110 is pre-configured with a fallback MUSIM gap mode for a non-fragmented CA RF configuration on the connection mode on SIM1, the first device 110 will indicate its selection of the fallback MUSIM gap mode and the indication of the RF configuration status on SIM1 via fast L2 / L1 signaling (such as MAC CE / DCI on PCell).
[0079] In some embodiments, if the first device 110 is not pre-configured with a fallback MUSIM gap mode for a connection-mode unfragmented CA RF configuration on SIM1, the first device 110 will request a MUSIM gap mode with a preference for the MUSIM gap configuration and an indication of the RF configuration status on SIM1 via L3 signaling (such as UE Assistance Information (UAI)). The network can provide the requested type of MUSIM gap mode to the UE in an RRC reconfiguration (L3) message. This is a slower method of adapting the MUSIM gap configuration to the RF configuration.
[0080] Now for reference Figure 7 It illustrates the use of SIM1 and SIM2 RF resources during the MUSIM gap.
[0081] like Figure 7As shown, when the first device 110 enters fragmented CA mode 1, it needs to support one RX chain, and the first device 110 should be able to use MUSIM gap configuration. On SIM1, CC1 and CC2 are scheduled by network A with UL / DL services. Since the RF configuration only requires one RX chain, the RF chain can be released in mode 1.
[0082] Through the above process, the data scheduling limits on SIM1 are increased due to the MUSIM gap configuration option configured on SIM1 for Mode 1, and due to the gapless MUSIM gap configuration that may be available during Mode 1.
[0083] Now for reference Figure 8 This diagram illustrates the use of RF resources in SIM1 and SIM2 during MUSIM gaps. When the first device 110 (on SIM1) enters fragmented CA mode 3, support for a 2RX chain with 2L MIMO / diversity is required. The first device 110 and the network should be able to use a MUSIM gap configuration with gaps, such as... Figure 8 As shown.
[0084] On SIM1, CC1 and CC2 are scheduled by network A with UL / DL services. Due to the partially shared or completely separate RF architecture used in this mode, the RF chain is no longer idle for SIM2 idle mode operation. Therefore, UL / DL scheduling on SIM1 is interrupted during the MUSIM gap because some RF resources must be released to SIM1.
[0085] Through the above process, due to the availability of the MUSIM gap configuration, which is only available during Mode 1 of the RRM state machine in Mode 2 and on SIM1, the data scheduling restrictions on SIM1 are limited to Mode 3.
[0086] The solution proposed in this disclosure increases the flexibility of switching to a MUSIM gap configuration that is suitable for the RF architecture of the first device 110, and aligns this between the NW and the MUSIM UE (i.e., the first device 110).
[0087] According to the scheme proposed in this disclosure, when the device (e.g., first device 110) has available remaining RF Rx chains, the RF Rx chains can be used to perform (SIM2) idle mode operation and can be adapted according to the current RRF Rx chain configuration for fragmented carriers. This reduces the need for MUSIM gaps for performing the (SIM2) idle mode procedure as much as possible, taking into account the current CA / MIMO configuration and actual RF setup on SIM1. The solution proposed in this disclosure also reduces the need for MUSIM gaps and the alignment of this reduced need with the network. Compared to a measured configuration, the network can compromise the RF configuration to avoid MUSIM gaps, meaning that MUSIM gaps can potentially be avoided if fragmented carrier settings or reduced MIMO are available on SIM1.
[0088] The network can pre-configure multiple MUSIM gaps and enable rapid dynamic switching, meaning it can quickly shift to fewer MUSIM gaps if the RF configuration allows. The device can inform the network which of the multiple MUSIM gap configurations it is using or notify it of different MUSIM gap requirements.
[0089] Now for reference Figure 9 This illustrates signaling diagram 900 for communication according to some example embodiments of the present disclosure. Figure 9 As shown, signaling diagram 900 relates to a first device 110, a second device 120, and a third device 130. For discussion purposes, see reference to... Figure 1 To describe signaling diagram 900.
[0090] The first device 110 may include two SIMs, namely a first SIM and a second SIM. The first SIM may also be referred to as SIM1 (in connected mode), and the second SIM may also be referred to as SIM2 (in idle mode), as described above. The second device 120 may provide network A, and the third device 130 may provide network B as described above. It should be noted that the schemes mentioned herein can also be applied to any signaling diagrams mentioned above or described below.
[0091] like Figure 9 The diagram illustrates the overall process by which the first device 110 exchanges the ability related to MUSIM gaps and fragmented CAs in the MUSIMDSDS between the first SIM and the second device 120.
[0092] like Figure 9 As shown, the second device 120 can send (905) a query related to the capabilities of the first device 110.
[0093] When the first SIM enters RRC connection mode, the first SIM can send (910) capability information of the first device 110 to the second device 120 regarding its ability to support different MUSIM gap configurations during fragmented CA and MUSIM DSDS operations.
[0094] Now for reference Figure 10 This illustrates a signaling diagram 1000 for communication according to some example embodiments of the present disclosure. For example... Figure 10 As shown, signaling diagram 1000 relates to a first device 110, a second device 120, and a third device 130. For discussion purposes, refer to... Figure 1 To describe signaling diagram 1000.
[0095] According to signaling diagram 1000, the first device 110 (i.e., the first SIM) can instruct the second device 120 (1005) that capability information for different types of MUSIM gap configurations associated with MUSIM DSDS operation is supported by the first device 110.
[0096] In some embodiments, the first device 110 may send capability information indicating that different MUSIM gap configurations (e.g., a first MUSIM gap configuration and a second MUSIM gap configuration) associated with MUSIM DSDS operation are supported by the first device 110.
[0097] For example, a first SIM in RRC connection mode can send capability information of the first device 110 to a second device 120 (network A). It carries an indication that the first device 110 can support different / multiple MUSIM gap configurations during different RF configurations in fragmented CA and MUSIM DSDS operations.
[0098] The first device 110 can receive a first MUSIM gap configuration for a first non-continuous in-band CA mode from a second device 120 to which the first SIM of the first device 110 is connected via a first RRC configuration message.
[0099] In this step, the first device 110 may receive the first MUSIM gap configuration from the second device 120 via a first RRC configuration message. In some examples, the first MUSIM gap configuration may be sent to the first device 110 via an RRC reconfiguration message.
[0100] For example, the second device 120 (i.e., network A) sends an RRC reconfiguration message with a MUSIM gap configuration (e.g., gap configuration 1 or the first MUSIM gap configuration) to be used for MUSIM DSDS and CA operations. After this step, the first device 110 can be in RRM state machine mode 3 ( Figure 6(As shown in the image) Start CA operation mode.
[0101] In some embodiments, if the first device 110 receives a first MUSIM gap configuration from the second device 120 via a first RRC configuration, the first device may apply a first MUSIM gap configuration that matches the Rx RF requirements used in the RRM state mode, wherein each carrier is configured with a separate Rx RF chain.
[0102] Based on the received RRC configuration message or RRC reconfiguration message, the first device 110 can apply the configuration and send an (1015) RRC reconfiguration complete message to the second device 120.
[0103] In some embodiments, the first device 110 may decide to switch (1020) from mode 3 of the RRM state machine to mode 1 of the RRM state machine. (The above is in conjunction with...) Figure 6 Mode 3 and Mode 1 are described.
[0104] In some embodiments, two receive radio frequency (Rx RF) chains are used to receive two non-contiguous intra-band carriers in the first non-contiguous intra-band CA mode. In this scenario, mode 3 of the RRM state machine can be considered as the first non-contiguous intra-band CA mode.
[0105] Furthermore, in the second discontinuous in-band CA mode, an Rx RF chain is used to receive two discontinuous in-band carriers. In this scenario, mode 1 of the RRM state machine can be considered as the second discontinuous in-band CA mode.
[0106] At step 1025, the first SIM in connected mode can continue data transmission.
[0107] according to Figure 10 If the first SIM switches from the first non-continuous in-band CA mode to the second non-continuous in-band CA mode, the first device 110 may send (1030) a request for the second MUSIM gap configuration for the second non-continuous in-band CA mode.
[0108] For example, if the first SIM switches to fragmented CA, RRM state machine mode 1, the first device 110 can send a request to the second device 120 (i.e., network A) via L3 messages.
[0109] In some embodiments, the request may be indicated in user assistance information and transmitted via a Layer 3 message. This message may include, for example, user assistance information (UAI) for an updated MUSIM gap configuration that matches the RF configuration used in Mode 1.
[0110] In some embodiments, the request may indicate a preference for a gapless MUSIM configuration to apply an additional RRM state mode or an additional RRM state mode to be supported by the first SIM. Alternatively or additionally, the request may indicate an RRM state mode to be supported by the first SIM.
[0111] In step 1035, data transmission between the first SIM and the second device 120 can continue.
[0112] Based on this request, in some embodiments, the second device 120 may send (1040) a second MUSIM gap configuration for a second non-continuous in-band CA mode. The second MUSIM gap configuration may be sent via an RRC configuration message. Figure 10 In the scenario shown, the first MUSIM gap configuration and the second MUSIM gap configuration are sent via separate configuration messages.
[0113] For example, the second device 120 (network A) can send an RRC reconfiguration message with an updated MUSIM gap configuration 2 (i.e., the second MUSIM gap configuration) to the first device 110.
[0114] In some embodiments, a measurement gap configuration for inter-frequency or intra-frequency measurements on a first SIM operating in a different RRM state mode is obtained together with a second MUSIM gap configuration. For example, RRC reconfiguration (or RRC configuration) may also optionally include a measurement gap configuration for Mode 1 for intra-frequency and / or inter-frequency measurements on the first SIM.
[0115] like Figure 10 As shown, the first device 110 can send an (1045) RRC reconfiguration complete message to the second device 120.
[0116] In step 1050, data transmission between the first device 110 and the second device 120 can continue.
[0117] Based on the received second MUSIM gap configuration, if the first device 110 receives the second MUSIM gap configuration from the second device 120 via the second RRC configuration, the first device 110 can switch from the first MUSIM gap configuration to the second MUSIM gap configuration to support data scheduling on the first SIM during idle mode process operation on the second SIM of the first device 110.
[0118] like Figure 10As shown, if the first device 110 receives the second MUSIM gap configuration from the second device 120 via the second RRC configuration, the first device 110 can apply (1055) the second MUSIM gap configuration that matches the additional Rx RF requirements used in another RRM state mode, wherein the two carriers are received via a shared RF Rx chain.
[0119] For example, when operating in mode 1 on SIM1, the first device 110 can apply MUSIM gap configuration 2 (i.e., the second MUSIM gap configuration) for MUSIM operation. In this scenario, due to the presence of a released RF chain, and because gap configuration 2 will contain gapless MUSIM gap modes, there will be no scheduling restrictions on the operation of the first SIM during idle mode process operation on the second SIM. If the first SIM is in mode 1, gap configuration 2 will be applied to the MUSIM operation.
[0120] When the new MUSIM gap configuration is applied, MUSIM operation on one RX chain may be interrupted, and another RX chain may be tuned for the third device 130 (i.e., network B). During this process, paging or idle mode activity for the third device 130 and data transmission between the first device 110 and the second device 120 can still continue.
[0121] Now for reference Figure 11 This illustrates signaling diagram 1100 for communication according to some example embodiments of the present disclosure. For example... Figure 11 As shown, signaling diagram 1100 relates to a first device 110, a second device 120, and a third device 130. For discussion purposes, refer to... Figure 1 To describe signaling diagram 1100.
[0122] Figure 11 Some of the steps involved are similar to combining Figure 11 The steps described will not be repeated in detail here.
[0123] like Figure 11 As shown, the first device 110 (first SIM) can indicate (1105) capability information to the second device 120, which indicates that different types of MUSIM gap configurations associated with MUSIM DSDS operation are supported by the first device.
[0124] Based on the capability information, the second device 120 (i.e., network A) can determine the first MUSIM gap configuration to be used for the first non-continuous intra-band carrier aggregation (CA) mode and the second MUSIM gap configuration to be used for the second non-continuous intra-band CA mode.
[0125] Based on the capability information, the first device 110 can receive (1110) a first MUSIM gap configuration to be used for a first non-continuous in-band CA mode and a second MUSIM gap configuration to be used for a second non-continuous in-band CA mode from the second device 120 to which the first SIM of the first device 110 is connected via the same configuration message.
[0126] For example, the RRC reconfiguration message from the second device 120 (i.e., network A) contains multiple MUSIM gap configuration types (i.e., different MUSIM gap configurations) to be used for fragmented CA and non-fragmented CA operations on the first SIM.
[0127] The configuration messages mentioned above may include RRC configuration messages and RRC reconfiguration messages.
[0128] Based on the received configuration message, the first device 110 can apply the second MUSIM gap configuration to the first SIM operating in RRM state mode, where two carriers are received via a shared RF Rx chain.
[0129] If the configuration message is received correctly and the configuration is applied, the first device 110 may send an (1115) RRC configuration complete message to the second device 120 (network A).
[0130] like Figure 11 As shown, if the first SIM transitions from the second discontinuous intra-band CA mode to the first discontinuous intra-band CA mode, the first device 110 can roll back (1120) from the second MUSIM gap configuration to the first MUSIM gap configuration during idle mode process operation on the second SIM of the first device 110, while data scheduling on the first SIM is restricted. The restrictions mentioned herein can be derived from... Figure 11 Box 1180 shown in the figure represents this.
[0131] Based on the rollback (or switching) of the RRM state mode, the first device 110 can send (1125) a first MUSIM gap configuration and an indication of an additional RRM state mode to be used by the first SIM to the second device 120 via a Layer 2 message. The Layer 2 message may include a MAC CE message.
[0132] Alternatively or additionally, the MUSIM gap configuration switching when entering the rollback RRM state machine mode 3 can be communicated between the first device 110 and the second device 120 (i.e., network A) via L3 signaling messages. The L3 signaling messages may include UAI messages.
[0133] For example, if the first SIM switches to non-fragmented CA, the RRM state machine mode 3 and the first device 110 (first SIM) send an indication in the L2 signal to fall back to MUSIM gap configuration type 1 (i.e., the first MUSIM gap configuration) and RRM mode. This indication can be carried by the UL MAC CE on the PCell, which can be sent to the second device 120 (i.e., network A) to indicate that the first device 110 has switched to MUSIM gap configuration 1 to match the RF configuration of mode 1.
[0134] In some embodiments, if the first device 110 determines that a second discontinuous in-band CA mode is to be used by the first device 110, the first device 110 may apply a second MUSIM gap configuration that matches another Rx RF requirement used in RRM state mode, wherein the two carriers are received via a shared RF Rx chain.
[0135] like Figure 11 As shown, if the first SIM transitions from the second discontinuous in-band CA mode to the first discontinuous in-band CA mode, the first device 110 can apply (1130) a first MUSIM gap configuration that matches the Rx RF requirements used in another RRM state mode, wherein each carrier is configured with a separate Rx RF chain.
[0136] For example, when operating in mode 3 on the first SIM, the first device 110 can apply MUSIM gap configuration 1 (i.e., the first MUSIM gap configuration) for MUSIM operation. In this scenario, since there is no idle RF chain and gap configuration 1 will contain MUSIM gaps, there will be scheduling constraints on the operation of the first SIM during idle mode process operation on the second SIM. The scheduling constraints are shown in block 1180.
[0137] After the MUSIM gap ends, the scheduling restrictions are removed and data transmission resumes. If the first SIM is in mode 3, gap configuration 1 will be applied to the MUSIM operation.
[0138] Figure 12 A flowchart of an example method 1200 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 1200 is described by the angle of the first device 110 in the middle.
[0139] In block 1210, the first device 110 receives a first MUSIM gap configuration for a first non-continuous in-band CA mode from a second device to which the first SIM of the first device is connected via a first RRC configuration message.
[0140] At block 1220, based on the first SIM switching from a first discontinuous in-band CA mode to a second discontinuous in-band CA mode, the first device 110 sends a request for a second MUSIM gap configuration for the second discontinuous in-band CA mode.
[0141] At block 1230, based on receiving a second MUSIM gap configuration from the second device via a second RRC configuration, the first device 110 switches from a first MUSIM gap configuration to a second MUSIM gap configuration to support data scheduling on the first SIM during idle mode process operation on the second SIM of the first device.
[0142] In some example embodiments, two receive radio frequency (Rx) RF chains are used to receive two non-contiguous intra-band carriers in a first non-contiguous intra-band CA mode, and one Rx RF chain is used to receive two non-contiguous intra-band carriers in a second non-contiguous intra-band CA mode.
[0143] In some example embodiments, the request is indicated in user assistance information and transmitted via layer 3 messages.
[0144] In some example embodiments, method 1200 further includes: receiving a first MUSIM gap configuration from a second device via a first RRC configuration, and applying a first MUSIM gap configuration that matches the Rx RF requirements used in the Radio Resource Management (RRM) state mode, wherein each carrier is configured with a separate Rx RF chain.
[0145] In some example embodiments, method 1200 further includes: receiving a second MUSIM gap configuration from the second device via a second RRC configuration, and applying a second MUSIM gap configuration that matches additional Rx RF requirements used in a separate RRM state mode, wherein the two carriers are received via a shared RF Rx chain.
[0146] In some example embodiments, the request indicates a preference for gapless MUSIM configuration to apply an additional RRM state mode or an additional RRM state mode to be supported by the first SIM.
[0147] In some example embodiments, the measurement gap configuration for inter-frequency or intra-frequency measurements on the first SIM used in a different RRM state mode is obtained together with the second MUSIM gap configuration.
[0148] In some example embodiments, method 1200 further includes: indicating capability information to a second device, the capability information indicating that different types of MUSIM gap configurations associated with MUSIM Dual SIM Dual Standby (DSDS) operation are supported by the first device.
[0149] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.
[0150] Figure 13 A flowchart of an example method 1300 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 1300 is described by the angle of the second device 120 in the middle.
[0151] In block 1310, the second device 120 sends a first MUSIM gap configuration for a first discontinuous in-band CA mode to the first device via a first radio resource control (RRC) configuration message, the first device having a first subscriber identification module (SIM) connected to the second device.
[0152] In block 1320, based on a request received from the first device for a second MUSIM gap configuration for a second discontinuous in-band CA mode, the second device 120 sends the second MUSIM gap configuration to the first device to support data scheduling on the first SIM during idle mode process operation on the second SIM of the first device.
[0153] In some example embodiments, two non-contiguous in-band carriers are received using two receive radio frequency (Rx RF) chains in a first non-contiguous in-band CA mode, and the two non-contiguous in-band carriers are received using one Rx RF chain in a second non-contiguous in-band CA mode.
[0154] In some example embodiments, the request is indicated in user assistance information and transmitted via layer 3 messages.
[0155] In some example embodiments, the request indicates a preference for a gapless MUSIM configuration that matches the Rx RF requirements used in the RRM state mode, where the two carriers are received via a shared RF Rx link, or the RRM state is to be supported by a first device.
[0156] In some example embodiments, a measurement gap configuration for inter-frequency or intra-frequency measurements on the first SIM operating in RRM state mode is provided together with a second MUSIM gap configuration.
[0157] In some example embodiments, method 1300 further includes receiving capability information from a first device, the capability information indicating that different types of MUSIM gap configurations associated with MUSIM Dual SIM Dual Standby (DSDS) operation are supported by the first device.
[0158] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.
[0159] Figure 14 A flowchart of an example method 1400 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 1400 is described by the angle of the first device 110 in the middle.
[0160] In block 1410, the first device 110 receives, via the same configuration message, a first multi-purpose subscriber identification module (MUSIM) gap configuration to be used for a first non-continuous intra-band carrier aggregation (CA) mode and a second MUSIM gap configuration to be used for a second non-continuous intra-band CA mode from a second device to which the first device is connected.
[0161] At box 1420, according to the first SIM switching from the second discontinuous intra-band CA mode to the first discontinuous intra-band CA mode, the first device 110, during the idle mode process operation on the second SIM of the first device, while data scheduling on the first SIM is restricted, falls back from the second MUSIM gap configuration to the first MUSIM gap configuration.
[0162] In some example embodiments, two non-contiguous in-band carriers are received using two receive radio frequency (Rx) RF chains in a first non-contiguous in-band CA mode, and the two non-contiguous in-band carriers are received using one Rx RF chain in a second non-contiguous in-band CA mode.
[0163] In some example embodiments, method 1400 further includes: indicating capability information to a second device, the capability information indicating that different types of MUSIM gap configurations associated with MUSIM dual SIM dual standby DSDS operation are supported by the first device.
[0164] In some example embodiments, method 1400 further includes: based on determining that a second discontinuous in-band CA mode is to be used by the first device, applying a second MUSIM gap configuration that matches an additional Rx RF requirement used in the Radio Resource Management (RRM) state mode, wherein the two carriers are received via a shared RF Rx link.
[0165] In some example embodiments, method 1400 further includes: applying a first MUSIM gap configuration that matches the Rx RF requirements used in another RRM state mode, based on the transition from a second discontinuous in-band CA mode to a first discontinuous in-band CA mode according to the first SIM, wherein each carrier is configured with a separate Rx RF chain.
[0166] In some example embodiments, method 1400 further includes sending an indication to a second device via a layer 2 message of the first MUSIM gap configuration and an additional RRM state mode to be used by the first SIM.
[0167] In some example embodiments, the measurement gap configuration for inter-frequency or intra-frequency measurements on the first SIM operating in RRM state mode is obtained together with the second MUSIM gap configuration, wherein the two carriers are received via a shared RF Rx chain.
[0168] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.
[0169] Figure 15 A flowchart of an example method 1500 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 1500 is described by the angle of the second device 120 in the middle.
[0170] In block 1510, the second device 120 sends a first MUSIM gap configuration and a second MUSIM gap configuration to the first device having a first subscriber identification module (SIM) connected to the second device via the same configuration message.
[0171] In some example embodiments, two non-contiguous in-band carriers are received using two receive radio frequency (Rx) RF chains in a first non-contiguous in-band CA mode, and the two non-contiguous in-band carriers are received using one Rx RF chain in a second non-contiguous in-band CA mode.
[0172] In some example embodiments, method 1500 further includes receiving from a first device via a layer 2 message an indication of an RRM state mode to be used by a first SIM and a first MUSIM gap configuration, wherein each carrier is configured with a separate Rx RF chain, the RRM state mode being used by the first SIM after the first SIM transitions from a second discontinuous intra-band CA mode to a first discontinuous intra-band CA mode.
[0173] In some example embodiments, a measurement gap configuration for inter-frequency or intra-frequency measurements on a first SIM operating in a different RRM state mode is provided together with a second MUSIM gap configuration, wherein the two carriers are received via a shared RF Rx link and the second MUSIM gap configuration.
[0174] In some example embodiments, method 1500 further includes receiving capability information from a first device, the capability information indicating that different types of MUSIM gap configurations associated with MUSIM dual SIM dual standby DSDS operation are supported by the first device.
[0175] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.
[0176] In some example embodiments, any of the first means of method 1200 can be performed (e.g., Figure 1 The first device 110 may include components for performing the corresponding operations of method 1200. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 1 In the first device 110.
[0177] In some example embodiments, the first device includes: means for receiving, via a first Radio Resource Control (RRC) configuration message, a first Multi-Universal Subscriber Identity Module (MUSIM) gap configuration for a first discontinuous intra-band CA mode from a second device, wherein a first subscriber identity module (SIM) of the first device is connected to the second device; means for sending a request for a second MUSIM gap configuration for the second discontinuous intra-band CA mode based on a transition from the first discontinuous intra-band CA mode to a second discontinuous intra-band CA mode according to the first SIM; and means for switching from the first MUSIM gap configuration to the second MUSIM gap configuration based on a second RRC configuration received from the second device to support data scheduling on the first SIM during idle mode procedure operation on the second SIM of the first device.
[0178] In some example embodiments, two non-contiguous in-band carriers are received using two receive radio frequency (Rx) RF chains in a first non-contiguous in-band CA mode, and the two non-contiguous in-band carriers are received using one Rx RF chain in a second non-contiguous in-band CA mode.
[0179] In some example embodiments, the request is indicated in user assistance information and transmitted via Layer 3 messages.
[0180] In some example embodiments, the first device further includes: a component for receiving a first MUSIM gap configuration from the second device via a first RRC configuration and applying a first MUSIM gap configuration that matches the Rx RF requirements used in the Radio Resource Management (RRM) state mode, wherein each carrier is configured with a separate Rx RF chain.
[0181] In some example embodiments, the first device further includes: a component for receiving a second MUSIM gap configuration from the second device via a second RRC configuration and applying a second MUSIM gap configuration that matches additional Rx RF requirements used in a separate RRM state mode, wherein the two carriers are received via a shared RF Rx link.
[0182] In some example embodiments, the request indicates a preference for gapless MUSIM configuration to apply an additional RRM state mode or an additional RRM state mode to be supported by the first SIM.
[0183] In some example embodiments, the measurement gap configuration for inter-frequency or intra-frequency measurements on the first SIM used in a different RRM state mode is obtained together with the second MUSIM gap configuration.
[0184] In some example embodiments, the first device further includes a component for indicating capability information to the second device, the capability information indicating that different types of MUSIM gap configurations associated with MUSIM dual SIM dual standby DSDS operation are supported by the first device.
[0185] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.
[0186] In some example embodiments, any of the second means of method 1300 can be performed (e.g., Figure 1 The second device 120 may include components for performing the corresponding operations of method 1300. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The second device may be implemented as or included in... Figure 1 The second device 120 in the middle.
[0187] In some example embodiments, the second device includes: means for sending a first MUSIM gap configuration for a first discontinuous in-band CA mode to a first device via a first radio resource control (RRC) configuration message, the first device having a first subscriber identification module (SIM) connected to the second device; and means for sending a second MUSIM gap configuration to the first device upon receiving a request from the first device for a second MUSIM gap configuration for a second discontinuous in-band CA mode to support data scheduling on the first SIM during idle mode process operation on the second SIM of the first device.
[0188] In some example embodiments, two non-contiguous in-band carriers are received using two receive radio frequencies (Rx RF) links in a first non-contiguous in-band CA mode, and the two non-contiguous in-band carriers are received using one Rx RF link in a second non-contiguous in-band CA mode.
[0189] In some example embodiments, the request is indicated in user assistance information and is transmitted via Layer 3 messages.
[0190] In some example embodiments, the request indicates a preference for a gapless MUSIM configuration that matches the Rx RF requirements used in the RRM state mode, where the two carriers are received via a shared RF Rx link, or the RRM state will be supported by a first device.
[0191] In some example embodiments, a measurement gap configuration for inter-frequency or intra-frequency measurements on the first SIM operating in RRM state mode is provided together with a second MUSIM gap configuration.
[0192] In some example embodiments, the second device further includes a component for receiving capability information from the first device, the capability information indicating that different types of MUSIM gap configurations associated with MUSIM Dual SIM Dual Standby (DSDS) operation are supported by the first device.
[0193] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.
[0194] In some example embodiments, any of the first means of method 1400 can be performed (e.g., Figure 1 The first device 110 may include a component for performing a corresponding operation of method 1400. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 1 In the first device 110.
[0195] In some example embodiments, the first device includes: components for receiving, via the same configuration message, a first multi-purpose subscriber identification module (MUSIM) gap configuration to be used for a first discontinuous intra-band carrier aggregation (CA) mode and a second MUSIM gap configuration to be used for a second discontinuous intra-band CA mode from a second device connected to a first subscriber identification module (SIM) of the first device; and components for falling back from the second MUSIM gap configuration to the first MUSIM gap configuration during an idle mode process operation on the second SIM of the first device when data scheduling on the first SIM is restricted, based on the first SIM transitioning from the second discontinuous intra-band CA mode to the first discontinuous intra-band CA mode according to the first SIM.
[0196] In some example embodiments, two non-contiguous in-band carriers are received using two receive radio frequency (Rx) RF chains in a first non-contiguous in-band CA mode, and the two non-contiguous in-band carriers are received using one Rx RF chain in a second non-contiguous in-band CA mode.
[0197] In some example embodiments, the first device further includes a component for indicating capability information to the second device, the capability information indicating that different types of MUSIM gap configurations associated with MUSIM dual SIM dual standby DSDS operation are supported by the first device.
[0198] In some example embodiments, the first device further includes: a component for applying a second MUSIM gap configuration that matches an additional Rx RF requirement used in a Radio Resource Management (RRM) state mode, based on determining that a second discontinuous in-band CA mode is to be used by the first device, wherein the two carriers are received via a shared RF Rx link.
[0199] In some example embodiments, the first device further includes: a component for applying a first MUSIM gap configuration that matches the Rx RF requirements used in an additional RRM state mode when switching from a second discontinuous in-band CA mode to a first discontinuous in-band CA mode based on a first SIM, wherein each carrier is configured with a separate Rx RF chain.
[0200] In some example embodiments, the first device further includes a component for sending an indication to the second device via a layer 2 message of an additional RRM state mode to be used by the first SIM and a first MUSIM gap configuration.
[0201] In some example embodiments, the measurement gap configuration for inter-frequency or intra-frequency measurements on the first SIM operating in RRM state mode is obtained together with the second MUSIM gap configuration, wherein the two carriers are received via a shared RF Rx chain.
[0202] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.
[0203] In some example embodiments, any of the second means of method 1500 can be performed (e.g., Figure 1 The second device 120 may include components for performing the corresponding operations of method 1500. These components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module. The second device may be implemented as or included in... Figure 1 The second device 120 in the middle.
[0204] In some example embodiments, the second device includes components for sending a first MUSIM gap configuration and a second MUSIM gap configuration to a first device having a first subscriber identification module (SIM) connected to the second device via the same configuration message.
[0205] In some example embodiments, two non-contiguous in-band carriers are received using two receive radio frequency (Rx) RF chains in a first non-contiguous in-band CA mode, and the two non-contiguous in-band carriers are received using one Rx RF chain in a second non-contiguous in-band CA mode.
[0206] In some example embodiments, the second device further includes: a component for receiving, via a layer 2 message, an indication of an RRM state mode to be used by the first SIM and a first MUSIM gap configuration, wherein each carrier is configured with a separate Rx RF chain, the RRM state mode being used by the first SIM after the first SIM transitions from a second discontinuous intra-band CA mode to a first discontinuous intra-band CA mode.
[0207] In some example embodiments, a measurement gap configuration for inter-frequency or intra-frequency measurements on the first SIM for operation in a different RRM state mode is provided together with a second MUSIM gap configuration, wherein the two carriers are received via a shared RF Rx link.
[0208] In some example embodiments, the second device further includes a component for receiving capability information from the first device, the capability information indicating that different types of MUSIM gap configurations associated with MUSIM dual SIM dual standby DSDS operation are supported by the first device.
[0209] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.
[0210] Figure 16 This is a simplified block diagram of a device 1600 suitable for implementing an example embodiment of the present disclosure. Device 1600 can be provided to implement a communication device, such as... Figure 1 The first device 110 or the second device 120 shown. As shown, the device 1600 includes one or more processors 1610, one or more memories 1620 coupled to the processors 1610, and one or more communication modules 1640 coupled to the processors 1610.
[0211] Communication module 1640 is used for bidirectional communication. Communication module 1640 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface necessary for communication with other network elements. In some example embodiments, communication module 1640 may include at least one antenna.
[0212] As a non-limiting example, processor 1610 can be any type suitable for a local technology network and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 1600 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.
[0213] Memory 1620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1624, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1622 and other volatile memories that will not be retained during power loss.
[0214] Computer program 1630 includes computer-executable instructions that are executed by an associated processor 1610. The instructions of program 1630 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 1630 may be stored in memory (e.g., ROM 1624). Processor 1610 can perform any suitable actions and processes by loading program 1630 into RAM 1622.
[0215] Example embodiments of this disclosure can be implemented by program 1630, enabling device 1600 to perform as described in the reference. Figures 2 to 15 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or a combination of software and hardware.
[0216] In some example embodiments, program 1630 may be tangibly included in a computer-readable medium, which may be included in device 1600 (such as in memory 1620) or in other storage devices accessible by device 1600. Device 1600 may load program 1630 from the computer-readable medium into RAM 1622 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation of the medium itself (i.e., tangible, not tactile), rather than a limitation of the persistence of data storage (e.g., RAM versus ROM).
[0217] Figure 17An example of a computer-readable medium 1700 is shown, which may be in the form of a CD, DVD, or other optical storage disc. The computer-readable medium 1700 has a program 1630 stored thereon.
[0218] In general, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, and others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.
[0219] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions, such as those included in a program module, which are executed in a device on a target physical or virtual processor to perform any of the methods described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, the program module can reside on both local and remote storage media.
[0220] Program code for performing the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be performed. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0221] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier wave to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carrier waves include signals, computer-readable media, etc.
[0222] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0223] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or requiring that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure, but rather as a description of features that may be specific to particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.
[0224] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.
[0225] Furthermore, the various implementations of this disclosure can be described with reference to the following terms, and their features can be combined in any reasonable manner.
[0226] Clause 1. A first device for communication, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first device to at least: receive a first Multi-Universal Subscriber Identity Module (MUSIM) gap configuration and a second MUSIM gap configuration from a second device via the same configuration message, wherein the first MUSIM of the first device is connected to the second device, the first MUSIM gap configuration is to be used for a first discontinuous intra-band carrier aggregation (CA) mode, and the second MUSIM gap configuration is to be used for a second discontinuous intra-band CA mode; and switch from the second discontinuous intra-band CA mode to the first discontinuous intra-band CA mode according to the first SIM, while data scheduling on the first SIM is restricted during idle mode process operation on the second SIM of the first device, and fall back from the second MUSIM gap configuration to the first MUSIM gap configuration.
[0227] Clause 2. The first apparatus according to Clause 1, wherein two discontinuous in-band carriers are received using two receive radio frequency (Rx) RF chains in the first discontinuous in-band CA mode, and wherein two discontinuous in-band carriers are received using one Rx RF chain in the second discontinuous in-band CA mode.
[0228] Clause 3. The first device according to Clause 1, wherein the first device is configured to: indicate capability information to the second device, the capability information indicating that different types of MUSIM gap configurations associated with MUSIM dual SIM dual standby DSDS operation are supported by the first device.
[0229] Clause 4. The first device according to Clause 2, wherein the first device is configured such that: if it is determined that a second discontinuous in-band CA mode is to be used by the first device, the second MUSIM gap configuration matching the additional Rx RF requirements used in the Radio Resource Management (RRM) state mode is applied, wherein the two carriers are received via a shared RF Rx chain.
[0230] Clause 5. The first means according to Clause 4, wherein the first means is configured to: apply the first MUSIM gap configuration matching the Rx RF requirements used in another RRM state mode when switching from the second discontinuous in-band CA mode to the first discontinuous in-band CA mode according to the first SIM, wherein each carrier is configured with a separate Rx RF chain.
[0231] Clause 6. The first device according to Clause 5, wherein the first device is configured to send an indication to the second device via a Layer 2 message of the configuration of the first MUSIM gap and the additional RRM state mode to be used by the first SIM.
[0232] Clause 7. A first device according to any one of Clauses 1 to 6, wherein the measurement gap configuration for inter-frequency or intra-frequency measurements on the first SIM for operation in RRM state mode is obtained together with the second MUSIM gap configuration, wherein the two carriers are received via a shared RF Rx chain.
[0233] Clause 8. A second device for communication, comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second device to at least: send a first MUSIM gap configuration and a second MUSIM gap configuration to a first device via the same configuration message, the first device having a first subscriber identification module (SIM) connected to the second device.
[0234] Clause 9. The second apparatus according to Clause 8, wherein two discontinuous in-band carriers are received using two receive radio frequency (Rx) RF chains in the first discontinuous in-band CA mode, and wherein two discontinuous in-band carriers are received using one Rx RF chain in the second discontinuous in-band CA mode.
[0235] Clause 10. The second means according to Clause 8, wherein the second means is configured to receive from the first means via a layer 2 message an indication of the RRM state mode to be used by the first SIM and the first MUSIM gap configuration, wherein each carrier is configured with a separate Rx RF chain, the RRM state mode to be used by the first SIM after the first SIM transitions from the second discontinuous in-band CA mode to the first discontinuous in-band CA mode.
[0236] Clause 11. The second apparatus according to Clause 9, wherein a measurement gap configuration for inter-frequency or intra-frequency measurements on the first SIM for operation in a separate RRM state mode is provided together with the second MUSIM gap configuration, wherein the two carriers are received via a shared RF Rx chain.
[0237] Clause 12. A second device according to any one of Clauses 8-11, wherein the second device is configured to: receive capability information from the first device indicating that different types of MUSIM gap configurations associated with MUSIM dual SIM dual standby DSDS operation are supported by the first device.
[0238] Clause 13. A method for communication, comprising: receiving, by a first device, a first MUSIM gap configuration and a second MUSIM gap configuration from a second device via the same configuration message, the first MUSIM of the first device being connected to the second device, the first MUSIM gap configuration being intended for use in a first discontinuous intra-band carrier aggregation (CA) mode, and the second MUSIM gap configuration being intended for use in a second discontinuous intra-band CA mode; and switching from the second discontinuous intra-band CA mode to the first discontinuous intra-band CA mode based on the first SIM, while data scheduling on the first SIM is restricted during idle mode process operation on the second SIM of the first device, and falling back from the second MUSIM gap configuration to the first MUSIM gap configuration.
[0239] Clause 14. A method for communication, comprising: sending a first MUSIM gap configuration and a second MUSIM gap configuration from a second device to a first device via the same configuration message, the first device having a first subscriber identification module (SIM) connected to the second device.
Claims
1. A first device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first device to at least: The first MUSIM gap configuration and the second MUSIM gap configuration are received from the second device via the same configuration message. The first SIM of the first device is connected to the second device. The first MUSIM gap configuration is to be used for the first non-continuous intra-band carrier aggregation (CA) mode, and the second MUSIM configuration is to be used for the second non-continuous intra-band CA mode. as well as According to the first SIM switching from the second discontinuous in-band CA mode to the first discontinuous in-band CA mode, during the idle mode process operation on the second SIM of the first device, while data scheduling on the first SIM is restricted, the system falls back from the second MUSIM gap configuration to the first MUSIM gap configuration.
2. The first apparatus of claim 1, wherein the two discontinuous in-band carriers are received using two receive radio frequency (Rx) RF chains in the first discontinuous in-band CA mode, and wherein the two discontinuous in-band carriers are received using one Rx RF chain in the second discontinuous in-band CA mode.
3. The first device according to claim 1, wherein the first device is configured to: The second device is instructed with capability information indicating that different types of MUSIM gap configurations associated with MUSIM dual SIM dual standby DSDS operation are supported by the first device.
4. The first device according to claim 2, wherein the first device is configured to: If it is determined that the second discontinuous in-band CA mode is to be used by the first device, then the second MUSIM gap configuration is applied to match the additional Rx RF requirements used in the Radio Resource Management (RRM) state mode, wherein the two carriers are received via a shared RF Rx chain.
5. The first device according to claim 4, wherein the first device is configured to: According to the first SIM transitioning from the second discontinuous in-band CA mode to the first discontinuous in-band CA mode, the first MUSIM gap configuration is applied to match the Rx RF requirements used in the other RRM state mode, wherein each carrier is configured with a separate Rx RF chain.
6. The first device according to claim 5, wherein the first device is configured to: Instructions for the first MUSIM gap configuration and the additional RRM state mode to be used by the first SIM are sent to the second device via Layer 2 messages.
7. The first apparatus according to any one of claims 1 to 6, wherein the measurement gap configuration for inter-frequency or intra-frequency measurements on the first SIM operating in RRM state mode is obtained together with the second MUSIM gap configuration, wherein the two carriers are received via a shared RF Rx chain.
8. A second means for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the second device to at least: The first MUSIM gap configuration and the second MUSIM gap configuration are sent to the first device via the same configuration message. The first device has a first subscriber identification module (SIM) connected to the second device.
9. The second apparatus of claim 8, wherein the two discontinuous in-band carriers are received using two receive radio frequency (Rx) RF chains in the first discontinuous in-band CA mode, and wherein the two discontinuous in-band carriers are received using one Rx RF chain in the second discontinuous in-band CA mode.
10. The second device according to claim 8, wherein the second device is configured to: The RRM state mode to be used by the first SIM and the first MUSIM gap configuration are received from the first device via a layer 2 message, wherein each carrier is configured with a separate Rx RF chain, and the RRM state mode will be used by the first SIM after the first SIM transitions from the second discontinuous intra-band CA mode to the first discontinuous intra-band CA mode.