Method and apparatus for configuring musim gap in dual connectivity in communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments of the present disclosure describe a method and system for configuring multiple Universal Subscriber Identity Module (MUSIM) gaps for multiple Subscriber Identity Module User Equipments (UEs) in a communications network. The method includes receiving (402), at a master node associated with a network entity, a gap configuration request from a multi-SIM UE. Further, the method includes configuring, by the master node, the MUSIM gap to the multi-SIM UE based on the received gap configuration request. Further, the method includes sending, by the primary node to a secondary node associated with the network entity, a message indicating the MUSIM gap configured for the multi-SIM UE, where the message includes information related to a gap priority of the MUSIM gap.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, and more particularly, to methods and systems for configuring multi-universal subscriber identity module (MUSIM) gaps for multi-SIM user equipment (UE) under dual connectivity. Background Art

[0002] 5G mobile communications technology defines a wide frequency band, enabling high transmission rates and new services. 5G mobile communications technology can be implemented not only in "sub-6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands, known as millimeter waves, including 28 GHz and 39 GHz. Furthermore, to achieve transmission rates 50 times faster than 5G mobile communications technology and ultra-low latency one-tenth that of 5G mobile communications technology, consideration has been given to implementing 6G mobile communications technology in the terahertz frequency band (e.g., the 95 GHz to 3 THz band) (referred to as "beyond 5G systems").

[0003] In the early stages of the development of 5G mobile communication technology, in order to support services and meet the performance requirements related to enhanced Mobile BroadBand (eMBB), Ultra Reliable & Low Latency Communications (URLLC) and massive Machine-Type Communications (mMTC), standardization is underway on the following: beamforming and massive MIMO to mitigate radio wave path loss and increase radio wave transmission distance in millimeter waves; support parameter sets (e.g., operating multiple subcarrier spacings) for efficient utilization of millimeter wave resources and dynamic operation of time slot formats; initial access technology to support multi-beam transmission and broadband; definition and operation of BWP (BandWidth Part); new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and polar codes for highly reliable transmission of control information; L2 preprocessing; and network slicing to provide dedicated networks dedicated to specific services.

[0004] Currently, discussions are underway on improvements and performance enhancements to initial 5G mobile communication technologies in view of the services they will support, and there is already physical layer standardization on technologies such as: Vehicle-to-everything (V2X), for assisting driving determinations of autonomous vehicles based on information sent by vehicles about their location and status, and for enhancing user convenience; New Radio Unlicensed (NR-U), for system operation complying with various regulatory requirements in unlicensed frequency bands; NR UE energy saving; Non-Terrestrial Network (NTN), which is UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable; and positioning.

[0005] Furthermore, in terms of air interface architecture / protocols, standardization is underway on technologies such as the Industrial Internet of Things (IIoT), which supports new services through interoperability and integration with other industries; Integrated Access and Backhaul (IAB), which provides a node for network service area expansion by integrating wireless backhaul and access links; enhanced mobility, including conditional handover and DAPS (Dual Active Protocol Stack) handover; and two-step random access, which simplifies the random access procedure (2-step RACH (Random Access Channel) for NR). In terms of system architecture / services, standardization is also underway on the following: 5G baseline architecture (e.g., service-based architecture or service-based interface), which combines Network Function Virtualization (NFV) and Software-Defined Networking (SDN) technologies; and Mobile Edge Computing (MEC), which enables UE location-based service delivery.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially increasing number of connected devices will be connected to the communication network. Therefore, it is expected that enhanced functionality and performance of 5G mobile communication systems and the integrated operation of connected devices will be necessary. To this end, new research is planned related to: extended reality (XR) for effectively supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc.; improving 5G performance and reducing complexity by leveraging artificial intelligence (AI) and machine learning (ML); AI service support; metaverse service support; and drone communications.

[0007] Furthermore, this development of 5G mobile communication systems will serve not only as a foundation for the development of new waveforms for providing coverage in the terahertz band for 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas, and massive antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM), and reconfigurable intelligent surfaces (RIS), but also as a foundation for the development of full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technologies for achieving system optimization by leveraging satellites and artificial intelligence (AI) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technologies for enabling services with a level of complexity that exceeds the operational capabilities of UEs by utilizing ultra-high-performance communication and computing resources. Summary of the Invention

[0008] Technical issues

[0009] The present disclosure relates to wireless communication systems, and more particularly, to MUSIM gaps in dual connectivity in a communication system.

[0010] Solution to the problem

[0011] This summary is provided to introduce some concepts in a simplified form that will be further described in the detailed description of the present disclosure. This summary is not intended to identify key or essential inventive concepts of the present disclosure, nor is it intended to determine the scope of the present disclosure.

[0012] According to one embodiment of the present disclosure, a method for configuring a multi-universal subscriber identity module (MUSIM) gap for a multi-subscriber identity module (SIM) user equipment (UE) in a communications network is disclosed. The method includes receiving, at a primary node associated with a network entity of the communications network, a gap configuration request from the multi-SIM UE. Furthermore, the method includes generating, by the primary node, a configuration for the multi-SIM UE having a MUSIM gap based on the received gap configuration request. Furthermore, the method includes sending, by the primary node, a message indicating the MUSIM gap configured for the multi-SIM UE to a secondary node associated with the network entity, wherein the message includes information related to a gap priority of the MUSIM gap.

[0013] According to one embodiment of the present disclosure, a system for configuring a multi-universal subscriber identity module (MUSIM) gap for a multi-subscriber identity module (SIM) user equipment (UE) in a communications network is disclosed. The system includes a primary node and a secondary node. The system is configured to receive a gap configuration request from a multi-SIM UE at the primary node associated with a network entity. Furthermore, the system is configured to generate, by the primary node, a configuration for the multi-SIM UE with a MUSIM gap based on the received gap configuration request. Furthermore, the system is configured to send, by the primary node, a message indicating the MUSIM gap configured for the multi-SIM UE to the secondary node associated with the network entity, wherein the message includes information related to a gap priority of the MUSIM gap.

[0014] To further illustrate the advantages and features of the present disclosure, a more detailed description of the present disclosure will be presented by reference to specific embodiments of the present disclosure shown in the accompanying drawings. It should be understood that these drawings depict only typical embodiments of the present disclosure and are not to be considered as limiting the scope of the present disclosure. Additional features and details will be used in the accompanying drawings to describe and explain the present disclosure.

