Method and device for reporting measurement result in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Specifically, the present disclosure relates to a method and device for reporting a measurement result in a wireless communication system.

Description

Method and apparatus for reporting measurement results in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method and apparatus for reporting measurement results in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands that meets various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes to expand network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) to incorporate Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] As a result of the aforementioned developments and advancements in mobile communication systems, it has become possible to provide a variety of services, and thus measures to effectively provide these services are required.

[0009] The present disclosure aims to provide an apparatus and method capable of effectively providing services in a wireless communication system.

[0010] According to one embodiment of the present disclosure, a method performed by a terminal (user equipment, UE) in a wireless communication system comprises: receiving an RRC release message from a base station containing a measIdleConfig regarding a measurement in an RRC (radio resource control) idle state or an RRC inactive state; if the measIdleConfig is set to setup, storing at least one setting within the measIdleConfig in VarMeasIdleConfig or VarEnhMeasIdleConfig; transitioning to the RRC idle state or the RRC inactive state; receiving a measIdleConfigSIB (system information block) 11 from the base station regarding a measurement in the RRC idle state or the RRC inactive state; performing the measurement while the UE is in the RRC idle state or the RRC inactive state; transitioning to an RRC connected state; receiving a UE information request message from the base station containing an idleModeMeasurementReq; and UE information The method may include the steps of setting measResultIdleEUTRA or measResultIdleNR within a response (UE information response) message, transmitting the UE information response message to the base station, and, if measIdleValidityDuration is stored in VarEnhMeasIdleConfig, deleting measIdleValidityDuration within VarEnhMeasIdleConfig.

[0011] According to one embodiment of the present disclosure, in a wireless communication system, a user equipment (UE) comprises at least one transceiver, at least one processor communicatively coupled to the at least one transceiver, and at least one memory communicatively coupled to the at least one processor for storing instructions, wherein the instructions are executed individually or in any combination by the at least one processor, and the UE receives an RRC release message from a base station comprising a measIdleConfig regarding a measurement in an RRC (radio resource control) idle state or an RRC inactive state, and if the measIdleConfig is set as a setup, at least one setting within the measIdleConfig is stored in VarMeasIdleConfig or VarEnhMeasIdleConfig, transitions to the RRC idle state or the RRC inactive state, and receives from the base station a measurement in the RRC idle state or the RRC inactive state Receive SIB (system information block) 11 regarding measIdleConfigSIB, perform the measurement while the UE is in the RRC idle state or the RRC disabled state, transition to the RRC connected state, receive a UE information request message including idleModeMeasurementReq from the base station, set measResultIdleEUTRA or measResultIdleNR in the UE information response message, and to the base station,The above UE information response message can be transmitted, and if measIdleValidityDuration is stored in the VarEnhMeasIdleConfig, the measIdleValidityDuration in the VarEnhMeasIdleConfig can be deleted.

[0012] The present disclosure can provide an apparatus and a method capable of effectively providing services in a wireless communication system.

[0013] FIG. 1 is a drawing illustrating the structure of a wireless communication system according to one embodiment of the present disclosure.

[0014] FIG. 2 is a drawing illustrating a wireless protocol structure in a wireless communication system according to one embodiment of the present disclosure.

[0015] FIG. 3 is a drawing illustrating the structure of a wireless communication system according to one embodiment of the present disclosure.

[0016] FIG. 4 is a diagram showing the wireless protocol structure of a wireless communication system according to one embodiment of the present disclosure.

[0017] FIG. 5 illustrates a flowchart showing a terminal in an RRC idle mode (RRC_IDLE) or RRC disabled state (RRC_INACTIVE) in a wireless communication system according to one embodiment of the present disclosure performing a cell reselection evaluation procedure.

[0018] FIG. 6 illustrates a flowchart of a procedure in which a terminal in an RRC idle mode (RRC_IDLE) and an RRC inactive mode (RRC_INACTIVE) according to one embodiment of the present disclosure performs idle / inactive measurements, and a base station quickly establishes Carrier Aggregation or Dual Connectivity to the terminal based on the idle / inactive measurement results recovered from the terminal.

[0019] FIG. 7 illustrates a flowchart of a procedure in which a terminal in an RRC idle mode (RRC_IDLE) and an RRC inactive mode (RRC_INACTIVE) according to one embodiment of the present disclosure performs idle / inactive measurements, and a base station quickly establishes Carrier Aggregation or Dual Connectivity to the terminal based on the idle / inactive measurement results recovered from the terminal.

[0020] FIG. 8 illustrates a flowchart of a procedure in which a terminal in an RRC idle mode (RRC_IDLE) and an RRC inactive mode (RRC_INACTIVE) according to one embodiment of the present disclosure performs a measurement for cell reselection, and a base station quickly establishes Carrier Aggregation or Dual Connectivity to the terminal based on the cell reselection measurement result recovered from the terminal.

[0021] FIG. 9 illustrates a flowchart of a procedure in which a terminal in an RRC idle mode (RRC_IDLE) and an RRC inactive mode (RRC_INACTIVE) according to one embodiment of the present disclosure performs a measurement for cell reselection, and a base station quickly establishes Carrier Aggregation or Dual Connectivity to the terminal based on the cell reselection measurement result recovered from the terminal.

[0022] FIG. 10 illustrates a flowchart of a procedure in which a terminal in an RRC idle mode (RRC_IDLE) and an RRC inactive mode (RRC_INACTIVE) according to one embodiment of the present disclosure performs idle / inactive measurements, and a base station quickly establishes Carrier Aggregation or Dual Connectivity to the terminal based on the idle / inactive measurement results recovered from the terminal.

[0023] FIG. 11 illustrates a flowchart of a procedure in which a terminal in an RRC idle mode (RRC_IDLE) and an RRC inactive mode (RRC_INACTIVE) according to one embodiment of the present disclosure performs idle / inactive measurements, and a base station quickly establishes Carrier Aggregation or Dual Connectivity to the terminal based on the idle / inactive measurement results recovered from the terminal.

[0024] FIG. 12 illustrates a flowchart of a procedure in which a terminal according to one embodiment of the present disclosure manages measIdleValidityDuration stored in the variable VarEnhMeasIdleConfig.

[0025] FIG. 13 illustrates a flowchart of a procedure in which a terminal according to one embodiment of the present disclosure manages measReselectionValidityDuration stored in the variable VarMeasReselectionConfig.

[0026] FIG. 14 illustrates the functional configuration of a terminal according to one embodiment of the present disclosure.

[0027] FIG. 15 illustrates the functional configuration of an NR base station according to one embodiment of the present disclosure.

[0028] The operating principles of the present disclosure will be described in detail below with reference to the attached drawings. In describing the present disclosure below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the present disclosure. Furthermore, the terms described below are defined considering their functions in the present invention, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0029] An embodiment of the present invention will be described below with reference to the attached drawings.

[0030] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0031] For convenience of explanation, the present disclosure uses terms and names defined in the 3GPP LTE (3rd Generation Partnership Project Long Term Evolution) standard. However, the present disclosure is not limited to the above terms and names and may be applied equally to systems conforming to other standards. In the present disclosure, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as an eNB may represent a gNB.

[0032] FIG. 1 illustrates the structure of a wireless communication system according to one embodiment of the present invention. According to one embodiment of the present disclosure, the wireless communication system may include an LTE system.

[0033] Referring to FIG. 1, a wireless access network of an LTE system according to one embodiment may be composed of a next-generation base station (Evolved Node B, hereinafter ENB, Node B or base station) (105, 110, 115, 120), a mobility management entity (MME) (125), and a serving gateway (S-GW) (130). A user device (user equipment, hereinafter UE or terminal) (135) may connect to an external network through the ENB (105, 110, 115, 120) and the S-GW (130).

[0034] According to one embodiment, the ENB (105, 110, 115, 120) in FIG. 1 may correspond to Node B of an existing UMTS (universal mobile telecommunications system) system. The ENB is connected to the UE (135) via a wireless channel and can perform a more complex role than the existing Node B. In an LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, can be serviced through a shared channel. Therefore, a device that aggregates status information such as the buffer status, available transmission power status, and channel status of the UEs and performs scheduling may be required. This can be handled by the ENB (105, 110, 115, 120). A single ENB can typically control multiple cells. For example, to achieve a transmission speed of 100 Mbps, the LTE system may use Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology in a 20 MHz bandwidth. Additionally, an Adaptive Modulation & Coding (AMC) method can be applied to determine the modulation scheme and channel coding rate according to the channel conditions of the terminal. The S-GW (130) can provide a data bearer. The S-GW (130) can create or remove a data bearer under the control of the MME (125). The MME is a device responsible for various control functions as well as mobility management functions for the terminal, and can be connected to multiple base stations.

[0035] FIG. 2 illustrates a wireless protocol structure in a wireless communication system according to an embodiment of the present invention. The wireless communication system of FIG. 2 may correspond to the wireless communication system of FIG. 1. For example, the wireless communication system of FIG. 2 may include an LTE system.

[0036] Referring to FIG. 2, a wireless protocol of an LTE system according to one embodiment of the present disclosure may include PDCP (Packet Data Convergence Protocol 205, 240), RLC (Radio Link Control 210, 235), MAC (Medium Access Control 215, 230), and PHY (physical layer) (220, 225) at the terminal and ENB, respectively.

[0037] According to one embodiment, the PDCP (Packet Data Convergence Protocol) (205, 240) can perform operations such as IP header compression / recovery. For example, the main functions of the PDCP (205, 240) can be summarized as follows. Of course, the functions of the PDCP (205, 240) are not limited to the following examples.

[0038] - Header compression and decompression (ROHC (robust header compression) only)

[0039] - User data transfer function (Transfer of user data)

[0040] - Sequential delivery function (In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM)

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

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

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

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

[0045] - Timer-based SDU (service data unit) discard function (Timer-based SDU discard in uplink.)

[0046] According to one embodiment of the present disclosure, the RLC (210, 235) can perform an ARQ operation by reconstructing the PDCP Packet Data Unit (PDU) into an appropriate size. The main functions of the RLC (210, 235) can be summarized as follows. Of course, the functions of the RLC (210, 235) are not limited to the following examples.

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

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

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

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

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

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

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

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

[0055] RLC re-establishment function

[0056] According to one embodiment of the present disclosure, the MAC (215, 230) may be connected to multiple RLC layer devices configured in a terminal. Additionally, the MAC (215, 230) may perform operations of multiplexing RLC PDUs into a MAC PDU and demultiplexing RLC PDUs from the MAC PDU. The main functions of the MAC (215, 230) can be summarized as follows. Of course, the functions of the MAC (215, 230) are not limited to the following examples.

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

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

[0059] - Scheduling information reporting function

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

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

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

[0063] - MBMS service identification function

[0064] - Transport format selection function

[0065] - Padding

[0066] According to one embodiment of the present disclosure, the physical layer (PHY) (220, 225) can channel code and modulate upper layer data. Additionally, the physical layer can create OFDM symbols from the channel-coded and modulated upper layer data and transmit them over a wireless channel. Additionally, the physical layer can demodulate and channel decode OFDM symbols received through the wireless channel and transmit them to the upper layer.

[0067] FIG. 3 illustrates the structure of a wireless communication system according to an embodiment of the present invention. According to an embodiment of the present disclosure, the wireless communication system may include a next-generation mobile communication system.

[0068] Referring to FIG. 3, a wireless access network of a next-generation mobile communication system (hereinafter referred to as a new radio (NR) system or a 5th generation (5g) system) according to one embodiment of the present disclosure may be composed of a next-generation base station (New Radio Node B, hereinafter referred to as an NR gNB or NR base station) (310) and an NR CN (new radio core network) (305). A user terminal (New Radio User Equipment, hereinafter referred to as an NR UE or terminal) (315) may connect to an external network through the NR gNB (310) and the NR CN (305).

[0069] In FIG. 3, the NR gNB (310) can correspond to the eNB (Evolved Node B) of an existing LTE system. The NR gNB is connected to the NR UE (315) via a wireless channel and can provide superior service compared to the existing Node B. In next-generation mobile communication systems, since all user traffic is serviced through a shared channel, a device is required to collect status information such as the buffer status, available transmission power status, and channel status of the UEs and perform scheduling, and the NR NB (310) can handle this. A single NR gNB can typically control multiple cells.

[0070] According to one embodiment of the present disclosure, in order to achieve ultra-high-speed data transmission compared to LTE, a next-generation mobile communication system may have a maximum bandwidth greater than that of existing systems, and may additionally incorporate beamforming technology by using Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as a wireless access technology.

[0071] According to one embodiment of the present disclosure, an Adaptive Modulation & Coding (hereinafter referred to as AMC) scheme that determines a modulation scheme and a channel coding rate according to the channel conditions of a terminal may be applied.

[0072] According to one embodiment of the present disclosure, the NR CN (305) can perform functions such as mobility support, bearer configuration, and QoS configuration. For example, the NR CN can be connected to multiple base stations as a device responsible for various control functions as well as mobility management functions for terminals.

[0073] According to one embodiment of the present disclosure, the next-generation mobile communication system can also be coupled with an existing LTE system. For example, the NR CN can be connected to the MME (325) via a network interface. The MME can be connected to an existing base station eNB (330).

[0074] FIG. 4 illustrates the wireless protocol structure of a next-generation mobile communication system according to one embodiment of the present invention.

[0075] Referring to Fig. 4, the wireless protocol of the next-generation mobile communication system can be composed of NR SDAP (401, 445), NR PDCP (405, 440), NR RLC (410, 435), and NR MAC (415, 430) layers at the terminal and the NR base station, respectively.

[0076] Hereinafter, in the present disclosure, 'layered device' is a term meaning a layer of NR and may be referred to interchangeably with 'layer'.

[0077] According to one embodiment of the present disclosure, the main functions of the NR SDAP (401, 445) may include some of the following functions. Of course, the functions of the NR SDAP (401, 445) are not limited to the following examples.

[0078] User data transfer function (transfer of user plane data)

[0079] Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

[0080] Marking QoS flow ID in both DL and UL packets for uplink and downlink

[0081] A function that maps reflective QoS flow to the data bearer for the uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0082] According to one embodiment of the present disclosure, regarding SDAP layer devices (401, 445), a terminal may receive a radio resource control (RRC) message indicating whether to use the header of an SDAP layer device (405, 440) or to use the functions of an SDAP layer device (401, 445) for each PDCP layer device, for each bearer, or for each logical channel. If an SDAP header is configured, the terminal may be instructed to update or reset the mapping information for the QoS flow of the uplink and downlink and the data bearer using a NAS QoS reflective setting 1-bit indicator (NAS reflective QoS) and an AS QoS reflective setting 1-bit indicator (AS reflective QoS) of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priority, scheduling information, etc., to support smooth service.

[0083] According to one embodiment of the present disclosure, the main functions of the NR PDCP layer device (405, 440) may include some of the following functions. Of course, the functions of the NR PDCP layer device (405, 440) are not limited to the following examples.

[0084] - Header compression and decompression features (ROHC only)

[0085] - User data transfer function (Transfer of user data)

[0086] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

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

[0088] - Reordering function (PDCP PDU reordering for reception)

[0089] - Duplicate detection function (Duplicate detection of lower layer SDUs)

[0090] - Retransmission of PDCP SDUs

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

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

[0093] The reordering function of the NR PDCP layer device (405, 440) may mean a function of reordering PDCP PDUs received from the lower layer in order based on the PDCP SN (sequence number). The reordering function of the NR PDCP layer device (405, 440) may include at least one of the following: a function of transmitting data to the upper layer in the reordered order; a function of transmitting immediately without considering the order; a function of recording lost PDCP PDUs by reordering the order; a function of reporting the status of lost PDCP PDUs to the transmitting side; or a function of requesting retransmission of lost PDCP PDUs.

[0094] The main functions of an NR RLC layer device (410, 435) according to one embodiment of the present disclosure may include some of the following functions. Of course, the functions of the NR RLC layer device (410, 435) are not limited to the following examples.

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

[0096] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

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

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

[0099] - Concatenation, segmentation, and reassembly functions of RLC SDUs

[0100] - Re-segmentation function (Re-segmentation of RLC data PDUs)

[0101] - Reordering function (Reordering of RLC data PDUs)

[0102] - Duplicate detection

[0103] - Error detection function (Protocol error detection)

[0104] - RLC SDU discard function

[0105] RLC re-establishment function

[0106] The in-sequence delivery function of the NR RLC layer device (410, 435) may refer to a function of delivering RLC SDUs received from a lower layer to an upper layer in order. For example, the in-sequence delivery function of the NR RLC layer device (410, 435) may include a function of reassembling the multiple RLC SDUs received in a divided manner and delivering them to an upper layer when a single RLC SDU is originally received in a divided manner. For example, the in-sequence delivery function of the NR RLC layer device (410, 435) may include a function of rearranging the multiple RLC PDUs received in a divided manner based on an RLC SN (sequence number) or a PDCP SN (sequence number). For example, the in-sequence delivery function of the NR RLC layer device (410, 435) may include a function of recording lost RLC PDUs by rearranging the order. For example, the sequential delivery function of the NR RLC layer device (410, 435) may include a function to report the status of lost RLC PDUs to the transmitting side. For example, the sequential delivery function of the NR RLC layer device (410, 435) may include a function to request retransmission of lost RLC PDUs. For example, the sequential delivery function of the NR RLC layer device (410, 435) may include a function to deliver only the RLC SDUs prior to the lost RLC SDU in order to the upper layer if there is a lost RLC SDU. For example, the sequential delivery function of the NR RLC layer device (410, 435) may include a function to deliver all RLC SDUs received before the timer started to the upper layer in order if a predetermined timer has expired even if there is a lost RLC SDU.For example, the sequential delivery function of the NR RLC layer device (410, 435) may include the function of delivering all RLC SDUs received up to that point to the upper layer in order when a predetermined timer expires, even if there are lost RLC SDUs. For example, the sequential delivery function of the NR RLC layer device (410, 435) may process RLC PDUs in the order 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). For example, when the NR RLC layer device (410, 435) receives a segment, it may receive segments stored in a buffer or to be received later, reconstruct them into a single complete RLC PDU, and then deliver the reconstructed RLC PDU to the PDCP layer device (410, 435).

