Method and device for measuring frequency according to configuration in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. According to various embodiments of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system may comprise the steps of: receiving first measurement configuration information associated with a master cell group (MCG) from a first base station; and transmitting a measurement result according to the first measurement configuration information to the first base station, wherein the first measurement configuration information may include information indicating the sequence of measuring at least one frequency associated with the first measurement configuration information.

Description

In a wireless communication system, a method and device for measuring a frequency according to a setting

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for measuring a frequency order according to a setting of a base station.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz (THz) band (for example, 3 THz band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

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

[0005] In addition, standardization of radio 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) to provide nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) to simplify random access procedures is also in progress, and standardization of system architecture / services for 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal is also in progress.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] According to various embodiments of the present disclosure, an electronic device and method capable of effectively providing a service in a wireless communication system are provided.

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

[0010] According to various embodiments of the present disclosure, in a wireless communication system, a method performed by a user equipment (UE) includes the steps of: receiving, from a first base station, first measurement configuration information associated with a master cell group (MCG); and transmitting, to the first base station, a measurement result according to the first measurement configuration information, wherein the first measurement configuration information may include information indicating an order for measurement of at least one frequency associated with the first measurement configuration information.

[0011] According to various embodiments of the present disclosure, in a wireless communication system, a method performed by a first base station includes the steps of transmitting, to a user equipment (UE), first measurement configuration information associated with a master cell group (MCG); and receiving, from the UE, a measurement result according to the first measurement configuration information, wherein the first measurement configuration information may include information indicating an order for measurement of at least one frequency associated with the first measurement configuration information.

[0012] The present disclosure provides an electronic device and method capable of effectively providing a service in a wireless communication system.

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

[0014] FIG. 1 illustrates the structure of an LTE system according to various embodiments of the present invention.

[0015] FIG. 2 illustrates a wireless protocol structure in an LTE system according to various embodiments of the present invention.

[0016] FIG. 3 illustrates the structure of a next-generation mobile communication system according to various embodiments of the present invention.

[0017] FIG. 4 illustrates a wireless protocol structure of a next-generation mobile communication system according to various embodiments of the present invention.

[0018] FIG. 5 illustrates a signal flow for a terminal to transmit a measurement result message to a base station in a next-generation mobile communication system according to various embodiments of the present invention.

[0019] FIG. 6 illustrates a signal flow for a terminal to transmit a measurement result message to a base station in a next-generation mobile communication system according to various embodiments of the present invention.

[0020] FIG. 7 illustrates an example for a terminal to perform measurements in accordance with a frequency measurement order set by a base station in a next-generation mobile communication system according to various embodiments of the present invention.

[0021] FIG. 8 illustrates a signal flow for a terminal with dual connectivity set to perform measurement according to a frequency measurement order set by a base station in a next-generation mobile communication system according to various embodiments of the present invention.

[0022] FIG. 9 illustrates a signal flow for a terminal with dual connectivity set to perform measurements according to a frequency measurement order set by a base station in a next-generation mobile communication system according to various embodiments of the present invention.

[0023] FIG. 10 illustrates a signal flow for a terminal with dual connectivity set to perform measurement according to a frequency measurement order set by a base station in a next-generation mobile communication system according to various embodiments of the present invention.

[0024] FIG. 11 illustrates the configuration of a terminal according to various embodiments of the present invention.

[0025] FIG. 12 illustrates the configuration of a base station according to various embodiments of the present invention.

[0026] The operating principles of the present invention will be described in detail below with reference to the attached drawings. In the following description of the present invention, detailed descriptions of known functions or components will be omitted if they are deemed to unnecessarily obscure the gist of the invention. Furthermore, the terms described below are defined based on their functions in the present invention and may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0027] In the following description of the present invention, detailed descriptions of known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present invention. Hereinafter, embodiments of the present invention will be described with reference to the attached drawings.

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

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

[0030] FIG. 1 illustrates the structure of an LTE system according to various embodiments of the present invention.

[0031] Referring to FIG. 1, the wireless access network of the LTE system may be composed of next-generation base stations (Evolved Node Bs, hereinafter referred to as ENBs, Node Bs or base stations) (105, 110, 115, 120), a Mobility Management Entity (MME) (125), and a Serving-Gateway (S-GW) (130). A user equipment (UE or terminal) (135) may access an external network through the ENBs (105 to 120) and the S-GW (130).

[0032] In Fig. 1, ENBs (105 to 120) may correspond to existing Node Bs of a UMTS (universal mobile telecommunication system) system. ENBs are connected to UEs (135) via a wireless channel and may perform more complex roles than existing Node Bs. In an LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, is serviced through a shared channel. Therefore, a device that collects status information such as buffer status, available transmission power status, and channel status of UEs and performs scheduling may be required, and ENBs (105 to 120) may be responsible for this. One ENB can typically control multiple cells. For example, in order to achieve a transmission speed of 100 Mbps, an LTE system may use, for example, Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology in a 20 MHz bandwidth. Additionally, an adaptive modulation and coding (AMC) method may be applied, which determines the modulation scheme and channel coding rate according to the channel conditions of the terminal. The S-GW (130) is a device that provides data bearers and can create or remove data bearers according to the control of the MME (125). The MME is a device that is responsible for various control functions as well as mobility management functions for the terminal and can be connected to multiple base stations.

[0033] FIG. 2 illustrates a wireless protocol structure in an LTE system according to various embodiments of the present invention.

[0034] Referring to FIG. 2, the wireless protocol of the LTE system may include PDCP (Packet Data Convergence Protocol) (205, 240), RLC (Radio Link Control) (210, 235), and MAC (Medium Access Control) (215, 230) in the terminal and ENB, respectively.

[0035] In one embodiment, Packet Data Convergence Protocol (PDCP) (205, 240) may be responsible for operations such as IP header compression / decompression. In one embodiment, the main functions of PDCP may include at least one of the following functions.

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

[0037] - User data transfer function

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

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

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

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

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

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

[0044] According to one embodiment, Radio Link Control (RLC) (210, 235) may reconfigure PDCP protocol data units (PDUs) to an appropriate size to perform automatic repeat request (ARQ) operations, etc. According to one embodiment, the main functions of RLC may include at least one of the following functions.

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

[0046] - ARQ function (Error Correction through ARQ (only for AM(acknowledged mode) data transfer))

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

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

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

[0050] - Duplicate detection (only for UM (unacknowledged mode) and AM data transfer)

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

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

[0053] - RLC re-establishment function

[0054] According to one embodiment, a medium access control (MAC) (215, 230) is connected to multiple RLC layer devices configured in a terminal, and can perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. According to one embodiment, the main functions of the MAC may include at least one of the following functions.

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

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

[0057] - Scheduling information reporting function

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

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

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

[0061] - MBMS (multimedia broadcast multicast services) service identification function

[0062] - Transport format selection function

[0063] - Padding function

[0064] According to one embodiment, the physical layer (220, 225) may perform an operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it over a wireless channel, or demodulating OFDM symbols received over a wireless channel, channel decoding them, and transmitting them to an upper layer.

[0065] FIG. 3 illustrates the structure of a next-generation mobile communication system according to various embodiments of the present invention.

[0066] Referring to FIG. 3, as illustrated, a wireless access network of a next-generation mobile communication system (hereinafter referred to as NR (new radio) or 2g) may be composed of a next-generation base station (New Radio Node B, hereinafter referred to as NR gNB or NR base station) (310) and a New Radio Core Network (NR CN) (305). A user terminal (New Radio User Equipment, hereinafter referred to as NR UE or terminal) (315) connects to an external network through the NR gNB (310) and the NR CN (core network) (305).

[0067] In Fig. 3, the NR gNB (310) may correspond to the eNB (Evolved Node B) of the existing LTE system. The NR gNB is connected to the NR UE (315) via a wireless channel and can provide a service that is superior to the existing Node B. In the next-generation mobile communication system, all user traffic is serviced through a shared channel, so a device that collects status information such as the buffer status of UEs, available transmission power status, and channel status and performs scheduling is required, and the NR NB (310) can be in charge of this. One NR gNB can typically control multiple cells. In order to implement ultra-high-speed data transmission compared to the current LTE, the NR system can have a bandwidth exceeding the existing maximum bandwidth, and beamforming technology can be additionally grafted with the orthogonal frequency division multiplexing method as a wireless access technology. In addition, an adaptive modulation and coding method that determines the modulation method and channel coding rate according to the channel status of the terminal can be applied. The NR CN (305) can perform functions such as mobility support, bearer setup, and QoS setup. The NR CN (305) is a device that handles various control functions as well as mobility management functions for terminals, and can be connected to multiple base stations. Furthermore, the next-generation mobile communication system can also be interoperable with the existing LTE system, and the NR CN (305) can be connected to the MME (325) via a network interface. The MME can be connected to the existing base station, the eNB (330).

[0068] FIG. 4 illustrates a wireless protocol structure of a next-generation mobile communication system according to various embodiments of the present invention.

[0069] Referring to FIG. 4, the wireless protocol of the next-generation mobile communication system may include NR SDAP (service data adaptation protocol) (401, 445), NR PDCP (405, 440), NR RLC (410, 435), and NR MAC (415, 430) in the terminal and NR base station, respectively.

[0070] According to one embodiment, the main functions of the NR SDAP (401, 445) may include some of the following functions:

[0071] - Transfer of user plane data

[0072] - Mapping function between a QoS (quality of service) flow and a DRB (data radio bearer) for both DL (downlink) and UL (uplink)

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

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

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

[0076] According to one embodiment, the main functions of NR PDCP (405, 440) may include some of the following functions:

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

[0078] - User data transfer function

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

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

[0081] - PDCP PDU reordering for reception

[0082] - Duplicate detection of lower layer SDUs

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

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

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

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

[0087] According to one embodiment, the main functions of the NR RLC (410, 435) may include some of the following functions:

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

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

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

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

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

[0093] - Re-segmentation of RLC data PDUs

[0094] - Reordering of RLC data PDUs

[0095] - Duplicate detection function

[0096] - Protocol error detection

[0097] - RLC SDU discard function

[0098] - RLC re-establishment function

[0099] In one embodiment, the in-sequence delivery function of an NR RLC device may mean the function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. The NR RLC device may include a function to reassemble and transmit a single RLC SDU that is received divided into multiple RLC SDUs, a function to reorder received RLC PDUs based on an RLC SN (sequence number) or a PDCP SN (sequence number), a function to record lost RLC PDUs by reordering the sequence, a function to report the status of lost RLC PDUs to the transmitter, a function to request retransmission of lost RLC PDUs, a function to transmit only RLC SDUs up to the lost RLC SDU in order to the upper layer in the case of a lost RLC SDU, or a function to transmit all RLC SDUs received before the timer starts in order to the upper layer in the case of a lost RLC SDU if a predetermined timer has expired even if there is a lost RLC SDU, or a function to transmit all RLC SDUs received up to the timer has expired in the order to the upper layer in the case of a lost RLC SDU if a predetermined timer has expired, or a function to transmit all RLC SDUs received up to the timer in the order to the upper layer in the case of a lost RLC SDU if there is a lost RLC SDU. It can contain at least one.

[0100] In one embodiment, the NR RLC device may also process RLC PDUs in the order in which they are received (e.g., in the order of arrival, regardless of the order of sequence number) and deliver them to the PDCP device out of order (out-of-sequence delivery). In the case of segments, the device may receive segments stored in a buffer or to be received later, reconstruct them into a complete RLC PDU, process them, and deliver them to the PDCP device.

[0101] In one embodiment, the NR RLC layer may not include concatenation functionality, and the above-described functions may be performed in the NR MAC layer or replaced with the multiplexing functionality of the NR MAC layer.

[0102] According to one embodiment, the out-of-sequence delivery function of the NR RLC device may mean a function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order. The NR RLC device may include a function of reassembling and delivering multiple RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs, or may include at least one of a function of storing and arranging the RLC SN or PDCP SN of received RLC PDUs to record any lost RLC PDUs.

[0103] According to one embodiment, the NR MAC (415, 430) may be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of the NR MAC may include some of the following functions.

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

[0105] - Multiplexing / demultiplexing of MAC SDUs

[0106] - Scheduling information reporting function

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

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

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

[0110] - MBMS service identification function

[0111] - Transport format selection function

[0112] - Padding function

[0113] According to one embodiment, the NR PHY layer (420, 425) may perform an operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it over a wireless channel, or demodulating OFDM symbols received over a wireless channel, channel decoding them, and transmitting them to an upper layer.

[0114] FIG. 5 illustrates a signal flow for a terminal to transmit a measurement result message to a base station in a next-generation mobile communication system according to various embodiments of the present invention.

[0115] According to various embodiments of the present disclosure, when a terminal measures frequencies set by a base station, the terminal has a characteristic of measuring a frequency according to the implementation of each terminal, regardless of the intention of the base station. As a result, even if a given service (e.g., voice over LTE (VoLTE)) can be optimally provided at a specific frequency, a situation may arise where the base station provides the above-described service to the terminal through a frequency other than the optimal frequency. This is because, based on a measurement result message sent by the terminal, the base station moves each terminal to a specific target cell by transmitting a predetermined RRC message (e.g., a handover message or an RRC disconnection message containing RedirectedCarrierInfo instructing the terminal to move to a specific frequency) to each terminal. For example, even if a base station sets the same measurement configuration information (e.g., E-UTRA frequency x, E-UTRA frequency y, E-UTRA frequecny z) to two terminals that want to provide VoLTE service, one terminal may first measure E-UTRA frequency x and transmit a measurement result message based on it to the base station, and the other terminal may first measure E-UTRA frequency z and transmit a measurement result message based on it to the base station. Even if E-UTRA frequency x is a frequency optimized for VoLTE service, there may be a case where the base station moves only one terminal to a cell belonging to E-UTRA frequency x and moves the other terminal to a cell belonging to E-UTRA frequency z.

[0116] Referring to FIG. 5, in steps (505, 506), each terminal (501, 503) may establish an RRC connection with an NR base station (502) and be in an RRC connection mode (RRC_CONNECTED).

[0117] In steps (510, 511), the base station (502) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to each terminal (501, 503). The measurement configuration information may include at least one of measurement objects, reporting configurations, measurement identities, measurement filtering configuration information (Quantity configurations), and measurement gap configuration information (Measurement gaps), and the description of each parameter may be as follows. At this time, the description of each parameter may refer to the document of 3GPP Release 17 TS 38.311.

[0118] 1.Measurement objects:A list of objects on which the UE shall perform the measurements.- For intra-frequency and inter-frequency measurements a measurement object indicates the frequency / time location and subcarrier spacing of reference signals to be measured. Associated with this measurement object, the network may configure a list of cell specific offsets, a list of 'exclude-listed' cells and a list of 'allow-listed' cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting. Allow-listed cells are the only ones applicable in event evaluation or measurement reporting.- ThemeasObjectIdof the MO which corresponds to each serving cell is indicated byservingCellMOwithin the serving cell configuration.- For inter-RAT E-UTRA measurements a measurement object is a single E-UTRA carrier frequency. Associated with this E-UTRA carrier frequency, the network can configure a list of cell specific offsets and a list of 'exclude-listed' cells.Exclude-listed cells are not applicable in event evaluation or measurement reporting.- For inter-RAT UTRA-FDD measurements a measurement object is a set of cells on a single UTRA-FDD carrier frequency.- For NR sidelink measurements of L2 U2N Relay UEs, a measurement object is a single NR sidelink frequency to be measured.- For CBR measurement of NR sidelink communication, a measurement object is a set of transmission resource pool(s) on a single carrier frequency for NR sidelink communication.- For CBR measurement of NR sidelink discovery, a measurement object is a set of discovery dedicated resource pool(s) or transmission resource pool(s) also used for NR sidelink discovery on a single carrier frequency for NR sidelink discovery.- For CLI measurements a measurement object indicates the frequency / time location of SRS resources and / or CLI-RSSI resources, and subcarrier spacing of SRS resources to be measured.2.Reporting configurations:A list of reporting configurations where there can be one or multiple reporting configurations per measurement object. Each measurement reporting configuration consists of the following:- Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be periodical or a single event description.- RS type: The RS that the UE uses for beam and cell measurement results (SS / PBCH block or CSI-RS).- Reporting format: The quantities per cell and per beam that the UE includes in the measurement report (e.g. RSRP) and other associated information such as the maximum number of cells and the maximum number beams per cell to report.In case of conditional reconfiguration, each configuration consists of the following:- Execution criteria: The criteria the UE uses for conditional reconfiguration execution.- RS type: The RS that the UE uses for obtaining beam and cell measurement results (SS / PBCH block-based or CSI-RS-based), used for evaluating conditional reconfiguration execution condition.3.Measurement identities:For measurement reporting, a list of measurement identities where each measurement identity links one measurement object with one reporting configuration. By configuring multiple measurement identities, it is possible to link more than one measurement object to the same reporting configuration, as well as to link more than one reporting configuration to the same measurement object. The measurement identity is also included in the measurement report that triggered the reporting, serving as a reference to the network. For conditional reconfiguration triggering, one measurement identity links to exactly one conditional reconfiguration trigger configuration. And up to 2 measurement identities can be linked to one conditional reconfiguration execution condition.4.Quantity configurations:The quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodic reporting of that measurement. For NR measurements, the network may configure up to 2 quantity configurations with a reference in the NR measurement object to the configuration that is to be used. In each configuration, different filter coefficients can be configured for different measurement quantities, for different RS types, and for measurements per cell and per beam.5.Measurement gaps:Periods that the UE may use to perform measurements.

