Method by which base station simultaneously configures plurality of gaps to terminal in next generation mobile communication system, and device

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. Presented in the present disclosure are a method by which a base station simultaneously configures a plurality of gaps to a terminal in a mobile communication system, and a device.

Description

Method and device for a base station to simultaneously set multiple gaps to a terminal in a next-generation mobile communication system

[0001] The present invention relates to a mobile communication system terminal and base station operation, and more specifically, to a method and device for a base station to simultaneously set multiple gaps to a terminal in a mobile 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] The purpose of the present invention is to provide a method and device for a base station to simultaneously set multiple gaps to a terminal in a mobile communication system.

[0009] The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0010] In order to solve the above problem, a method performed by a terminal of a wireless communication system according to an embodiment of the present invention may include the steps of transmitting a first message including information related to the terminal being able to set a MUSIM (multiple universal subscriber identity module) gap and a concurrent measurement gap together to a base station; and receiving a second message including at least one of setting information of the MUSIM gap and setting information of the concurrent measurement gap from the base station based on the information.

[0011] Depending on the embodiment, the preset measurement gap for positioning may not be set together with the MUSIM gap or the simultaneous measurement gap.

[0012] In an embodiment, information associated with the terminal's ability to set the MUSIM gap and the simultaneous measurement gap together may be associated with information indicating whether the terminal can provide MUSIM assistance information for priority preferences for periodic MUSIM gaps and support periodic MUSIM gap priority setting related thereto and support a preference for maintaining conflicting MUSIM gaps.

[0013] According to an embodiment, information related to the terminal being able to set the MUSIM gap and the simultaneous measurement gap together may be indicated as musim-GapPriorityPreference information.

[0014] According to an embodiment, the method may further include: setting up at least one periodic MUSIM gap setting when the setting information of the MUSIM gap includes information for adding at least one periodic MUSIM gap; setting up an aperiodic MUSIM gap setting when the setting information of the MUSIM gap includes information for adding an aperiodic MUSIM gap; and maintaining all conflicting MUSIM gaps when information indicating that the terminal is allowed to maintain both conflicting MUSIM periodic and aperiodic gaps is set according to the setting information of the MUSIM gap.

[0015] In some embodiments, the information associated with the terminal being able to set the MUSIM gap and the simultaneous measurement gap together may further indicate that the terminal prefers to maintain all conflicting MUSIM gaps.

[0016] In addition, a method performed by a base station of a wireless communication system according to an embodiment of the present invention for solving the above-described problem may include the steps of: receiving, from a terminal, a first message including information related to the terminal being able to set a multiple universal subscriber identity module (MUSIM) gap and a concurrent measurement gap together; and transmitting, based on the information, a second message including at least one of setting information of the MUSIM gap and setting information of the concurrent measurement gap to the terminal.

[0017] According to an embodiment, the MUSIM gap configuration information may include information for adding at least one periodic MUSIM gap, information for adding an aperiodic MUSIM gap, and information indicating that the terminal is allowed to maintain both conflicting MUSIM periodic and aperiodic gaps.

[0018] According to an embodiment, at least one periodic MUSIM gap setting is set up, an aperiodic MUSIM gap setting is set up, and all conflicting MUSIM gaps can be maintained according to the setting information of the MUSIM gap.

[0019] In addition, a terminal of a wireless communication system according to an embodiment of the present invention for solving the above-described problem may include a transceiver; and a control unit connected to the transceiver, the terminal transmitting a first message including information related to the terminal being able to set a MUSIM (multiple universal subscriber identity module) gap and a concurrent measurement gap together to a base station, and receiving a second message including at least one of setting information of the MUSIM gap and setting information of the concurrent measurement gap from the base station based on the information.

[0020] In addition, a base station of a wireless communication system according to an embodiment of the present invention for solving the above-described problem may include a transceiver; and a control unit connected to the transceiver, receiving from a terminal a first message including information related to the terminal being able to set a MUSIM (multiple universal subscriber identity module) gap and a concurrent measurement gap together, and transmitting to the terminal a second message including at least one of setting information of the MUSIM gap and setting information of the concurrent measurement gap based on the information.

[0021] One embodiment of the present invention can provide a method and device for a base station to simultaneously set multiple gaps to a terminal in a mobile communication system.

[0022] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0023] FIG. 1a is a diagram illustrating the structure of an LTE system according to an embodiment of the present invention.

[0024] FIG. 1b is a diagram illustrating a wireless protocol structure in an LTE system according to an embodiment of the present invention.

[0025] FIG. 1c is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present invention.

[0026] FIG. 1d is a diagram illustrating a wireless protocol structure of a next-generation mobile communication system according to an embodiment of the present invention.

[0027] FIG. 1e is an example of a flowchart of operations in which a terminal supporting one or more independent gap features receives a gap from a base station according to an embodiment of the present invention.

[0028] FIG. 1f is an example of a flowchart of operations in which a terminal supporting one or more independent gap features receives a gap from a base station according to another embodiment of the present invention.

[0029] FIG. 1g is an example of a flowchart of operations in which a terminal supporting one or more independent gap features receives a gap from a base station according to another embodiment of the present invention.

[0030] FIG. 1h is an example of a flowchart of operations in which a terminal supporting one or more independent gap features receives a gap from a base station according to another embodiment of the present invention.

[0031] FIG. 1i is an example of a flowchart of operations in which a terminal supporting one or more independent gap features receives a gap from a base station according to another embodiment of the present invention.

[0032] FIG. 1J is an example of a flowchart for processing colliding MUSIM gaps by a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple USIMs (universal subscriber identity modules) according to an embodiment of the present invention.

[0033] FIG. 1k is an example of a flowchart for processing conflicting MUSIM gaps by a terminal (MUSIM UE) supporting multiple USIMs according to another embodiment of the present invention.

[0034] FIG. 1l is a block diagram illustrating the internal structure of a terminal according to an embodiment of the present invention.

[0035] Figure 1m is a block diagram showing the configuration of an NR base station according to one embodiment of the present invention.

[0036] 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.

[0037] 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.

[0038] The operating principles of the present invention are described in detail with reference to the attached diagram. The terms described below are defined based on their functions within the present invention. These terms may vary depending on the intent or custom of the user or operator, and therefore their definitions should be determined based on the overall content of this specification.

[0039] 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.

[0040] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure 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 is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the disclosure.

[0041] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings 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 flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable storage medium that can direct a computer or other programmable data processing equipment to implement the function in a specific manner, so that the instructions stored in the computer-available or computer-readable storage medium can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart 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).

[0042] 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.

[0043] Here, the term '~ unit' used in this 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 regenerate one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, 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'. In addition, the components and '~ units' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card.

[0044] Certain terms used in the following description are provided to aid in understanding the present disclosure, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present disclosure.

[0045] 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.

[0046] 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.

[0047] FIG. 1a is a diagram illustrating the structure of an LTE system according to an embodiment of the present invention.

[0048] Referring to FIG. 1a, as illustrated, a wireless access network of an LTE system may be composed of next-generation base stations (Evolved Node Bs, hereinafter referred to as ENBs, eNBs, Node Bs or base stations) (1a-05, 1a-10, 1a-15, 1a-20), an MME (1a-25, mobility management entity) and an S-GW (1a-30, serving-gateway). A user equipment (hereinafter referred to as UE or terminal) (1a-35) may access an external network through the ENBs (1a-05 to 1a-20) and the S-GW (1a-30).

[0049] In Fig. 1a, ENBs (1a-05 to 1a-20) correspond to existing Node Bs of the UMTS system. ENBs (1a-05 to 1a-20) are connected to UEs (1a-35) via a wireless channel and perform a more complex role than existing Node Bs. 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 buffer status, available transmission power status, and channel status of UEs (1a-35) and performs scheduling is required, and this is handled by ENBs (1a-05 to 1a-20). One ENB (1a-05 to 1a-20) 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 an adaptive modulation & coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel condition of the terminal (1a-35). The S-GW (1a-30) is a device that provides a data bearer and creates or removes a data bearer according to the control of the MME (1a-25). The MME (1a-25) is a device that is responsible for various control functions as well as mobility management functions for the terminal (1a-35) and is connected to a number of base stations (1a-05 to 1a-20).

[0050] FIG. 1b is a diagram illustrating a wireless protocol structure in an LTE system according to an embodiment of the present invention.

[0051] Referring to Fig. 1b, the wireless protocol of the LTE system consists of PDCP (packet data convergence protocol, 1b-05, 1b-40), RLC (radio link control, 1b-10, 1b-35), and MAC (medium access control, 1b-15, 1b-30) in the terminal and ENB, respectively.

[0052] PDCP (1b-05, 1b-40) is responsible for operations such as IP header compression / decompression. The main functions of PDCP (1b-05, 1b-40) are summarized as follows.

[0053] - Header compression and decompression (ROHC only)

[0054] - User data transfer function

[0055] - In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM

[0056] - Order reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0057] - Duplicate detection function (Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

[0058] - 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)

[0059] - Encryption and decryption functions (Ciphering and deciphering)

[0060] - Timer-based SDU discard in uplink.

[0061] Radio Link Control (RLC) (1b-10, 1b-35) reconfigures PDCP packet data units (PDUs) into appropriate sizes and performs ARQ operations, etc. The main functions of RLC (1b-10, 1b-35) are summarized as follows.

[0062] - Data transfer function (Transfer of upper layer PDUs)

[0063] - ARQ function (Error Correction through ARQ (only for AM data transfer))

[0064] - Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer)

[0065] - Re-segmentation of RLC data PDUs (only for AM data transfer)

[0066] - Reordering of RLC data PDUs (only for UM and AM data transfer)

[0067] - Duplicate detection (only for UM and AM data transfer)

[0068] - Error detection function (Protocol error detection (only for AM data transfer))

[0069] - RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))

[0070] - RLC re-establishment function

[0071] MAC(1b-15, 1b-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(1b-15, 1b-30) are summarized as follows.

[0072] - Mapping function (Mapping between logical channels and transport channels)

[0073] - 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)

[0074] - Scheduling information reporting function

[0075] - HARQ function (Error correction through HARQ)

[0076] - Priority handling between logical channels of one UE

[0077] - Priority handling between UEs by means of dynamic scheduling

[0078] - MBMS service identification function

[0079] - Transport format selection function

[0080] - Padding function

[0081] The physical layer (1b-20, 1b-25) performs the operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it over a wireless channel, or demodulating and channel decoding OFDM symbols received over a wireless channel and transmitting them to the upper layer.

[0082] FIG. 1c is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present invention.

[0083] Referring to FIG. 1c, as illustrated, a wireless access network of a next-generation mobile communication system (hereinafter referred to as NR or 5g) is composed of a next-generation base station (new radio node B, hereinafter referred to as NR gNB, gNB or NR base station) (1c-10) and an NR CN (1c-05, new radio core network). A user terminal (new radio user equipment, hereinafter referred to as NR UE or terminal) (1c-15) accesses an external network through the NR gNB (1c-10) and the NR CN (1c-05).

