Method and device for transmitting information related to terminal capability by terminal in mobile communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a user equipment (UE) in a wireless communication system may comprise the steps of: receiving a radio resource control (RRC) message including needForGAPSConfigNR information from a base station; identifying that the UE is configured to provide measurement gap information of at least one target new radio (NR) band when the needForGAPSConfigNR information is configured as setup; transmitting first UEAssistanceInformation including first measurement gap information to the base station; and when the UE is configured to provide the measurement gap information of the at least one target NR band and current measurement gap information is different from the first measurement gap information, transmitting second UEAssistanceInformation including the current measurement gap information to the base station, wherein the needForGapsConfigNR information includes information on the at least one target NR band.

Description

Method and device for transmitting information related to terminal capabilities in a mobile communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting information related to terminal capabilities by 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] According to one embodiment of the present disclosure, a device and method for effectively providing a service in a mobile communication system are provided.

[0009] According to one embodiment of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system includes the steps of: receiving, from a base station, an RRC (radio resource control) message including needForGapsConfigNR information; identifying, when the needForGapsConfigNR information is set to setup, that the UE is configured to provide measurement gap information of at least one target NR band; transmitting, to the base station, a first UEAssistanceInformation including first measurement gap information; and transmitting, to the base station, a second UEAssistanceInformation including current measurement gap information when the UE is configured to provide measurement gap information of the at least one target NR band and current measurement gap information is different from the first measurement gap information, wherein the needForGapsconfigNR information may include information on at least one target new radio (NR) band.

[0010] According to one embodiment of the present disclosure, a device and method for effectively providing a service in a wireless communication system can be provided.

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

[0012] FIG. 1a is a diagram illustrating the structure of a long term evolution (LTE) system according to one embodiment.

[0013] FIG. 1b is a diagram illustrating a wireless protocol structure in an LTE system according to one embodiment.

[0014] FIG. 1c is a diagram illustrating the structure of a mobile communication system according to one embodiment.

[0015] FIG. 1d is a diagram illustrating a wireless protocol structure of a mobile communication system according to one embodiment.

[0016] FIG. 1e is a flowchart illustrating a process in which a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple Universal Subscriber Identity Modules (USIMs) according to an embodiment requests / provides temporary UE capability restrictions to a base station according to the settings of the base station.

[0017] FIG. 1f is a flowchart illustrating a process in which a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple Universal Subscriber Identity Modules (USIMs) according to an embodiment requests / provides temporary UE capability restrictions to a base station according to the settings of the base station.

[0018] FIG. 1g is a flowchart illustrating a process in which a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple Universal Subscriber Identity Modules (USIMs) according to an embodiment requests / provides temporary UE capability restrictions to a base station according to the settings of the base station.

[0019] FIG. 1h is a flowchart illustrating a process in which a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple Universal Subscriber Identity Modules (USIMs) according to an embodiment requests / provides temporary UE capability restrictions to a base station according to the settings of the base station.

[0020] FIG. 1i is a block diagram illustrating the internal structure of a terminal according to one embodiment.

[0021] FIG. 1j is a block diagram showing the configuration of an NR base station according to one embodiment.

[0022] The operating principles of the present disclosure are described in detail below with reference to the attached drawings. In the following description of the present disclosure, detailed descriptions of known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present 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.

[0023] An embodiment of the present invention is described below with reference to the attached drawings.

[0024] In the following description, terms used to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and / or terms referring to various identification information are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0025] 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 disclosure is not limited to the above-described terms and names, and can be equally applied to systems conforming to other standards. In the present disclosure, the term eNB (evolved Node B) may be used interchangeably with gNB (next generation Node B) for convenience of explanation. For example, a base station described as an eNB may be replaced with a gNB.

[0026] FIG. 1a is a diagram illustrating the structure of an LTE system according to one embodiment.