[0107] According to one embodiment of the present disclosure, the NR RLC layer device (410, 435) may not include a concatenation function. For example, the concatenation function may be performed in the NR MAC layer device (415, 430) or replaced by the multiplexing function of the NR MAC layer device (415, 430).

[0108] The 'out-of-sequence delivery' of the NR RLC layer device (410, 435) may mean a function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order. For example, the out-of-sequence delivery function of the NR RLC layer device (410, 435) may include a function of reassembling and delivering RLC SDUs when a single RLC SDU is originally received divided into multiple RLC SDUs. For example, the out-of-sequence delivery function of the NR RLC layer device (410, 435) may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs and sorting the order to record the lost RLC PDUs.

[0109] According to one embodiment of the present disclosure, an NR MAC (415, 430) may be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include some of the following functions, but the functions of the NR MAC layer devices (415, 430) are not limited to the following examples.

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

[0111] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)

[0112] - Scheduling information reporting function

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

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

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

[0116] - MBMS service identification function

[0117] - Transport format selection function

[0118] - Padding

[0119] According to one embodiment of the present disclosure, an NR PHY layer device (420, 425) can perform the operation of channel coding and modulating data transmitted from an upper layer, making it into an OFDM symbol and transmitting it to a wireless channel, or demodulating and channel decoding an OFDM symbol received through a wireless channel and transmitting it to an upper layer.

[0120] FIG. 5 illustrates an example in which a terminal in an RRC idle mode (RRC_IDLE) or RRC disabled state (RRC_INACTIVE) performs a cell reselection evaluation process in a next-generation mobile communication system according to an embodiment of the present disclosure.

[0121] In the present disclosure, the ‘cell reselection evaluation process’ may mean a procedure for determining whether to maintain the current serving cell or reselect the cell to a neighbor cell when the service quality of the serving cell currently camp-on becomes lower than the service quality of a neighbor cell due to a predetermined reason or movement, when a terminal in RRC idle mode (RRC_IDLE) or RRC inactive state (RRC_INACTIVE).

[0122] Here, the cell that the terminal itself re-selects may mean a cell using the same NR frequency (NR intra-frequency or serving NR frequency) as the serving cell currently camp-on, a cell using a different NR frequency (NR inter-frequency) from the serving cell, or a cell on a frequency using a different Radio Access Technology (hereinafter RAT) (inter-RAT frequency).

[0123] Referring to FIG. 5, a terminal (5-01) according to one embodiment of the present disclosure may be in an RRC connection mode (RRC_CONNECTED) by establishing an RRC connection with an NR cell (5-02) (503).

[0124] According to one embodiment of the present disclosure, an NR cell (502) may transmit an RRC disconnection message (RRCRelease) (504) to disconnect the RRC connection with a terminal (501) in an RRC connection mode.

[0125] According to one embodiment of the present disclosure, if the message contains suspension configuration information (suspendConfig), the terminal (501) may transition (505) to an RRC inactive mode (RRC_INACTIVE). If the message does not contain suspendConfig, the terminal (501) may transition (505) to an RRC idle mode (RRC_IDLE).

[0126] According to one embodiment of the present disclosure, the RRC disconnection message may include cellReselectionPriorities for the terminal (501) to perform cell reselection. The cellReselectionPriorities may contain at least one value among freqPriorityListEUTRA, freqPriorityListNR, and t320. If the value t320 is included, the terminal (501) may drive the T320 timer with that value.

[0127] According to one embodiment of the present disclosure, the RRC disconnection message (RRCRelease) may include configuration information such as that shown in Table 1 below.

[0128]

[0129]

[0130]

[0131]

[0132]

[0133] According to one embodiment of the present disclosure, in step 513, a terminal (501) in an RRC idle mode or RRC disabled state can obtain essential system information from an NR cell (502). For example, the essential system information may include a Master Information Block (MIB) and a System Information Block 1 (SIB1).

[0134] According to one embodiment of the present disclosure, a terminal (501) in an RRC idle mode (RRC_IDLE) or RRC inactive state (RRC_INACTIVE) at step 515 may perform a cell selection procedure based on the essential system information obtained at step 513. For example, the terminal (501) may find an NR suitable cell belonging to a selected PLMN (public land mobile network) or SNPN (standalone non-public network) and camp on to that cell. The cell that the terminal camps on may be referred to as a serving cell. In the present disclosure, the cell that the terminal (501) camps on may be referred to as a 'serving cell'. In the present disclosure, based on the 3GPP standard document "38.304: User Equipment (UE) procedures in Idle mode and RRC Inactive state", a cell in which the conditions listed in Table 2 below are satisfied may be defined as a 'suitable cell'.

[0135]

[0136] According to one embodiment of the present disclosure, the terminal (501) can determine that the cell selection criteria are fulfilled if the following [Equation 1] is satisfied.

[0137] [Mathematical Formula 1]

[0138]

[0139]

[0140] According to one embodiment of the present disclosure, in step 520, a terminal (501) in an RRC idle mode or RRC disabled state may obtain system information for cell reselection containing cell reselection information from a serving cell (502) to perform a cell reselection evaluation process. For example, the terminal (501) may obtain SIB2, SIB3, SIB4, and SIB5 from the serving cell (502). According to one embodiment of the present disclosure, SIB2 may include information or parameters commonly applied to the reselection of NR intra-frequency, NR inter-frequency, and inter-RAT frequency cells by the terminal (501) in an RRC idle mode or RRC disabled state, and NR intra-frequency cell reselection information excluding information related to NR intra-frequency surrounding cells. For example, SIB2 may include one cell reselection priority setting information for the serving NR frequency (the frequency to which the currently camp-on cell belongs). In the present disclosure, the cell reselection priority setting information may be referred to as a term meaning cellReselectionPriority and cellReselectionSubPriority. According to one embodiment, cellReselectionPriority may accommodate an integer value. For example, cellReselectionPriority may accommodate one integer value from 0 to 7. According to one embodiment, cellReselectionSubPriority may accommodate a decimal value. For example, cellReselectionSubPriority may accommodate one decimal value from 0.2, 0.4, 0.6, or 0.8.

[0141] According to one embodiment of the present disclosure, when both cellReselectionPriority and cellReselectionSubPriority are signaled, the terminal (501) can derive a cell reselection priority value by adding the two values. Here, a larger cell reselection priority value may mean a higher priority, but the value indicating the priority is not limited thereto.

[0142] According to one embodiment of the present disclosure, cell reselection setting information broadcast in SIB2 may be as shown in Table 3 below.

[0143]

[0144]

[0145]

[0146]

[0147] According to one embodiment of the present disclosure, SIB3 may include neighboring cell information or parameters for a terminal (501) in an RRC idle mode or an RRC disabled state to re-select an NR intra-frequency cell. For example, SIB3 may broadcast an NR intra-frequency cell list (intraFreqNeighCellList), a cell list where NR intra-frequency cell re-selection is allowed (intraFreqAllowedCellList), and a cell list where NR intra-frequency cell re-selection is not allowed (intraFreqExcludedCellList). For example, SIB3 may broadcast the information of Table 4 below.

[0148]

[0149]

[0150] According to one embodiment of the present disclosure, SIB4 may include information or parameters for a terminal in an RRC idle mode or an RRC disabled state to reselect an NR inter-frequency cell. For example, SIB4 may broadcast one or more NR inter-frequencies and may broadcast one cell reselection priority setting information for each NR inter-frequency. Here, 'cell reselection priority setting information for each NR inter-frequency' may mean cell reselection priority setting information mapped to each NR inter-frequency described above. For example, cell reselection priority setting information for each NR inter-frequency may mean cellReselectionPriority or cellReselectionSubPriority mapped to each NR inter-frequency.

[0151] According to one embodiment of the present disclosure, one cell reselection priority setting information for each inter-frequency may be optionally broadcast. For example, the information in Table 5 below may be broadcast to SIB4.

[0152]

[0153]

[0154]

[0155]

[0156] According to one embodiment of the present disclosure, SIB5 may include information or parameters for a terminal in an RRC idle mode or RRC disabled state to reselect an inter-RAT frequency cell. For example, SIB5 may broadcast one or more EUTRA frequencies. For example, SIB5 may broadcast one cell reselection priority setting information for each EUTRA frequency. Here, 'cell reselection priority setting information for each EUTRA frequency' may mean cell reselection priority setting information mapped to each EUTRA frequency. For example, cell reselection priority setting information for each EUTRA frequency may mean cellReselectionPriority or cellReselectionSubPriority mapped to each EUTRA frequency.

[0157] According to one embodiment of the present disclosure, one cell reselection priority setting information for each EUTRA frequency may be broadcast optionally. For example, the information in Table 6 below may be broadcast to SIB5.

[0158]

[0159]

[0160] According to one embodiment of the present disclosure, a terminal (501) in an RRC idle mode or an RRC disabled state may perform a cell reselection evaluation process. For example, the cell reselection evaluation process may include a reselection priorities handling step (525), a frequency measurement step (530) by applying measurement rules for cell re-selection, and a cell reselection step (535) by evaluating cell reselection criteria.

[0161] According to one embodiment of the present disclosure, at step 525, a terminal (501) in an RRC idle mode or RRC disabled state may determine a re-selection priority based on an RRC release message received at step 504 or system information received at step 520.

[0162] According to one embodiment of the present disclosure, if the RRC disconnection message received in step 504 includes cellReselectionPriorities, and if there is no t320 timer value in cellReselectionPriorities or if the t320 timer value is set and the T320 timer is running, the terminal (501) can determine the reselection priority according to the RRC disconnection message. That is, if the cellReselectionPriorities included in the RRC disconnection message can be applied, the terminal (501) can determine the reselection priority according to the RRC disconnection message.

[0163] According to one embodiment of the present disclosure, the terminal (501) can determine the reselection priority based on the system information received in step 520 when, in step 525, the RRC disconnection message does not include cellReselectionPriorities or cellReselectionPriorities are released.

[0164] According to one embodiment of the present disclosure, the terminal (501) can determine whether the cell reselection priority for each NR inter-frequency or inter-RAT frequency has the same cell reselection priority as the NR frequency to which the serving cell belongs, has a higher cell reselection priority than the NR frequency to which the serving cell belongs, or has a lower cell reselection priority than the NR frequency to which the serving cell belongs, based on the cell reselection priority value mapped to the NR frequency to which the serving cell belongs. For example, if the terminal (501) has a cell reselection priority value mapped to the NR frequency to which the serving cell currently camp-on belongs in the system information obtained in step 520, a cell reselection priority value of inter NR frequency 1, a cell reselection priority value of inter NR frequency 2, a cell reselection priority value of inter NR frequency 3, a cell reselection priority value of EUTRA frequency 1, and a cell reselection priority value of EUTRA frequency 1, then inter NR frequency 1 and EUTRA frequency 1 are determined to have a lower reselection priority, the cell reselection priority of inter NR frequency 2 is determined to have an equal reselection priority, and the cell reselection priority of inter NR frequency 3 is determined to have a higher reselection priority.

[0165] According to one embodiment of the present disclosure, a terminal (501) in an RRC idle mode or RRC disabled state at step 530 may perform a frequency measurement for cell reselection. For example, the terminal (501) may perform the frequency measurement using the following measurement rule according to the cell reselection priority determined at step 525. As a result, the terminal (501) may minimize battery consumption.

[0166] - According to one embodiment, the terminal (501) may not perform NR intra-frequency measurement if the following condition 1 is satisfied. Otherwise (for example, if the following condition 1 is not satisfied), the terminal (501) may perform NR intra-frequency measurement.

[0167] -- Condition 1: The serving cell's receive level (Srxlev) is greater than the SIntraSearchP threshold and the serving cell's receive quality (Squal) is greater than the SIntraSearchQ threshold (Serving cell fulfils Srxlev > SIntraSearchP and Squal > SIntraSearchQ).

[0168] - For NR inter-frequency or inter-RAT frequency that has a higher reselection priority than the current serving cell's NR frequency, the terminal (501) can perform measurements according to the 3GPP TS 38.133 standard.

[0169] - For an NR inter-frequency with a reselection priority lower than or equal to the NR frequency of the current serving cell and an inter-RAT frequency with a reselection priority lower than the NR frequency of the current serving cell, the terminal (501) may not perform a measurement if condition 2 below is satisfied. Otherwise (for example, if condition 2 below is not satisfied), the terminal (501) may measure cells in an NR inter-frequency with a reselection priority lower than or equal to the NR frequency, or cells in an inter-RAT frequency with a reselection priority lower than the NR frequency.

[0170] -- Condition 2: The serving cell's receive level (Srxlev) is greater than the SnonIntraSearchP threshold and the serving cell's receive quality (Squal) is greater than the SnonIntraSearchQ threshold (Serving cell fulfils Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ).

[0171] According to one embodiment of the present disclosure, the aforementioned threshold values ​​(SintraSearchP, SintraSearchQ, SnonIntraSearchP, SnonIntraSearchQ) may be broadcast in the system information obtained in step 520.

[0172] According to one embodiment of the present disclosure, a terminal (501) in an RRC idle mode or RRC disabled state at step 535 may determine to reselect a cell that satisfies cell reselection criteria based on the measurement value performed at step 530. Cell reselection criteria may vary depending on the cell reselection priority. If multiple cells satisfying the cell reselection criteria have different cell reselection priorities, reselecting a frequency / RAT cell with a higher priority may take precedence over reselecting a frequency / RAT cell with a lower priority (Cell reselection to a higher priority RAT / frequency shall take precedence over a lower priority RAT / frequency if multiple cells of different priorities fulfil the cell reselection criteria). Specifically, the operation of the terminal regarding the reselection criteria for an inter-frequency / inter-RAT cell that has a higher priority than the frequency of the currently serving cell is as follows.

[0173] - 1st operation:

[0174] -- In one embodiment, a threshold for threshServingLowQ is broadcast in SIB2 and, if 1 second has passed since the terminal camped on to the current serving cell, the signal quality (Squal) of the inter-frequency / inter-RAT cell is greater than the threshold ThreshX,HighQ during a specific time interval TreselectionRAT (Squal > ThreshX,HighQ during a time interval TreselectionRAT), the terminal performs reselection to the corresponding inter-frequency / inter-RAT cell.

[0175] - Second operation:

[0176] -- If the terminal is unable to perform the first operation, it may perform the second operation.

[0177] -- If 1 second has passed since the terminal camped on to the current serving cell and the reception level (Srxlev) of the inter-frequency / inter-RAT cell is greater than the threshold ThreshX,HighP during a specific time interval TreselectionRAT (Srxlev > ThreshX, HighP during a time interval TreselectionRAT), the terminal can perform reselection to the corresponding inter-frequency / inter-RAT cell.

[0178] According to one embodiment, the terminal has signal quality (Squal) of an inter-frequency cell, a reception level (Srxlev), and threshold values ​​(Threh X, HighQ , Thresh X, HighP ), Treselection RAT The values ​​perform the first or second operation based on the information contained in the SIB4 broadcast from the serving cell, and the signal quality (Squal), reception level (Srxlev), and threshold (Thresh) of the inter-RAT cell X,HighQ, Thresh X, HighP ), TreselectionRAT The values ​​can perform the first or second operation based on the information contained in SIB5 broadcast from the serving cell. For example, in SIB4, Q qualmin Value or Q rxlevmin Values, etc. may be included. The terminal, Q included in SIB4 qualmin Value or Q rxlevmin The signal quality (Squal) or reception level (Srxlev) of an inter-frequency cell can be derived based on values, etc. If there are multiple cells in an NR frequency that satisfy a high cell reselection priority, the terminal can perform cell reselection on the cell with the highest rank (highest ranked cell) among the cells that satisfy the reselection criteria for intra-frequency / inter-frequency cells that have the same priority as the frequency of the current serving cell described below.

[0179] In addition, the terminal's operation regarding the reselection criteria for intra-frequency / inter-frequency cells having the same priority as the current serving cell's frequency is as follows.

[0180] - Third operation:

[0181] -- If the signal quality (Squal) and reception level (Srxlev) of an intra-frequency / inter-frequency cell are greater than 0, the cell-specific rank can be derived based on the measured value (RSRP) (The UE shall perform ranking of all cells that fulfills the cell selection criterion S). The ranks of the serving cell and surrounding cells can be calculated respectively through [Equation 2] below.

[0182] [Mathematical Formula 2]

[0183]

[0184] In [Equation 2], Qmeas,s is the RSRP measurement of the serving cell, Qmeas,n is the RSRP measurement of the surrounding cell, Qhyst is the hysteresis value of the serving cell, and Qoffset is the offset between the serving cell and the surrounding cell. The Qhyst value is included in SIB2 and is used commonly for intra-frequency / inter-frequency cell reselection. In the case of intra-frequency cell reselection, Qoffset is signaled per cell, applies only to the designated cell, and is included in SIB3. In the case of inter-frequency cell reselection, Qoffset is signaled per cell, applies only to the designated cell, and may be included in SIB4. If the Rank of the surrounding cell obtained from [Equation 2] is greater than the Rank of the serving cell (Rn > Rs), the terminal can perform reselection to the optimal cell among the surrounding cells.

