Patent Application
20250105958
This application is based on and claims priority under 35 U.S.C. § 119 (a) of a Korean patent application number 10-2023-0130527, filed on Sep. 27, 2023, in the Korean Intellectual Property Office, and of a Korean patent application number 10-2024-0026452, filed on Feb. 23, 2024, in the Korean Intellectual Property Office, the disclosure of each of which is incorporated by reference herein in its entirety.
The disclosure relates to an operation of a terminal and a base station in a mobile communication system. More particularly, the disclosure relates to a method and device in which multi-subscriber identification module (SIM) terminals manage colliding gaps.
5th generation (5G) mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6 GHz” bands, such as 3.5 GHZ, but also in “Above 6 GHz” bands referred to as millimeter wave (mmWave) including 28 GHz and 39 GHz. In addition, it has been considered to implement 6th generation (6G) mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95 GHz to 3 THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.
At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced mobile broadband (eMBB), ultra reliable low latency communications (URLLC), and massive machine-type communications (mMTC), there has been ongoing standardization regarding beamforming and massive multiple-input multiple-output (MIMO) for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of bandwidth part (BWP), new channel coding methods, such as a low density parity check (LDPC) code for large amount of data transmission and a polar code for highly reliable transmission of control information, layer 2 (L2) pre-processing, and network slicing for providing a dedicated network specialized to a specific service.
Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical (PHY) layer standardization regarding technologies, such as vehicle-to-everything (V2X) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, new radio unlicensed (NR-U) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, new radio (NR) user equipment (UE) power saving, non-terrestrial network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.
Moreover, there has been ongoing standardization in air interface architecture/protocol regarding technologies, such as industrial Internet of things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (integrated access and backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and dual active protocol Stack (DAPS) handover, and two-step random access for simplifying random access procedures (2-step random access channel (RACH) for NR). There also has been ongoing standardization in system architecture/service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining network functions virtualization (NFV) and software-defined networking (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE positions.
As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with extended reality (XR) for efficiently supporting augmented reality (AR), virtual reality (VR), mixed reality (MR) and the like, 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.
Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies, such as full dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using orbital angular momentum (OAM), and reconfigurable intelligent surface (RIS), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and artificial intelligence (AI) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
The above information is presented as background information only to assist with an understanding of the disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the disclosure.
Aspects of the disclosure are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a method and device in which multi-SIM terminals manage colliding gaps in a next generation wireless communication system based on the above discussion.
Additional aspects will be set forth in part in the description which follows and, in part, will be apparent from the description, or may be learned by practice of the presented embodiments.
In accordance with an aspect of the disclosure, a method performed by a user equipment (UE) in a wireless communication system is provided. The method includes receiving, from a base station, a radio resource control (RRC) message for configuring the UE to provide a preference for a multi-universal subscriber identity module (MUSIM) gap and a MUSIM gap priority, identifying whether to initiate a transmission of a UE assistance information message for providing first preference information on the MUSIM gap priority or second preference information indicating to keep all colliding MUSIM gaps based on a timer T346h, and in case that the timer T346h is not running, initiating the transmission of the UE assistance information message for providing the first preference information or the second preference information.
In accordance with another aspect of the disclosure, a method performed by a base station in a wireless communication system is provided. The method includes transmitting, to a user equipment (UE), a radio resource control (RRC) message for configuring the UE to provide a preference for a multi-universal subscriber identity module (MUSIM) gap and a MUSIM gap priority, receiving, from the UE, a UE assistance information message including at least one first preference information on the MUSIM gap priority or second preference information indicating to keep all colliding MUSIM gaps, wherein the UE assistance information message including the at least one first preference information or second preference information is received in case that a timer T346h is not running.
In accordance with another aspect of the disclosure, a user equipment (UE) in a wireless communication system is provided. The UE includes a transceiver, and a controller coupled with the transceiver and configured to receive, from a base station, a radio resource control (RRC) message for configuring the UE to provide a preference for a multi-universal subscriber identity module (MUSIM) gap and a MUSIM gap priority, identify whether to initiate a transmission of a UE assistance information message for providing first preference information on the MUSIM gap priority or second preference information indicating to keep all colliding MUSIM gaps based on a timer T346h, and, in case that the timer T346h is not running, initiate the transmission of the UE assistance information message for providing the first preference information or the second preference information.
In accordance with another aspect of the disclosure, a base station in a wireless communication system is provided. The base station includes a transceiver, and a controller coupling with the transceiver and configured to transmit, to a user equipment (UE), a radio resource control (RRC) message for configuring the UE to provide a preference for a multi-universal subscriber identity module (MUSIM) gap and a MUSIM gap priority, and receive, from the UE, a UE assistance information message including at least one first preference information on the MUSIM gap priority or second preference information indicating to keep all colliding MUSIM gaps, wherein the UE assistance information message including the at least one first preference information or second preference information is received in case that a timer T346h is not running.
According to an embodiment of the disclosure, it is possible to provide a method and device in which a multi-SIM terminal manages colliding gaps.
Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.
The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:
Throughout the drawings, like reference numerals will be understood to refer to like parts, components, and structures.
The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and construction may be omitted for clarity and conciseness.
The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.
It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.
Hereinafter, a term identifying an access node used in the description, a term indicating network entities, a term indicating messages, a term indicating an interface between network objects, a term indicating various identification information and the like are exemplified for convenience of description. Accordingly, the disclosure is not limited to the terms described below, and other terms indicating an object having an equivalent technical meaning may be used.
Hereinafter, a base station is a subject performing resource allocation of a terminal, and may be at least one of a gNode B (gNB), an eNode B (eNB), a node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In an embodiment of the disclosure, a downlink (DL) is a wireless transmission path of a signal transmitted from a base station to a UE, and an uplink (UL) is a wireless transmission path of a signal transmitted from a UE to a base station. Hereinafter, although an LTE or long-term evolution advanced (LTE-A) system may be described as an example, embodiments of the disclosure may be applied to other communication systems having a similar technical background or channel type. For example, 5G mobile communication technology (5G, new radio (NR)) developed after LTE-A may be included in a system to which an embodiment of the disclosure may be applied, and the following 5G may be a concept including existing LTE, LTE-A and other similar services. Further, the disclosure may be applied to other communication systems through some modifications within a range that does not significantly deviate from the scope of the disclosure by the determination of a person having skilled technical knowledge. In this case, it will be understood that each block of signal flow diagrams and combinations of the signal flow diagrams may be performed by computer program instructions.
Because these computer program instructions may be mounted in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, the instructions performed by a processor of a computer or other programmable data processing equipment generate a means that performs functions described in the signal flow diagram block(s). Because these computer program instructions may be stored in a computer usable or computer readable memory that may direct a computer or other programmable data processing equipment in order to implement a function in a particular manner, the instructions stored in the computer usable or computer readable memory may produce a production article containing instruction means for performing the function described in the signal flow diagram block(s). Because the computer program instructions may be mounted on a computer or other programmable data processing equipment, a series of operation steps are performed on the computer or other programmable data processing equipment to generate a computer-executed process; thus, instructions for performing the computer or other programmable data processing equipment may provide steps for performing functions described in the signal flow diagram block(s).
Further, each block may represent a portion of a module, a segment, or a code including one or more executable instructions for executing specified logical function(s). Further, it should be noted that in some alternative implementations, functions recited in the blocks may occur out of order. For example, two blocks illustrated one after another may in fact be performed substantially simultaneously, or the blocks may be sometimes performed in the reverse order according to the corresponding function. In this case, the term ‘-unit’ used in this embodiment means software or hardware components, such as field programmable gate array (FPGA) or application specific integrated circuit (ASIC), and ‘-unit’ may perform certain roles. However, ‘-unit’ is not limited to software or hardware. ‘-unit’ may be constituted to reside in an addressable storage medium or may be constituted to reproduce one or more processors. Therefore, as an example, ‘-unit’ includes components, such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuit, data, databases, data structures, tables, arrays, and variables. Functions provided in the components and ‘-units’ may be combined into a smaller number of components and ‘-units’ or may be further separated into additional components and ‘-units’. Further, components and ‘-units’ may be implemented to reproduce one or more central processing units (CPUs) in a device or secure multimedia card. Further, in an embodiment or the disclosure, the ‘˜ unit’ may include one or more processors.
Hereinafter, for convenience of description, the disclosure uses terms and names defined in the 3rd generation partnership project (3GPP) standards. However, the disclosure is not limited by the above terms and names, and may be equally applied to systems conforming to other standards. In an embodiment of the disclosure, an evolved node B (eNB) may be used interchangeably with a gNB for convenience of description. For example, a base station described as an eNB may represent a gNB.
It should be appreciated that the blocks in each flowchart and combinations of the flowcharts may be performed by one or more computer programs which include computer-executable instructions. The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.
Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphical processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a wireless-fidelity (Wi-Fi) chip, a Bluetooth™ chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display drive integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like.
Referring to
Referring to
Referring to
The PDCPs 1b-05 and 1b-40 are responsible for operations, such as IP header compression/restoration. Main functions of the PDCP may be summarized as follows.
The RLCs 1b-10 and 1b-35 may reconstitute the PDCP packet data unit (PDU) into an appropriate size and perform an automatic repeat request (ARQ) operation. Main functions of the RLC may be summarized as follows.
The MACs 1b-15 and 1b-30 may be connected to several RLC layer devices constituted in one UE, and perform operations of multiplexing RLC PDUs to MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. Main functions of the MAC may be summarized as follows.
Physical layers 1b-20 and 1b-25 may perform operations of channel-coding and modulating higher layer data, making the higher layer data into OFDM symbols and transmitting the OFDM symbols through a radio channel, or demodulating OFDM symbols received through a radio channel, channel-decoding the OFDM symbols, and delivering the OFDM symbols to a higher layer.
Referring to
Referring to
Referring to
Main functions of the NR SDAPs 1d-01 and 1d-45 may include some of the following functions.
For the SDAP layer device, the UE may receive a configuration on whether to use a header of the SDAP layer device or whether to use a function of the SDAP layer device for each PDCP layer device, each bearer, or each logical channel with a radio resource control (RRC) message, and in the case that the SDAP header is configured, the UE may instruct to update or reconfigure mapping information on uplink and downlink QoS flows and data bearers with non-access stratum (NAS) reflective quality of service (QOS) and access stratum (AS) reflective QOS of the SDAP header. The SDAP header may include QOS flow ID information indicating a QoS. QoS information may be used as a data processing priority and scheduling information for supporting a smooth service.
Main functions of the NR PDCPs 1d-05 and 1d-40 may include some of the following functions.
Header compression and decompression: ROHC only
In the above description, reordering of the NR PDCP device may refer to a function of reordering PDCP PDUs received from a lower layer based on a PDCP sequence number (SN), and include a function of delivering data to a higher layer in the rearranged order, a function of directly delivering data without considering the order, a function of rearranging the order and recording lost PDCP PDUs, a function of reporting a status of lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of lost PDCP PDUs.
Main functions of the NR RLCs 1d-10 and 1d-35 may include some of the following functions.
In the above description, in-sequence delivery of the NR RLC device may mean a function of sequentially delivering RLC SDUs received from a lower layer to a higher layer, and include a function of reassembling and delivering several RLC SDUs in the case that an original RLC SDU is divided into several RLC SDUs and received, a function of rearranging received RLC PDUs based on an RLC sequence number (SN) or a PDCP sequence number (SN), a function of rearranging the order and recording lost RLC PDUs, a function of reporting a status of lost RLC PDUs to the transmitting side, a function of requesting retransmission of lost RLC PDUs, and a function of sequentially delivering only RLC SDUs before the lost RLC SDU to a higher layer in the case that there is a lost RLC SDU, or a function of sequentially delivering all RLC SDUs received before the timer starts to the higher layer, when a predetermined timer has expired even if there is a lost RLC SDU, or a function of sequentially delivering all RLC SDUs received so far to the higher layer, when a predetermined timer has expired even if there is a lost RLC SDU. Further, in the above description, the RLC PDUs may be processed in the order of reception (regardless of order of serial numbers and sequence numbers, in order of arrival) and transferred to the PDCP device regardless of order (out-of sequence delivery), and in the case of a segment, the NR RLC device may receive segments stored in a buffer or to be received later, reconstitute segments into one complete RLC PDU, and then transfer the one complete RLC PDU to the NR PDCP device. The NR RLC layer may not include a concatenation function, and the NR MAC layer may perform the concatenation function or the concatenation function may be replaced with a multiplexing function of the NR MAC layer.
In the above description, out-of-sequence delivery of the NR RLC device may mean a function of directly delivering RLC SDUs received from a lower layer to a higher layer regardless of order and include a function of reassembling and delivering several RLC SDUs in the case that an original RLC SDU is divided into several RLC SDUs and received and a function of storing RLC SNs or PDCP sequence numbers (SNs) of received RLC PDUs, arranging the order, and recording lost RLC PDUs.
The NR MACs 1d-15 and 1d-30 may be connected to several NR RLC layer devices constituted in one UE, and main functions of the NR MAC may include some of the following functions.
NR PHY layers 1d-20 and 1d-25 may perform operations of channel-coding and modulating higher layer data, making the higher layer data into OFDM symbols and transmitting the OFDM symbols through a radio channel, or demodulating OFDM symbols received through a radio channel, channel-decoding the OFDM symbols, and delivering the OFDM symbols to a higher layer.
Referring to
Referring to
In this case, base stations 1e-04 and 1e-05 associated with each USIM may recognize a USIM 1 UE 1e-02 and a USIM 2 UE 1e-03 as separate UEs, not the multi-USIM capable UE 1e-01 in which a USIM 1 UE 1e-02 and a USIM 2 UE 1e-03 operate in the same device. The USIM 1 UE 1e-02 and the USIM 2 UE 1e-03 according to an embodiment of the disclosure may share and use a hardware capability of the multi-USIM capable UE 1e-01 with each other. Therefore, in the case that the USIM 1 UE 1e-02 and the USIM 2 UE 1e-03 simultaneously transmit and receive signals to and from a base station 1 (NW1) 1e-04 and a base station 2 (NW2) 1e-05, the capability of each USIM UE may be temporarily limited by each other.
In step 1e-10, the USIM 1 UE 1e-02 may configure a radio resource control (RRC) connection with the NW11e-04 to be in an RRC connected mode (RRC_CONNECTED).
In step 1e-11, the USIM 2 UE 1e-03 may configure an RRC connection with the NW21e-05 to be in an RRC connected mode (RRC_CONNECTED).
In step 1e-11, the USIM 1 UE 1e-02 may transmit a UE capability information message (UECapabilityInformation) containing capability information of the multi-USIM capable UE 1e-01 to the NW11e-04.
The capability of the multi-USIM capable UE 1e-01 is static, but because the USIM 1 UE 1e-02 shares and uses the capability of the multi-USIM capable UE 1e-01 with the USIM 2 UE 1e-03, the capability of the USIM 1 UE 1e-02 may be temporarily restricted according to an operation of the USIM 2 UE 1e-03.
For example, the USIM 1 UE 1e-02 may include a full capability of not sharing hardware with the USIM 2 UE 1e-03 in UECapabilityInformation according to the capability of the multi-USIM capable UE 1e-01, but the capability of the USIM 1 UE 1e-02 may be temporarily restricted according to the operation of the USIM 2 UE 1e-03. Therefore, the USIM 1 UE 1e-02 may include capability information related to such temporary UE capability restriction in the message and notify the NW11e-04 of the capability information. Specifically, the message may include the following information.
In step 1e-20, the NW11e-04 may transmit otherConfig including a musim-CapabilityRestrictionConfig to the USIM1 UE 1e-02.
The NW11e-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration message) including configuration information (musim-CapabilityRestrictionConfig) that allows the USIM1 UE 1e-02 to report preferred/required temporary UE capability restriction information to the NW11e-04. The musim-CapabilityRestrictionConfig may be stored in otherConfig. For example, the musim-CapabilityRestrictionConfig may include the following information.
In step 1e-25, the USIM 2 UE 1e-03 may configure an RRC connection with the NW21e-05 to be in an RRC connected mode (RRC_CONNECTED).
In step 1e-30, the USIM 1 UE 1e-02 may transmit UEAssistanceInformation including musim-CapabilityRestriction to the NW11e-04.
More specifically, the USIM 1 UE 1e-02 may transmit a predetermined RRC message (e.g., UEAssistanceInformation) including temporary UE capability restriction information (musim-CapabilityRestriction) due to the operation of the USIM 2 UE 1e-03 to the NW11e-04. For example, the predetermined RRC message may include at least one of the following temporary UE capability restriction information.
For reference, in step 1e-30, in the case that at least one of the following conditions is satisfied, the USIM 1 UE 1e-02 may transmit a predetermined RRC message (e.g., UEAssistanceInformation) including temporary UE capability restriction information (musim-CapabilityRestriction) to the NW11e-04.
In step 1e-35, the NW11e-04 may transmit an RRCReconfiguration message to the USIM 1 UE 1e-02.
More specifically, the NW11e-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing RRC configuration information based on temporary UE capability restriction information provided by the USIM 1 UE 1e-02 in response to step 1e-30.
In step 1e-40, the USIM 1 UE 1e-02 may transmit an RRCReconfigurationComplete message to the NW11e-04.
More specifically, the USIM 1 UE 1e-02 may transmit a predetermined RRC message (e.g., RRCReconfigurationComplete) to the NW11e-04 in response to a predetermined RRC message received in step 1e-35.
In step 1e-41, the NW11e-04 may transmit an RRC connection release message (RRCRelease) including suspension configuration information (suspendConfig) to the USIM 1 UE 1e-02.
In step 1e-45, the USIM 1 UE 1e-02 may change the mode thereof to an RRC inactive mode (RRC_INACTIVE).
In step 1e-50, the USIM 1 UE 1e-02 may acquire system information from the NW11e-04.
In system information according to an embodiment of the disclosure, in the case that the USIM 1 UE 1e-02 has temporary UE capability restrictions due to a MUSIM operation (i.e., by the USIM 2 UE 1e-03), an indicator indicating whether it is allowed to transmit an indicator indicating this to the NW11e-04 may be broadcasted.
For example, in the case that system information includes the indicator, the USIM 1 UE 1e-02 may include an indicator about temporary UE capability restrictions in a predetermined RRC message (e.g., RRCSetupComplete, RRCResumeComplete, RRCReconfigurationComplete, RRCReestablishmentComplete) and transmit the predetermined RRC message to the NW11e-04.
The NW11e-04 that has received the temporary UE capability restriction indicator may not provide RRC configuration information to the USIM 1 UE 1e-02 according to the capability of the multi-USIM capable UE 1e-01, but may provide RRC configuration information according to specific temporary UE capability restriction information after receiving the specific temporary UE capability restriction information later from the USIM 1 UE 1e-02.
In step 1e-55, the USIM 1 UE 1e-02 may transmit an RRC connection resumption request message (e.g., RRCResumeRequest or RRCResumeRequest1) so as to resume an RRC connection with the NW11e-04.
In step 1e-60, the NW11e-04 may transmit an RRC connection resumption message (RRCResume) or an RRC connection setup message (RRCSetup) to the USIM 1 UE 1e-02.
For example, the RRC connection resumption message may include a fullConfig, and include (some) information (e.g., masterCellGroup, radioBearerConfig) included in the RRC connection setup message.
In step 1e-65, the USIM 1 UE 1e-02 may apply configuration information received in step 1e-60 to change the mode thereof to an RRC connected mode (RRC_CONNECTED).
In step 1e-60, the USIM 1 UE 1e-02 in an RRC connected mode may transmit a predetermined RRC message (RRCResumeComplete or RRCSetupComplete) including an indicator about temporary UE capability restrictions to the NW11e-04.
A predetermined RRC message may mean at least one of the following:
For reference, in the case that at least one of the following conditions is satisfied, the USIM 1 UE 1e-02 may transmit a predetermined RRC message including an indicator about temporary UE capability restrictions to the NW11e-04.
Referring to
A multi-USIM capable UE 1f-01 according to an embodiment of the disclosure may mean a UE supporting two or more USIMs. According to an embodiment of the disclosure, for convenience of description, a dual-USIM UE supporting two USIMs is considered. The dual-USIM UE has a feature of transmitting to a base station associated with one USIM at a given time or transmitting to a base station associated with each USIM. Similarly, a dual-USIM UE has a feature of receiving from a base station associated with one USIM at a given time or simultaneously receiving from a base station associated with each USIM.
Referring to
Hereinafter, in embodiments of the disclosure, for convenience of description, in the case that the MUSIM UE communicates using the USIM 1, the MUSIM UE is referred to as a USIM 1 UE, and in the case that the MUSIM UE communicates using the USIM 2, the MUSIM UE is referred to as a USIM 2 UE. For example, the MUSIM UE may be a USIM 1 UE or a USIM 2 UE according to which USIM between the USIM 1 and USIM 2 is used.
In step 1f-10, the USIM 1 UE 1f-02 may configure an RRC connection with the NW11f-04 to be in an RRC connected mode (RRC_CONNECTED).
In step 1f-10, the USIM 2 UE 1f-03 may not configure an RRC connection with the NW21f-05 to be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE).
The disclosure may be equally applied even to the case that the USIM 2 UE 1f-03 may configure an RRC connection with the NW21f-05 to be in an RRC connected mode (RRC_CONNECTED).
In step 1f-15, the USIM 1 UE 1f-02 may transmit UECapabilityInformation including musim-CapPreference to the NW11f-04.
More specifically, the USIM 1 UE 1f-02 may transmit a UE capability information message (UECapabilityInformation) to the NW11f-04. The UE capability information message may include the following information.
In step 1f-20, the NW11f-04 may transmit otherConfig including musim-GapAssistanceConfig to the USIM1 UE 1f-02.
More specifically, the NW11f-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration message) including configuration information (musim-GapAssistanceConfig) that enables the USIM1 UE 1f-02 to report preferred/required MUSIM gap information for a MUSIM operation.
Additionally, the musim-GapAssistanceConfig may be stored in otherConfig. The musim-GapAssistanceConfig may include one or more of the following information.
In step 1f-25, the USIM 2 UE 1f-03 may determine whether to perform required activities in an RRC idle mode or an RRC inactive mode.
The predetermined operation is an operation of the USIM 2 UE 1f-03 related to the NW21f-05, and may mean at least one of the following.
The above-described operation may be a periodic operation, an aperiodic operation, or a one-time operation.
In step 1f-30, the USIM 2 UE 1f-03 may notify the USIM 1 UE 1f-02 of information required to perform the above-described operations in step 1f-25 in an RRC idle mode or an RRC inactive mode.
For reference, step 1f-30 may be implemented by the MUSIM UE 1f-01.
In step 1f-35, the USIM 1 UE 1f-02 may transmit UEAssistanceInformation including a musim-GapPreferenceList to the NW11f-04.
More specifically, the USIM 1 UE 1f-02 may transmit a predetermined RRC message (e.g., UEAssistanceInformation message) containing configuration information (MUSIM-GapPreferenceList) on one or more preferred MUSIM gap patterns to the NW11f-04. The MUSIM-GapPreferenceList may include information having the following ASN. 1 structure.
indicates data missing or illegible when filed
In step 1f-35, the USIM 1 UE 1f-02 may transmit a predetermined RRC message including a musim-GapPreferenceList to the NW11f-04 according to the following conditions. Table 2 to Table 4 may be referred to.
In step 1f-40, the NW11f-04 may transmit RRCReconfiguration including musim-GapConfig to the USIM 1 UE 1f-02.
More specifically, the NW11f-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing one or more MUSIM gap configuration information (musim-GapConfig) based on a musim-GapPreferenceList requested by the USIM 1 UE 1f-02 in response to step 1f-35. The musim-GapConfig may include information having the following ASN.1 structure.
indicates data missing or illegible when filed
In step 1f-45, the USIM 1 UE 1f-02 may transmit an RRCReconfigurationComplete message to the NW11f-04.
More specifically, the USIM 1 UE 1f-02 may transmit a predetermined RRC message (e.g., RRCReconfigurationComplete) to the NW11f-04 in response to a predetermined RRC message received in step 1f-40.
In step 1f-50, in the case that each MUSIM gap occurs according to the MUSIM gap configuration received in step 1f-40, at least one of operations of step 1f-25 described above may be performed. In this case, the USIM 1 UE 1f-02 may maintain the RRC connected mode with the NW11f-04.
Referring to
A multi-USIM capable UE 1g-01 according to an embodiment of the disclosure may mean a UE that supports two or more USIMs. According to an embodiment of the disclosure, for convenience of description, a dual-USIM UE supporting two USIMs is considered. The dual-USIM UE has a feature of transmitting to a base station associated with one USIM at a given time or transmitting to a base station associated with each USIM. Similarly, the dual-USIM UE has a feature of receiving from a base station associated with one USIM at a given time or simultaneously receiving from a base station associated with each USIM.
Referring to
Hereinafter, in the embodiments of the disclosure, for convenience of description, in the case that the MUSIM UE communicates using the USIM 1, the MUSIM UE is referred to as a USIM 1 UE, and in the case that the MUSIM UE communicates using the USIM 2, the MUSIM UE is referred to as a USIM 2 UE. For example, the MUSIM UE may be a USIM 1 UE or a USIM 2 UE according to which USIM between the USIM 1 and USIM 2 is used.
In step 1g-10, the USIM 1 UE 1g-02 may configure an RRC connection with the NW11g-04 to be in an RRC connected mode (RRC_CONNECTED).
In step 1g-10, the USIM 2 UE 1g-03 may not configure an RRC connection with the NW21g-05 to be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE).
The disclosure may be equally applied even to the case that the USIM 2 UE 1g-03 may configure an RRC connection with the NW21g-05 to be in an RRC connected mode (RRC_CONNECTED).
In step 1g-15, the USIM 1 UE 1g-02 may transmit a UE capability information message (UECapabilityInformation) to the NW11g-04.
This may follow the foregoing embodiment. Additionally, the UE capability information message may include the following information.
In step 1g-20, the NW11g-04 may transmit otherConfig to the USIM1 UE 1g-02.
More specifically, the NW11g-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration message) including configuration information (musim-GapAssistanceConfig) that enables the USIM1 UE 1g-02 to report preferred/required MUSIM gap information for a MUSIM operation. Additionally, the musim-GapAssistanceConfig may be stored in otherConfig. This may follow the foregoing embodiment.
Additionally, the musim-GapAssistanceConfig according to an embodiment of the disclosure may include at least one of the following information.
In step 1g-25, the USIM 2 UE 1g-03 may determine whether to perform required activities in an RRC idle mode or an RRC inactive mode. This may follow the foregoing embodiment.
In step 1g-30, the USIM 2 UE 1g-03 may notify the USIM 1 UE 1g-02 of information required to perform an operation of step 1g-25 in an RRC idle mode or an RRC inactive mode. This may follow the foregoing embodiment.
In step 1g-35, the USIM 1 UE 1g-02 may transmit UEAssistanceInformation to the NW11g-04.
More specifically, the USIM 1 UE 1g-02 may transmit a predetermined RRC message (e.g., UEAssistanceInformation message) containing configuration information (musim-GapPreferenceList) on one or more preferred MUSIM gap patterns to the NW11g-04. This may follow the foregoing embodiment.
Additionally, the UE may store a preferred gap priority for each periodic MUSIM gap pattern in the UEAssistanceInformation message due to step 1g-30. For reference, for an aperiodic MUSIM gap, the gap priority may not be stored in the UEAssistanceInformation message. This is because the aperiodic MUSIM gap is maintained even if it collides with any measurement gaps (all gaps including MUSIM gaps, MGs, or the like) and the UE applies this when configuring the aperiodic MUSIM gap.
The UE may set GapPriority-r17 considering a gap priority based on all measurement gaps for all preferred periodic MUSIM gap patterns. For example, the UE may set GapPriority-r17 to one integer value from 1 to 16 for each periodic MUSIM gap pattern. In this case, 1 may represent the highest priority, 2 may represent the next highest priority, and 16 may represent the lowest priority. Two or more periodic MUSIM gap patterns may be configured to the same gap priority.
In the above description, the UE may store an indicator wanting to maintain and apply colliding periodic MUSIM gaps in the UEAssistanceInformation. The indicator may be a 1-bit indicator or an indicator for each periodic MUSIM gap.
Alternatively, in the above description, the UE may store an indicator that it wants to maintain and apply all colliding MUSIM gaps (including an aperiodic MUSIM gap) in the UEAssistanceInformation message. The indicator may be a 1-bit indicator or an indicator for each MUSIM gap.
In step 1g-40, the NW11g-04 may transmit an RRCReconfiguration message including musim-GapConfig to the USIM 1 UE 1g-02.
More specifically, the NW11g-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing one or more MUSIM gap configuration information (musim-GapConfig) based on the musim-GapPreferenceList requested by the USIM 1 UE 1g-02 in response to step 1g-35. This may follow the foregoing embodiment.
Additionally, in an embodiment of the disclosure, the base station may configure a periodic MUSIM gap to the UE through the following methods.
For reference, GapPriority-r17 may be configured to an integer value from 1 to 16, 1 may represent the highest priority, and 2 may represent the next highest priority.
In the above description, the base station may not configure a separate gap priority for the aperiodic MUSIM gap.
In the above description, the base station may configure an indicator indicating to apply a keep solution to the UE for one or more MUSIM gaps. The indicator may be separately indicated only for periodic MUSIM gaps to which the keep solution is applied or only for all MUSIM gaps, or the indicator may be indicated to apply a keep solution for all colliding periodic MUSIM gaps or all colliding periodic MUSIM gaps and aperiodic MUSIM gap through 1 bit. For reference, in the above description, it may be explicitly indicated whether to apply a priority solution or a keep solution for the MUSIM gap.
Alternatively, in the above description, it may be indicated whether to apply a keep solution to the MUSIM gap. In this case, a gap priority may not be configured for the MUSIM gap to which a keep solution is applied.
In step 1g-45, the USIM 1 UE 1g-02 may transmit an RRCReonfigurationComplete message to the NW11g-04.
More specifically, the USIM 1 UE 1g-02 may transmit a predetermined RRC message to the NW11g-04 in response to a predetermined RRC message received in step 1g-40. For example, the predetermined RRC message may mean RRCReconfigurationComplete.
In step 1g-50, the NW11g-04 may transmit MeasGapConfig to the USIM 1 UE 1g-02.
More specifically, the NW11g-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration message) containing measurement gap configuration information (MeasGapConfig) to the USIM 1 UE 1g-02. One or more GapConfig-r17 information may be stored in the MeasGapConfig. Specifically, Gap-Config-r17 may have ASN.1 structure and information illustrated in Table 5.
According to an embodiment of the disclosure, type-2 MG means a gap configured to Gap-Config-r17, and in this case, type-2 MG may mean that preConfigInd-r17 and ncsgInd-r17 are not configured to true. Alternatively, type-2 MG may mean another MG known to a MUSIM gap. For reference, when the base station configures type-2 MG to the UE, the base station has a feature of not receiving UE assistance information but directly configuring a gap priority, unlike the MUSIM gap.
In step 1g-55, the USIM 1 UE 1g-02 may determine that the configured type-2 MG and the MUSIM gap to which the keep solution is applied overlap or collide in the time axis. In this case, the UE may maintain and apply the MUSIM gap to which the keep solution is applied. For example, the UE may perform an operation required for the USIM 2 UE 1g-03.
Referring to
A multi-USIM capable UE 1h-01 according to an embodiment of the disclosure may mean a UE that supports two or more USIMs. According to an embodiment of the disclosure, for convenience of description, a dual-USIM UE supporting two USIMs is considered. The dual-USIM UE has a feature of transmitting to a base station associated with one USIM at a given time or transmitting to a base station associated with each USIM. Similarly, the dual-USIM UE has a feature of receiving from a base station associated with one USIM at a given time or simultaneously receiving from a base station associated with each USIM.
Referring to
Hereinafter, in embodiments of the disclosure, for convenience of description, in the case that the MUSIM UE communicates using the USIM 1, the MUSIM UE is referred to as a USIM 1 UE, and in the case that the MUSIM UE communicates using the USIM 2, the MUSIM UE is referred to as a USIM 2 UE. For example, the MUSIM UE may be a USIM 1 UE or a USIM 2 UE according to which USIM between the USIM 1 and USIM 2 is used.
In step 1h-10, the USIM 1 UE 1h-02 may configure an RRC connection with the NW11h-04 to be in an RRC connected mode (RRC_CONNECTED).
In step 1h-10, because the USIM 2 UE 1h-03 does not configure an RRC connection with the NW21h-05, the USIM 2 UE 1h-03 may be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE).
The disclosure may be equally applied even to the case that the USIM 2 UE 1h-03 may configure an RRC connection with the NW21h-05 to be in an RRC connected mode (RRC_CONNECTED).
In step 1h-15, the USIM 1 UE 1h-02 may transmit a UE capability information message (UECapabilityInformation) to the NW11h-04.
This may follow the foregoing embodiment. Additionally, the UE capability information message may include the following information.
In step 1h-20, the NW11h-04 may transmit otherConfig to the USIM1 UE 1h-02.
More specifically, the NW11h-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration message) including configuration information (musim-GapAssistanceConfig) that enables the USIM1 UE 1h-02 to report preferred/required MUSIM gap information for a MUSIM operation. Additionally, the musim-GapAssistanceConfig may be stored in otherConfig. This may follow the foregoing embodiment.
Additionally, according to an embodiment of the disclosure, the musim-GapAssistanceConfig may include at least one of the following information.
In step 1h-25, the USIM 2 UE 1h-03 may determine whether it should perform required activities in an RRC idle mode or an RRC inactive mode. This may follow the foregoing embodiment.
In step 1h-30, the USIM 2 UE 1h-03 may notify the USIM 1 UE 1h-02 of information required to perform an operation of step 1h-25 in an RRC idle mode or an RRC inactive mode. This may follow the foregoing embodiment.
In step 1h-35, the USIM 1 UE 1h-02 may transmit UEAssistanceInformation to the NW11h-04.
More specifically, the USIM 1 UE 1h-02 may transmit a predetermined RRC message (e.g., UEAssistanceInformation message) containing configuration information (musim-GapPreferenceList) on one or more preferred MUSIM gap patterns to the NW11h-04. This may follow the foregoing embodiment.
Additionally, the UE may store the preferred gap priority for each periodic MUSIM gap pattern in the UEAssistanceInformation message due to step 1h-30. For reference, for an aperiodic MUSIM gap, the gap priority may not be stored in the UEAssistanceInformation message. This is because the aperiodic MUSIM gap is maintained even if it collides with any measurement gap (all gaps including MUSIM gaps, MGs, or the like) and the UE applies this when configuring the aperiodic MUSIM gap.
The UE may set GapPriority-r17 considering a gap priority based on all measurement gaps for all preferred periodic MUSIM gap patterns. For example, the UE may set GapPriority-r17 to one integer value from 1 to 16 for each periodic MUSIM gap pattern. In this case, 1 may represent the highest priority, 2 may represent the next highest priority, and 16 may represent the lowest priority. Two or more periodic MUSIM gap patterns may be configured to the same gap priority.
In the above description, the UE may store an indicator wanting to maintain and apply colliding periodic MUSIM gaps in the UEAssistanceInformation message. The indicator may be a 1-bit indicator or an indicator for each periodic MUSIM gap.
Alternatively, in the above description, the UE may store an indicator wanting to maintain and apply all colliding MUSIM gaps (including aperiodic MUSIM gap) in the UEAssistanceInformation message. The indicator may be a 1-bit indicator or an indicator for each MUSIM gap. In the above description, the UE may store an indicator about which gap (MUSIM gap or type-2 MG) to use in the case that MUSIM gaps to which the keep solution is applied and the type-2 MG collide in the UEAssistanceInformation message.
In step 1h-40, the NW11h-04 may transmit an RRCReconfiguration message including musim-GapConfig to the USIM1 UE 1h-02.
More specifically, the NW11h-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing one or more MUSIM gap configuration information (musim-GapConfig) based on a musim-GapPreferenceList requested by the USIM 1 UE 1h-02 in response to step 1h-35. This may follow the foregoing embodiment.
Additionally, in an embodiment of the disclosure, the base station may configure a periodic MUSIM gap to the UE through the following methods.
For reference, GapPriority-r17 may be configured to an integer value from 1 to 16. 1 may represent the highest priority, and 2 may represent the next highest priority. In the above description, the base station may not separately configure a gap priority to the aperiodic MUSIM gap.
In the above description, the base station may configure an indicator indicating to apply the keep solution to one or more MUSIM gaps to the UE. The indicator may be separately indicated only for periodic MUSIM gaps to which the keep solution is applied or only for all MUSIM gaps, or the indicator may be indicted to apply the keep solution to all colliding periodic MUSIM gaps or all colliding periodic MUSIM gaps and aperiodic MUSIM gap through 1 bit.
For reference, in the above description, it may be explicitly indicated whether to apply the priority solution or the keep solution to the MUSIM gap. Alternatively, in the above description, it may be indicated whether to apply the keep solution to the MUSIM gap. In this case, the gap priority may not be configured to the MUSIM gap to which the keep solution is applied. In the above description, an indicator may be included indicating which gap (MUSIM gap or type-2 MG) to use in the case that MUSIM gaps to which the keep solution is applied collides with type-2 MG.
In step 1h-45, the USIM 1 UE 1h-02 may transmit an RRCReonfigurationComplete message to the NW11h-04.
More specifically, the USIM 1 UE 1h-02 may transmit a predetermined RRC message to the NW11h-04 in response to a predetermined RRC message received in step 1h-40. For example, the predetermined RRC message may mean RRCReconfigurationComplete.
In step 1h-50, the NW11h-04 may transmit MeasGapConfig to the USIM1 UE 1h-02.
More specifically, the NW11h-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration message) containing measurement gap configuration information (MeasGapConfig) to the USIM 1 UE 1h-02. One or more GapConfig-r17 information may be stored in the MeasGapConfig. Specifically, Gap-Config-r17 may have an ASN.1 structure and information illustrated in Table 6.
In an embodiment of the disclosure, type-2 MG means a gap configured to Gap-Config-r17, and in this case, type-2 MG may mean that preConfigInd-r17 and ncsgInd-r17 are not configured to true. Alternatively, type-2 MG may mean another MG known to a MUSIM gap. For reference, when the base station configures type-2 MG to the UE, the base station has a feature of not receiving UE assistance information but directly configuring a gap priority, unlike the MUSIM gap.
In step 1h-55, the USIM 1 UE 1h-02 may determine that the configured type-2 MG and the MUSIM gap to which the keep solution is applied overlap or collide on the time axis. In this case, the UE may determine and apply whether to maintain and apply the MUSIM gap to which the keep solution is applied or to apply the type-2 MG according to a configuration of the base station.
Referring to
A multi-USIM capable UE 1i-01 according to an embodiment of the disclosure may mean a UE that supports two or more USIMs. According to an embodiment of the disclosure, for convenience of description, a dual-USIM UE supporting two USIMs is considered. The dual-USIM UE has a feature of transmitting to a base station associated with one USIM at a given time or transmitting to a base station associated with each USIM. Similarly, the dual-USIM UE has a feature of receiving from a base station associated with one USIM at a given time or simultaneously receiving from a base station associated with each USIM.
Referring to
In step 1i-10, the USIM 1 UE 1i-02 may configure an RRC connection with the NW11i-04 to be in an RRC connected mode (RRC_CONNECTED).
In step 1i-10, the USIM 2 UE 1i-03 may not configure an RRC connection with the NW2 li-05 to be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE).
The disclosure may be equally applied even to the case that the USIM 2 UE 1i-03 may configure an RRC connection with the NW2 li-05 to be in an RRC connected mode (RRC_CONNECTED).
In step 1i-15, the USIM 1 UE 1i-02 may transmit a UE capability information message (UECapabilityInformation) to the NW11i-04. This may follow the foregoing embodiment. Additionally, the UE capability information message may include the following information.
In step 1i-20, the NW11i-04 may transmit otherConfig to the USIM 1 UE 1i-02.
More specifically, the NW1 li-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration message) including configuration information (musim-GapAssistanceConfig) that enables the USIM1 UE 1i-02 to report preferred/required MUSIM gap information for a MUSIM operation. Additionally, the musim-GapAssistanceConfig may be stored in otherConfig. This may follow the foregoing embodiment.
Additionally, according to an embodiment of the disclosure, the musim-GapAssistanceConfig may include at least one of the following information.
In step 1i-25, the USIM 2 UE 1i-03 may determine whether it should perform required activities in an RRC idle mode or an RRC inactive mode. This may follow the foregoing embodiment.
In step 1i-30, the USIM 2 UE 1i-03 may notify the USIM 1 UE 1i-02 of required information in order to perform an operation in step 1i-25 in an RRC idle mode or an RRC inactive mode. This may follow the foregoing embodiment.
In step 1i-35, the USIM 1 UE 11-02 may transmit UEAssistanceInformation to the NW11i-04.
More specifically, the USIM 1 UE 1i-02 may transmit a predetermined RRC message (e.g., UEAssistanceInformation message) containing configuration information (musim-GapPreferenceList) on one or more preferred MUSIM gap patterns to the NW11i-04. This may follow the foregoing embodiment.
Additionally, the UE may store a preferred gap priority for each periodic MUSIM gap pattern in the UEAssistanceInformation message due to step 1i-30. For reference, for an aperiodic MUSIM gap, the gap priority may not be stored in the UEAssistanceInformation message. This is because the aperiodic MUSIM gap is maintained even if it collides with any measurement gap (all gaps including MUSIM gaps, MGs, or the like) and the UE applies this when configuring the aperiodic MUSIM gap.
The UE may set GapPriority-r17 considering a gap priority based on all measurement gaps for all preferred periodic MUSIM gap patterns. For example, the UE may set GapPriority-r17 to one integer value from 1 to 16 for each periodic MUSIM gap pattern. In this case, 1 may represent the highest priority, 2 may represent the next highest priority, and 16 may represent the lowest priority. Two or more periodic MUSIM gap patterns may be configured to the same gap priority.
In the above description, the UE may store an indicator wanting to maintain and apply colliding periodic MUSIM gaps in the UEAssistanceInformation message. The indicator may be a 1-bit indicator or an indicator for each periodic MUSIM gap.
Alternatively, in the above description, the UE may store an indicator wanting to maintain and apply all colliding MUSIM gaps (including aperiodic MUSIM gap) in the UEAssistanceInformation message. The indicator may be a 1-bit indicator or an indicator for each MUSIM gap. In the above description, in the case that MUSIM gaps to which the keep solution is applied and the type-2 MG collide, an indicator about which gap (MUSIM gap or type-2 MG) wants to use may be stored in the UEAssistanceInformation message.
In step 1i-40, the NW1 li-04 may transmit an RRCReconfiguration message including musim-GapConfig to the USIMM 1 UE 1i-02.
More specifically, the NW1 li-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing one or more MUSIM gap configuration information (musim-GapConfig) based on a musim-GapPreferenceList requested by the USIM 1 UE 1i-02 in response to step 1i-35. This may follow the foregoing embodiment. Additionally, in an embodiment of the disclosure, the base station may configure a periodic MUSIM gap to the UE through the following methods.
For reference, GapPriority-r17 may be configured to an integer value from 1 to 16. 1 may represent the highest priority, and 2 may represent the next highest priority. In the above description, the base station may not separately configure a gap priority for the aperiodic MUSIM gap.
In the above description, the base station may configure an indicator indicating to apply the keep solution to the UE for one or more MUSIM gaps. The indicator may be separately indicated only for periodic MUSIM gaps to which the keep solution is applied or only for all MUSIM gaps, or the indicator may be indicated to apply the keep solution for all colliding periodic MUSIM gaps or all colliding periodic MUSIM gaps and aperiodic MUSIM gap through 1 bit.
For reference, in the above description, it may be explicitly indicated whether to apply the priority solution or the keep solution to the MUSIM gap. Alternatively, in the above description, it may be indicated whether to apply the keep solution to the MUSIM gap. In this case, a gap priority may not be configured to the MUSIM gap to which the keep solution is applied.
In step 1i-45, the USIM 1 UE 1i-02 may transmit an RRCReconfigurationComplete message to the NW11i-04.
More specifically, the USIM 1 UE 1i-02 may transmit a predetermined RRC message to the NW1 li-04 in response to a predetermined RRC message received in step 1i-40. For example, the predetermined RRC message may mean RRCReconfigurationComplete.
In step 1i-50, the NW1 li-04 may transmit MeasGapConfig to the USIM 1 UE 1i-02.
More specifically, the NW1 li-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration message) containing measurement gap configuration information (MeasGapConfig) to the USIM 1 UE 1i-02. One or more GapConfig-r17 information may be stored in the MeasGapConfig. Specifically, Gap-Config-r17 may have an ASN.1 structure and information as illustrated in Table 7.
In an embodiment of the disclosure, type-2 MG means a gap configured to Gap-Config-r17, and in this case, type-2 MG may mean that preConfigInd-r17 and ncsgInd-r17 are not configured to true. Alternatively, type-2 MG may mean another MG known to a MUSIM gap. For reference, when the base station configures type-2 MG to the UE, the base station has a feature of not receiving UE assistance information but directly configuring a gap priority, unlike a MUSIM gap.
In step 1i-55, the USIM 1 UE 1i-02 may determine that the configured type-2 MG and the MUSIM gap to which the keep solution is applied overlap or collide in the time axis. In this case, the UE may compare the highest gap priority of MUSIM gaps configured to use keep solution and the gap priority of type-2 MG.
For example, in the case that the highest gap priority among MUSIM gaps to which the keep solution is applied is 1 and that the priority of type-2 MG is 2, the MUSIM gaps to which the keep solution is applied may be applied and the type-2 MG may be dropped (Then, apply gap of higher gap priority). For reference, the UE may regard an aperiodic MUSIM gap as the highest gap priority (i.e., the gap priority is 1).
Referring to
Referring to
In step 1j-05, the MUSIM UE may be configured to provide MUSIM assistance information for a gap priority. This may follow at least one of the foregoing embodiments.
In step 1j-10, the MUSIM UE may determine whether at least one of the following conditions is satisfied (Need to initiate transmission of the UEAssistanceInformation message to provide current musim-GapPrioirtyPreferenceList?).
Condition In 3: the case that the current musim-GapPriorityPreferenceList is different from the one indicated in the last transmission of the UEAssistanceInformation message including musim-GapPriorityPreferenceList and that a prohibit timer for this is not running
In step 1j-15, the MUSIM UE may include the musim-GapPriorityPreferenceList the UE prefers to be configured in the UEAssistanceInformation message.
In the case that the UE has a preference for using a keep solution, the UE may include the keep solution information the UE prefers to be configured in the UEAssistanceInformation message. The keep solution information may follow at least one of the foregoing embodiments. The UE may transmit UEAssistanceInformation to the base station. For reference, the UE may run or rerun a prohibit timer when initiating the UEAssistanceInformation.
The UE according to the disclosure has a feature of not triggering a separate UEAssistanceInformation transmission procedure in order to send only keep solution information preference. For example, the UE has a feature of including together keep solution information when it wants to send the musim-GapPriorityPreferenceList the UE prefers to be configured.
Referring to
Referring to
In step 1k-05, the MUSIM UE may be configured to provide MUSIM assistance information for gap priority preference. This may follow the foregoing embodiment.
In step 1k-10, the MUSIM UE may determine whether at least one of the following conditions is satisfied (Need to initiate transmission of the UEAssistanceInformation message to provide current keep solution preference?).
In the case that the current keep solution application preference of the UE is different from the keep solution application preference most recently transmitted and indicated in UEAssistanceInformation.
In step 1k-15, in the case that the UE include a musim-GapPriorityPreferenceList the UE prefers to be configured), the UE may store the musim-GapPriorityPreferenceList in the UEAssistanceInformation message.
In the case that the UE has a preference for using keep solution, the UE may include the keep solution information the UE prefers to be configured in the UEAssistanceInformation message. The keep solution information may follow at least one of the foregoing embodiments. The UE may transmit UEAssistanceInformation to the base station. For reference, the UE may run or rerun a prohibit timer when initiating the UEAssistanceInformation. For reference, in the case that a musim-GapPriorityPreferenceList has never been sent, the UE may not store only keep solution information in the UEAssistanceInformation message.
The UE according to an embodiment of the disclosure has a feature that may trigger a UEAssistanceInformation transmission procedure so as to send only keep solution information preference.
Referring to
The RF processer 11-10 may perform a function for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. For example, the RF processer 11-10 may up-convert a baseband signal provided from the baseband processer 11-210 into an RF band signal, transmit the RF band signal through an antenna, and down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processer 11-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), and the like. In the drawing, only one antenna is illustrated, but the UE may be equipped with multiple antennas. Further, the RF processer 11-10 may include multiple RF chains. Furthermore, the RF processer 11-10 may perform beamforming. For the above beamforming, the RF processer 11-10 may adjust a phase and size of each of signals transmitted and received through multiple antennas or antenna elements. Further, the RF processer may perform MIMO and receive multiple layers when performing a MIMO operation.
The baseband processer 11-20 may perform a conversion function between a baseband signal and a bit string according to the physical layer specification of the system. For example, when transmitting data, the baseband processer 11-20 may encode and modulate a transmitted bit string to generate complex symbols. Further, when receiving data, the baseband processer 11-20 may demodulate and decode a baseband signal provided from the RF processer 11-10 to restore a received bit string. For example, in the case of following an orthogonal frequency division multiplexing (OFDM) method, when transmitting data, the baseband processer 11-20 may encode and modulate a transmitted bit string to generate complex symbols, map the complex symbols into subcarriers, and then constitute OFDM symbols through inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. Further, when receiving data, the baseband processer 11-20 divides the baseband signal provided from the RF processer 11-10 into OFDM symbol units, restore signals mapped to subcarriers through fast Fourier transform (FFT), and then restores the received bit string through demodulation and decoding.
The baseband processer 11-20 and the RF processer 11-10 may transmit and receive signals, as described above. Accordingly, the baseband processer 11-20 and the RF processer 11-10 may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processer 11-20 or the RF processer 11-10 may include a plurality of communication modules so as to support a plurality of different wireless access technologies. Further, at least one of the baseband processer 11-20 or the RF processer 11-10 may include different communication modules so as to process signals of different frequency bands. For example, the different wireless access technologies may include a wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), and the like. Further, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band, and a millimeter wave (e.g., 60 GHz) band.
The storage 11-30 may store data, such as a basic program, an application program, and configuration information for an operation of the UE. More particularly, the storage 11-30 may store information related to a second access node that performs wireless communication using second wireless access technology. The storage 11-30 provides stored data according to a request from the controller 11-40.
The controller 11-40 may include a multi-connection processor 11-42 and may control the overall operations of the UE. For example, the controller 11-40 may transmit and receive signals through the baseband processer 11-20 and the RF processer 11-10. Further, the controller 11-40 records and reads data in the storage 11-40. For this purpose, the controller 11-40 may include at least one processor. For example, the controller 11-40 may include a communication processor (CP) that performs the control for communication and an application processor (AP) that controls upper layers, such as application programs.
Referring to
The baseband processer 1m-20 may perform a conversion function between a baseband signal and a bit string according to the physical layer standard of first wireless access technology. For example, when transmitting data, the baseband processer 1m-20 may encode and modulate a transmitted bit string to generate complex symbols. Further, when receiving data, the baseband processer 1m-20 may demodulate and decode a baseband signal provided from the RF processer 1m-10 to restore a received bit string. For example, in the case of following an OFDM method, when transmitting data, the baseband processer 1m-20 may encode and modulate a transmitted bit string to generate complex symbols, map the complex symbols into subcarriers, and then constitute OFDM symbols through IFFT operation and CP insertion. Further, when receiving data, the baseband processer 1m-20 may divide a baseband signal provided from the RF processer 1m-10 into OFDM symbol units, restore signals mapped to subcarriers through FFT operation, and then restore the received bit string through demodulation and decoding. The baseband processer 1m-20 and the RF processer 1m-10 transmit and receive signals, as described above. Accordingly, the baseband processer 1m-20 and the RF processer 1m-10 may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a RF unit.
The backhaul communication unit 1m-30 may provide an interface for performing communication with other nodes within the network. For example, the backhaul communication unit 1m-30 converts a bit string transmitted from a main base station to another node, for example, an auxiliary base station, and a core network into a physical signal, and converts a physical signal received from the other node into a bit string.
The storage 1m-40 may include a multi-connection processor 1m-52 and may store data, such as a basic program, an application program, and configuration information for an operation of the main base station. More particularly, the storage 1m-40 may store information on bearers allocated to accessed UEs, measurement results reported from accessed UEs, and the like. Further, the storage 1m-40 may store information that serves as a determination criterion for whether to provide or to terminate multiple connections to the UE. The storage 1m-40 provides stored data according to a request from the controller 1m-50.
The controller 1m-50 may control the overall operations of the main base station. For example, the controller 1m-50 may transmit and receive signals through the baseband processer 1m-20 and the RF processer 1m-10 or through the backhaul communication unit 1m-30. Further, the controller 1m-50 records and reads data in the storage 1m-40. For this purpose, the controller 1m-50 may include at least one processor.
Referring to
A multi-USIM capable UE 1n-01 according to an embodiment of the disclosure may mean a UE that supports two or more USIMs. According to an embodiment of the disclosure, for convenience of description, a dual-USIM UE supporting two USIMs is considered. The dual-USIM UE has a feature of transmitting to a base station associated with one USIM at a given time or transmitting to a base station associated with each USIM. Similarly, the dual-USIM UE has a feature of receiving from a base station associated with one USIM at a given time or simultaneously receiving from a base station associated with each USIM.
Referring to
In step 1n-10, the USIM 1 UE 1n-02 may configure an RRC connection with the NW11n-04 to be in an RRC connected mode (RRC_CONNECTED).
In step 1n-10, because the USIM 2 UE 1n-03 does not configure an RRC connection with the NW21n-05, the USIM 2 UE 1n-03 may be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE).
The disclosure may be equally applied even to the case that the USIM 2 UE 1n-03 configures an RRC connection with the NW21n-05 to be in an RRC connected mode (RRC_CONNECTED).
In step 1n-15, the USIM 1 UE 1n-02 may transmit a UE capability information message (UECapabilityInformation) to the NW11n-04. This may follow the foregoing embodiment. Additionally, the UE capability information message may include the following information.
For reference, an indicator that supports a keep solution may not be included separately. In this case, it may mean that the UE also supports a keep solution in the case that it supports a 1-bit indicator indicating whether it supports a MUSIM gap priority configuration and preference.
In step 1n-20, the NW11n-04 may transmit otherConfig to the USIM 1 UE 1n-02.
More specifically, the NW11n-04 may transmit a predetermined RRC message (e.g., an RRCReconfiguration message) including configuration information (musim-GapAssistanceConfig) that enables the USIM1 UE 1n-02 to report preferred/required MUSIM gap information for a MUSIM operation. Additionally, the musim-GapAssistanceConfig may be stored in otherConfig. This may follow the foregoing embodiment.
Additionally, according to an embodiment of the disclosure, the musim-GapAssistanceConfig may include at least one of the following information.
In step 1n-25, the USIM 2 UE 1n-03 may determine whether it should perform required activities in an RRC idle mode or an RRC inactive mode. This may follow the foregoing embodiment.
In step 1n-30, the USIM 2 UE 1n-03 may notify the USIM 1 UE 1n-02 of required information in order to perform an operation of step 1n-25 in an RRC idle mode or an RRC inactive mode. This may follow the foregoing embodiment.
In step 1n-35, the USIM 1 UE 1n-02 may determine whether to initiate transmission of UEAssistanceInformation to the NW11n-04.
More specifically, the USIM 1 UE 1n-02 according to the disclosure may distinguish the case that it is configured to provide only MUSIM assistance information for MUSIM gap preference and the case that while it is configured to provide MUSIM assistance information for MUSIM gap preference, it is configured to provide MUSIM assistance information for MUSIM gap priority preference to determine whether to transmit UEAssistanceInformation to the base station 1n-04. For example, in the case that it is configured to provide only MUSIM assistance information for gap preference, the USIM 1 UE 1n-02 may transmit UEAssistanceInformation including a musim-GapPreferenceList to the base station 1n-04 according to the foregoing embodiment (see
The above conditions may be expressed as an example as follows.
For example, the USIM 1 UE 1n-01 according to the disclosure has a feature of not initiating transmission of the current musim-GapPreferenceList and/or UEAssistanceInformation to provide the musim-GapPriorityPreferenceList and/or musim-GapKeepPreference in the case that a timer T346h is running. The UE has a feature that when it initiates transmission of the current musim-GapPreferenceList and/or UEAssistanceInformation to provide the musim-GapPriorityPreferenceList and/or musim-GapKeepPreference, it runs only once or reruns the timer T346h according to a timer value configured in a musim-GapProhibitTimer.
For reference, the USIM 1 UE 1n-02 may include the current musim-GapPreferenceList and/or musim-GapPriorityPreferenceList and/or musim-GapKeepPreference in the UEAssistanceInformation message according to the following procedure.
More specifically, the NW11n-04 may transmit a predetermined RRC message (e.g., RRCReconfiguration message) containing one or more MUSIM gap configuration information (musim-GapConfig) based on the musim-GapPreferenceList and/or musim-GapPriorityPreferenceList and/or musim-GapKeepPreference requested by the USIM 1 UE 1n-02 in response to step 1n-35. This may follow at least one of the foregoing embodiments.
In step 1n-45, the USIM 1 UE 1n-02 may transmit an RRCReconfigurationComplete message to the NW11n-04.
Methods according to the embodiments described in the claims or specifications of the disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
In the case of being implemented in software, a computer readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in the computer readable storage medium are configured for execution by one or more processors in an electronic device. The one or more programs include instructions for causing an electronic device to execute methods according to embodiments described in claims or specification of the disclosure.
Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable ROM (EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), another form of optical storage device, or a magnetic cassette. Alternatively, the programs may be stored in memory including a combination of some or all thereof. Further, each constitution memory may be included in the plural.
Further, the program may be stored in an attachable storage device that may access through a communication network, such as the Internet, Intranet, local area network (LAN), wide LAN (WLAN), or storage area network (SAN), or a communication network including a combination thereof. Such a storage device may access a device implementing an embodiment of the disclosure through an external port. Further, a separate storage device on the communication network may access the device implementing the embodiment of the disclosure.
In an embodiment of the disclosure, the term “computer program product” or “computer readable medium” is used for collectively referring to media, such as memory, a hard disk installed in a hard disk drive, and signals. These “computer program products” or “computer readable medium” are components provided in a method of reporting UE capabilities in a wireless communication system according to the disclosure.
The machine readable storage medium may be provided in the form of a non-transitory storage medium. Here, ‘non-transitory storage medium’ is a tangible device and only means that the storage medium does not include a signal (e.g., electromagnetic wave), and this term does not distinguish the case that data is semi-permanently stored in the storage medium and the case that data is temporary stored. For example, a ‘non-transitory storage medium’ may include a buffer in which data is temporarily stored.
According to an embodiment or the disclosure, a method according to various embodiments disclosed in this document may be included and provided in a computer program product. Computer program products may be traded between sellers and buyers as commodities. The computer program product may be distributed in the form of a machine readable storage medium (e.g., compact disc read only memory (CD-ROM)), or via an application store (e.g., Play Store™) or may be distributed (e.g., download or upload) online or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a part of the computer program product (e.g., downloadable app) may be at least temporarily stored or temporarily generated in a machine readable storage medium, such as memory of a server of a manufacturer, a server of an application store, or a relay server.
In the specific embodiments of the disclosure described above, components included in the disclosure are expressed in the singular or plural according to the presented specific embodiments. However, the singular or plural expression is appropriately selected for a situation presented for convenience of description, and the disclosure is not limited to the singular or plural components, and even if a component is represented in the plural, it may include the singular, or even if a component is represented in the singular, it may include the plural.
It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.
Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform a method of the disclosure.
Any such software may be stored in the form of volatile or non-volatile storage, such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory, such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium, such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.
While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2023-0130527 | Sep 2023 | KR | national |
| 10-2024-0026452 | Feb 2024 | KR | national |