[0119] According to one embodiment, the base station (502) may provide measurement configuration information for measuring frequencies (intra-frequency) to which the corresponding Special Cell (SpCell) belongs, frequencies adjacent to the SpCell (inter-frequency), and frequencies using a different radio access technology (RAT) than the SpCell, to each of the terminals (501, 503). Specific information regarding the measurement configuration information may be expressed in the following ASN.1 structure.

[0120]

[0121]

[0122] According to various embodiments of the present disclosure, for convenience of explanation, the following embodiments are described based on an operation in which a base station (502) sets three E-UTRA carrier frequency x, E-UTRA carrier frequency y, and E-UTRA carrier frequency z to each of terminals (501, 503) through the same measurement setting information and sequentially includes them in MeasObjectToAddModList or MeasIdToAddModList.

[0123] In one embodiment, for example, each MeasObjectToAddMod included in the MeasObjectToAddModList may be composed of a measObjectId and a MeasObject, and the MeasObject may be set to MeasObjectEUTRA (e.g., set to one of E-UTRA carrier frequency x, E-UTRA carrier frequency y, E-UTRA carrier frequency z), and the MeasObjectToAddModList may sequentially include (measObjectId 1, E-UTRA carrier frequency x), (measObjectId 2, E-UTRA carrier frequency y), (measObjectId 3 E-UTRA carrier frequency z).

[0124] According to one embodiment, each MeasIdToAddMod included in the MeasIdToAddModList may be composed of measId, measObjectId, and reportConfigId, and the MeasIdToAddModList may sequentially include (measId 1, measObjectId1, reportConfigId 1), (measId 2, measObjectId2, reportConfigId2), (measId 3, measObjectId3, reportConfigId3).

[0125] In steps (515, 516), each terminal (501, 503) can perform measurement based on measurement setting information received from the base station (502).

[0126] According to various embodiments of the present disclosure, the order in which terminals (501, 503) measure the set frequencies can be measured according to the implementation of each terminal.

[0127] For example, in step (515), the terminal (501) can perform measurement in the order of measObjects included in MeasObjectToAddModList set in MeasConfig (e.g., E-UTRA frequency x, E-UTRA frequency y, E-UTRA frequencyz).

[0128] In step (516), unlike the terminal (501), another terminal (503) can perform measurements in the reverse order of measObjects included in MeasObjectToAddModList set in MeasConfig (e.g., E-UTRA frequency z, E-UTRA frequency y, E-UTRA frequency x).

[0129] According to one embodiment, each terminal (501, 503) may perform measurement by applying measurement gap configuration information (measGapConfig) included in the measurement configuration information, or may perform measurement without measurement gap configuration information (e.g., when interFrequencyConfig-NoGap is set and inter-frequency SSB belongs to the active Downlink Bandwidth Part of the terminal). Specifically, according to one embodiment, each terminal (501, 503) may perform measurement through the following procedure. At this time, a description of the operation of each terminal (501, 503) performing measurement may refer to the document of 3GPP Release 17 TS 38.311.

[0130] 1> whenever the UE has ameasConfig, perform RSRP and RSRQ measurements for each serving cell for whichservingCellMOis configured as follows:2> if thereportConfigassociated with at least onemeasIdincluded in themeasIdListwithinVarMeasConfigcontains anrsTypeset tossbandssb-ConfigMobilityis configured in themeasObjectindicated by theservingCellMO:3> if thereportConfigassociated with at least onemeasIdincluded in themeasIdListwithinVarMeasConfigcontains areportQuantityRS-IndexesandmaxNrofRS-IndexesToReportand contains anrsTypeset tossb:4> derive layer 3 filtered RSRP and RSRQ per beam for the serving cell based on SS / PBCH block, as described in 5.5.3.3a;3> derive serving cell measurement results based on SS / PBCH block, as described in 5.5.3.3;2> if thereportConfigassociated with at least onemeasIdincluded in themeasIdListwithinVarMeasConfigcontains anrsTypeset tocsi-rsandCSI-RS-ResourceConfigMobilityis configured in themeasObjectindicated by theservingCellMO:3> if thereportConfigassociatedwith at least onemeasIdincluded in themeasIdListwithinVarMeasConfigcontains areportQuantityRS-IndexesandmaxNrofRS-IndexesToReportand contains anrsTypeset tocsi-rs:4> derive layer 3 filtered RSRP and RSRQ per beam for the serving cell based on CSI-RS, as described in 5.5.3.3a;3> derive serving cell measurement results based on CSI-RS, as described in 5.5.3.3;1> for each serving cell for whichservingCellMOis configured, if thereportConfigassociated with at least onemeasIdincluded in themeasIdListwithinVarMeasConfigcontains SINR as trigger quantity and / or reporting quantity:2> if thereportConfigcontainsrsTypeset tossbandssb-ConfigMobilityis configured in theservingCellMO:3> if thereportConfigcontains areportQuantityRS-IndexesandmaxNrofRS-IndexesToReport:4> derive layer 3 filtered SINR per beam for the serving cell based on SS / PBCH block, as described in 5.5.3.3a;3> derive serving cell SINR based on SS / PBCH block, as described in 5.5.3.3;2> if thereportConfigcontainsrsTypesettocsi-rsandCSI-RS-ResourceConfigMobilityis configured in theservingCellMO:3> if thereportConfigcontains areportQuantityRS-IndexesandmaxNrofRS-IndexesToReport:4> derive layer 3 filtered SINR per beam for the serving cell based on CSI-RS, as described in 5.5.3.3a;3> derive serving cell SINR based on CSI-RS, as described in 5.5.3.3;1> for eachmeasIdincluded in themeasIdListwithinVarMeasConfig:2> if thereportTypefor the associatedreportConfigis set toreportCGIand timer T321 is running:3> ifuseAutonomousGapsis configured for the associatedreportConfig:4> perform the corresponding measurements on the frequency and RAT indicated in the associatedmeasObjectusing autonomous gaps as necessary;3> else:4> perform the corresponding measurements on the frequency and RAT indicated in the associatedmeasObjectusing available idle periods;3> if the cell indicated byreportCGIfield for the associatedmeasObjectis an NR cell and that indicated cell is broadcastingSIB1(see TS 38.213

[0013] , clause 13):4> tryto acquireSIB1in the concerned cell;3> if the cell indicated byreportCGIfield is an E-UTRA cell:4> try to acquireSystemInformationBlockType1in the concerned cell;2> if theul-DelayValueConfigis configured for the associatedreportConfig:3> ignore themeasObject;3> for each of the configured DRBs,configure the PDCP layer to perform corresponding average UL PDCP packet delay measurement per DRB;2> if theul-ExcessDelayConfigis configured for the associatedreportConfig:3> ignore themeasObject;3> for each of the configured DRBs,configure the PDCP layer to perform corresponding UL PDCP Excess Packet Delay delay measurement according to the configured threshold per DRB;2> if thereportTypefor the associatedreportConfigisperiodical,eventTriggered; or2> if thereportTypefor the associatedreportConfigiscondTriggerConfig,themeasIdis within the MCGmeasConfigand is indicated in thecondExecutionCondassociated to acondReconfigIdin the MCGVarConditionalReconfig(for CHO, CPA or MN-initiated inter-SN CPC inNR-DC); or2> if thereportTypefor the associatedreportConfigiscondTriggerConfig, themeasIdis within the SCGVarMeasConfigand is indicated in thecondExecutionCondassociated to acondReconfigIdin the SCGVarConditionalReconfig(for intra-SN CPC); or2> if thereportTypefor the associatedreportConfigiscondTriggerConfig, themeasIdis within the SCGVarMeasConfigand is indicated in thecondExecutionCondSCGassociated to acondReconfigIdin the MCGVarConditionalReconfig(for SN-initiated inter-SN CPC in NR-DC); or2> if thereportTypefor the associatedreportConfigiscondTriggerConfig, themeasIdis within the SCGVarMeasConfigand is indicated in thetriggerConditionSNassociated to acondReconfigurationIdinVarConditionalReconfigurationas specified in TS 36.331

[0010] (for SN-initiated inter-SN CPC in EN-DC):3> if a measurement gap configuration is setup, or3> if the UE does not require measurement gaps to perform the concerned measurements:4> ifs-MeasureConfigis not configured, or4> ifs-MeasureConfigis settossb-RSRPand the NR SpCell RSRP based on SS / PBCH block, after layer 3 filtering, is lower thanssb-RSRP,or4> ifs-MeasureConfigis set tocsi-RSRPand the NR SpCell RSRP based on CSI-RS, after layer 3 filtering, is lower thancsi-RSRP:5> if themeasObjectis associated to NR and thersTypeis set tocsi-rs:6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:7> derive layer 3 filtered beam measurements only based on CSI-RS for each measurement quantity indicated inreportQuantityRS-Indexes, as described in 5.5.3.3a;6> derive cell measurement results based on CSI-RS for the trigger quantity and each measurement quantity indicated inreportQuantityCellusing parameters from the associatedmeasObject, as described in 5.5.3.3;5> if themeasObjectis associated to NR and thersTypeis set tossb:6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:7> derive layer 3 beam measurements only based onSS / PBCH block for each measurement quantity indicated inreportQuantityRS-Indexes, as described in 5.5.3.3a;6> derive cell measurement results based on SS / PBCH block for the trigger quantity and each measurement quantity indicated inreportQuantityCellusing parameters from the associatedmeasObject, as described in 5.5.3.3;5> if themeasObjectis associated to E-UTRA:6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concernedmeasObject, as described in 5.5.3.2;5> if the measObject is associated to UTRA-FDD:6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concernedmeasObject, as described in 5.5.3.2;5> if the measObject is associated to L2 U2N Relay UE:6> perform the corresponding measurements associated to candidate Relay UEs on the frequencies indicated in the concernedmeasObject, as described in 5.5.3.4;4> if themeasRSSI-ReportConfigis configured in theassociatedreportConfig:5> perform the RSSI and channel occupancy measurements on the frequency indicated in the associatedmeasObject;NOTE 0: The network avoids configuring UEs supporting only CHO and / or Rel-16 CPC with measurements not referred to by any execution condition.2> if thereportTypefor the associatedreportConfigis set toreportSFTDand thenumberOfReportsSentas defined within theVarMeasReportListfor thismeasIdis less than one:3> if thereportSFTD-Measis set totrue:4> if themeasObjectis associated to E-UTRA:5> perform SFTD measurements between the PCell and the E-UTRA PSCell;5> if thereportRSRPis set totrue;6> perform RSRP measurements for the E-UTRA PSCell;4> else if themeasObjectis associated to NR:5> perform SFTD measurements between the PCell and the NR PSCell;5> if thereportRSRPis set totrue;6> perform RSRP measurements for the NR PSCell based on SSB;3> else if thereportSFTD-NeighMeasis included:4> if themeasObjectis associated to NR:5> if thedrx-SFTD-NeighMeasis included:6>perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected based on parameters in the associatedmeasObjectusing available idle periods;5> else:6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected based on parameters in the associatedmeasObject;5> if thereportRSRPis set totrue:6> perform RSRP measurements based on SSB for the NR neighbouring cell(s) detected based on parameters in the associatedmeasObject;2> if thereportTypefor the associatedreportConfigiscli-Periodicalorcli-EventTriggered:3> perform the corresponding measurements associated to CLI measurement resources indicated in the concernedmeasObjectCLI;2> perform the evaluation of reporting criteria as specified in 5.5.4, except ifreportConfigiscondTriggerConfig.The UE acting as a L2 U2N Remote UE whenever configured withmeasConfigshall:1> perform the corresponding measurements associated to the serving L2 U2N Relay UE, as described in 5.5.3.4;NOTE 1: The evaluation ofconditional reconfiguration execution criteria is specified in 5.3.5.13.The UE capable of Rx-Tx time difference measurement when configured withmeasObjectRxTxDiffshall:1> perform the corresponding Rx-Tx time difference measurements associated with downlink reference signals indicated in the concernedmeasObjectRxTxDiff.The UE capable of CBR measurement when configured to transmit NR sidelink communication / discovery shall:1> If the frequency used for NR sidelink communication / discovery is included insl-FreqInfoToAddModListinsl-ConfigDedicatedNRwithinRRCReconfigurationmessage or includedinsl-ConfigCommonNRwithinSIB12:2> if the UE is in RRC_IDLE or in RRC_INACTIVE:3> if configured with NR sidelink communication and the cell chosen for NR sidelink communication providesSIB12which includessl-TxPoolSelectedNormalorsl-TxPoolExceptionalforthe concerned frequency; or3> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery providesSIB12whichincludessl-TxPoolSelectedNormalorsl-TxPoolExceptionalbut does not includesl-DiscTxPoolSelectedforthe concerned frequency:4> perform CBR measurement on pool(s) insl-TxPoolSelectedNormalorsl-TxPoolExceptionalfor the concerned frequency inSIB12;3> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery providesSIB12which includessl-DiscTxPoolSelectedforthe concerned frequency:4> perform CBR measurement on pools insl-DiscTxPoolSelectedandsl-TxPoolExceptionalfor the concerned frequency inSIB12;2> if the UE is in RRC_CONNECTED:3> iftx-PoolMeasToAddModListis included inVarMeasConfig:4> perform CBR measurements on each transmission resource pool indicated in thetx-PoolMeasToAddModList;3> ifsl-DiscTxPoolSelected,sl-TxPoolSelectedNormal,sl-TxPoolSchedulingorsl-TxPoolExceptionalis included insl-ConfigDedicatedNRfor the concerned frequency withinRRCReconfiguration:4> perform CBR measurement on pool(s)insl-DiscTxPoolSelected,sl-TxPoolSelectedNormal,sl-TxPoolSchedulingandsl-TxPoolExceptionalif included insl-ConfigDedicatedNRfor the concerned frequency withinRRCReconfiguration;3> else:4> if configured with NR sidelink communication and the cell chosen for NR sidelink communication providesSIB12which includessl-TxPoolSelectedNormalorsl-TxPoolExceptionalforthe concerned frequency; or4> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery providesSIB12which includessl-TxPoolSelectedNormalorsl-TxPoolExceptionalbut does not providesl-DiscTxPoolSelectedforthe concerned frequency:5> perform CBR measurement on pool(s) insl-TxPoolSelectedNormalorsl-TxPoolExceptionalfor the concerned frequency inSIB12;4> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery providesSIB12which includessl-DiscTxPoolSelectedforthe concerned frequency:5> perform CBR measurement on pools insl-DiscTxPoolSelectedandsl-TxPoolExceptionalfor the concernedfrequency inSIB12;1> else:2> if configured with NR sidelink communication andsl-TxPoolSelectedNormalis included inSidelinkPreconfigNRfor the concerned frequency; or2> if configured with NR sidelink discovery andsl-TxPoolSelectedNormalis included inSidelinkPreconfigNRbutsl-DiscTxPoolSelectedis not included inSidelinkPreconfigNRfor the concerned frequency:3> perform CBR measurement on pool(s) insl-TxPoolSelectedNormalinSidelinkPreconfigNRfor the concerned frequency.2> if configured with NR sidelink discovery andsl-DiscTxPoolSelectedis included inSidelinkPreconfigNRfor the concerned frequency:3> perform CBR measurement on pools insl-DiscTxPoolSelectedif included inSidelinkPreconfigNR.NOTE 2: In case the configurations for NR sidelink communication and CBR measurement are acquired via the E-UTRA, configurations for NR sidelink communication inSIB12,sl-ConfigDedicatedNRwithinRRCReconfigurationused in this clause are provided by the configurationsinSystemInformationBlockType28,sl-ConfigDedicatedForNRwithinRRCConnectionReconfigurationas specified in TS 36.331

[0010] , respectively.NOTE 3: If a UE that is configured by upper layers to transmit V2X sidelink communication is configured by NR with transmission resource pool(s) and the measurement objects concerning V2X sidelink communication (i.e. bysl-ConfigDedicatedEUTRA-Info), it shall perform CBR measurement as specified in clause 5.5.3 of TS 36.331

[0010] , based on the transmission resource pool(s) and the measurement object(s) concerning V2X sidelink communication configured by NR.NOTE 4: For V2X sidelink communication, each of the CBR measurement results is associated with a resource pool, as indicated by thepoolReportId(see TS 36.331

[0010] ), that refers to a pool as included insl-ConfigDedicatedEUTRA-InfoorSIB13.

[0131] When each terminal performs measurement through the above-described procedure, the method for performing Layer 3 filtering (Layer 3 filtering), the method for deriving cell measurement results (Derivation of cell measurement results), and the method for deriving Layer 3 beam filtered measurement (Derivation of layer 3 beam filtered measurement) can each follow the procedures below. At this time, the description of the operation for performing the above-described cell measurement can be referenced from the document of 3GPP Release 17 TS 38.311.

[0132]

[0133]

[0134]