[0015] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprising" and their derivatives are meant to include, but are not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean including, being included, interconnected with, containing, being contained within, connected to or connected with, coupled to or coupled with, communicable with, cooperating with, interwoven, juxtaposed, proximate, bound to or bound with, having, having the property of, and the like; the term "controller" means any device, system, or portion thereof that controls at least one operation, which device may be implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0016] In addition, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed from computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, related data, or portions thereof, suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard drive, compact disc (CD), digital video disc (DVD), or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes both media that can permanently store data and media that can store and later overwrite data, such as rewritable optical discs or erasable memory devices.

[0017] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0018] In one embodiment, a method is provided. The method is performed by a user equipment (UE) in a communication system, the method comprising: sending a request message for at least one Multiple Universal Subscriber Identity Module (MUSIM) gap to a first base station; receiving a radio resource control (RRC) message including a configuration of at least one MUSIM gap from the first base station, the configuration including information associated with a MUSIM gap priority; and performing a MUSIM gap configuration procedure based on the MUSIM gap priority, wherein the information associated with the MUSIM gap priority is sent from the first base station to a second base station.

[0019] In one embodiment, a method is provided. The method is performed by a first base station in a communication system, the method comprising: receiving a request message for at least one Multiple Universal Subscriber Identity Module (MUSIM) gap from a user equipment (UE); and sending a radio resource control (RRC) message including a configuration of at least one MUSIM gap to the UE, the configuration including information associated with a MUSIM gap priority, wherein a MUSIM gap configuration procedure based on the MUSIM gap priority is performed, and wherein the information associated with the MUSIM gap priority is sent to a second base station. In one embodiment, a UE is provided. The UE comprises: a transceiver; and a controller coupled to the transceiver, the controller configured to: send a request message for at least one Multiple Universal Subscriber Identity Module (MUSIM) gap to the first base station; receive a radio resource control (RRC) message including a configuration of at least one MUSIM gap from the first base station, the configuration including information associated with the MUSIM gap priority; and perform a MUSIM gap configuration procedure based on the MUSIM gap priority, wherein the information associated with the MUSIM gap priority is sent from the first base station to the second base station.

[0020] In one embodiment, a first base station is provided. The first base station in a communication system includes a transceiver and a controller coupled to the transceiver, the controller configured to: receive a request message for at least one Multiple Universal Subscriber Identity Module (MUSIM) gap from a user equipment (UE); and send a radio resource control (RRC) message including a configuration of at least one MUSIM gap to the UE, the configuration including information associated with a MUSIM gap priority, wherein a MUSIM gap configuration procedure based on the MUSIM gap priority is performed, and wherein the information associated with the MUSIM gap priority is sent to a second base station.

[0021] Advantageous Effects of the Invention

[0022] According to the embodiments of the present disclosure, wireless communication can be performed efficiently. In particular, MUSIM gaps can be efficiently configured in dual connectivity in a communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] These and other features, aspects, and advantages of the present disclosure will become more readily understood upon reading the following detailed description with reference to the accompanying drawings (like numerals represent like parts throughout), in which:

[0024] Figure 1 shows an example of a communication environment associated with a communication network according to embodiments as disclosed herein;

[0025] Figure 2 shows a timing diagram depicting communications between a multi-SIM UE (e.g., a first USIM configured for dual connectivity) in a communication network, a primary node (associated with a first network associated with the first USIM), and a secondary node for configuring MUSIM gap for the multi-SIM UE according to embodiments as disclosed herein;

[0026] Figure 3 shows a flow chart depicting the operation / behavior of a secondary node with gap priority according to embodiments as disclosed herein; and

[0027] Figure 4 Shown is a method flow diagram depicting a method for configuring MUSIM gap for a multi-SIM UE in a communication network according to embodiments as disclosed herein.

[0028] Furthermore, those skilled in the art will appreciate that the elements in the accompanying drawings are illustrated for simplicity and may not necessarily be drawn to scale. For example, a flow chart illustrates a method in terms of the most essential steps involved to help enhance understanding of various aspects of the present disclosure. Furthermore, with respect to the construction of a device, one or more components of the device may have been represented in the accompanying drawings by conventional symbols, and the accompanying drawings may show only those specific details that are relevant to understanding the embodiments of the present disclosure so as not to obscure the drawings with details that would be apparent to one of ordinary skill in the art having the benefit of the description herein. DETAILED DESCRIPTION

[0029] A multi-Subscriber Identity Module (SIM) device is a device that hosts more than one SIM, allowing multiple SIMs to connect to two or more different networks to utilize different data plans, user profiles such as home and office, and multiple connections for improved connectivity and reliability. To save costs, the radio frequency (RF) circuitry used by the UE is common to multiple SIMs. Therefore, multiple SIMs need to coordinate and share common RF resources to perform various activities and / or utilize various services. In practice, only one SIM and its associated protocol stack can be serviced. Meanwhile, all other SIMs and their associated protocol stacks can wait for RF resources to become available. One or more of the multiple SIMs can participate in paging, system information block (SIB) acquisition, measurements, data or voice calls, multimedia broadcast multicast service (MBMS), emergency calls, access stratum (AS) signaling, non-access stratum (NAS) signaling, and more.

[0030] MUSIM UEs previously operated without network control by creating arbitrary gaps until the 3rd Generation Partnership Project (3GPP) decided to introduce support for MUSIM device operation in Release 17. Starting from Release 17, the connected universal-SIM (USIM) in a MUSIM device can inform the connected mode network for multi-SIM operation when switching networks. In the context of this disclosure, USIM can refer to the radio protocol stack associated with the UE. There are two types of network switching supported by the network. In the first type, the connected USIM leaves the connected network and switches completely to the other USIM, that is, the other USIM becomes connected. In the other type, the connected USIM requests a gap from its network for MUSIM operation, such as listening for paging or performing measurements in an idle USIM.

[0031] Refer to 3GPP V17.3.0 of TS 38.331, TS 38.300, TS 37.340, and TS 38.423. In Release 17, MUSIM UEs use the radio resource control (RRC) UE assistance information (UAI) procedure to request a gap or notify a leave. The network (next-generation Node B (gNB)) uses the "otherConfig" field in the RRC message to configure whether the UE can provide assistance information for a MUSIM gap or MUSIM leave. The "Musim-GapAssistanceConfig" field in the "otherConfig" field informs the UE whether the UE can provide MUSIM assistance information for providing gap information. In Release 17, only per-UE gaps are supported for MUSIM operation.

[0032] Table 1 depicts an example of new radio (NR) RRC specification on how to use otherConfig including musim-GapAssistanceConfig.

[0033]

[0034] Table 1

[0035] Table 2 depicts an example of NR RRC specification regarding the definition of otherConfig including musim-GapAssistanceConfig.