[0185] --- In [Mathematical Equation 2], Qoffset temp is an offset temporarily applied to the cell, which may refer to the connEstFailOffset included in ConnEstFailureControld broadcast on SIB1, and Qoffset temp This can be applied in the event of an RRC connection failure (e.g., when the T300 timer expires).

[0186] According to one embodiment, the operation of the terminal regarding the reselection criteria of an inter-frequency / inter-RAT cell having a lower priority than the frequency of the current serving cell is as follows in the fourth operation below.

[0187] - 4th Action:

[0188] -- According to one embodiment, if a threshold for threshServingLowQ is broadcast in SIB2 and 1 second has passed since the terminal camped on to the current serving cell, and the signal quality (Squal) of the current serving cell is smaller than the threshold ThreshServing, LowQ (Squal < ThreshServing, LowQ) and the signal quality (Squal) of the inter-frequency / inter-RAT cell is larger than the threshold ThreshX, LowQ during a specific time interval TreselectionRAT (Squal > ThreshX, LowQ during a time interval TreselectionRAT), the terminal can perform reselection to the corresponding inter-frequency / inter-RAT cell.

[0189] - Fifth Action:

[0190] -- If the terminal is unable to perform the fourth operation, it may perform the fifth operation.

[0191] -- If 1 second has passed since the terminal camped on to the current serving cell, and the reception level (Srxlev) of the current serving cell is less than the threshold ThreshServing, LowP (Srxlev < ThreshServing, LowP), and the reception level (Srxlev) of the inter-frequency / inter-RAT cell is greater than the threshold ThreshX, LowQ during a specific time interval TreselectionRAT (Srxlev > ThreshX,LowP during a time interval TreselectionRAT), the terminal can perform reselection to the corresponding inter-frequency / inter-RAT cell.

[0192] According to one embodiment, a fourth or fifth operation for an inter-frequency cell of a terminal comprises threshold values ​​(ThreshServing, LowQ, ThreshServing, LowP) included in SIB2 broadcast from a serving cell and the signal quality (Squal), reception level (Srxlev), and threshold values ​​(Threh) of the inter-frequency cell included in SIB4 broadcast from a serving cell. X, LowQ, Thresh X, LowP ), Treselection RAT It can be performed based on. Additionally, the fourth or fifth operation for the inter-RAT cell of the terminal is based on the threshold values ​​(ThreshServing, LowQ, ThreshServing, LowP) included in SIB2 broadcast from the serving cell and the signal quality (Squal), reception level (Srxlev), and threshold values ​​(Thresh) of the inter-RAT cell included in SIB5 broadcast from the serving cell. X,LowQ , Thresh X, LowP ), Treselection RAT It can be performed based on. For example, in SIB4, Q qualmin Value or Q rxlevmin Values, etc. are included, and the terminal is Q included in SIB4 qualmin Value or Q rxlevmin The signal quality (Squal) or reception level (Srxlev) of an inter-frequency cell can be derived based on values, etc. If there are multiple cells in an NR frequency that satisfy a high cell reselection priority, the terminal can perform cell reselection to the highest-ranked cell among the cells that satisfy the reselection criteria for intra-frequency / inter-frequency cells that have the same priority as the frequency of the current serving cell described later.

[0193] According to one embodiment of the present disclosure, a terminal in an RRC idle mode or RRC disabled state at step 540 may receive system information broadcast from a candidate target cell before finally re-selecting a candidate target cell. For example, at step 540, the terminal may receive an MIB or SIB 1 broadcast from a candidate target cell. The terminal may determine the final suitability of a candidate target cell based on receiving system information broadcast from the candidate target cell. For example, the terminal may determine whether the reception level (Srxlev) and reception quality (Squal) of the candidate target cell satisfy a cell selection criterion referred to as the S-criterion (Equation 1) (Srxlev > 0 AND Squal > 0) based on the system information received from the candidate target cell. Based on the determination that mathematical formula 1 is satisfied and the candidate target cell is suitable, the terminal can re-select a candidate target cell that satisfies the criteria.

[0194] FIG. 6 illustrates a flowchart of a procedure in which a terminal in RRC idle mode (RRC_IDLE) and RRC inactive mode (RRC_INACTIVE) performs idle / inactive measurements according to one embodiment of the present disclosure, and a base station quickly establishes Carrier Aggregation or Dual Connectivity to the terminal based on the idle / inactive measurement results recovered from the terminal.

[0195] Referring to FIG. 6, the terminal (601) may be in an RRC connection mode (RRC_CONNECTED) state by establishing an RRC connection with the base station (602).

[0196] According to one embodiment of the present disclosure, in step 610, the base station (602) may transmit a message to the terminal (601) to retrieve radio access capability information of the terminal (601). For example, the base station (602) may transmit a terminal capability request message (UECapabilityEnquiry) to the terminal (601).

[0197] According to one embodiment of the present disclosure, in step 615, the terminal (601) may transmit a terminal capability information message (UECapabilityInformation) to the base station (602). The terminal capability information message may include at least one of the following parameters.

[0198] - idleInactiveNR-MeasReport-r16, idleInactiveNR-MeasReport-r17

[0199] Parameters idleInactiveNR-MeasReport-r16 and idleInactiveNR-MeasReport-r17 are terminal capability parameters that indicate, in accordance with 3GPP technical specification 38.331, the ability of the terminal to support configuration of NR SSB measurements in RRC_IDLE / RRC_INACTIVE mode and to report the corresponding results upon network request. If parameters idleInactiveNR-MeasReport-r16 and idleInactiveNR-MeasReport-r17 are indicated differently in FR1 and FR2, each indication may correspond to the frequency range of the measured target cell. idleInactiveNR-MeasReport-r17 may represent terminal capability parameters for FR2-2.

[0200] -idleInactiveNR-MeasBeamReport-r16

[0201] The parameter idleInactiveNR-MeasBeamReport-r16 is a terminal capability parameter that indicates, in accordance with 3GPP technical specification 38.331, the ability of a terminal to support beam level measurements in RRC_IDLE / RRC_INACTIVE mode and to report the corresponding beam measurement results upon network request. A terminal that supports this terminal capability parameter may also support idleInactiveNR-MeasReport-r16. If this parameter is indicated for FR1 and FR2 differently, each indication corresponds to the frequency range of the measured target cell.

[0202] -idleInactiveEUTRA-MeasReport-r16

[0203] -- The parameter idleInactiveEUTRA-MeasReport-r16 is a terminal capability parameter that indicates whether the UE supports configuration of E-UTRA measurements in RRC_IDLE / RRC_INACTIVE and reporting of the corresponding results upon network request as specified in TS 38.331.

[0204] -idleInactive-ValidityArea-r16

[0205] The parameter idleInactive-ValidityArea-r16 is a terminal capability parameter that indicates whether the terminal supports configuration of a validity area for NR measurements in RRC_IDLE / RRC_INACTIVE as specified in TS 38.331.

[0206] According to one embodiment of the present disclosure, in step 620, the base station (602) may transmit an RRC disconnection message (RRCRelease) to the terminal (601). The RRC disconnection message may include information about a measurement setting (measIdleConfig) that the terminal stores and uses in RRC idle mode or RRC disabled mode. The base station (602) may set up or disable a MeasIdleConfigDedicated Information Element (hereinafter IE) through the measIdleConfig. The MeasIdleConfigDedicated IE may include at least one of the following.

[0207] - measIdleCarrierListNR-r16

[0208] -- measIdleCarrierListNR-r16 may mean a list containing NR carriers (MeasIdleCarrierNR-16) that the terminal will measure in RRC idle mode or RRC disabled mode.

[0209] -measIdleCarrierListEUTRA-r16

[0210] -- measIdleCarrierListEUTRA-r16 may mean a list containing E-UTRA carriers (MeasIdleCarrierEUTRA-r16) that the terminal will measure in RRC idle mode or RRC disabled mode.

[0211] - measIdleDuration-r16

[0212] -- measIdleDuration-r16 may represent a field containing the duration for performing idle / inactive measurements while in RRC_IDLE or RRC_INACTIVE. For example, a value of sec10 may mean 10 seconds, and a value of sec30 may mean 30 seconds.

[0213] - validityAreaList-r16

[0214] validityAreaList-r16 may mean a field containing the list of frequencies and optionally, for each frequency, a list of cells within the UE is required to perform measurements while in RRC_IDLE and RRC_INACTIVE.

[0215] According to one embodiment, the configuration information included in MeasIdleConfigDedicated IE and the description of each configuration information may be as shown in [Table 7] below.

[0216]

[0217]

[0218]

[0219]

[0220] According to one embodiment, if the RRC disconnection message includes measIdleConfig, the terminal may perform the following procedures in order.

[0221] - The terminal can stop the running T331 timer if T331 is running. Additionally, the terminal can release the terminal variable VarMeasIdleConfig.

[0222] If the measIdleConfig is set to setup,

[0223] -- The terminal can store the received measIdleDuration in VarMeasIdleConfig.

[0224] -- The terminal can start the T331 timer with the value set to measIdleDuration.

[0225] -- The terminal can store the received measIdleCarrierListNR in VarMeasIdleConfig if the measIdleConfig contains measIdleCarrierListNR.

[0226] -- The terminal can store the received measIdleCarrierListEUTRA in VarMeasIdleConfig if the measIdleConfig contains measIdleCarrierListEUTRA.

[0227] -- The terminal can store the received validityAreaList in VarMeasIdleConfig if the measIdleConfig contains validityAreaList.

[0228] According to one embodiment of the present disclosure, in step 625, the terminal (601) may transition to an RRC idle mode and perform a cell selection process. The cell selection process may include the cell selection process described above with reference to FIG. 5.

[0229] According to one embodiment of the present disclosure, at step 630, the terminal (601) may obtain system information related to idle / inactive measurement. For example, interFreqCarrierList broadcast via SIB4 may include parameters to be used for NR idle / inactive measurement. Additionally, measIdleConfigSIB broadcast via SIB11 may include information related to idle / inactive measurement. For example, measIdleConfigSIB may include measIdleCarrierListNR and measIdleCarrierLisEUTRA described above in step 620.

[0230] According to one embodiment of the present disclosure, in step 635, the terminal (601) can update the idle / inactive measurement setting if the T331 timer is running and the SDT (small data transmission) procedure is not in progress, and at least one of the following conditions is satisfied.

[0231] - When selecting a cell when switching from RRC_IDLE or RRC_INACIVE to RRC_CONNECTED or RRC_INACTIVE

[0232] - Upon update of system information (SIB4 or SIB11), eg due to intra-RAT cell (re)selection

[0233] Specifically, the terminal (601) can perform the following procedures in sequence when the T331 timer is running in RRC idle mode.

[0234] - If the terminal variable VarMeasIdleConfig does not include either a measIdleCarrierListEUTRA or a measIdleCarrierListNR received from the RRCRelease message

[0235] -- If the UE supports idleInactiveEUTRA-MeasReport,

[0236] --- If the SIB11 includes the measIdleConfigSIB and contains measIdleCarrierListEUTRA

[0237] ---- You can store or replace the measIdleCarrierListEUTRA of measIdleConfigSIB of SIB11 within VarMeasIdleConfig

[0238] --- Otherwise (i.e., if measIdleConfigSIB does not exist in SIB11 or if measIdleCarrierListEUTRA is not broadcast to measIdleConfigSIB)

[0239] If measIdleCarrierListEUTRA is stored in VarMeasIdleConfig, you can remove it.

[0240] -- If the UE supports idleInactiveNR-MeasReport,

[0241] --- If SIB11 includes measIdleConfigSIB and contains measIdleCarrierListNR

[0242] ---- Store or replace the measIdleCarrierListNR of measIdleConfigSIB of SIB11 within VarMeasIdleConfig

[0243] --- Otherwise (i.e., if measIdleConfigSIB does not exist in SIB11 or measIdleCarrrierListNR is not broadcast to measIdleConfigSIB)

[0244] If measIdleCarrierListNR is stored in VarMeasIdleConfig, you can remove it.

[0245] - For each entry in the measIdleCarrierListNR within VarMeasIdleConfig that does not contain an ssb-MeasConfig received from the RRCRelease message, the terminal (601) may change or disable the SSB measurement settings to those in SIB4 / SIB11. For example, the terminal (601) may change or disable the SSB measurement settings according to the following [Table 8].

[0246]

[0247] According to one embodiment of the present disclosure, in step 640, the terminal (601) may perform idle / inactive measurements. For example, the terminal (601) in an RRC idle mode or RRC disabled mode state may perform idle / inactive measurements according to the following [Table 9] when the T331 timer is running and the SDT procedure is not in progress.

[0248]

[0249]

[0250]

[0251]

[0252] According to one embodiment of the present disclosure, in step 641, the terminal (601) can trigger Random Access to establish an RRC connection with the base station (602).

[0253] According to one embodiment of the present disclosure, in step 642, when random access is triggered, the terminal (601) can select a PRACH occasion and transmit a Random Access Preamble to the base station.

[0254] According to one embodiment of the present disclosure, in step 643, when a base station receives a random access preamble, the base station may transmit a Random Access Response (hereinafter RAR) message for the random access preamble to a terminal.

[0255] According to one embodiment of the present disclosure, a terminal (601) in RRC idle mode can establish reverse transmission synchronization with a base station (602) through steps 642 and 643.

[0256] According to one embodiment of the present disclosure, an RRC idle mode terminal (601) that has established reverse transmission synchronization can perform an RRC connection establishment procedure with a base station (602). First, in step 645, the terminal can transmit an RRC connection establishment request message (RRCSetupRequest) to the base station. The RRC connection establishment request message may include an identifier (ue-Identity) and an establishment cause, etc., for the terminal to establish an RRC connection. In step 650, if the base station receives the RRC connection establishment request message from the terminal, it can transmit an RRC connection establishment message (RRCSetup) to the terminal. In step 651, if the terminal receives the RRC setup message from the base station, it can stop the T331 timer if it is running, set up wireless resource setup information, and switch to an RRC connection mode (RRC_CONNECTED).

[0257] According to one embodiment of the present disclosure, in step 655, the terminal that has switched to the RRC connection mode may transmit an RRC connection setup complete (RRCSetupComplete) message to the base station, including an indicator (idleMeasAvailable) indicating that there is an idle / inactive measurement result, if at least one of the following conditions is satisfied.

[0258] - If the SIB1 contains idleModeMeasurementsNR and the UE has NR idle / inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport

[0259] - If the SIB1 contains idleModeMeasurementsEUTRA and the UE has E-UTRA idle / inactive measurement information available in VarMeasIdleReport

[0260] According to one embodiment of the present disclosure, in step 660, if the base station has successfully performed an RRC connection establishment procedure with the terminal, the base station (602) may perform an RRC connection reconfiguration procedure with the terminal (601). In step 660, the base station may transmit RRC connection reconfiguration setting information to the terminal.

[0261] According to one embodiment of the present disclosure, in step 665, the terminal that receives the RRC connection reconfiguration message applies the configuration information included in the RRC connection reconfiguration message, and the terminal can transmit an RRC connection reconfiguration completion message (RRCReconfigurationComplete) to the base station.

[0262] According to one embodiment of the present disclosure, at step 670, the base station (602) may perform a terminal information (UE Information) procedure to retrieve idle / inactive measurement information from the terminal (601). The base station may initiate this UE information procedure only after successful security activation. The base station may transmit a terminal information request message (UEInformationRequest) to the terminal, which includes an indicator (idleModeMeasurementReq) to report the idle / inactive measurement results.

[0263] According to one embodiment of the present disclosure, in step 675, a terminal that receives a UEInformationRequest containing idleModeMeasurementReq can perform the following procedure to transmit a terminal information response message (UEInformationResponse) to a base station that includes at least one of measIdleResultEUTRA and measIdleResultNR.

[0264] - If the UE has stored a VarMeasIdleReport that contains measurement information concerning cells other than the PCell

[0265] -- The terminal may set the measResultIdleEUTRA in the UEInformationResponse to the value of measReportIdleEUTRA in the VarMeasIdleReport, if available

[0266] -- The terminal can set the measResultIdleNR in the UEInformationResponse message to the value of measReportIdleNR in the VarMeasIdleReport, if available

[0267] -- The terminal can discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers.

[0268] According to one embodiment of the present disclosure, a base station (602) may perform an RRC Connection Reconfiguration procedure to set Carrier Aggregation (CA) or Dual Connectivity (DC) for a terminal based on idle / inactive measurement information recovered from a terminal (601). That is, at step 680, the base station (602) may transmit an RRC Connection Reconfiguration message containing CA or DC settings to the terminal (601). At step 685, the terminal (601) may apply the CA or DC settings included in the RRC Connection Reconfiguration message received from the base station (602) and transmit an RRC Connection Reconfiguration Complete message to the base station (602).

[0269] FIG. 7 illustrates a flowchart of a procedure in which a terminal in RRC idle mode (RRC_IDLE) and RRC inactive mode (RRC_INACTIVE) performs idle / inactive measurements according to an embodiment of the present invention, and a base station quickly establishes Carrier Aggregation (CA) or Dual Connectivity (DC) to the terminal based on the idle / inactive measurement results recovered from the terminal.

[0270] According to one embodiment of the present disclosure, in step 705, the terminal (701) may be in an RRC connection mode (RRC_CONNECTED) state by establishing an RRC connection with the base station (702).