[0135] In step (520), the terminal (501) can determine whether a condition for reporting a measurement result message (MeasurementReport) to the base station (502) is triggered based on the result measured in step (515).

[0136] In step (521), the terminal (503) can determine whether a condition for reporting a measurement result message (MeasurementReport) to the base station (502) is triggered based on the result measured in step (516).

[0137] According to various embodiments, the measurement report triggering condition determined by each terminal (501, 503) may include an event-based or periodic basis. For example, the measurement configuration information received by each terminal in step (510) (or step (511)) may include one or more measObjectId, reportConfigId, and measId, and since each measId is mapped to a specific measObject and a specific reportConfig, the terminal may determine whether the reporting criterion specified in a specific reportConfig is satisfied.

[0138] In steps (525, 536), if each terminal (501, 503) satisfies the above-described reporting conditions, the terminal may transmit a measurement result report message (MeasurementReport) including the measId mapped to the corresponding reportConfig and the measurement result associated with the corresponding measId to the base station. Specifically, according to one embodiment, each terminal (501, 503) may determine whether the measurement result is triggered through the following procedure. At this time, a description of the operation for each terminal (501, 503) to determine whether the measurement result is triggered may refer to the document of 3GPP Release 17 TS 38.311.

[0139] If AS security has been activated successfully, the UE shall:1> for eachmeasIdincluded in themeasIdListwithinVarMeasConfig:2> if the correspondingreportConfigincludes areportTypeset toeventTriggeredorperiodical:3> if the correspondingmeasObjectconcerns NR:4> if the correspondingreportConfigincludesmeasRSSI-ReportConfig:5> consider the resource indicated by thermtc-Configon the associated frequency to be applicable;4> if theeventA1oreventA2is configured in the correspondingreportConfig:5> consider only the serving cell to be applicable;4> if theeventA3oreventA5is configured in the correspondingreportConfig:5> if a serving cell is associated with ameasObjectNRand neighbours are associated with anothermeasObjectNR, consider any serving cell associated with the othermeasObjectNRto be a neighbouring cell as well;4> if theeventX2is configured in the correspondingreportConfig:5> consider only the serving L2 U2N Relay UE to be applicable;4> if correspondingreportConfigincludesreportTypeset toperiodical; or4> for measurement events other thaneventA1,eventA2, eventD1oreventX2:5> ifuseAllowedCellListis set totrue:6> consider any neighbouring cell detected based on parameters in the associatedmeasObjectNRto be applicable when the concerned cell is included in theallowedCellsToAddModListdefined within theVarMeasConfigfor thismeasId;5> else:6> consider any neighbouring cell detected based on parameters in the associatedmeasObjectNRto be applicable when the concerned cell is not included in theexcludedCellsToAddModListdefined within theVarMeasConfigfor thismeasId;3> else if the correspondingmeasObjectconcerns E-UTRA:4> ifeventB1oreventB2is configured in the correspondingreportConfig:5> consider a serving cell, if any, on the associated E-UTRA frequency as neighbour cell;4> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is not included in theexcludedCellsToAddModListEUTRANdefined within theVarMeasConfigfor thismeasId;3> else if the correspondingmeasObjectconcerns UTRA-FDD:4> ifeventB1-UTRA-FDDoreventB2-UTRA-FDDis configured in the correspondingreportConfig; or4> if correspondingreportConfigincludesreportTypeset toperiodical:5> consider a neighbouring cell on the associated frequency to be applicable when the concerned cell is included in thecellsToAddModListdefined within theVarMeasConfigfor thismeasId;3> else if the correspondingmeasObjectconcerns L2 U2N Relay UE:4> ifeventY1-RelayoreventY2-Relayis configured in the correspondingreportConfig; or4> if correspondingreportConfigincludesreportTypeset toperiodical:5> consider any L2 U2N Relay UE fulfilling upper layer criteria detected on the associated frequency to be applicable for thismeasId;2> else if the correspondingreportConfigincludes areportTypeset toreportCGI:3> consider the cell detected on the associatedmeasObjectwhich has a physical cell identity matching the value of thecellForWhichToReportCGIincluded in the correspondingreportConfigwithin theVarMeasConfigto be applicable;2> else if the correspondingreportConfigincludes areportTypeset toreportSFTD:3> if the correspondingmeasObjectconcerns NR:4> if thereportSFTD-Measis set totrue:5> consider the NR PSCell to be applicable;4> else if thereportSFTD-NeighMeasis included:5> ifcellsForWhichToReportSFTDis configured in the correspondingreportConfig:6> consider any NR neighbouring cell detected on the associatedmeasObjectNRwhich has a physical cell identity that is included in thecellsForWhichToReportSFTDto be applicable;5> else:6> consider up to 3 strongest NR neighbouring cells detected based on parameters in the associatedmeasObjectNRto be applicable when the concerned cells are not included in theexcludedCellsToAddModListdefined within theVarMeasConfigfor thismeasId;3> else if the correspondingmeasObjectconcerns E-UTRA:4> if thereportSFTD-Measis set totrue:5> consider the E-UTRA PSCell to be applicable;2> else if the correspondingreportConfigincludes areportTypeset tocli-Periodical or cli-EventTriggered:3> consider all CLI measurement resources included in the correspondingmeasObjectto be applicable;2> else if the correspondingreportConfigincludes areportTypeset torxTxPeriodical:3> consider all Rx-Tx time difference measurement resources included in the correspondingmeasObjectto be applicable;2> if the correspondingreportConfigconcerns the reporting for NR sidelink communication / discovery (i.e.reportConfigNR-SL):3> consider the transmission resource pools indicated by thetx-PoolMeasToAddModListdefined within theVarMeasConfigfor thismeasIdto be applicable;2> if thereportTypeis set toeventTriggeredand if the entry condition applicable for this event, i.e. the event corresponding with theeventIdof the correspondingreportConfigwithinVarMeasConfig, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken duringtimeToTriggerdefined for this event within theVarMeasConfig, while theVarMeasReportListdoes not include a measurement reporting entry for thismeasId(a first cell triggers the event):3> include a measurement reporting entry within theVarMeasReportListfor thismeasId;3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> include the concerned cell(s) in thecellsTriggeredListdefined within theVarMeasReportListfor thismeasId;3> ifuseT312is set totrueinreportConfigfor this event:4> if T310 for the corresponding SpCell is running; and4> if T312 is not running for corresponding SpCell:5> start timer T312 for the corresponding SpCell with the value of T312 configured in the correspondingmeasObjectNR;3> initiate the measurement reporting procedure, as specified in 5.5.5;2> else if thereportTypeis set toeventTriggeredand if the entry condition applicable for this event, i.e. the event corresponding with theeventIdof the correspondingreportConfigwithinVarMeasConfig, is fulfilled for one or more applicable cells not included in thecellsTriggeredListfor all measurements after layer 3 filtering taken duringtimeToTriggerdefined for this event within theVarMeasConfig(a subsequent cell triggers the event):3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> include the concerned cell(s) in thecellsTriggeredListdefined within theVarMeasReportListfor thismeasId;3> ifuseT312is set totrueinreportConfigfor this event:4> if T310 for the corresponding SpCell is running; and4> if T312 is not running for corresponding SpCell:5> start timer T312 for the corresponding SpCell with the value of T312 configured in the correspondingmeasObjectNR;3> initiate the measurement reporting procedure, as specified in 5.5.5;2> if thereportTypeis set toeventTriggeredand if the leaving condition applicable for this event is fulfilled for one or more of the cells included in thecellsTriggeredListdefined within theVarMeasReportListfor thismeasIdfor all measurements after layer 3 filtering taken duringtimeToTriggerdefined within theVarMeasConfigfor this event:3> remove the concerned cell(s) in thecellsTriggeredListdefined within theVarMeasReportListfor thismeasId;3> ifreportOnLeaveis set totruefor the corresponding reporting configuration:4> initiate the measurement reporting procedure, as specified in 5.5.5;3> if thecellsTriggeredListdefined within theVarMeasReportListfor thismeasIdis empty:4> remove the measurement reporting entry within theVarMeasReportListfor thismeasId;4> stop the periodical reporting timer for thismeasId, if running;2> if thereportTypeis set toeventTriggeredand if the entry condition applicable for this event, i.e. the event corresponding with theeventIdof the correspondingreportConfigwithinVarMeasConfig, is fulfilled for one or more applicable L2 U2N Relay UEs for all measurements after layer 3 filtering taken duringtimeToTriggerdefined for this event within theVarMeasConfig, while theVarMeasReportListdoes not include a measurement reporting entry for thismeasId(a first L2 U2N Relay UE triggers the event):3> include a measurement reporting entry within theVarMeasReportListfor thismeasId;3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> include the concerned L2 U2N Relay UE(s) in therelaysTriggeredListdefined within theVarMeasReportListfor thismeasId;3> initiate the measurement reporting procedure, as specified in 5.5.5;2> else if thereportTypeis set toeventTriggeredand if the entry condition applicable for this event, i.e. the event corresponding with theeventIdof the correspondingreportConfigwithinVarMeasConfig, is fulfilled for one or more applicable L2 U2N Relay UEs not included in therelaysTriggeredListfor all measurements after layer 3 filtering taken duringtimeToTriggerdefined for this event within theVarMeasConfig(a subsequent L2 U2N Relay UE triggers the event):3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> include the concerned L2 U2N Relay UE(s) in therelaysTriggeredListdefined within theVarMeasReportListfor thismeasId;3> initiate the measurement reporting procedure, as specified in 5.5.5;2> else if thereportTypeis set toeventTriggeredand if the leaving condition applicable for this event is fulfilled for one or more of the L2 U2N Relay UEs included in therelaysTriggeredListdefined within theVarMeasReportListfor thismeasIdfor all measurements after layer 3 filtering taken duringtimeToTriggerdefined within theVarMeasConfigfor this event:3> remove the concerned L2 U2N Relay UE(s) in therelaysTriggeredListdefined within theVarMeasReportListfor thismeasId;3> ifreportOnLeaveis set totruefor the corresponding reporting configuration:4> initiate the measurement reporting procedure, as specified in 5.5.5;3> if therelaysTriggeredListdefined within theVarMeasReportListfor thismeasIdis empty:4> remove the measurement reporting entry within theVarMeasReportListfor thismeasId;4> stop the periodical reporting timer for thismeasId, if running;2> else if thereportTypeis set toeventTriggeredand if the entry condition applicable for this event, i.e. the event corresponding with theeventIdof the correspondingreportConfigwithinVarMeasConfig, is fulfilled for one or more applicable transmission resource pools for all measurements taken duringtimeToTriggerdefined for this event within theVarMeasConfig, while theVarMeasReportListdoes not include an measurement reporting entry for thismeasId(a first transmission resource pool triggers the event):3> include a measurement reporting entry within theVarMeasReportListfor thismeasId;3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> include the concerned transmission resource pool(s) in thepoolsTriggeredListdefined within theVarMeasReportListfor thismeasId;3> initiate the measurement reporting procedure, as specified in 5.5.5;2> else if thereportTypeis set toeventTriggeredand if the entry condition applicable for this event, i.e. the event corresponding with theeventIdof the correspondingreportConfigwithinVarMeasConfig, is fulfilled for one or more applicable transmission resource pools not included in thepoolsTriggeredListfor all measurements taken duringtimeToTriggerdefined for this event within theVarMeasConfig(a subsequent transmission resource pool triggers the event):3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> include the concerned transmission resource pool(s) in thepoolsTriggeredListdefined within theVarMeasReportListfor thismeasId;3> initiate the measurement reporting procedure, as specified in 5.5.5;2> if thereportTypeis set toeventTriggeredand if the leaving condition applicable for this event is fulfilled for one or more applicable transmission resource pools included in thepoolsTriggeredListdefined within theVarMeasReportListfor thismeasIdfor all measurements taken duringtimeToTriggerdefined within theVarMeasConfigfor this event:3> remove the concerned transmission resource pool(s) in thepoolsTriggeredListdefined within theVarMeasReportListfor thismeasId;3> if thepoolsTriggeredListdefined within theVarMeasReportListfor thismeasIdis empty:4> remove the measurement reporting entry within theVarMeasReportListfor thismeasId;4> stop the periodical reporting timer for thismeasId, if running2> else if thereportTypeis set toeventTriggeredand if theeventIdis set toeventD1and if the entering condition applicable for this event, i.e. the event corresponding with theeventIdof the correspondingreportConfigwithinVarMeasConfig, is fulfilled duringtimeToTriggerdefined for this event within theVarMeasConfig, while theVarMeasReportListdoes not include a measurement reporting entry for thismeasId:3> include a measurement reporting entry within theVarMeasReportListfor thismeasId;3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> initiate the measurement reporting procedure, as specified in 5.5.5;2> else if thereportTypeis set toeventTriggeredand if theeventIdis set toeventD1and if the leaving condition applicable for this event is fulfilled for the associatedVarMeasReportwithin theVarMeasReportListfor thismeasIdduringtimeToTriggerdefined within theVarMeasConfigfor this event:3> ifreportOnLeaveis set totruefor the corresponding reporting configuration:4> initiate the measurement reporting procedure, as specified in 5.5.5;3> remove the measurement reporting entry within theVarMeasReportListfor thismeasId;3> stop the periodical reporting timer for thismeasId, if running;NOTE 1: Void.2> ifreportTypeis set toperiodicaland if a (first) measurement result is available:3> include a measurement reporting entry within theVarMeasReportListfor thismeasId;3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> if the correspondingreportConfigincludesmeasRSSI-ReportConfig:4> initiate the measurement reporting procedure as specified in 5.5.5 immediately when RSSI sample values are reported by the physical layer after the first L1 measurement duration;3> else if the correspondingreportConfigincludes theul-DelayValueConfig:4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first measurement result is provided from lower layers of the associated DRB identity;3> else if the correspondingreportConfigincludes theul-ExcessDelayConfig:4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first measurement result is provided from lower layers of the associated DRB identity(ies) according to the configured threshold per DRB identity(ies);3> else if thereportAmountexceeds 1:4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell or for the serving L2 U2N Relay UE (if the UE is a L2 U2N Remote UE);3> else (i.e. thereportAmountis equal to 1):4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell and for the strongest cell among the applicable cells, or for the NR SpCell and for the strongest L2 U2N Relay UEs among the applicable L2 U2N Relay UEs; or initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the serving L2 U2N Relay UE and for the strongest cell among the applicable cells (if the UE is a L2 U2N Remote UE);2> if, in case the correspondingreportConfigconcerns the reporting for NR sidelink communication / discovery,reportTypeis set toperiodicaland if a (first) measurement result is available:3> include a measurement reporting entry within theVarMeasReportListfor thismeasId;3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell and CBR measurement results become available;2> if thereportTypeis set tocli-EventTriggeredand if the entry condition applicable for this event, i.e. the event corresponding with theeventIdof the correspondingreportConfigwithinVarMeasConfig, is fulfilled for one or more applicable CLI measurement resources for all measurements after layer 3 filtering taken duringtimeToTriggerdefined for this event within theVarMeasConfig, while theVarMeasReportListdoes not include a measurement reporting entry for thismeasId(a first CLI measurement resource triggers the event):3> include a measurement reporting entry within theVarMeasReportListfor thismeasId;3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> include the concerned CLI measurement resource(s) in thecli-TriggeredListdefined within theVarMeasReportListfor thismeasId;3> initiate the measurement reporting procedure, as specified in 5.5.5;2> else if thereportTypeis set tocli-EventTriggeredand if the entry condition applicable for this event, i.e. the event corresponding with theeventIdof the correspondingreportConfigwithinVarMeasConfig, is fulfilled for one or more CLI measurement resources not included in thecli-TriggeredListfor all measurements after layer 3 filtering taken duringtimeToTriggerdefined for this event within theVarMeasConfig(a subsequent CLI measurement resource triggers the event):3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> include the concerned CLI measurement resource(s) in thecli-TriggeredListdefined within theVarMeasReportListfor thismeasId;3> initiate the measurement reporting procedure, as specified in 5.5.5;2> if thereportTypeis set tocli-EventTriggeredand if the leaving condition applicable for this event is fulfilled for one or more of the CLI measurement resources included in thecli-TriggeredListdefined within theVarMeasReportListfor thismeasIdfor all measurements after layer 3 filtering taken duringtimeToTriggerdefined within theVarMeasConfigfor this event:3> remove the concerned CLI measurement resource(s) in thecli-TriggeredListdefined within theVarMeasReportListfor thismeasId;3> ifreportOnLeaveis set totruefor the corresponding reporting configuration:4> initiate the measurement reporting procedure, as specified in 5.5.5;3> if thecli-TriggeredListdefined within theVarMeasReportListfor thismeasIdis empty:4> remove the measurement reporting entry within theVarMeasReportListfor thismeasId;4> stop the periodical reporting timer for this measId, if running;2> ifreportTypeis set tocli-Periodicaland if a (first) measurement result is available:3> include a measurement reporting entry within theVarMeasReportListfor thismeasId;3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for at least one CLI measurement resource;2> ifreportTypeis set torxTxPeriodicaland if a (first) measurement result is available:3> include a measurement reporting entry within theVarMeasReportListfor thismeasId;3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> initiate the measurement reporting procedure, as specified in 5.5.5;2> upon expiry of the periodical reporting timer for thismeasId:3> initiate the measurement reporting procedure, as specified in 5.5.5.2> if the correspondingreportConfigincludes areportTypeis set toreportSFTD:3> if the correspondingmeasObjectconcerns NR:4> if thedrx-SFTD-NeighMeasis included:5> if the quantity to be reported becomes available for each requested pair of PCell and NR cell:6> stop timer T322;6> initiate the measurement reporting procedure, as specified in 5.5.5;4> else5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for each requested pair of PCell and NR cell or the maximal measurement reporting delay as specified in TS 38.133