[0084] In Fig. 1c, the NR gNB (1c-10) corresponds to the eNB (Evolved Node B) of the existing LTE system. The NR gNB (1c-10) is connected to the NR UE (1c-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 buffer status, available transmission power status, and channel status of the UEs (1c-15) and performs scheduling is required, and the NR NB (1c-10) is responsible for this. One NR gNB (1c-10) typically controls multiple cells. The next-generation mobile communication system may have a bandwidth exceeding the existing maximum bandwidth in order to implement ultra-high-speed data transmission compared to the current LTE, and may additionally incorporate beamforming technology by using orthogonal frequency division multiplexing (OFDM) as a wireless access technology. In addition, the next-generation mobile communication system applies an adaptive modulation & coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel condition of the terminal (1c-15). The NR CN (1c-05) performs functions such as mobility support, bearer setup, and QoS setup. The NR CN (1c-05) is a device that is responsible for various control functions as well as mobility management functions for the terminal (1c-15) and is connected to a number of base stations (1c-10). In addition, the next-generation mobile communication system can also be linked with the existing LTE system, and the NR CN (1c-05) can be connected to the MME (1c-25) through a network interface. The MME (1c-25) can be connected to the existing base station, eNB (1c-30).

[0085] FIG. 1d is a diagram illustrating a wireless protocol structure of a next-generation mobile communication system according to an embodiment of the present invention.

[0086] FIG. 1d is a diagram showing the wireless protocol structure of a next-generation mobile communication system to which the present invention can be applied.

[0087] Referring to FIG. 1d, the wireless protocol of the next-generation mobile communication system consists of NR SDAP (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), NR RLC (1d-10, 1d-35), and NR MAC (1d-15, 1d-30) in the terminal and NR base station, respectively.

[0088] Key features of NR SDAP (1d-01, 1d-45) may include some of the following:

[0089] - Transfer of user plane data

[0090] - Mapping function between QoS flow and data bearer for both DL and UL

[0091] - QoS flow ID marking function for uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0092] - Ability to map relective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0093] 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.

[0094] The main functions of NR PDCP (1d-05, 1d-40) may include some of the following functions:

[0095] Header compression and decompression (ROHC only)

[0096] - User data transfer function

[0097] - In-sequence delivery of upper layer PDUs

[0098] - Out-of-sequence delivery of upper layer PDUs

[0099] - PDCP PDU reordering for reception

[0100] - Duplicate detection of lower layer SDUs

[0101] - Retransmission function (Retransmission of PDCP SDUs)

[0102] - Encryption and decryption functions (Ciphering and deciphering)

[0103] - Timer-based SDU discard in uplink.

[0104] 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.

[0105] The main features of NR RLC(1d-10, 1d-35) may include some of the following:

[0106] - Data transfer function (Transfer of upper layer PDUs)

[0107] - In-sequence delivery of upper layer PDUs

[0108] - Out-of-sequence delivery of upper layer PDUs

[0109] - ARQ function (Error Correction through ARQ)

[0110] - Concatenation, segmentation and reassembly of RLC SDUs

[0111] - Re-segmentation of RLC data PDUs

[0112] - Reordering of RLC data PDUs

[0113] - Duplicate detection function

[0114] - Protocol error detection

[0115] - RLC SDU discard function

[0116] - RLC re-establishment function

[0117] 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.

[0118] 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.