[0271] According to one embodiment of the present disclosure, in step 710, the base station (702) may transmit a terminal capability request message (UECapabilityEnquiry) to the terminal (701) to retrieve radio access capability information of the terminal (701).

[0272] According to one embodiment of the present disclosure, in step 715, the terminal (701) may transmit a terminal capability information message (UECapabilityInformation) to the base station (702). Step 715 may include step 615 described above with reference to FIG. 6.

[0273] According to one embodiment of the present disclosure, in step 720, the base station (702) may transmit an RRC disconnection message (RRCRelease) to the terminal (701). The RRC disconnection message may contain a measurement setting (measIdleConfig) that the terminal stores and uses in RRC idle mode or RRC disabled mode according to the embodiment described above with reference to FIG. 6. If the RRC disconnection message contains measIdleConfig, the terminal may apply measIdleConfig according to step 620 described above with reference to FIG. 6. Additionally, the RRC disconnection message may contain suspend setting information (suspendConfig) for the terminal to switch to RRC disabled mode.

[0274] According to one embodiment of the present disclosure, in step 725, the terminal (701) may transition to an RRC disabled mode and perform a cell selection process. The cell selection process may include the cell selection process described above with reference to FIG. 5.

[0275] According to one embodiment of the present disclosure, at step 730, the terminal (701) may obtain system information related to idle / inactive measurement. For example, interFreqCarrierList broadcast via SIB4 may include parameters to be used for NR idle / inactive measurement. measIdleConfigSIB broadcast via SIB11 may include information related to idle / inactive measurement. measIdleConfigSIB may include measIdleCarrierListNR and measIdleCarrierLisEUTRA described above in step 720.

[0276] According to one embodiment of the present disclosure, in step 735, the terminal (701) in RRC disabled mode can update idle / inactive measurements according to step 635 described above with reference to FIG. 6 when the T331 timer is running and the SDT (small data transmission) procedure is not in progress.

[0277] According to one embodiment of the present disclosure, in step 740, the terminal (701) may perform an idle / inactive measurement. Step 740 may correspond to step 640 of FIG. 6.

[0278] According to one embodiment of the present disclosure, in step 741, the terminal (701) may trigger Random Access to establish an RRC connection with the base station (702). When Random Access is triggered, in step 742, the terminal (701) may select a PRACH occasion and transmit a Random Access Preamble to the base station (702). When the base station (702) receives the Random Access Preamble, in step 743, the base station (702) may transmit a Random Access Response (RAR) message to the terminal (701). The terminal (701), which is in an RRC disabled mode, may establish a reverse transmission synchronization with the base station (702) through steps 742 to 743.

[0279] According to one embodiment of the present disclosure, an RRC disabled mode terminal (701) that has established reverse transmission synchronization can perform an RRC connection resume procedure with a base station (702). In step 745, the terminal (701) can transmit an RRC connection resume request (RRCResumeRequest) message or an RRC connection resume request 1 (RRCResumeRequest1) message to the base station (702). The RRC connection resume request message or the RRC connection resume request 1 message may include a terminal identifier (resumeIdentity) and an RRC connection resume reason (resumeCause), etc. When the base station receives the RRC connection resume request message or the RRC connection resume request 1 message, in step 750, the base station (702) can transmit an RRC connection resume message (RRCResume) to the terminal (701) (750). The RRC connection resumption message may contain an indicator (idleModeMeasurementReq) instructing the terminal to report if there are idle / inactive measurement results. When the terminal (701) receives the RRC connection resumption message from the base station (702), at step 751, the terminal (701) may stop the T331 timer if it is running, set the wireless resource configuration information, and switch to the RRC connection mode (RRC_CONNECTED). If the terminal (701) that has switched to the RRC connection mode has idle / inactive measurement information for cells excluding PCell in VarMeasIdleReport, it may perform the following operations and then, at step 755, send an RRC connection resumption complete (RRCResumeComplete) message to the base station (702).

[0280] - If the idleModeMeasurementReq is included in the RRCResume message received from the base station (702):

[0281] -- The terminal (701) can set the measResultIdleEUTRA in the RRCResumeComplete message to the value of measReportIdleEUTRA in the VarMeasIdleReport, if available

[0282] -- The terminal (701) can set the measResultIdleNR in the RRCResumeComplete message to the value of measReportIdleNR in the VarMeasIdleReport, if available

[0283] -- The terminal (701) can discard the VarMeasIdleReport upon successful delivery of the RRCResumeComplete message is confirmed by lower layers.

[0284] - Otherwise (else), i.e., if the RRC connection resumption message does not include idleModeMeasurementReq:

[0285] -- The terminal (701) can include an indicator (idleMeasAvailable) indicating that there is an idle / inactive measurement result in the RRC connection resumption completion message if the SIB1 contains idleModeMeasurementsNR and the terminal has NR idle / inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport, or if the IB1 contains idleModeMeasurementsEUTRA and the terminal has E-UTRA idle / inactive measurement information available in VarMeasIdleReport.

[0286] According to one embodiment of the present disclosure, when a terminal (701) and a base station (702) successfully perform an RRC connection reconfiguration procedure, the base station (702) may perform an RRC connection reconfiguration procedure with the terminal (701). If the RRC connection reconfiguration completion message includes idle / inactive measurement results, at step 760, the base station (702) may transmit an RRC Connection Reconfiguration message to the terminal (701) that includes Carrier Aggregation (CA) or Dual Connectivity (DC) settings based on the idle / inactive measurement results included in the RRC connection reconfiguration completion message. At step 765, the terminal (701) may apply the CA or DC settings within the RRC connection reconfiguration message received from the base station (702) and transmit an RRC Connection Reconfiguration Complete message to the base station (702).

[0287] According to one embodiment of the present disclosure, if the RRC connection reconfiguration completion message does not contain an idle / inactive measurement result, or if the RRC connection reconfiguration completion message does not contain an indicator indicating that there is an idle / inactive measurement result, then at step 760, the base station (702) may, if necessary, transmit an RRC connection reconfiguration message to the terminal. For example, at step 760, the base station (702) may transmit an RRC Connection Reconfiguration message to the terminal (701), for example, if it intends to modify the wireless bearer. At step 765, the terminal (701) may apply the settings within the RRC connection reconfiguration message received from the base station and transmit an RRC Connection Reconfiguration Complete message to the base station (702).

[0288] According to one embodiment of the present disclosure, a base station (702) may perform a terminal information (UE Information) procedure to retrieve idle / inactive measurement information from a terminal (701) if the RRC connection resumption completion message received from the terminal (701) includes an indicator indicating that there is an idle / inactive measurement result. The base station (702) may initiate this UE information procedure only after successful security activation. In step 770, the base station (702) may transmit a terminal information request message (UEInformationRequest) to the terminal (701), which includes an indicator (idleModeMeasurementReq) for the terminal (701) to report the idle / inactive measurement result.

[0289] According to one embodiment of the present disclosure, a terminal (701) that receives a UEInformationRequest containing idleModeMeasurementReq can perform the following procedure and, in step 775, transmit a terminal information response message (UEInformationResponse) containing at least one of measIdleResultEUTRA and measIdleResultNR to a base station (702).

[0290] - If the UE has stored a VarMeasIdleReport that contains measurement information concerning cells other than the PCell:

[0291] -- The terminal (701) can set the measResultIdleEUTRA in the UEInformationResponse message to the value of measReportIdleEUTRA in the VarMeasIdleReport, if available

[0292] The terminal (701) can, if available, set the measResultIdleNR in the UEInformation to the value of measReportIdleNR in the VarMeasIdleReport.

[0293] The terminal (701) can discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers.

[0294] According to one embodiment of the present disclosure, a base station (702) may perform an RRC connection reconfiguration procedure to set up Carrier Aggregation (CA) or Dual Connectivity (DC) for the terminal (701) based on idle / inactive measurement information recovered from the terminal (701). That is, at step 780, the base station (702) transmits an RRC connection reconfiguration message including a CA setting or a DC setting to the terminal (701), and the terminal (701) applies the CA setting or a DC setting included in the RRC connection reconfiguration message received from the base station (702), and then at step 785, transmits an RRC connection reconfiguration completion message to the base station (702).

[0295] FIG. 8 illustrates a flowchart of a procedure in which a terminal in an RRC idle mode (RRC_IDLE) and an RRC inactive mode (RRC_INACTIVE) according to one embodiment of the present disclosure performs a measurement for cell reselection, and a base station quickly establishes Carrier Aggregation or Dual Connectivity to the terminal based on the cell reselection measurement result recovered from the terminal.

[0296] According to one embodiment of the present disclosure, in step 805, the terminal (801) may be in an RRC connection mode (RRC_CONNECTED) state by establishing an RRC connection with the base station (802).

[0297] According to one embodiment of the present disclosure, in step 810, the base station (802) may transmit a terminal capability request message (UECapabilityEnquiry) to the terminal (801) to retrieve radio access capability information of the terminal (801).

[0298] According to one embodiment of the present disclosure, in step 815, the terminal (801) may transmit a terminal capability information message (UECapabilityInformation) to the base station (802). Step 815 may include at least one of the steps in which the aforementioned terminal transmits the terminal capability information message (UECapabilityInformation) to the base station. According to one embodiment of the present disclosure, the terminal capability information message may include the following terminal capability parameters.

[0299] -measValidationReportReselectionMeasurements-r18

[0300] -- The terminal capability parameter measValidationReportReselectionMeasurements-r18 may mean a terminal capability parameter indicating whether the terminal supports measurement validation based on reselection measurements during IDLE / INACTIVE state and reporting for fast CA / DC setup. The terminal (801) may set the capability parameter value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands, and all TDD-FR2-2 bands, respectively.

[0301] According to one embodiment of the present disclosure, in step 820, the base station (802) may transmit an RRC disconnection message (RRCRelease) to the terminal (801). The RRC disconnection message may contain a measurement setting (measIdleConfig) that the terminal stores and uses in RRC idle mode or RRC disabled mode. Through measIdleConfig, a MeasIdleConfigDedicated Information Element (hereinafter IE) may be set up or released, and the MeasIdleConfigDedicated IE may contain information according to the embodiment described above with reference to FIG. 6. Additionally, the MeasIdleConfigDedicated IE according to one embodiment of the present disclosure may include at least one of the following.

[0302] - measReselectionCarrierListNR-r18

[0303] -- measReselectionCarrierListNR-r18 may mean a list containing the NR carriers for reselection measurement reporting.

[0304] -measIdleValidityDuration-r18

[0305] -- measIdleValidityDuration-r18 may refer to a field containing time values ​​that determine the validity of reported idle / inactive measurements as defined in TS 38.133, in accordance with 3GPP technical specification 38.133. For example, the value s5 may mean 5 seconds, and s10 may mean 10 seconds.

[0306] -measReselectionValidityDuration-r18

[0307] -- measReselectionValidityDuration-r18 may indicate the time values ​​for UE to determine validity of reported reselection measurements as defined in TS 38.133, which indicate the validity of reselection measurements reported by the terminal in RRC idle mode or RRC disabled mode. For example, the value s5 may indicate 5 seconds, and s10 may indicate 10 seconds.

[0308] According to one embodiment of the present disclosure, if the RRC disconnection message includes measIdleConfig (if the RRCRelease includes the measIdleConfig), the terminal (801) may perform the following procedures in order.

[0309] - The terminal (801) can stop the T331 timer if the T331 timer is running. Additionally, the terminal (801) can release the terminal variable VarMeasIdleConfig.

[0310] - If the measIdleConfig is set to setup,

[0311] -- The terminal (801) can store the received measIdleDuration in VarMeasIdleConfig.

[0312] -- The terminal (801) can start the T331 timer with the value set to measIdleDuration.

[0313] -- The terminal (801) can store the received measIdleCarrierListNR in VarMeasIdleConfig if the measIdleConfig contains measIdleCarrierListNR.

[0314] -- The terminal (801) can store the received measIdleCarrierListEUTRA in VarMeasIdleConfig if the measIdleConfig contains measIdleCarrierListEUTRA.

[0315] -- If the measIdleConfig contains validityAreaList, store the received validityAreaList in VarMeasIdleConfig.

[0316] -- The terminal (801) can store the received measReselectionCarrierListNR in VarMeasReselectionConfig if the measIdleConfig contains measReselectionCarrierListNR.

[0317] - The terminal (801) can store the received measReselectionValidityDuration in VarMeasReselectionConfig if the measIdleConfig contains measReselectionValidityDuration.

[0318] -- The terminal (801) can store the received measIdleValidityDuration in VarEnhMeasIdleConfig if the measIdleConfig contains measIdleValidityDuration.

[0319] According to one embodiment of the present disclosure, in step 825, the terminal (801) may transition to an RRC idle mode or an RRC disabled mode and perform a cell selection process. The cell selection process of the terminal (801) in step 825 of FIG. 8 may include the cell selection process described above with reference to FIG. 5.

[0320] According to one embodiment of the present disclosure, at step 830, the terminal (801) can obtain system information related to idle / inactive measurements. The measIdleConfigSIB broadcast via SIB11 may include measIdleCarrierListNR and measIdleCarrierLisEUTRA according to the embodiment described above with reference to FIG. 6.

[0321] According to one embodiment of the present disclosure, measIdleConfigSIB may include at least one of the following.

[0322] - measReselectionCarrierListNR-r18

[0323] -measIdleValidityDuration-r18

[0324] -measReselectionValidityDuration-r18

[0325] -measIdleCarrierListNR-LessThan5MHz-r18

[0326] -- Indicates the NR carriers to be measured during RRC_IDLE or RRC_INACTIVE for the cell(s) supporting 12 PRB, 15 PRB, or 20 PRB transmission bandwidth configuration as defined in TS 38.101-1, TS 38.211 and TS 38.213 in accordance with 3GPP technical specifications 38.101-1, 38.211 and 38.213. The total number of MeasIdleCarrierNR included in measIdleCarrierListNR and measIdleCarrierListNR-LessThan5MHz does not exceed maxFreqIdle-r16

[0327] -measReselectionCarrierListNR-LessThan5MHz-r18

[0328] -- May mean a list containing the NR carriers for reselection measurement reporting for the cell(s) supporting 12 PRB (Physical Resource Block), 15 PRB, or 20 PRB transmission bandwidth configuration as defined in TS 38.101-1, TS 38.211, and TS 38.213, in accordance with 3GPP technical specifications 38.101-1, 38.211, and TS 38.213. The total number of MeasReselectionCarrierNR included in measReselectionCarrierListNR and measReselectionCarrierListNR-LessThan5MHz cannot exceed maxFreqIdle-r16.

[0329] According to one embodiment of the present disclosure, in step 835, the terminal (801) can update the cell reselection measurement configuration. That is, the terminal (801) can update the reselection measurement configuration when the SDT (small data transmission) procedure is not in progress and at least one of the following conditions is satisfied.

[0330] - When selecting a cell when switching from RRC_IDLE or RRC_INACIVE to RRC_CONNECTED or RRC_INACTIVE

[0331] - upon update of system information (SIB11), eg due to intra-RAT cell (re)selection

[0332] According to one embodiment of the present disclosure, a terminal (801) may update a cell reselection measurement setting when at least one of the above conditions is satisfied, provided that the terminal (801) supports cell reselection measurement reporting (e.g., the terminal supports measValidationReportReselectionMeasurements-r18). A terminal that does not support cell reselection measurement reporting cannot report cell reselection measurement results to a base station, and therefore may not manage the unnecessary terminal variable VarMeasReselectionConfig. A terminal that supports cell reselection measurement reporting may update the cell reselection measurement setting by performing the following procedures in sequence.

[0333] - If the terminal variable VarMeasReselectionConfig does not include measReselectionCarrierListNR received from the RRCRelease message:

[0334] -- If the terminal supports cell reselection measurement reporting (e.g., if the terminal supports measValidationReportReselectionMeasurements-r18):

[0335] --- If SIB11 includes the measIdleConfigSIB and contains measReselectionCarrierListNR

[0336] The terminal can store or replace the measReselectionCarrierListNR of measIdleConfigSIB of SIB11 within VarMeasReselectionConfig.

[0337] --- Otherwise (i.e., if measIdleConfigSIB does not exist in SIB11 or measReselectionCarrierListNR is not broadcast to measIdleConfigSIB)

[0338] The terminal can remove the measReselectionCarrierListNR in VarMeasReselectionConfig if it is stored.

[0339] - If the terminal variable VarMeasReselectionConfig does not include measReselectionValidityDuration received from the RRCR release message:

[0340] -- If the terminal supports cell reselection measurement reporting (e.g., if the terminal supports measValidationReportReselectionMeasurements-r18):

[0341] --- If SIB11 includes the measIdleConfigSIB and contains measReselectionValidityDuration

[0342] The terminal can store or replace the measReselectionValidityDuration of measIdleConfigSIB of SIB11 within VarMeasReselectionConfig.

[0343] --- Otherwise (i.e., if measIdleConfigSIB does not exist in SIB11 or measReselectionValidityDuration is not broadcast to measIdleConfigSIB)

[0344] The terminal can remove the measReselectionValidityDuration in VarMeasReselectionConfig if it is stored.

[0345] According to one embodiment of the present disclosure, in step 840, the RRC idle mode or RRC disabled mode terminal (801) may perform a cell reselection evaluation procedure. The cell reselection evaluation procedure may include the cell reselection evaluation procedure described above with reference to FIG. 5.