[0014] ;3> else if the correspondingmeasObjectconcerns E-UTRA:4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the pair of PCell and E-UTRA PSCell or the maximal measurement reporting delay as specified in TS 38.133

[0014] ;2> ifreportTypeis set toreportCGI:3> if the UE acquired theSIB1orSystemInformationBlockType1for the requested cell; or3> if the UE detects that the requested NR cell is not transmittingSIB1(see TS 38.213

[0013] , clause 13):4> stop timer T321;4> include a measurement reporting entry within theVarMeasReportListfor thismeasId;4> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;4> initiate the measurement reporting procedure, as specified in 5.5.5;2> upon the expiry of T321 for thismeasId:3> include a measurement reporting entry within theVarMeasReportListfor thismeasId;3> set thenumberOfReportsSentdefined within theVarMeasReportListfor thismeasIdto 0;3> initiate the measurement reporting procedure, as specified in 5.5.5.2> upon the expiry of T322 for thismeasId:3> initiate the measurement reporting procedure, as specified in 5.5.5.;

[0140] 5.5.4.2 Event A1 (Serving becomes better than threshold)The UE shall:1> consider the entering condition for this event to be satisfied when condition A1-1, as specified below, is fulfilled;1> consider the leaving condition for this event to be satisfied when condition A1-2, as specified below, is fulfilled;1> for this measurement, consider the NR serving cell corresponding to the associatedmeasObjectNRassociated with this event.Inequality A1-1 (Entering condition)Ms - Hys > ThreshInequality A1-2 (Leaving condition)Ms + Hys < ThreshThe variables in the formula are defined as follows:Msis the measurement result of the serving cell, not taking into account any offsets.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigNRfor this event).Threshis the threshold parameter for this event (i.e.a1-Thresholdas defined withinreportConfigNRfor this event).Msis expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.Hysis expressed in dB.Threshis expressed in the same unit asMs.5.5.4.3 Event A2 (Serving becomes worse than threshold)The UE shall:1> consider the entering condition for this event to be satisfied when condition A2-1, as specified below, is fulfilled;1> consider the leaving condition for this event to be satisfied when condition A2-2, as specified below, is fulfilled;1> for this measurement, consider the serving cell indicated by themeasObjectNRassociated to this event.Inequality A2-1 (Entering condition)Ms + Hys < ThreshInequality A2-2 (Leaving condition)Ms - Hys > ThreshThe variables in the formula are defined as follows:Msis the measurement result of the serving cell, not taking into account any offsets.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigNRfor this event).Threshis the threshold parameter for this event (i.e.a2-Thresholdas defined withinreportConfigNRfor this event).Msis expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.Hysis expressed in dB.Threshis expressed in the same unit asMs.5.5.4.4 Event A3 (Neighbour becomes offset better than SpCell)The UE shall:1> consider the entering condition for this event to be satisfied when condition A3-1, as specified below, is fulfilled;1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified below, is fulfilled;1> use the SpCell forMp,Ofp and Ocp.NOTE 1: The cell(s) that triggers the event has reference signals indicated in themeasObjectNRassociated to this event which may be different from the NR SpCellmeasObjectNR.Inequality A3-1 (Entering condition)Mn + Ofn + Ocn - Hys > Mp + Ofp + Ocp + OffInequality A3-2 (Leaving condition)Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + OffThe variables in the formula are defined as follows:Mnis the measurement result of the neighbouring cell, not taking into account any offsets.Ofnis the measurement object specific offset of the reference signal of the neighbour cell (i.e.offsetMOas defined withinmeasObjectNRcorresponding to the neighbour cell).Ocnis the cell specific offset of the neighbour cell (i.e.cellIndividualOffsetas defined withinmeasObjectNRcorresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.Mpis the measurement result of the SpCell, not taking into account any offsets.Ofpis the measurement object specific offset of the SpCell (i.e.offsetMOas defined withinmeasObjectNRcorresponding to the SpCell).Ocpis the cell specific offset of the SpCell (i.e.cellIndividualOffsetas defined withinmeasObjectNRcorresponding to the SpCell), and is set to zero if not configured for the SpCell.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigNRfor this event).Offis the offset parameter for this event (i.e.a3-Offsetas defined withinreportConfigNRfor this event).Mn, Mpare expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.Ofn,Ocn,Ofp,Ocp,Hys,Offare expressed in dB.NOTE 2: The definition of Event A3 also applies to CondEvent A3.5.5.4.5 Event A4 (Neighbour becomes better than threshold)The UE shall:1> consider the entering condition for this event to be satisfied when condition A4-1, as specified below, is fulfilled;1> consider the leaving condition for this event to be satisfied when condition A4-2, as specified below, is fulfilled.Inequality A4-1 (Entering condition)Mn + Ofn + Ocn - Hys > ThreshInequality A4-2 (Leaving condition)Mn + Ofn + Ocn + Hys < ThreshThe variables in the formula are defined as follows:Mnis the measurement result of the neighbouring cell, not taking into account any offsets.Ofnis the measurement object specific offset of the neighbour cell (i.e.offsetMOas defined withinmeasObjectNRcorresponding to the neighbour cell).Ocnis the measurement object specific offset of the neighbour cell (i.e.cellIndividualOffsetas defined withinmeasObjectNRcorresponding to the neighbour cell), and set to zero if not configured for the neighbour cell.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigNRfor this event).Threshis the threshold parameter for this event (i.e.a4-Thresholdas defined withinreportConfigNRfor this event).Mnis expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.Ofn, Ocn, Hysare expressed in dB.Threshis expressed in the same unit asMn.NOTE: The definition of Event A4 also applies to CondEvent A4.5.5.4.6 Event A5 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2)The UE shall:1> consider the entering condition for this event to be satisfied when both condition A5-1 and condition A5-2, as specified below, are fulfilled;1> consider the leaving condition for this event to be satisfied when condition A5-3 or condition A5-4, i.e.at least one of the two, as specified below, is fulfilled;1> use the SpCell forMp.NOTE 1: The parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in themeasObjectNRassociated to the event which may be different from themeasObjectNRof the NR SpCell.Inequality A5-1 (Entering condition 1)Mp + Hys < Thresh1Inequality A5-2 (Entering condition 2)Mn + Ofn + Ocn - Hys > Thresh2Inequality A5-3 (Leaving condition 1)Mp - Hys > Thresh1Inequality A5-4 (Leaving condition 2)Mn + Ofn + Ocn + Hys < Thresh2The variables in the formula are defined as follows:Mpis the measurement result of the NR SpCell, not taking into account any offsets.Mnis the measurement result of the neighbouring cell, not taking into account any offsets.Ofnis the measurement object specific offset of the neighbour cell (i.e.offsetMOas defined withinmeasObjectNRcorresponding to the neighbour cell).Ocnis the cell specific offset of the neighbour cell (i.e.cellIndividualOffsetas defined withinmeasObjectNRcorresponding to the neighbour cell), and set to zero if not configured for the neighbour cell.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigNRfor this event).Thresh1is the threshold parameter for this event (i.e.a5-Threshold1as defined withinreportConfigNRfor this event).Thresh2is the threshold parameter for this event (i.e.a5-Threshold2as defined withinreportConfigNRfor this event).Mn, Mpare expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.Ofn, Ocn, Hysare expressed in dB.Thresh1is expressed in the same unit asMp.Thresh2is expressed in the same unit asMn.NOTE 2: The definition of Event A5 also applies to CondEvent A5.

[0141] 5.5.4.7 Event A6 (Neighbour becomes offset better than SCell)The UE shall:1> consider the entering condition for this event to be satisfied when condition A6-1, as specified below, is fulfilled;1> consider the leaving condition for this event to be satisfied when condition A6-2, as specified below, is fulfilled;1> for this measurement, consider the (secondary) cell corresponding to themeasObjectNRassociated to this event to be the serving cell.NOTE: The reference signal(s) of the neighbour(s) and the reference signal(s) of the SCell are both indicated in the associatedmeasObjectNR.Inequality A6-1 (Entering condition)Mn + Ocn - Hys > Ms + Ocs + OffInequality A6-2 (Leaving condition)Mn + Ocn + Hys < Ms + Ocs + OffThe variables in the formula are defined as follows:Mnis the measurement result of the neighbouring cell, not taking into account any offsets.Ocnis the cell specific offset of the neighbour cell (i.e.cellIndividualOffsetas defined within the associatedmeasObjectNR), and set to zero if not configured for the neighbour cell.Msis the measurement result of the serving cell, not taking into account any offsets.Ocsis the cell specific offset of the serving cell (i.e.cellIndividualOffsetas defined within the associatedmeasObjectNR), and is set to zero if not configured for the serving cell.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigNRfor this event).Offis the offset parameter for this event (i.e.a6-Offsetas defined withinreportConfigNRfor this event).Mn, Msare expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.Ocn, Ocs, Hys, Offare expressed in dB.5.5.4.8 Event B1 (Inter RAT neighbour becomes better than threshold)The UE shall:1> consider the entering condition for this event to be satisfied when condition B1-1, as specified below, is fulfilled;1> consider the leaving condition for this event to be satisfied when condition B1-2, as specified below, is fulfilled.Inequality B1-1 (Entering condition)Mn + Ofn + Ocn - Hys > ThreshInequality B1-2 (Leaving condition)Mn + Ofn + Ocn + Hys < ThreshThe variables in the formula are defined as follows:Mnis the measurement result of the inter-RAT neighbour cell, not taking into account any offsets.Ofnis the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e.eutra-Q-OffsetRangeas defined within themeasObjectEUTRAcorresponding to the frequency of the neighbour inter-RAT cell,utra-FDD-Q-OffsetRangeas defined within themeasObjectUTRA-FDDcorresponding to the frequency of the neighbour inter-RAT cell).Ocnis the cell specific offset of the inter-RAT neighbour cell (i.e.cellIndividualOffsetas defined within themeasObjectEUTRAcorresponding to the neighbour inter-RAT cell), and set to zero if not configured for the neighbour cell.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigInterRATfor this event).Threshis the threshold parameter for this event (i.e.b1-ThresholdEUTRAas defined withinreportConfigInterRATfor this event,b1-ThresholdUTRA-FDDas defined for UTRA-FDD withinreportConfigInterRATfor this event).Mnis expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell.Ofn, Ocn, Hysare expressed in dB.Threshis expressed in the same unit asMn.5.5.4.9 Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2)The UE shall:1> consider the entering condition for this event to be satisfied when both condition B2-1 and condition B2-2, as specified below, are fulfilled;1> consider the leaving condition for this event to be satisfied when condition B2-3 or condition B2-4, i.e. at least one of the two, as specified below, is fulfilled;Inequality B2-1 (Entering condition 1)Mp + Hys < Thresh1Inequality B2-2 (Entering condition 2)Mn + Ofn + Ocn - Hys > Thresh2Inequality B2-3 (Leaving condition 1)Mp - Hys > Thresh1Inequality B2-4 (Leaving condition 2)Mn + Ofn + Ocn + Hys < Thresh2The variables in the formula are defined as follows:Mpis the measurement result of the PCell, not taking into account any offsets.Mnis the measurement result of the inter-RAT neighbour cell, not taking into account any offsets.Ofnis the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e.eutra-Q-OffsetRangeas defined within themeasObjectEUTRAcorresponding to the frequency of the inter-RAT neighbour cell,utra-FDD-Q-OffsetRangeas defined within themeasObjectUTRA-FDDcorresponding to the frequency of the neighbour inter-RAT cell).Ocnis the cell specific offset of the inter-RAT neighbour cell (i.e.cellIndividualOffsetas defined within themeasObjectEUTRAcorresponding to the neighbour inter-RAT cell), and set to zero if not configured for the neighbour cell.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigInterRATfor this event).Thresh1is the threshold parameter for this event (i.e. b2-Threshold1as defined withinreportConfigInterRATfor this event).Thresh2is the threshold parameter for this event (i.e.b2-Threshold2EUTRAas defined withinreportConfigInterRATfor this event,b2-Threshold2UTRA-FDDas defined for UTRA-FDD withinreportConfigInterRATfor this event).Mpis expressed in dBm in case of RSRP, or in dB in case of RSRQ and SINR.Mnis expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbour cell.Ofn, Ocn, Hysare expressed in dB.Thresh1is expressed in the same unit asMp.Thresh2is expressed in the same unit asMn.5.5.4.10 Event I1 (Interference becomes higher than threshold)The UE shall:1> consider the entering condition for this event to be satisfied when condition I1-1, as specified below, is fulfilled;1> consider the leaving condition for this event to be satisfied when condition I1-2, as specified below, is fulfilled.Inequality I1-1 (Entering condition)Mi-Hys > ThreshInequality I1-2 (Leaving condition)Mi+ Hys < ThreshThe variables in the formula are defined as follows:Miis the measurement result of the interference, not taking into account any offsets.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigNRfor this event).Threshis the threshold parameter for this event (i.e.i1-Thresholdas defined withinreportConfigNRfor this event).Mi, Threshare expressed in dBm.Hysis expressed in dB.5.5.4.11 Event C1 (The NR sidelink channel busy ratio is above a threshold)The UE shall:1> consider the entering condition for this event to be satisfied when condition C1-1, as specified below, is fulfilled;1> consider the leaving condition for this event to be satisfied when condition C1-2, as specified below, is fulfilled;Inequality C1-1 (Entering condition)Ms-Hys > ThreshInequality C1-2 (Leaving condition)Ms+Hys < ThreshThe variables in the formula are defined as follows:Msis the measurement result of channel busy ratio of the transmission resource pool, not taking into account any offsets.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigNR-SLfor this event).Threshis the threshold parameter for this event (i.e.c1-Thresholdas defined withinreportConfigNR-SLfor this event).Msis expressed in decimal from 0 to 1 in steps of 0.01.Hysis expressed is in the same unit asMs.Threshis expressed in the same unit asMs.