[0027] Referring to FIG. 1a, a wireless access network of an LTE system according to an embodiment may be composed of next-generation base stations (Evolved Node Bs, hereinafter referred to as 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 (UE or terminal) (1a-35) may access an external network through the ENBs (1a-05 to 1a-20) and the S-GW (1a-30).

[0028] According to one embodiment, ENBs (1a-05, 1a-10, 1a-15, 1a-20) in FIG. 1a may correspond to existing Node Bs of a universal mobile telecommunication system (UMTS) system. For example, ENBs (1a-05, 1a-10, 1a-15, 1a-20) are connected to UEs (1a-35) via a wireless channel and may 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, so a device that collects status information such as buffer status, available transmission power status, and channel status of UEs and performs scheduling may be required. In this case, ENBs (1a-05 to 1a-20) may be responsible for collecting status information and performing scheduling.

[0029] In one embodiment, a single ENB can typically control multiple cells. For example, to achieve 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. For example, the LTE system may apply an adaptive modulation and coding (AMC) method that determines a modulation scheme and channel coding rate according to the channel conditions of the terminal.

[0030] According to one embodiment, the S-GW (1a-30) is a device that provides data bearers and can create or remove data bearers under the control of the MME (1a-25). For example, the MME (1a-25) is a device that is responsible for various control functions as well as mobility management functions for terminals and can be connected to multiple base stations.

[0031] FIG. 1b is a diagram illustrating a wireless protocol structure in an LTE system according to one embodiment.

[0032] Referring to FIG. 1b, the wireless protocol of the LTE system according to one embodiment may be composed 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 the eNB, respectively. PDCP (Packet Data Convergence Protocol) (1b-05, 1b-40) is responsible for operations such as IP header compression / decompression. For example, the main function of PDCP may include at least one of the following functions.

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

[0034] - User data transfer function

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

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

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

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

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

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

[0041] According to one embodiment, Radio Link Control (RLC) (1b-10, 1b-35) can reconfigure PDCP Packet Data Unit (PDU) to an appropriate size and perform ARQ operation, etc. For example, the main function of RLC can include at least one of the following functions.

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

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

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

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

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

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

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

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

[0050] - RLC re-establishment function

[0051] According to one embodiment, MAC (1b-15, 1b-30) is connected to multiple RLC layer devices configured in one terminal, and can perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC may include at least one of the following functions.

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

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

[0054] - Scheduling information reporting function

[0055] - HARQ (hybrid automatic repeat request) function (Error correction through HARQ)

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

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

[0058] - MBMS (Multimedia Broadcast Multicast. Service) service identification function (MBMS service identification)

[0059] - Transport format selection function

[0060] - Padding function

[0061] According to one embodiment, the physical layer (1b-20, 1b-25) may perform an operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.

[0062] FIG. 1c is a diagram illustrating the structure of a next-generation mobile communication system according to one embodiment.

[0063] Referring to FIG. 1c, a wireless access network of a next-generation mobile communication system (hereinafter referred to as NR or 2g) according to an embodiment may be composed of a next-generation base station (New Radio Node B, hereinafter referred to as NR 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) may access an external network through the NR gNB (1c-10) and the NR CN (1c-05).

[0064] According to one embodiment, the NR gNB (1c-10) may correspond to an eNB (Evolved Node B) of an existing LTE system. For example, the NR gNB is connected to an NR UE (1c-15) via a wireless channel and may provide superior services than an existing Node B (e.g., eNB).

[0065] According to one embodiment, in a next-generation mobile communication system, since all user traffic is serviced through a shared channel, a device may be required to collect status information such as buffer status, available transmission power status, and channel status of UEs and perform scheduling. The NR NB (1c-10) may be responsible for collecting status information and performing scheduling.

[0066] In one embodiment, a single NR gNB can typically control multiple cells. Next-generation mobile communication systems may exceed the existing maximum bandwidth to achieve ultra-high-speed data transmission compared to current LTE. In next-generation mobile communication systems, orthogonal frequency division multiplexing (OFDM) may be used as a wireless access technology, and beamforming technology may be additionally incorporated.

[0067] For example, an adaptive modulation and coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel status of the terminal may be applied. The NR CN (1c-05) may perform functions such as mobility support, bearer setup, and / or QoS (quality of service) setup. For example, the NR CN may be a device that is responsible for various control functions as well as mobility management functions for the terminal and may be connected to multiple base stations. In addition, the next-generation mobile communication system may also be interoperable with the existing LTE system, and the NR CN may be connected to the MME (1c-25) via a network interface. The MME may be connected to an existing base station, eNB (1c-30).

[0068] FIG. 1d is a diagram illustrating a wireless protocol structure of a next-generation mobile communication system according to one embodiment.

[0069] Referring to FIG. 1d, the wireless protocol of the next-generation mobile communication system according to one embodiment may be composed of NR SDAP (service data adaptation protocol) (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), NR RLC (1d-10, 1d-35), and / or NR MAC (1d-15, 1d-30) in the terminal and the NR base station, respectively.

[0070] According to one embodiment, the main functions of NR SDAP (1d-01, 1d-45) may include at least some of the following functions:

[0071] - Transfer of user plane data

[0072] - Mapping function between QoS flow and data bearer for both DL (downlink) and UL (uplink)

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

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

[0075] For an SDAP layer device, the terminal can be configured via an RRC (radio resource control) message for each PDCP layer device, each bearer, or each logical channel to use the header of the SDAP layer device. For an SDAP layer device, the terminal can be configured via an RRC (radio resource control) message for each PDCP layer device, each bearer, or each logical channel to use the function of the SDAP layer device. When the SDAP header is set, the SDAP layer device can instruct the terminal to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink through a 1-bit indicator for non-access stratum (NAS) QoS reflection configuration (NAS reflective QoS) and a 1-bit indicator for AS QoS reflection configuration (AS reflective QoS) in the SDAP header. For example, the SDAP header can include QoS flow ID information indicating QoS. For example, QoS information can be used as data processing priority and / or scheduling information to support smooth service.

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

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

[0078] - User data transfer function

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

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

[0081] - PDCP PDU reordering for reception

[0082] - Duplicate detection of lower layer SDUs

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

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

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

[0086] The reordering function of an NR PDCP device refers to the 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. As another example, the reordering function of an NR PDCP device may include a function of transmitting data directly without considering the order, and a function of recording lost PDCP PDUs by reordering the order. As another example, the reordering function of an NR PDCP device may include a function of reporting a status on lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of lost PDCP PDUs.

[0087] The main functions of NR RLC(1d-10, 1d-35) may include at least some of the following functions:

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

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

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

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

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

[0093] - Re-segmentation of RLC data PDUs

[0094] - Reordering of RLC data PDUs

[0095] - Duplicate detection function

[0096] - Protocol error detection

[0097] - RLC SDU discard function

[0098] - RLC re-establishment function

[0099] According to one embodiment, the in-sequence delivery function of an NR RLC device may be referred to as a function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. The in-sequence delivery function of an NR RLC device may include a function of reassembling and delivering multiple RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs. The in-sequence delivery function of an NR RLC device may include a function of reordering received RLC PDUs based on an RLC SN (sequence number) or a PDCP SN (sequence number). The in-sequence delivery function of an NR RLC device may include a function of recording lost RLC PDUs by rearranging the order. The in-sequence delivery function of an NR RLC device may include a function of transmitting a status report on lost RLC PDUs to the transmitting side. The in-sequence delivery function of an NR RLC device may include a function of requesting retransmission of lost RLC PDUs. The in-sequential delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer only the RLC SDUs up to the lost RLC SDU when there is a lost RLC SDU. The in-sequential delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer all RLC SDUs received before the timer starts if a predetermined timer has expired even if there is a lost RLC SDU. The in-sequential delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer all RLC SDUs received up to the present if a predetermined timer has expired even if there is a lost RLC SDU (service data unit).

[0100] According to one embodiment, the NR RLC device (1d-10, 1d-35) may process the RLC PDUs in the order in which they are received (in the order of arrival, regardless of the order of the sequence number) and deliver them to the PDCP device out of order (out-of-sequence delivery). In the case of segments, the NR RLC device (1d-10, 1d-35) may receive segments stored in a buffer or to be received later, reconstruct them into a complete RLC PDU, process them, and deliver them to the PDCP device. For example, the NR RLC layer may not include a concatenation function, and the concatenation function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

[0101] The out-of-sequence delivery function of an NR RLC device can be referred to as the function of directly delivering RLC SDUs received from a lower layer to the upper layer, regardless of the order. The out-of-sequence delivery function may include the function of reassembling and delivering multiple RLC SDUs when an original RLC SDU is received fragmented into multiple RLC SDUs. The out-of-sequence delivery function may include the function of storing and reordering the RLC SN or PDCP SN of the received RLC PDUs to record any lost RLC PDUs.

[0102] According to one embodiment, the NR MAC (1d-15, 1d-30) may be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of the NR MAC may include at least some of the following functions.

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

[0104] - Multiplexing / demultiplexing of MAC SDUs

[0105] - Scheduling information reporting function

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

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

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

[0109] - MBMS service identification function

[0110] - Transport format selection function

[0111] - Padding function

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

[0113] FIG. 1e is a flowchart illustrating a process in which a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple Universal Subscriber Identity Modules (USIMs) according to an embodiment requests and / or provides temporary UE capability restrictions to a base station according to the settings of the base station.

[0114] Referring to FIG. 1e, a MUSIM terminal (1e-01) according to one embodiment may be referred to as a terminal supporting multiple USIMs in a single device. For convenience of explanation, the present disclosure will be described based on a Dual-USIM terminal supporting two USIMs. However, this is merely an example, and the MUSIM terminal of the present disclosure may support three or more USIMs.

[0115] According to one embodiment, a MUSIM terminal (1e-01) may be referred to as a USIM 1 terminal (1e-02) when operating on USIM 1, and may be referred to as a USIM 2 terminal (1e-03) when operating on USIM 2. At this time, the base stations (1e-04, 1e-05) associated with each USIM may recognize the USIM 1 terminal (1e-02) and the USIM 2 terminal (1e-03) as separate terminals rather than the MUSIM terminal (1e-01) operating on the same device. For example, the base stations (1e-04, 1e-05) may identify the USIM 1 terminal (1e-2) and the USIM 2 terminal (1e-03) as different terminals.

[0116] According to one embodiment, the USIM 1 terminal (1e-02) and the USIM 2 terminal (1e-03) can share and use the hardware capabilities of the USIM terminal (1e-01). Therefore, when the USIM 1 terminal (1e-02) and the USIM 2 terminal (1e-03) simultaneously transmit and / or receive signals to and from base station 1 (1e-04) and base station 2 (1e-05), the capabilities of each USIM terminal may be temporarily limited by the other. For example, even if the USIM 1 terminal (1e-02) and the USIM 2 terminal (1e-03) are identified as each other's terminals by the base station, the USIM 1 terminal (1e-02) and the USIM 2 terminal (1e-03) can utilize hardware resources (e.g., an application processor (AP), a communication processor (CP), and / or a transceiver) included in one device. In this case, if the USIM 1 terminal and the USIM 2 terminal transmit and / or receive signals simultaneously, temporary limitations may occur in the USIM terminal capabilities.

[0117] According to one embodiment, at step 1e-10, the USIM 1 terminal (1e-02) may establish an RRC connection with base station 1 (1e-04) and be in RRC connected mode (RRC_CONNECTED).

[0118] According to one embodiment, at step 1e-11, the USIM 2 terminal (1e-03) may establish an RRC connection with the base station 2 (1e-05) and be in RRC connected mode (RRC_CONNECTED).

[0119] According to one embodiment, at step 1e-15, the USIM 1 terminal (1e-02) may transmit a terminal capability information message (UECapabilityInformation) containing or including capability information of the MUSIM terminal (1e-01) to the base station 1 (1e-04). For example, the capability of the MUSIM terminal (1e-01) is static, but since the USIM 1 terminal (1e-02) shares the capability of the MUSIM terminal (1e-01) with the USIM 2 terminal (1e-03), the capability of the USIM 1 terminal (1e-02) may be temporarily restricted depending on the operation of the USIM 2 terminal (1e-03). That is, even if the capability of the USIM 1 terminal (1e-02) is fixed, the capability may be temporarily limited because the USIM 1 terminal (1e-02) shares hardware with the USIM 2 terminal (1e-03).

[0120] Accordingly, the USIM 1 terminal (1e-02) may include capability information related to such temporary terminal capability constraints in a message (e.g., UECapabilityInformation) and transmit it to the base station 1 (1e-04). For example, the message (e.g., UECapabilityInformation) may include at least some of the following information:

[0121] - Information about the ability of USIM 1 terminal (1e-02) to request or provide details of temporary UE capability restrictions to base station 1 (1e-04) through a specific RRC message (e.g., UEAssistanceInformation).

[0122] * The ability of the base station (1e-04) to transmit to the base station 1 (1e-04) a predetermined RRC message including preference information (e.g., information related to specific temporary terminal capability restrictions) that changes some of the information currently set for the USIM 1 terminal (1e-02) due to temporary restrictions on the capability of the USIM 1 terminal (1e-02) by the USIM 2 terminal (1e-03), according to the settings of the base station 1 (1e-04) (i.e., capability information on whether the terminal can report to the base station (1e-04) information (or parameters) that must be changed when a limitation occurs in the capability of the USIM 1 terminal (1e-02) among the information set by the base station (1e-04). For example, the preference information can be referenced as configuration information that the USIM 1 terminal (1e-02) with limited capabilities can support.

[0123] - Information on the ability of USIM 1 terminal (1e-02) to proactively notify base station 1 (1e-04) of temporary terminal capability restrictions through a specific RRC message (e.g., RRCSetupComplete, RRCResumeComplete, RRCReconfigurationComplete, RRCReestablishmentComplete).

[0124] * When the capability of USIM 1 terminal (1e-02) is temporarily restricted by USIM 2 terminal (1e-03), USIM 1 terminal (1e-02) has the ability to transmit a predetermined RRC message including an indicator indicating whether the capability is temporarily restricted to base station 1 (1e-04) according to the settings of base station 1 (1e-04).

[0125] According to one embodiment, at step 1e-20, base station 1 (1e-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration message) including configuration information (musim-CapabilityRestrictionConfig) that allows a USIM1 terminal (1e-02) to report preferred / required temporary terminal capability restriction information to base station 1 (1e-04). For example, the configuration information (e.g., musim-CapabilityRestrictionConfig) may be stored in otherConfig. For example, the configuration information (e.g., musim-CapabilityRestrictionConfig) may include at least one of the following information: OtherConfig(musim-CapabilityRestrictionConfig)

[0126] - Measurement gap requirement constraint request / change setting information

[0127] * An indicator or new prohibit timer value indicating whether the USIM 1 terminal (1e-02) may transmit preferred measurement gap requirement constraint information to base station 1 (1e-04) due to MUSIM operation. For example, the preferred measurement gap requirement constraint information may include measurement gap information that the USIM 1 terminal (1e-02) can support even if the capability of the USIM 1 terminal (1e-02) is restricted. For example, the preferred measurement gap requirement constraint information may include information about a measurement gap that is restricted when the capability of the USIM 1 terminal is restricted.

[0128] - An indicator or Wait timer Txx value indicating whether the USIM 1 terminal (1e-02) may send a release request or a preference information that the release request is no longer needed (i.e., cancel the release request) for at least one of the following information set by the base station 1 (1e-04) to the MUSIM 1 terminal (1e-02) due to MUSIM operation.

[0129] * Preference information for requesting release of the current serving cell and / or serving cell group, or preference information that a release request for the same is no longer needed.

[0130] * Preference information for MIMO (multi-input multi-output) layers for the current serving cell and / or serving cell group, or preference information that preference information for the same is no longer needed.

[0131] ** Preference information for MIMO layers is separate for uplink and downlink (or, preference information for MIMO layers can be applied separately for uplink and downlink)

[0132] * The Txx Wait timer value can be set to at least one of the specified integer values.

[0133] - MUSIM candidate frequency band list (e.g. musim-candidateBandList) configuration information that should be referenced when USIM 1 terminal (1e-01) sends preference information for MUSIM affected frequency band list (e.g. musim-AffectedBandCombList) and / or MUSIM restricted frequency band list (e.g. musimForbiddenBandCombList) to base station 1 (1e-04) due to MUSIM operation.

[0134] * musim-CandidateBandList may contain one or more FreqBandIndicatorNR information.

[0135] - Txy Prohibit timer value that can be applied when USIM 1 terminal (1e-01) sends preference information for musim-AffectedBandCombList and / or musimForbiddenBandCombList to base station 1 (1e-04) due to MUSIM operation.

[0136] * musim-AffectedBandCombList may consist of one or more MUSIM-AffectedBandCombs, and each MUSIM-AffectedBandComb may contain at least one of an integer value indicating specific FreqBandIndicatorNR information included in musim-CandidateBandList, a musim-MIMO-Layer-UL value, a musim-MIMO-Layer-DL value, or Bandwidth restriction information.

[0137] * Musim-ForbiddenBandCombList may consist of one or more MUSIM-ForbiddenBandCombs, and each MUSIM-ForbiddenBandComb may contain integer values ​​indicating at least one FreqBandIndicatorNR information contained in musim-CandidateBandList.

[0138] - An indicator indicating whether the USIM 1 terminal (1e-02) can proactively notify the base station 1 (1e-04) of temporary terminal capability restrictions through a predetermined RRC message transmitted to the base station 1 (1e-04) after transitioning to the RRC connection mode or a predetermined RRC message transmitted in the RRC connection mode.

[0139] According to one embodiment, at step 1e-25, base station 1 (1e-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing RRC configuration information to USIM 1 terminal (1e-02). The message (e.g., RRCReconfiguration) may include at least some of the following RRC configuration information: RRCReconfiguration (sCellToAddModList, mrdc-SecondaryCellGroup for DC)

[0140] - List of SCells (Serving Cell, secondary cell) to be added or modified for MN (Master Node) (sCellToAddModList)

[0141] * Each SCell may contain at least one of the following configuration information:

[0142] ** sCellIndex: A short identifier that identifies the SCell.

[0143] ** servingCellConfigCommon: Configuration information containing cell-specific parameters for the terminal's serving cell.

[0144] ** PCI (physical cell ID) information

[0145] ** Downlink setting information and / or Uplink setting information commonly applied to each cell

[0146] *** For example, the Downlink configuration information commonly applied to each cell may include at least one of frequencyInfoDL, initialDownlinkBWP, or initialDownlink-RedCap.

[0147] *** For example, the Uplink configuration information commonly applied to each cell may mean at least one of frequencyInfoUL and initialUplink BWP.

[0148] ** servingCellConfig: Configuration information for serving cells per terminal

[0149] *** For example, the configuration information for the serving cell per terminal may mean at least one of the initial Downlink BWP configuration information, downlinkBW-ToAddModList, firstActiveDownlinkBWP-Id, defaultDownlinkBWP-Id, uplinkConfig, and supplementaryUplink.

[0150] ** smtc: SSB cycle / offset / period setting information for target cell when adding NR Cell

[0151] ** sCellState: Indicator indicating whether the sCell state is enabled.

[0152] ** plmn-IdentityInfoList and / or npn-IdentityInfoList configuration information

[0153] - Information to add / modify SN (Secondary Node)

[0154] * For example, information to add / modify SN (Secondary Node) may refer to mrdc-SecondaryCellGroup configuration information. Specifically, information to add / modify SN (Secondary Node) may refer to configuration information including RRCReconfiguration for NR-DC, and configuration information including RRCConnectionReconfiguration for NE-DC.

[0155] ** Information for adding / modifying a SN (Secondary Node) may include configuration information (e.g., CellGroup) for configuring a Secondary cell group (SCG). In this case, CellGroupConfig may include at least some of the following information.

[0156] *** cellGroupId: An identifier that identifies the cell group.

[0157] *** spCellConfig: Configuration information for PSCell (Primary Secondary Cell)

[0158] *** List of SCells (Serving Cells) to add or modify for SN (Secondary Node) (sCellToAddModList)

[0159] For reference, the ASN.1 structure for the above-described RRC message (e.g., RRCReconfiguration) may be as shown in [Table 1].

[0160]

[0161]

[0162]

[0163]

[0164]

[0165]

[0166]

[0167]

[0168]

[0169] According to one embodiment, in step 1e-30, the USIM 1 terminal (1e-02) may transmit a predetermined RRC message (e.g., RRCReconfigurationComplete) to the base station 1 (1e-04) in response to a predetermined RRC message received in step 1e-35. (UEAssistanceInformation(musim-CapabilityRestriction i.e., SCellIndex or indicator to release SCG)

[0170] According to one embodiment, in step 1e-35, a USIM 1 terminal (1e-02) configured to provide information on temporary capability restriction may transmit a predetermined RRC message (e.g., UEAssistanceInformation) including temporary terminal capability restriction information (e.g., musim-CapabilityRestriction) due to the operation of a USIM 2 terminal (1e-03) to base station 1 (1e-04). For example, the USIM 1 terminal (1e-01) may transmit a predetermined RRC message (e.g., UEAssistanceInformation) including temporary terminal capability restriction information (musim-CapabilityRestriction) to base station 1 (1e-04) if at least one of the following conditions is satisfied.

[0171] - Condition 1: If the UE has a preference on the temporary capability restriction and the UE did not transmit a UEAssistanceInformation message with musim-CapRestriction since it was configured to provide MUSIM assistance information for temporary capability restriction, the meaning of the USIM 1 terminal having a preference for temporary capability restriction may practically mean that there is a setting that the USIM 1 terminal can support or that can be set for the USIM 1 terminal when a temporary capability restriction occurs.

[0172] * At this time, the terminal can drive or restart the T3xx timer with the T3xx value set by the base station.

[0173] * At this time, the terminal can drive or restart the T3xy timer with the T3xy value set by the base station.

[0174] * At this time, the terminal may initiate a procedure for transmitting a terminal assistance information message to provide current MUSIM assistance information including temporary terminal capability information. For example, the terminal may perform the following procedure. If the UE has a preference for temporary terminal capability restriction information,

[0175] ** if the UE has a preference to indicate band(s) or combination of band(s) for which capabilities are restricted and if there is at least one combination of bands compromising of at least one band that is indicated in musim-candidateBandList

[0176] *** The UE may include the musim-AffectedBandCombList the UE prefers to be configured in the UE Assistance Information message.

[0177] *** The terminal may include the bandEntryIndex for each band for each combination of bands for which terminal capabilities are restricted in the terminal assistance information message.

[0178] *** A terminal may include terminal restriction information for the bands indicated in musim-candidateBandList in musim-CapabilityRestricted for the combination of bands for which terminal capabilities are restricted. (Include the musim-capabilityRestricted for the bands indicated in musim-candidateBandList with restricted capability together for the combination of bands for which capabilities are restricted)

[0179] ** if the UE has a preference to indicate combination of bands to be avoided and if there is at least one combination of bands comprising at least one band that is indicated in musim-candidateBandList

[0180] *** The UE may include the musim-ForbiddenBandCombList that it prefers not to be configured in the UE Assistance Information message.

[0181] *** The terminal may include the musim-ForbiddenBandComb for the corresponding combinations of bands in the terminal assistance information message.

[0182] *** A terminal may include a bandEntryIndex for each band for each combination of bands to be avoided in the terminal assistance information message.

[0183] ** if the UE has a preference for serving cell(s) and / or SCG to release

[0184] *** musim-Cell-SCG-ToRelease may be included.

[0185] *** The terminal may include the preferred serving cell(s) to be released in musim-CellToRelease. In this case, the information included in musim-CellToRelease may be ScellIndex.

[0186] *** The terminal has a preferred SCG to release, and can set scg-ReleasePreference with scg-ReleasePreferred. In other words, scg-ReleasePreferred is information that only indicates whether or not the terminal prefers to release SCGs in the ENUMERATED format.

[0187] ** If the UE has a preference to indicate the affected capabilities for the serving cells

[0188] *** The UE may include the musim-CellToAffectList the UE prefers not to be configured in the UE Assistance Information message.

[0189] *** The terminal may include at least one of musim-ServCellIndex, musim-MIMO-Layer-DL, musim-MIMO-Layers-UL, or information about bandwidth restriction (UL and / or DL) in the terminal assistance information message, which indicates information about capability constraints for the corresponding serving cell.

[0190] - Condition 2: If the current musim-CapabilityRestriction is different from the one indicated in the last transmission of the UEAssistanceInformation message including musim-CapRestriction for affected capability for serving cell(s) or serving cell(s) release or SCG release and timer T3xx is not running.

[0191] * At this time, the UE may initiate a procedure to transmit a UE assistance information message to provide the current musim-Cell-SCG-ToRelease and / or musim-CellToAffectList. For example, the UE may perform the following procedure: If the UE has a preference for temporary capability restriction information,

[0192] ** if the UE has a preference for serving cell(s) and / or SCG to release

[0193] *** The terminal auxiliary information message may include musim-Cell-SCG-ToRelease.

[0194] *** The terminal can enter the preferred serving cell(s) to be released in musim-CellToRelease. The information included here is ScellIndex.

[0195] *** The terminal has a preferred SCG to release, and can set scg-ReleasePreference to scg-ReleasePreferred. In other words, scg-ReleasePreference can be information that only indicates whether or not the terminal prefers to release SCGs in the ENUMERATED format.

[0196] ** If the UE has a preference to indicate the affected capabilities for the serving cells

[0197] *** The UE may include the musim-CellToAffectList that the UE prefers not to be configured in the UE Assistance Information message.

[0198] *** The terminal may include at least one of musim-ServCellIndex, musim-MIMO-Layer-DL, musim-MIMO-Layers-UL, or information about bandwidth restriction (UL and / or DL) in the terminal assistance information message, which indicates information about capability constraints for the corresponding serving cell.

[0199] * At this time, the terminal can drive or restart the T3xx timer with the T3xx value set by the base station.

[0200] - Condition 3: If the current musim-CapabilityRestriction is different from the one indicated in the last transmission of the UEAssistanceInformation message including musim-CapRestriction for constraint band combination(s) and timer T3xy is not running.

[0201] * At this time, the UE may initiate a procedure to transmit a UE assistance information message to provide the current musim-AffectedBandCombList and / or musim-ForbiddenBandCombList. For example, the UE may perform the following procedure: If the UE has a preference for temporary capability restriction information,

[0202] ** if the UE has a preference to indicate band(s) or combination of band(s) for which capabilities are restricted and if there is at least one combination of bands compromising of at least one band that is indicated in musim-candidateBandList

[0203] *** The UE may include the musim-AffectedBandCombList that it prefers to be configured in the UE Assistance Information message.

[0204] *** A terminal may include a bandEntryIndex for each band in the terminal assistance information message for each combination of bands whose capabilities are restricted.

[0205] *** A terminal may include terminal restriction information for the bands indicated in musim-candidateBandList in musim-CapabilityRestricted for the combination of bands for which terminal capabilities are restricted. (Include the musim-capabilityRestricted for the bands indicated in musim-candidateBandList with restricted capability together for the combination of bands for which capabilities are restricted)

[0206] ** if the UE has a preference to indicate combination of bands to be avoided and if there is at least one combination of bands comprising at least one band that is indicated in musim-candidateBandList

[0207] *** The UE may include the musim-ForbiddenBandCombList that it prefers not to be configured in the UE Assistance Information message.

[0208] *** The terminal may include the musim-ForbiddenBandComb for the corresponding combinations of bands.

[0209] *** A terminal may include a bandEntryIndex for each band for each combination of bands to be avoided in the terminal assistance information message.

[0210] * At this time, the terminal can drive or restart the T3xy timer with the T3xy value set by the base station.

[0211] For reference, if the UE has no longer preference for temporary capability restriction, the UE may transmit the temporary UE capability restriction preference to the musim-CapabilityRestriction in the musim-Assistance IE to the base station 1 (1e-04). That is, if the USIM 1 UE (1e-02) previously included information A in the musim-Assistance IE but no longer needs the preference A, the UE may not include information A in the musim-Assistance IE.

[0212] According to one embodiment, in step 1e-40, base station 1 (1e-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing RRC configuration information based on temporary terminal capability constraint information provided by USIM 1 terminal (1e-02) in response to step 1e-35. For example, if the temporary terminal capability constraint provided in step 1e-35 is resolved through the received RRC message, USIM 1 terminal (1e-02) may stop the T3xx timer started in step 1e-41. (stop timer T3xx)

[0213] According to one embodiment, at step 1e-45, the USIM 1 terminal (1e-02) may transmit a predetermined RRC message (e.g., RRCReconfigurationComplete) to the base station 1 (1e-04) in response to a predetermined RRC message received at step 1e-40.

[0214] In the present disclosure, when a USIM 1 terminal (1e-02) transmits a preference request for SCell release to a base station 1 (1e-04) via a terminal assistance information message, it may transmit SCellIndex to indicate the request for SCell release. In this case, since the terminal and the base station only remember the most recently sent terminal assistance information message, they cannot know which specific RRC setting the SCell indicated by SCellIndex is configured with or on which frequency the SCell is operated. This may be because the SCellIndex information only indicates a specific integer value from 1 to 31. In addition, there is a limitation that the base station cannot add another cell to the terminal using the same SCellIndex unless the terminal sends a terminal assistance information message to the base station that does not include the SCellIndex that was previously indicated to the base station via the terminal assistance information message. If a terminal makes a preference request for the release of multiple SCells by indicating multiple SCellIndexes in a terminal assistance information message, the base station may also encounter a limitation in that it cannot add additional SCells to the terminal.

[0215] In the present disclosure, when a USIM 1 terminal (1e-02) transmits a preference request for SCG release to a base station (1e-04) as a terminal assistance information message, only an indicator indicating an SCG release preference request may be sent to indicate the preference request for SCG release. Since the terminal and the base station only remember the most recently sent terminal assistance information message, there is a characteristic that they cannot know which RRC setting is specifically configured for the PSCell belonging to the corresponding SCG indicated by the SCG release indicator, or at which frequency the corresponding PSCell operates.

[0216] FIG. 1f is a flowchart illustrating a process in which a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple Universal Subscriber Identity Modules (USIMs) according to an embodiment requests and / or provides temporary UE capability restrictions to a base station according to the settings of the base station.

[0217] Referring to FIG. 1f, a MUSIM terminal (1f-01) according to one embodiment may be referred to as a terminal supporting multiple USIMs in a single device. In the present disclosure, for convenience of explanation, a Dual-USIM terminal supporting two USIMs is described.

[0218] For example, a MUSIM terminal (1f-01) may be referred to as a USIM 1 terminal (1f-02) when operating on USIM 1, and may be referred to as a USIM 2 terminal (1f-03) when operating on USIM 2. In this case, the base stations (1f-04, 1f-05) associated with each USIM may recognize or identify the USIM 1 terminal (1f-02) and the USIM 2 terminal (1f-03) as separate terminals rather than the MUSIM terminal (1f-01) operating on the same device.

[0219] According to one embodiment, the USIM 1 terminal (1f-02) and the USIM 2 terminal (1f-03) may share the hardware capabilities (or hardware (e.g., CP, AP, transceiver)) of the USIM terminal (1f-01) with each other. Accordingly, when the USIM 1 terminal (1f-02) and the USIM 2 terminal (1f-03) transmit and / or receive signals simultaneously with the base station 1 (1f-04) and the base station 2 (1f-05), the capabilities of each USIM terminal may be temporarily limited by each other.

[0220] According to one embodiment, in step 1f-10, the USIM 1 terminal (1f-02) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 1 (1f-04).

[0221] According to one embodiment, in step 1f-11, the USIM 2 terminal (1f-03) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 2 (1f-05).

[0222] According to one embodiment, in step 1f-15, the USIM 1 terminal (1f-02) may transmit a terminal capability information message (e.g., UECapabilityInformation) containing or including capability information of the MUSIM terminal (1f-01) to the base station 1 (1f-04). This may follow the embodiment described above. For example, the terminal capability information message (e.g., UECapabilityInformation) may include information described in FIG. 1e (e.g., information about the ability to request or provide detailed temporary UE capability restrictions, information about the ability to proactively notify whether there are temporary UE capability restrictions).

[0223] In one embodiment, at step 1f-20, base station 1 (1f-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration message) containing configuration information (e.g., musim-CapabilityRestrictionConfig) that allows the USIM1 terminal (1f-02) to report preferred / required temporary terminal capability restriction information to base station 1 (1f-04). For example, musim-CapabilityRestrictionConfig may be contained or included in otherConfig. This may follow the embodiment described above. For example, musim-CapabilityRestrictionConfig may contain information as described in Figure 1e (e.g., measurement gap requirement constraint request / change configuration information, an indicator or Wait timer Txx value indicating whether preference information may be sent, a Txy Prohibit timer value that may be applied when sending preference information for musim-AffectedBandCombList and / or musimForbiddenBandCombList, and an indicator indicating whether temporary terminal capability restrictions may be proactively notified). OtherConfig(musim-CapabilityRestrictionConfig)

[0224] According to one embodiment, in step 1f-25, base station 1 (1f-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing RRC configuration information to USIM 1 terminal (1f-02). The message (e.g., RRCReconfiguration) may include at least one of the following RRC configuration information. This may follow the embodiment described above. For example, a message (e.g., RRCReconfiguration) may include information described in Fig. 1e (e.g., a list (sCellToAddModList) for adding or modifying SCells (Serving Cells) for MNs (Master Nodes), sCellIndex, servingCellConfigCommon, PCI (physical cell ID) information, Downlink configuration information and / or Uplink configuration information commonly applied to each cell, servingCellConfig, smtc, sCellState, plmn-IdentityInfoList and / or npn-IdentityInfoList configuration information, information for adding / modifying SNs (Secondary Nodes), cellGroupId, spCellConfig, a list (sCellToAddModList) for adding or modifying SCells (Serving Cells) for SNs (Secondary Nodes)). RRCReconfiguration (sCellToAddModList, mrdc-SecondaryCellGroup for DC)

[0225] According to one embodiment, in step 1f-30, the USIM 1 terminal (1f-02) may transmit a predetermined RRC message (e.g., RRCReconfigurationComplete) to the base station 1 (1f-04) in response to a predetermined RRC message received in step 1f-35. (UEAssistanceInformation(musim-CapabilityRestriction ie detailed SCell / PSCell information)

[0226] According to one embodiment, in step 1f-35, a USIM 1 terminal (1f-02) configured to provide information on temporary terminal capability restriction may transmit a predetermined RRC message (e.g., UEAssistanceInformation) including temporary terminal capability restriction information (e.g., musim-CapabilityRestriction) due to the operation of a USIM 2 terminal (1f-03) to base station 1 (1f-04). For example, the USIM 1 terminal (1f-01) may transmit a predetermined RRC message (e.g., UEAssistanceInformation) including temporary terminal capability restriction information (musim-CapabilityRestriction) to base station 1 (1f-04) if at least one of the following conditions is satisfied.

[0227] - Condition 1: If the UE has a preference on the temporary capability restriction and the UE did not transmit a UEAssistanceInformation message with musim-CapabilityRestriction since it was configured to provide MUSIM assistance information for temporary capability restriction,

[0228] * At this time, the terminal can drive or restart the T3xx timer with the T3xx value set by the base station.

[0229] * At this time, the terminal can drive or restart the T3xy timer with the T3xy value set by the base station.

[0230] * At this time, the terminal may initiate a procedure for transmitting a terminal assistance information message to provide current MUSIM assitance information including temporary terminal capability information. For example, the terminal may perform the following procedure: If the UE has a preference for temporary terminal capability restriction information,

[0231] ** if the UE has a preference to indicate band(s) or combination of band(s) for which capabilities are restricted and if there is at least one combination of bands compromising of at least one band that is indicated in musim-candidateBandList

[0232] *** The UE may include the musim-AffectedBandCombList the UE prefers to be configured in the UE Assistance Information message.

[0233] *** The terminal may include the bandEntryIndex for each band for each combination of bands for which terminal capabilities are restricted in the terminal assistance information message.

[0234] *** The terminal may include the terminal restriction information for the bands indicated in musim-candidateBandList in musim-CapabilityRestricted for the combination of bands with restricted capabilities.

[0235] ** if the UE has a preference to indicate combination of bands to be avoided and if there is at least one combination of bands comprising at least one band that is indicated in musim-candidateBandList

[0236] *** The UE may include the musim-ForbiddenBandCombList that it prefers not to be configured in the UE Assistance Information message.

[0237] *** The terminal may include the musim-ForbiddenBandComb for the corresponding combinations of bands.

[0238] *** A terminal may include a bandEntryIndex for each band for each combination of bands to be avoided in the terminal assistance information message.

[0239] ** if the UE has a preference for serving cell(s) and / or SCG to release

[0240] *** The terminal may include musim-Cell-SCG-ToRelease in the terminal assistance information message.

[0241] *** The terminal may include the preferred serving cell(s) to be released in musim-CellToRelease. Unlike the aforementioned embodiment, the terminal according to the present disclosure may include information on the preferred serving cell(s) to be released in musim-CellToRelease through at least one of the following methods to inform the base station which specific SCell(s) to be released are, rather than including the SCellIndex.

[0242] **** Option 1: If the UE has global cell identity information of the SCell to be released, it can include it in musim-CellToRelease. For example, global cell identity is an identifier that can uniquely identify an NR cell and can be composed of a combination of PLMN (Public Land Mobile Network) Identity, cellIdentity, and / or TrackingAreaCode. For example, global cell identity can have an ASN.1 structure as shown in [Table 2]. If global cell identity is not available, the UE can include physical cell identity and carrier frequency information of the SCell in musim-CellToRelease. Of course, the carrier frequency information can mean one of the frequency-related configuration information included in the configuration information (servingCellConfigCommon and / or servingCellConfig) for the SCell.

[0243]

[0244]

[0245] **** Option 2: The FreqBandIndicatorNR information of the SCell to be released may be included. However, the information may not be included in musim-CandiateBandList.

[0246] **** Option 3: The base station can configure only the SCells included in the muism-CandidateBandList. This allows the UE to include the FreqBandIndicatorNR information of the SCells it wishes to deactivate in the UE Assistance Information message.

[0247] *** If the terminal has a preferred SCG to be released, unlike the above-described embodiment, the terminal of the present disclosure may indicate musim-CellToRelease through at least one of the following methods to inform the base station which specific cell is the PSCell of the SCG to be released, rather than including an indicator indicating whether or not the terminal prefers to release the SCG.

[0248] *** If the PSCell has global cell identity information, the UE may include the global cell identity information in the UE Assistance Information message. Otherwise, the UE may include the PSCell's physical cell identity and carrier frequency information in the UE Assistance Information message. Of course, the carrier frequency information may refer to one of the frequency-related configuration information included in the configuration information for the PSCell (e.g., spCellConfig).

[0249] ** If the UE has a preference to indicate the affected capabilities for the serving cells

[0250] *** The UE may include the musim-CellToAffectList the UE prefers not to be configured in the UE Assistance Information message.

[0251] *** The terminal may include at least one of information about capability constraints for the corresponding serving cell in the terminal assistance information message: musim-ServCellIndex (an identifier or information element indicating one of the methods proposed in the present disclosure), musim-MIMO-Layer-DL, musim-MIMO-Layers-UL, and bandwidth restriction (UL and / or DL).

[0252] - Condition 2: If the current musim-CapabilityRestriction is different from the one indicated in the last transmission of the UEAssistanceInformation message including musim-CapRestriction for affected capability for serving cell(s) or serving cell(s) release or SCG release and timer T3xx is not running.

[0253] * At this time, the UE may initiate a procedure to transmit a UE assistance information message to provide the current musim-Cell-SCG-ToRelease and / or musim-CellToAffectList. For example, the UE may perform the following procedure: If the UE has a preference for temporary capability restriction information,

[0254] ** if the UE has a preference for serving cell(s) and / or SCG to release

[0255] *** The terminal may include musim-Cell-SCG-ToRelease in the terminal assistance information message.

[0256] *** The terminal may include the preferred serving cell(s) to be released in musim-CellToRelease. The information included may be identical to the information described above.

[0257] *** If the terminal has a preferred SCG to release, the terminal may include information indicating the preferred SCG to release in musim-Cell-SCG-ToRelease. The included information may be the same as described above.

[0258] ** If the UE has a preference to indicate the affected capabilities for the serving cells

[0259] *** The UE may include the musim-CellToAffectList that the UE prefers not to be configured in the UE Assistance Information message.

[0260] *** The terminal may include at least one of musim-ServCellIndex (an identifier or information element indicating one of the methods proposed in the present disclosure), musim-MIMO-Layer-DL, musim-MIMO-Layers-UL, or information about bandwidth restriction (UL and / or DL) in the terminal assistance information message, which indicates information about capability constraints for the corresponding serving cell.

[0261] * At this time, the terminal can drive or restart the T3xx timer with the T3xx value set by the base station.

[0262] - Condition 3: If the current musim-CapabilityRestriction is different from the one indicated in the last transmission of the UEAssistanceInformation message including musim-CapRestriction for constraint band combination(s) and timer T3xy is not running.

[0263] * At this time, the UE may initiate a procedure to transmit a UE assistance information message to provide the current musim-AffectedBandCombList and / or musim-ForbiddenBandCombList. For example, the UE may perform the following procedure: If the UE has a preference for temporary capability restriction information,

[0264] ** if the UE has a preference to indicate band(s) or combination of band(s) for which capabilities are restricted and if there is at least one combination of bands compromising of at least one band that is indicated in musim-candidateBandList

[0265] *** The UE may include the musim-AffectedBandCombList that it prefers to be configured in the UE Assistance Information message.

[0266] *** A terminal may include a bandEntryIndex for each band in the terminal assistance information message for each combination of bands whose capabilities are restricted.

[0267] *** A terminal may include terminal restriction information for the bands indicated in musim-candidateBandList in musim-CapabilityRestricted for the combination of bands for which terminal capabilities are restricted. (Include the musim-capabilityRestricted for the bands indicated in musim-candidateBandList with restricted capability together for the combination of bands for which capabilities are restricted)

[0268] ** If the UE has a preference to indicate combination of bands to be avoided and if there is at least one combination of bands comprising at least one band that is indicated in musim-candidateBandList

[0269] *** The UE may include the musim-ForbiddenBandCombList that it prefers not to be configured in the UE Assistance Information message.

[0270] *** The terminal can include the musim-ForbiddenBandComb for the corresponding combinations of bands.

[0271] *** A terminal may include a bandEntryIndex for each band for each combination of bands to be avoided in the terminal assistance information message.

[0272] * At this time, the terminal can drive or restart the T3xy timer with the T3xy value set by the base station.

[0273] For reference, if the UE has no longer preference for temporary capability restriction, the UE may transmit to the base station 1 (1f-04) the musim-CapabilityRestriction in the musim-Assistance IE (information element) without including the temporary UE capability restriction preference. That is, if the UE previously included information A in the musim-Assistance IE but no longer needs the preference A, the UE may not include information A in the musim-Assistance IE.

[0274] According to one embodiment, in step 1f-40, base station 1 (1f-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing RRC configuration information based on temporary terminal capability constraint information provided by USIM 1 terminal (1f-02) in response to step 1f-35. If the temporary terminal capability constraint provided in step 1f-35 is resolved through the received RRC message, USIM 1 terminal (1f-02) may stop the T3xx timer started in step 1f-35.

[0275] According to one embodiment, in step 1f-45, the USIM 1 terminal (1f-02) may transmit a predetermined RRC message (e.g., RRCReconfigurationComplete) to the base station 1 (1f-04) in response to a predetermined RRC message received in step 1f-40.

[0276] In the present disclosure, when a USIM 1 terminal (1f-02) transmits a preference request for SCell release to base station 1 (1f-04) as a terminal assistance information message, the terminal (1f-02) may not send SCellIndex to base station 1 (1f-04) to indicate the preference request for SCell release, but may include information that can specifically identify the SCell in the terminal assistance information message and transmit it to base station 1 (1f-04). Since the terminal (1f-02) and the base station (1f-04) only remember the most recently sent terminal assistance information message, if information that can specifically identify the SCell is included in the terminal assistance information message, the base station (1f-04) can use the same SCellIndex for other SCells, and if the terminal (1f-02) no longer prefers a preference request for SCell release in the future, if the terminal assistance information message is transmitted to the base station without including in the terminal assistance information message the information that can specifically identify the SCell that was already included in the terminal assistance information message, the base station (1f-04) can identify which SCell can be re-configured for the terminal (1f-02).

[0277] In the present disclosure, when a USIM 1 terminal (1f-01) transmits a preference request for SCG release to a base station (1f-04) as a terminal assistance information message, instead of only sending an indicator indicating an SCG release preference request to indicate the preference request for SCG release, information that can specifically identify a PSCell operating in the corresponding SCG can be included in the terminal assistance information message and transmitted to base station 1 (1f-04). Accordingly, when a terminal (1f-02) later no longer prefers a preference request for PSCell release, the terminal (1f-02) does not include information that can specifically identify a PSCell (primary secondary cell group cell) in the terminal assistance information message, and instead transmits a terminal assistance information message that does not include the identifying information to base station 1 (1f-04), so that the base station can know which PSCell can be re-configured for the terminal.

[0278] FIG. 1g is a flowchart illustrating a process in which a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple Universal Subscriber Identity Modules (USIMs) according to an embodiment requests and / or provides temporary UE capability restrictions to a base station according to the settings of the base station.

[0279] Referring to FIG. 1g, a MUSIM terminal (1g-01) according to one embodiment may be referred to as a terminal supporting multiple USIMs in a single device. For convenience of explanation, the present disclosure will be described based on a Dual-USIM terminal supporting two USIMs. However, this is merely an example, and the present disclosure is not limited thereto.

[0280] For example, a MUSIM terminal (1g-01) may be referenced as a USIM 1 terminal (1g-02) when operating on USIM 1, and as a USIM 2 terminal (1g-03) when operating on USIM 2. In this case, the base stations (1g-04, 1g-05) associated with each USIM may recognize or identify the USIM 1 terminal (1g-02) and the USIM 2 terminal (1g-03) as separate terminals rather than the MUSIM terminal (1g-01) operating on the same device.

[0281] According to one embodiment, the USIM 1 terminal (1g-02) and the USIM 2 terminal (1g-03) can share and use the hardware capabilities of the MUSIM terminal (1g-01). Therefore, when the USIM 1 terminal (1g-02) and the USIM 2 terminal (1g-03) simultaneously transmit and / or receive signals to and from base station 1 (1g-04) and base station 2 (1g-05), the capabilities of each USIM terminal may be temporarily limited by the other.

[0282] According to one embodiment, in step 1g-10, the USIM 1 terminal (1g-02) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 1 (1g-04).

[0283] According to one embodiment, in step 1g-11, the USIM 2 terminal (1g-03) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 2 (1g-05).

[0284] According to one embodiment, in step 1g-15, the USIM 1 terminal (1g-02) may transmit a terminal capability information message (e.g., UECapabilityInformation) containing or including capability information of the MUSIM terminal (1g-01) to the base station 1 (1g-04). This may follow at least one of the embodiments described above.

[0285] According to one embodiment, in step 1g-20, base station 1 (1g-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration message) containing configuration information (e.g., musim-CapabilityRestrictionConfig) that allows a USIM 1 terminal (1g-02) to report preferred / required temporary UE capability restriction information to base station 1 (1g-04). For example, musim-CapabilityRestrictionConfig may be included in otherConfig, which may follow at least one of the embodiments described above. For example, the UE capability information message (e.g., UECapabilityInformation) may include the information described in FIG. 1e (e.g., information about the capability to request or provide detailed temporary UE capability restrictions, information about the capability to proactively notify whether there are temporary UE capability restrictions). OtherConfig(musim-CapabilityRestrictionConfig)

[0286] According to one embodiment, in step 1g-25, base station 1 (1g-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing RRC configuration information to USIM 1 terminal (1g-02). The message (e.g., RRCReconfiguration) may include at least one of the following RRC configuration information. This may follow at least one of the embodiments described above. For example, a message (e.g., RRCReconfiguration) may include information (e.g., a list (sCellToAddModList) to add or modify SCells (Serving Cells) for MN (Master Node), sCellIndex, servingCellConfigCommon, PCI (physical cell ID) information, information to add / modify Downlink configuration information and / or Uplink configuration information commonly applied to each cell, servingCellConfig, smtc, sCellState, plmn-IdentityInfoList and / or npn-IdentityInfoList configuration information, SN Secondary Node) information to add / modify, cellGroupId, spCellConfig, a list (sCellToAddModList) to add or modify SCells (Serving Cells) for SN (Secondary Node) as described in Fig. 1e. RRCReconfiguration (sCellToAddModList, mrdc-SecondaryCellGroup for DC)

[0287] According to one embodiment, at step 1g-30, the USIM 1 terminal (1g-02) may transmit a predetermined RRC message (e.g., RRCReconfigurationComplete) to base station 1 (1g-04) in response to a predetermined RRC message received at step 1g-35.

[0288] According to one embodiment, in step 1g-35, a USIM 1 terminal (1g-02) configured to provide information on temporary capability restriction may transmit a predetermined RRC message (e.g., UEAssistanceInformation) containing temporary terminal capability restriction information (e.g., musim-CapabilityRestriction) due to the operation of a USIM 2 terminal (1g-03) to a base station 1 (1g-04). This may follow at least one of the embodiments described above. For example, musim-CapabilityRestrictionConfig may contain information as described in Fig. 1e (e.g., measurement gap requirement constraint request / change configuration information, an indicator or Wait timer Txx value indicating whether preference information may be sent, a Txy Prohibit timer value that may be applied when sending preference information for musim-AffectedBandCombList and / or musimForbiddenBandCombList, an indicator indicating whether temporary terminal capability restrictions may be proactively notified). (UEAssistanceInformation(musim-CapabilityRestriction i.e. detailed SCell / PSCell information)

[0289] According to one embodiment, at step 1g-35, the terminal may drive a T3xx timer.

[0290] According to one embodiment, in step 1g-40, the USIM 1 terminal (1g-02) may transition to RRC idle mode (e.g., RRC_IDLE) or RRC inactive mode (e.g., RRC_INACTIVE). For example, the USIM 1 terminal (1g-02) may receive an RRC connection release message from base station 1 (1g-04), apply the RRC connection release message, and transition to RRC idle mode or RRC inactive mode. As another example, the USIM 1 terminal (1g-02) may autonomously transition to RRC idle mode due to a predetermined reason (e.g., when the RRC connection with the current cell cannot be maintained due to a radio link failure).

[0291] According to one embodiment, the USIM terminal 1 (1g-02) may propose or trigger to stop the T3xx timer if the T3xx timer is running in step 1g-41. For example, the terminal may stop the T3xx timer while performing operations that must be performed to transition to RRC idle mode or RRC deactivation mode (i.e., before actually transitioning to RRC idle mode or RRC deactivation mode). For example, if the running T3xx timer is not stopped and continues to run, when the T3xx timer expires, the terminal may apply the temporary terminal capability information indicated in step 1g-35 regardless of the configuration of the base station. Therefore, the terminal stops the running T3xx timer to prevent a mismatch between the UE and the network in understanding the RRC configuration that the terminal later connects to. That is, by stopping the running T3xx timer, the terminal can be configured with common RRC configuration information with the base station to which it later connects.

[0292] FIG. 1h is a flowchart illustrating a process in which a terminal (Multi-USIM UE, hereinafter referred to as MUSIM UE) supporting multiple Universal Subscriber Identity Modules (USIMs) according to an embodiment requests and / or provides temporary UE capability restrictions to a base station according to the settings of the base station.

[0293] Referring to FIG. 1h, a MUSIM terminal (1h-01) according to one embodiment may be referred to as a terminal supporting multiple USIMs in a single device. For convenience of explanation, the present disclosure is described based on a Dual-USIM terminal supporting two USIMs. However, this is merely an example, and the present disclosure is not limited thereto.

[0294] For example, a MUSIM terminal (1h-01) may be referenced as a USIM 1 terminal (1h-02) when operating on USIM 1, and may be referenced as a USIM 2 terminal (1h-03) when operating on USIM 2. In this case, the base stations (1h-04, 1h-05) associated with each USIM may recognize or identify the USIM 1 terminal (1h-02) and the USIM 2 terminal (1h-03) as separate terminals rather than the MUSIM terminal (1h-01) operating on the same device.

[0295] According to one embodiment, the USIM 1 terminal (1h-02) and the USIM 2 terminal (1h-03) can share and use the hardware capabilities of the USIM terminal (1h-01). Therefore, when the USIM 1 terminal (1h-02) and the USIM 2 terminal (1h-03) simultaneously transmit and / or receive signals to and from base station 1 (1h-04) and base station 2 (1h-05), the capabilities of each USIM terminal may be temporarily limited by the other.

[0296] According to one embodiment, at step 1h-10, the USIM 1 terminal (1h-02) may establish an RRC connection with base station 1 (1h-04) and be in RRC connected mode (RRC_CONNECTED).

[0297] According to one embodiment, at step 1h-11, the USIM 2 terminal (1h-03) may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with base station 2 (1h-05).

[0298] According to one embodiment, in step 1h-15, the USIM 1 terminal (1h-02) may transmit a terminal capability information message (e.g., UECapabilityInformation) containing capability information of the MUSIM terminal (1h-01) to the base station 1 (1h-04). This may follow at least one of the embodiments described above. For example, the terminal capability information message (e.g., UECapabilityInformation) may include the information described in FIG. 1e (e.g., information about the capability to request or provide details of temporary UE capability restrictions, information about the capability to proactively notify whether there are temporary UE capability restrictions). (UECapabilityInformation(support of signaling of UE capability restrictions, nr-NeedForGap-Reporting-r16)

[0299] Additionally, the terminal capability information message (e.g., UECapabilityInformation) may include at least some of the following capability information:

[0300] - nr-NeedForGap-Reporting-r16

[0301] * Indicates whether the UE supports reporting the measurement gap requirement information for the NR target in the UE response to a network configuration RRC message.

[0302] - musim-NeedForGap-Reporting

[0303] * An indicator indicating the ability of a terminal to report to the base station its preferred measurement gap requirements for an NR target via a terminal assistance information message. If the indicator (e.g., musim-NeedForGap-Reporting) is included separately in a message (e.g., a terminal assistance information message), only terminals that support nr-NeedForGap-Reporting can include the indicator (e.g., musim-NeedForGap-Reporting) in the terminal assistance information message.

[0304] * Note that the indicator (e.g., musim-NeedForGap-Reporting) may also be indicated as a separate message (e.g., a terminal assistance information message). As another example, if the terminal supports nr-NeedForGap-Reporting and supports the ability to request or provide temporary terminal capability constraints in detail, as described in the aforementioned embodiments, the musim-NeedForGap-Reporting capability may also be supported.

[0305] In one embodiment, at step 1h-20, base station 1 (1h-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration message) containing configuration information (e.g., musim-CapabilityRestrictionConfig) that allows the USIM1 terminal (1h-02) to report preferred / required temporary terminal capability restriction information to base station 1 (1h-04). For example, musim-CapabilityRestrictionConfig may be stored in otherConfig. This may follow at least one of the embodiments described above. For example, musim-CapabilityRestrictionConfig may contain information as described in Figure 1e (e.g., measurement gap requirement constraint request / change configuration information, an indicator or Wait timer Txx value indicating whether preference information may be sent, a Txy Prohibit timer value that may be applied when sending preference information for musim-AffectedBandCombList and / or musimForbiddenBandCombList, and an indicator indicating whether temporary terminal capability restrictions may be proactively notified).

[0306] According to one embodiment, at step 1h-25, base station 1 (1h-04) may transmit a predetermined RRC message (e.g., RRCReconfiguration or RRCResume) containing RRC configuration information to USIM 1 terminal (1h-02). For example, the message (e.g., RRCReconfiguration or RRCResume) may include at least some of the following RRC configuration information. This may follow at least one of the embodiments described above. For example, a message (e.g., RRCReconfiguration or RRCResume) may include information described in Fig. 1e (e.g., a list of SCells (Serving Cells) to be added or modified for the MN (Master Node) (sCellToAddModList), sCellIndex, servingCellConfigCommon, PCI (physical cell ID) information, Downlink configuration information and / or Uplink configuration information commonly applied to each cell, servingCellConfig, smtc, sCellState, plmn-IdentityInfoList and / or npn-IdentityInfoList configuration information, information to be added / modified for the SN (Secondary Node), cellGroupId, spCellConfig, a list of SCells (Serving Cells) to be added or modified for the SN (Secondary Node) (sCellToAddModList)). RRCreconfiguration(needForGapsConfigNR)

[0307] Additionally, the message (e.g. RRCReconfiguration or RRCResume) may include at least some of the following:

[0308] - if the RRCReconfiguration message includes the needForGapsConfigNR

[0309] * if needForGapsConfigNR is set to setup

[0310] ** The terminal may identify or consider itself configured to provide measurement gap requirement information for NR target bands.

[0311] * if not (else)

[0312] ** The terminal may identify or consider itself not to be configured to provide the measurement gap requirement information for NR target bands.

[0313] According to one embodiment, in step 1h-30, the USIM 1 terminal (1h-02) may transmit a predetermined RRC message (e.g., RRCReconfigurationComplete or RRCResumeComplete) to the base station 1 (1h-04) in response to the predetermined RRC message received in step 1h-25. At this time, the terminal may transmit a predetermined RRC message including the following information to the base station according to the following procedure. (RRCReconfigurationcomplete(NeedForGapsInfoNR))

[0314] - If the UE is configured to provide the measurement gap requirement information of NR target bands

[0315] * If the RRCReconfiguration message contains needForGapsConfigNR or if the information most recently sent by the terminal has changed from the current NeedForGapsInfoNR information (Note that this condition may not be considered when transmitting RRCResumeComplete)

[0316] ** The terminal can be set to include NeedForGapsInfoNR and the content can be set as follows.

[0317] *** Include intraFreq-needForGap and set the gap requirement information of intra-frequency measurement for each NR serving cell.

[0318] *** If requestedTargetBandFilterNR is set, for each supported NR band that is also included in requestedTargetBandFilterNR, include an entry in interFreq-needForGap and set the gap requirement information for that band.

[0319] *** Otherwise, you can include an entry in interFreq-needForGap for each supported NR band and set the gap requirement information for that band.

[0320] According to one embodiment, in step 1h-35, a USIM 1 terminal (1h-02) configured to provide information on temporary capability restriction may transmit a predetermined RRC message (e.g., UEAssistanceInformation) containing temporary capability restriction information (musim-CapabilityRestriction) due to the operation of a USIM 2 terminal (1h-03) to a base station 1 (1h-04). This may follow at least one of the embodiments described above. (UEAssistanceInformation(musim-CapabilityRestriction ie musim-NeedForGapsInfoNR)

[0321] Additionally, a terminal according to an embodiment may transmit to a base station a terminal assistance information message including musim-NeedForGapsInfoNR containing measurement gap requirement information for NR target bands for which the terminal prefers to be configured, if at least one of the following conditions is satisfied:

[0322] - If the terminal has a preference for temporary terminal capability constraints,

[0323] * If the base station explicitly allows the UE to transmit preferred measurement gap requirement constraint information and the current musim-NeedForGapsInfoNR is different from the measurement gap requirement information for the NR target bands most recently provided via a given RRC message (one of RRCResumeComplete, RRCReconfigurationComplete, or UEAssistanceInformation), or

[0324] * If the base station sets up needForGapsConfigNR via RRCResume and / or RRCReconfiguration, and the current musim-NeedForGapsInfoNR is different from the measurement gap requirement information for NR target bands provided via the most recent RRC message (one of RRCResumeComplete, RRCReconfigurationComplete, or UEAssistanceInformation).

[0325] In one embodiment, if the terminal does not support nr-NeedForGap-Reporting-r16, the terminal may not transmit the terminal assistance information message including musim-NeedForGapsInfoNR to the base station. That is, the terminal may transmit the terminal assistance information message including musim-NeedForGapsInfoNR to the base station only when it supports nr-NeedForGap-Reporting-r16, according to an explicit configuration of the base station, or when needForGapsConfigNR is set up in RRCReconfiguration and / or RRCResume.

[0326] According to one embodiment, needForGapsInfoNR and musim-NeedForGapsInfoNR may have substantially the same ASN.1 structure as [Table 3].

[0327]

[0328]

[0329]

[0330]

[0331] According to one embodiment, needForGapsConfigNR may have an ASN.1 structure as in [Table 4].

[0332]

[0333]

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

[0335] Referring to FIG. 1i, a terminal according to one embodiment may include a radio frequency (RF) processing unit (1i-10), a baseband processing unit (1i-20), a storage unit (1i-30), and / or a control unit (1i-40).

[0336] According to one embodiment, the RF processing unit (1i-10) may perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. For example, the RF processing unit (1i-10) may up-convert a baseband signal provided from the baseband processing unit (1i-20) into an RF band signal and transmit the up-converted signal through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1i-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), and / or an analog to digital convertor (ADC). In FIG. 1i, only one antenna is illustrated, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (1i-10) may include multiple RF chains. Furthermore, the RF processing unit (1i-10) can perform beamforming. For the beamforming, the RF processing unit (1i-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.

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

[0338] According to one embodiment, the baseband processing unit (1i-20) and the RF processing unit (1i-10) may transmit and / or receive signals as described above. Accordingly, the baseband processing unit (1i-20) and the RF processing unit (1i-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 (1i-20) and the RF processing unit (1i-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 (1i-20) and the RF processing unit (1i-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.

[0339] According to one embodiment, the storage unit (1i-30) stores data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (1i-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 (1i-30) provides the stored data upon request from the control unit (1i-40).

[0340] According to one embodiment, the control unit (1i-40) controls the overall operations of the terminal. For example, the control unit (1i-40) transmits and receives signals through the baseband processing unit (1i-20) and the RF processing unit (1i-10). In addition, the control unit (1i-40) records and reads data in the storage unit (1i-40). For this purpose, the control unit (1i-40) may include at least one processor. For example, the control unit (1i-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.

[0341] FIG. 1j is a block diagram showing the configuration of an NR base station according to an embodiment of the present invention.

[0342] Referring to FIG. 1j, the branch office is configured to include an RF processing unit (1j-10), a baseband processing unit (1j-20), a backhaul communication unit (1j-30), a storage unit (1j-40), and / or a control unit (1j-50).

[0343] According to one embodiment, the RF processing unit (1j-10) may perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. For example, the RF processing unit (1j-10) up-converts a baseband signal provided from the baseband processing unit (1j-20) into an RF band signal and transmits the up-converted signal through an antenna, and down-converts an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1j-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, and / or an ADC, etc. In Fig. 1j, only one antenna is illustrated, but the first access node may have multiple antennas. In addition, the RF processing unit (1j-10) may include multiple RF chains. Furthermore, the RF processing unit (1j-10) may perform beamforming. For beamforming, the RF processing unit (1j-10) can adjust the phase and amplitude of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit (1j-10) can perform a downlink MIMO operation by transmitting one or more layers.

[0344] According to one embodiment, the baseband processing unit (1j-20) may perform a conversion function between a baseband signal and a bit stream according to the physical layer specification of the first wireless access technology. For example, when transmitting data, the baseband processing unit (1j-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (1j-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (1j-10). For example, in the case of following the OFDM method, when transmitting data, the baseband processing unit (1j-20) may generate complex symbols by encoding and modulating a transmission bit stream, map the complex symbols to subcarriers, and then configure OFDM symbols through an IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (1j-20) can divide the baseband signal provided from the RF processing unit (1j-10) into OFDM symbol units, restore the signals mapped to subcarriers through FFT operation, and then restore the received bit string through demodulation and decoding. The baseband processing unit (1j-20) and the RF processing unit (1j-10) can transmit and receive signals as described above. Accordingly, the baseband processing unit (1j-20) and the RF processing unit (1j-10) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0345] According to one embodiment, the backhaul communication unit (1j-30) may provide an interface for performing communication with other nodes within the network. That is, the backhaul communication unit (1j-30) may convert a bit string transmitted from the main base station to another node, such as an auxiliary base station or a core network, into a physical signal, and may convert a physical signal received from the other node into a bit string.

[0346] According to one embodiment, the storage unit (1j-40) can store data such as basic programs, application programs, and setting information for the operation of the base station. In particular, the storage unit (1j-40) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (1j-40) can store information that serves as a judgment criterion for whether to provide or terminate multiple connections to a terminal. In addition, the storage unit (1j-40) can provide the stored data upon request of the control unit (1j-50).

[0347] According to one embodiment, the control unit (1j-50) can control the overall operations of the base station. For example, the control unit (1j-50) transmits and receives signals through the baseband processing unit (1j-20) and the RF processing unit (1j-10) or through the backhaul communication unit (1j-30). In addition, the control unit (1j-50) records and reads data in the storage unit (1j-40). For this purpose, the control unit (1j-50) can include at least one processor.

[0348] Meanwhile, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples to easily explain the technical content of the present invention and assist in understanding the present invention, and are not intended to limit the scope of the present invention. In other words, it will be apparent to those skilled in the art that other modifications based on the technical concept of the present invention are possible. Furthermore, each embodiment can be combined and operated as needed. For example, all embodiments of the present invention can be operated as a base station and a terminal by combining parts thereof.

[0349] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0350] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.

[0351] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0352] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.

[0353] Meanwhile, the order of description in the drawings explaining the method of the present invention does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel.

[0354] Alternatively, the drawings illustrating the method of the present invention may omit some components and include only some components within a scope that does not harm the essence of the present invention.

[0355] In addition, the method of the present invention may be implemented by combining some or all of the contents included in each embodiment within a scope that does not harm the essence of the invention.

[0356] Various embodiments of the present disclosure have been described above. The above description of the present disclosure is for illustrative purposes only, and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will appreciate that the present disclosure can be easily modified into other specific forms without altering the technical spirit or essential characteristics of the present disclosure. The scope of the present disclosure is indicated by the claims below rather than the detailed description described above, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included within the scope of the present disclosure.

[0357] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0358] 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. For example, some or all of the embodiments may be combined with some or all of one or more other embodiments, and such combinations should naturally fall within the scope of the embodiments proposed in this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the claims described below, but also by equivalents thereof.

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

[0360] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples to easily explain the technical contents of the present disclosure and to help the understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modified examples based on the technical idea of ​​the present disclosure are possible. In addition, each of the above embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and another embodiment can be combined with each other to operate a base station and a terminal. In addition, other modified examples based on the technical idea of ​​the above embodiments can be implemented in various systems such as an FDD LTE system, a TDD LTE system, a 5G or NR system, etc.

Claims

1. A method performed by a UE (user equipment) in a wireless communication system, A step of receiving an RRC (radio resource control) message including needForGapsConfigNR information from a base station, wherein the needForGapsconfigNR information includes information on at least one target NR (new radio) band; When the above needForGapsConfigNR information is set to setup, a step for identifying that the UE is set to provide measurement gap information of at least one target NR band; A step of transmitting a first UEAssistanceInformation including first measurement gap information to the base station; and A method comprising the step of transmitting a second UEAssistanceInformation including the current measurement gap information to the base station, when the UE is configured to provide measurement gap information of the at least one target NR band and the current measurement gap information is different from the first measurement gap information.

2. In claim 1, The above current measurement gap information is a method based on MUSIM (multi-USIM (universal subscriber identity module)) operation.

3. In claim 1, A step of transmitting capability information about provision of information on temporary capability restriction associated with MUSIM (multi-USIM (universal subscriber identity module)) to the base station; and A step of receiving setting information for the temporary capacity limitation from the base station, A method wherein the setting information for the temporary capability limitation includes information about a list of candidate bands.

4. In claim 1, When the second UEAssistanceInformation including information about temporary capability limitation associated with MUSIM (multi-USIM (universal subscriber identity module)) is transmitted to the base station, a step of starting a timer associated with the temporary capability limitation; and A method comprising the step of stopping the timer when an RRC release message is received from the base station.

5. In a wireless communication system, in the UE (user equipment), transceiver; and A controller coupled with the above transceiver, The above controller: Receive an RRC (radio resource control) message including needForGapsConfigNR information from a base station, wherein the needForGapsconfigNR information includes information on at least one target NR (new radio) band, When the above needForGapsConfigNR information is set to setup, it identifies that the UE is set to provide measurement gap information of at least one target NR band, Transmitting to the base station a first UEAssistanceInformation including first measurement gap information, A UE configured to provide measurement gap information of the at least one target NR band and, if current measurement gap information is different from the first measurement gap information, transmit a second UEAssistanceInformation including the current measurement gap information to the base station.

6. In claim 5, The above current measurement gap information is based on MUSIM (multi-USIM (universal subscriber identity module)) operation of the UE.

7. In claim 5, The above controller: Transmit capability information to the above base station regarding provision of information on temporary capability restriction associated with MUSIM (multi-USIM (universal subscriber identity module)), It is set to receive setting information for the temporary capacity limitation from the above base station, The above setting information for the above temporary capability limitation includes information about the list of candidate bands, UE.

8. In claim 5, The above controller: When the second UEAssistanceInformation including information about temporary capability limitation associated with MUSIM (multi-USIM (universal subscriber identity module)) is transmitted to the base station, a timer associated with the temporary capability limitation is started, A UE configured to stop the timer when an RRC release message is received from the base station.

9. A method performed by a base station in a wireless communication system, A step of transmitting an RRC (radio resource control) message including needForGapsConfigNR information to a UE (user equipment), wherein the needForGapsConfigNR information includes information on at least one target NR (new radio) band, and the needForGapsConfigNR information is set to setup; A step of receiving a first UEAssistanceInformation including first measurement gap information from the UE; and If the current measurement gap information is different from the first measurement gap information, the step of receiving a second UEAssistanceInformation including the current measurement gap information from the UE, A method wherein provision of measurement gap information of at least one target NR band is based on the needForGapsConfigNR information.

10. In claim 9, The above current measurement gap information is a method based on MUSIM (multi-USIM (universal subscriber identity module)) operation.

11. In claim 9, A step of receiving capability information for provision of information on temporary capability restriction associated with a multi-USIM (universal subscriber identity module) from the UE; and Including a step of transmitting setting information for the temporary capability limitation to the UE, A method wherein the setting information for the temporary capability limitation includes information about a list of candidate bands.

12. In claim 9, When the second UEAssistanceInformation including information about temporary capability limitation associated with MUSIM (multi-USIM (universal subscriber identity module)) is received from the UE, a timer associated with the temporary capability limitation is started, A method wherein the timer is stopped when an RRC release message is transmitted to the UE.

13. In a base station in a wireless communication system, transceiver; and A controller coupled with the above transceiver, The above controller: Transmitting an RRC (radio resource control) message including needForGapsConfigNR information to a UE (user equipment), wherein the needForGapsConfigNR information includes information on at least one target NR (new radio) band, and the needForGapsConfigNR information is set to setup, Receive a first UEAssistanceInformation including first measurement gap information from the UE, If the current measurement gap information is different from the first measurement gap information, the second UEAssistanceInformation including the current measurement gap information is set to be received from the UE, A base station, wherein provision of measurement gap information of at least one target NR band is based on the needForGapsConfigNR information.

14. In claim 13, The above controller: Receive capability information about provision of information on temporary capability restriction associated with MUSIM (multi-USIM (universal subscriber identity module)) from the UE, It is configured to transmit setting information for the temporary capability limitation to the above UE, The above setting information for the above temporary capability limitation includes information about the list of candidate bands, The above current measurement gap information is based on the operation of the multi-USIM (universal subscriber identity module) MUSIM (base station).

15. In claim 13, When the second UEAssistanceInformation including information about temporary capability limitation associated with MUSIM (multi-USIM (universal subscriber identity module)) is received from the UE, a timer associated with the temporary capability limitation is started, A base station, wherein the timer is stopped when an RRC release message is transmitted to the UE.

Images