[0119] NR MAC (1d-15, 1d-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.

[0120] - Mapping function (Mapping between logical channels and transport channels)

[0121] - Multiplexing / demultiplexing of MAC SDUs

[0122] - Scheduling information reporting function

[0123] - HARQ function (Error correction through HARQ)

[0124] - Priority handling between logical channels of one UE

[0125] - Priority handling between UEs by means of dynamic scheduling

[0126] - MBMS service identification function

[0127] - Transport format selection function

[0128] - Padding function

[0129] The NR PHY layer (1d-20, 1d-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.

[0130] FIG. 1e is an example of a flowchart of operations in which a terminal supporting one or more independent gap features receives a gap from a base station according to an embodiment of the present invention.

[0131] Referring to FIG. 1e, at step 1e-15, a terminal (UE) (1e-05) may establish an RRC connection with a base station (e.g., gNB) (1e-10) and be in an RRC connected mode (RRC connected state).

[0132] At step 1e-20, the terminal (1e-05) may transmit a terminal capability information (e.g., UECapabilityInformation) message to the base station (1e-10). The message may include at least one of the following:

[0133] - independentGapConfig

[0134] ■ IndependentGapConfig indicates whether the UE supports two independent measurement gap configurations for FR1 (frequency range 1) and FR2 (frequency range 2) as described in clause 9.1.2 of TS 38.133.

[0135] ■ The above terminal capability indicator is signaled for each terminal, and there is no functional difference between FDD (frequency division duplexing) and TDD (time division duplexing), and no functional difference between FR1 and FR2.

[0136] ■ The above terminal capability indicator may also indicate whether the UE supports the FR2 inter-RAT measurement without gaps when (NG)EN-DC is not configured (independentGapConfig also indicates whether the UE supports the FR2 inter-RAT measurement without gaps when (NG)EN-DC is not configured).

[0137] - musim-GapPreference

[0138] ■ musim-GapPreference indicates whether the UE supports providing MUSIM assistance information with MUSIM gap preference and related MUSIM gap configuration, as defined in Technical Specification (TS) 38.331.

[0139] ■ The above terminal capability indicator is signaled for each terminal, there is no functional difference between FDD and TDD, and there is no functional difference between FR1 and FR2.

[0140] ■ A UE supporting this feature supports 3 periodic gaps and 1 aperiodic gap.

[0141] - concurrentMeasGap

[0142] ■ ConcurrentMeasGap indicates whether the UE supports the concurrent measurements gaps as specified in TS 38.133.

[0143] ■ The above terminal capability indicator is signaled for each terminal, there is no functional difference between FDD and TDD, and there is no functional difference between FR1 and FR2.

[0144] ■ The capability signaling for the terminal capability indicator may be composed of at least one of the following parameters (The capability signaling comprises the following parameters), and may be signaled with one of the two.

[0145] ◆ concurrentPerUE-OnlyMeasGap

[0146] ● ConcurrentPerUE-OnlyMeasGap indicates whether the UE supports more than 1 per-UE measurement gap configurations (i.e. gap combination configuration id = 2 as specified in TS 38.133)

[0147] ◆ concurrentPerUE-PerFRCombMeasGap

[0148] ● ConcurrentPerUE-PerFRCombMeasGap indicates whether the UE supports all concurrent gap combination configurations as specified in TS 38.133 including support of more than 1 per-UE measurement gap configurations.

[0149] ● For a UE capable of per-FR gap (independentGapConfig), this field indicates whether the UE supports more than 1 per-FR gap measurement gap configurations in an FR, or simultaneous 1 per UE measurement gap plus 1 per-FR measurement gap configurations in an FR, or more than 1 per-UE measurement gap configurations (i.e. gap combination configuration id = 2 as specified in TS 38.133).

[0150] - mg-ActivationCommPRS-Meas

[0151] ■ mg-ActivationCommPRS-Meas indicates whether UE supports preconfiguration of MGs in RRC signaling for PRS measurements and the use of DL MAC CE from the gNB, as specified in TS 38.321, to activate / deactivate the preconfigured MG for PRS measurements.

[0152] ■ The above terminal capability indicator is signaled for each terminal, there is no functional difference between FDD and TDD, and there is no functional difference between FR1 and FR2.

[0153] -mg-ActivationRequestPRS-Meas

[0154] ■ mg-ActivationRequestPRS-Meas indicates whether the UE supports preconfiguration of MGs in RRC signaling for PRS measurements and supports the use of UL MAC CE, as specified in TS38.321 [8], to request the activation / deactivation of the preconfigured MG for PRS measurements.

[0155] ■ The above terminal capability indicator is signaled for each terminal, there is no functional difference between FDD and TDD, and there is no functional difference between FR1 and FR2.

[0156] ■ The terminal capability indicator (mg-ActivationRequestPRS-Meas) can be signaled only for terminals that support the aforementioned mg-ActivationCommPRS-Meas.

[0157] At step 1e-25, the base station (1e-10) may transmit to the terminal (1e-05) a predetermined RRC message (e.g., RRCResume or RRCReconfiguration) containing gap configuration information (one single gap feature, configuration information for one single gap capability) for one or more gap capabilities supported by the terminal (1e-05). In the above, the gap capability may mean one of the following:

[0158] - Terminals that support musim-GapPreference support "MUSIM gap capability"

[0159] - A terminal that supports mg-ActivationCommPRS-Meas or supports mg-ActivationCommPRS-Meas and mg-ActivationRequestPRS-Meas has the ability to "pre-configure a measurement gap for positioning purposes and use it through a MAC (medium access control) CE (control element)."

[0160] - Terminals that support concurrentMeasGap support "concurrent measurement gap capability".

[0161] ■ As mentioned above, concurrentMeasGap support means either concurrentPerUE-OnlyMeasGap or concurrentPerUE-PerFRCombMeasGap.

[0162] The gap setting information for one gap capability above may mean one of the following:

[0163] - MUSIM gap configuration information (MUSIM-GapConfig)

[0164] ■ The specific ASN.1 structure and description of each field for MUSIM gap setting may be as follows.

[0165] -MUSIM-GapConfig

[0166] The IEMUSIM-GapConfigspecifies the MUSIM gap configuration and controls setup / release of MUSIM gaps.

[0167] MUSIM-GapConfiginformation element

[0168] -- ASN1START-- TAG-MUSIM-GAPCONFIG-STARTMUSIM-GapConfig-r17 ::= SEQUENCE {musim-GapToReleaseList-r17 SEQUENCE (SIZE (1..3)) OF MUSIM-GapId-r17 OPTIONAL, -- Need N musim-GapToAddModList-r17 SEQUENCE (SIZE (1..3)) OF MUSIM-Gap-r17 OPTIONAL, -- Need N musim-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-SEASON-GAPCONFIG-STOP-- ASN1STOP

[0169] MUSIM-GapConfig field descriptionsmusim-AperiodicGapIndicates the MUSIM aperiodic gap as specified in TS 38.133

[0014] clause 9.1.10. If UE indicates the musim-Starting-SFN-AndSubframe when requesting aperiodic gap the network can only configure the aperiodic gap with the same start point or no aperiodic gap. If the field musim-Starting-SFN-AndSubframe is 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 for musim-GapLength and musim-GapRepetitionAndOffset. When network provides periodic gap, network always signals the musim-GapLength and musim-GapRepetitionAndOffset as 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.

[0170] -MUSIM-GapInfo

[0171] The IEMUSIM-GapInfois used to indicate MUSIM gap parameters.

[0172] MUSIM-GapInfoinformation element

[0173] -- 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-- ASN1STOP

[0174] MUSIM-GapInfo field descriptionsmusim-GapLengthIndicates the length of the UE's MUSIM gap as specified in TS 38.133

[0014] 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

[0014] 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.

[0175] 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.

[0176] - Pre-configured measurement gap settings for positioning purposes (posMeasGapPreConfigToAddModList)

[0177] ■ The specific ASN.1 structure and description of each field for the preset measurement gap for positioning purposes may be as follows.

[0178] PosMeasGapPreConfigToAddModList-r17 ::= SEQUENCE (SIZE (1..maxNrofPreConfigPosGapId-r17)) OF PosGapConfig-r17PosGapConfig-r17 ::= SEQUENCE {measPosPreConfigGapId-r17 MeasPosPreConfigGapId-r17,gapOffset-r17 INTEGER (0..159),mgl-r17 ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6, ms10, ms20},mgrp-r17 ENUMERATED {ms20, ms40, ms80, ms160},mgta-r17 ENUMERATED {ms0, ms0dot25, ms0dot5},gapType-r17 ENUMERATED {perUE, perFR1, perFR2},...}MeasPosPreConfigGapId-r17 ::= INTEGER (1..maxNrofPreConfigPosGapId-r17)

[0179] gapOffsetValue gapOffset is the gap offset of the gap pattern with MGRP indicated in the field mgrp. The value range is from 0 to mgrp-1. If ncsgInd-r17 is present, this offset value refers to the starting point of VIL1 (the visible interruption length before the ML).gapTypeIndicates the type of this measurement gap. Value perUE indicates that it is a per UE measurement gap, value perFR1 indicates that it is an FR1 measurement gap, and value perFR2 indicates that it is an FR2 measurement gap.mglValue mgl is the measurement gap length in ms of the measurement gap. If ncsgInd-r17 is not present, the measurement gap length is according to in Table 9.1.2-1 in TS 38.133

[0014] . If ncsgInd-r17 is present, this field indicates the measurement length (ML) in NCSG pattern and is configured according to Table 9.1.9.3-1 in TS 38.133

[0014] . Value ms1dot5 corresponds to 1.5 ms, ms3 corresponds to 3 ms and so on. If mgl-r16 is present, UE shall ignore the mgl (without suffix).Value ms1, ms2, and ms5 can only be configured if ncsgInd is present.mgrpIf ncsgInd-r17 is not present, the mgrp field indicates the measurement gap repetition period in (ms) of the measurement gap according to Table 9.1.2-1 in TS 38.133

[0014] . If ncsgInd-r17 is present, the mgrp field indicates the Visible Interruption Repetition Period (VIRP) of NCSG pattern and is configured according to Table 9.1.9.3-1 in TS 38.133

[0014] .mgtaValue mgta is the measurement gap timing advance in ms. The applicability of the measurement gap timing advance is according to clause 9.1.2 of TS 38.133

[0014] , or according to clause 9.1.9 of TS 38.133

[0014] if ncsgInd is present. Value ms0 corresponds to 0 ms, ms0dot25 corresponds to 0.25 ms, ms0dot5 corresponds to 0.5 ms and ms0dot75 corresponds to 0.75 ms. For FR2, the network only configures 0 ms and 0.25 ms if ncsgInd is not present. If ncsgInd is present, the network only configures 0ms for per-UE NCSG and FR1 NCSG and only configures 0ms or 0.75ms for FR2 NCSG. Value ms0dot75 can only be configured if ncsgInd is present.posMeasGapPreConfigToAddModListList of preconfigured measurement gap for positioning to add and / or modify. All the gaps configured are associated with the measurement of PRS for RSTD, UE-RxTx Time Difference, PRS-RSRP and PRS-RSRPP as defined in TS 38.215 [9]. In this version of the specification, the network does not configure preconfigured measurement gap for positioning together with concurrent measurement gap or MUSIM gap.preConfigIndIndicates whether the measurement gap is a pre-configured measurement gap.

[0180] - Concurrent 측정 갭 설정 정보(gapToAddModList)

[0181] ■ Concurrent measurement gap에 대한 구체적인 ASN.1 구조 및 각 필드에 대한 설명은 하기와 같을 수 있다.

[0182] MeasGapConfig ::= SEQUENCE {gapFR2 SetupRelease { GapConfig} OPTIONAL, -- Need M...,[[gapFR1 SetupRelease { GapConfig} OPTIONAL, -- Need MgapUE SetupRelease { GapConfig} OPTIONAL -- Need M]],[[gapToAddModList-r17 SEQUENCE (SIZE (1..maxNrofGapId-r17)) OF GapConfig-r17 OPTIONAL, -- Need N}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...}.

[0183] MeasGapConfig field descriptionsgapAssociationPRSIndicates that PRS measurement is associated with this measurement gap. The network only includes this field for one per-UE gap or for one per-FR gap. If concurrent gap (i.e. one of the gap combination as defined in Table 9.1.8-1 in TS 38.133

[0014] ) is configured and no gap is configured with this field, the PRS measurement is associated with the gap configured via GapConfig (without suffix), if available. If both per-UE gap and per-FR gap are configured via GapConfig and / or GapConfig-r17, the PRS measurement is always associated with the per-UE gap.gapOffsetValue gapOffset is the gap offset of the gap pattern with MGRP indicated in the field mgrp. The value range is from 0 to mgrp-1. If ncsgInd-r17 is present, this offset value refers to the starting point of VIL1 (the visible interruption length before the ML).gapPriorityIndicates the priority of this measurement gap (see TS 38.133

[0014] , clause 9.1.8.3).Value 1 indicates highest priority, value 2 indicates second level priority, and so on.gapSharingIndicates the measurement gap sharing scheme that applies to this GapConfig. For applicability of the different gap sharing schemes, see TS 38.133

[0014] . Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on.gapToAddModListA list of of measurement gap configuration to be added or modified. If more than one measurement gap is configured (i.e. concurrent measurement gap as specified in TS 38.133

[0014] , clause 9.1.8), the maximum number of configured measurement gap is limited by the gap combinations defined in Table 9.1.8-1 in TS 38.133

[0014] . The network configures at most one NCSG or pre-configured measurement gap for a given gap type. In this version of the specification, the network configures this field only in NR standalone. This field is used only for a UE that supports pre-configured measurement gap, concurrent measurement gap, or NCSG.In this version of the specification, the network does not configure concurrent measurement gap together with MUSIM gap or preconfigured measurement gap for positioning.gapTypeIndicates the type of this measurement gap. Value perUE indicates that it is a per UE measurement gap, value perFR1 indicates that it is an FR1 measurement gap, and value perFR2 indicates that it is an FR2 measurement gap.measGapIdThe ID of this measurement gap configuration.mglValue mgl is the measurement gap length in ms of the measurement gap. If ncsgInd-r17 is not present, the measurement gap length is according to in Table 9.1.2-1 in TS 38.133

[0014] . If ncsgInd-r17 is present, this field indicates the measurement length (ML) in NCSG pattern and is configured according to Table 9.1.9.3-1 in TS 38.133

[0014] . Value ms1dot5 corresponds to 1.5 ms, ms3 corresponds to 3 ms and so on. If mgl-r16 is present, UE shall ignore the mgl (without suffix).Value ms1, ms2, and ms5 can only be configured if ncsgInd is present.mgrpIf ncsgInd-r17 is not present, the mgrp field indicates the measurement gap repetition period in (ms) of the measurement gap according to Table 9.1.2-1 in TS 38.133

[0014] . If ncsgInd-r17 is present, the mgrp field indicates the Visible Interruption Repetition Period (VIRP) of NCSG pattern and is configured according to Table 9.1.9.3-1 in TS 38.133

[0014] .mgtaValue mgta is the measurement gap timing advance in ms. The applicability of the measurement gap timing advance is according to clause 9.1.2 of TS 38.133

[0014] , or according to clause 9.1.9 of TS 38.133

[0014] if ncsgInd is present. Value ms0 corresponds to 0 ms, ms0dot25 corresponds to 0.25 ms, ms0dot5 corresponds to 0.5 ms and ms0dot75 corresponds to 0.75 ms. For FR2, the network only configures 0 ms and 0.25 ms if ncsgInd is not present. If ncsgInd is present, the network only configures 0ms for per-UE NCSG and FR1 NCSG and only configures 0ms or 0.75ms for FR2 NCSG. Value ms0dot75 can only be configured if ncsgInd is present.ncsgIndIndicates that the measurement gap is a NCSG as specified in 38.133

[0014] .refFR2ServCellAsyncCAIndicates the FR2 serving cell identifier whose SFN and subframe is used for FR2 gap calculation for this gap pattern with asynchronous CA involving FR2 carrier(s).refServCellIndicatorIndicates the serving cell whose SFN and subframe are used for gap calculation for this gap pattern. Value pCell corresponds to the PCell, pSCell corresponds to the PSCell, and mcg-FR2 corresponds to a serving cell on FR2 frequency in MCG.

[0184] A terminal (1e-05) according to the present disclosure has the characteristic of supporting one or more independent gap capabilities. Specifically, each independent gap capability may mean at least one of the following:

[0185] - Ability to set and use a MUSIM gap from a base station (1e-10)

[0186] - Ability to receive a preconfigured measurement gap for positioning from a base station (1e-10) and use it later by activating / deactivating it with MAC CE.

[0187] - Ability to set and use concurrent measurement gaps from base stations (1e-10).

[0188] A base station (1e-10) according to the present disclosure has a feature of setting a gap for one gap capability to a terminal (1e-05) supporting one or more independent gap capabilities. Specifically,

[0189] - The base station (1e-10) does not configure a MUSIM gap together with a concurrent measurement gap or a preconfigured measurement gap for positioning purposes. That is, the base station (1e-10) has a characteristic of not configuring a concurrent measurement gap or a preconfigured measurement gap for positioning purposes for a terminal (1e-05) for which a MUSIM gap is configured.

[0190] - The base station (1e-10) does not configure a preconfigured measurement gap for positioning together with a concurrent measurement gap or MUSIM gap. That is, the base station (1e-10) has a characteristic of not configuring a concurrent measurement gap and a MUSIM gap for a terminal (1e-05) for which a preconfigured measurement gap for positioning purposes has been set.

[0191] - The base station (1e-10) does not configure concurrent measurement gap together with the MUSIM gap or preconfigured measurement gap for positioning. That is, the base station (1e-10) has a characteristic of not configuring the MUSIM gap and the preconfigured measurement gap for positioning to the terminal (1e-05) for which the concurrent measurement gap is configured.

[0192] FIG. 1f is an example of a flowchart of operations in which a terminal supporting one or more independent gap features receives a gap from a base station according to another embodiment of the present invention.

[0193] Referring to FIG. 1f, in step 1f-15, the terminal (1f-05) may establish an RRC connection with the base station (1f-10) and be in an RRC connection mode (RRC connection state).

[0194] In step 1f-20, the terminal (1f-05) may transmit a terminal capability information (e.g., UECapabilityInformation) message to the base station (1f-10). The terminal capability information included in the message may follow the aforementioned embodiment (Fig. 1e). Additionally, in the present embodiment, the message may include the following information:

[0195] - jointConcurrentMG-MUSIM-Gap

[0196] ■ It may mean a terminal capability indicator indicating whether it supports joint configurations of concurrent measurement gap (MG) and MUSIM gap. Or it may mean a terminal capability indicator indicating whether it can handle a conflict between configured concurrent measurement gaps and MUSIM gaps (for example, the ability to use a gap with a higher priority and not use (drop) (or delete) a gap with a lower priority, or to use a gap with a long gap repetition period (MGRP) and not use a gap with a lower priority). For reference, the condition for determining that gaps conflict may mean that at least one of the following is satisfied.

[0197] ◆ When gap opportunities are fully or partially overlapping in the time domain

[0198] ◆ When the distance between two gap occasions is equal to or smaller than 4ms

[0199] ● The distance between two gap opportunities is defined as the time difference between the ending point of the first occasion and the starting point of the second occasion, where the first gap occasion occurs earlier in time than the second gap occasion. The gap occasion can be either a MUSIM gap occasion or a measurement gap occasion.

[0200] ■ The above terminal capability indicator is signaled for each terminal, and there is no functional difference between FDD and TDD, and no functional difference between FR1 and FR2.

[0201] - musim-GapPriorityPreference

[0202] ■ musim-GapPriorityPreference indicates whether the UE supports providing MUSIM assistance information with periodic MUSIM gap priority preference and related periodic MUSIM gap priority configuration, and its preference of keeping all collided MUSIM gaps, as defined in TS 38.331.

[0203] ■ The above terminal capability indicator is signaled for each terminal, there is no functional difference between FDD and TDD, and there is no functional difference between FR1 and FR2.

[0204] ■ A terminal supporting the above capability may support the aforementioned musim-GapPreference (UE supporting this feature (musim-GapPriorityPreference) shall support musim-GapPreference).

[0205] ■ A terminal supporting the above capabilities can provide the base station with periodic MUSIM gap preferences and priority preferences thereof as MUSIM auxiliary information.

[0206] ■ For reference, a terminal that supports both the capabilities of musim-GapPriorityPreference and musim-GapPreference and a terminal that supports only the musim-GapPreference capability may only provide MUSIM assistance information for aperiodic MUSIM gap preference to the base station and may not explicitly provide a priority preference value for it to the base station. However, a terminal that supports both the capabilities of musim-GapPriorityPreference and musim-GapPreference has the characteristic of not unnecessarily providing a priority value for aperiodic MUSIM gap to the base station because it prefers aperiodic MUSIM gap with the highest priority, whereas a terminal that supports only the capability of musim-GapPreference has the characteristic of not providing a priority preference value for aperiodic MUSIM gap to the base station (i.e., there is no priority preference value). Accordingly, the base station also sets an aperiodic MUSIM gap without an explicit priority value for a terminal that supports both the capabilities of musim-GapPriorityPreference and musim-GapPreference and a terminal that supports only the musim-GapPreference capability, but sets the highest priority for the aperiodic MUSIM gap for a terminal that supports both the capabilities of musim-GapPriorityPreference and musim-GapPreference, whereas does not set a priority value for the aperiodic MUSIM gap for a terminal that supports only the musim-GapPreference capability.

[0207] At step 1f-25, the base station (1f-10) may transmit to the terminal (1f-05) a predetermined RRC message (e.g., RRCResume or RRCReconfiguration) containing one or more gap configuration information according to predetermined conditions among one or more gap capabilities supported by the terminal (1f-05). Specifically,

[0208] - If the base station (1f-10) sets a preset measurement gap for positioning purposes to the terminal (1f-05), the base station (1f-10) does not set a simultaneous measurement gap and a MUSIM gap to the terminal (1f-05). That is, the base station (1f-10) has a characteristic of not setting a simultaneous measurement gap and a MUSIM gap to the terminal (1f-05) for which a preset measurement gap for positioning purposes has been set.

[0209] - If the base station (1f-10) does not set a preset measurement gap for positioning purposes to the terminal (1f-05), the base station (1f-10) can set at least one of a simultaneous measurement gap and a MUSIM gap to the terminal (1f-05). That is, the base station (1f-10) can set a simultaneous measurement gap and a MUSIM gap simultaneously, or only a simultaneous measurement gap, or only a MUSIM gap to the terminal (1f-05) for which a preset measurement gap for positioning purposes has not been set.

[0210] For reference, the gap configuration information for one or more gap capabilities included in the above-described RRC message may follow the aforementioned embodiment (the embodiment illustrated in FIG. 1e). Additionally, in the present embodiment, the MUSIM gap configuration information included in the message may include the following information:

[0211] - MUSIM gap configuration information (MUSIM-GapConfig)

[0212] ■ The specific ASN.1 structure for MUSIM gap setting and the description of each field may be as follows. The difference from the above-described embodiment (the embodiment illustrated in FIG. 1e) is that priority information for periodic MUSIM gaps and setting information for an indicator (musim-GapKeep) indicating whether the terminal can maintain and use MUSIM gaps when they collide are added.

[0213] -MUSIM-GapConfig

[0214] The IEMUSIM-GapConfigspecifies the MUSIM gap configuration and controls setup / release of MUSIM gaps.

[0215] MUSIM-GapConfiginformation element

[0216] -- ASN1START-- TAG-SEASON-GAPCONFIG-STARTSeason-GapConfig-r17 ::= SEQUENCE {season-GapToReleaseList-r17 SEQUENCE (SIZE (1..3)) OF SEASON-GapId-r17 OPTIONAL, -- Need Nseason-GapToAddModList-r17 SEQUENCE (SIZE (1..3)) OF SEASON-Gap-r17 OPTIONAL, -- Need Nseason-AperiodicGap-r17 SEASON-GapInfo-r17 OPTIONAL, -- Need N...,[[season-GapPriorityToAddModList-r18 SEQUENCE (SIZE (1..3)) OF GapPriority-r17 OPTIONAL, -- Need Nseason-GapKeep-r18 ENUMERATED {true} OPTIONAL -- Need R]]}MUSIM-Gap-r17 ::= SEQUENCE {musim-GapId-r17 MUSIM-GapId-r17,musim-GapInfo-r17 MUSIM-GapInfo-r17}-- TAG-MUSIM-GAPCONFIG-STOP-- ASN1STOP

[0217] MUSIM-GapConfig field descriptionsmusim-AperiodicGapIndicates the MUSIM aperiodic gap as specified in TS 38.133

[0014] clause 9.1.10. If UE indicates the musim-Starting-SFN-AndSubframe when requesting aperiodic gap the network can only configure the aperiodic gap with the same start point or no aperiodic gap. If the field musim-Starting-SFN-AndSubframe is 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 for musim-GapLength and musim-GapRepetitionAndOffset. When network provides periodic gap, network always signals the musim-GapLength and musim-GapRepetitionAndOffset as indicated by the UE's preferred MUSIM gap configuration.musim-GapKeepIndicates the UE is allowed to use “keep solution” for collided MUSIM periodic gaps. If “keep solution” is not granted, priority based solution is used as fallback solution) as specified in TS 38.133

[0014] .musim-GapPriorityToAddModListIndicates the priority of MUSIM periodic gap(s).If the network includes musim-GapPriorityToAddModList-r18, it includes the same number of entries, and listed in the same order, as in musim-GapToAddModList-r17.For the priority of MUSIM aperiodic gap, the MUSIM aperiodic gap is always kept (not dropped) from UE perspective in case of collisions with other gaps (i.e. all gaps including MUSIM gaps, etc).musim-GapToAddModListList of MUSIM periodic gap patterns to add or modify.musim-GapToReleaseListList of MUSIM periodic gap patterns to release.

[0218] -MUSIM-GapInfo

[0219] The IEMUSIM-GapInfois used to indicate MUSIM gap parameters.

[0220] MUSIM-GapInfoinformation element

[0221] -- 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-- ASN1STOP

[0222] MUSIM-GapInfo field descriptionsmusim-GapLengthIndicates the length of the UE's MUSIM gap as specified in TS 38.133

[0014] 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

[0014] 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.

[0223] 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.

[0224] A terminal (1f-05) according to the present disclosure has the feature of supporting one or more independent gap capabilities, as in the above-described embodiment (the embodiment illustrated in FIG. 1e). Additionally, a terminal (1f-05) according to the present disclosure may configure configuration information for a simultaneous measurement gap and a MUSIM gap together if a preset measurement gap for positioning purposes is not configured. If a preset measurement gap for positioning purposes is configured simultaneously with a simultaneous measurement gap and / or a MUSIM gap, the terminal (1f-05) may perform an RRC connection re-establishment procedure because it cannot follow all the configuration information therefor.

[0225] A base station (1f-10) according to the present disclosure has a feature of setting a gap for one or more gap capabilities to a terminal (1f-05) supporting one or more independent gap capabilities as follows.

[0226] - The base station (1f-10) does not configure MUSIM gap together with preconfigured measurement gap for positioning, but it can configure MUSIM gap together with concurrent measurement gap.

[0227] - The base station (1f-10) does not configure preconfigured measurement gap for positioning together with concurrent measurement gap or MUSIM gap.

[0228] - The base station (1f-10) does not configure a concurrent measurement gap together with a preconfigured measurement gap for positioning purposes, but it can configure a concurrent measurement gap together with a MUSIM gap.

[0229] For reference, the maximum number of gaps that the base station (1f-10) can set (simultaneously) for the terminal (1f-05) may be limited to a predetermined integer value (e.g., 16). In this case, the predetermined integer value may be explicitly notified to the base station (1f-10) by the terminal (1f-05) through a separate terminal capability indicator, or may be a value that is predetermined only for the terminal (1f-05) according to the present disclosure (i.e., in the case where gap settings for two or more independent gap capabilities can be set simultaneously).

[0230] FIG. 1g is an example of a flowchart of operations in which a terminal supporting one or more independent gap features receives a gap from a base station according to another embodiment of the present invention.

[0231] Referring to FIG. 1g, at step 1g-15, the terminal (1g-05) may be in RRC connection mode by establishing an RRC connection with the base station (1g-10).

[0232] In step 1g-20, the terminal (1g-05) may transmit a terminal capability information (e.g., UECapabilityInformation) message to the base station (1g-10). The terminal capability information included in the message may follow at least one of the aforementioned embodiments (the embodiments illustrated in FIGS. 1e and / or 1f). Additionally, in the present embodiment, the message may include the following information.

[0233] - jointMUSIM-ConcurrentMG-OrMUSIM-PrePosMG

[0234] ■ It may mean a terminal capability indicator indicating whether it supports concurrent measurement gaps and MUSIM gaps being set at the same time, and concurrently setting of a MUSIM gap and a preset measurement gap for positioning purposes. Or it may mean a terminal capability indicator indicating whether it can handle a conflict between concurrent measurement gaps and MUSIM gaps that are set at the same time (for example, the ability to use a gap with a higher priority and not use (drop) a lower priority one, or to use a gap with a long gap repetition cycle and not use a lower priority one). For reference, the condition for determining that gaps conflict can follow the embodiment described above (the embodiment illustrated in FIG. 1F). There is no separate handling requirement for a conflict between a MUSIM gap and a preset measurement gap for (activated) positioning purposes.

[0235] ■ The above terminal capability indicator is signaled for each terminal, and there is no functional difference between FDD and TDD, and no functional difference between FR1 and FR2.

[0236] In step 1g-25, the base station (1g-10) can transmit to the terminal (1g-05) a predetermined RRC message (e.g., RRCResume or RRCReconfiguration) containing one or more gap configuration information according to predetermined conditions among one or more gap capabilities supported by the terminal (1g-05). Specifically,

[0237] - If the base station (1g-10) sets a preset measurement gap for positioning purposes to the terminal (1g-05), the base station (1g-10) cannot set a simultaneous measurement gap to the terminal (1g-05), but can set a MUSIM gap.

[0238] - If the base station (1g-10) does not set a measurement gap for positioning purposes to the terminal (1g-05), the base station (1g-10) may set a simultaneous measurement gap and a MUSIM gap to the terminal (1g-05) at the same time, or may set only a simultaneous measurement gap, or may set only a MUSIM gap.

[0239] For reference, the gap configuration information for one or more gap capabilities included in the above-described RRC message may follow at least one of the embodiments described above (the embodiments illustrated in FIG. 1e and / or FIG. 1f).

[0240] A terminal (1g-05) according to the present disclosure has the feature of supporting one or more independent gap capabilities, as in the above-described embodiment (the embodiment illustrated in FIG. 1e). Additionally, a terminal (1g-05) according to the present disclosure has the feature that a preset measurement gap for positioning purposes, a simultaneous measurement gap, and a MUSIM gap cannot be set together, but configuration information for the simultaneous measurement gap and the MUSIM gap can be set together, or a preset measurement gap for positioning purposes and the MUSIM gap can be set together. If a preset measurement gap for positioning purposes is set together with a simultaneous measurement gap, the terminal (1g-05) may perform an RRC connection re-establishment procedure because it cannot follow all the configuration information therefor.

[0241] A base station (1g-10) according to the present disclosure has a feature of setting a gap for one or more gap capabilities to a terminal (1g-05) supporting one or more independent gap capabilities as follows.

[0242] - The network (1g-10) can configure MUSIM gap together with either preconfigured measurement gap for positioning or concurrent measurement gap, but it does not configure MUSIM gap together with both preconfigured measurement gap for positioning and concurrent measurement gap.

[0243] - The network (1g-10) does not configure a preconfigured measurement gap for positioning together with a concurrent measurement gap, but it can configure a preconfigured measurement gap for positioning together with a MUSIM gap.

[0244] - The base station (1g-10) does not configure concurrent measurement gap together with preconfigured measurement gap for positioning, but it can configure concurrent measurement gap together with MUSIM gap.

[0245] For reference, the maximum number of gaps that the base station (1g-10) can set (simultaneously) for the terminal (1g-05) may be limited to a predetermined integer value (e.g., 16). In this case, the predetermined integer value may be explicitly notified to the base station (1g-10) by the terminal (1g-05) through a separate terminal capability indicator, or may be a value that is predetermined only for the terminal (1g-05) according to the present disclosure (i.e., in the case where gap settings for two or more independent gap capabilities can be set simultaneously).

[0246] FIG. 1h is an example of a flowchart of operations in which a terminal supporting one or more independent gap features receives a gap from a base station according to another embodiment of the present invention.

[0247] Referring to FIG. 1h, at step 1h-15, the terminal (1h-05) may be in RRC connection mode by establishing an RRC connection with the base station (1h-10).

[0248] In step 1h-20, the terminal (1h-05) may transmit a terminal capability information (e.g., UECapabilityInformation) message to the base station (1h-10). The terminal capability information included in the message may follow at least one of the aforementioned embodiments (the embodiments illustrated in FIGS. 1e, 1f, and / or 1g). Additionally, in the present embodiment, the message may include the following information.

[0249] - jointMUSIM-ConcurrentMG-PrePosMG (or jointMUSIM-ConcurrentMG-MUSIM-PrePosMG)

[0250] ■ It may mean a terminal capability indicator indicating whether the terminal supports simultaneous setting of any combination of MUSIM gap, concurrent measurement gap, and preset measurement gap for positioning purpose. Through the capability indicator, the terminal may have the ability to handle a conflict between a concurrently set concurrent measurement gap and a MUSIM gap (for example, the ability to use a gap with a higher priority and not use (drop) a lower priority one, or to use a gap with a long gap repetition cycle and not use a lower priority one). For reference, the condition for determining that gaps are in conflict may follow the embodiment described above (the embodiment illustrated in FIG. 1F). There may be no separate handling requirement for a conflict between a MUSIM gap and a preset measurement gap for (activated) positioning purpose.

[0251] ■ The above terminal capability indicator is signaled for each terminal, and there is no functional difference between FDD and TDD, and no functional difference between FR1 and FR2.

[0252] ■ Terminals that support the above capabilities can have gaps set simultaneously up to X (meaning a predetermined integer value, for example, 16).

[0253] At step 1h-25, the base station (1h-10) can transmit a predetermined RRC message (e.g., RRCResume or RRCReconfiguration) containing one or more gap configuration information among one or more gap features supported by the terminal (1h-05) without any separate restrictions. Specifically,

[0254] - The base station (1g-10) can set at least one of a MUSIM gap, a simultaneous measurement gap, and a measurement gap preset for positioning purposes to the terminal (1g-05). That is, even if the base station (1g-10) sets three gaps to the terminal (1g-05) at the same time, the terminal (1g-05) can apply them.

[0255] For reference, the gap configuration information for one or more gap capabilities included in the above-described RRC message may follow at least one of the embodiments described above (the embodiments illustrated in FIG. 1e and / or FIG. 1f).

[0256] A terminal (1g-05) according to the present disclosure has the feature of supporting one or more independent gap capabilities, as in the aforementioned embodiment (the embodiment illustrated in FIG. 1e). Additionally, a terminal (1g-05) according to the present disclosure has the feature of being able to simultaneously set a preset measurement gap, a simultaneous measurement gap, and a MUSIM gap for positioning purposes.

[0257] A base station (1g-10) according to the present disclosure can set a simultaneous measurement gap, a preset measurement gap for positioning purposes, and a MUSIM gap together for a terminal (1g-05) supporting one or more independent gap capabilities. However, the maximum number of gaps that the base station (1g-10) can set (simultaneously) for the terminal (1g-05) may be limited to a predetermined integer value (e.g., 16). In this case, the predetermined integer value may be explicitly notified to the base station (1g-10) by the terminal (1g-05) through a separate terminal capability indicator.

[0258] FIG. 1i is an example of a flowchart of operations in which a terminal supporting one or more independent gap features receives a gap from a base station according to another embodiment of the present invention.

[0259] Referring to FIG. 1i, at step 1i-15, the terminal (1i-05) may be in RRC connection mode by establishing an RRC connection with the base station (1i-10).

[0260] In step 1i-20, the terminal (1i-05) may transmit a terminal capability information (e.g., UECapabilityInformation) message to the base station (1i-10). The terminal capability information included in the message may follow at least one of the above-described embodiments (the embodiments illustrated in FIGS. 1e, 1f, 1g, and / or 1h). For example, the message may include the following information, which may follow the above-described embodiments (the embodiment illustrated in FIG. 1f).

[0261] - musim-GapPriorityPreference

[0262] For example, if musim-GapPriorityPreference is included in UECapabilityInformation, this may mean that the terminal (1i-05) supports simultaneous configuration of a concurrent measurement gap and a MUSIM gap, according to the embodiment illustrated in FIG. 1f. Alternatively, this may mean that the terminal (1i-05) can handle a conflict between a configured concurrent measurement gap and a MUSIM gap (e.g., use a gap with a higher priority and drop (or delete) a gap with a lower priority, or use a gap with a longer gap repetition cycle and drop a gap with a lower priority). For reference, the conditions for determining that gaps conflict may follow the above-described embodiment (the embodiment illustrated in FIG. 1f).

[0263] Alternatively, if musim-GapPriorityPreference is included in UECapabilityInformation, it may mean that the terminal (1i-05) supports simultaneous setting of a concurrent measurement gap and a MUSIM gap, and simultaneous setting of a MUSIM gap and a measurement gap preset for positioning purposes, according to the embodiment illustrated in FIG. 1g.

[0264] Alternatively, if musim-GapPriorityPreference is included in UECapabilityInformation, it may mean that the terminal (1i-05) supports any combination of a MUSIM gap, a concurrent measurement gap, and a measurement gap preset for positioning purposes, as illustrated in the embodiment shown in FIG. 1h.

[0265] At step 1i-25, the base station (1i-10) may transmit a predetermined RRC message (e.g., RRCResume or RRCReconfiguration) containing gap configuration information of one or more gap capabilities supported by the terminal (1i-05). At this time, the base station (1i-10) may set gap configuration information of one or more gap capabilities to the terminal (1i-05) according to at least one of the above-described embodiments (the embodiments illustrated in FIGS. 1e, 1f, 1g, and / or 1h). For reference, the maximum number of gaps set by the base station (1i-10) to the terminal (1i-05) may be restricted to a predetermined integer value (e.g., 16).

[0266] For example, in the case where musim-GapPriorityPreference is included in UECapabilityInformation, as in the embodiment illustrated in FIG. 1f, if the terminal (1i-05) supports simultaneous setting of a concurrent measurement gap and a MUSIM gap, and the base station (1i-10) sets a preset measurement gap for positioning purposes to the terminal (1i-05), the base station (1i-10) may not set a concurrent measurement gap and a MUSIM gap to the terminal (1i-05). That is, the base station (1i-10) has a characteristic of not setting a concurrent measurement gap and a MUSIM gap to the terminal (1f-05) for which a preset measurement gap for positioning purposes has been set. And, if the base station (1i-10) does not set a preset measurement gap for positioning purposes to the terminal (1i-05), the base station (1i-10) can set at least one of a simultaneous measurement gap and a MUSIM gap to the terminal (1i-05). That is, the base station (1i-10) can set both a simultaneous measurement gap and a MUSIM gap at the same time, or only a simultaneous measurement gap, or only a MUSIM gap to the terminal (1i-05) for which a preset measurement gap for positioning purposes has not been set. FIG. 1j is an example of a flowchart for processing colliding MUSIM gaps by a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple USIMs according to an embodiment of the present invention.

[0267] A MUSIM terminal (1j-01) according to one embodiment of the present disclosure may refer to a terminal that supports two or more USIMs. For convenience of explanation, the present disclosure considers a Dual-USIM terminal that supports two USIMs. A Dual-USIM terminal has the characteristic of transmitting to a base station associated with one USIM at a given time or transmitting to base stations associated with each USIM. Similarly, a Dual-USIM terminal has the characteristic of receiving from a base station associated with one USIM at a given time or simultaneously receiving from base stations associated with each USIM.

[0268] Referring to FIG. 1j, a MUSIM terminal (1j-01) may refer to a terminal that supports multiple USIMs in one device. For example, when the MUSIM terminal (1j-01) operates on USIM 1, it may refer to a USIM 1 terminal (1j-02), and when it operates on USIM 2, it may refer to a USIM 2 terminal (1j-03). The base stations (1j-04, 1j-05) (network, NW) associated with each USIM may not recognize the MUSIM terminal (1j-01) as one terminal, but may recognize each USIM terminal as one terminal. For example, base station 1 (1j-04) may recognize the USIM 1 terminal (1j-02) as one terminal, and base station 2 (1j-05) may recognize the USIM 2 terminal (1j-03) as one terminal. For convenience of explanation in the embodiments of the present disclosure below, when a MUSIM terminal (1j-01) communicates using USIM 1, the MUSIM terminal (1j-01) will be referred to as a USIM 1 terminal (1j-02), and when the MUSIM terminal (1j-01) communicates using USIM 2, the MUSIM terminal (1j-01) will be referred to as a USIM 2 terminal (1j-03). That is, the MUSIM terminal (1j-01) can be a USIM 1 terminal (1j-02) or a USIM 2 terminal (1j-03) depending on which USIM between USIM 1 and USIM 2 is used.

[0269] In step 1j-13, the USIM 1 terminal (1j-02) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 1 (1j-04). On the other hand, at this time, as in step 1j-10, the USIM 2 terminal (1j-03) may not establish an RRC connection with base station 2 (1j-05) and may be in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE). Of course, the contents of the present invention may be equally applied even when the USIM 2 terminal (1j-03) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 2 (1j-05).

[0270] In step 1j-15, the USIM 1 terminal (1j-02) may transmit a terminal capability information message (e.g., UECapabilityInformation) to the base station 1 (1j-04). The message may include any of the following information:

[0271] - musim-GapPreference

[0272] ■ The description of the above terminal capability indicator may follow the above-described embodiment (the embodiment illustrated in FIG. 1e).

[0273] - musim-GapPriorityPreference

[0274] ■ The description of the above terminal capability indicator may follow the above-described embodiment (the embodiment exemplified in FIG. 1f). A terminal supporting the above capability has the characteristic of being able to maintain periodic MUSIM gaps that collide according to the instruction of the base station (e.g., musim-GapKeep). For reference, the criterion by which the terminal determines that multiple MUSIM gaps collide may follow the above-described embodiment (the embodiment exemplified in FIG. 1f).

[0275] At step 1j-20, base station 1 (1j-04) can transmit otherConfig containing musim-GapAssistanceConfig and musim-GapPriorityAssistanceConfig to USIM 1 terminal (1j-02). For reference, otherConfig can be transmitted to terminal (1j-02) via a predetermined RRC message (e.g., RRCReconfiguration, etc.). Upon receiving this, terminal (1j-02) can perform the following actions.

[0276] - if musim-GapAssistanceConfig is set to setup

[0277] ■ The terminal (1j-02) may be considered to be configured to provide MUSIM assistance information for gap preference to the base station (1j-04).

[0278] - Otherwise (e.g. if musim-GapAssistanceConfig is set to release)

[0279] ■ The terminal (1j-02) may consider itself not to be configured to provide MUSIM assistance information for gap preference and stop timer T346h, if running.

[0280] - if musim-GapPriorityAssistanceConfig is set to setup

[0281] ■ The terminal (1j-02) may be considered to be configured to provide MUSIM assistance information for gap priority to the base station (1j-04).

[0282] - if not (e.g. if musim-GapPriorityAssistanceConfig is set to release)

[0283] ■ The terminal (1j-02) above may be considered not to be configured to provide MUSIM assistance information for gap(s) priority to the base station (1j-04).

[0284] For reference, the description and Abstract Syntax Notation.One (ASN.1) for the above musim-GapAssistanceConfig and musim-GapPriorityAssistanceConfig may be as follows.

[0285] OtherConfig-v1700 ::= SEQUENCE {...musim-GapAssistanceConfig-r17 SetupRelease {MUSIM-GapAssistanceConfig-r17} OPTIONAL, -- Need MMUSIM-GapAssistanceConfig-r17 ::= SEQUENCE {musim-GapProhibitTimer-r17 ENUMERATED {s0, s0dot1, s0dot2, s0dot3, s0dot4, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10}}MUSIM-LeaveAssistanceConfig-r17 ::= SEQUENCE {musim-LeaveWithoutResponseTimer-r17 ENUMERATED {ms10, ms20, ms40, ms60, ms80, ms100, spare2, spare1}}OtherConfig-v18xy ::= SEQUENCE {musim-GapPriorityAssistanceConfig-r18 ENUMERATED {true} OPTIONAL, -- Cond musimGapConfig

[0286] musim-GapAssistanceConfigConfig Configuration information for the UE to report assistance information for gap preference. musim-GapPriorityAssistanceConfigConfig Indicates the UE is allowed to provide MUSIM assistance information for gap(s) priority and / or MUSIM gaps keep preference. musim-GapProhibitTimerProhibit timer for MUSIM assistance information reporting for gap preference.

[0287] Conditional PresenceExplanationmusimGapConfigThis field is optionally present, need R, if musim-GapAssistanceConfig-r17 is configured; otherwise it is absent, need R.

[0288] In step 1j-25, the USIM 2 terminal (1j-03) may notify (notify) the USIM 1 terminal (1j-02) of information (e.g., one or more MUSIM gap setting information) required to perform operations (e.g., cell reselection, system information reception, frequency measurement, etc.) required in RRC idle mode or RRC inactive mode.

[0289] In step 1j-30, the USIM 1 terminal (1j-02) may transmit a terminal assistance information message (e.g., UEAssistanceInformation) containing MUSIM assistance information (MUSIM-Assistance) to the base station 1 (1j-04). The MUSIM-Assistance may include at least one of the following information.

[0290] - musim-GapPreferenceList

[0291] ■ It means a list consisting of one or more MUSIM-GapInfo, and the description of each MUSIM-GapInfo can refer to the embodiment described above (the embodiment illustrated in FIG. 1e).

[0292] ■ Up to three MUSIM-GapInfo for periodic MUSIM gaps and up to one MUSIM-GapInfo for aperiodic MUSIM gap can be stored in the musim-GapPreferenceList.

[0293] -musim-GapPriorityPreferenceList

[0294] ■ Refers to a list consisting of one or more gap priority values ​​(GapPriority).

[0295] ■ The gap priority value indicates the priority for gap settings and can be indicated by a single integer value. For example, the gap priority value can be indicated as '1', '2', or '16'. A smaller indicated value can indicate a higher priority. For example, a value of '1' can indicate the highest priority, and a value of '2' can indicate the second level priority.

[0296] ■ Each gap priority value can be mapped to each periodic MUSIM gap contained in musim-GapPreferenceList in one of the following ways:

[0297] ◆ Method 1: musim-GapPriorityPreferenceList can be mapped according to the order of periodic MUSIM gaps stored in musim-GapPreferenceList. For example, if musim-GapPreferenceList is configured with {Periodic MUSIM gap a, aperiodic MUSIM gap b, periodic MUSIM gap c} and musim-GapPriorityPreferenceList is configured with {Gap Priority x, Gap Priority y}, the first priority value 'Gap Priority x' can be mapped to 'Periodic MUSIM gap a', and the second priority value 'Gap Priority y' can be mapped to 'Periodic gap c'. That is, each gap priority value stored in musim-GapPriorityPreferenceList can know which periodic MUSIM gap among the MUSIM gaps stored in musim-GapPreferenceList it is mapped to without a separate indicator.

[0298] ◆ Method 2: Each entry in musim-GapPriorityPreferenceList can consist of a gap priority value and an indicator indicating which periodic MUSIM gap in musim-GapPreferenceList that value maps to.

[0299] - musim-GapKeepPreference

[0300] At step 1j-35, base station 1 (1j-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing musim-GapConfig to USIM 1 terminal (1j-02). musim-GapConfig may include at least one of the following:

[0301] - List of MUSIM gaps to be released (musim-GapToReleaseList)

[0302] ■ The above list may consist of one or more identifiers (MUSIM-GapId).

[0303] ■ You can release the periodic MUSIM gap set for the terminal through the above list.

[0304] - List of MUSIM gaps to add or modify (musim-GapToAddModList)

[0305] ■ The above list consists of one or more MUSIM gaps (MUSIM-Gap), and each MUSIM gap can be composed of MUSIM gap setting information (MUSIM-GapInfo) and an identifier for it (MUSIM-GapId).

[0306] ■ One or more periodic MUSIM gaps can be set for the terminal through the above list.

[0307] - Aperiodic MUSIM gap setting information (musim-AperiodicGap)

[0308] ■ You can set an aperiodic MUSIM gap for the terminal through MUSIM gap setting information (MUSIM-GapInfo).

[0309] - MUSIM gap priority list to add or modify (musim-GapPriorityToAddModList)

[0310] ■ The above list may consist of one or more MUSIM gap priority values ​​(GapPriority).

[0311] ■ The above list allows you to set gap priority values ​​for each periodic MUSIM gap for the terminal.

[0312] - An indicator indicating whether it is acceptable to keep conflicting periodic MUSIM gaps (musim-GapKeep)

[0313] ■ The above directive can be used to configure the terminal to maintain and use periodic MUSIM gaps that satisfy at least one of the following conditions.

[0314] ◆ Condition 1: Gap occasions are fully or partially overlapping in the time domain

[0315] ◆ Condition 2: When the distance between two gap occasions is equal to or smaller than 4ms

[0316] ● The distance between two gap opportunities is defined as the time difference between the ending point of the first occasion and the starting point of the second occasion, where the first gap opportunity occurs earlier in time than the second gap opportunity.

[0317] The terminal (1j-02) that receives musim-GapConfig can perform the following actions.

[0318] - if musim-GapConfig is set to setup

[0319] ■ For each musim-GapId included in the received musim-GapToReleaseList, the UE shall release the periodic MUSIM gap configuration associated with the musim-GapId.

[0320] ■ For each musim-Gap included in the received musim-GapToAddModList

[0321] ◆ The UE shall setup periodic MUSIM gap configuration indicated by the MUSIM-Gap in accordance with the received musim-GapRepetitionAndOffset. The musim-GapRepetition and Offset values ​​are provided according to the following conditions, and the first subframe of each periodic MUSIM gap occurs at an SFN (System Frame Number) and subframe of the NR PCell meeting the following conditions.

[0322] condition:

[0323] SFN mod T = FLOOR(Offset / 10);

[0324] subframe = Offset mod 10;

[0325] with T = musim-GapRepetition / 10;

[0326] ◆ For each periodic MUSIM gap, you can set the MUSIM gap priority configuration indicated by musim-GapPriority, if configured, for each periodic MUSIM gap.

[0327] ◆ If all collided MUSIM gaps are configured to be kept, musim-GapKeep can be set. That is, if the base station instructs musim-GapKeep, the terminal can keep all collided MUSIM gaps and use them (use keep solution) without deciding which ones to use or not based on priority.

[0328] ■ If musim-AperiodicGap is included

[0329] ◆ An aperiodic MUSIM gap configuration indicated by the musim-AperiodicGap in accordance with the received musim-Starting-SFN-AndSubframe can be set up. The first subframe of an aperiodic MUJSIM gap can occur in an SFN and subframe of the NR PCell that meets the following conditions:

[0330] condition:

[0331] SFN = starting-SFN;

[0332] Subframe = startingSubframe;

[0333] - if musim-GapConfig is set to release (else if musim-Gapconfig is set to release)

[0334] ■ The UE shall release the MUSIM gap configuration.

[0335] At step 1j-40, the USIM 1 terminal (1j-02) may transmit a predetermined RRC message (e.g., RRCReconfigurationComplete) to the base station 1 (1j-04) in response to step 1j-35.

[0336] In step 1j-45, the USIM 1 terminal (1j-02) can determine whether the MUSIM gaps set up in step 1j-35 collide. That is, if the MUSIM gap opportunities overlap on the time axis or the distance between the MUSIM gap opportunities is less than or equal to 4 ms, the terminal (1j-02) can determine that the corresponding MUSIM gaps collide.

[0337] In step 1j-50, if the USIM 1 terminal (1j-02) determines that there are conflicting MUSIM gaps in step 1j-45, it can decide which of these MUSIM gaps to keep or drop. Specifically,

[0338] - If all colliding MUSIM gaps are periodic MUSIM gaps:

[0339] ■ If musim-GapKeep is indicated:

[0340] ◆ The above terminal (1j-02) can maintain periodic MUSIM gaps that collide.

[0341] ■ Otherwise (i.e., musim-GapKeep is not indicated):

[0342] ◆ The terminal (1j-02) above can keep the periodic MUSIM gap with the highest priority among the colliding periodic MUSIM gaps and discard the remaining periodic MUSIM gaps (for each collision, the MUSIM gap with the highest priority among the colliding occasions shall be kept and the rest shall be dropped). For reference, the smaller the GapPriority value set in step 1j-35, the higher the priority it can have.

[0343] - If aperiodic MUSIM gaps and periodic MUSIM gap(s) collide:

[0344] ■ Regardless of whether musim-GapKeep is indicated, the terminal (1j-02) can maintain the aperiodic MUSIM gap and discard the periodic MUSIM gap(s). This is because, as described above, the aperiodic MUSIM gap always has the highest priority, and in step 1j-35, the terminal (1j-02) applies musim-GapKeep before setting the aperiodic MUSIM gap. Or, the musim-GapKeep indicated by the base station (1j-04) is set to the terminal (1j-02) to keep the conflicting periodic MUSIM gaps.

[0345] Note that steps 1j-45 and 1j-50 may be performed before step 1j-35.

[0346] In step 1j-60, the USIM 1 terminal (1j-02) may not perform transmission and reception operations with base station 1 (1j-04) during the MUSIM gap that it has decided to use. That is, if a MUSIM gap that it has decided to use without discarding it occurs in step 1j-50, the terminal (1j-02) may not perform transmission and reception operations with base station 1 (1j-04) (e.g., NR serving cells) during the gap. On the other hand, in step 1j-55, the USIM 2 terminal (1j-03) may perform necessary operations during the MUSIM gap. That is, the USIM 2 terminal (1j-03) may perform necessary operations (e.g., cell selection or cell reselection operations) with base station 2 (1j-05).

[0347] A USIM 1 terminal (1j-02) according to the present disclosure can maintain and use periodic MUSIM gaps when a collision occurs between them if musim-GapKeep is indicated. However, even if musim-GapKeep is indicated, the terminal (1j-02) has a characteristic of maintaining and using only the aperiodic MUSIM gaps and discarding the periodic MUSIM gaps when the periodic MUSIM gap(s) and the aperiodic MUSIM gap(s) collide. However, this may prevent the USIM 2 terminal (1j-03) from successfully performing the required operation. For example, the USIM 2 terminal (1j-03) must use both the conflicting aperiodic MUSIM gaps and the periodic MUSIM gaps to successfully acquire system information broadcast by base station 2 (1j-05). However, since the periodic MUSIM gap is discarded and not used, a problem may arise in which there is a delay in successfully acquiring the system information.

[0348] Base station 1 (1j-04) according to the present disclosure can set musim-GapKeep to maintain and use periodic MUSIM gaps that may collide with USIM 1 terminals (1j-02). However, this only applies to collisions between periodic MUSIM gaps, and may not apply to collisions between non-periodic MUSIM gaps and periodic MUSIM gaps.

[0349] FIG. 1k is an example of a flowchart for processing conflicting MUSIM gaps by a terminal (MUSIM UE) supporting multiple USIMs according to another embodiment of the present invention.

[0350] A MUSIM terminal (1k-01) according to one embodiment of the present disclosure may refer to a terminal that supports two or more USIMs. For convenience of explanation, the present disclosure considers a Dual-USIM terminal that supports two USIMs. A Dual-USIM terminal has the characteristic of transmitting to a base station associated with one USIM at a given time or transmitting to base stations associated with each USIM. Similarly, a Dual-USIM terminal has the characteristic of receiving from a base station associated with one USIM at a given time or receiving simultaneously from base stations associated with each USIM.

[0351] Referring to FIG. 1k, a MUSIM terminal (1k-01) may refer to a terminal that supports multiple USIMs in one device. For example, when the MUSIM terminal (1k-01) operates on USIM 1, it may refer to a USIM 1 terminal (1k-02), and when it operates on USIM 2, it may refer to a USIM 2 terminal (1k-03). The base stations (NWs) (1k-04, 1k-05) associated with each USIM may not recognize the MUSIM terminal (1k-01) as one terminal, but may recognize each USIM terminal as one terminal. For example, base station 1 (1k-04) may recognize the USIM 1 terminal (1k-02) as one terminal, and base station 2 (1k-05) may recognize the USIM 2 terminal (1k-03) as one terminal. For convenience of explanation in the embodiments of the present disclosure below, when a MUSIM terminal (1k-01) communicates using USIM 1, the MUSIM terminal will be referred to as a USIM 1 terminal (1k-02), and when the MUSIM terminal (1k-01) communicates using USIM 2, the MUSIM terminal will be referred to as a USIM 2 terminal (1k-03). That is, the MUSIM terminal (1k-01) can be a USIM 1 terminal (1k-02) or a USIM 2 terminal (1k-03) depending on which USIM between USIM 1 and USIM 2 is used.

[0352] At step 1k-15, the USIM 1 terminal (1k-02) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 1 (1k-04). On the other hand, at this time, at step 1k-10, the USIM 2 terminal (1k-03) may not establish an RRC connection with base station 2 (1k-05) and may be in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE). Of course, the contents of the present invention may be equally applied even when the USIM 2 terminal (1k-03) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 2 (1k-05).

[0353] At step 1k-15, the USIM 1 terminal (1k-02) may transmit a terminal capability information message (e.g., UECapabilityInformation) to base station 1 (1k-04). The message may include at least one of the following information:

[0354] - musim-GapPreference

[0355] ■ The description of the above terminal capability indicator may follow the above-described embodiment (the embodiment illustrated in FIG. 1e).

[0356] - musim-GapPriorityPreference

[0357] ■ The description of the terminal capability indicator may follow the above-described embodiment (the embodiment illustrated in FIG. 1f). A terminal supporting the capability has a feature of being able to maintain all colliding MUSIM gaps according to the instruction of the base station (e.g., musim-GapKeep). That is, unlike the above-described embodiment (the embodiment illustrated in FIG. 1j), a terminal supporting the capability according to the present disclosure has a feature of maintaining and using both aperiodic MUSIM gaps and periodic MUSIM gaps even when they collide. For reference, the criterion by which the terminal (1k-01) determines that multiple MUSIM gaps collide may follow the above-described embodiment (the embodiment illustrated in FIG. 1f).

[0358] At step 1k-20, base station 1 (1k-04) may transmit otherConfig containing musim-GapAssistanceConfig and musim-GapPriorityAssistanceConfig to USIM 1 terminal (1k-02). Upon receiving this, the terminal (1k-02) may follow the operation of the aforementioned embodiment (the embodiment illustrated in FIG. 1j).

[0359] At step 1k-25, the USIM 2 terminal (1k-03) may notify the USIM 1 terminal (1k-02) of information (e.g., one or more MUSIM gap setting information) required to perform operations (e.g., cell reselection, system information reception, frequency measurement, etc.) required in RRC idle mode or RRC deactivation mode.

[0360] At step 1k-30, the USIM 1 terminal (1k-02) may transmit a terminal assistance information message (e.g., UEAssistanceInformation) containing MUSIM assistance information (MUSIM-Assistance) to the base station 1 (1k-04). The information that may be included in the MUSIM-Assistance may follow the aforementioned embodiment (the embodiment illustrated in FIG. 1j).

[0361] At step 1k-35, base station 1 (1k-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing musim-GapConfig to USIM 1 terminal (1k-02). musim-GapConfig may include at least one of the following:

[0362] - List of MUSIM gaps to be released (musim-GapToReleaseList)

[0363] ■ The above list may consist of one or more identifiers (MUSIM-GapId).

[0364] ■ You can release the periodic MUSIM gap set for the terminal through the above list.

[0365] - List of MUSIM gaps to add or modify (musim-GapToAddModList)

[0366] ■ The above list consists of one or more MUSIM gaps (MUSIM-Gap), and each MUSIM gap can be composed of MUSIM gap setting information (MUSIM-GapInfo) and an identifier for it (MUSIM-GapId).

[0367] ■ One or more periodic MUSIM gaps can be set for the terminal through the above list.

[0368] - Aperiodic MUSIM gap setting information (musim-AperiodicGap)

[0369] ■ You can set an aperiodic MUSIM gap for the terminal through MUSIM gap setting information (MUSIM-GapInfo).

[0370] - MUSIM gap priority list to add or modify (musim-GapPriorityToAddModList)

[0371] ■ The above list may consist of one or more MUSIM gap priority values ​​(GapPriority).

[0372] ■ The above list allows you to set gap priority values ​​for each periodic MUSIM gap for the terminal.

[0373] - An indicator (musim-GapKeep) indicating whether all conflicting MUSIM gaps can be kept and used.

[0374] ■ Through the above directive, the terminal can be configured to maintain and use periodic MUSIM gap(s) and aperiodic MUSIM gap(s) that satisfy at least one of the following conditions.

[0375] ◆ Condition 1: Gap occasions are fully or partially overlapping in the time domain

[0376] ◆ Condition 2: When the distance between two gap occasions is equal to or smaller than 4ms

[0377] ● The distance between two gap opportunities is defined as the time difference between the ending point of the first occasion and the starting point of the second occasion, where the first gap opportunity occurs earlier in time than the second gap opportunity.

[0378] The terminal (1k-02) that receives musim-GapConfig can perform the following actions.

[0379] - if musim-GapConfig is set to setup

[0380] ■ For each musim-GapId included in the received musim-GapToReleaseList, the UE shall release the periodic MUSIM gap configuration associated with the musim-GapId.

[0381] ■ For each musim-Gap included in the received musim-GapToAddModList

[0382] ◆ The UE shall setup periodic MUSIM gap configuration indicated by the MUSIM-Gap in accordance with the received musim-GapRepetitionAndOffset. The musim-GapRepetition and Offset values ​​are provided according to the following conditions, and the first subframe of each periodic MUSIM gap occurs at an SFN (System Frame Number) and subframe of the NR PCell meeting the following conditions.

[0383] condition:

[0384] SFN mod T = FLOOR(Offset / 10);

[0385] subframe = Offset mod 10;

[0386] with T = musim-GapRepetition / 10;

[0387] ◆ For each periodic MUSIM gap, you can set the MUSIM gap priority configuration indicated by musim-GapPriority, if configured, for each periodic MUSIM gap.

[0388] ■ If musim-AperiodicGap is included

[0389] ◆ An aperiodic MUSIM gap configuration indicated by the musim-AperiodicGap in accordance with the received musim-Starting-SFN-AndSubframe can be set up. The first subframe of an aperiodic MUJSIM gap can occur in an SFN and subframe of the NR PCell that meets the following conditions:

[0390] condition:

[0391] SFN = starting-SFN;

[0392] Subframe = startingSubframe;

[0393] - If all collided MUSIM gaps are configured to be kept, musim-GapKeep can be set. That is, if the base station instructs musim-GapKeep (if musim-GapKeep is configured), the terminal can keep all collided MUSIM gaps and use them (use keep solution) without deciding which collided MUSIM gaps to use or not based on priority.

[0394] - if musim-GapConfig is set to release (else if musim-Gapconfig is set to release)

[0395] ■ The UE shall release the MUSIM gap configuration.

[0396] At step 1k-40, the USIM 1 terminal (1k-02) may transmit a predetermined RRC message (e.g., RRCReconfigurationComplete) to the base station 1 (1k-04) in response to step 1k-35.

[0397] At step 1k-45, the USIM 1 terminal (1k-02) can determine whether the MUSIM gaps set up at step 1k-35 collide. That is, if the MUSIM gap opportunities overlap on the time axis or the distance between the MUSIM gap opportunities is less than or equal to 4 ms, the terminal (1k-02) can determine that the corresponding MUSIM gaps collide.

[0398] At step 1k-50, a USIM 1 terminal (1k-02) with musim-GapKeep set can maintain all MUSIM gaps that collide at step 1k-45.

[0399] Note that steps 1k-45 and 1k-50 may be performed before step 1k-35.

[0400] In step 1k-60, the USIM 1 terminal (1k-02) may not perform transmission and reception operations with base station 1 (1k-04) during the MUSIM gap that it has decided to use. That is, if a MUSIM gap that it has decided to use without discarding occurs in step 1k-50, the terminal may not perform transmission and reception operations with base station 1 (1k-04) (e.g., NR serving cells) during the gap. On the other hand, in step 1k-55, the USIM 2 terminal (1k-03) may perform necessary operations during the MUSIM gap. That is, the USIM 2 terminal (1k-03) may perform necessary operations (e.g., cell selection or cell reselection operations) with base station 2 (1k-05).

[0401] A USIM 1 terminal (1k-02) according to the present disclosure can maintain and use periodic MUSIM gaps when a collision occurs between periodic MUSIM gaps or between aperiodic MUSIM gaps and periodic MUSIM gaps when musim-GapKeep is instructed. Therefore, unlike the embodiment described above (the embodiment illustrated in FIG. 1j), a USIM 2 terminal (1k-03) according to the present disclosure can successfully perform necessary operations during a MUSIM gap. For example, the USIM 2 terminal (1k-03) can successfully acquire system information broadcast by base station 2 (1k-05) without delay by using both aperiodic MUSIM gaps and periodic MUSIM gaps that collide.

[0402] Base station 1 (1k-04) according to the present disclosure can set musim-GapKeep to allow all MUSIM gaps that may collide with a USIM 1 terminal (1k-02) to be maintained and used. That is, even if a collision occurs between periodic MUSIM gaps or between an aperiodic MUSIM gap and a periodic MUSIM gap, the terminal can be set to maintain and use them.

[0403] FIG. 1l is a block diagram illustrating the internal structure of a terminal according to an embodiment of the present invention.

[0404] Referring to FIG. 1l, the terminal includes an RF (Radio Frequency) processing unit (1l-10), a baseband processing unit (1l-20), a storage unit (1l-30), and a control unit (1l-40).

[0405] The RF processing unit (11-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 (11-10) up-converts the baseband signal provided from the baseband processing unit (11-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 (11-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. In the drawing, only one antenna is illustrated, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (11-10) may include multiple RF chains. Furthermore, the RF processing unit (11-10) may perform beamforming. For the above beamforming, the RF processing unit (11-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.

[0406] The baseband processing unit (11-20) 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 (11-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (11-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (11-10). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (11-20) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols by performing an inverse fast Fourier transform (IFFT) operation and inserting a cyclic prefix (CP). In addition, when receiving data, the baseband processing unit (11-20) divides the baseband signal provided from the RF processing unit (11-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.

[0407] The baseband processing unit (11-20) and the RF processing unit (11-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (11-20) and the RF processing unit (11-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 (11-20) and the RF processing unit (11-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 (11-20) and the RF processing unit (11-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.

[0408] The storage unit (1l-30) stores data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (1l-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 (1l-30) provides the stored data at the request of the control unit (1l-40).

[0409] The above control unit (11-40) controls the overall operations of the terminal. For example, the control unit (11-40) transmits and receives signals through the baseband processing unit (11-20) and the RF processing unit (11-10). In addition, the control unit (11-40) records and reads data in the storage unit (11-40). For this purpose, the control unit (11-40) may include at least one processor. For example, the control unit (11-40) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.

[0410] Figure 1m is a block diagram showing the configuration of an NR base station according to one embodiment of the present invention.

[0411] Referring to FIG. 1m, the base station is configured to include an RF processing unit (1m-10), a baseband processing unit (1m-20), a backhaul communication unit (1m-30), a storage unit (1m-40), and a control unit (1m-50).

[0412] The RF processing unit (1m-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 (1m-10) up-converts the baseband signal provided from the baseband processing unit (1m-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 (1m-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 (1m-10) may include multiple RF chains. Furthermore, the RF processing unit (1m-10) may perform beamforming. For the above beamforming, the RF processing unit (1m-10) can adjust the phase and magnitude 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.

[0413] The baseband processing unit (1m-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 (1m-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (1m-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (1m-10). For example, in the case of OFDM, when transmitting data, the baseband processing unit (1m-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 (1m-20) divides the baseband signal provided from the RF processing unit (1m-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 (1m-20) and the RF processing unit (1m-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (1m-20) and the RF processing unit (1m-10) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0414] The above backhaul communication unit (1m-30) provides an interface for communicating with other nodes within the network. That is, the backhaul communication unit (1m-30) converts a bit string transmitted from the 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.

[0415] The storage unit (1m-40) stores data such as basic programs, application programs, and configuration information for the operation of the base station. In particular, the storage unit (1m-40) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (1m-40) can store information that serves as a basis for determining whether to provide or terminate multiple connections to a terminal. In addition, the storage unit (1m-40) provides the stored data at the request of the control unit (1m-50).

[0416] The control unit (1m-50) controls the overall operations of the base station. For example, the control unit (1m-50) transmits and receives signals through the baseband processing unit (1m-20) and the RF processing unit (1m-10) or through the backhaul communication unit (1m-30). In addition, the control unit (1m-50) records and reads data from the storage unit (1m-40). For this purpose, the control unit (1m-50) may include at least one processor.

[0417] It should be noted that the configuration diagrams, exemplary diagrams of control / data signal transmission methods, exemplary diagrams of operating procedures, and configuration diagrams illustrated in the above FIGS. 1A to 1M are not intended to limit the scope of the present disclosure. That is, not all components, entities, or operational steps described in the above FIGS. 1A to 1P should be construed as essential components for implementing the disclosure, and the disclosure may be implemented without detracting from its essence even if only some components are included.

[0418] The operations of the network entity or terminal described above can be realized by providing a memory device storing the corresponding program code within any component of the network entity or terminal device. That is, the control unit of the network entity or terminal device can execute the operations described above by reading and executing the program code stored in the memory device using a processor or CPU (Central Processing Unit).

[0419] The various components and modules of the network entity, base station or terminal device described in this specification may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates and application-specific semiconductors.

[0420] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. A method performed by a terminal of a wireless communication system, A step of transmitting a first message to a base station including information related to the terminal being able to set a MUSIM (multiple universal subscriber identity module) gap and a concurrent measurement gap together; and A method comprising the step of receiving, from the base station, a second message including at least one of setting information of the MUSIM gap and setting information of the simultaneous measurement gap, based on the above information.

2. In paragraph 1, A method characterized in that the preset measurement gap for positioning is not set together with the MUSIM gap or the simultaneous measurement gap.

3. In paragraph 1, Information associated with the ability of the terminal to set the MUSIM gap and the simultaneous measurement gap together is associated with information indicating whether the terminal can provide MUSIM assistance information for priority preference for periodic MUSIM gaps and support periodic MUSIM gap priority setting related thereto and support preference for maintaining conflicting MUSIM gaps, A method characterized in that information related to the ability of the terminal to set the MUSIM gap and the simultaneous measurement gap together is indicated by musim-GapPriorityPreference information.

4. In paragraph 1, A step of setting up at least one periodic MUSIM gap setting, when the setting information of the above MUSIM gap includes information for adding at least one periodic MUSIM gap; If the setting information of the above MUSIM gap includes information for adding an aperiodic MUSIM gap, a step for setting up an aperiodic MUSIM gap; and If information indicating that the terminal is allowed to maintain both conflicting MUSIM periodic and aperiodic gaps is set according to the setting information of the above MUSIM gap, the step of maintaining all conflicting MUSIM gaps is further included. A method characterized in that the information associated with the terminal being able to set the MUSIM gap and the simultaneous measurement gap together further indicates that the terminal prefers to maintain all conflicting MUSIM gaps.

5. A method performed by a base station of a wireless communication system, A step of receiving, from a terminal, a first message including information related to the terminal being able to set a MUSIM (multiple universal subscriber identity module) gap and a concurrent measurement gap together; and A method comprising the step of transmitting, to the terminal, a second message including at least one of setting information of the MUSIM gap and setting information of the simultaneous measurement gap, based on the above information.

6. In paragraph 5, A method characterized in that the preset measurement gap for positioning is not set together with the MUSIM gap or the simultaneous measurement gap.

7. In paragraph 5, Information associated with the ability of the terminal to set the MUSIM gap and the simultaneous measurement gap together is associated with information indicating whether the terminal can provide MUSIM assistance information for priority preference for periodic MUSIM gaps and support periodic MUSIM gap priority setting related thereto and support preference for maintaining conflicting MUSIM gaps, A method characterized in that information related to the ability of the terminal to set the MUSIM gap and the simultaneous measurement gap together is indicated by musim-GapPriorityPreference information.

8. In paragraph 5, The above MUSIM gap configuration information includes information for adding at least one periodic MUSIM gap, information for adding an aperiodic MUSIM gap, and information indicating that the terminal is allowed to maintain both colliding MUSIM periodic and aperiodic gaps. According to the setting information of the above MUSIM gap, at least one periodic MUSIM gap setting is set up, an aperiodic MUSIM gap setting is set up, and all conflicting MUSIM gaps are maintained. A method characterized in that the information associated with the terminal being able to set the MUSIM gap and the simultaneous measurement gap together further indicates that the terminal prefers to maintain all conflicting MUSIM gaps.

9. In the terminal of a wireless communication system, Transmitter and receiver; and Connected to the above transmitter and receiver, The terminal transmits to the base station a first message including information related to the ability to set a MUSIM (multiple universal subscriber identity module) gap and a concurrent measurement gap together, A terminal including a control unit that receives a second message including at least one of setting information of the MUSIM gap and setting information of the simultaneous measurement gap from the base station based on the above information.

10. In paragraph 9, A terminal characterized in that the preset measurement gap for positioning is not set together with the MUSIM gap or the simultaneous measurement gap.

11. In paragraph 9, Information associated with the ability of the terminal to set the MUSIM gap and the simultaneous measurement gap together is associated with information indicating whether the terminal can provide MUSIM assistance information for priority preference for periodic MUSIM gaps and support periodic MUSIM gap priority setting related thereto and support preference for maintaining conflicting MUSIM gaps, A terminal characterized in that information related to the ability of the terminal to set the MUSIM gap and the simultaneous measurement gap together is indicated by musim-GapPriorityPreference information.

12. In paragraph 9, the control unit, If the setting information of the above MUSIM gap includes information for adding at least one periodic MUSIM gap, setting up at least one periodic MUSIM gap, If the above MUSIM gap setting information includes information for adding an aperiodic MUSIM gap, set up the aperiodic MUSIM gap setting, If information indicating that the terminal is allowed to maintain both conflicting MUSIM periodic and aperiodic gaps is set according to the setting information of the above MUSIM gap, all conflicting MUSIM gaps are maintained, A terminal characterized in that the information associated with the terminal being able to set the MUSIM gap and the simultaneous measurement gap together further indicates that the terminal prefers to maintain all conflicting MUSIM gaps.

13. In a base station of a wireless communication system, Transmitter and receiver; and Connected to the above transmitter and receiver, Receives from a terminal a first message including information related to the terminal being able to set a MUSIM (multiple universal subscriber identity module) gap and a concurrent measurement gap together, A base station including a control unit that transmits a second message including at least one of setting information of the MUSIM gap and setting information of the simultaneous measurement gap to the terminal based on the above information.

14. In paragraph 13, The preset measurement gap for positioning is not set together with the MUSIM gap or the simultaneous measurement gap, Information associated with the ability of the terminal to set the MUSIM gap and the simultaneous measurement gap together is associated with information indicating whether the terminal can provide MUSIM assistance information for priority preference for periodic MUSIM gaps and support periodic MUSIM gap priority setting related thereto and support preference for maintaining conflicting MUSIM gaps, A base station, characterized in that information related to the terminal being able to set the MUSIM gap and the simultaneous measurement gap together is indicated by musim-GapPriorityPreference information.

15. In paragraph 13, The above MUSIM gap configuration information includes information for adding at least one periodic MUSIM gap, information for adding an aperiodic MUSIM gap, and information indicating that the terminal is allowed to maintain both colliding MUSIM periodic and aperiodic gaps. According to the setting information of the above MUSIM gap, at least one periodic MUSIM gap setting is set up, an aperiodic MUSIM gap setting is set up, and all conflicting MUSIM gaps are maintained. A base station characterized in that the information associated with the terminal being able to set the MUSIM gap and the simultaneous measurement gap together further indicates that the terminal prefers to maintain all colliding MUSIM gaps.

Images