[0142] 5.5.4.12 Event C2 (The NR sidelink channel busy ratio is below a threshold)The UE shall:1> consider the entering condition for this event to be satisfied when condition C2-1, as specified below, is fulfilled;1> consider the leaving condition for this event to be satisfied when condition C2-2, as specified below, is fulfilled;Inequality C2-1 (Entering condition)Ms+Hys<ThreshInequality C2-2 (Leaving condition)Ms-Hys>ThreshThe variables in the formula are defined as follows:Msis the measurement result of channel busy ratio of the transmission resource pool, not taking into account any offsets.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigNR-SLfor this event).Threshis the threshold parameter for this event (i.e.c2-Thresholdas defined withinreportConfigNR-SLfor this event).Msis expressed in decimal from 0 to 1 in steps of 0.01.Hysis expressed is in the same unit asMs.Threshis expressed in the same unit asMs.5.5.4.13 Void5.5.4.14 Void5.5.4.15 Event D1 (Distance between UE and referenceLocation1 is above threshold1 and distance between UE and referenceLocation2 is below threshold2)The UE shall:1> consider the entering condition for this event to be satisfied when both condition D1-1 and condition D1-2, as specified below, are fulfilled;1> consider the leaving condition for this event to be satisfied when condition D1-3 or condition D1-4, i.e. at least one of the two, as specified below, are fulfilled;Inequality D1-1 (Entering condition 1)Ml1-Hys>Thresh1Inequality D1-2 (Entering condition 2)Ml2+Hys<Thresh2Inequality D1-3 (Leaving condition 1)Ml1+Hys<Thresh1Inequality D1-4 (Leaving condition 2)Ml2-Hys>Thresh2The variables in the formula are defined as follows:Ml1is the UE location, represented by the distance between UE and a reference location parameter for this event (i.e.referenceLocation1as defined withinreportConfigNRfor this event), not taking into account any offsets.Ml2is the UE location, represented by the distance between UE and a reference location parameter for this event (i.e.referenceLocation2as defined withinreportConfigNRfor this event), not taking into account any offsets.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigNRfor this event).Thresh1is the threshold for this event defined as a distance, configured with parameterdistanceThreshFromReference1,from a reference location configured with parameterreferenceLocation1withinreportConfigNRfor this event.Thresh2is the threshold for this event defined as a distance, configured with parameterdistanceThreshFromReference2,from a reference location configured with parameterreferenceLocation2withinreportConfigNRfor this event.Ml1is expressed in meters.Ml2is expressed in the same unit asMl1.Hysis expressed in the same unit asMl1.Thresh1is expressed in the same unit asMl1.Thresh2is expressed in the same unit asMl1.NOTE: The definition of Event D1 also applies to CondEvent D1.5.5.4.16 CondEvent T1 (Time measured at UE is within a duration from threshold)The UE shall:1> consider the entering condition for this event to be satisfied when condition T1-1, as specified below, is fulfilled;1> consider the leaving condition for this event to be satisfied when condition T1-2, as specified below, is fulfilled;Inequality T1-1 (Entering condition)Mt>Thresh1Inequality T1-2 (Leaving condition)Mt>Thresh1+DurationThe variables in the formula are defined as follows:Mtis the time measured at UE.Thresh1is the threshold parameter for this event (i.e.t1-Thresholdas defined withinreportConfigNRfor this event).Durationis the duration parameter for this event (i.e.durationas defined withinreportConfigNRfor this event).Mtis expressed inms.Thresh1is expressed in the same unit asMt.Durationis expressed in the same unit asMt.5.5.4.17 Event X1 (Serving L2 U2N Relay UE becomes worse than threshold1 and NR Cell becomes better than threshold2)The UE shall:1> consider the entering condition for this event to be satisfied when both condition X1-1 and condition X1-2, as specified below, are fulfilled;1> consider the leaving condition for this event to be satisfied when condition X1-3 or condition X1-4, i.e. at least one of the two, as specified below, is fulfilled;Inequality X1-1 (Entering condition 1)Mr + Hys < Thresh1Inequality X1-2 (Entering condition 2)Mn + Ofn + Ocn - Hys > Thresh2Inequality X1-3 (Leaving condition 1)Mr - Hys > Thresh1Inequality X1-4 (Leaving condition 2)Mn + Ofn + Ocn + Hys < Thresh2The variables in the formula are defined as follows:Mris the measurement result of the serving L2 U2N Relay UE, not taking into account any offsets.Mnis the measurement result of the NR cell, not taking into account any offsets.Ofnis the measurement object specific offset of the reference signal of the NR cell (i.e.offsetMOas defined withinmeasObjectNRcorresponding to the NR cell).Ocnis the cell specific offset of the NR cell (i.e.cellIndividualOffsetas defined withinmeasObjectNRcorresponding to the frequency of the NR cell), and set to zero if not configured for the cell.Hysis the hysteresis parameter for this event.Thresh1is the threshold parameter for this event (i.e.x1-Threshold1-Relayas defined withinreportConfigNRfor this event).Thresh2is the threshold parameter for this event (i.e.x1-Threshold2as defined withinreportConfigNRfor this event).Mris expressed in dBm.Mnis expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.Ofn, Ocn, Hysare expressed in dB.Thresh1is expressed in the same unit asMr.Thresh2is expressed in the same unit asMn.5.5.4.18 Event X2 (Serving L2 U2N Relay UE becomes worse than threshold)The UE shall:1> consider the entering condition for this event to be satisfied when condition X2-1, as specified below, is fulfilled;1> consider the leaving condition for this event to be satisfied when condition X2-2, as specified below, is fulfilled;Inequality X2-1 (Entering condition)Mr + Hys < ThreshInequality X2-2 (Leaving condition)Mr - Hys > ThreshThe variables in the formula are defined as follows:Mris the measurement result of the serving L2 U2N Relay UE, not taking into account any offsets.Hysis the hysteresis parameter for this event.Threshis the threshold parameter for this event (i.e.x2-Threshold-Relayas defined withinreportConfigNRfor this event).Mris expressed in dBm.Hysare expressed in dB.Threshis expressed in the same unit asMr.5.5.4.19 Event Y1 (PCell becomes worse than threshold1 and candidate L2 U2N Relay UE becomes better than threshold2)The UE shall:1> consider the entering condition for this event to be satisfied when both condition Y1-1 and condition Y1-2, as specified below, are fulfilled;1> consider the leaving condition for this event to be satisfied when condition Y1-3 or condition Y1-4, i.e. at least one of the two, as specified below, is fulfilled;Inequality Y1-1 (Entering condition 1)Mp + Hys < Thresh1Inequality Y1-2 (Entering condition 2)Mr- Hys > Thresh2Inequality Y1-3 (Leaving condition 1)Mp - Hys > Thresh1Inequality Y1-4 (Leaving condition 2)Mr + Hys < Thresh2The variables in the formula are defined as follows:Mpis the measurement result of the PCell, not taking into account any offsets.Mris the measurement result of the candidate L2 U2N Relay UE, not taking into account any offsets.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigInterRATfor this event).Thresh1is the threshold parameter for this event (i.e.y1-Threshold1as defined withinreportConfigInterRATfor this event).Thresh2is the threshold parameter for this event (i.e.y1-Threshold2-Relayas defined withinreportConfigInterRATfor this event).Mpis expressed in dBm in case of RSRP, or in dB in case of RSRQ and SINR.Mris expressed in dBm or dB, depending on the measurement quantity of candidate L2 U2N Relay UE.Hysare expressed in dB.Thresh1is expressed in the same unit asMp.Thresh2is expressed in the same unit asMr.5.5.4.20 Event Y2 (Candidate L2 U2N Relay UE becomes better than threshold)The UE shall:1> consider the entering condition for this event to be satisfied when condition Y2-1, as specified below, is fulfilled;1> consider the leaving condition for this event to be satisfied when condition Y2-2, as specified below, is fulfilled;Inequality Y2-1 (Entering condition)Mr- Hys > Thresh2Inequality Y2-2 (Leaving condition)Mr + Hys < Thresh2The variables in the formula are defined as follows:Mris the measurement result of the candidate L2 U2N Relay UE, not taking into account any offsets.Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinreportConfigInterRATfor this event).Threshis the threshold parameter for this event (i.e.y2-Threshold-Relayas defined withinreportConfigInterRATfor this event).Mris expressed in dBm or dB, depending on the measurement quantity of candidate L2 U2N Relay UE.Hysare expressed in dB.Threshis expressed in the same unit asMr.

[0143] In step (525), the terminal (501) may include the measurement results (measResults) for the measId for which the measurement reporting procedure was triggered in step (520) in a measurement result message (MeasurementReport) and transmit it to the base station (502). According to various embodiments of the present disclosure, the terminal (501) may first measure the E-UTRA carrier frequency x, and the measurement reporting procedure may be triggered in the measId associated therewith (e.g., measId = 1, measObjectId = 1, reportConfigId = 1).

[0144] In step (526), ​​the terminal (503) may include the measurement results (measResults) for the measId for which the measurement reporting procedure was triggered in step (521) in a measurement result message (MeasurementReport) and transmit it to the base station (502). On the other hand, according to various embodiments of the present disclosure, the terminal (503) may first measure the E-UTRA carrier frequency z, and the measurement reporting procedure may be triggered in the measId associated therewith (e.g., measId = 3, measObjectId = 3, reportConfigId = 3).

[0145] According to one embodiment, at this time, each terminal (501, 503) can store beam measurement information and cell measurement results in the measurement results as follows. At this time, for a description of the operation for each terminal (501, 503) to store beam measurement information and cell measurement results in the measurement results, reference may be made to the document of 3GPP Release 17 TS 38.311.

[0146] 5.5.5.2 Reporting of beam measurement informationFor beam measurement information to be included in a measurement report the UE shall:1> ifreportTypeis set toeventTriggered:2> consider the trigger quantity as the sorting quantity if available, otherwise RSRP as sorting quantity if available, otherwise RSRQ as sorting quantity if available, otherwise SINR as sorting quantity;1> ifreportTypeis set toperiodical:2> if a single reporting quantity is set totrueinreportQuantityRS-Indexes;3> consider the configured single quantity as the sorting quantity;2> else:3> ifrsrpis set totrue;4> consider RSRP as the sorting quantity;3> else:4> consider RSRQ as the sorting quantity;1> setrsIndexResultsto include up tomaxNrofRS-IndexesToReportSS / PBCH block indexes or CSI-RS indexes in order of decreasing sorting quantity as follows:2> if the measurement information to be included is based on SS / PBCH block:3> include withinresultsSSB-Indexesthe index associated to the best beam for that SS / PBCH block sorting quantity and ifabsThreshSS-BlocksConsolidationis included in theVarMeasConfigfor themeasObjectassociated to the cell for which beams are to be reported, the remaining beams whose sorting quantity is aboveabsThreshSS-BlocksConsolidation;3> ifincludeBeamMeasurementsis set totrue, include the SS / PBCH based measurement results for the quantities inreportQuantityRS-Indexesfor each SS / PBCH block index;2> else if the beam measurement information to be included is based on CSI-RS:3> include withinresultsCSI-RS-Indexesthe index associated to the best beam for that CSI-RS sorting quantity and, ifabsThreshCSI-RS-Consolidationis included in theVarMeasConfigfor themeasObjectassociated to the cell for which beams are to be reported, the remaining beams whose sorting quantity is aboveabsThreshCSI-RS-Consolidation;3> ifincludeBeamMeasurementsis set totrue, include the CSI-RS based measurement results for the quantities inreportQuantityRS-Indexesfor each CSI-RS index.5.5.5.3 Sorting of cell measurement resultsThe UE shall determine the sorting quantity according to parameters of thereportConfigassociated with themeasIdthat triggered the reporting:1> if thereportTypeis set toeventTriggered:2> for an NR cell, consider the quantity used in theaN-Threshold(foreventA1,eventA2andeventA4) or in thea5-Threshold2(foreventA5) or in theaN-Offset(foreventA3andeventA6) as the sorting quantity;2> for an E-UTRA cell, consider the quantity used in thebN-ThresholdEUTRAas the sorting quantity;2> for an UTRA-FDD cell, consider the quantity used in thebN-ThresholdUTRA-FDDas the sorting quantity;2> for a candidate L2 U2N Relay UE, consider the yN-Threshold2-Relayas the sorting quantity;1> if thereportTypeis set toperiodical:2> determine the sorting quantity according toreportQuantityCellfor an NR cell, and according toreportQuantityfor an E-UTRA cell, as below:3> if a single quantity is set totrue:4> consider this quantity as the sorting quantity;3> else:4> ifrsrpis set totrue;5> consider RSRP as the sorting quantity;4> else:5> consider RSRQ as the sorting quantity;2> determine the sorting quantity according toreportQuantityUTRA-FDDfor UTRA-FDD cell, as below:3> if a single quantity is set totrue:4> consider this quantity as the sorting quantity;3> else:4> consider RSCP as the sorting quantity.2> for a candidate L2 U2N Relay UE, consider thereportQuantityRelayas the sorting quantity;

[0147] According to one embodiment, the specific procedure for each terminal (501, 503) to include the measurement results (MeasResults) in the measurement report message may be as follows. At this time, the description of the operation for each terminal (501, 503) to include the measurement results (MeasResults) in the measurement report message may be referenced to the document of 3GPP Release 17 TS 38.311.

[0148] 1> set themeasIdto the measurement identity that triggered the measurement reporting;1> for each serving cell configured withservingCellMO:2> if thereportConfigassociated with themeasIdthat triggered the measurement reporting includesrsType:3> if the serving cell measurements based on thersTypeincluded in thereportConfigthat triggered the measurement report are available:4> set themeasResultServingCellwithinmeasResultServingMOListto include RSRP, RSRQ and the available SINR of the serving cell, derived based on thersTypeincluded in thereportConfigthat triggered the measurement report;2> else:3> if SSB based serving cell measurements are available:4> set themeasResultServingCellwithinmeasResultServingMOListto include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB;3> else if CSI-RS based serving cell measurements are available:4> set themeasResultServingCellwithinmeasResultServingMOListto include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS;1> set theservCellIdwithinmeasResultServingMOListto include each NR serving cell that is configured withservingCellMO, if any;1> if thereportConfigassociated with themeasIdthat triggered the measurement reporting includesreportQuantityRS-IndexesandmaxNrofRS-IndexesToReport:2> for each serving cell configured withservingCellMO, include beam measurement information according to the associatedreportConfigas described in 5.5.5.2;1> if thereportConfigassociated with themeasIdthat triggered the measurement reporting includesreportAddNeighMeas:2> for eachmeasObjectIdreferenced in themeasIdListwhich is also referenced withservingCellMO, other than themeasObjectIdcorresponding with themeasIdthat triggered the measurement reporting:3> if themeasObjectNRindicated by theservingCellMOincludes the RS resource configuration corresponding to thersTypeindicated in thereportConfig:4> set themeasResultBestNeighCellwithinmeasResultServingMOListto include thephysCellIdand the available measurement quantities based on thereportQuantityCellandrsTypeindicated inreportConfigof the non-serving cell corresponding to the concernedmeasObjectNRwith the highest measured RSRP if RSRP measurement results are available for cells corresponding to thismeasObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to thismeasObjectNR, otherwise with the highest measured SINR;4> if thereportConfigassociated with themeasIdthat triggered the measurement reporting includesreportQuantityRS-IndexesandmaxNrofRS-IndexesToReport:5> for each best non-serving cell included in the measurement report:6> include beam measurement information according to the associatedreportConfigas described in 5.5.5.2;1> if thereportConfigassociated with themeasIdthat triggered the measurement reporting is set toeventTriggeredandeventIDis set toeventA3, oreventA4, oreventA5, oreventB1, oreventB2:2> if the UE is in NE-DC and the measurement configuration that triggered this measurement report is associated with the MCG:3> set themeasResultServFreqListEUTRA-SCGto include an entry for each E-UTRA SCG serving frequency with the following:4> includecarrierFreqof the E-UTRA serving frequency;4> set themeasResultServingCellto include the available measurement quantities that the UE is configured to measure by the measurement configuration associated with the SCG;4> ifreportConfigassociated with themeasIdthat triggered the measurement reporting includesreportAddNeighMeas:5> set themeasResultServFreqListEUTRA-SCGto include withinmeasResultBestNeighCellthe quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;1> ifreportConfigassociated with themeasIdthat triggered the measurement reporting is set toeventTriggeredandeventIDis set toeventA3, oreventA4, oreventA5:2> if the UE is in NR-DC and the measurement configuration that triggered this measurement report is associated with the MCG:3> set themeasResultServFreqListNR-SCGto include for each NR SCG serving cell that is configured withservingCellMO, if any, the following:4> if thereportConfigassociated with themeasIdthat triggered the measurement reporting includesrsType:5> if the serving cell measurements based on thersTypeincluded in thereportConfigthat triggered the measurement report are available according to the measurement configuration associated with the SCG:6> set themeasResultServingCellwithinmeasResultServFreqListNR-SCGto include RSRP, RSRQ and the available SINR of the serving cell, derived based on thersTypeincluded in thereportConfigthat triggered the measurement report;4> else:5> if SSB based serving cell measurements are available according to the measurement configuration associated with the SCG:6> set themeasResultServingCellwithinmeasResultServFreqListNR-SCGto include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB;5> else if CSI-RS based serving cell measurements are available according to the measurement configuration associated with the SCG:6> set themeasResultServingCellwithinmeasResultServFreqListNR-SCGto include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS;4> if results for the serving cell derived based on SSB are included:5> include thessbFrequencyto the value indicated by ssbFrequency as included in theMeasObjectNRof the serving cell;4> if results for the serving cell derived based on CSI-RS are included:5> include therefFreqCSI-RSto the value indicated byrefFreqCSI-RSas included in theMeasObjectNRof the serving cell;4> if thereportConfigassociated with themeasIdthat triggered the measurement reporting includesreportQuantityRS-IndexesandmaxNrofRS-IndexesToReport:5> for each serving cell configured withservingCellMO, include beam measurement information according to the associatedreportConfigas described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG;4> ifreportConfigassociated with themeasIdthat triggered the measurement reporting includesreportAddNeighMeas:5> if themeasObjectNRindicated by theservingCellMOincludes the RS resource configuration corresponding to thersTypeindicated in thereportConfig:6> set themeasResultNeighCellListNRwithinmeasResultServFreqListNR-SCGto include one entry with thephysCellIdand the available measurement quantities based on thereportQuantityCellandrsTypeindicated inreportConfigof the non-serving cell corresponding to the concernedmeasObjectNRwith the highest measured RSRP if RSRP measurement results are available for cells corresponding to thismeasObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to thismeasObjectNR, otherwise with the highest measured SINR, where availability is considered according to the measurement configuration associated with the SCG;7> if thereportConfigassociated with themeasIdthat triggered the measurement reporting includesreportQuantityRS-IndexesandmaxNrofRS-IndexesToReport:8> for each best non-serving cell included in the measurement report:9> include beam measurement information according to the associatedreportConfigas described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG;1> if themeasRSSI-ReportConfigis configured within the correspondingreportConfigfor thismeasId:2> set therssi-Resultto the linear average of sample value(s) provided by lower layers in thereportInterval;2> set thechannelOccupancyto the rounded percentage of sample values which are beyond thechannelOccupancyThresholdwithin all the sample values in thereportInterval;1> if the UE is acting as L2 U2N Remote UE:2> set thesl-MeasResultServingRelayin accordance with the following:3> set thecellIdentityto include thecellAccessRelatedInfocontained in the discovery message received from the serving L2 U2N Relay UE;3> set thesl-RelayUE-Identityto include the Source L2 ID of the serving L2 U2N Relay;3> set thesl-MeasResultto include the SL-RSRP of the serving L2 U2N Relay UE;NOTE 1: In case of no data transmission from L2 U2N Relay UE to L2 U2N Remote UE, it is left to UE implementation whether to use SL-RSRP or SD-RSRP when setting thesl-MeasResultServingRelayof the serving L2 U2N Relay UE.1> if there is at least one applicable neighbouring cell or candidate L2 U2N Relay UE to report:2> if thereportTypeis set toeventTriggeredorperiodical:3> if the measurement report concerns the candidate L2 U2N Relay UE:4> set thesl-MeasResultsCandRelayinmeasResultNeighCellsto include the best candidate L2 U2N Relay UEs up tomaxReportCellsin accordance with the following:5> if thereportTypeis set toeventTriggered:6> include the L2 U2N Relay UEs included in therelaysTriggeredListas defined within theVarMeasReportListfor thismeasId;5> else:6> include the applicable L2 U2N Relay UEs for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;5> for each L2 U2N Relay UE that is included in thesl-MeasResultsCandRelay:6> set thecellIdentityto include thecellAccessRelatedInfocontained in the discovery message received from the concerned L2 U2N Relay UE;6> set thesl-RelayUE-Identityto include the Source L2 ID of the concerned L2 U2N Relay UE;6> set thesl-MeasResultto include the SD-RSRP of the concerned L2 U2N Relay UE;5> for each included L2 U2N Relay UE, include the layer 3 filtered measured results in accordance with thereportConfigfor thismeasId, ordered as follows:6> set thesl-MeasResultto include the quantity(ies) indicated in thereportQuantityRelaywithin the concernedreportConfigRelayin decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best L2 U2N Relay UE is included first;3> else:4> set themeasResultNeighCellsto include the best neighbouring cells up tomaxReportCellsin accordance with the following:5> if thereportTypeis set toeventTriggeredandeventIdis not set toeventD1:6> include the cells included in thecellsTriggeredListas defined within theVarMeasReportListfor thismeasId;5> else:6> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;5> for each cell that is included in themeasResultNeighCells, include thephysCellId;5> if the reportType is set to eventTriggered or periodical:6> for each included cell, include the layer 3 filtered measured results in accordance with thereportConfigfor thismeasId, ordered as follows:7> if themeasObjectassociated with thismeasIdconcerns NR:8> ifrsTypein the associatedreportConfigis set tossb:9> setresultsSSB-Cellwithin themeasResultto include the SS / PBCH block based quantity(ies) indicated in thereportQuantityCellwithin the concernedreportConfig, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;9> ifreportQuantityRS-IndexesandmaxNrofRS-IndexesToReportare configured, include beam measurement information as described in 5.5.5.2;8> else ifrsTypein the associatedreportConfigis set tocsi-rs:9> setresultsCSI-RS-Cellwithin themeasResultto include the CSI-RS based quantity(ies) indicated in thereportQuantityCellwithin the concernedreportConfig, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;9> ifreportQuantityRS-IndexesandmaxNrofRS-IndexesToReportare configured, include beam measurement information as described in 5.5.5.2;7> if themeasObjectassociated with thismeasIdconcerns E-UTRA:8> set themeasResultto include the quantity(ies) indicated in thereportQuantitywithin the concernedreportConfigInterRATin decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;7> if themeasObjectassociated with thismeasIdconcerns UTRA-FDD and ifReportConfigInterRATincludes thereportQuantityUTRA-FDD:8> set themeasResultto include the quantity(ies) indicated in thereportQuantityUTRA-FDDwithin the concernedreportConfigInterRATin decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;2> else:3> if the cell indicated bycellForWhichToReportCGIis an NR cell:4> ifplmn-IdentityInfoListof thecgi-Infofor the concerned cell has been obtained:5> include theplmn-IdentityInfoListincludingplmn-IdentityList,trackingAreaCode(if available),trackingAreaList(if available), ranac(if available),cellIdentityandcellReservedForOperatorUsefor each entry of theplmn-IdentityInfoList;5> includefrequencyBandListif available;5> for eachPLMN-IdentityInfoinplmn-IdentityInfoList:6> if thegNB-ID-Lengthis broadcast:7> includegNB-ID-Length;4> ifnr-CGI-Reporting-NPNis supported by the UE andnpn-IdentityInfoListof thecgi-Infofor the concerned cell has been obtained:5> include thenpn-IdentityInfoListincludingnpn-IdentityList,trackingAreaCode,ranac(if available),cellIdentityandcellReservedForOperatorUsefor each entry of thenpn-IdentityInfoList;5> for eachNPN-IdentityInfoinNPN-IdentityInfoList:6> if thegNB-ID-Lengthis broadcast:7> includegNB-ID-Length;5> includecellReservedForOtherUseif available;4> else ifMIBindicates theSIB1is not broadcast:5> include thenoSIB1including thessb-SubcarrierOffsetandpdcch-ConfigSIB1obtained fromMIBof the concerned cell;3> if the cell indicated bycellForWhichToReportCGIis an E-UTRA cell:4> if all mandatory fields of thecgi-Info-EPCfor the concerned cell have been obtained:5> include in thecgi-Info-EPCthe fields broadcasted in E-UTRASystemInformationBlockType1associated to EPC;4> if the UE is E-UTRA / 5GC capable and all mandatory fields of thecgi-Info-5GCfor the concerned cell have been obtained:5> include in thecgi-Info-5GCthe fields broadcasted in E-UTRASystemInformationBlockType1associated to 5GC;4> if the mandatory present fields of thecgi-Infofor the cell indicated by thecellForWhichToReportCGIin the associatedmeasObjecthave been obtained:5> include thefreqBandIndicator;5> if the cell broadcasts themultiBandInfoList, include themultiBandInfoList;5> if the cell broadcasts thefreqBandIndicatorPriority, include thefreqBandIndicatorPriority;