[0036]

[0037] Table 2

[0038] In the NR specification (initial version of TS 38.331 specification), the musim-GapAssistanceConfig transmitted by the network (gNB) to the UE only contains the musim-GapProhibitTimer which is the prohibit timer for MUSIM assistance information reporting in the absence of leaving RRC_CONNECTED for MUSIM purposes.

[0039] As shown in the following example, taken from the 3GPP TS 38.331 specification, a configured MUSIM UE (connected USIM) requests gaps for MUSIM purposes by sending UE assistance information, as shown in Tables 3 and 4 below. The MUSIM UE (connected USIM) requests gaps for the operation of other USIMs in the same device. Other USIMs (i.e., other than the connected USIM) can use these gaps to perform measurements, read paging messages, read system information, etc.

[0040]

[0041] Table 3

[0042]

[0043] Table 4

[0044] The UE uses MUSIM assistance information for both periodic and aperiodic gaps. For periodic gaps, the assistance information includes the gap repetition period and the gap offset. For aperiodic gaps, also known as one-time gaps, the UE provides the starting system frame number (SFN) and subframe required for the gap.

[0045] Tables 5 and 6 depict excerpts including definitions and descriptions of MUSIM gap information requested by a connected UE from a connected network in UE assistance information.

[0046]

[0047]

[0048] Table 5

[0049]

[0050] Table 6

[0051] Once the network receives UE assistance information (UAI) indicating gap preference for MUSIM operation, the network may configure MUSIM gaps to the UE.

[0052] An example of an RRC specification indicating the UE behavior upon receiving an RRC reconfiguration (RRCReconfiguration) with a gap configuration is given in Table 7 below.

[0053]

[0054] Table 7

[0055] An example of an RRC specification including the definition of GapConfiguration is given in Table 8 below.

[0056]

[0057]

[0058] Table 8

[0059] In addition, the definitions of various fields according to the 3GPP standard specifications are given in Table 9 below.

[0060]

[0061] Table 9

[0062] The MUSIM gap configuration for the UE includes musim-Start-SFN-AndSubframe for aperiodic gaps and musim-GapRepetitionAndOffset for periodic gaps. In another example embodiment, the musim gap may be specified as shown in Table 10.

[0063]

[0064]

[0065] Table 10

[0066] The UE can use gaps configured based on the timing information configured by MUSIM-GapInfo. For example, a periodic gap can be created based on the starting-SFN and startingSubFrame, with a duration of musim-GapLength. In some scenarios, multiple MUSIM gaps can overlap in time.

[0067] Multi-radio dual connectivity (DC) is specified by 3GPP in specifications such as TS 37.340. NG-RAN supports multi-radio dual connectivity (MR-DC) operation, in which a UE in RRC_CONNECTED is configured to utilize radio resources provided by two different schedulers located in two different NG-RAN nodes connected via a non-ideal backhaul, one of the two different schedulers providing new radio (NR) access and the other providing evolved UMTS terrestrial radio access (E-UTRA) or NR access. One node can act as a master node (MN) and the other node can act as a secondary node (SN). The MN and SN are connected via a network interface, and at least the MN is connected to the core network. NG-RAN supports NG-RAN E-UTRA-NR dual connectivity (NGEN-DC), in which a UE is connected to an ng-eNB (an E-UTRA base station that can be connected to the 5G core) acting as a mobile node (MN) and a gNB (a 5G base station) acting as a network node (SN). NG-RAN also supports NR-E-UTRA Dual Connectivity (NE-DC), in which a UE is connected to a gNB acting as a mobile node (MN) and an ng-eNB acting as a network node (SN). The primary cell of a primary cell group or secondary cell group is called an SpCell. The SpCell of a primary cell group is called a PCell, while the SpCell of a secondary cell group is called a PSCell. In MR-DC, a group of serving cells associated with a primary node, including an SpCell (PCell) and optionally one or more SCells, is called an MCG or primary cell group. In MR-DC, a group of serving cells associated with a secondary node, including an SpCell (PSCell) and optionally one or more SCells, is called a secondary cell group (SCG). The frame timing and SFN between cells in the MCG and SCG may not be aligned.

[0068] In wireless communication technologies such as NR and long term evolution (LTE), a radio resource control (RRC_CONNECTED) user equipment (UE) performs various measurements for radio resource management (RRM) purposes, positioning, etc. For RRM, the UE measures reference signals such as the synchronization signal block (SSB) and channel state information-reference signal (CSI-RS) and reports them to the wireless network.

[0069] According to the latest version of the 3GPP 5G NR (New Radio) Phase 2 specification TS 38.300, the measurements to be performed by the UE for connected mode mobility are categorized into at least four measurement types:

[0070] Intra-frequency NR measurement,

[0071] Inter-frequency NR measurement,

[0072] Inter-RAT measurements for evolved universal terrestrial radioaccess (E-UTRA), and

[0073] Used for inter-RAT measurements for universal terrestrial radio access (UTRA).

[0074] For each measurement type, one or several measurement objects can be defined (a measurement object defines, for example, the carrier frequency to be monitored). For each measurement object, one or several reporting configurations can be defined (a reporting configuration defines, for example, the reporting criteria). Three reporting criteria are used: event-triggered reporting, periodic reporting, and event-triggered periodic reporting. The association between measurement objects and reporting configurations is established by a measurement identity (a measurement identity links a measurement object and a reporting configuration for the same radio access technology). The measurement identity is also used when reporting measurement results.

[0075] For positioning, the UE may report SSB / CSI-RS measurements and may also report measurements based on additional reference signals like positioning reference signal (PRS).

[0076] When an SSB is not fully contained within the active downlink (DL) bandwidth part (BWP), the UE can use measurement gaps when it needs to measure inter-NR or inter-RAT measurements or intra-frequency measurements outside the active DL BWP. Measurement gaps are configured by the network entity (e.g., the base station or gNB in ​​NR), and there may be no transmission or reception between the network and the UE during the gap period. The measurement gap configuration includes the gap offset, gap length, repetition period, and measurement gap timing advance (mgta). The gap offset specifies the subframe (and / or time slot) in which the measurement gap occurs. The gap length gives the duration of the gap, while the repetition period defines how often the measurement gap occurs.

[0077] In some scenarios, MUSIM gaps can overlap in time with other types of gaps, such as measurement gaps. A method is needed by which the UE decides which gap to use, or specifically whether to perform MUSIM operations or measurements, and which measurements or MUSIM operations to perform. Therefore, prioritization is required when making this decision.