[0346] According to one embodiment of the present disclosure, in step 841, the terminal (801) may trigger Random Access to establish an RRC connection with the base station (802). When Random Access is triggered, in step 842, the terminal (801) may select a PRACH occasion and transmit a Random Access Preamble to the base station. When the base station (802) receives the Random Access Preamble from the terminal (802), in step 843, the base station (802) may transmit a Random Access Response (hereinafter RAR) message to the terminal (801) regarding the Random Access Preamble received from the terminal (802). The terminal (801) in RRC idle mode may establish reverse transmission synchronization with the base station (802) through steps 842 to 843.

[0347] According to one embodiment of the present disclosure, an RRC idle mode terminal (801) that has established reverse transmission synchronization can perform an RRC connection establishment procedure with a base station (802), and an RRC deactivation mode terminal (801) can perform an RRC connection resumption procedure with a base station (802). In step 845, the terminal (801) in the RRC idle mode state can transmit an RRC connection establishment request message (RRCSetupRequest) to the base station (802). The RRC connection establishment request message may include an identifier (ue-Identity) and an establishment cause, etc., for the terminal to establish an RRC connection. When the base station (802) receives the RRC connection establishment request message from the terminal (801), in step 850, the base station (802) can transmit an RRC connection establishment message (RRCSetup) to the terminal (801). When the terminal (801) receives an RRC setting message from the base station (802), in step 851, the terminal (801) can stop the T331 timer if it is running, set wireless resource setting information, and switch to RRC connection mode (851).

[0348] According to one embodiment of the present disclosure, a terminal (801) that has switched to an RRC connection mode may transmit an RRC connection setup completion message (855) to a base station (802) including an indicator (reselectionMeasAvailable) indicating that there is a reselection measurement result, when at least one of the following options is satisfied.

[0349] - Option 1: The terminal (801) may include reselectionMeasAvailable if there is an idle / inactive cell reselection measurement result, regardless of whether the cell reselection measurement result is valid.

[0350] -- For example, if the SIB1 contains reselectionMeasurementsNR

[0351] --- If measReselectionCarrierListNR exists in VarMeasReselectionConfig and there are NR cell reselection measurement results for at least one frequency in said measReselectionCarrierListNR,

[0352] --- If measReselectionCarrierListNR is not present in VarMeasReselectionConfig and if the UE has NR cell reselection measurements available, or

[0353] If the UE has NR reselection measurements available for any frequency listed in measReselectionCarrierListNR in VarMeasReselecionConfig

[0354] The terminal (801) can include reselectionMeasAvailable in the RRC connection setup completion message.

[0355] - Option 2: The terminal can determine whether to include reselectionMeasAvailable based on whether measReselectionValidityDuration is included in VarMeasReselectionConfig.

[0356] -- For example, if the SIB1 contains reselectionMeasurementsNR

[0357] --- If measReselectionValidityDuration is included in VarMeasReselectionConfig

[0358] ---- If measReselectionCarrierListNR exists in VarMeasReselectionConfig and there are valid NR cell reselection measurement results for at least one frequency in said measReselectionCarrierListNR (if measReselectionCarrierListNR is present in VarMeasReselectionConfig and the UE has valid NR reselection measurements available for any frequency listed in measReselectionCarrierListNR in VarMeasReselectionConfig), or

[0359] ---- If measReselectionCarrierListNR is not present in VarMeasReselectionConfig and the UE has valid NR cell reselection measurements available

[0360] ----- The terminal (801) can include reselectionMeasAvailable in the RRC connection setup completion message.

[0361] --- Otherwise (e.g., if VarMeasReselecionConfig does not include measReselectionValidityDuration)

[0362] The terminal (801) can include reselectionMeasAvailable in the RRC connection setup completion message according to option 1.

[0363] According to one embodiment of the present disclosure, the terminal (801) may determine that the measurement results (cell reselection) are valid if the following conditions are met for the validity check.

[0364] - The measurements are performed before msg1 transmission for RRC setup / resume within the last measReselectionValidityDuration-r18 seconds for carriers configured in measReselectionCarrierListNR-r18,

[0365] - When the measurement results satisfy the measurement accuracy requirement at the measurement instance

[0366] According to one embodiment of the present disclosure, if a timer for measReselectionValidityDuration-r18 is not configured, the terminal (801) is not required to perform a validity check, and the terminal (801) may report measurement results to the base station (802) if the measurement results satisfy the measurement accuracy requirement at the measurement instance.

[0367] According to one embodiment of the present disclosure, an RRC disabled mode terminal may transmit an RRC connection resumption request message (RRCResumeRequest) or an RRC connection resumption request 1 message (RRCResumeRequest1) to a base station (845). The RRC connection resumption request or RRC connection resumption request 1 message may include an identifier (resumeIdentity) and a reason (resumeCause) for the terminal to resume the RRC connection. When the base station (802) receives the RRC connection resumption request or RRC connection resumption request 1 message from the terminal (801), in step 850, the base station (802) may transmit an RRC connection setup message (RRCSetup) to the terminal (801). When the terminal (801) receives an RRC setting message from the base station (802), in step (851), the terminal (801) can stop the T331 timer if the T331 timer is running, set wireless resource setting information, and switch to RRC connection mode (851).

[0368] According to one embodiment of the present disclosure, a terminal (801) that has switched to an RRC connection mode may, in step (855), transmit an RRC connection setup completion message to a base station (801) including an indicator (reselectionMeasAvailable) indicating that there is a reselection measurement result, as described above.

[0369] According to one embodiment of the present disclosure, a base station (802) may perform an RRC connection reconfiguration procedure with a terminal (801). In step 860, the base station (802) may transmit an RRC connection reconfiguration to the terminal (801). In step 865, the terminal (801) that receives the RRC connection reconfiguration message may apply the received RRC connection reconfiguration to the base station (802) and transmit an RRC connection reconfiguration completion message (RRCConnectionReconfigurationComplete) to the base station (802) (865).

[0370] According to one embodiment of the present disclosure, a base station (802) may perform a UE Information procedure to retrieve reselection measurement information from a terminal (801). The base station may initiate this UE Information procedure only after successful security activation. In step 870, the base station (802) may transmit a UE Information Request message to the terminal (801) that includes a reselectionMeasurementReq instructing the terminal to report the reselection measurement results (870). Additionally, the base station (802) may transmit a UE Information Request message to the terminal (801) that includes a validatedMeasurementsReq instructing the terminal to report valid reselection measurement results. A terminal (801) that receives a UEInformationRequest containing reselectionMeasurementReq can perform the following procedure and, in step 875, transmit a terminal information response message (UEInformationResponse) containing measResultReselectionNR to a base station (802).

[0371] - If validatedMeasurementsReq is included in the UEInformationRequest and measReselectionValidityDuration is included in VarMeasReselectionConfig:

[0372] -- If measReselectionCarrierListNR is present in VarMeasReselectionConfig:

[0373] --- The terminal (801) can set the measResultReselectionNR in the UEInformationResponse message the valid NR measurement results, if available for any frequency listed in measReselectionCarrierListNR in VarMeasReselectionConfig and set validityStatus to the value of measReselectionValidityDuration in VarMeasReselectionConfig for each reported measurement.

[0374] -- Otherwise (e.g., if VarMeasReselectionConfig does not have measReselectionCarrierList)

[0375] If possible, set the measResultReselectionNR in the UEInformationResponse message to any valid NR measurement results (e.g., cell reselection measurement results), and set validityStatus to the value of measReselectionValidityDuration in VarMeasReselectionConfig.

[0376] - Otherwise (e.g., if validatedMeasurementReq is not included in UEInformationRequest or measReselectionValidityDuration is not included in VarMeasReselectionConfig)

[0377] -- If measReselectionCarrierListNR is present in VarMeasReselectionConfig

[0378] --- The terminal (801) can, if possible, set the measResultReselectionNR in the UEInformationResponse message the NR measurement results, if available for any frequency listed in measReselectionCarrierListNR in VarMeasReselectionConfig.

[0379] -- Otherwise (e.g., if VarMeasReselectionConfig does not have measReselectionCarrierListNR),

[0380] --- The terminal (801) can set the measResultReselectionNR in the UEInformationResponse message to any NR measurement results, if available.

[0381] According to one embodiment of the present disclosure, a base station (802) may perform an RRC connection reconfiguration procedure to set Carrier Aggregation (CA) or Dual Connectivity (DC) for a terminal based on reselection measurement information recovered from a terminal (801). That is, at step 880, the base station (802) may transmit an RRC connection reconfiguration message including CA or DC settings to the terminal (801). At step 885, the terminal (801) may apply the CA or DC settings within the RRC connection reconfiguration message and transmit an RRC connection reconfiguration completion message to the base station (802).

[0382] FIG. 9 illustrates a flowchart of a procedure in which a terminal in RRC idle mode (RRC_IDLE) and RRC inactive mode (RRC_INACTIVE) performs a measurement for cell reselection according to one embodiment of the present disclosure, and a base station quickly establishes Carrier Aggregation or Dual Connectivity to the terminal based on the cell reselection measurement result recovered from the terminal.

[0383] According to one embodiment of the present disclosure, in step 905, the terminal (901) may be in an RRC connection mode (RRC_CONNECTED) state by establishing an RRC connection with the base station (902).

[0384] According to one embodiment of the present disclosure, in step 910, the base station (902) may transmit a terminal capability request message (UECapabilityEnquiry) to the terminal (901) to retrieve radio access capability information of the terminal (901).

[0385] According to one embodiment of the present disclosure, in step 915, the terminal (901) may transmit a terminal capability information message (UECapabilityInformation) to the base station (902). Step 915 may include at least one of the steps of transmitting the aforementioned terminal capability information message (UECapabilityInformation).

[0386] According to one embodiment of the present disclosure, in step 920, the base station (902) may transmit an RRC disconnection message (RRCRelease) to the terminal (901). The RRC disconnection message may contain a measurement setting (measIdleConfig) that the terminal (901) stores and uses in RRC idle mode or RRC disabled mode. Through measIdleConfig, a MeasIdleConfigDedicated Information Element (hereinafter IE) may be set up or released, and the information included in the MeasIdleConfigDedicated IE may include at least one of the information included in the MeasIdleConfigDedicated IE described above in FIG. 6 and FIG. 8. If the RRC disconnection message includes measIdleConfig (if the RRCRelease includes the measIdleConfig), the terminal (901) may apply the measIdleConfig according to the embodiment described above with reference to FIG. 8.

[0387] According to one embodiment of the present disclosure, in step 925, the terminal (901) may transition to an RRC deactivation mode and perform a cell selection process. The cell selection process of the terminal (901) in step 925 may include the cell selection process described above with reference to FIG. 5.

[0388] According to one embodiment of the present disclosure, in step 930, the terminal (901) can obtain system information related to idle / inactive measurement. The operation of the terminal (901) obtaining system information related to idle / inactive measurement in step 930 may include the operation of obtaining system information related to idle / inactive measurement as described above with reference to FIG. 8.

[0389] According to one embodiment of the present disclosure, in step 935, the terminal (901) can update the reselection measurement settings. The operation of the terminal (901) updating the reselection measurement settings in step 935 may include the operation of updating the reselection measurement settings described above with reference to FIG. 8.

[0390] According to one embodiment of the present disclosure, at step 940, the terminal (901) in the RRC disabled mode may perform a cell reselection evaluation procedure. The cell reselection evaluation procedure of the terminal (901) at step 940 may include the cell reselection evaluation procedure described above with reference to FIG. 5.

[0391] According to one embodiment of the present disclosure, in step 941, the terminal (901) may trigger Random Access to establish an RRC connection with the base station (902). When Random Access is triggered, in step (942), the terminal (901) may select a PRACH occasion and transmit a Random Access Preamble to the base station (902). When the base station (902) receives the Random Access Preamble, in step 943, the base station (902) may transmit a Random Access Response (hereinafter RAR) message to the terminal (901) regarding the Random Access Preamble. The terminal (901) in RRC idle mode may establish reverse transmission synchronization with the base station (902) through steps 942 and 943.

[0392] According to one embodiment of the present disclosure, an RRC disabled mode terminal (901) that has established reverse transmission synchronization can perform an RRC connection resumption procedure with a base station (902). First, in step 945, the terminal (901) can transmit an RRC connection resumption request message (RRCResumeRequest) or an RRC connection resumption request 1 message (RRCResumeRequest1) to the base station (902). The RRC connection resumption request message or the RRC connection resumption request 1 message may include a terminal identifier (resumeIdentity) and an RRC connection resumption reason (resumeCause), etc. When the base station (902) receives the RRC connection resumption request message or the RRC connection resumption request 1 message, in step 950, the base station (902) can transmit an RRC connection resumption message (RRCResume) to the terminal (901). The RRC connection resumption message may contain a reselectionMeasurementReq, which instructs the terminal (901) to report the reselection measurement result through the RRC connection resumption completion message if the terminal (901) has one. The RRC connection resumption message may contain a validatedMeasurementsReq, which instructs the terminal (901) to report a valid reselection measurement result. When the terminal (901) receives the RRC connection resumption message, in step (951), the terminal (901) may apply the received RRC connection resumption message and switch to the RRC connection mode (951). After switching to the RRC connection mode, the terminal (901) may perform the following operations and then transmit the RRC connection resumption completion message (955) to the base station (902).

[0393] - If the reselectionMeasurementReq is included in the RRCResume message

[0394] -- If validatedMeasurementsReq is included in the RRCResume and measReselectionValidityDuration is included in the terminal variable VarMeasReselectionConfig,

[0395] --- If measReselectionCarrierListNR is present in VarMeasReselectionConfig:

[0396] If the terminal has valid cell reselection measurement results for any frequency listed in measReselectionCarrierListNR in VarMeasReselectionConfig (if the UE has valid cell reselection measurement results for any frequency listed in measReselectionCarrierListNR in VarMeasReselectionConfig)

[0397] ----- The terminal (901) can set the measResultReselectionNR in the RRCResumeComplete message to the valid NR measurement results, if available for any frequency listed in measReselectionCarrierListNR in VarMeasReselectionConfig and set validityStatus to the value of measReselectionValidityDuration in VarMeasReselectionConfig.

[0398] --- Otherwise (e.g., if measReselectionCarrierListNR does not exist in VarMeasReselectionConfig):

[0399] If the terminal has valid NR cell reselection measurement results,

[0400] ----- The terminal (901) can, if possible, set the measResultReselectionNR in the RRCResumeComplete message to any available valid NR measurement results, if available. And the terminal following the present disclosure can set the validityStatus to the measReselectionValidityDuration value in VarMeasReselectionConfig. This is to inform the base station of the criteria for whether the NR cell reselection measurement results are valid, even if measReselectionCarrierListNR does not exist in VarMeasReselectionConfig.

[0401] -- Otherwise (e.g., if validatedMeasurementsReq is not included in RRCResume or measReselectionValidityDuration is not included in the terminal variable VarMeasReselectionConfig),

[0402] --- If measReselectionCarrierListNR is present in VarMeasReselectionConfig:

[0403] If the terminal (901) has cell reselection measurement results for at least one frequency listed in measReselectionCarrierListNR in VarMeasReselectionConfig,

[0404] ----- The terminal (901) can set the measResultReselectionNR in the RRCResumeComplete message to the NR measurement results, if available for any frequency listed in measReselectionCarrierListNR in VarMeasReselectionConfig.

[0405] --- Otherwise (e.g., if measReselectionCarrierListNR does not exist in VarMeasReselectionConfig):

[0406] If the terminal (901) has NR cell reselection measurement results,

[0407] ----- The terminal (901) can set the measResultReselectionNR in the RRCResumeComplete message to any available NR measurement results, if available.

[0408] According to one embodiment of the present disclosure, if reselectionMeasurementReq is not received in the RRC connection resumption message, the terminal (901) may receive reselectionMeasAvailable in the RRCResumeComplete message according to the embodiment described above with reference to FIG. 8 (e.g., Option 1 and / or Option 2).

[0409] According to one embodiment of the present disclosure, the terminal (901) may determine that the measurement results are valid if the following conditions are met for the validity check (cell re-selection).

[0410] - The measurements are performed before msg1 transmission for RRC setup / resume within the last measReselectionValidityDuration-r18 seconds for carriers configured in measReselectionCarrierListNR-r18,

[0411] - When the measurement results satisfy the measurement accuracy requirement at the measurement instance

[0412] According to one embodiment of the present disclosure, if a timer of measReselectionValidityDuration-r18 is not configured, the terminal (901) is not required to perform a validity check, and if the measurement results satisfy the measurement accuracy requirement at the measurement instance, the terminal (901) may report the measurement results.

[0413] According to one embodiment of the present disclosure, a base station (902) may perform an RRC connection reconfiguration procedure with a terminal (901). When the base station (902) recovers cell reselection measurement information through an RRC connection resumption procedure, it may perform an RRC connection reconfiguration procedure to set Carrier Aggregation (CA) or Dual Connectivity (DC) for the terminal (901) based on this information. That is, at step 960, the base station (902) transmits an RRC connection reconfiguration message containing CA and DC settings to the terminal (960), and at step 965, the terminal (901) may apply this and transmit an RRC connection reconfiguration completion message to the base station (902) (965). The base station (902) may also perform an RRC connection reconfiguration procedure with the terminal even when there is no cell reselection measurement information recovered from the terminal (901).