[0149] 1> if the correspondingmeasObjectconcerns NR:2> if thereportSFTD-Measis set totruewithin the correspondingreportConfigNRfor thismeasId:3> set themeasResultSFTD-NRin accordance with the following:4> setsfn-OffsetResultandframeBoundaryOffsetResultto the measurement results provided by lower layers;4> if thereportRSRPis set totrue;5> setrsrp-Resultto the RSRP of the NR PSCell derived based on SSB;2> else if thereportSFTD-NeighMeasis included within the correspondingreportConfigNRfor thismeasId:3> for each applicable cell which measurement results are available, include an entry in themeasResultCellListSFTD-NRand set the contents as follows:4> setphysCellIdto the physical cell identity of the concerned NR neighbour cell.4> setsfn-OffsetResultandframeBoundaryOffsetResultto the measurement results provided by lower layers;4> if thereportRSRPis set totrue:5> setrsrp-Resultto the RSRP of the concerned cell derived based on SSB;1> else if the correspondingmeasObjectconcerns E-UTRA:2> if thereportSFTD-Measis set totruewithin the correspondingreportConfigInterRATfor thismeasId:3> set themeasResultSFTD-EUTRAin accordance with the following:4> setsfn-OffsetResultandframeBoundaryOffsetResultto the measurement results provided by lower layers;4> if thereportRSRPis set totrue;5> setrsrpResult-EUTRAto the RSRP of the EUTRA PSCell;1> if average uplink PDCP delay values are available:2> set theul-PDCP-DelayValueResultListto include the corresponding average uplink PDCP delay values;1> if PDCP excess delay measurements are available:2> set theul-PDCP-ExcessDelayResultListto include the corresponding PDCP excess delay measurements;1> if theincludeCommonLocationInfois configured in the correspondingreportConfigfor thismeasIdand detailed location information that has not been reported is available, set the content ofcommonLocationInfoof thelocationInfoas follows:2> include thelocationTimestamp;2> include thelocationCoordinate, if available;2> include thevelocityEstimate, if available;2> include thelocationError, if available;2> include thelocationSource, if available;2> if available, include thegnss-TOD-msec,1> if thecoarseLocationRequestis set totruein the correspondingreportConfigfor thismeasId:2> includecoarseLocationInfo,if available;1> if theincludeWLAN-Measis configured in the correspondingreportConfigfor thismeasId, set thewlan-LocationInfoof thelocationInfoin themeasResultsas follows:2> if available, include theLogMeasResultWLAN, in order of decreasing RSSI for WLAN APs;1> if theincludeBT-Measis configured in the correspondingreportConfigfor thismeasId, set theBT-LocationInfoof thelocationInfoin themeasResultsas follows:2> if available, include theLogMeasResultBT, in order of decreasing RSSI for Bluetooth beacons;1> if theincludeSensor-Measis configured in the correspondingreportConfigfor thismeasId, set thesensor-LocationInfoof thelocationInfoin themeasResultsas follows:2> if available, include thesensor-MeasurementInformation;2> if available, include thesensor-MotionInformation;1> if there is at least one applicable transmission resource pool for NR sidelink communication / discovery (formeasResultsSL):2> set themeasResultsListSLto include the CBR measurement results in accordance with the following:3> if thereportTypeis set toeventTriggered:4> include the transmission resource pools included in thepoolsTriggeredListas defined within theVarMeasReportListfor thismeasId;3> else:4> include the applicable transmission resource pools for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;3> if the correspondingmeasObjectconcerns NR sidelink communication / discovery, then for each transmission resource pool to be reported:4> set thesl-poolReportIdentityto the identity of this transmission resource pool;4> set thesl-CBR-ResultsNRto the CBR measurement results on PSSCH and PSCCH of this transmission resource pool provided by lower layers, if available;NOTE 1: Void.1> if there is at least one applicable CLI measurement resource to report:2> if thereportTypeis set tocli-EventTriggeredorcli-Periodical:3> set themeasResultCLIto include the most interfering SRS resources or most interfering CLI-RSSI resources up tomaxReportCLIin accordance with the following:4> if thereportTypeis set tocli-EventTriggered:5> if trigger quantity is set tosrs-RSRPi.e.i1-Thresholdis set tosrs-RSRP:6> include the SRS resource included in thecli-TriggeredListas defined within theVarMeasReportListfor thismeasId;5> if trigger quantity is set tocli-RSSIi.e.i1-Thresholdis set tocli-RSSI:6> include the CLI-RSSI resource included in thecli-TriggeredListas defined within theVarMeasReportListfor thismeasId;4> else:5> ifreportQuantityCLIis set tosrs-rsrp:6> include the applicable SRS resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;5> else:6> include the applicable CLI-RSSI resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;4> for each SRS resource that is included in themeasResultCLI:5> include thesrs-ResourceId;5> setsrs-RSRP-Resultto include the layer 3 filtered measured results in decreasing order, i.e. the most interfering SRS resource is included first;4> for each CLI-RSSI resource that is included in themeasResultCLI:5> include therssi-ResourceId;5> setcli-RSSI-Resultto include the layer 3 filtered measured results in decreasing order, i.e. the most interfering CLI-RSSI resource is included first;1> if there is at least one applicable UE Rx-Tx time difference measurement to report:2> setmeasResultRxTxTimeDiffto the latest measurement result;1> increment thenumberOfReportsSentas defined within theVarMeasReportListfor thismeasIdby 1;1> stop the periodical reporting timer, if running;1> if thenumberOfReportsSentas defined within theVarMeasReportListfor thismeasIdis less than thereportAmountas defined within the correspondingreportConfigfor thismeasId:2> start the periodical reporting timer with the value ofreportIntervalas defined within the correspondingreportConfigfor thismeasId;1> else:2> if thereportTypeis set toperiodicalorcli-PeriodicalorrxTxPeriodical:3> remove the entry within theVarMeasReportListfor thismeasId;3> remove thismeasIdfrom themeasIdListwithinVarMeasConfig;1> if the measurement reporting was configured by asl-ConfigDedicatedNRreceived within theRRCConnectionReconfiguration:2> submit theMeasurementReportmessage to lower layers for transmission via SRB1, embedded in E-UTRA RRC messageULInformationTransferIRATas specified TS 36.331

[0010] , clause 5.6.28;1> else if the UE is in (NG)EN-DC:2> if SRB3 is configured and the SCG is not deactivated:3> submit theMeasurementReportmessage via SRB3 to lower layers for transmission, upon which the procedure ends;2> else:3> submit theMeasurementReportmessage via E-UTRA embedded in E-UTRA RRC messageULInformationTransferMRDCas specified in TS 36.331

[0010] .1> else if the UE is in NR-DC:2> if the measurement configuration that triggered this measurement report is associated with the SCG:3> if SRB3 is configured and the SCG is not deactivated:4> submit theMeasurementReportmessage via SRB3 to lower layers for transmission, upon which the procedure ends;3> else:4> submit theMeasurementReportmessage via SRB1 embedded in NR RRC messageULInformationTransferMRDCas specified in5.7.2a.3;2> else:3> submit theMeasurementReportmessage via SRB1 to lower layers for transmission, upon which the procedure ends;1> else:2> submit theMeasurementReportmessage to lower layers for transmission, upon which the procedure ends.;

[0150] In steps (530, 531), the base station (502) may transmit a predetermined RRC message (e.g., MobilityFromNRCommand or an RRC disconnect message containing RedirectedCarrierInfo to move to a specific frequency) to move each terminal (501, 503) to a specific inter-RAT target cell based on the measurement result message received from each terminal (501, 503). For example, the base station (502) may move the terminal (501) to a target cell belonging to an E-UTRA carrier frequency x (step (530)), and may move the terminal (503) to a target cell belonging to an E-UTRA carrier frequency z (step (531)).

[0151] FIG. 6 illustrates a signal flow for a terminal to transmit a measurement result message to a base station in a next-generation mobile communication system according to various embodiments of the present invention.

[0152] According to various embodiments of the present disclosure, a terminal may sequentially measure one or more specific frequencies with priority according to a configuration of a base station. For example, if a specific service is supported on one or more frequencies, the base station may configure the terminal to first measure the frequency at which the specific service is best supported, in order to efficiently provide the specific service to the terminal. For example, if a VoLTE (Voice over LTE) service is supported on both E-UTRA frequency x and E-UTRA frequency y, but can be more efficiently provided on E-UTRA frequency x, the base station may configure measurement configuration information (measConfig) to first measure E-UTRA frequency x, then E-UTRA frequency y, and then measure the remaining frequencies according to the terminal implementation. According to various embodiments of the present disclosure, since a terminal according to a base station configuration measures E-UTRA frequency x first, a measurement reporting procedure may be first triggered from a measurement identifier (measId) associated with E-UTRA frequency x, and the terminal may transmit a measurement result message (MeasurementReport) for E-UTRA frequency x to the base station upon triggering. Accordingly, the base station may optimally provide a VoLTE service by moving the terminal to a cell belonging to E-UTRA frequency x by transmitting a predetermined RRC message (e.g., a handover message or an RRC disconnection message containing RedirectedCarrierInfo to move to a specific frequency) to the terminal.

[0153] Referring to FIG. 6, in step (605), the terminal (601) may establish an RRC connection with the NR base station (602) and be in RRC connected mode (RRC_CONNECTED).

[0154] In step (610), the terminal (601) may transmit a terminal capability information message (UECapabilityInformation) to the base station (602). The capability information message transmitted by the terminal may include at least one of the following information.

[0155] * Information on the ability to sequentially measure one or more measurement objects indicated by the base station.

[0156] - The above-described capability information may include at least one of per UE capability information or per frequency range capability information.

[0157] - The capability information described above may be limited to one or more RATs. For example, the capability information may apply only to NR frequencies and LTE frequencies, or only to NR frequencies or LTE frequencies, or only to NR frequencies, LTE frequencies, and 3G frequencies.

[0158] In step (615), the base station (602) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to the terminal (601). This may follow the above-described embodiment. Additionally, according to various embodiments of the present disclosure, the base station may include information in the measurement configuration information that configures the terminal to sequentially perform measurements by giving priority to specific measurement objects among the measurement objects, and the information and operation are specifically described. The above-described information may mean at least one of the following.

[0159] * RecommendedMeasObjectIdList: A list of MeasObjectIds to indicate measurement objects that the terminal should prioritize and sequentially measure among the measurement objects included in MeasObjectToAddModList.

[0160] - The RecommendedMeasObjectIdList may consist of at most X MeasObjectIds (where X is an integer value). For example, X may include 64, which is the maximum number of measurement objects that the base station can configure. In one embodiment, each MeasObjectId included in the RecommendedMeasObjectIdList may point to one of the MeasObjectIds configured in the MeasObjectToAddModList.

[0161] - The terminal can sequentially measure the measurement objects associated with the MeasObjectIds in the order of the MeasObjecIds included in the RecommendedMeasObjectIdList. For example, the terminal can first measure the measurement object associated with the first MeasObjectId included in the RecommendedMeasObjectIdList, and lastly measure the measurement object associated with the last MeasObjectId included in the RecommendedMeasObjectIdList.

[0162] - The base station can set a separate indicator so that the terminal can measure the measurement target according to the order of MeasObjectToAddModList, or can include RecommendedMeasObjectIdList but set its size to 0.

[0163] * RecommendedMeasIdList: A list of MeasIds to indicate measurement targets that the terminal should prioritize and sequentially measure among the measurement identifiers included in MeasIdToAddModList.

[0164] - RecommendedMeasIdList can consist of up to X MeasIds (where X is an integer value). For example, X can include 64, which is the maximum number of measurement identifiers that a base station can set.