[0078] Consider the case of a MUSIM UE with two USIMs (i.e., two UEs in the same MUSIM device), UE-A (USIM-A) is in RRC_CONNECTED state with network A. Dual connectivity (NR-NR DC) is configured at UE-A. UE-B (USIM-B) is in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED state with network B and requires MUSIM gaps for its operation.

[0079] In the prior art, there is no solution for MN-SN coordination (coordination between the primary and secondary nodes of Network A, i.e., MN-A and SN-A) regarding MUSIM gaps and the interaction with UE-A and MN-A / SN-A when Network A is NR-DC. There is also no solution for managing MUSIM gap prioritization and the interaction between the MN and SN for gap prioritization.

[0080] Therefore, it is desirable to address the above-mentioned shortcomings or other deficiencies, or at least provide a useful alternative for configuring MUSIM gaps (especially gap priority) for multi-SIM UEs under dual connectivity.

[0081] The following discussion in this patent document Figures 1 to 4The various embodiments used to describe the principles of the present disclosure are merely exemplary and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0082] To promote an understanding of the principles of the present disclosure, reference will now be made to the embodiments illustrated in the drawings, and specific language will be used to describe the embodiments. It will be understood, however, that this is not intended to limit the scope of the present disclosure, and that changes and further modifications in the illustrated systems and further applications of the principles of the present disclosure illustrated therein are considered to be within the ordinary skill of those skilled in the art to which the present disclosure relates.

[0083] Those skilled in the art will understand that both the foregoing general description and the following detailed description are intended to explain the present disclosure rather than to limit the present disclosure.

[0084] Throughout this specification, reference to "on one hand," "on the other hand," or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, appearances of the phrases "in an embodiment," "in one embodiment," "in another embodiment," and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0085] The terms "comprises," "includes," or any other variations thereof are intended to cover a non-exclusive inclusion such that a process or method that comprises a series of steps may include not only those steps but also other steps not expressly listed or inherent to the process or method. Similarly, the phrase "comprises" or "includes" preceding one or more devices, subsystems, elements, structures, or components does not, without more constraints, preclude the presence of other devices, subsystems, elements, structures, or components, or additional devices, subsystems, elements, structures, or components.

[0086] The embodiments of this invention and their various features and beneficial details are explained more fully with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following description. Descriptions of well-known components and processing technologies are omitted so as not to unnecessarily obscure the embodiments of this invention. In addition, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. Unless otherwise indicated, the term "or" used herein refers to a non-exclusive or. The examples used herein are merely to facilitate understanding of the manner in which the embodiments of this invention can be practiced, and further enable those skilled in the art to practice the embodiments of this invention. Therefore, these examples should not be interpreted as limiting the scope of the embodiments of this invention.

[0087] According to the tradition of this field, embodiments can be described and explained according to blocks that perform one or more functions described. These blocks, which may be referred to as units or modules herein, are physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and may optionally be driven by firmware and software. For example, the circuit may be embodied in one or more semiconductor chips, or on a substrate support such as a printed circuit board. The circuits that make up the blocks may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuits), or by a combination of dedicated hardware that performs some functions of the block and a processor that performs other functions of the block. Without departing from the scope of this disclosure, each block of the embodiment may be physically divided into two or more interactive and discrete blocks. Similarly, without departing from the scope of this disclosure, the blocks of the embodiment may be physically combined into more complex blocks.

[0088] The accompanying drawings are used to help easily understand various technical features, and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. Therefore, the present disclosure should be interpreted as extending to any changes, equivalents and substitutes other than those specifically set forth in the accompanying drawings. Although the terms first, second, etc. can be used to describe various elements in this article, these elements should not be limited by these terms. These terms are usually only used to distinguish one element from another element.

[0089] Reference is now made to the drawings, in which like reference numerals refer to corresponding features throughout.

[0090] Figure 1 An example of a communication environment 100 associated with a communication network is shown. The communication environment 100 depicts a configuration of a network entity 110 and a user equipment 120, according to one or more embodiments disclosed herein. Figure 1 The configuration disclosed in the foregoing may be understood as a part of the configuration of the network entity 110 and the user equipment 120. Hereinafter, it should be understood that terms including "unit" or "module" at the end may refer to a unit for processing at least one function or operation and may be implemented in hardware, software, or a combination of hardware and software.

[0091] refer to Figure 1The network entity 110 may include one or more processors 112 (also referred to as processor 112), a transceiver 114 (e.g., a communicator or communication interface), and a storage unit (e.g., memory 116). For example, the network entity 110 may be associated with one or more gNBs (gNBs). The network entity 110 may also be associated with a primary node and a secondary node. In an embodiment, the primary node and the secondary node may be two different gNBs from two different vendors communicating via a standardized interface. In an embodiment, the primary node and the secondary node may be different gNBs from the same vendor. The network entity may be associated with a radio access node in any technology, such as 4G LTE or 6G. In other words, gNB is used as an example of a radio access node in a wireless technology. Any other dual connectivity technology may be used in place of New Radio Dual Connectivity. Similarly, a MUSIM device may contain more than two USIMs.

[0092] The transceiver 114 may perform the functions of sending and receiving signals. The memory 116 may include a memory that, when executed by the processor, causes the system to perform the functions described above. Figures 2 to 3 Executable instructions for the steps described. For example, processor 112 may be a single processing unit or multiple units, each of which may include multiple computing units. Processor 112 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuits, and / or any device that manipulates signals based on operational instructions. Among other capabilities, processor 112 is configured to retrieve and execute computer-readable instructions and data stored in memory. Processor 112 may include one or more processors. In this case, one or more processors 112 may be general-purpose processors such as a central processing unit (CPU), an application processor (AP), and AI-specific processors such as a neural processing unit (NPU). Processor 112 may control the processing of input data based on predefined operational rules or artificial intelligence (AI) models stored in non-volatile memory and volatile memory (i.e., memory 116). The predefined operational rules or AI models are provided through training or learning.

[0093] The memory 116 may include any non-transitory computer-readable medium known in the art, including, for example, volatile memory such as static random-access memory (SRAM) and dynamic random-access memory (DRAM), and / or non-volatile memory such as read-only memory (ROM), erasable programmable ROM, flash memory, hard disk, optical disk, and magnetic tape.

[0094] In some embodiments, the network entity 110 may be implemented as a dedicated hardware unit. In some embodiments, the network entity 110 may be implemented in the form of a virtualized software unit in hardware or in a cloud environment.