[0414] According to one embodiment of the present disclosure, a base station (902) may perform a terminal information (UE Information) procedure to retrieve cell reselection measurement information from a terminal (901). For example, the base station (902) may initiate the terminal information procedure if the RRCResumeComplete message received from the terminal (901) contains a reselectionMeasAvailable indicator. The base station (902) may initiate this UE information procedure only after successful security activation. In step 970, the base station (902) may transmit a terminal information request message (UEInformationRequest) to the terminal (901), which includes a reselectionMeasurementReq indicator instructing the terminal (901) to report the results of the cell reselection measurement (970). Additionally, the base station (902) may transmit a terminal information request message to the terminal (901) that includes a validatedMeasurementsReq, which instructs the terminal to report valid reselection measurement results. Upon receiving a UEInformationRequest containing the reselectionMeasurementReq from the base station (902), the terminal (901) may, in step 975, perform the following procedure to transmit a terminal information response message (UEInformationResponse) containing the measResultReselectionNR to the base station (902).

[0415] - If validatedMeasurementsReq is included in the UEInformationRequest and measReselectionValidityDuration is included in VarMeasReselectionConfig,

[0416] -- If measReselectionCarrierListNR is present in VarMeasReselectionConfig:

[0417] --- The terminal (901) can set the measResultReselectionNR in the UEInformationResponse message the valid NR measurement results, if available for any frequency listed in measReselectionCarrierListNR in VarMeasReselectionConfig and set validityStatus to the value of measReselectionValidityDuration in VarMeasReselectionConfig for each reported measurement.

[0418] -- Otherwise (e.g., if VarMeasReselectionConfig does not have measReselectionCarrierList):

[0419] --- The terminal (901) can, if possible, set the measResultReselectionNR in the UEInformationResponse message to any valid NR measurement results, if available, and set validityStatus to the value of measReselectionValidityDuration in VarMeasReselectionConfig.

[0420] - Otherwise (e.g., if validatedMeasurementReq is not included in UEInformationRequest or measReselectionValidityDuration is not included in VarMeasReselectionConfig),

[0421] -- If measReselectionCarrierListNR is present in VarMeasReselectionConfig:

[0422] --- The terminal (901) can, if possible, set the measResultReselectionNR in the UEInformationResponse message the NR measurement results, if available for any frequency listed in measReselectionCarrierListNR in VarMeasReselectionConfig.

[0423] -- Otherwise (e.g., if VarMeasReselectionConfig does not have measReselectionCarrierListNR):

[0424] --- The terminal (901) can set the measResultReselectionNR in the UEInformationResponse message to any NR measurement results (e.g., reselection measurement results), if available.

[0425] According to one embodiment of the present disclosure, a base station (902) may perform an RRC connection reconfiguration procedure to set Carrier Aggregation (CA) or Dual Connectivity (DC) to a terminal based on reselection measurement information recovered from a terminal (901). That is, at step 980, the base station (901) may transmit (980) an RRC connection reconfiguration message including CA or DC settings to the terminal (901). At step 985, the terminal (901) may transmit an RRC connection reconfiguration completion message to the base station (902) by applying the CA settings or DC settings within the RRC connection reconfiguration message received from the base station (902).

[0426] FIG. 10 illustrates a flowchart of a procedure in which a terminal in an RRC idle mode (RRC_IDLE) and an RRC inactive mode (RRC_INACTIVE) performs idle / inactive measurements according to one embodiment of the present disclosure, and a base station quickly establishes Carrier Aggregation or Dual Connectivity to the terminal based on the idle / inactive measurement results recovered from the terminal.

[0427] According to one embodiment of the present disclosure, in step 1005, the terminal (1001) may be in an RRC connection mode (RRC_CONNECTED) state by establishing an RRC connection with the base station (1002).

[0428] According to one embodiment of the present disclosure, in step 1010, the base station (1002) may transmit a terminal capability request message (UECapabilityEnquiry) to the terminal (1001) to retrieve radio access capability information of the terminal (1001).

[0429] According to one embodiment of the present disclosure, in step 1015, the terminal (1001) may transmit a terminal capability information message (UECapabilityInformation) to the base station (1002). The parameters included in the terminal capability information message may include at least one of the parameters included in the aforementioned terminal capability information message.

[0430] According to one embodiment of the present disclosure, a terminal capability information message may include the following parameters.

[0431] - measValidationReportEMR-r18

[0432] -- measValidationReportEMR-r18 may refer to a terminal capability parameter indicating whether the terminal can review and report the validity of measurement results based on idle / inactive measurement settings during the RRC connection establishment / RRC connection resumption procedure for fast Carrier Aggregation / Double Connection setup (this may also be referred to as EMR (Early measurement reporting) measurement). The terminal may set the capability parameter value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands, and all TDD-FR2-2 bands, respectively. A terminal supporting a function to review the validity of measurement results and report them may indicate support for idleInactiveNR-MeasReport-r16 or idleInactiveEUTRA-MeasReport-r16.

[0433] According to one embodiment of the present disclosure, in step 1020, the base station (1002) may transmit an RRC disconnection message (RRCRelease) to the terminal (1001). The RRC disconnection message may contain a measurement setting (measIdleConfig) that the terminal stores and uses in an RRC idle mode or an RRC disabled mode according to at least one of the embodiments described above. Through measIdleConfig, a MeasIdleConfigDedicated Information Element (IE) may be set up or released, and the fields included in the MeasIdleConfigDedicated IE may be understood in correspondence with at least one of the embodiments regarding the MeasIdleConfigDedicated IE described above. If the RRC disconnection message includes measIdleConfig (if the RRCRelease includes the measIdleConfig), the terminal may perform the following procedures in order.

[0434] - The terminal (1001) can stop the T331 timer if T331 is running. Also, the terminal (1001) can release the terminal variable VarMeasIdleConfig.

[0435] - If the measIdleConfig is set to setup,

[0436] -- The terminal (1001) can store the received measIdleDuration in VarMeasIdleConfig.

[0437] -- The terminal (1001) can start the T331 timer with the value set to measIdleDuration.

[0438] -- The terminal (1001) can store the received measIdleCarrierListNR in VarMeasIdleConfig if the measIdleConfig contains measIdleCarrierListNR.

[0439] -- The terminal (1001) can store the received measIdleCarrierListEUTRA in VarMeasIdleConfig if the measIdleConfig contains measIdleCarrierListEUTRA.

[0440] -- The terminal (1001) can store the received validityAreaList in VarMeasIdleConfig if the measIdleConfig contains validityAreaList.

[0441] -- The terminal (1001) can store the received measReselectionCarrierListNR in VarMeasReselectionConfig if the measIdleConfig contains measReselectionCarrierListNR.

[0442] -- The terminal (1001) can store the received measReselectionValidityDuration in VarMeasReselectionConfig if the measIdleConfig contains measReselectionValidityDuration

[0443] -- The terminal (1001) can store the received measIdleValidityDuration in VarEnhMeasIdleConfig if the measIdleConfig contains measIdleValidityDuration.

[0444] According to one embodiment of the present disclosure, in step 1025, the terminal (1001) may transition to an RRC idle mode and perform a cell selection process. The cell selection process of the terminal (1001) in step 1025 may include the cell selection process described above with reference to FIG. 5.

[0445] According to one embodiment of the present disclosure, in step 1030, the terminal (1001) may obtain system information related to idle / inactive measurement. For example, interFreqCarrierList broadcast via SIB4 may include parameters to be used for NR idle / inactive measurement, and measIdleConfigSIB broadcast via SIB11 may include information related to idle / inactive measurement. Specifically, measIdleConfigSIB may include measIdleCarrierListNR and measIdleCarrierLisEUTRA described in step 1020.

[0446] According to one embodiment of the present disclosure, in step 1035, the terminal (1001) can update the idle / inactive measurement setting if the T331 timer is running and the SDT (small data transmission) procedure is not in progress and at least one of the following conditions is satisfied.

[0447] - When selecting a cell when switching from RRC_IDLE or RRC_INACIVE to RRC_CONNECTED or RRC_INACTIVE

[0448] - Upon update of system information (SIB4 or SIB11), for example, due to intra-RAT cell (re)selection

[0449] For example, specifically, the terminal (1001) can perform the following procedures in sequence when the T331 timer is running in RRC idle mode.

[0450] - If the terminal variable VarMeasIdleConfig does not include either a measIdleCarrierListEUTRA or a measIdleCarrierListNR received from the RRCRelease message

[0451] -- If the UE supports idleInactiveEUTRA-MeasReport,

[0452] --- If the SIB11 includes the measIdleConfigSIB and contains measIdleCarrierListEUTRA

[0453] The terminal (1001) can store or replace the measIdleCarrierListEUTRA of measIdleConfigSIB of SIB11 within VarMeasIdleConfig.

[0454] --- Otherwise (i.e., if measIdleConfigSIB does not exist in SIB11 or if measIdleCarrierListEUTRA is not broadcast to measIdleConfigSIB)

[0455] The terminal (1001) can remove the measIdleCarrierListEUTRA in VarMeasIdleConfig if the measIdleCarrierListEUTRA is stored in VarMeasIdleConfig.

[0456] -- If the UE supports idleInactiveNR-MeasReport,

[0457] --- If SIB11 includes measIdleConfigSIB and contains measIdleCarrierListNR

[0458] The terminal (1001) can store or replace the measIdleCarrierListNR of measIdleConfigSIB of SIB11 within VarMeasIdleConfig.

[0459] --- Otherwise (i.e., if measIdleConfigSIB does not exist in SIB11 or measIdleCarrrierListNR is not broadcast to measIdleConfigSIB)

[0460] The terminal (1001) can remove the measIdleCarrierListtNR in VarMeasIdleConfig if the measIdleCarrierListtNR is stored in VarMeasIdleConfig.

[0461] - If the terminal variable VarEnhMeasIdleConfig does not include measIdleValidityDuration received from the RRC disconnection message, for example, if measIdleValidityDuration is not set in the RRC disconnection message,

[0462] -- If the device supports measValidationReportEMR (note that the device may not check this)

[0463] --- If SIB11 includes the measIdleConfigSIB and contains measIdleValidityDuration

[0464] The terminal (1001) can store or replace the measIdleValidityDuration of measIdleConfigSIB of SIB11 within VarEnhMeasIdleConfig.

[0465] --- Otherwise (e.g., if measIdleConfigSIB does not exist in SIB11 or measIdleCarrrierListNR is not broadcast to measIdleConfigSIB),

[0466] If measIdleValidityDuration is stored in VarEnhMeasIdleConfig, you can remove the measIdleValidityDuration within VarEnhMeasIdleConfig.

[0467] - For each entry in the measIdleCarrierListNR within VarMeasIdleConfig that does not contain an ssb-MeasConfig received from the RRCRelease message, the terminal (1001) may change the SSB measurement setting to the setting included in SIB4 / SIB11 or disable it. The specific procedure associated with this may correspond to the procedure described above with reference to FIG. 6.

[0468] According to one embodiment of the present disclosure, the terminal (1001) can determine whether to store, replace, or delete measIdleValidityDuration in VarEnhMeasIdleConfig depending on whether measIdleCarrrierListEUTRA and measIdleCarrierListNR are set in RRCRelease. That is, the terminal (1001) can manage VarEnhMeasIdleConfig with the value of measIdleValidityDuration broadcast from SIB11 depending on whether the value of measIdleValidityDuration is set in RRCRelease. As a result, even if the base station (1002) does not set the idle / inactive measurement frequency within the RRC disconnection message, the terminal (1001) can manage (i.e., save, replace, or release) the measIdleValidityDuration in VarEnhMeasIdleConfig according to the SIB11 broadcast by the current camping / serving cell when the measIdleValidityDuration is not set through the RRC disconnection message.

[0469] According to one embodiment of the present disclosure, in step 1040, the terminal (1001) may perform an idle / inactive measurement. Step 1040 may correspond to at least one of the aforementioned idle / inactive measurement procedures.

[0470] According to one embodiment of the present disclosure, in step 1041, the terminal (1001) may trigger Random Access to establish an RRC connection with the base station (1002). When Random Access is triggered, in step 1042, the terminal (1001) may select a PRACH occasion and transmit a Random Access Preamble to the base station (1002). When the base station (1002) receives the Random Access Preamble, in step 1043, the base station (1002) may transmit a Random Access Response (RAR) message for the Random Access Preamble to the terminal (1001). A terminal (1001) in RRC idle mode can establish reverse transmission synchronization with a base station (1002) through steps 1042 and 1043.

[0471] According to one embodiment of the present disclosure, an RRC idle mode terminal (1001) that has established reverse transmission synchronization can perform an RRC connection establishment procedure with a base station (1002). First, in step 1045, the terminal (1001) can transmit an RRC connection establishment request message (RRCSetupRequest) to the base station (1002). The RRC connection establishment request message may include an identifier (ue-Identity) and an establishment cause, etc., for the terminal to establish an RRC connection. When the base station (1002) receives the RRC connection establishment request message, in step 1050, the base station (1002) can transmit an RRC connection establishment message (RRCSetup) to the terminal (1001). When the terminal (1001) receives an RRC connection setup message, in step 1051, the terminal (1001) can stop the T331 timer if it is running, set wireless resource setup information, and switch to RRC connection mode (1051). The terminal (1001) that has switched to RRC connection mode can, in step 1055, send an RRC connection setup completion message to the base station (1002) including an indicator (idleMeasAvailable) indicating that there is an idle / inactive measurement result, if any of the following conditions are satisfied.

[0472] - If the SIB1 contains idleModeMeasurementsNR and the UE has NR idle / inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport

[0473] - If the SIB1 contains idleModeMeasurementsEUTRA and the UE has E-UTRA idle / inactive measurement information available in VarMeasIdleReport

[0474] According to one embodiment of the present disclosure, when the RRC connection establishment procedure is successfully performed, the base station (1002) may perform an RRC connection reconfiguration procedure with the terminal (1001). In step 1060, the base station (1002) may transmit the RRC connection reconfiguration to the terminal (1001). In step 1065, the terminal (1001) that receives the RRC connection reconfiguration message may apply the RRC connection reconfiguration and transmit an RRC connection reconfiguration completion message to the base station (1002).

[0475] According to one embodiment of the present disclosure, a base station (1002) may perform a terminal information (UE Information) procedure to retrieve idle / inactive measurement information from a terminal (1001). The base station (1002) may initiate this UE information procedure only after successful security activation. In step 1070, the base station (1002) may transmit a terminal information request message (UEInformationRequest) to the terminal (1001), which includes an indicator (idleModeMeasurementReq) to report the idle / inactive measurement results of the terminal (1001). Additionally, according to one embodiment of the present disclosure, the base station (1002) may transmit a UEInformationRequest message to the terminal (1001), which includes an indicator (validatedMeasurementsReq) to report valid idle / inactive measurement results in the UEInformationRequest message. validatedMeasurementsReq can be applied to both idle / inactive measurement results and cell reselection measurement results.

[0476] According to one embodiment of the present disclosure, if the terminal (1001) receives a UEInformationRequest containing idleModeMeasurementReq and stores a VarMeasIdleReport containing measurement information for cells other than the PCell (if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored a VarMeasIdleReport that has contained measurement information concerning cells other than the PCell), in step 1075, the terminal may transmit a terminal information response message (UEInformationResponse) containing at least one of measIdleResultEUTRA or measIdleResultNR to a base station (1002).

[0477] - If validatedMeasurementsReq is included in UEInformationRequest and the terminal variable VarEnhMeasIdleConfig includes measIdleValidityDuration

[0478] -- The terminal (1001) can, if possible, set the measResultIdleEUTRA in the UEInformationResponse message to the value of measReportIdleEUTRA in the VarMeasIdleReport for any valid measurement results, if available, and set validityStatus to the value of measIdleValidityDuration in VarEnhMeasIdleConfig for each reported measurement.

[0479] -- The terminal (1001) can, if possible, set the measIdleResultNR in the UEInformation to the value of measReportIdleNR in the VarMeasIdleReport for any valid measurement results, if available, and set validityStatus to the value of measIdleValidityDuration in VarEnhMeasIdleConfig for each reported measurement.

[0480] -- The terminal (1001) may discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers. The terminal may discard VarEnhMeasIdleConfig. Alternatively, the terminal may discard VarEnhMeasIdleConfig if supported by instructions from the base station (SIB or UEInformationRequest or a specific dedicated RRC message).

[0481] - If not,

[0482] -- The terminal (1001) can, if possible, set the measResultIdleEUTRA in UEInformationResponse to the value of measReportIdleEUTRA in VarMeasIdleReport.

[0483] -- The terminal (1001) can, if possible, set the measIdleResultNR in UEInformation to the measReportIdleNR value in VarMeasIdleReport.

[0484] -- The terminal (1001) may delete VarMeasIdleReport when it is confirmed that the UEInformationResponse message has been successfully transmitted from the lower layers. The terminal may delete VarEnhMeasIdleConfig. Alternatively, the terminal (1001) may delete VarEnhMeasIdleConfig if supported by the instructions of the base station (SIB or UEInformationRequest or a specific dedicated RRC message). Of course, the terminal (1001) may not delete VarEnhMeasIdleConfig if it does not report a valid result value.

[0485] According to one embodiment of the present disclosure, a base station (1002) may perform an RRC connection reconfiguration procedure to set Carrier Aggregation (CA) or Dual Connectivity (DC) for the terminal (1001) based on idle / inactive measurement information recovered from the terminal (1001). That is, in step 1080, the base station (1002) may transmit (1080) an RRC connection reconfiguration message including a CA setting or a DC setting to the terminal (1001). In step 1085, the terminal (1001) may transmit (1085) an RRC connection reconfiguration completion message to the base station (1002) by applying the CA setting or a DC setting within the RRC connection reconfiguration message received from the base station (1002).

