Method and device for managing musim gap priority in wireless communication system
The method of configuring MUSIM gap priorities through RRC messages in wireless communication systems addresses the inefficiencies in managing MUSIM gaps and measurement gaps, enhancing network efficiency and reducing conflicts.
Patent Information
- Application Number
- PCT/KR2024/006167
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-11
- Filing Date
- 2024-05-08
- Publication Date
- 2024-11-14
AI Technical Summary
In wireless communication systems, managing priorities for multiple USIM (MUSIM) gaps is necessary to prevent conflicts between MUSIM gaps and measurement gaps, which current technologies do not effectively address, leading to inefficiencies and potential communication disruptions.
A method and device that allow user equipment (UE) to provide a MUSIM gap priority preference list to the base station, using radio resource control (RRC) messages to configure and manage MUSIM gaps, ensuring efficient operation and conflict avoidance.
This approach reduces the processing load on terminals and enhances network communication efficiency by effectively managing MUSIM gaps and measurement gaps, thereby improving overall system performance.
Smart Images

Figure KR2024006167_14112024_PF_FP_ABST
Abstract
Description
Method and device for managing MUSIM gap priority in a wireless communication system
[0001] The present disclosure relates to a wireless communication system. More specifically, the present disclosure relates to a method and device for setting and managing priorities for multiple USIM (Multi-Universal Subscriber Identity Module, MUSIM) gaps in a wireless communication system.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.
[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.
[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.
[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.
[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.
[0008] As discussions on MUSIM operation in wireless communication systems evolve, the need for methods to set and manage gap priorities to prevent conflicts between MUSIM gaps and measurement gaps arises.
[0009] In one embodiment of the present disclosure, a method performed by a user equipment (UE) of a wireless communication system is provided. The method comprises the steps of: receiving, from a base station, a first radio resource control (RRC) reconfiguration message including information indicating that the UE is permitted to provide multi-universal subscriber identity module (MUSIM) support information for gap priorities; and transmitting, to the base station, a UE support information message including a MUSIM gap priority preference list indicating MUSIM gap priorities preferred by the UE. The MUSIM gap priority preference list includes information representing respective priorities for all periodic MUSIM gap preference patterns as integer values.
[0010] In one embodiment of the present disclosure, a method performed by a base station of a wireless communication system is provided. The method comprises the steps of transmitting, to the UE, a first RRC reconfiguration message including information indicating that the UE is permitted to provide MUSIM support information for gap priorities, and receiving, from the UE, a UE support information message including a MUSIM gap priority preference list indicating MUSIM gap priorities preferred by the UE. The MUSIM gap priority preference list includes information expressing respective priorities for all periodic MUSIM gap preference patterns as integer values.
[0011] In one embodiment of the present disclosure, a UE of a wireless communication system is provided. The UE includes a transceiver and a control unit. The control unit is configured to receive, from a base station through the transceiver, a first RRC reconfiguration message including information indicating that the UE is permitted to provide MUSIM support information for gap priorities, and to transmit, to the base station through the transceiver, a UE support information message including a MUSIM gap priority preference list indicating MUSIM gap priorities preferred by the UE. The MUSIM gap priority preference list includes information expressing respective priorities for all periodic MUSIM gap preference patterns as integer values.
[0012] In one embodiment of the present disclosure, a base station of a wireless communication system is provided. The base station includes a transceiver and a control unit. The control unit is configured to transmit, to the UE via the transceiver, a first RRC reconfiguration message including information indicating that the UE is permitted to provide MUSIM support information for gap priorities, and to receive, from the UE, a UE support information message including a MUSIM gap priority preference list indicating MUSIM gap priorities preferred by the UE. The MUSIM gap priority preference list includes information expressing respective priorities for all periodic MUSIM gap preference patterns as integer values.
[0013] According to one embodiment of the present disclosure, the processing load of a terminal of a wireless communication system can be reduced and the communication efficiency of a network can be increased.
[0014] FIG. 1 is a diagram illustrating the structure of an LTE system according to one embodiment of the present invention.
[0015] FIG. 2 is a diagram illustrating a wireless protocol structure in an LTE system according to an embodiment of the present invention.
[0016] FIG. 3 is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present invention.
[0017] FIG. 4 is a diagram showing a wireless protocol structure of a next-generation mobile communication system according to an embodiment of the present invention.
[0018] FIG. 5 is a diagram illustrating a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple USIMs (Universal Subscriber Identity Modules) performing operations related to another USIM while maintaining an RRC connection mode (RRC_CONNECTED) with a base station related to one USIM, according to one embodiment of the present disclosure.
[0019] FIG. 6 is a diagram illustrating a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple USIMs (Universal Subscriber Identity Modules) performing operations related to another USIM while maintaining an RRC connection mode (RRC_CONNECTED) with a base station related to one USIM, according to one embodiment of the present disclosure.
[0020] FIG. 7 is a diagram illustrating a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple USIMs (Universal Subscriber Identity Modules) performing operations associated with another USIM while maintaining an RRC connection mode (RRC_CONNECTED) with a base station associated with one USIM, according to one embodiment of the present disclosure.
[0021] FIG. 8 is a diagram illustrating a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple USIMs (Universal Subscriber Identity Modules) performing operations associated with another USIM while maintaining an RRC connection mode (RRC_CONNECTED) with a base station associated with one USIM, according to one embodiment of the present disclosure.
[0022] FIG. 9 is a block diagram illustrating the internal structure of a terminal according to an embodiment of the present invention.
[0023] Figure 10 is a block diagram showing the configuration of an NR base station according to one embodiment of the present invention.
[0024] In describing the embodiments herein, descriptions of technical details that are well-known in the technical field to which the present invention pertains and are not directly related to the present invention will be omitted. This is to avoid obscuring the gist of the present invention by omitting unnecessary explanations and to convey the gist more clearly.
[0025] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.
[0026] The advantages and features of the present invention, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present invention is complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification.
[0027] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).
[0028] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.
[0029] Here, the term '~ unit' used in the present embodiment means a software or hardware component such as an FPGA or ASIC, and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, as an example, the '~ 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, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card.
[0030] The operating principles of the present invention will be described in detail below with reference to the attached drawings. In the following description of the present invention, detailed descriptions of known functions or components will be omitted if they are deemed to unnecessarily obscure the gist of the invention. Furthermore, the terms described below are defined based on their functions in the present invention and may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the overall content of this specification.
[0031] In the following description of the present invention, detailed descriptions of known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present invention. Hereinafter, embodiments of the present invention will be described with reference to the attached drawings.
[0032] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.
[0033] For convenience of explanation, the present invention uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP) LTE standard. However, the present invention is not limited to these terms and names and can be equally applied to systems conforming to other standards. In the present invention, the term "eNB" may be used interchangeably with "gNB" for convenience of explanation. In other words, a base station described as an eNB may also represent a gNB.
[0034] FIG. 1 is a diagram illustrating the structure of an LTE system according to one embodiment of the present invention.
[0035] Referring to FIG. 1, as illustrated, the wireless access network of the LTE system is composed of next-generation base stations (Evolved Node Bs, hereinafter ENBs, Node Bs or base stations) (1-05, 1-10, 1-15, 1-20), MMEs (1-25, Mobility Management Entity) and S-GWs (1-30, Serving-Gateway). User equipment (UEs, hereinafter UEs or terminals) (1-35) access external networks through ENBs (1-05 to 1-20) and S-GWs (1-30).
[0036] In Fig. 1, ENBs (1-05 to 1-20) correspond to the existing Node B of the UMTS system. ENBs are connected to UEs (1-35) via a wireless channel and perform a more complex role than the existing Node B. In the LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, is serviced through a shared channel. Therefore, a device that collects status information such as the buffer status of UEs, available transmission power status, and channel status and performs scheduling is required, and ENBs (1-05 to 1-20) are in charge of this. One ENB typically controls multiple cells. For example, in order to implement a transmission speed of 100 Mbps, the LTE system uses, for example, orthogonal frequency division multiplexing (OFDM) as a wireless access technology in a 20 MHz bandwidth. In addition, it applies Adaptive Modulation & Coding (AMC) method that determines modulation scheme and channel coding rate according to the channel condition of the terminal. S-GW (1-30) is a device that provides data bearers and creates or removes data bearers according to the control of MME (1-25). MME is a device that is responsible for mobility management function for terminals as well as various control functions and is connected to multiple base stations.
[0037] FIG. 2 is a diagram illustrating a wireless protocol structure in an LTE system according to an embodiment of the present invention.
[0038] Referring to Figure 2, the wireless protocol of the LTE system consists of PDCP (Packet Data Convergence Protocol 2-05, 2-40), RLC (Radio Link Control 2-10, 2-35), and MAC (Medium Access Control 2-15, 2-30) in the terminal and ENB, respectively. PDCP (Packet Data Convergence Protocol) (2-05, 2-40) is responsible for operations such as IP header compression / decompression. The main functions of PDCP are summarized as follows.
[0039] - Header compression and decompression (ROHC only)
[0040] - User data transfer function
[0041] - In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM
[0042] - Order reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)
[0043] - Duplicate detection function (Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)
[0044] - Retransmission function (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)
[0045] - Encryption and decryption functions (Ciphering and deciphering)
[0046] - Timer-based SDU discard in uplink.
[0047] Radio Link Control (RLC) (2-10, 2-35) reconfigures PDCP PDUs (Packet Data Units) to an appropriate size and performs ARQ operations, etc. The main functions of RLC are summarized as follows.
[0048] - Data transfer function (Transfer of upper layer PDUs)
[0049] - ARQ function (Error Correction through ARQ (only for AM data transfer))
[0050] - Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer)
[0051] - Re-segmentation of RLC data PDUs (only for AM data transfer)
[0052] - Reordering of RLC data PDUs (only for UM and AM data transfer)
[0053] - Duplicate detection (only for UM and AM data transfer)
[0054] - Error detection function (Protocol error detection (only for AM data transfer))
[0055] - RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))
[0056] - RLC re-establishment function
[0057] MAC (2-15, 2-30) connects to multiple RLC layer devices configured in a single terminal, and multiplexes RLC PDUs into MAC PDUs and demultiplexes RLC PDUs from MAC PDUs. The main functions of MAC are summarized as follows.
[0058] - Mapping function (Mapping between logical channels and transport channels)
[0059] - Multiplexing and demultiplexing function (Multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels)
[0060] - Scheduling information reporting function
[0061] - HARQ function (Error correction through HARQ)
[0062] - Priority handling between logical channels of one UE
[0063] - Priority handling between UEs by means of dynamic scheduling
[0064] - MBMS service identification function
[0065] - Transport format selection function
[0066] - Padding function
[0067] The physical layer (2-20, 2-25) performs the operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to the upper layer.
[0068] FIG. 3 is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present invention.
[0069] Referring to FIG. 3, as illustrated, the wireless access network of the next-generation mobile communication system (hereinafter referred to as NR or 2g) is composed of a next-generation base station (New Radio Node B, hereinafter referred to as NR gNB or NR base station) (3-10) and an NR CN (3-05, New Radio Core Network). A user terminal (New Radio User Equipment, hereinafter referred to as NR UE or terminal) (3-15) connects to an external network through the NR gNB (3-10) and the NR CN (3-05).
[0070] In Fig. 3, the NR gNB (3-10) corresponds to the eNB (Evolved Node B) of the existing LTE system. The NR gNB is connected to the NR UE (3-15) via a wireless channel and can provide a service that is superior to the existing Node B. In the next-generation mobile communication system, all user traffic is serviced through a shared channel, so a device that collects status information such as the buffer status of UEs, available transmission power status, and channel status and performs scheduling is required, and the NR NB (3-10) is in charge of this. One NR gNB typically controls multiple cells. In order to implement ultra-high-speed data transmission compared to the current LTE, it can have a bandwidth higher than the existing maximum, and beamforming technology can be additionally grafted using the orthogonal frequency division multiplexing (OFDM) method as a wireless access technology. In addition, it applies the Adaptive Modulation & Coding (AMC) method that determines the modulation scheme and channel coding rate according to the channel condition of the terminal. NR CN (3-05) performs functions such as mobility support, bearer setup, and QoS setup. NR CN is a device that handles various control functions as well as mobility management functions for terminals and is connected to multiple base stations. In addition, the next-generation mobile communication system can also be linked with the existing LTE system, and NR CN is connected to MME (3-25) through a network interface. MME is connected to the existing base station, eNB (3-30).
[0071] FIG. 4 is a diagram showing a wireless protocol structure of a next-generation mobile communication system according to an embodiment of the present invention.
[0072] Figure 4 is a diagram showing the wireless protocol structure of a next-generation mobile communication system to which the present invention can be applied.
[0073] Referring to FIG. 4, the wireless protocol of the next-generation mobile communication system consists of NR SDAP (4-01, 4-45), NR PDCP (4-05, 4-40), NR RLC (4-10, 4-35), and NR MAC (4-15, 4-30) in the terminal and NR base station, respectively.
[0074] Key features of NR SDAP (4-01, 4-45) may include some of the following:
[0075] - Transfer of user plane data
[0076] - Mapping function between QoS flow and data bearer for both DL and UL
[0077] - QoS flow ID marking function for uplink and downlink (marking QoS flow ID in both DL and UL packets)
[0078] - Ability to map relective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).
[0079] For the above SDAP layer device, the terminal can be configured by RRC message for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device, and when the SDAP header is configured, the terminal can be instructed to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink with the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) of the SDAP header. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support a smooth service.
[0080] The main functions of NR PDCP (4-05, 4-40) may include some of the following functions:
[0081] Header compression and decompression (ROHC only)
[0082] - User data transfer function
[0083] - In-sequence delivery of upper layer PDUs
[0084] - Out-of-sequence delivery of upper layer PDUs
[0085] - PDCP PDU reordering for reception
[0086] - Duplicate detection of lower layer SDUs
[0087] - Retransmission function (Retransmission of PDCP SDUs)
[0088] - Encryption and decryption functions (Ciphering and deciphering)
[0089] - Timer-based SDU discard in uplink.
[0090] The reordering function of the NR PDCP device above refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order, or may include a function of transmitting data directly without considering the order, may include a function of recording lost PDCP PDUs by reordering the order, may include a function of reporting the status of lost PDCP PDUs to the transmitting side, and may include a function of requesting retransmission of lost PDCP PDUs.
[0091] The main functions of NR RLC(4-10, 4-35) may include some of the following functions:
[0092] - Data transfer function (Transfer of upper layer PDUs)
[0093] - In-sequence delivery of upper layer PDUs
[0094] - Out-of-sequence delivery of upper layer PDUs
[0095] - ARQ function (Error Correction through ARQ)
[0096] - Concatenation, segmentation and reassembly of RLC SDUs
[0097] - Re-segmentation of RLC data PDUs
[0098] - Reordering of RLC data PDUs
[0099] - Duplicate detection function
[0100] - Protocol error detection
[0101] - RLC SDU discard function
[0102] - RLC re-establishment function
[0103] The in-sequence delivery function of the NR RLC device above refers to the function of sequentially transmitting RLC SDUs received from a lower layer to an upper layer, and may include a function of reassembling and transmitting RLC SDUs when an RLC SDU is originally received divided into multiple RLC SDUs, may include a function of reordering received RLC PDUs based on RLC SN (sequence number) or PDCP SN (sequence number), may include a function of recording lost RLC PDUs by reordering the sequence, may include a function of reporting the status of lost RLC PDUs to the transmitting side, may include a function of requesting retransmission of lost RLC PDUs, may include a function of sequentially transmitting only RLC SDUs up to the lost RLC SDU to an upper layer when there is a lost RLC SDU, or may include a function of sequentially transmitting all RLC SDUs received before the timer starts when a predetermined timer expires even when there is a lost RLC SDU. Or, even if there are lost RLC SDUs, if a predetermined timer has expired, it may include a function to sequentially deliver all RLC SDUs received up to the upper layer. In addition, the RLC PDUs may be processed in the order they are received (in the order of arrival, regardless of the order of the sequence number) and delivered to the PDCP device out of sequence (out-of-sequence delivery). In the case of segments, the segments stored in the buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and then delivered to the PDCP device.The above NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.
[0104] The out-of-sequence delivery function of the NR RLC device above refers to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order, and may include a function of reassembling and delivering RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of received RLC PDUs and arranging the order to record lost RLC PDUs.
[0105] NR MAC (4-15, 4-30) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions.
[0106] - Mapping function (Mapping between logical channels and transport channels)
[0107] - Multiplexing / demultiplexing of MAC SDUs
[0108] - Scheduling information reporting function
[0109] - HARQ function (Error correction through HARQ)
[0110] - Priority handling between logical channels of one UE
[0111] - Priority handling between UEs by means of dynamic scheduling
[0112] - MBMS service identification function
[0113] - Transport format selection function
[0114] - Padding function
[0115] The NR PHY layer (4-20, 4-25) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.
[0116] FIG. 5 is a diagram illustrating a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple USIMs (Universal Subscriber Identity Modules) performing operations related to another USIM while maintaining an RRC connection mode (RRC_CONNECTED) with a base station related to one USIM, according to one embodiment of the present disclosure.
[0117] A MUSIM terminal (5-01) according to an embodiment of the present disclosure may refer to a terminal that supports two or more USIMs. For the sake of convenience of explanation, the present disclosure assumes a Dual-USIM terminal that supports two USIMs, but the scope of the present disclosure is not limited to two USIMs and may be applied to a terminal that supports two or more USIMs. In one example, a Dual-USIM terminal may transmit a signal to a base station associated with one USIM at a given time, or may transmit signals to base stations associated with each USIM. Similarly, a Dual-USIM terminal may receive a signal from a base station associated with one USIM at a given time, or may simultaneously receive signals from base stations associated with each USIM.
[0118] Referring to FIG. 5, a MUSIM terminal (5-01) may refer to a terminal that supports multiple USIMs in one device. For example, a MUSIM terminal may refer to a USIM 1 terminal (5-02) when operating on USIM 1, and a USIM 2 terminal (5-03) when operating on USIM 2. A base station associated with each USIM may not recognize the MUSIM terminal as one terminal, but may recognize each USIM terminal as one terminal. For example, base station 1 (5-04) may recognize a USIM 1 terminal (5-02) as one terminal, and base station 2 (5-05) may recognize a USIM 2 terminal (5-03) as one terminal.
[0119] For convenience of explanation in the embodiments of the present disclosure below, when a MUSIM terminal communicates using USIM 1, the MUSIM terminal will be referred to as a USIM 1 terminal, and when the MUSIM terminal communicates using USIM 2, the MUSIM terminal will be referred to as a USIM 2 terminal. For example, the MUSIM terminal may be a USIM 1 terminal or a USIM 2 terminal depending on which USIM is used between USIM 1 and USIM 2.
[0120] In step 5-10, the USIM 1 terminal (5-02) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 1 (5-04). On the other hand, in step 5-12, the USIM 2 terminal (5-03) may not establish an RRC connection with base station 2 (5-05) and may be in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE). In addition, the embodiments of the present disclosure may be equally applied even when the USIM 2 terminal (5-03) establishes an RRC connection with base station 2 (5-05) and is in RRC connected mode (RRC_CONNECTED).
[0121] In step 5-15, the USIM 1 terminal (5-02) can transmit a terminal capability information message (UECapabilityInformation) to base station 1 (5-04). The terminal capability information message can include the following information.
[0122] - An indicator (musim-GapPreference) indicating whether or not a USIM 1 terminal (5-02) can transmit MUSIM gap preference and related MUSIM gap configuration to base station 1 (5-04) as MUSIM assistance information. The terminal supporting the above capability can support a specific number of periodic gap(s) and aperiodic gap(s). For example, the terminal supporting the above capability can support three periodic gaps and one aperiodic gap.
[0123] In the present disclosure, the term 'MUSIM gap' may mean a time period or time pattern that allows a network corresponding to a specific USIM of a MUSIM terminal to perform operations related to cell identification and measurement, paging monitoring, SIB acquisition, and / or on-demand SI request for a cell (target cell) of a network (target network) corresponding to another USIM of the MUSIM terminal for a certain period of time.
[0124] In step 5-20, base station 1 (5-04) may transmit a predetermined RRC message (e.g., an RRCReconfiguration message) containing configuration information (musim-GapAssistanceConfig) requesting the USIM1 terminal (5-02) to report preferred / required MUSIM gap information for MUSIM operation. Additionally, the musim-GapAssistanceConfig may be stored in the otherConfig field within the RRC message. The musim-GapAssistanceConfig may include the following information:
[0125] ● musim-GapProhibitTimer value
[0126] ■ When the base station 1 (5-04) sets or sets up a newly defined prohibit timer value for the USIM 1 terminal (5-02), the USIM 1 terminal (5-02) may start the timer with the set prohibit timer value when initiating a procedure for sending preferred MUSIM gap setting information to the base station 1 (5-04). In one example, when the timer is running, the USIM 1 terminal (5-02) may not be able to send a predetermined RRC message including the preferred MUSIM gap setting information of the USIM 1 terminal (5-02) to the base station 1 (5-04). Additionally, if the new timer is not running or has expired, the USIM 1 terminal (5-02) may transmit to the base station 1 (5-04) a predetermined RRC message (e.g., UEAssistanceInformation) containing the MUSIM gap setting information preferred by the USIM 1 terminal (5-02).
[0127] In step 5-25, the USIM 2 terminal (5-03) can determine whether to perform or must perform a predetermined operation in RRC idle mode or RRC deactivation mode. The predetermined operation is an operation related to base station 2 (5-05) performed by the USIM 2 terminal (5-03), and may mean at least one of the following or a combination thereof.
[0128] ● Operation 1: The USIM 2 terminal (5-03) does not perform the RRC connection establishment procedure or the RRC connection resume procedure with base station 2 (5-05), but can perform an operation of receiving a signal transmitted by base station 2 (5-05) or an internal operation of the USIM 2 terminal through reception. For example:
[0129] ■ USIM 2 terminal (5-03) can monitor a paging channel or short message associated with base station 2 (5-05). For example, USIM2 terminal (5-03) can monitor a paging occasion for each DRX (Discontinuous Reception) cycle.
[0130] ■ The USIM 2 terminal (5-03) can perform monitoring to receive a notification of a change in system information associated with the base station 2 (5-05). For example, the USIM2 terminal (5-03) can monitor a paging occasion for each DRX (Discontinuous Reception) cycle.
[0131] ■ The USIM 2 terminal (5-03) can perform cell selection or cell reselection evaluation procedures. For example, the USIM 2 terminal (5-03) can perform serving cell or neighboring cell measurements as part of the cell selection or cell reselection evaluation procedures.
[0132] ■ USIM 2 terminal (5-03) can perform PLMN (Public Land Mobile Network) selection procedure.
[0133] ● Action 2: USIM 2 terminal (5-03) does not perform the RRC connection establishment procedure or RRC connection resume procedure with base station 2 (5-05), but can transmit and receive signals with base station 2 (5-05). For example:
[0134] ■ USIM 2 terminal (5-03) can request on-demand system information to base station 2 (5-05) or to obtain system information in an on-demand manner.
[0135] ● Action 3: The USIM 2 terminal (5-03) in RRC deactivation mode may perform an action of resuming RRC connection with base station 2 (5-05) but not transitioning to RRC connected mode. For example:
[0136] ■ The USIM 2 terminal (5-03) receives a radio access network (RAN) paging message transmitted by the base station 2 (5-05), and although the received RAN paging message includes a UE identifier (I-RNTI) indicating the USIM 2 terminal (5-03), the USIM 1 terminal (5-02) may need to continue transmitting and receiving data with the base station 1 (5-04). In this case, the USIM 2 terminal (5-03) may transmit a message (e.g., RRCResumeRequest or RRCResumeRequest1) containing an indication (busy indication) indicating that it cannot respond to the RAN paging message received from the base station 2 (5-05) to the base station 2 (5-05). Here, the busy indication may be contained in the resumeCause field included in the message. In response, base station 2 (5-05) may transmit an RRCReject or RRCRelease message to USIM 2 terminal (5-03).
[0137] ● Action 4: The USIM 2 terminal (5-03) can perform an action to transition to RRC connection mode by performing an RRC connection establishment or resumption procedure with base station 2 (5-05). For example:
[0138] ■ USIM 2 terminal (5-03) can perform the Registration Update procedure or the RAN Notification Area Update procedure.
[0139] The above-described actions 1 to 4 may be periodic actions, aperiodic actions, or one-time actions.
[0140] In step 5-30, the USIM 2 terminal (5-03) may notify the USIM 1 terminal (5-02) of the information required to perform the operation described above in step 5-25 in RRC idle mode or RRC deactivation mode. Here, step 5-30 may be performed depending on the implementation of the MUSIM terminal (5-01).
[0141] In step 5-35, the USIM 1 terminal (5-02) may transmit a predetermined RRC message (e.g., a UEAssistanceInformation message) containing configuration information (MUSIM-GapPreferenceList) for one or more preferred MUSIM gap pattern(s) to the base station 1 (5-04). The MUSIM-GapPreferenceList may include information having an ASN.1 structure according to the following Table 1.
[0142] MUSIM-GapPreferenceList-r17 ::= SEQUENCE (SIZE (1..4)) OF MUSIM-GapInfo-r17-MUSIM-GapInfoThe IEMUSIM-GapInfois used to indicate MUSIM gap parameters.MUSIM-GapInfoinformation element-- ASN1START-- TAG-MUSIM-GAPINFO-STARTMUSIM-GapInfo-r17 ::= SEQUENCE {musim-Starting-SFN-AndSubframe-r17 MUSIM-Starting-SFN-AndSubframe-r17 OPTIONAL, -- Cond aperiodicmusim-GapLength-r17 ENUMERATED {ms3, ms4, ms6, ms10, ms20} OPTIONAL, -- Cond gapSetupmusim-GapRepetitionAndOffset-r17 CHOICE {ms20-r17 INTEGER (0..19),ms40-r17 INTEGER (0..39),ms80-r17 INTEGER (0..79),ms160-r17 INTEGER (0..159),ms320-r17 INTEGER (0..319),ms640-r17 INTEGER (0..639),ms1280-r17 INTEGER (0..1279),ms2560-r17 INTEGER (0..2559),ms5120-r17 INTEGER (0..5119),...} OPTIONAL -- Cond periodic}MUSIM-Starting-SFN-AndSubframe-r17 ::= SEQUENCE {starting-SFN-r17 INTEGER (0..1023),startingSubframe-r17 INTEGER (0..9)}-- TAG-MUSIM-GAPINFO-STOP-- ASN1STOPMUSIM-GapInfofield descriptionsmusim-GapLengthIndicates the length of the UE's MUSIM gap as specified in TS 38.133 clause 9.1.10. This field is mandatory present for both periodic gap and aperiodic gap preference indication.musim-GapRepetitionAndOffsetIndicates the gap repetition period in ms and gap offset in number of subframes for the periodic MUSIM gap as specified in TS 38.133 clause 9.1.10. This field is mandatory present for the periodic MUSIM gap preference indication.musim-Starting-SFN-AndSubframeIndicates gap starting position for the aperiodic MUSIM gap. This field is optionally present for the aperiodic MUSIM gap preference indication.starting-SFNIndicates gap starting SFN number for the aperiodic MUSIM gap.startingSubframeIndicates gap starting subframe number for the aperiodic MUSIM gap.Conditional PresenceExplanationaperiodicThis field is mandatory present in case of aperiodic MUSIM gap configuration. Otherwise it is absent.gapSetupThe field is mandatory present upon configuration of a new MUSIM gap. The field is optionally present, Need M, otherwise.periodicThis field is mandatory present in case of periodic MUSIM gap configuration. Otherwise it is absent.
[0143] In step 5-35, the USIM 1 terminal (5-02) can transmit a predetermined RRC message including musim-GapPreferenceList to the base station 1 (5-04). In one example, the conditions for initiating the operation of the USIM 1 terminal (5-02) transmitting a predetermined RRC message including musim-GapPreferenceList to the base station 1 (5-04) can be expressed as shown in Tables 2 to 4 below. In this case, unless otherwise specified, the 3GPP standard TS 38.331 document can be referenced.
[0144] Initiation1> if configured to provide MUSIM assistance information for gap preference: 2> if the UE has a preference on the MUSIM gap(s) and the UE did not transmit aUEAssistanceInformationmessage withmusim-GapPreferenceListsince it was configured to provide MUSIM assistance information for gap preference; or 2> if the currentmusim-GapPreferenceListis different from the one indicated in the last transmission of theUEAssistanceInformationmessage includingmusim-GapPreferenceListand the timer T346h is not running: 3> initiate transmission of theUEAssistanceInformationmessage in accordance with 5.7.4.3 to provide the currentmusim-GapPreferenceList; 3> start or restart the timer T346h with the timer value set to themusim-GapProhibitTimer.NOTE: The UE does not need to initiate transmission of theUEAssistanceInformationmessage if the difference between the currentmusim-GapPreferenceListand the last transmission of theUEAssistanceInformationmessage includingmusim-GapPreferenceListis only due to removal of an ended aperiodic gap.
[0145] Actions related to transmission ofUEAssistanceInformationmessage1> if transmission of theUEAssistanceInformationmessage is initiated to provide MUSIM assistance information according to 5.7.4.2 or 5.3.5.3: 2> if the UE has a preference for MUSIM periodic gap(s): 3> includemusim-GapPreferenceListwith an entry for each periodic gap the UE prefers to be configured; 4> setmusim-GapLengthandmusim-GapRepetitionAndOffsetin themusim-GapInfoIEto the values of the length and the repetition / offset of the gap(s), respectively, the UE prefers to be configured with; 2> if the UE has a preference for MUSIM aperiodic gap: 3> include the fieldmusim-GapPreferenceList, with one entry for the aperiodic gap the UE prefers to be configured; 4> includemusim-GapLengthin themusim-GapInfoIEand set it to the values of the length of the gap the UE prefers to be configured with; 4> optionally includemusim-Starting-SFN-AndSubframein themusim-GapInfoIE and set it to the starting SFN / subframe of the gap the UE prefers to be configured with; 2> if the UE has no longer preference for the periodic / aperiodic gaps: 3> do not includemusim-GapPreferenceListin themusim-AssistanceIE;.
[0146] Reception of anRRCReconfigurationby the UE1> ifreconfigurationWithSyncwas included inspCellConfigof an MCG or SCG, and when MAC of an NR cell group successfully completes a Random Access procedure triggered above: 2> stop timer T304 for that cell group; 2> stop timer T310 for source SpCell if running; 2> apply the parts of the CSI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any; 2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell; 2> for each DRB configured as DAPS bearer, request uplink data switching to the PDCP entity, as specified in TS 38.323;2> if thereconfigurationWithSyncwas included inspCellConfigof an MCG: 3> if T390 is running: 4> stop timer T390 for all access categories; 4> perform the actions as specified in 5.3.14.4. 3> if T350 is running: 4> stop timer T350; 3> ifRRCReconfigurationdoes not includededicatedSIB1-Deliveryand 3> if the active downlink BWP, which is indicated by thefirstActiveDownlinkBWP-Idfor the target SpCell of the MCG, has a common search space configured bysearchSpaceSIB1: 4> acquire theSIB1, which is scheduled as specified in TS 38.213, of the target SpCell of the MCG; 4> upon acquiringSIB1, perform the actions specified in clause 5.2.2.4.2; 2> if thereconfigurationWithSyncwas included inspCellConfigof an MCG; or 2> if thereconfigurationWithSyncwas included inspCellConfigof an SCG and the CPA or CPC was configured 3> remove all the entries withinVarConditionalReconfig, if any;3> remove all the entries withinVarConditionalReconfigurationas specified in TS 36.331, clause 5.3.5.9.6, if any; 3> for eachmeasIdof the source SpCell configuration, if the associatedreportConfighas areportTypeset tocondTriggerConfig: 4> for the associatedreportConfigId: 5> remove the entry with the matchingreportConfigIdfrom thereportConfigListwithin theVarMeasConfig; 4> if the associatedmeasObjectIdis only associated to areportConfigwithreportTypeset tocondTriggerConfig: 5> remove the entry with the matchingmeasObjectIdfrom themeasObjectListwithin theVarMeasConfig; 4> remove the entry with the matchingmeasIdfrom themeasIdListwithin theVarMeasConfig;2> ifreconfigurationWithSyncwas included inmasterCellGrouporsecondaryCellGroup: 3> if the UE initiated transmission of aUEAssistanceInformationmessage for the corresponding cell group during the last 1 second, and the UE is still configured to provide the concerned UE assistance information for the corresponding cell group; or 3> if theRRCReconfigurationmessage is applied due to a conditional reconfiguration execution, and the UE is configured to provide UE assistance information for the corresponding cell group, and the UE has initiated transmission of aUEAssistanceInformationmessage for the corresponding cell group since it was configured to do so in accordance with 5.7.4.2: 4> initiate transmission of aUEAssistanceInformationmessage for the corresponding cell group in accordance with clause 5.7.4.3 to provide the concerned UE assistance information;4> start or restart the prohibit timer (if exists) or the leave without response timer for the MUSIM associated with the concerned UE assistance information with the timer value set to the value in corresponding configuration;
[0147] In step 5-40, base station 1 (5-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing one or more MUSIM gap configurations (musim-GapConfig)(s) based on the musim-GapPreferenceList requested by the USIM 1 terminal (5-02) in response to step 5-35. The musim-GapConfig may include information having an ASN.1 structure according to the following Table 5.
[0148] -MUSIM-GapConfigThe IEMUSIM-GapConfigspecifies the MUSIM gap configuration and controls setup / release of MUSIM gaps.MUSIM-GapConfiginformation element-- ASN1START-- TAG-MUSIM-GAPCONFIG-STARTMUSIM-GapConfig-r17 ::= SEQUENCE {musim-GapToReleaseList-r17 SEQUENCE (SIZE (1..3)) OF MUSIM-GapId-r17 OPTIONAL, -- Need Nmusim-GapToAddModList-r17 SEQUENCE (SIZE (1..3)) OF MUSIM-Gap-r17 OPTIONAL, -- Need Nmusim-AperiodicGap-r17 MUSIM-GapInfo-r17 OPTIONAL, -- Need N...}MUSIM-Gap-r17 ::= SEQUENCE {musim-GapId-r17 MUSIM-GapId-r17,musim-GapInfo-r17 MUSIM-GapInfo-r17}-- TAG-MUSIM-GAPCONFIG-STOP-- ASN1STOPMUSIM-GapConfigfield descriptionsmusim-AperiodicGapIndicates the MUSIM aperiodic gap as specified in TS 38.133 clause 9.1.10. If UE indicates themusim-Starting-SFN-AndSubframewhen requesting aperiodic gap the network can only configure the aperiodic gap with the same start point or no aperiodic gap.If the fieldmusim-Starting-SFN-AndSubframeis absent for aperiodic gap, network can configure any timing as the starting point for aperiodic gap or configure no aperiodic gap.musim-GapInfoIndicates the values formusim-GapLengthandmusim-GapRepetitionAndOffset. When network provides periodic gap, network always signals themusim-GapLengthandmusim-GapRepetitionAndOffsetas indicated by the UE's preferred MUSIM gap configuration.musim-GapToAddModListList of MUSIM periodic gap patterns to add or modify.musim-GapToReleaseListList of MUSIM periodic gap patterns to release.
[0149] In step 5-45, the USIM 1 terminal (5-02) can transmit a predetermined RRC message (e.g., RRCReconfigurationComplete) to the base station 1 (5-04) in response to the predetermined RRC message received in step 5-40.
[0150] In step 5-50, the USIM 2 terminal (5-03) may perform at least one of the operations of step 5-25 described above when each MUSIM gap occurs according to the MUSIM gap setting received in step 5-40. At this time, the USIM 1 terminal (5-02) may maintain an RRC connection mode with base station 1 (5-04).
[0151] FIG. 6 is a diagram illustrating a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple USIMs (Universal Subscriber Identity Modules) performing operations related to another USIM while maintaining an RRC connection mode (RRC_CONNECTED) with a base station related to one USIM, according to one embodiment of the present disclosure.
[0152] A MUSIM terminal (6-01) according to an embodiment of the present disclosure may refer to a terminal that supports two or more USIMs. For the sake of convenience of explanation, the present disclosure assumes a Dual-USIM terminal that supports two USIMs, but the scope of the present disclosure is not limited to two USIMs and may be applied to a terminal that supports two or more USIMs. A Dual-USIM terminal may transmit a signal to a base station associated with one USIM at a given time or transmit signals to base stations associated with each USIM. Similarly, a Dual-USIM terminal may receive a signal from a base station associated with one USIM at a given time or receive signals simultaneously from base stations associated with each USIM.
[0153] Referring to FIG. 6, a MUSIM terminal (6-01) may refer to a terminal that supports multiple USIMs in one device. For example, a MUSIM terminal may refer to a USIM 1 terminal (6-02) when operating on USIM 1, and a USIM 2 terminal (6-03) when operating on USIM 2. A base station associated with each USIM may not recognize the MUSIM terminal as one terminal, but may recognize each USIM terminal as one terminal. For example, base station 1 (6-04) may recognize a USIM 1 terminal (6-02) as one terminal, and base station 2 (not shown) may recognize a USIM 2 terminal (6-03) as one terminal. For convenience of explanation in the embodiments of the present disclosure below, when a MUSIM terminal communicates using USIM 1, the MUSIM terminal will be referred to as a USIM 1 terminal, and when the MUSIM terminal communicates using USIM 2, the MUSIM terminal will be referred to as a USIM 2 terminal. That is, the MUSIM terminal can be a USIM 1 terminal or a USIM 2 terminal depending on which USIM between USIM 1 and USIM 2 is used.
[0154] In step 6-10, the USIM 1 terminal (6-02) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 1 (6-04). On the other hand, in step 6-12, the USIM 2 terminal (6-03) may not establish an RRC connection with base station 2 (not shown) and may be in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE). In addition, the embodiments of the present disclosure may be equally applied even when the USIM 2 terminal (6-03) establishes an RRC connection with base station 2 (not shown) and is in RRC connected mode (RRC_CONNECTED).
[0155] In step 6-15, the USIM 1 terminal (6-02) may transmit a terminal capability information message (UECapabilityInformation) to base station 1 (6-04). Step 6-15 may follow steps 5-15 described above. Additionally, the terminal capability information message may further include the following information:
[0156] - An indicator indicating whether USIM 1 terminal (6-02) supports MUSIM gap priority configuration and preference to base station 1 (6-04): In one example, the indicator is a 1-bit indicator, a per-UE capability indicator, and may not differentiate xDD / FRx (1 optional per-UE capability bit (without xDD / FRx differentiation) to indicate MUSIM gap priority configuration and preference). A terminal may support the capability indicator if it supports the terminal capability of the above-described embodiment (i.e., musim-GapPreference).
[0157] In step 6-20, the base station 1 (6-04) may transmit a predetermined RRC message (e.g., an RRCReconfiguration message) containing configuration information (musim-GapAssistanceConfig) requesting the USIM1 terminal (6-02) to report preferred / required MUSIM gap information for MUSIM operation. Additionally, the musim-GapAssistanceConfig may be stored in otherConfig. This may follow step 5-20 described above. Additionally, in the present disclosure, the musim-GapAssistanceConfig may include at least one of the following information:
[0158] ● A directive to report the priority information of the gap pattern preferred by the terminal (e.g., it can be referred to as gap priority).
[0159] ■ The terminal can report its preferred gap priority to the base station only when the above indicator is included in musim-GapAssistanceConfig. This can reduce unnecessary signaling overhead, since if the base station cannot interpret the terminal's preferred gap priority, the terminal can avoid reporting it by not including the above indicator in musim-GapAssistanceConfig.
[0160] In step 6-25, the USIM 2 terminal (6-03) can determine whether to perform or be required to perform a predetermined operation in RRC idle mode or RRC inactive mode. Step 6-25 may follow steps 5-25 described above.
[0161] In step 6-30, the USIM 2 terminal (6-03) may notify the USIM 1 terminal (6-02) of the information required to perform the step 6-25 operation in RRC idle mode or RRC deactivation mode. Step 6-30 may follow the steps 5-30 described above.
[0162] In step 6-35, the USIM 1 terminal (6-02) may transmit a predetermined RRC message (e.g., a UEAssistanceInformation message) containing configuration information (musim-GapPreferenceList) for one or more preferred MUSIM gap pattern(s) to the base station 1 (6-04). Step 6-35 may follow step 5-35 described above.
[0163] Additionally, the terminal can store the preferred gap priority for each MUSIM gap pattern in the UEAssistanceInformation message due to steps 6-30. In the present disclosure, for convenience of explanation, the periodic MUSIM gap pattern is described, but the following description can be equally applied to the aperiodic MUSIM gap. The terminal can set the gap priority between the MUSIM gap patterns for all preferred periodic MUSIM gap pattern(s) or for some of the periodic MUSIM gap pattern(s). For example, the gap priority can be set with information that can indicate low, medium, and high by considering the relative priority for three periodic MUSIM gap patterns. In addition, two or more periodic MUSIM gap patterns can be set with the same gap priority. The gap priority can be expressed as a single integer value to mean the above-described content, or can be expressed as a high, medium, or low gap priority.
[0164] In step 6-40, the base station 1 (6-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing one or more MUSIM gap configurations (musim-GapConfig)(s) based on the musim-GapPreferenceList requested by the USIM 1 terminal (6-02) in response to step 6-35. Step 6-40 may follow step 5-40 described above. Additionally, in one embodiment of the present disclosure, the base station may configure a periodic MUSIM gap to the terminal through at least one of the following methods or a combination thereof.
[0165] - Method 1: The base station can set the gap priority for all periodic MUSIM gaps set to the terminal through parameters (e.g., GapPriority-r17) included in the MUSIM gap configuration information (musim-GapConfig) even if the terminal does not have preferred gap priority information for a specific periodic MUSIM gap.
[0166] - Method 2: If the terminal does not have preferred priority information for a specific periodic MUSIM gap, the base station can set the priority for the gap to be lower than or equal to the preferred gap priority value transmitted by the terminal through GapPriority-r17. Alternatively, if the terminal does not have preferred priority information for a specific periodic MUSIM gap, the base station can set the priority for the gap to be lower than or equal to the Type-2 MG (measurement gap) described later through GapPriority-r17.
[0167] - Method 3: If the base station does not have preferred priority information for a periodic MUSIM gap, the base station may not set GapPriority-r17 for the gap. In this case, the terminal may always consider the priority of the gap to be lower than the gap for which GapPriority-r17 is set (MUSIM gap or Type-2 MG).
[0168] In one example, GapPriority-r17 can be set to an integer value from 1 to 16, with a value of 1 representing the highest priority, 2 representing the next highest priority, and so on.
[0169] In step 6-45, the USIM 1 terminal (6-02) may transmit a predetermined RRC message to the base station 1 (6-04) in response to the predetermined RRC message received in step 6-40. For example, the predetermined RRC message may mean RRCReconfigurationComplete.
[0170] In step 6-50, base station 1 (6-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration message) containing measurement gap configuration information (MeasGapConfig) to USIM 1 terminal (6-02). In the present disclosure, the measurement gap may refer to a time period during which the terminal stops transmitting and receiving signals with the serving cell and measures a neighboring cell of a different frequency or a different radio access technology (RAT). One or more gap configuration (GapConfig-r17 IE)(s) may be stored in the MeasGapConfig. In addition, the predetermined RRC message (e.g., RRCReconfiguration message) containing the MeasGapConfig is not limited to the order illustrated in the drawing. For example, the message of step 6-50 may be transmitted before the message of step 6-40 is transmitted. Additionally, base station 1 (6-04) may transmit one message (e.g., RRCReconfiguration message) containing both musim-GapConfig and MeasGapConfig.
[0171] Specifically, GapConfig-r17 can have an ASN.1 structure as shown in Table 6 below.
[0172] GapConfig-r17 ::= SEQUENCE {measGapId-r17 MeasGapId-r17,gapType-r17 ENUMERATED {perUE, perFR1, perFR2},gapOffset-r17 INTEGER (0..159),mgl-r17 ENUMERATED {ms1, ms1dot5, ms2, ms3, ms3dot5, ms4, ms5, ms5dot5, ms6, ms10, ms20},mgrp-r17 ENUMERATED {ms20, ms40, ms80, ms160},mgta-r17 ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot75},refServCellIndicator-r17 ENUMERATED {pCell, pSCell, mcg-FR2} OPTIONAL, -- Cond NEDCorNRDCrefFR2-ServCellAsyncCA-r17 ServCellIndex OPTIONAL, -- Cond AsyncCApreConfigInd-r17 ENUMERATED {true} OPTIONAL, -- Need RncsgInd-r17 ENUMERATED {true} OPTIONAL, -- Need RgapAssociationPRS-r17 ENUMERATED {true} OPTIONAL, -- Need RgapSharing-r17 MeasGapSharingScheme OPTIONAL, -- Need RgapPriority-r17 GapPriority-r17 OPTIONAL, -- Need R...}
[0173] In the present disclosure, Type-2 MG means a measurement gap set to GapConfig-r17, and in this case, Type-2 MG may mean that preConfigInd-r17 and ncsgInd-r17 are not set to true.
[0174] In the present disclosure, if the preferred gap priority for a specific periodic MUSIM gap reported by the terminal in step 6-35 is high, the base station may set a gap priority level having a lower priority than the periodic MUSIM gap through GapPriority-r17 included in the gap setting in MeasGapConfig when setting the gap priority for the Type-2 MG. For example, if the base station set the value of GapPriority-r17 to 2 for the periodic MUSIM gap through step 6-40, the value of GapPriority-r17 may be set to a value greater than 2 for the Type-2 MG. Here, when the base station sets the Type-2 MG to the terminal, the base station may directly set the gap priority without receiving UE assistance information, unlike the MUSIM gap. Due to this, when Type-2 MG and MUSIM gap collide (e.g., when the times at which the terminal must apply Type-2 MG and MUSIM gap overlap), the base station cannot know which gap the terminal prefers. Therefore, by setting GapPriority-r17 for Type-2 MG by the method according to the present disclosure, the terminal can perform an operation according to priority when a collision occurs between the Type-2 MG and MUSIM gap.
[0175] In step 6-55, the USIM 1 terminal (6-02) can determine that the configured Type-2 MG and the periodic MUSIM gap overlap or collide on the time axis. At this time, the terminal can apply / use a gap with a higher gap priority. For example, when applying / using the MUSIM gap, the required operation is performed for the USIM 2 terminal (6-03), and when applying / using the Type-2 MG, the USIM 1 terminal (6-02) can perform the required operation for the base station 1 (6-04).
[0176] FIG. 7 is a diagram illustrating a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple USIMs (Universal Subscriber Identity Modules) performing operations associated with another USIM while maintaining an RRC connection mode (RRC_CONNECTED) with a base station associated with one USIM, according to one embodiment of the present disclosure.
[0177] A MUSIM terminal (7-01) according to an embodiment of the present disclosure may refer to a terminal that supports two or more USIMs. For the sake of convenience of explanation, the present disclosure assumes a Dual-USIM terminal that supports two USIMs, but the scope of the present disclosure is not limited to two USIMs and may be applied to a terminal that supports two or more USIMs. A Dual-USIM terminal can transmit a signal to a base station associated with one USIM at a given time or transmit signals to base stations associated with each USIM. Similarly, a Dual-USIM terminal has the characteristic of being able to receive a signal from a base station associated with one USIM at a given time or simultaneously receive signals from base stations associated with each USIM.
[0178] Referring to FIG. 7, a MUSIM terminal (7-01) may refer to a terminal that supports multiple USIMs in one device. For example, a MUSIM terminal may refer to a USIM 1 terminal (7-02) when operating on USIM 1, and a USIM 2 terminal (7-03) when operating on USIM 2. A base station associated with each USIM may not recognize the MUSIM terminal as one terminal, but may recognize each USIM terminal as one terminal. For example, base station 1 (7-04) may recognize a USIM 1 terminal (7-02) as one terminal, and base station 2 (not shown) may recognize a USIM 2 terminal (7-03) as one terminal. For convenience of explanation in the embodiments of the present disclosure below, when a MUSIM terminal communicates using USIM 1, the MUSIM terminal will be referred to as a USIM 1 terminal, and when the MUSIM terminal communicates using USIM 2, the MUSIM terminal will be referred to as a USIM 2 terminal. That is, the MUSIM terminal can be a USIM 1 terminal or a USIM 2 terminal depending on which USIM between USIM 1 and USIM 2 is used.
[0179] In step 7-10, the USIM 1 terminal (7-02) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 1 (7-04). On the other hand, in step 7-12, the USIM 2 terminal (7-03) may not establish an RRC connection with base station 2 (not shown) and may be in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE). In addition, the embodiments of the present disclosure may be equally applied even when the USIM 2 terminal (7-03) establishes an RRC connection with base station 2 (not shown) and is in RRC connected mode (RRC_CONNECTED).
[0180] In step 7-15, the USIM 1 terminal (7-02) may transmit a terminal capability information message (UECapabilityInformation) to base station 1 (7-04). Step 7-15 may follow at least one of steps 5-15 and 6-15 described above.
[0181] In step 7-20, base station 1 (7-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration message) containing configuration information (musim-GapAssistanceConfig) to request the USIM1 terminal (7-02) to report preferred / required MUSIM gap information for MUSIM operation. Step 7-20 may follow at least one of steps 5-20 and 6-20 described above.
[0182] In step 7-25, the USIM 2 terminal (7-03) can determine whether to perform or be required to perform a predetermined operation in RRC idle mode or RRC inactive mode. Step 7-25 may follow at least one of steps 5-25 and 6-25 described above.
[0183] In step 7-30, the USIM 2 terminal (7-03) may inform the USIM 1 terminal (7-02) of the information required to perform the step 7-25 operation in RRC idle mode or RRC deactivation mode. Step 7-30 may follow at least one of steps 5-30 and 6-30 described above.
[0184] In step 7-35, the USIM 1 terminal (7-02) may transmit a predetermined RRC message (e.g., a UEAssistanceInformation message) containing configuration information (musim-GapPreferenceList) for one or more preferred MUSIM gap pattern(s) to the base station 1 (7-04). Step 7-35 may follow at least one of steps 5-35 and 6-35 described above.
[0185] In step 7-40, the base station 1 (7-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing one or more MUSIM gap configurations (musim-GapConfig)(s) based on the musim-GapPreferenceList requested by the USIM 1 terminal (7-02) in response to step 7-35. Step 7-40 may follow at least one of steps 5-40 and 6-40 described above.
[0186] In step 7-45, the USIM 1 terminal (7-02) may transmit a predetermined RRC message to the base station 1 (7-04) in response to the predetermined RRC message received in step 7-40. For example, the predetermined RRC message may mean RRCReconfigurationComplete.
[0187] In step 7-50, base station 1 (7-04) can transmit a predetermined RRC message (e.g., RRCReconfiguration message) containing measurement gap configuration information (MeasGapConfig) to USIM 1 terminal (7-02). The measurement gap has been described in the description of FIG. 6. One or more gap configurations (GapConfig-r17 IE)(s) can be stored in the MeasGapConfig. In addition, the predetermined RRC message (e.g., RRCReconfiguration message) containing the MeasGapConfig is not restricted to the order shown in this drawing. For example, the message in step 7-50 can be transmitted before the message in step 7-40 is transmitted. In addition, base station 1 (7-04) can transmit one message (e.g., RRCReconfiguration message) containing both musim-GapConfig and MeasGapConfig.
[0188] 구체적으로, GapConfig-r17 은 하기의 표 7과 같은 ASN.1 구조를 가질 수 있다.
[0189] GapConfig-r17 ::= SEQUENCE {measGapId-r17 MeasGapId-r17,gapType-r17 ENUMERATED {perUE, perFR1, perFR2},gapOffset-r17 INTEGER (0..159),mgl-r17 ENUMERATED {ms1, ms1dot5, ms2, ms3, ms3dot5, ms4, ms5, ms5dot5, ms6, ms10, ms20},mgrp-r17 ENUMERATED {ms20, ms40, ms80, ms160},mgta-r17 ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot75},refServCellIndicator-r17 ENUMERATED {pCell, pSCell, mcg-FR2} OPTIONAL, -- Cond NEDCorNRDCrefFR2-ServCellAsyncCA-r17 ServCellIndex OPTIONAL, -- Cond AsyncCApreConfigInd-r17 ENUMERATED {true} OPTIONAL, -- Need RncsgInd-r17 ENUMERATED {true} OPTIONAL, -- Need RgapAssociationPRS-r17 ENUMERATED {true} OPTIONAL, -- Need RgapSharing-r17 MeasGapSharingScheme OPTIONAL, -- Need RgapPriority-r17 GapPriority-r17 OPTIONAL, -- Need R...}
[0190] In the present disclosure, Type-2 MG means a gap set with GapConfig-r17, and in this case, Type-2 MG may mean that preConfigInd-r17 and ncsgInd-r17 are not set to true. In the present disclosure, the base station may set GapPriority-r17 for Type-2 MG.
[0191] At step 7-55, the USIM 1 terminal (7-02) can determine whether the set Type-2 MG and the periodic MUSIM gap overlap or collide on the time axis.
[0192] In step 7-60, if the USIM 1 terminal (7-02) wants to apply the periodic MUSIM gap even though the gap priority of the periodic MUSIM gap is lower than that of the Type-2 MG, it can transmit a UEAssistanceInformation message to the base station 1 (7-04). For example, the terminal can transmit the UEAssistanceInformation message to the base station (7-04) including information or a 1-bit indicator indicating a gap priority preference for the periodic MUSIM gap to high (or information or an indicator requesting the base station to set the gap priority of the periodic MUSIM gap higher than that of the colliding Type-2 MG).
[0193] In step 7-65, the base station 1 (7-04) can transmit an RRC Reconfiguration message containing musim-GapConfig to the USIM 1 terminal (7-02). Based on step 7-60, the base station can set the value of GapPriority-r17 of the periodic MUSIM gap to be lower than that of the Type-2 MG. Alternatively, the base station can release or modify the Type-2 MG. As a result, the USIM 1 terminal (7-02) can apply / use the periodic MUSIM gap with priority over the Type-2 MG.
[0194] FIG. 8 is a diagram illustrating a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple USIMs (Universal Subscriber Identity Modules) performing operations associated with another USIM while maintaining an RRC connection mode (RRC_CONNECTED) with a base station associated with one USIM, according to one embodiment of the present disclosure.
[0195] A MUSIM terminal (8-01) according to an embodiment of the present disclosure may refer to a terminal that supports two or more USIMs. For the sake of convenience of explanation, the present disclosure assumes a Dual-USIM terminal that supports two USIMs, but the scope of the present disclosure is not limited to two USIMs and may be applied to a terminal that supports two or more USIMs. A Dual-USIM terminal may transmit a signal to a base station associated with one USIM at a given time or transmit signals to base stations associated with each USIM. Similarly, a Dual-USIM terminal has the characteristic of being able to receive a signal from a base station associated with one USIM at a given time or simultaneously receive signals from base stations associated with each USIM.
[0196] Referring to FIG. 8, a MUSIM terminal (8-01) may refer to a terminal that supports multiple USIMs in one device. For example, a MUSIM terminal may refer to a USIM 1 terminal (8-02) when operating on USIM 1, and a USIM 2 terminal (8-03) when operating on USIM 2. A base station associated with each USIM may not recognize the MUSIM terminal as one terminal, but may recognize each USIM terminal as one terminal. For example, base station 1 (8-04) may recognize a USIM 1 terminal (8-02) as one terminal, and base station 2 (not shown) may recognize a USIM 2 terminal (8-03) as one terminal. For convenience of explanation in the embodiments of the present disclosure below, when a MUSIM terminal communicates using USIM 1, the MUSIM terminal will be referred to as a USIM 1 terminal, and when the MUSIM terminal communicates using USIM 2, the MUSIM terminal will be referred to as a USIM 2 terminal. That is, the MUSIM terminal can be a USIM 1 terminal or a USIM 2 terminal depending on which USIM between USIM 1 and USIM 2 is used.
[0197] In step 8-10, the USIM 1 terminal (8-02) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 1 (8-04). On the other hand, in step 8-12, the USIM 2 terminal (8-03) may not establish an RRC connection with base station 2 (not shown) and may be in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE). In addition, the embodiments of the present disclosure may be equally applied even when the USIM 2 terminal (8-03) establishes an RRC connection with base station 2 (not shown) and is in RRC connected mode (RRC_CONNECTED).
[0198] In step 8-15, the USIM 1 terminal (8-02) may transmit a terminal capability information message (UECapabilityInformation) to the base station 1 (8-04). Step 8-15 may follow at least one of steps 5-15, 6-15, and 7-15 described above.
[0199] In step 8-20, base station 1 (8-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration message) containing configuration information (musim-GapAssistanceConfig) to request the USIM1 terminal (8-02) to report preferred / required MUSIM gap information for MUSIM operation. Step 8-20 may follow at least one of steps 5-20, 6-20, and 7-20 described above.
[0200] In step 8-25, the USIM 2 terminal (8-03) can determine whether to perform a predetermined operation in RRC idle mode or RRC inactive mode. Step 8-25 can follow at least one of steps 5-25, 6-25, and 7-25 described above.
[0201] In step 8-30, the USIM 2 terminal (8-03) may notify the USIM 1 terminal (8-02) of the information required to perform the step 8-25 operation in RRC idle mode or RRC deactivation mode. Step 8-30 may follow at least one of steps 5-30, 6-30, and 7-30 described above.
[0202] In step 8-35, the USIM 1 terminal (8-02) may transmit a predetermined RRC message (e.g., a UEAssistanceInformation message) containing configuration information (musim-GapPreferenceList) for one or more preferred MUSIM gap patterns to the base station 1 (8-04). Step 8-35 may follow at least one of steps 5-35, 6-35, and 7-35 described above. Additionally, if the terminal desires to set a specific periodic MUSIM gap to the highest gap priority, the terminal may store information indicating the gap priority for the periodic MUSIM gap to be 'highest' in the musim-GapPreferenceList. Alternatively, if the terminal wants to set a specific periodic MUSIM gap to the lowest gap priority, the terminal can store information indicating the gap priority for the periodic MUSIM gap to be 'lowest' in the musim-GapPreferenceList.
[0203] In step 8-40, the base station 1 (8-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing one or more MUSIM gap configurations (musim-GapConfig)(s) based on the musim-GapPreferenceList requested by the USIM 1 terminal (8-02) in response to step 8-35. Step 8-40 may follow at least one of steps 5-40, 6-40, and 7-40 described above. Additionally, if the base station receives a preferred gap priority indicated as 'lowest' for a specific periodic MUSIM gap from the terminal, the base station may set GapPriority-r17 to the largest integer value, or to a specific integer value or higher, or to a value that is always higher than Type-2 MG, or may not set GapPriority-t17 when configuring the periodic MUSIM gap. Alternatively, if the base station receives a preferred gap priority indicated as 'highest' for a specific periodic MUSIM gap from the terminal, the base station may set GapPriority-r17 to the smallest integer value, or to a value lower than a specific integer value, or to a value that is always lower than that of Type-2 MG when setting the periodic MUSIM gap.
[0204] In step 8-45, the USIM 1 terminal (8-02) may transmit a predetermined RRC message to the base station 1 (8-04) in response to the predetermined RRC message received in step 8-40. For example, the predetermined RRC message may mean RRCReconfigurationComplete.
[0205] In step 8-50, base station 1 (8-04) can transmit a predetermined RRC message (e.g., RRCReconfiguration message) containing measurement gap configuration information (MeasGapConfig) to USIM 1 terminal (8-02). The measurement gap has been described in the description of FIG. 6. One or more gap configurations (GapConfig-r17 IE)(s) can be stored in the MeasGapConfig. In addition, the predetermined RRC message (e.g., RRCReconfiguration message) containing the MeasGapConfig is not restricted to the order shown in this drawing. For example, the message in step 8-50 can be transmitted before the message in step 8-40 is transmitted. In addition, base station 1 (8-04) can transmit one message (e.g., RRCReconfiguration message) containing both musim-GapConfig and MeasGapConfig.
[0206] Specifically, GapConfig-r17 can have an ASN.1 structure as shown in Table 8 below.
[0207] GapConfig-r17 ::= SEQUENCE {measGapId-r17 MeasGapId-r17,gapType-r17 ENUMERATED {perUE, perFR1, perFR2},gapOffset-r17 INTEGER (0..159),mgl-r17 ENUMERATED {ms1, ms1dot5, ms2, ms3, ms3dot5, ms4, ms5, ms5dot5, ms6, ms10, ms20},mgrp-r17 ENUMERATED {ms20, ms40, ms80, ms160},mgta-r17 ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot75},refServCellIndicator-r17 ENUMERATED {pCell, pSCell, mcg-FR2} OPTIONAL, -- Cond NEDCorNRDCrefFR2-ServCellAsyncCA-r17 ServCellIndex OPTIONAL, -- Cond AsyncCApreConfigInd-r17 ENUMERATED {true} OPTIONAL, -- Need RncsgInd-r17 ENUMERATED {true} OPTIONAL, -- Need RgapAssociationPRS-r17 ENUMERATED {true} OPTIONAL, -- Need RgapSharing-r17 MeasGapSharingScheme OPTIONAL, -- Need RgapPriority-r17 GapPriority-r17 OPTIONAL, -- Need R...}
[0208] In the present disclosure, Type-2 MG means a measurement gap set to GapConfig-r17, and at this time, Type-2 MG may mean that preConfigInd-r17 and ncsgInd-r17 are not set to true. In the present disclosure, the base station may set GapPriority-r17 for Type-2 MG. Here, when setting the gap priority for Type-2 MG, the base station may set a gap priority lower than the gap priority of the periodic MUSIM gap indicating 'highest'. The terminal may send a gap priority value other than 'highest' for the periodic MUSIM gap to the base station, and if the gap priority for Type-2 MG is higher, send UEAssistanceInformation to the base station so that the priority value of the periodic MUSIM gap may be set to be changed.
[0209] At step 8-55, the USIM 1 terminal (8-02) can determine whether the set Type-2 MG and the periodic MUSIM gap overlap or collide on the time axis.
[0210] In step 8-60, if the USIM 1 terminal (8-02) wants to apply the periodic MUSIM gap even though the gap priority of the periodic MUSIM gap is lower than that of the Type-2 MG, it can transmit a UEAssistanceInformation message to the base station 1 (8-04). In the present disclosure, the terminal can transmit the UEAssistanceInformation message to the base station (8-04) including an indicator requesting that the gap priority preference for the periodic MUSIM gap be set higher than that of the colliding Type-2 MG with information indicating the highest.
[0211] In step 8-65, the base station 1 (8-04) can transmit an RRC Reconfiguration message containing the changed musim-GapConfig to the USIM 1 terminal (8-02). Based on step 8-60, the base station can set the value of GapPriority-r17 of the periodic MUSIM gap to be lower than that of the Type-2 MG. Alternatively, the base station can release or modify the Type-2 MG. As a result, the USIM 1 terminal (8-02) can apply / use the periodic MUSIM gap with priority over the Type-2 MG.
[0212] FIG. 9 is a block diagram illustrating the internal structure of a terminal according to an embodiment of the present invention.
[0213] Referring to the above drawing, the terminal includes an RF (Radio Frequency) processing unit (9-10), a baseband processing unit (9-20), a storage unit (9-30), and a control unit (9-40).
[0214] The RF processing unit (9-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (9-10) up-converts the baseband signal provided from the baseband processing unit (9-20) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (9-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), etc. In the drawing, only one antenna is shown, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (9-10) may include multiple RF chains. Furthermore, the RF processing unit (9-10) may perform beamforming. For the above beamforming, the RF processing unit (9-10) can adjust the phase and size of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit can perform MIMO, and can receive multiple layers when performing the MIMO operation.
[0215] The baseband processing unit (9-20) above performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (9-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (9-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (9-10). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (9-20) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processing unit (9-20) divides the baseband signal provided from the RF processing unit (9-10) into OFDM symbol units, restores signals mapped to subcarriers through FFT (fast Fourier transform), and then restores the received bit string through demodulation and decoding.
[0216] The baseband processing unit (9-20) and the RF processing unit (9-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (9-20) and the RF processing unit (9-10) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (9-20) and the RF processing unit (9-10) may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processing unit (9-20) and the RF processing unit (9-10) may include different communication modules 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), etc. Additionally, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band and a millimeter wave (mm wave) (e.g., 60GHz) band.
[0217] The storage unit (9-30) stores data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (9-30) can store information related to a second access node that performs wireless communication using a second wireless access technology. In addition, the storage unit (9-30) provides the stored data at the request of the control unit (9-40).
[0218] The control unit (9-40) controls the overall operations of the terminal. The control unit (9-40) can control the terminal to perform at least one or a combination of the methods corresponding to the above-described embodiments. For example, the control unit (9-40) transmits and receives signals through the baseband processing unit (9-20) and the RF processing unit (9-10). In addition, the control unit (9-40) records and reads data in the storage unit (9-40). For this purpose, the control unit (9-40) can include at least one processor. For example, the control unit (9-40) can include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.
[0219] Figure 10 is a block diagram showing the configuration of an NR base station according to one embodiment of the present invention.
[0220] As shown in the above drawing, the base station is configured to include an RF processing unit (10-10), a baseband processing unit (10-20), a backhaul communication unit (10-30), a storage unit (10-40), and a control unit (10-50).
[0221] The RF processing unit (10-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (10-10) up-converts the baseband signal provided from the baseband processing unit (10-20) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (10-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In the drawing, only one antenna is shown, but the first access node may have multiple antennas. In addition, the RF processing unit (10-10) may include multiple RF chains. Furthermore, the RF processing unit (10-10) may perform beamforming. For the above beamforming, the RF processing unit (10-10) can adjust the phase and size of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit can perform a downlink MIMO operation by transmitting one or more layers.
[0222] The baseband processing unit (10-20) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (10-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (10-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (10-10). For example, in the case of OFDM, when transmitting data, the baseband processing unit (10-20) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (10-20) divides the baseband signal provided from the RF processing unit (10-10) into OFDM symbol units, restores the signals mapped to subcarriers through FFT operation, and then restores the received bit string through demodulation and decoding. The baseband processing unit (10-20) and the RF processing unit (10-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (10-20) and the RF processing unit (10-10) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.
[0223] The above backhaul communication unit (10-30) provides an interface for performing communication with other nodes within the network. That is, the backhaul communication unit (10-30) converts a bit string transmitted from the main base station to another node, such as an auxiliary base station or core network, into a physical signal, and converts a physical signal received from the other node into a bit string.
[0224] The storage unit (10-40) stores data such as basic programs, application programs, and setting information for the operation of the main base station. In particular, the storage unit (10-40) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (10-40) can store information that serves as a judgment criterion for whether to provide or terminate multiple connections to a terminal. In addition, the storage unit (10-40) provides the stored data at the request of the control unit (10-50).
[0225] The control unit (10-50) controls the overall operations of the base station. The control unit (10-50) can control the base station to perform at least one or a combination of the methods corresponding to the above-described embodiments. For example, the control unit (10-50) transmits and receives signals through the baseband processing unit (10-20) and the RF processing unit (10-10) or through the backhaul communication unit (10-30). In addition, the control unit (10-50) records and reads data in the storage unit (10-40). For this purpose, the control unit (10-50) can include at least one processor.
[0226] Meanwhile, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples to easily explain the technical content of the present invention and facilitate understanding of the present invention, and are not intended to limit the scope of the present invention. It will be apparent to those skilled in the art that other modifications based on the technical concept of the present invention are possible in addition to the embodiments disclosed herein. Furthermore, the above-described embodiments can be combined and operated as needed.
Claims
1. A method performed by a user equipment (UE) of a wireless communication system, A step of receiving, from a base station, a first radio resource control (RRC) reconfiguration message including information indicating that the UE is allowed to provide multi-universal subscriber identity module (MUSIM) support information for gap priority; and Comprising the step of transmitting, to the base station, a UE support information message including a MUSIM gap priority preference list indicating the MUSIM gap priorities preferred by the UE; A method characterized in that the above MUSIM gap priority preference list includes information expressing the respective priorities for all periodic MUSIM gap preference patterns as integer values.
2. In paragraph 1, A method further comprising the step of transmitting, to the base station, a UE capability information message including information indicating whether the UE supports provision of MUSIM support information including MUSIM gap priority preference.
3. In paragraph 1, A method further comprising the step of receiving, from the base station, a second RRC reconfiguration message including MUSIM gap setting information set based on the UE support information message.
4. In paragraph 1, The above first RRC reset message further includes information indicating the value of a timer associated with reporting of MUSIM gap priority preference, A method characterized in that the UE support information message is transmitted when the timer is not running.
5. A method performed by a base station of a wireless communication system, A step of transmitting a first radio resource control (RRC) reconfiguration message to a user equipment (UE), the first radio resource control (RRC) reconfiguration message including information indicating that the UE is allowed to provide multi-universal subscriber identity module (MUSIM) support information for gap priority; and A step of receiving, from the UE, a UE support information message including a MUSIM gap priority preference list indicating MUSIM gap priorities preferred by the UE, A method characterized in that the above MUSIM gap priority preference list includes information expressing the respective priorities for all periodic MUSIM gap preference patterns as integer values.
6. In paragraph 5, A method further comprising the step of receiving, from the UE, a UE capability information message including information indicating whether the UE supports provision of MUSIM support information including MUSIM gap priority preference.
7. In paragraph 5, A method further comprising the step of transmitting, to the UE, a second RRC reconfiguration message including MUSIM gap setting information set based on the UE support information message.
8. In paragraph 5, The above first RRC reset message further includes information indicating the value of a timer associated with reporting of MUSIM gap priority preference, A method characterized in that the UE support information message is received when the timer is not running.
9. In a user equipment (UE) of a wireless communication system, Transmitter and receiver; and comprising a control unit, said control unit comprising: The UE receives, from the base station through the transceiver, a first radio resource control (RRC) re-establishment message including information indicating that the UE is allowed to provide multi-universal subscriber identity module (MUSIM) support information for gap priority, The UE is configured to transmit, to the base station through the transceiver, a UE support information message including a MUSIM gap priority preference list indicating preferred MUSIM gap priorities of the UE, A UE characterized in that the above MUSIM gap priority preference list includes information expressing the respective priorities for all periodic MUSIM gap preference patterns as integer values.
10. In paragraph 9, A UE characterized in that the control unit is configured to transmit, to the base station through the transceiver, a UE capability information message including information indicating whether the UE supports provision of MUSIM support information including MUSIM gap priority preference.
11. In paragraph 9, The UE is characterized in that the control unit is configured to receive, from the base station through the transceiver, a second RRC reconfiguration message including MUSIM gap setting information set based on the UE support information message.
12. In paragraph 9, The above first RRC reset message further includes information indicating the value of a timer associated with reporting of MUSIM gap priority preference, A UE characterized in that the above UE support information message is transmitted when the timer is not running.
13. In a base station of a wireless communication system, Transmitter and receiver; and comprising a control unit, said control unit comprising: Transmitting to the UE, through the transceiver, a first radio resource control (RRC) re-establishment message including information indicating that the user equipment (UE) is allowed to provide multi-universal subscriber identity module (MUSIM) support information for gap priority, configured to receive from the UE a UE support information message including a MUSIM gap priority preference list indicating the MUSIM gap priorities preferred by the UE; A base station, characterized in that the above MUSIM gap priority preference list includes information expressing the respective priorities for all periodic MUSIM gap preference patterns as integer values.
14. In paragraph 13, A base station, characterized in that the control unit is configured to receive, from the UE through the transceiver, a UE capability information message including information indicating whether the UE supports provision of MUSIM support information including MUSIM gap priority preference.
15. In paragraph 13, The control unit is configured to transmit a second RRC reset message including MUSIM gap setting information set based on the UE support information message to the UE through the transceiver unit, The above first RRC reset message further includes information indicating the value of a timer associated with reporting of MUSIM gap priority preference, A base station, characterized in that the UE support information message is received when the timer is not running.
Citation Information
Patent Citations
Communication Coordination and Collision Mitigation for Multi-Subscriber Identity Module Devices
US20210014822A1
Communication based on plurality of sims
US20220240222A1
Cited By
Configuration request in wireless communications
US12439399B2
Configuration request in wireless communications
US20230224890A1