[0095] In addition, user equipment 120 may also include one or more processors 122 (also referred to as processor 112), a transceiver 124 (e.g., a communicator or communication interface), and a storage unit (e.g., memory 126). Transceiver 124 may perform the functions of transmitting and receiving signals. The functions and features of processor 122, transceiver 124, and memory 126 may be similar to those of processor 112, transceiver 114, and memory 116, respectively. Therefore, for the sake of brevity of this disclosure, a detailed explanation thereof is omitted herein.

[0096] The terms "multi-SIM UE" and "UE" may be used interchangeably in this disclosure.

[0097] like Figure 1 As shown, user equipment 120 may be a multi-SIM UE having multiple SIMs 135a, 135b, ..., 135n. The multiple SIMs may include a first SIM and a second SIM among SIMs 135a to 135n, or a first USIM and a second USIM. In some embodiments, the first USIM is associated with a first communication network, and the second USIM is associated with a second communication network. Multi-SIM UE 120 may be configured for New Radio (NR) dual connectivity (DC) communication.

[0098] Figure 1Also depicted is a system 130 associated with network entity 110. System 130 is adapted to configure a multi-universal subscriber identity module (MUSIM) gap for a multi-subscriber identity module (SIM) user equipment (UE) in a communications network. System 130 may include a primary node 140 and a secondary node 150. In some embodiments, system 130 may communicate with network entity 110. In some embodiments, system 130 may correspond to and be integrated with network entity 110. In some embodiments, network entity 110 and system 130 (including primary node 140 and secondary node 150) are associated with a first network and a first USIM associated with a multi-SIM UE. In alternative embodiments, network entity 110 and system 130 (including primary node 140 and secondary node 150) are associated with a second network and a second USIM associated with a multi-SIM UE.

[0099] It should be understood that when the term "multi-SIM UE" is mentioned in the present disclosure, the term "multi-SIM UE" may be intended to refer to one of the first USIM or the second USIM in dual connectivity, and therefore, the primary node and the secondary node may refer to the primary node and the secondary node of the corresponding network (the first network in the case of the first USIM under DC, and the second network in the case of the second USIM under DC).

[0100] Initially, the multi-SIM UE 120 may be in an RRC connected state (eg, corresponding to one of the first and second USIMs), and dual connectivity may be configured for the SIM UE 120 .

[0101] The system 130, and in particular the master node 140, may be configured to send an RRC reconfiguration with a MUSIMGapAssistanceConfig configuration message to the multi-SIM UE 120. The master node 140 may receive an RRC reconfiguration complete indication from the multi-SIM UE 120. In an embodiment, the master node 140 may send a configuration (otherConfig) to the multi-SIM UE 120 for sending a MUSIM gap request.

[0102] The system 130 may be configured to receive a gap configuration request at a master node 140 associated with the network entity 110. The gap configuration request may be received at the master node 140 from the multi-SIM UE 120. The gap configuration request received at the master node 140 may be a UE Assistance Information (UAI) Radio Resource Control (RRC) message.

[0103] Upon receiving the UAI RRC message, the master node 140 may generate a configuration for the multi-SIM UE 120 with one or more MUSIM gaps based on the received gap configuration request. In an embodiment, the master node 140 determines and allocates the MUSIM gaps based on the received request and / or the impact of the MUSIM gaps on the performance and measurements of both the master node 140 and the secondary node 150.

[0104] In an embodiment, master node 140 may be configured to transmit a MUSIM gap to UE 120. The MUSIM gap transmitted to UE 120 may include a gap priority and a MUSIM gap configuration (i.e., starting SFN (system frame number), starting subframe, offset, gap repetition period, and gap length). In an embodiment, master node 140 may indicate details of a reference cell that may be used as a timing reference, i.e., whether the gap's SFN / subframe / offset is based on at least one of the primary node's PCell (i.e., SpCell), the secondary node's PCell (i.e., PScell), and any secondary cells of the primary or secondary nodes. In an embodiment, the MUSIM gap (SFN / subframe / offset) is based on the PSCell of UE 120 in dual connectivity.

[0105] In an embodiment, the master node 140 may send otherConfig and the gap configuration via signaling radio bearer 1 (SRB1) configured by the master node 140. In an embodiment, the UE 120 may send the gap configuration request via SRB1 configured by the master node 140.

[0106] In an embodiment, the UE 120 may request a MUSIM gap from the secondary node 150 through an RRC message (eg, UE Assistance Information (UAI)), and the secondary node 150 sends a configuration (otherConfig) for sending a gap configuration request.

[0107] In addition, the primary node 140 may send a message to the secondary node 150 indicating the MUSIM gaps configured for the multi-SIM UE 120. The message may include information regarding the gap priority of the MUSIM gap relative to one or more other gaps. The message sent by the primary node 140 to the secondary node 150 may be a CG-ConfigInfo InterNode RRC message. In an embodiment, the configuration of the gap priority and a "keep solution indication" may be conveyed from the primary node 140 to the secondary node 150 in the CG-ConfigInfo InterNode RRC message. In an embodiment, the gap priority may apply to periodic measurement gaps and may not be provided for aperiodic measurement gaps. In an embodiment, aperiodic measurement gaps may always be prioritized.

[0108] In one embodiment, the gap priority of a MUSIM gap indicates the priority of each MUSIM gap relative to other MUSIM gaps. That is, each MUSIM gap may have a corresponding priority that is different from other MUSIM gaps. For example, MUSIM gap A may have a higher priority than MUSIM gap B.

[0109] In another embodiment, each of the MUSIM slots may be of the same slot priority.

[0110] Furthermore, the gap priority of a MUSIM gap indicates the priority of each MUSIM gap relative to one or more other gaps. The one or more other gaps may be measurement gaps. The gap priority of a MUSIM gap may define whether the MUSIM gap can be used in overlapping scenarios. Overlapping scenarios may refer to overlap between MUSIM gaps, as well as overlap between one or more MUSIM gaps and one or more other gaps. In the case of full or partial overlap between MUSIM gaps, or between one or more MUSIM gaps and one or more other gaps (measurement gaps), the gap priority may indicate whether the MUSIM gap or the measurement gap may be used, and which MUSIM gap may be used based on the corresponding gap priority. For example, if there are two gaps configured by master node 140, namely, a MUSIM gap with priority M and a measurement gap with priority N, and these gaps fully or partially overlap, UE 120 uses the gap with the higher priority. For example, if there are three gaps configured by master node 140, namely, a MUSIM gap with priority M, another MUSIM gap with priority N, and a measurement gap with priority X, and these gaps fully or partially overlap, UE 120 uses the gap with the higher priority.

[0111] In some embodiments, the gap priority of a MUSIM gap also defines whether the multi-SIM UE 120 can prioritize all MUSIM gaps.