[0165] - The terminal can sequentially measure the measurement objects associated with the MeasIds in the RecommendedMeasIdList in the order of the MeasIds. For example, the terminal can first measure the measurement object associated with the first MeasId included in the RecommendedMeasIdList, and lastly measure the measurement object associated with the last MeasId included in the RecommendedMeasIdList.

[0166] - Depending on one embodiment, the MeasIds included in the RecommendedMeasIdList may only include those MeasObjects associated with different ones.

[0167] * RecommendedMeasObjectList: MeasObject list to indicate measurement objects that the terminal should prioritize and sequentially measure.

[0168] - The terminal can sequentially measure measurement targets according to the order of the MeasObjects included in the RecommendedMeasObjectList. For example, the terminal can measure the first measurement target included in the RecommendedMeasObjectList first, and the last measurement target included in the RecommendedMeasObjectList last.

[0169] - In one embodiment, the base station may not include MeasObjects included in the RecommendedMeasObjectList in the MeasObjectToAddModList. This may have the advantage of not having to set the same information to the terminal.

[0170] - According to one embodiment, the MeasObject set in the RecommendedMeasObjectList may mean only some information among the MeasObjects set in the MeasObjectToAddModList. For example, only configuration information for indicating information related to frequency information may be included in the RecommendedMeasObjectList. For example, the above-described information may mean at least one of an Absolute Radio Frequency Channel Number (ARFCN), a Subcarrier Spacing, or a Measurement Reference Signal (SSB (synchronization signal block) or CSI (channel state information)-RS (reference signal)).

[0171] According to various embodiments, the above-described information may be separately signaled to the terminal for each frequency domain. Alternatively, the above-described information may be applied only to frequencies belonging to one or more specific RATs. According to various embodiments of the present disclosure, for convenience of explanation, the base station may configure the terminal to sequentially measure MeasObjectEUTRA x (E-UTRA carrier frequency x), MeasObjectEUTRA y (E-UTRA carrier frequency y), and MeasObjectEUTRA z (E-UTRA carrier frequency z), and the measurement order for the remaining measurement objects may be determined by the terminal implementation as in the above-described embodiment.

[0172] In step (620), the terminal (601) may perform measurement based on measurement setting information received from the base station (602). According to various embodiments of the present disclosure, the order in which the terminal (601) measures the set frequencies may be as follows.

[0173] - E-UTRA frequency x

[0174] - E-UTRA frequency y

[0175] - E-UTRA frequency z

[0176] - other frequencies

[0177] According to one embodiment, a specific measurement method may follow the embodiments described above.

[0178] In step (625), the terminal (601) can determine whether a condition for reporting a measurement result message (MeasurementReport) to the base station (602) is triggered based on the measurement result in step (620). This may follow the embodiments described above.

[0179] In step (625), the terminal (601) can transmit the measurement results (measResults) for the measId for which the measurement report procedure was triggered in step (625) to the base station (602) by including them in a measurement result message (MeasurementReport).

[0180] According to various embodiments of the present disclosure, the terminal (601) may first measure the E-UTRA carrier frequency x, and a measurement reporting procedure may be triggered in the measId associated therewith (e.g., measId = x, measObjectId = x, reportConfigId = x). At this time, a specific procedure in which the terminal (601) includes the measurement result (MeasResults) in the measurement report message may follow the embodiments described above. Of course, even if the terminal measures the E-UTRA carrier frequency x with priority, it does not necessarily mean that the measurement reporting procedure associated therewith is triggered. As in the embodiments described above, when the measurement reporting procedure associated with the measId is triggered, the terminal may include the measurement result in the measurement report message and transmit it to the base station.

[0181] In step (635), the base station (602) may transmit a predetermined RRC message (e.g., MobilityFromNRCommand or an RRC disconnect message containing RedirectedCarrierInfo to move to a specific frequency) to move the terminal (601) to a specific inter-RAT target cell based on the measurement result message received from the terminal (601). For example, the base station (602) may move the terminal (601) to a target cell belonging to an E-UTRA carrier frequency x, thereby optimally providing the voLTE service to the terminal.

[0182] According to one embodiment, when a terminal operates in NR SA (Standalone), the base station may configure the terminal to sequentially measure one or more specific frequencies with priority, as described above in the present disclosure. For example, when the terminal operates in MR-DC (Multi-RAT Dual Connectivity) or NR-DC, the base station may not be able to configure the above-described information according to the above-described information in the present disclosure. According to one embodiment, when configuring MR-DC or NR-DC for the terminal, the base station may explicitly release the information configured to sequentially measure one or more specific frequencies with priority, or the terminal may release the above-described information without applying it when NR-DC or MR-DC is configured.

[0183] FIG. 7 illustrates an example for a terminal to perform measurements in accordance with a frequency measurement order set by a base station in a next-generation mobile communication system according to various embodiments of the present invention.

[0184] According to various embodiments of the present disclosure, a terminal may sequentially perform measurements by giving priority to one or more specific frequencies according to the settings of a base station, as in the embodiments described above. According to one embodiment, the terminal may perform frequency measurements based on a measurement gap. For example, for a frequency that does not require a measurement gap, the terminal may perform measurements according to the period of a reference signal (SSB or CSI-RS) of the corresponding frequency. According to one embodiment, for a frequency that requires a measurement gap, the terminal may perform measurements according to the period of the reference signal for each frequency according to the measurement gap period set by the base station. The base station may set frequency-specific reference signal measurement timing configuration information (for example, in the case of SSB, SS / PBCH (synchronization signal and physical broadcasting channel) block measurement timing configuration) to the terminal, and the terminal may perform frequency measurements based on the measurement gap.

[0185] Referring to FIG. 7, a base station may provide measurement gap (MG) configuration information to a terminal, and the terminal may perform measurements according to periodic measurement gap points (705, 710, 715, 720). According to one embodiment, the measurement gap point may be set per terminal (per UE) or per frequency range (per FR). Here, the frequency range per frequency range may mean at least one of FR (frequency range) 1, FR2, or FR3.

[0186] In one embodiment, the terminal may be configured to sequentially perform measurements by prioritizing one or more specific frequencies according to the settings of the base station, as in the aforementioned embodiments. For convenience of explanation, the terminal may be configured to sequentially perform measurements on three frequencies (e.g., F1, F2, F3), and may be configured to perform measurements on the remaining frequencies according to the terminal implementation. In one embodiment, as described above, the reference measurement time points for each frequency may vary. For example, the reference measurement time points for each frequency may be as follows.

[0187] - The measurement points for the frequency (F1) that is set to be measured first can be (725, 730, 735, 740).

[0188] - The measurement point for the frequency (F2) set to be measured with second priority may be (745, 750, 755).

[0189] - The measurement points for the frequency (F3) set to be measured with the third priority may be (760, 765, 770, 775).

[0190] A terminal according to various embodiments of the present disclosure may perform measurements at periodic measurement gap times (705, 710, 715, 720) through at least one of the following methods.

[0191] * Method 1: If the terminal cannot measure the frequency that is currently required to be measured with the highest priority, it can measure the next highest priority frequency. For example, at time points 705 and 710, if the terminal needs to measure the F1 frequency but cannot measure it, it can measure the F2 frequency. At time points 715, if the terminal needs to measure the F1 frequency or the F2 frequency but cannot measure it, it can measure the F3 frequency.

[0192] - Method 1 has the advantage of reducing the delay in providing a specific service, as it allows the terminal to move to a frequency that supports the specific service as quickly as possible.

[0193] * Method 2: If the terminal cannot measure the frequency that is currently given the highest priority, it may not perform frequency measurement. For example, at time points 705 and 710, if the terminal needs to measure the F1 frequency but cannot measure it, it may not measure the F1, F2, or F3 frequencies.

[0194] - Method 2 has the advantage of being able to optimally provide a specific service, as it allows the terminal to move to the frequency that best supports that service.

[0195] * Method 3: If the terminal can measure the frequency that is currently given the highest priority, it can measure that frequency. For example, at time 720, the terminal can measure the F1 frequency.

[0196] * Method 4: If the terminal has measured all of the currently prioritized frequencies during the measurement gap, it can measure the next priority frequency. For example, at time 720, the terminal measures the F1 frequency, and if it can also measure the F3 frequency, it can measure the F3 frequency.

[0197] In one embodiment, when measurement gap setting information is set for each terminal, the above-described methods can be applied commonly to all frequencies. In another embodiment, when measurement gap setting information is set for each frequency range, the above-described methods can be applied commonly to frequencies within the corresponding frequency range. For example, the base station can configure the terminal to perform sequential measurements by prioritizing one or more specific frequencies within each frequency range.

[0198] According to one embodiment, the method for determining the frequency at which the terminal currently has the highest priority for measurement may be implemented by the terminal. According to one embodiment, or, if the terminal has sufficiently derived measurement results for the corresponding frequency, it may perform measurement on the frequency set to be measured next. For example, after performing measurement on the frequency set to be measured first, the terminal may determine whether a measurement report procedure is triggered, and then perform measurement on the frequency set to be measured next. For example, the terminal may determine whether a measurement report procedure is triggered through report configuration information for a measurement object (Measurement Object) or whether a measurement report procedure is triggered for a measurement identifier (Measurement Id), thereby identifying which frequency is currently being measured with priority, and performing measurement according to the frequency measurement order of the base station.

[0199] FIG. 8 illustrates a signal flow for a terminal with dual connectivity set to perform measurement according to a frequency measurement order set by a base station in a next-generation mobile communication system according to various embodiments of the present invention.

[0200] According to various embodiments of the present disclosure, for a terminal configured with Dual Connectivity (DC), configuration information can be set to allow only a node operating as a Master Node (MN) to perform measurements on the terminal according to the frequency measurement order. For example:

[0201] * When the terminal is set to E-UTRA-NR Dual Connectivity (EN-DC), only the eNB base station operating as MN can set the configuration information to perform measurements according to the frequency measurement order for the terminal.

[0202] * When the terminal is set to NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), only the ng-eNB base station operating as an MN can set the configuration information to perform measurements according to the frequency measurement order for the terminal.

[0203] * When the terminal is set to NR-E-UTRA Dual Connectivity (NE-DC), only the gNB base station operating as an MN can set the configuration information to perform measurements according to the frequency measurement order for the terminal.

[0204] * When the terminal is set to NR-NR Dual Connectivity (NR-DC), only the gNB base station operating as an MN can set the configuration information to perform measurements according to the frequency measurement order for the terminal.

[0205] Referring to FIG. 8, in step (805), the terminal (801) may establish an RRC connection with the base station (802) and be in RRC connected mode (RRC_CONNECTED). According to various embodiments, the base station (802) may be referred to as a Master Node (MN).

[0206] In step (810), the terminal (801) may transmit a terminal capability information message (UECapabilityInformation) to the base station (802). The information included in the capability information message may follow at least one of the embodiments described above.

[0207] In step (815), dual connectivity may be set for the terminal (801). For example:

[0208] * When the terminal is set to E-UTRA-NR Dual Connectivity (EN-DC), MN (802) may mean an eNB base station, and SN (803) may mean a gNB base station.

[0209] * When the terminal is set to NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), MN (802) may mean an ng-eNB base station, and SN (803) may mean a gNB base station.

[0210] * When the terminal is set to NR-E-UTRA Dual Connectivity (NE-DC), MN (802) may mean a gNB base station, and SN (803) may mean an eNB base station or an ng-eNB base station.

[0211] * When the terminal is set to NR-NR Dual Connectivity (NR-DC), MN (802) may mean a gNB base station, and SN (803) may mean a gNB base station.

[0212] In step (820), the MN (802) may transmit a predetermined message (e.g., CG-ConfigInfo of an RRC message) to the SN (803) via at least one of the X2 interface, the Xn interface, or the NG interface. The message transmitted by the MN (802) may include at least one of the following:

[0213] * List of frequencies that the terminal measures sequentially with priority

[0214] * One or more frequencies and a measurement priority value that indicates the measurement order for each frequency.

[0215] * An indicator or information that sets the setting information for the terminal to sequentially measure one or more specific frequencies with priority.

[0216] In step (825), the SN (803) may transmit a predetermined message (e.g., CG-Config of an RRC message) to the MN (802) via at least one of the X2 interface, the Xn interface, or the NG interface. The message transmitted by the SN (803) may include at least one of the following:

[0217] * List of frequencies that the terminal measures sequentially with priority

[0218] - The above-described list may mean a separate list from the list in step (820) or may mean a list to be modified based on step (820). For example, the above-described list may mean refusing to set a specific frequency to the terminal in step (820), or may mean an acceptable frequency among the frequency list indicated in step (820), or may mean adding a new frequency that is not in the frequency list indicated in step (820).

[0219] * Measurement priority value indicating one or more frequencies and the measurement order for each frequency.

[0220] - According to one embodiment, at least one of the frequency and measurement priority received in step (820) may be modified by the above-described value.

[0221] * An indicator that the MN sets configuration information for the terminal to sequentially measure one or more specific frequencies with priority, or an indicator that approves or rejects the above-described information.

[0222] In step (830), the MN (802) can set a specific frequency or list of frequencies to the terminal (801), and the terminal can determine which frequencies to prioritize and sequentially measure.

[0223] In step (835), the MN (802) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to the terminal (801). This may follow at least one of the embodiments described above.

[0224] In step (840), the terminal (801) may perform measurement based on measurement setting information received from the MN (802). This may follow at least one of the embodiments described above.

[0225] In step (845), the terminal (801) can determine whether a condition for reporting a measurement result message (MeasurementReport) to the MN (802) is triggered based on the measurement result in step (840). This may follow at least one of the embodiments described above.

[0226] In step (850), the terminal (801) may transmit the measurement results (measResults) for the measId for which the measurement report procedure was triggered in step (845) to the MN (802) by including them in a measurement result message (MeasurementReport). If the SN instructs the terminal to measure a specific frequency with priority, the MN may also transmit the corresponding information from the information in the measurement result message to the SN.

[0227] According to various embodiments of the present disclosure, only a base station operating as an MN can be configured to sequentially measure one or more specific frequencies with priority for a terminal configured for dual connectivity. To this end, the MN and SN can exchange information regarding whether to sequentially measure specific frequencies with priority for the terminal.

[0228] FIG. 9 illustrates a signal flow for a terminal with dual connectivity set to perform measurements according to a frequency measurement order set by a base station in a next-generation mobile communication system according to various embodiments of the present invention.

[0229] According to various embodiments of the present disclosure, for a terminal configured with Dual Connectivity (DC), configuration information may be set to allow only one node among the nodes operating as a Master Node (MN) and a Secondary Node (SN) to perform measurements on the terminal according to the frequency measurement order. For example:

[0230] * When the terminal is set to E-UTRA-NR Dual Connectivity (EN-DC), only one of the eNB base stations operating as MN and the gNB base station operating as SN can set configuration information to instruct the terminal to perform measurements in accordance with the frequency measurement order.

[0231] * When the terminal is set to NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), only one of the ng-eNB base stations operating as MN and the gNB base station operating as SN can set configuration information to instruct the terminal to perform measurements in accordance with the frequency measurement order.

[0232] * When the terminal is set to NR-E-UTRA Dual Connectivity (NE-DC), only one of the gNB base stations operating as MN and the ng-eNB (or eNB) base station operating as SN can set configuration information to instruct the terminal to perform measurements in accordance with the frequency measurement order.

[0233] * When the terminal is set to NR-NR Dual Connectivity (NR-DC), only one of the gNB base stations operating as MN and the gNB base station operating as SN can set configuration information to instruct the terminal to perform measurements in accordance with the frequency measurement order.

[0234] Referring to FIG. 9, in step (905), the terminal (901) may establish an RRC connection with the base station (902) and be in RRC connected mode (RRC_CONNECTED). In one embodiment, the base station (902) may be referred to as a Master Node (MN).

[0235] In step (910), the terminal (901) may transmit a terminal capability information message (UECapabilityInformation) to the base station (902). The information included in the capability information message may follow at least one of the embodiments described above.

[0236] In step (915), the terminal (901) may be configured for dual connectivity. For example:

[0237] * When the terminal is set to E-UTRA-NR Dual Connectivity (EN-DC), MN (902) may mean an eNB base station, and SN (903) may mean a gNB base station.

[0238] * When the terminal is set to NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), MN (902) may mean an ng-eNB base station, and SN (903) may mean a gNB base station.

[0239] * When the terminal is set to NR-E-UTRA Dual Connectivity (NE-DC), MN (902) may mean a gNB base station, and SN (903) may mean an eNB base station or an ng-eNB base station.

[0240] * When the terminal is set to NR-NR Dual Connectivity (NR-DC), MN (902) may mean a gNB base station, and SN (903) may mean a gNB base station.

[0241] In step (920), the MN (902) may transmit a predetermined message (e.g., CG-ConfigInfo of an RRC message) to the SN (903) via at least one of the X2 interface, the Xn interface, or the NG interface. The message transmitted by the MN (902) may include at least one of the following:

[0242] * List of frequencies that the terminal measures sequentially with priority

[0243] * One or more frequencies and a measurement priority value that indicates the measurement order for each frequency.

[0244] * An instruction or information that instructs the terminal to set configuration information for sequential measurement by giving priority to one or more specific frequencies.

[0245] * New timer value