[0486] FIG. 11 illustrates a flowchart of a procedure in which a terminal in an RRC idle mode (RRC_IDLE) and an RRC inactive mode (RRC_INACTIVE) according to one embodiment of the present disclosure performs idle / inactive measurements, and a base station quickly establishes Carrier Aggregation or Dual Connectivity to the terminal based on the idle / inactive measurement results recovered from the terminal.

[0487] According to one embodiment of the present disclosure, in step 1105, the terminal (1101) may be in an RRC connection mode (RRC_CONNECTED) state by establishing an RRC connection with the base station (1102).

[0488] According to one embodiment of the present disclosure, in step 1110, the base station (1102) may transmit a terminal capability request message (UECapabilityEnquiry) to the terminal (1001) to retrieve radio access capability information of the terminal (1101).

[0489] According to one embodiment of the present disclosure, in step 1115, the terminal (1101) may transmit a terminal capability information message (UECapabilityInformation) to the base station (1102). The parameters included in the terminal capability information message may include at least one of the parameters included in the aforementioned terminal capability information message.

[0490] According to one embodiment of the present disclosure, in step 1120, the base station (1102) may transmit an RRC disconnection message (RRCRelease) to the terminal (1101). The RRC disconnection message may contain a measurement setting (measIdleConfig) that the terminal stores and uses in RRC idle mode or RRC disabled mode according to at least one of the aforementioned embodiments. Fields that can be set through measIdleConfig may be understood in correspondence with at least one of the embodiments regarding fields that can be set through measIdleConfig described above. If the RRC disconnection message includes measIdleConfig (if the RRCRelease includes the measIdleConfig), the terminal (1101) may perform the following procedures in order.

[0491] - The terminal (1101) can stop the T331 timer if T331 is running. And the terminal variable VarMeasIdleConfig can be released.

[0492] - The terminal (1101) is set to setup when measIdleConfig is set to setup,

[0493] -- The terminal (1101) can store the received measIdleDuration in VarMeasIdleConfig.

[0494] -- The terminal (1101) can start the T331 timer with the value set to measIdleDuration.

[0495] -- The terminal (1101) can store the received measIdleCarrierListNR in VarMeasIdleConfig if the measIdleConfig contains measIdleCarrierListNR.

[0496] -- The terminal (1101) can store the received measIdleCarrierListEUTRA in VarMeasIdleConfig if the measIdleConfig contains measIdleCarrierListEUTRA.

[0497] -- The terminal (1101) can store the received validityAreaList in VarMeasIdleConfig if the measIdleConfig contains validityAreaList.

[0498] -- The terminal (1101) can store the received measReselectionCarrierListNR in VarMeasReselectionConfig if the measIdleConfig contains measReselectionCarrierListNR.

[0499] -- The terminal (1101) can store the received measReselectionValidityDuration in VarMeasReselectionConfig if the measIdleConfig contains measReselectionValidityDuration.

[0500] -- The terminal (1101) can store the received measIdleValidityDuration in VarEnhMeasIdleConfig if the measIdleConfig contains measIdleValidityDuration.

[0501] According to one embodiment of the present disclosure, in step 1125, the terminal (1101) may transition to an RRC idle mode and perform a cell selection process. The cell selection process of the terminal (1101) in step 1125 may include the cell selection process described above with reference to FIG. 5.

[0502] According to one embodiment of the present disclosure, at step 1130, the terminal (1101) may obtain system information related to idle / inactive measurement. For example, interFreqCarrierList broadcast via SIB4 may include parameters to be used for NR idle / inactive measurement, and measIdleConfigSIB broadcast via SIB11 may include information related to idle / inactive measurement. Specifically, measIdleConfigSIB may include the measIdleCarrierListNR and measIdleCarrierLisEUTRA described above in step 1120.

[0503] According to one embodiment of the present disclosure, in step 1135, the terminal (1101) can update the idle / inactive measurement setting if the T331 timer is running and the SDT (small data transmission) procedure is not in progress and at least one of the following conditions is satisfied.

[0504] - When selecting a cell when switching from RRC_IDLE or RRC_INACIVE to RRC_CONNECTED or RRC_INACTIVE

[0505] - Upon update of system information (SIB4 or SIB11), for example due to intra-RAT cell (re)selection

[0506] For example, specifically, the terminal (1101) can perform the following procedures in sequence when the T331 timer is running in RRC disabled mode.

[0507] - If the terminal variable VarMeasIdleConfig does not include both a measIdleCarrierListEUTRA and a measIdleCarrierListNR received from the RRC disconnection message,

[0508] -- If the UE supports idleInactiveEUTRA-MeasReport,

[0509] --- If the SIB11 includes the measIdleConfigSIB and contains measIdleCarrierListEUTRA

[0510] The terminal (1101) can store or replace the measIdleCarrierListEUTRA of measIdleConfigSIB of SIB11 within VarMeasIdleConfig.

[0511] --- Otherwise (i.e., if measIdleConfigSIB does not exist in SIB11 or if measIdleCarrierListEUTRA is not broadcast to measIdleConfigSIB)

[0512] The terminal (1101) can remove the measIdleCarrierListEUTRA in VarMeasIdleConfig if the measIdleCarrierListEUTRA is stored in VarMeasIdleConfig.

[0513] -- If the UE supports idleInactiveNR-MeasReport,

[0514] --- If SIB11 includes measIdleConfigSIB and contains measIdleCarrierListNR

[0515] The terminal (1101) can store or replace the measIdleCarrierListNR of measIdleConfigSIB of SIB11 within VarMeasIdleConfig.

[0516] --- Otherwise (i.e., if measIdleConfigSIB does not exist in SIB11 or measIdleCarrrierListNR is not broadcast to measIdleConfigSIB)

[0517] The terminal (1101) can remove the measIdleCarrierListNR in VarMeasIdleConfig if the measIdleCarrierListNR is stored in VarMeasIdleConfig.

[0518] - If the terminal variable VarEnhMeasIdleConfig does not include measIdleValidityDuration received from the RRC disconnection message (if VarEnhMeasIdleConfig does not include measIdleValidityDuration received from the RRCR release message), for example, if measIdleValidityDuration is not set in the RRC disconnection message

[0519] -- If the device supports measValidationReportEMR (note that the device may not check this)

[0520] --- If SIB11 includes the measIdleConfigSIB and contains measIdleValidityDuration,

[0521] ---- Store or replace the measIdleValidityDuration of measIdleConfigSIB of SIB11 within VarEnhMeasIdleConfig

[0522] --- Otherwise (e.g., if measIdleConfigSIB does not exist in SIB11 or if measIdleCarrrierListNR is not broadcast to measIdleConfigSIB)

[0523] If measIdleValidityDuration is stored in VarEnhMeasIdleConfig, you can remove the measIdleValidityDuration within VarEnhMeasIdleConfig.

[0524] - For each entry in the measIdleCarrierListNR within VarMeasIdleConfig that does not contain an ssb-MeasConfig received from the RRCRelease message, the SSB measurement setting may be changed to that in SIB4 / SIB11 or disabled. The specific procedure may follow the aforementioned embodiment (1f).

[0525] According to one embodiment of the present disclosure, the terminal (1101) may store, replace, or not delete measIdleValidityDuration in VarEnhMeasIdleConfig depending on whether measIdleCarrrierListEUTRA and measIdleCarrierListNR are set in RRCRelease. That is, depending on whether the value of measIdleValidityDuration is set in RRCRelease, VarEnhMeasIdleConfig can be managed with the value of measIdleValidityDuration broadcast in SIB11. As a result, even if the base station (1102) does not set the idle / inactive measurement frequency in the RRC disconnection message, the terminal may manage (i.e. store, replace, or delete) measIdleValidityDuration in VarEnhMeasIdleConfig according to SIB11 broadcast by the current camping / serving cell when measIdleValidityDuration is not set through the RRC disconnection message.

[0526] According to one embodiment of the present disclosure, in step 1140, the terminal (1101) may perform an idle / inactive measurement. Step 1140 may correspond to at least one of the aforementioned idle / inactive measurement procedures.

[0527] According to one embodiment of the present disclosure, at step 1141, the terminal (1101) may trigger Random Access to resume an RRC connection with the base station (1102). When Random Access is triggered, the terminal (1101) may select a PRACH occasion and transmit a Random Access Preamble to the base station (1102) (1142). When the base station (1102) receives the Random Access Preamble, at step 1143, the base station (1102) may transmit a Random Access Response (RAR) message for the Random Access Preamble to the terminal (1101) (1143). A terminal (1101) in RRC idle mode can establish reverse transmission synchronization with a base station (1102) through steps 1142 and 1143.

[0528] According to one embodiment of the present disclosure, an RRC idle mode terminal (1101) that has established reverse transmission synchronization can perform an RRC connection resume procedure with a base station (1102). First, in step 1145, the terminal (1101) can transmit an RRC connection resume request message (RRCResumeRequest) or an RRC connection resume request 1 message (RRCResumeRequest1) to the base station (1102). The RRC connection resume request message may include an identifier (resumeIdentity) and a reason (resumeCause) for the terminal to resume the RRC connection. When the base station (1102) receives the RRC connection resume request message or the RRC connection resume request 1 message, in step 1150, the base station (1102) can transmit an RRC connection resume message (RRCResume) to the terminal (1101). When the terminal (1101) receives an RRC connection setup message (RRCSetup), the terminal (1101) can perform the operation described above with reference to FIG. 10 when the terminal receives the RRC connection setup message. When the terminal (1101) receives an RRC connection resumption message, at step 1151, the terminal (1101) can stop the T331 timer if it is running, set wireless resource setup information, and switch to RRC connection mode. When the terminal (1101) has switched to RRC connection mode, if there is idle / inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport (if the UE has idle / inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport), the terminal can perform the following procedure and, at step 1155, send an RRC connection resumption completion (RRCResumeComplete) message to the base station (1102).

[0529] - If the RRCResume message includes idleModeMeasurementReq,

[0530] -- If validatedMeasurementsReq is included in RRCResume and the terminal variable VarEnhMeasIdleConfig includes measIdleValidityDuration

[0531] --- The terminal (1101) may, if possible, set the measResultIdleEUTRA in the RRCResumeComplete message to the value of measReportIdleEUTRA in the VarMeasIdleReport for any valid measurement results, if available, and set validityStatus to the value of measIdleValidityDuration in VarEnhMeasIdleConfig (for each reported measurement)

[0532] --- The terminal (1101) can, if possible, set the measResultIdleNR in the RRCResumeComplete message to the value of measReportIdleNR in the VarMeasIdleReport for any valid measurement results, if available, and set validityStatus to the value of measIdleValidityDuration in VarEnhMeasIdleConfig (for each reported measurement)

[0533] --- The terminal (1101) may discard the VarMeasIdleReport upon successful delivery of the RRCResumeComplete message confirmed by lower layers. The terminal may discard VarEnhMeasIdleConfig. Alternatively, the terminal may discard VarEnhMeasIdleConfig if supported by instructions from the base station (SIB, RRCResumeComplete, or a specific dedicated RRC message).

[0534] -- else

[0535] --- The terminal (1101) can, if possible, set the measResultIdleEUTRA in RRCResumeComplete to the value of measReportIdleEUTRA in VarMeasIdleReport.

[0536] --- The terminal (1101) can, if possible, set the measResultIdleNR in RRCResumeComplete to the value of measReportIdleNR in VarMeasIdleReport.

[0537] --- The terminal (1101) may delete VarMeasIdleReport when it is confirmed that the RRCResumeComplete message has been successfully transmitted from the lower layers. The terminal may delete VarEnhMeasIdleConfig. Alternatively, VarEnhMeasIdleConfig may be deleted if supported by the terminal according to instructions from the base station (SIB or RRCResumeComplete or a specific dedicated RRC message). Of course, VarEnhMeasIdleConfig may not be deleted if a valid result value is not reported.

[0538] - Otherwise (e.g., if the RRCResume message does not include idleModeMeasurementReq),

[0539] -- If the SIB1 contains idleModeMeasurementsNR and the UE has NR idle / inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport

[0540] -- If the SIB1 contains idleModeMeasurementsEUTRA and the UE has E-UTRA idle / inactive measurement information available in VarMeasIdleReport

[0541] The terminal may include an indicator (idleMeasAvailable) in the RRC connection resumption message to show that there is an idle / inactive measurement result.

[0542] According to one embodiment of the present disclosure, if the RRC connection resumption procedure is successfully performed, the base station (1102) may perform an RRC connection reconfiguration procedure with the terminal (1101). If the base station (1102) has recovered idle / inactive measurement information through the RRC connection resumption procedure, the base station (1102) may perform an RRC connection reconfiguration procedure to set up Carrier Aggregation (CA) or Dual Connectivity (DC) for the terminal (1101) based thereon. That is, in step 1160, the base station (1102) may transmit an RRC connection reconfiguration message including CA setting or DC setting to the terminal (1101). Additionally, in step 1165, the terminal (1101) may apply the CA setting or DC setting within the RRC connection reconfiguration message and transmit an RRC connection reconfiguration complete (RRCConnectionReconfigurationComplete) message (1165) to the base station (1102). The base station (1102) may also perform the RRC connection reconfiguration procedure with the terminal (1101) even if there is no idle / inactive measurement information recovered from the terminal (1101).

[0543] According to one embodiment of the present disclosure, a base station (1102) may perform a terminal information (UE Information) procedure to retrieve idle / inactive measurement information from a terminal (1101). The base station (1102) may initiate this UE information procedure only after successful security activation. In step 1170, the base station (1102) may transmit a terminal information request message (UEInformationRequest) to the terminal (1101), which includes an indicator (idleModeMeasurementReq) to report the idle / inactive measurement results of the terminal. The information included in the UEInformationRequest may correspond to at least one of the information included in the above-described UEInformationRequest. In step 1175, the terminal (1101) that receives the UEInformationRequest may transmit a UEInformationResponse to the base station (1102) in accordance with at least one of the above-described embodiments.

[0544] According to one embodiment of the present disclosure, a base station (1102) may perform an RRC connection reconfiguration procedure to set up Carrier Aggregation (CA) or Dual Connectivity (DC) for a terminal (1101) based on idle / inactive measurement information recovered from a terminal (1101). That is, at step 1180, the base station (1102) may transmit an RRC connection reconfiguration message (1180) including a CA setting or a DC setting to the terminal (1101). At step 1185, the terminal (1101) may transmit an RRC connection reconfiguration completion (RRCConnectionReconfiguration) message to the base station (1102) by applying the CA setting or a DC setting within the RRC connection reconfiguration message.

[0545] FIG. 12 illustrates a flowchart of a procedure in which a terminal according to one embodiment of the present disclosure manages measIdleValidityDuration stored in the variable VarEnhMeasIdleConfig.

[0546] Referring to FIG. 12, a terminal according to one embodiment of the present disclosure can manage VarEnhMeasIdleConfig by supporting measValidationReportEMR-r18.

[0547] According to one embodiment of the present disclosure, in step 1210, the terminal may store or replace the received measIdleValidityDuration in VarEnhMeasIdleConfig. The content of the terminal receiving the measIdleValidityDuration and storing or replacing it may correspond to at least one of the aforementioned embodiments.

[0548] According to one embodiment of the present disclosure, in step 1220, the terminal may release the measIdleValidityDuration stored in VarEnhMeasIdleConfig or delete VarEnhMeasIdleConfig if at least one of the following conditions is satisfied.

[0549] - Condition 1: If the selected or re-selected cell is outside the validityAreaList, specifically

[0550] -- If intra-RAT cell selection or reselection occurs while T331 is running (Note: intra-RAT may refer to NR)

[0551] --- If validityAreaList is set in VarMeasIdleConfig (if intra-RAT cell selection or reselection occurs while T331 is running)

[0552] ---- If the serving frequency does not match with the carrierFreq of an entry in the validityAreaList, or

[0553] If the serving frequency matches with the carrierFreq of an entry in the validityAreaList, the validityCellList is included in that entry, and the physical cell identity of the current serving cell does not match with any entry in validityCellList.

[0554] - Condition 2: When inter-RAT cell selection or reselection occurs (i.e., when cell selection or reselection occurs for a RAT other than NR)

[0555] - Condition 3: When valid idle / inactive measurement results are transmitted to the base station, for example, when valid idle / inactive measurement results are successfully transmitted to the base station via RRCResumeComplete (or UEInformationResponse) upon receiving RRCResume (or validatedMeasurementsReq via UEInformationRequest).

[0556] - Condition 4: When an RRC connected mode terminal, in which measIdleValidityDuration is stored in VarEnhMeasIdleConfig, receives an RRC release message from the base station that does not include the measIdleValidityDuration value (or if measIdleConfig is not set up or measIdleConfig is not included) and switches to RRC idle mode (or RRC disabled mode).

[0557] - Condition 5: When an RRC connection disabled mode terminal, in which measIdleValidityDuration is stored in VarEnhMeasIdleConfig, receives an RRC release message from the base station that does not include the measIdleValidityDuration value (or if measIdleConfig is not set up or measIdleConfig is not included) and switches to RRC idle mode (or RRC disabled mode).

[0558] - Condition 6: When the base station instructs the terminal via a separate directive to release the measIdleValidityDuration stored in VarEnhMeasIdleConfig or to delete VarEnhMeasIdleConfig

[0559] - Condition 7: When stopping a running T331 timer, if the measIdleValidityDuration value is not broadcast from the SIB11 of the current serving / camping cell