[0112] In an embodiment, when adding a MUSIM gap to the UE 120, the master node 140 notifies the secondary node 150 of the MUSIM gap. In an embodiment, when modifying the MUSIM gap for the UE 120, the master node 140 notifies the secondary node 150 of the MUSIM gap. In an embodiment, when releasing the MUSIM gap for the UE 120, the master node 140 notifies the secondary node 150 of the MUSIM gap.

[0113] refer to Figure 3 , which shows a flowchart 300 depicting the operation / behavior of a secondary node with gap priority according to one or more embodiments of the present disclosure. In step 302, the secondary node 150 receives the MUSIM gap priority from the primary node 140. In an embodiment, the secondary node 150 uses the MUSIM gap priority to identify a measurement requirement for any of the measurements configured by itself. In step 304, the secondary node 150 identifies whether the measurement gap can be used for MUSIM operation and not for the measurements configured by itself. In step 306, upon identifying that the measurement gap can be used for MUSIM operation and not for the measurements configured by itself, the secondary node 150 can take mitigation actions. In a non-limiting example, the mitigation actions can include one or more actions as depicted in steps 306a to 306e.

[0114] In one action, depicted in step 306a, if the secondary node 150 identifies that the measurement gap can be used for a MUSIM gap and is not used for one of the required measurement gaps in its neighboring frequencies, the secondary node may configure a different neighboring frequency for measurement. In another action, depicted in step 306b, if the secondary node 150 identifies that the measurement gap can be used for a MUSIM gap and is not used for one of the required measurement gaps in its neighboring frequencies, the secondary node may configure different reference signals for the neighboring frequencies to avoid overlap. In yet another action, depicted in step 306c, if the secondary node 150 identifies that the measurement gap can be used for a MUSIM gap and is not used for one of the required measurement gaps in its neighboring frequencies, the secondary node may configure different measurement characteristics, such as a different repetition period or a different gap length. In yet another action, depicted in step 306d, the secondary node 150 may signal the primary node 140 to assign different gap priorities. In another action depicted in step 306e, the secondary node 150 identifies that the measurement gap may be used for a MUSIM gap and not for a required measurement gap in one of its neighboring frequencies. The secondary node uses the information for optimization of its mobility operations, such as to identify the cause of the radio link failure or late handover.

[0115] The secondary node 150 also uses other information related to the MUSIM gap to perform scheduling. During the MUSIM gap, the secondary node 150 may not send any data in the downlink. During the MUSIM gap, the SN may also not allocate any resources to the UE for its transmission.

[0116] In an embodiment, the information for MUSIM gap configuration sent from the primary node 140 to the secondary node 150 includes NRRRC IE MUSIM-GapConfig-r17, as given in Table 11 below.

[0117]

[0118]

[0119]

[0120] Table 11

[0121] Furthermore, the secondary node 150 may be configured to apply the message received from the primary node 140. As described above, the received message indicates a MUSIM gap and a gap priority. The secondary node 150 is configured to create gaps in the uplink / downlink schedule and configure measurements. The secondary node 150 may consider the gap priority. If the gap priority indicates that the MUSIM gap can be prioritized (i.e., the MUSIM gap has a higher priority than one or more other gaps), the secondary node 150 may reallocate one or more other gaps (measurement gaps) to different time periods.

[0122] In an embodiment, the secondary node 150 notifies the primary node 140 whether the secondary node 150 supports (configuration of) a MUSIM gap. The primary node 140 configures the UE 120 to request a MUSIM gap and configures the MUSIM gap based on the information that the secondary node 150 supports the MUSIM gap. If the secondary node 150 does not support (configuration of) the MUSIM gap, the primary node 140 refrains from configuring the MUSIM gap for the UE 120.

[0123] In some embodiments, the message sent by master node 140 to secondary node 150 may also indicate a reference cell that can be used as a timing reference, namely, whether the gap is based on at least one of the PCell (i.e., SpCell) of master node 140, the pCell (i.e., PScell) of secondary node 150, and any secondary cells of master node 140 or secondary node 150. Secondary node 150 creates a MUSIM gap based on the information from master node 140. Secondary node 150 creates the gap at the time indicated by master node 140 (starting SFN + starting subframe + offset), with the gap length and gap repetition indicated by master node 140. In some embodiments, secondary node 150 creates the gap using the reference cell indicated by master node 140 as the timing reference. In some embodiments, the CG-ConfigInfo inter-node RRC message may include the MUSIM gap configuration with the reference cell and gap priority in a new information element (IE) or MeasConfigMN.

[0124] In an embodiment, the secondary node 150 creates a MUSIM gap by using a PCell (SpCell or PCell of a master cell group (MCG)) configured by the master node 140 .

[0125] In an embodiment, the secondary node 150 does not transmit any downlink physical downlink control channel (PDCCH) or physical downlink shared channel (PDSCH) in the created MUSIM gap. In an embodiment, the secondary node 150 does not transmit any downlink reference signal in the created MUSIM gap. In an embodiment, the secondary node 150 does not receive the physical random access channel (PRACH), physical uplink control channel (PUCCH), or physical uplink shared channel (PUSCH) in the created MUSIM gap.

[0126] Table 12 depicts an example in which CG-ConfigInfo-v1700 is included in CG-ConfigInfo by using a new information element in R17 NR RRC specification.

[0127]

[0128]

[0129] Table 12

[0130] As described above, the master node 140 sends the MUSIM gap configuration in the CG-ConfigInfo inter-node RRC message within the MeasConfigMN. An example structure is given in Table 13 below.

[0131]

[0132] Table 13

[0133] In an embodiment, the IE MUSIM-GapConfig specifies the MUSIM gap configuration and controls the establishment / release of the MUSIM gap. An example structure is given in Table 14 below.

[0134]

[0135]

[0136] Table 14

[0137] In an embodiment, the master node 140 releases the configured MUSIM gap when configuring one or more other gaps such as a measurement gap. In an embodiment, the master node 140 may configure the gap to the UE 120 and the master node 140.

[0138] In an embodiment, master node 140 may configure measurement gaps for UE 120, and master node 140 releases the configured measurement gaps when configuring MUSIM gaps. In an embodiment, master node 140 may configure measurement gaps for UE 120, and master node 140 releases the secondary cell group (SCG) when configuring MUSIM gaps. In an embodiment, master node 140 may configure measurement gaps for UE 120, and master node 140 deactivates the SCG when configuring MUSIM gaps. In an embodiment, master node 140 releases dual connectivity when configuring measurement gaps.