[0246] - In one embodiment, the timer value may be a value indicating whether the terminal has been set to sequentially measure one or more specific frequencies with priority. For example, an SN that has received the timer value may operate it, and when the timer expires, the SN may determine that the priority measurement setting information set for the terminal has been released, or that the SN can set the priority measurement setting information for the terminal.

[0247] In step (925), the SN (903) may transmit a predetermined message (e.g., CG-Config of an RRC message) to the MN (902) via at least one of the X2 interface, the Xn interface, or the NG interface. The message transmitted by the SN (903) may include at least one of the following:

[0248] * List of frequencies that the terminal measures sequentially with priority

[0249] - The above-described list may mean a separate list from the list in step (920) or may mean a list to be modified based on step (920). For example, the above-described list may mean refusing to set a specific frequency to the terminal in step (920), or may mean an acceptable frequency among the frequency list indicated in step (920), or may mean adding a new frequency that is not in the frequency list indicated in step (920).

[0250] * One or more frequencies and a measurement priority value that indicates the measurement order for each frequency.

[0251] - According to one embodiment, the frequency and value described above may modify at least one of the frequency and measurement priority received in step (920).

[0252] * An instruction that the MN sets to the terminal the configuration information that sets the terminal to sequentially measure one or more specific frequencies with priority, or an instruction that approves or rejects the information.

[0253] * An indicator or information that sets the terminal to sequentially measure one or more specific frequencies with priority.

[0254] * New timer value

[0255] - In one embodiment, the timer value may be a value indicating whether the terminal has been set to sequentially measure one or more specific frequencies with priority. For example, an MN that has received the timer value can operate it, and when the timer expires, it can determine that the priority measurement setting information set for the terminal has been released, or that the MN can set the priority measurement setting information for the terminal.

[0256] At step (930), the MN (902) may determine whether to set a specific frequency or list of frequencies for the terminal (901) so that the terminal can sequentially measure them with priority. In one embodiment, either the MN (902) or the SN (903) may perform step (930). However, for convenience of explanation, according to various embodiments of the present disclosure, the MN (902) is described as performing step (930).

[0257] At step (935), the MN (902) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to the terminal (901). This may follow at least one of the embodiments described above.

[0258] In step (940), the terminal (901) may perform measurement based on measurement setting information received from the MN (902). This may follow at least one of the embodiments described above.

[0259] In step (945), the terminal (901) can determine whether a condition for reporting a measurement result message (MeasurementReport) to the MN (902) based on the measurement result in step (940) is triggered. This can follow at least one of the embodiments described above.

[0260] In step (950), the terminal (901) may include the measurement results (measResults) for the measId for which the measurement report procedure was triggered in step (945) in a measurement result message (MeasurementReport) and transmit it to the MN (902). If the SN instructs the terminal to measure a specific frequency with priority, the MN may also transmit the corresponding information from the information in the measurement result message to the SN.

[0261] In step (955), MN (902) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to terminal (901). The measurement configuration information may release the information set in step (935) that allows the terminal to sequentially perform measurements by giving priority to specific measurement objects among the measurement objects.

[0262] In step (960), MN (902) can transmit a predetermined message (e.g., CG-ConfigInfo of RRC message) to SN (903) through at least one of X2 interface, Xn interface, or NG interface. The message transmitted by MN (902) can include an indicator that the configuration information that sets the terminal to perform measurement sequentially by giving priority to specific measurement objects among measurement objects has been released. Through this, SN (903) can directly set the configuration information to perform measurement sequentially to the terminal (901) if necessary in the future.

[0263] According to various embodiments of the present disclosure, among base stations operating as both a MN and a SN, only one base station can be configured to sequentially measure one or more specific frequencies with priority for a terminal with dual connectivity. To this end, the MN and SN can exchange information regarding which node will sequentially measure which frequencies with priority for the terminal.

[0264] FIG. 10 illustrates a signal flow for a terminal with dual connectivity set to perform measurement according to a frequency measurement order set by a base station in a next-generation mobile communication system according to various embodiments of the present invention.

[0265] According to various embodiments of the present disclosure, nodes operating as a Master Node (MN) and a Secondary Node (SN) for a terminal configured with Dual Connectivity (DC) may each set configuration information to perform measurements for the terminal according to a frequency measurement order. For example:

[0266] * When the terminal is set to E-UTRA-NR Dual Connectivity (EN-DC), the eNB base station operating as MN and the gNB base station operating as SN can each set configuration information to perform measurements according to the frequency measurement order for the terminal.

[0267] * When the terminal is set to NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), the ng-eNB base station operating as MN and the gNB base station operating as SN can each set configuration information to perform measurements according to the frequency measurement order for the terminal.

[0268] * When the terminal is set to NR-E-UTRA Dual Connectivity (NE-DC), the gNB base station operating as MN and the ng-eNB (or eNB) base station operating as SN can each set configuration information to perform measurements according to the frequency measurement order for the terminal.

[0269] * When the terminal is set to NR-NR Dual Connectivity (NR-DC), the gNB base station operating as MN and the gNB base station operating as SN can each set configuration information to perform measurements according to the frequency measurement order for the terminal.

[0270] Referring to FIG. 10, in step (1005), the terminal (1001) may establish an RRC connection with the base station (1002) and be in RRC connected mode (RRC_CONNECTED). According to one embodiment, the base station (1002) may be referred to as a Master Node (MN).

[0271] In step (1010), the terminal (1001) may transmit a terminal capability information message (UECapabilityInformation) to the base station (1002). The information included in the terminal capability information message may follow at least one of the above-described embodiments.

[0272] In step (1015), the terminal (1001) may be configured for dual connectivity. For example:

[0273] * When the terminal is set to E-UTRA-NR Dual Connectivity (EN-DC), MN (1002) may mean an eNB base station, and SN (1003) may mean a gNB base station.

[0274] * When the terminal is set to NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), MN (1002) may mean an ng-eNB base station, and SN (1003) may mean a gNB base station.

[0275] * When the terminal is set to NR-E-UTRA Dual Connectivity (NE-DC), MN (1002) may mean a gNB base station, and SN (1003) may mean an eNB base station or an ng-eNB base station.

[0276] * When the terminal is set to NR-NR Dual Connectivity (NR-DC), MN (1002) may mean a gNB base station, and SN (1003) may mean a gNB base station.

[0277] In step (1020), the MN (1002) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to the terminal (1001). This may follow at least one of the embodiments described above.

[0278] In step (1025), the terminal (1001) may perform measurement based on measurement setting information received from the MN (1002). This may follow at least one of the embodiments described above.

[0279] In step (1030), the terminal (1001) can determine whether a condition for reporting a measurement result message (MeasurementReport) to the MN (1002) is triggered based on the measurement result in step (1025). This may follow at least one of the embodiments described above.

[0280] In step (1035), the terminal (1001) can transmit the measurement results (measResults) for the measId for which the measurement report procedure was triggered in step (1045) to the MN (1002) by including them in a measurement result message (MeasurementReport).

[0281] In step (1040), the SN (1003) may transmit a predetermined RRC message (e.g., RRCReconfiguration) containing measurement configuration information (MeasConfig) to the terminal (1001). This may follow at least one of the aforementioned embodiments. According to one embodiment, if Signaling Radio Bearer 3 (SRB 3) is not configured, the terminal may receive the measurement configuration information provided by the SN from the MN (1002).

[0282] In step (1045), the terminal (1001) may perform measurement based on measurement setting information received from the SN (1003). This may follow at least one of the embodiments described above.

[0283] In step (1050), the terminal (1001) can determine whether a condition for reporting a measurement result message (MeasurementReport) to the MN (1002) is triggered based on the measurement result in step (1045). This may follow at least one of the embodiments described above.

[0284] In step (1055), the terminal (1001) may include the measurement results (measResults) for the measId for which the measurement report procedure was triggered in step (1050) in a measurement result message (MeasurementReport) and transmit it to the SN (1003). According to one embodiment, if SRB 3 (Signaling Radio Bearer 3) is not set, the terminal may also transmit the measurement result message to the MN (1002). In this case, the MN (1002) that receives the message may forward the received message to the SN (1003).

[0285] According to various embodiments of the present disclosure, base stations operating as MN and SN may each configure a dual-connection terminal to sequentially measure one or more specific frequencies with priority. According to one embodiment, in the above-described content, the MN and SN may not set the same measurement priority value to the terminal. To this end, as in the above-described embodiment, the MN and SN may exchange the measurement priority values ​​assigned to each frequency. Of course, if the same measurement priority value is assigned to the terminal, the terminal may implementally determine which frequency to prioritize for measurement, or may prioritize a specific node and measure the frequency of the prioritized specific node first.

[0286] FIG. 11 illustrates the configuration of a terminal according to various embodiments of the present invention.

[0287] Referring to FIG. 11, the terminal includes an RF (Radio Frequency) processing unit (1110), a baseband processing unit (1120), a storage unit (1130), and a control unit (1140).

[0288] The RF processing unit (1110) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1110) up-converts the baseband signal provided from the baseband processing unit (1120) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1110) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. With reference to FIG. 11, only one antenna is illustrated, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (1110) may include a plurality of RF chains. Furthermore, the RF processing unit (1110) may perform beamforming. For beamforming, the RF processing unit (1110) can adjust the phase and amplitude of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit can perform MIMO and receive multiple layers when performing MIMO operations.

[0289] The baseband processing unit (1120) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (1120) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (1120) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (1110). For example, in the case of OFDM, when transmitting data, the baseband processing unit (1120) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols by performing an inverse fast Fourier transform (IFFT) operation and inserting a cyclic prefix (CP). In addition, when receiving data, the baseband processing unit (1120) divides the baseband signal provided from the RF processing unit (1110) into OFDM symbol units, restores signals mapped to subcarriers through FFT (fast Fourier transform), and then restores the received bit string through demodulation and decoding.

[0290] The baseband processing unit (1120) and the RF processing unit (1110) transmit and receive signals as described above. Accordingly, the baseband processing unit (1120) and the RF processing unit (1110) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (1120) and the RF processing unit (1110) may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processing unit (1120) and the RF processing unit (1110) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. Additionally, different frequency bands may include super high frequency (SHF) (e.g., 2.NRHz, NRhz) bands, millimeter wave (mm wave) (e.g., 60GHz) bands.

[0291] The storage unit (1130) stores data such as basic programs, application programs, and configuration information for the operation of the terminal. In particular, the storage unit (1130) can store information related to a second access node that performs wireless communication using a second wireless access technology. Furthermore, the storage unit (1130) provides the stored data upon request from the control unit (1140).

[0292] The control unit (1140) (processor) (or controller) controls the overall operations of the terminal. For example, the control unit (1140) transmits and receives signals through the baseband processing unit (1120) and the RF processing unit (1110). In addition, the control unit (1140) records and reads data in the storage unit (1140). For this purpose, the control unit (1140) may include at least one processor. For example, the control unit (1140) may include a communication processor (CP) that performs control for communication, an application processor (AP) that controls upper layers such as application programs, or a multi-connection processing unit (1142). According to various embodiments, the control unit (1140) may be controlled or configured to perform the various embodiments described above.

[0293] FIG. 12 illustrates the configuration of a base station according to various embodiments of the present invention.

[0294] Referring to FIG. 12, the base station is configured to include an RF processing unit (1210), a baseband processing unit (1220), a backhaul communication unit (1230), a storage unit (1240), and a control unit (1250).

[0295] The RF processing unit (1210) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1210) upconverts the baseband signal provided from the baseband processing unit (1220) into an RF band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1210) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. With reference to FIG. 12, only one antenna is illustrated, but the first access node may have multiple antennas. In addition, the RF processing unit (1210) may include multiple RF chains. Furthermore, the RF processing unit (1210) may perform beamforming. For beamforming, the RF processing unit (1210) may adjust the phase and magnitude of each signal transmitted and received through a plurality of antennas or antenna elements. The RF processing unit can perform downlink MIMO operations by transmitting one or more layers.

[0296] The baseband processing unit (1220) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (1220) generates complex symbols by encoding and modulating the transmission bit stream. In addition, when receiving data, the baseband processing unit (1220) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (1210). For example, in the case of OFDM, when transmitting data, the baseband processing unit (1220) generates complex symbols by encoding and modulating the transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (1220) divides the baseband signal provided from the RF processing unit (1210) into OFDM symbol units, restores the signals mapped to subcarriers through FFT operation, and then restores the received bit string through demodulation and decoding. The baseband processing unit (1220) and the RF processing unit (1210) transmit and receive signals as described above. Accordingly, the baseband processing unit (1220) and the RF processing unit (1210) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0297] The backhaul communication unit (1230) provides an interface for communicating with other nodes within the network. That is, the backhaul communication unit (1230) converts a bit string transmitted from a primary base station to other nodes, such as auxiliary base stations or core networks, into a physical signal, and converts a physical signal received from other nodes into a bit string.

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

[0299] The control unit (1250) (processor) (or controller) controls the overall operations of the base station. For example, the control unit (1250) transmits and receives signals through the baseband processing unit (1220) and the RF processing unit (1210) or through the backhaul communication unit (1230). In addition, the control unit (1250) records and reads data in the storage unit (1240). For this purpose, the control unit (1250) may include at least one processor or a multi-connection processing unit (1252). According to various embodiments, the control unit (1250) may be controlled or configured to perform the various embodiments described above.

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

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

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

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

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

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

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

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

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

[0309] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. For example, some or all of the embodiments may be combined with some or all of one or more other embodiments, and such combinations should naturally fall within the scope of the embodiments proposed in this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the claims described below, but also by equivalents thereof.

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

Claims

1. In a wireless communication system, a user equipment (UE) Transceiver; and Including a controller coupled with the above transceiver, The above controller, Receive first measurement setting information associated with a master cell group (MCG) from a first base station, and It is configured to transmit the measurement result according to the first measurement setting information to the first base station, A terminal wherein the first measurement setting information includes information indicating an order for measurement of at least one frequency associated with the first measurement setting information.

2. In claim 1, when second measurement configuration information associated with a secondary cell group (SCG) is received, the terminal does not include information indicating an order for measurement of at least one frequency associated with the second measurement configuration information.

3. In claim 1, the controller, A terminal further configured to transmit terminal capability information indicating to the first base station whether the terminal supports setting of information indicating the order for the measurement.

4. In claim 1, DC (dual connectivity) with the first base station and the second base station is set for the terminal, The above first base station is a NR (new radio) base station, and The second base station is a terminal which is either an NR base station or an evolved-universal mobile telecommunication system (UMTS) terrestrial radio access (E-UTRA) base station.

5. In a wireless communication system, the first base station, Transceiver; and Including a controller coupled with the above transceiver, The above controller, Transmitting first measurement configuration information associated with a master cell group (MCG) to a user equipment (UE), and It is configured to receive a measurement result according to the first measurement setting information from the terminal, A first base station, wherein the first measurement setting information includes information indicating an order for measurement of at least one frequency associated with the first measurement setting information.

6. In claim 5, when second measurement configuration information associated with a secondary cell group (SCG) is transmitted, the second measurement configuration information is a first base station that does not include information indicating an order for measurement of at least one frequency associated with the second measurement configuration information.

7. In claim 5, the controller, A first base station further configured to receive terminal capability information from the terminal, the terminal capability information indicating whether the terminal supports setting of information indicating the order for the measurement.

8. In claim 5, DC (dual connectivity) with the first base station and the second base station is set for the terminal, The above first base station is a NR (new radio) base station, and The second base station is a first base station which is either an NR base station or an evolved-universal mobile telecommunication system (UMTS) terrestrial radio access (E-UTRA) base station.

9. In a wireless communication system, a method performed by a user equipment (UE) is as follows: A step of receiving first measurement setting information associated with a master cell group (MCG) from a first base station; and Including a step of transmitting a measurement result according to the first measurement setting information to the first base station, A method wherein the first measurement setup information includes information indicating an order for measurement of at least one frequency associated with the first measurement setup information.

10. A method according to claim 9, wherein, when second measurement configuration information associated with a secondary cell group (SCG) is received, the second measurement configuration information does not include information indicating an order for measurement of at least one frequency associated with the second measurement configuration information.

11. In claim 9, the method comprises: A method further comprising the step of transmitting terminal capability information indicating to the first base station whether the terminal supports setting of information indicating the order for the measurement.

12. In claim 9, DC (dual connectivity) with the first base station and the second base station is set for the terminal, The above first base station is a NR (new radio) base station, and A method wherein the second base station is one of an NR base station or an evolved-universal mobile telecommunication system (UMTS) terrestrial radio access (E-UTRA) base station.

13. In a wireless communication system, a method performed by a first base station, A step of transmitting first measurement setting information associated with a master cell group (MCG) to a terminal (user equipment, UE); and A step of receiving a measurement result according to the first measurement setting information from the terminal, A method wherein the first measurement setup information includes information indicating an order for measurement of at least one frequency associated with the first measurement setup information.

14. A method according to claim 13, wherein, when second measurement configuration information associated with a secondary cell group (SCG) is transmitted, the second measurement configuration information does not include information indicating an order for measurement of at least one frequency associated with the second measurement configuration information.

15. In claim 13, the method comprises: A method further comprising the step of receiving, from the terminal, terminal capability information indicating whether the terminal supports setting of information indicating the order for the measurement.

Images