[0560] - Condition 8: When performing PLMN (Public Land Mobile Network) selection or SNPN (Standalone Non-Public Network) selection by NAS (Non-Access Stratum) request

[0561] - Condition 9: Upon power off or upon deregistration

[0562] According to one embodiment of the present disclosure, when at least one of the above-described conditions is satisfied, the terminal may stop the running T331 timer and release the measIdleValidityDuration stored in VarEnhMeasIdleConfig or delete VarEnhMeasIdleConfig. This is because, due to the feature of managing VarEnhMeasIdleConfig only when the T331 timer is running, when the terminal stops the running T331 timer under a predetermined condition, the terminal no longer has a reason to manage VarMeasIdleConfig, and also allows the base station to subsequently set the measIdleValidityDuration anew for the terminal. Alternatively, if measIdleValidityDuration is set for the terminal via an RRC disconnection message, the purpose is to enable the terminal to manage the measIdleValidityDuration value anew through VarEnhMeasIdleConfig by releasing the measIdleValidityDuration stored in VarMeasIdleConfig or deleting VarEnhMeasIdleConfig according to certain conditions, since the measIdleValidityDuration set for the terminal can only be released later via an RRC disconnection message.

[0563] FIG. 13 illustrates a flowchart of a procedure in which a terminal according to one embodiment of the present disclosure manages measReselectionValidityDuration stored in the variable VarMeasReselectionConfig.

[0564] Referring to Fig. 13, the terminal can manage VarMeasReselectionConfig by supporting measValidationReportReselectionMeasurements-r18.

[0565] According to one embodiment of the present disclosure, in step 1310, the terminal may store or replace the received measReselectionValidityDuration in VarMeasReselectionConfig. The details of the terminal receiving the measReselectionValidityDuration and storing or replacing the received measReselectionValidityDuration may follow at least one of the aforementioned embodiments.

[0566] According to one embodiment of the present disclosure, in step 1320, the terminal may release the measReselectionValidityDuration stored in VarMeasReselectionConfig or delete VarMeasReselectionConfig if at least one of the following conditions is satisfied.

[0567] - Condition 1: When valid idle / inactive cell reselection measurement results are transmitted to the base station, for example, when valid idle / inactive cell reselection measurement results are successfully transmitted to the base station via RRCResumeComplete (or UEInformationResponse) upon receiving RRCResume (or validatedMeasurementsReq via UEInformationRequest).

[0568] - Condition 2: When an RRC connected mode terminal, in which measReselectionValidityDuration is stored in VarMeasReselectionConfig, receives an RRC release message from the base station that does not include the measReselectionValidityDuration value (this includes cases where measIdleConfig is missing) and switches to RRC idle mode (or RRC disabled mode).

[0569] - Condition 3: When an RRC disabled mode terminal, in which measReselectionValidityDuration is stored in VarMeasReselectionConfig, receives an RRC release message from the base station that does not include the measReselectionValidityDuration value (this includes cases where measIdleConfig is missing) and switches to RRC idle mode (or RRC disabled mode).

[0570] - Condition 4: When the base station instructs the terminal via a separate directive to disable measReselectionValidityDuration stored in VarMeasReselectionConfig or to delete VarMeasReselectionConfig

[0571] - Condition 5: When transitioning to RRC connection mode, if the measIdleValidityDuration value from the current PCell is not broadcast from SIB11

[0572] - Condition 6: When performing PLMN (Public Land Mobile Network) selection or SNPN (Standalone Non-Public Network) selection by NAS (Non-Access Stratum) request

[0573] - Condition 7: Upon power off or upon deregistration

[0574] According to one embodiment of the present disclosure, when at least one of the above-described conditions is satisfied, the terminal may release measReselectionValidityDuration stored in VarrMeasReselectionConfig or delete VarrMeasReselectionConfig. If the base station has set measReselectionValidityDuration to the terminal via an RRC disconnection message, the terminal may later release the measReselectionValidityDuration value via a separate RRC disconnection message. Accordingly, by causing the terminal to release measReselectionValidityDuration stored in VarrMeasReselectionConfig or delete VarrMeasReselectionConfig when a predetermined condition is satisfied, the base station may later set measReselectionValidityDuration to the terminal anew.

[0575] FIG. 14 illustrates the functional structure of a terminal according to one embodiment of the present disclosure.

[0576] Referring to FIG. 14, a terminal according to one embodiment of the present disclosure may include an RF (Radio Frequency) processing unit (1410), a baseband processing unit (1420), a storage unit (1430), and a control unit (1440).

[0577] An RF processing unit (1410) according to one embodiment of the present disclosure can perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1410) can up-convert a baseband signal provided by a baseband processing unit (1420) into an RF band signal and transmit it through an antenna, and down-convert an RF band signal received through an antenna into a baseband signal. For example, the RF processing unit (1410) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. Although only one antenna is shown in FIG. 14, the terminal may be equipped with multiple antennas. Additionally, the RF processing unit (1410) may include multiple RF chains. Furthermore, the RF processing unit (1410) may perform beamforming. For beamforming, the RF processing unit (1410) can adjust the phase and magnitude of each of the signals transmitted and received through multiple antennas or antenna elements. Additionally, the RF processing unit can perform MIMO and can receive multiple layers when performing MIMO operation.

[0578] A baseband processing unit (1420) according to one embodiment of the present disclosure can perform a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (1420) can generate complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (1420) can restore the received bit sequence by demodulating and decoding the baseband signal provided by the RF processing unit (1410). For example, in the case of following the orthogonal frequency division multiplexing (OFDM) method, when transmitting data, the baseband processing unit (1420) can generate complex symbols by encoding and modulating the transmitted bit sequence, map the complex symbols to subcarriers, and then construct OFDM symbols through inverse fast Fourier transform (IFFT) operations and cyclic prefix (CP) insertion. Additionally, upon receiving data, the baseband processing unit (1420) can divide the baseband signal provided by the RF processing unit (1410) into OFDM symbol units, restore the signals mapped to subcarriers through a fast Fourier transform (FFT), and then restore the received bit sequence through demodulation and decoding.

[0579] According to one embodiment of the present disclosure, the baseband processing unit (1420) and the RF processing unit (1410) can transmit and receive signals as described above. Accordingly, the baseband processing unit (1420) and the RF processing unit (1410) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, or a communication unit. Furthermore, at least one of the baseband processing unit (1420) and the RF processing unit (1410) may include a plurality of communication modules to support a plurality of different wireless access technologies. Additionally, at least one of the baseband processing unit (1420) and the RF processing unit (1410) may include different communication modules to process signals of different frequency bands. For example, different wireless access technologies may include wireless LAN (e.g., IEEE 802.11), cellular network (e.g., LTE), etc. In addition, different frequency bands may include super high frequency (SHF) bands (e.g., 2 NRHz, NRHz) and millimeter wave (e.g., 60 GHz) bands.

[0580] According to one embodiment of the present disclosure, the storage unit (1430) can store data such as a basic program, an application program, and setting information for the operation of the terminal. In particular, the storage unit (1430) can store information related to a second connection node that performs wireless communication using a second wireless connection technology. Additionally, the storage unit (1430) can provide the stored data upon a request from the control unit (1440).

[0581] According to one embodiment of the present disclosure, the control unit (1440) can control the overall operations of the terminal. For example, the control unit (1440) can transmit and receive signals through the baseband processing unit (1420) and the RF processing unit (1410). Additionally, the control unit (1440) can write and read data to and from the storage unit (1440). To this end, the control unit (1440) may include at least one processor. For example, the control unit (1440) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as applications.

[0582] FIG. 15 illustrates the functional configuration of an NR base station according to one embodiment of the present disclosure.

[0583] Referring to FIG. 15, the base station may be configured to include an RF processing unit (1510), a baseband processing unit (1520), a backhaul communication unit (1530), a storage unit (1540), and a control unit (1550).

[0584] According to one embodiment of the present disclosure, the RF processing unit (1510) can perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1510) can up-convert a baseband signal provided by the baseband processing unit (1520) into an RF band signal and transmit it through an antenna, and down-convert an RF band signal received through an antenna into a baseband signal. For example, the RF processing unit (1510) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Although only one antenna is shown in FIG. 15, the first connection node may be equipped with multiple antennas. Additionally, the RF processing unit (1510) may include multiple RF chains. Furthermore, the RF processing unit (1510) may perform beamforming. For beamforming, the RF processing unit (1510) can adjust the phase and magnitude of each of the signals transmitted and received through a plurality of antennas or antenna elements. The RF processing unit can perform down-to-down MIMO operation by transmitting one or more layers.

[0585] According to one embodiment of the present disclosure, the baseband processing unit (1520) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (1520) can generate complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (1520) restores the received bit sequence by demodulating and decoding the baseband signal provided by the RF processing unit (1510). For example, in the case of an OFDM method, when transmitting data, the baseband processing unit (1520) can generate complex symbols by encoding and modulating the transmitted bit sequence, map the complex symbols to subcarriers, and then construct OFDM symbols through IFFT operation and CP insertion. Additionally, upon receiving data, the baseband processing unit (1520) can divide the baseband signal provided by the RF processing unit (1510) into OFDM symbol units, restore the signals mapped to subcarriers through FFT operations, and then restore the received bit sequence through demodulation and decoding. The baseband processing unit (1520) and the RF processing unit (1510) can transmit and receive signals as described above. Accordingly, the baseband processing unit (1520) and the RF processing unit (1510) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, a communication unit, or a wireless communication unit.

[0586] According to one embodiment of the present disclosure, the backhaul communication unit (1530) may provide an interface for performing communication with other nodes within the network. That is, the backhaul communication unit (1530) may convert a bit sequence transmitted from a main base station to another node, e.g., an auxiliary base station, a core network, etc., into a physical signal, and convert a physical signal received from another node into a bit sequence.

[0587] According to one embodiment of the present disclosure, the storage unit (1540) may store data such as a basic program, an application program, and configuration information for the operation of the main station. In particular, the storage unit (1540) may store information regarding a bearer assigned to a connected terminal, measurement results reported from the connected terminal, etc. Additionally, the storage unit (1540) may store information that serves as a criterion for determining whether to provide or disconnect multiple connections to the terminal. Furthermore, the storage unit (1540) may provide the stored data upon a request from the control unit (1550).

[0588] According to one embodiment, the control unit (1550) can control the overall operations of the main station. For example, the control unit (1550) can transmit and receive signals through the baseband processing unit (1520) and the RF processing unit (1510) or through the backhaul communication unit (1530). Additionally, the control unit (1550) can write and read data to and from the storage unit (1540). To this end, the control unit (1550) may include at least one processor.

[0589] Methods according to the embodiments described in the claims or specification of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software.

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

[0591] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), magnetic disc storage devices, CD-ROM (Compact Disc-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0592] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present invention through an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present invention.

[0593] In the specific embodiments of the present invention described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present invention is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed in the singular form, or even if a component is expressed in the singular form, it may be composed in the plural form.

[0594] Meanwhile, although specific embodiments have been described in the detailed description of the present invention, it is understood that various modifications are possible within the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

[0595] In the drawings describing the embodiments of the present disclosure, the order of description does not necessarily correspond to the order of execution, and the order of execution may be changed or executed in parallel. Additionally, the drawings describing the embodiments of the present disclosure may omit some components and include only some components to the extent that the essence of the present disclosure is not impaired.

[0596] The embodiments of the present disclosure may be practiced by combining some or all of the contents included in each embodiment to the extent that the essence of the present disclosure is not impaired.

[0597] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure are possible in addition to the embodiments disclosed herein.

Claims

1. A method performed by a terminal (user equipment, UE) in a wireless communication system, wherein the method comprises: A step of receiving an RRC release message from a base station that includes measIdleConfig regarding measurements in an RRC (radio resource control) idle state or an RRC inactive state; If the above measIdleConfig is set to setup, the step of saving at least one setting within the above measIdleConfig into VarMeasIdleConfig or VarEnhMeasIdleConfig; A step of transitioning to the above RRC idle state or the above RRC deactivated state; A step of receiving a measIdleConfigSIB (system information block) 11 from the base station regarding measurements in the RRC idle state or the RRC disabled state; A step of performing the measurement while the UE is in the RRC idle state or the RRC disabled state; Step of transitioning to an RRC connected state; A step of receiving a UE information request message including idleModeMeasurementReq from the base station; Step of setting measResultIdleEUTRA or measResultIdleNR within the UE information response message; The step of transmitting the UE information response message to the base station; and A method comprising the step of deleting measIdleValidityDuration within VarEnhMeasIdleConfig when measIdleValidityDuration is stored within VarEnhMeasIdleConfig.

2. In Paragraph 1, The above VarMeasIdleConfig includes configuration information for the measurement in the RRC idle state or the RRC disabled state, and The step of transitioning to the above RRC connection state is: A method comprising the step of stopping the T331 timer and releasing the VarMeasIdleConfig when the T331 timer is running.

3. In claim 1, the method is: If the above VarEnhMeasIdleConfig does not include the measIdleValidityDuration received from the above RRC release message: If the above SIB11 includes the measIdleConfigSIB and measIdleValidityDuration, the step of storing or replacing the measIdleValidityDuration of the measIdleConfigSIB within the SIB11 in the VarEnhMeasIdleConfig; and A method comprising the step of deleting the setting information regarding the validity period within the VarEnhMeasIdleConfig if the above SIB11 does not include the above measIdleConfigSIB or measIdleValidityDuration, and if the setting information regarding the validity period is stored within the VarEnhMeasIdleConfig.

4. In paragraph 3, the above method is: A method comprising the step of determining not to store or replace the measIdleValidityDuration of the measIdleConfigSIB in the SIB11 when the VarEnhMeasIdleConfig contains the measIdleValidityDuration received from the RRC release message.

5. In Paragraph 3, The above UE supports measValidationReportEMR, a method.

6. In Paragraph 1, A method in which the above measIdleValidityDuration indicates a time value for determining the validity of the measurement result in the above RRC idle state or the above RRC disabled state.

7. In claim 1, the step of setting the measResultIdleEUTRA or the measResultIdleNR within the UE information response message is: If the above UE has stored a VarMeasIdleReport containing measurement information regarding cells other than the PCell (primary cell): If validatedMeasurementsReq is included in the above UE information request message and the above measIdleValidityDuration is included in the above VarEnhMeasIdleConfig: A step of setting the measResultIdleEUTRA in the UE information response message to the value of the measReportIdleEUTRA in the VarMeasIdleReport for all valid measurement results; and A method comprising the step of setting the measResultIdleNR in the UE information response message to the value of the measReportIdleNR in the VarMeasIdleReport for all valid measurement results.

8. In a wireless communication system, regarding a terminal (user equipment, UE): At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the UE: Receive an RRC release message from a base station containing measIdleConfig regarding measurements in an RRC (radio resource control) idle state or RRC inactive state, and If the above measIdleConfig is set to setup, at least one setting within the above measIdleConfig is stored in VarMeasIdleConfig or VarEnhMeasIdleConfig, and Transitioning to the above RRC idle state or the above RRC disabled state, From the above base station, receive SIB (system information block)11, which contains measIdleConfigSIB regarding measurements in the RRC idle state or the RRC disabled state, and The above UE performs the measurement while the above RRC is in an idle state or the above RRC is disabled, and Transition to the RRC connected state, and Receive a UE information request message including idleModeMeasurementReq from the above base station, and Set measResultIdleEUTRA or measResultIdleNR within the UE information response message, and Transmitting the UE information response message to the above base station, and A UE that deletes the measIdleValidityDuration within the VarEnhMeasIdleConfig when the measIdleValidityDuration is stored in the VarEnhMeasIdleConfig.

9. In Paragraph 8, The above VarMeasIdleConfig includes configuration information for the measurement in the RRC idle state or the RRC disabled state, and The above commands are the above UE: A UE that stops the T331 timer and releases the VarMeasIdleConfig when the T331 timer is running.

10. In claim 8, the above instructions are: the UE If the above VarEnhMeasIdleConfig does not include configuration information regarding the validity period received from the above RRC release message: If the above SIB11 includes the measIdleConfigSIB and measIdleValidityDuration, the measIdleValidityDuration of the measIdleConfigSIB within the SIB11 is stored in or replaced with the VarEnhMeasIdleConfig, and A UE that, if the above SIB11 does not include the above measIdleConfigSIB or measIdleValidityDuration, deletes the setting information regarding the validity period within the above VarEnhMeasIdleConfig when the setting information regarding the validity period is stored within the above VarEnhMeasIdleConfig.

11. In Clause 10, the above instructions are: the UE A UE that determines not to store the measIdleValidityDuration of the measIdleConfigSIB in the SIB11 when the above VarEnhMeasIdleConfig includes the measIdleValidityDuration received from the RRC release message.

12. In Paragraph 10, The above UE is a UE that supports measValidationReportEMR.

13. In Paragraph 8, The above measIdleValidityDuration indicates a time value for determining the validity of the measurement result in the above RRC idle state or the above RRC disabled state, UE.

14. In Paragraph 13, The above commands are the above UE: If the above UE has stored a VarMeasIdleReport containing measurement information regarding cells other than the PCell (primary cell): If validatedMeasurementsReq is included in the above UE information request message and the above measIdleValidityDuration is included in the above VarEnhMeasIdleConfig: For all valid measurement results, the measResultIdleEUTRA in the above UE information response message is set to the value of measReportIdleEUTRA in the above VarMeasIdleReport, and A UE that sets the measResultIdleNR in the UE information response message to the value of measReportIdleNR in the VarMeasIdleReport for all valid measurement results.

Images