[0139] In an embodiment, the master node 140 configures only one of the MUSIM gap and the measurement gap to the UE-A configured with dual connectivity.

[0140] In an embodiment, the one or more other gaps may include measurement gaps, FR2 gaps, and positioning measurement gaps. In an embodiment, the master node 140 configures only any two of the MUSIM gaps, measurement gaps, FR2 gaps, and positioning measurement gaps, or dual connectivity for the UE 120, and releases one of the configured gaps when configuring the third one.

[0141] As described above, the multi-SIM UE 120 may include a first USIM and a second USIM. Given that the first USIM is configured for dual connectivity, the first USIM may be configured with a MUSIM gap by the first network regarding PSCell addition. The first USIM may avoid performing second USIM operations, such as at least one of paging reception, system information block (SIB) reception, cell search, and cell reselection measurements, during the configured measurement gap when performing PSCell addition, and may utilize shared hardware, RF, and software resources for operations within the first USIM.

[0142] In an embodiment, upon receiving an RRC reconfiguration message for PSCell addition, or when performing conditional PSCell addition, the first USIM avoids performing second USIM operations such as at least one of paging reception, SIB reception, cell search, cell reselection measurement during the configured measurement gap, and uses shared hardware, RF and software resources for operations in UE-A until random access in the SN PSCell is completed during PSCell addition.

[0143] In an embodiment, with respect to the first USIM behavior for PSCell change, the first USIM avoids performing UE-B operations such as at least one of paging reception, SIB reception, cell search, cell reselection measurement during the configured measurement gap when performing the PSCell change, and uses shared hardware, RF, and software resources for operations in the first USIM.

[0144] In an embodiment, upon receiving an RRC reconfiguration message for a PSCell change, or when performing a conditional PSCell change, the first USIM avoids performing second USIM operations such as at least one of paging reception, SIB reception, cell search, and cell reselection measurements during the configured measurement gap, and uses shared hardware, RF, and software resources for operations in the first USIM until random access in the target SN PSCell during the PSCell change is completed.

[0145] refer to Figure 2 , which shows a timing diagram depicting communication between a multi-SIM UE (e.g., a first USIM configured for dual connectivity) in a communication network, a primary node (related to a first network associated with the first USIM), and a secondary node for configuring MUSIM gap for the multi-SIM UE.

[0146] At step 202 , the multi-SIM UE 120 may be in an RRC connected state, and dual connectivity may be configured for the multi-SIM UE 120 .

[0147] At step 204 , the master node 140 may send an RRC reconfiguration with a MUSIMGapAssistanceConfig configuration message to the Multi-SIM UE 120 .

[0148] At step 206 , the master node 140 may receive an RRC reconfiguration complete indication from the multi-SIM UE 120 .

[0149] At step 208, the multi-SIM UE 120 sends a gap configuration request, such as a UE Assistance Information (UAI) Radio Resource Control (RRC) message, to the master node 140. Upon receiving the UAI RRC message, the master node 140 may configure one or more MUSIM gaps to the multi-SIM UE 120 based on the received gap configuration request.

[0150] At step 210, the primary node 140 may send a message to the secondary node 150 indicating the MUSIM gap configured for the multi-SIM UE 120. The message may include information related to the gap priority of the MUSIM gap relative to one or more other gaps. The message sent by the primary node 140 to the secondary node 150 may be a CG-ConfigInfo inter-node RRC message.

[0151] At step 212, the secondary node 150 applies the message indicating the MUSIM gap and gap priority received from the primary node 140. The secondary node 150 is configured to create gaps in the uplink / downlink schedule and to configure measurements. The secondary node 150 may consider the gap priority in its operations.

[0152] At step 214 , the master node 140 may send an RRC reconfiguration with MUSIM gap configuration message to the multi-SIM UE 120 .

[0153] At step 216 , the multi-SIM UE 120 may send an RRC reconfiguration complete indication to the master node 140 .

[0154] and Figure 2 The detailed description of each step is covered in Figure 1 The relevant description is omitted here for the sake of brevity.

[0155] Figure 3 A method flow diagram depicting a method 400 for configuring MUSIM gap for a multi-SIM UE in a communication network according to an example embodiment of the present disclosure is shown. The multi-SIM UE is configured for New Radio (NR) dual connectivity (DC) communication. The multi-SIM UE includes a first USIM associated with a first communication network and a second USIM associated with a second communication network. A network entity, a primary node, and a secondary node are associated with the first USIM and the first network of the multi-SIM UE.

[0156] At step 402 , the method 400 includes receiving a gap configuration request from the multi-SIM UE 120 at a master node 140 associated with a network entity.

[0157] At step 404, the method 400 includes generating, by the master node 140, a configuration for the multi-SIM UE with a MUSIM gap based on the received gap configuration request. The gap configuration request is a UE assistance information (UAI) radio resource control (RRC) message.

[0158] At step 406, the method 400 includes sending, by the primary node 140, a message indicating a MUSIM gap configured for a multi-SIM UE to a secondary node 150 associated with the network entity, wherein the message includes information related to a gap priority of the MUSIM gap. The message sent by the primary node to the secondary node is a CG-ConfigInfo inter-node RRC message.

[0159] The gap priority of the MUSIM gap indicates the priority of the MUSIM gap relative to the one or more other gaps if the MUSIM gap overlaps with the one or more other gaps, including the measurement gap.

[0160] The gap priority of a MUSIM gap indicates whether a multi-SIM UE can prioritize all MUSIM gaps.

[0161] The method 400 may also include utilizing, by the secondary node, the received message indicating the MUSIM gap and the gap priority to create one or more MUSIM gaps and one or more other gaps in the uplink / downlink scheduling and for configuring measurements.

[0162] Although shown and described in a specific order Figure 3 However, according to various embodiments, these steps may appear in variations of this order. Figure 3 The detailed description of each step is covered in Figures 1 to 2 The relevant description is omitted here for the sake of brevity.

[0163] This disclosure describes the communication of gap priorities and other gap-related parameters for MUSIM gaps and other gaps. This allows the secondary node to identify whether it can perform the measurements configured by itself, and if not, the secondary node can ensure that mobility performance is not affected. The secondary node can also use this information for self-optimization purposes. If a radio link failure occurs due to a late handover (a handover triggered after mobility has weakened at the source cell), one reason may be that there is insufficient time to perform measurements because the gap is being used for MUSIM operations. The gap priority and other information help identify and mitigate this problem. In addition, the other information also helps the SN decide whether to schedule the UE.

[0164] The various actions, behaviors, blocks, steps, etc. in the sequential flow charts can be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, behaviors, blocks, steps, etc. can be omitted, added, modified, skipped, etc. without departing from the scope of the present disclosure.

[0165] Unless defined otherwise, 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 belongs. The systems, methods, and examples provided herein are illustrative only and not limiting.

[0166] Although specific language has been used to describe this topic, it is not intended to create any limitation thereto. It is clear to those skilled in the art that various feasible modifications can be made to the method to realize the inventive concept taught herein. The accompanying drawings and the foregoing description provide examples of embodiments. It will be understood by those skilled in the art that one or more of the described elements can be well combined into a single functional element. Alternatively, some elements can be divided into multiple functional elements. Elements in one embodiment can be added to another embodiment.

[0167] The embodiments disclosed herein may be implemented using at least one hardware device and performing network management functions to control elements.

[0168] The foregoing description of specific embodiments sufficiently reveals the general nature of the embodiments herein so that others can, by applying current knowledge, readily modify and / or adapt such specific embodiments for various applications without departing from the general concepts, and therefore, such adaptations and modifications should and are intended to be understood to be within the meaning and range of equivalents of the disclosed embodiments. It should be understood that the phraseology or terminology used herein is for descriptive purposes only and not for limiting purposes. Therefore, although the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein may be practiced with modifications within the scope of the embodiments described herein.

[0169] The embodiments disclosed herein may be implemented by at least one software program running on at least one hardware device and performing network management functions to control elements. These elements may be at least one of a hardware device and a combination of a hardware device and a software module.

[0170] Although specific language has been used to describe the present disclosure, no limitation is intended thereby. It will be apparent to those skilled in the art that various possible modifications can be made to the methods to implement the inventive concepts taught herein.

[0171] The accompanying drawings and the foregoing description provide examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may be combined into a single functional element. Alternatively, certain elements may be separated into multiple functional elements. Elements in one embodiment may be added to another embodiment. For example, the order of the processes described herein may be changed and are not limited to the methods described herein.

[0172] Furthermore, the actions in any flowchart do not need to be performed in the order shown; nor do all actions necessarily need to be performed. Furthermore, actions that are not dependent on other actions can be performed in parallel with those other actions. The scope of the embodiments is in no way limited by these specific examples. Numerous variations (such as differences in structure, dimensions, and use of materials) are possible, whether or not expressly provided in the specification. The scope of the embodiments is at least as broad as that given by the appended claims.

[0173] The benefits, other advantages, and solutions to problems have been described above with respect to specific embodiments. However, the benefits, advantages, solutions to problems, and any components that may make any benefit, advantage, or solution appear or become more significant should not be construed as key, required, or essential features or components of any or all claims.

[0174] Although the present disclosure has been described with various embodiments, various changes and modifications may occur to those skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method performed by a user equipment (UE) in a communication system, the method comprising: Sending a request message for at least one Multi-Universal Subscriber Identity Module (MUSIM) gap to the first base station; receiving a radio resource control (RRC) message from the first base station including a configuration of the at least one MUSIM gap, the configuration including information associated with a MUSIM gap priority; as well as performing a MUSIM gap configuration process based on the MUSIM gap priority, The information associated with the MUSIM gap priority is sent from the first base station to the second base station.

2. The method according to claim 1, in, In case that the at least one MUSIM gap collides with another gap, at least one of paging reception, system information block (SIB) reception, cell identification, and measurement is not performed.

3. The method according to claim 2, in, The another gap is at least one of a measurement gap and a MUSIM gap other than the at least one MUSIM gap.

4. The method according to claim 1, in, The configuration of the at least one MUSIM gap further includes at least one of a starting system frame number SFN, a starting subframe, an offset, a gap repetition period, and a gap length.

5. A method performed by a first base station in a communication system, the method comprising: receiving a request message for at least one Multiple Universal Subscriber Identity Module (MUSIM) gap from a user equipment (UE); as well as sending a radio resource control (RRC) message to the UE including a configuration of at least one MUSIM gap, the configuration including information associated with a MUSIM gap priority, wherein a MUSIM gap configuration process based on the MUSIM gap priority is performed, and Information associated with the MUSIM gap priority is sent to the second base station.

6. The method according to claim 5, in, In case that the at least one MUSIM gap collides with another gap, at least one of paging reception, system information block (SIB) reception, cell identification, and measurement is not performed.

7. The method according to claim 6, in, The another gap is at least one of a measurement gap and a MUSIM gap other than the at least one MUSIM gap.

8. The method according to claim 5, in, The configuration of the at least one MUSIM gap further includes at least one of a starting system frame number SFN, a starting subframe, an offset, a gap repetition period, and a gap length.

9. A user equipment (UE) in a communication system, the UE comprising: transceiver, and a controller coupled to the transceiver, the controller being configured to: Sending a request message for at least one Multi-Universal Subscriber Identity Module (MUSIM) gap to the first base station; receiving a radio resource control (RRC) message from a first base station including a configuration of at least one MUSIM gap, the configuration including information associated with a MUSIM gap priority; as well as performing a MUSIM gap configuration process based on the MUSIM gap priority, The information associated with the MUSIM gap priority is sent from the first base station to the second base station.

10. The UE according to claim 9, in, In case that the at least one MUSIM gap collides with another gap, at least one of paging reception, system information block (SIB) reception, cell identification, and measurement is not performed.

11. The UE according to claim 10, in, The another gap is at least one of a measurement gap and a MUSIM gap other than the at least one MUSIM gap.

12. The UE according to claim 9, in, The configuration of the at least one MUSIM gap further includes at least one of a starting system frame number SFN, a starting subframe, an offset, a gap repetition period, and a gap length.

13. A first base station in a communication system, the first base station comprising: transceiver, and a controller coupled to the transceiver, the controller being configured to: receiving a request message for at least one Multiple Universal Subscriber Identity Module (MUSIM) gap from a user equipment (UE); as well as sending a radio resource control (RRC) message to the UE including a configuration of at least one MUSIM gap, the configuration including information associated with a MUSIM gap priority, wherein a MUSIM gap configuration process based on the MUSIM gap priority is performed, and The information associated with the MUSIM gap priority is sent to the second base station.

14. The first base station according to claim 13, in, In case the at least one MUSIM gap collides with another gap, at least one of paging reception, system information block (SIB) reception, cell identification, and measurement is not performed, and The another gap is at least one of a measurement gap and a MUSIM gap other than the at least one MUSIM gap.

15. The first base station according to claim 13, in, The configuration of the at least one MUSIM gap further includes at least one of a starting system frame number SFN, a starting subframe, an offset, a gap repetition period, and a gap length.

Images