Transmission of measurement report based on report configuration identifiers of multiple triggered measurement reports

Abstract

A method and apparatus for a transmission of a measurement report based on report configuration Identifiers (IDs) of multiple triggered measurement reports is provided. A first measurement reporting is considered to be triggered based on a first event condition associated with a first report configuration being fulfilled for a first measurement target, and a second measurement reporting is considered to be triggered based on a second event condition associated with the first report configuration being fulfilled for a second measurement target. Based on the first measurement reporting and the second measurement reporting which have been considered to be triggered for the first report configuration, the wireless device transmits a measurement report media access control (MAC) control element (CE) to the network based on the first report configuration.

Description

TRANSMISSION OF MEASUREMENT REPORT BASED ON REPORT CONFIGURATION IDENTIFIERS OF MULTIPLE TRIGGERED MEASUREMENT REPORTS

[0001] The present disclosure relates to a transmission of a measurement report based on report configuration identifiers (IDs) of multiple triggered measurement reports.

[0002] 3rd Generation Partnership Project (3GPP) New Radio (NR) targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), Ultra-Reliable and Low Latency Communications (URLLC), etc. The NR shall be inherently forward compatible. Further, the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.

[0003] 6G is the successor to 5G cellular technology. 6G networks will be able to use higher frequencies than 5G networks and provide substantially higher capacity and much lower latency. The 6G technology market is expected to facilitate large improvements in the areas of imaging, presence technology and location awareness. Working in conjunction with Artificial Intelligence (AI), the 6G computational infrastructure will be able to identify the best place for computing to occur. This includes decisions about data storage, processing and sharing.

[0004] Layer 3 based mobility has evolved over several releases. Conditional Handover (CHO) and other conditional mobility procedures (Conditional PSCell Addition and Change (CPAC), Subsequent CPAC (SCPAC)) were developed to achieve high robustness by enabling the procedure to be executed without necessitating a signaling exchange with source cell beforehand. L1 / L2 Triggered Mobility (LTM) as introduced in Rel-18 offers short interruption time but not with the same level of robustness as the conditional L3 mobility procedures. In Rel-19, enhancements should be specified so that the system can benefit from both the high robustness and short interruption.

[0005] In an aspect, a method is provided. The method comprises receiving one or more measurement target resources and one or more report configuration including one or more event conditions related to the one or more measurement target resources from a network. A first measurement reporting is considered to be triggered based on a first event condition associated with a first report configuration being fulfilled for a first measurement target, and a second measurement reporting is considered to be triggered based on a second event condition associated with the first report configuration being fulfilled for a second measurement target. Based on the first measurement reporting and the second measurement reporting which have been considered to be triggered for the first report configuration, the method further comprises transmitting a measurement report media access control (MAC) control element (CE) to the network based on the first report configuration.

[0006] In another aspect, an apparatus for implementing the above method is provided.

[0007] FIG. 1 shows an example of a communication system to which implementations of the present disclosure are applied.

[0008] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure are applied.

[0009] FIG. 3 shows an example of UE to which implementations of the present disclosure are applied.

[0010] FIGS. 4 and 5 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.

[0011] FIG. 6 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.

[0012] FIG. 7 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure are applied.

[0013] FIG. 8 shows an example of inter-gNB handover procedures to which implementations of the present disclosure are applied.

[0014] FIG. 9 shows an example of signaling procedure for LTM to which implementations of the present disclosure are applied.

[0015] FIG. 10 shows an example of measurement reporting triggered by beam-related event condition to which implementations of the present disclosure are applied.

[0016] FIG. 11 shows an example of a method to which implementations of the present disclosure are applied.

[0017] FIG. 12 shows an example of another method to which implementations of the present disclosure are applied.

[0018] FIG. 13 shows an example of a L1 measurement report MAC CE to which implementations of the present disclosure are applied.

[0019] FIG. 14 shows an example of controlling triggering of measurement reporting based on beam related event condition to which implementations of the present disclosure are applied.

[0020] FIG. 15 shows another example of controlling triggering of measurement reporting based on beam related event condition to which implementations of the present disclosure are applied.

[0021] The following techniques, apparatuses, and systems may be applied to a variety of wireless multiple access systems. Examples of the multiple access systems include a Code Division Multiple Access (CDMA) system, a Frequency Division Multiple Access (FDMA) system, a Time Division Multiple Access (TDMA) system, an Orthogonal Frequency Division Multiple Access (OFDMA) system, a Single Carrier Frequency Division Multiple Access (SC-FDMA) system, and a Multi Carrier Frequency Division Multiple Access (MC-FDMA) system. CDMA may be embodied through radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be embodied through radio technology such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE). OFDMA may be embodied through radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is a part of a Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in Downlink (DL) and SC-FDMA in Uplink (UL). Evolution of 3GPP LTE includes LTE-Advanced (LTE-A), LTE-A Pro, 5G New Radio (NR) and / or 6G.

[0022] For convenience of description, implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems.

[0023] For terms and technologies which are not specifically described among the terms of and technologies employed in the present disclosure, the wireless communication standard documents published before the present disclosure may be referenced.

[0024] In the present disclosure, "A or B" may mean "only A", "only B", or "both A and B". In other words, "A or B" in the present disclosure may be interpreted as "A and / or B". For example, "A, B or C" in the present disclosure may mean "only A", "only B", "only C", or "any combination of A, B and C".

[0025] In the present disclosure, slash ( / ) or comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Accordingly, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B or C".

[0026] In the present disclosure, "at least one of A and B" may mean "only A", "only B" or "both A and B". In addition, the expression "at least one of A or B" or "at least one of A and / or B" in the present disclosure may be interpreted as same as "at least one of A and B".

[0027] In addition, in the present disclosure, "at least one of A, B and C" may mean "only A", "only B", "only C", or "any combination of A, B and C". In addition, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C".

[0028] Also, parentheses used in the present disclosure may mean "for example". In detail, when it is shown as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information". In other words, "control information" in the present disclosure is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when shown as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information".

[0029] Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously.

[0030] Although not limited thereto, various descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure disclosed herein can be applied to various fields requiring wireless communication and / or connection (e.g., 5G) between devices.

[0031] Hereinafter, the present disclosure will be described in more detail with reference to drawings. The same reference numerals in the following drawings and / or descriptions may refer to the same and / or corresponding hardware blocks, software blocks, and / or functional blocks unless otherwise indicated.

[0032] FIG. 1 shows an example of a communication system to which implementations of the present disclosure are applied.

[0033] The 5G usage scenarios shown in FIG. 1 are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown in FIG. 1.

[0034] Three main requirement categories for 5G include (1) a category of enhanced Mobile BroadBand (eMBB), (2) a category of massive Machine Type Communication (mMTC), and (3) a category of Ultra-Reliable and Low Latency Communications (URLLC).

[0035] Referring to FIG. 1, the communication system 1 includes wireless devices 100a to 100f, Base Stations (BSs) 200, and a network 300. Although FIG. 1 illustrates a 5G network as an example of the network of the communication system 1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system.

[0036] The BSs 200 and the network 300 may be implemented as wireless devices and a specific wireless device may operate as a BS / network node with respect to other wireless devices.

[0037] The wireless devices 100a to 100f represent devices performing communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may be referred to as communication / radio / 5G devices. The wireless devices 100a to 100f may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, an eXtended Reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an Internet-of-Things (IoT) device 100f, and an Artificial Intelligence (AI) device / server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. The vehicles may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may include an Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter.

[0038] In the present disclosure, the wireless devices 100a to 100f may be called User Equipments (UEs). A UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a navigation system, a slate Personal Computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather / environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field.

[0039] The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs 200 / network 300. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., Vehicle-to-Vehicle (V2V) / Vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0040] Wireless communication / connections 150a, 150b and 150c may be established between the wireless devices 100a to 100f and / or between wireless device 100a to 100f and BS 200 and / or between BSs 200. Herein, the wireless communication / connections may be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication (or Device-to-Device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, Integrated Access and Backhaul (IAB)), etc. The wireless devices 100a to 100f and the BSs 200 / the wireless devices 100a to 100f may transmit / receive radio signals to / from each other through the wireless communication / connections 150a, 150b and 150c. For example, the wireless communication / connections 150a, 150b and 150c may transmit / receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, and resource mapping / de-mapping), and resource allocating processes, for transmitting / receiving radio signals, may be performed based on the various proposals of the present disclosure.

[0041] NR supports multiples numerologies (and / or multiple Sub-Carrier Spacings (SCS)) to support various 5G services. For example, if SCS is 15 kHz, wide area can be supported in traditional cellular bands, and if SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth can be supported. If SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz can be supported to overcome phase noise.

[0042] The NR frequency band may be defined as two types of frequency range, i.e., Frequency Range 1 (FR1) and Frequency Range 2 (FR2). The numerical value of the frequency range may be changed. For example, the frequency ranges of the two types (FR1 and FR2) may be as shown in Table 1 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean "sub 6 GHz range", FR2 may mean "above 6 GHz range," and may be referred to as millimeter Wave (mmW).

[0043] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0044] As mentioned above, the numerical value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410MHz to 7125MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving).

[0045] Frequency Range designationCorresponding frequency rangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0046] Here, the radio communication technologies implemented in the wireless devices in the present disclosure may include NarrowBand IoT (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and be called by various names such as enhanced MTC (eMTC). For example, LTE-M technology may be implemented in at least one of the various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and may not be limited to the above-mentioned names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN which take into account low-power communication, and may not be limited to the above-mentioned names. For example, ZigBee technology may generate Personal Area Networks (PANs) associated with small / low-power digital communication based on various specifications such as IEEE 802.15.4 and may be called various names.

[0047] FIG. 2 shows an example of wireless devices to which implementations of the present disclosure are applied.

[0048] In FIG. 2, The first wireless device 100 and / or the second wireless device 200 may be implemented in various forms according to use cases / services. For example, {the first wireless device 100 and the second wireless device 200} may correspond to at least one of {the wireless device 100a to 100f and the BS 200}, {the wireless device 100a to 100f and the wireless device 100a to 100f} and / or {the BS 200 and the BS 200} of FIG. 1. The first wireless device 100 and / or the second wireless device 200 may be configured by various elements, devices / parts, and / or modules.

[0049] The first wireless device 100 may include at least one transceiver, such as a transceiver 106, at least one processing chip, such as a processing chip 101, and / or one or more antennas 108.

[0050] The processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. Additional and / or alternatively, the memory 104 may be placed outside of the processing chip 101.

[0051] The processor 102 may control the memory 104 and / or the transceiver 106 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor 102 may process information within the memory 104 to generate first information / signals and then transmit radio signals including the first information / signals through the transceiver 106. The processor 102 may receive radio signals including second information / signals through the transceiver 106 and then store information obtained by processing the second information / signals in the memory 104.

[0052] The memory 104 may be operably connectable to the processor 102. The memory 104 may store various types of information and / or instructions. The memory 104 may store a firmware and / or a software code 105 which implements codes, commands, and / or a set of commands that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 105 may control the processor 102 to perform one or more protocols. For example, the firmware and / or the software code 105 may control the processor 102 to perform one or more layers of the radio interface protocol.

[0053] Herein, the processor 102 and the memory 104 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals through one or more antennas 108. Each of the transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the first wireless device 100 may represent a communication modem / circuit / chip.

[0054] The second wireless device 200 may include at least one transceiver, such as a transceiver 206, at least one processing chip, such as a processing chip 201, and / or one or more antennas 208.

[0055] The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. Additional and / or alternatively, the memory 204 may be placed outside of the processing chip 201.

[0056] The processor 202 may control the memory 204 and / or the transceiver 206 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts described in the present disclosure. For example, the processor 202 may process information within the memory 204 to generate third information / signals and then transmit radio signals including the third information / signals through the transceiver 206. The processor 202 may receive radio signals including fourth information / signals through the transceiver 106 and then store information obtained by processing the fourth information / signals in the memory 204.

[0057] The memory 204 may be operably connectable to the processor 202. The memory 204 may store various types of information and / or instructions. The memory 204 may store a firmware and / or a software code 205 which implements codes, commands, and / or a set of commands that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the firmware and / or the software code 205 may control the processor 202 to perform one or more protocols. For example, the firmware and / or the software code 205 may control the processor 202 to perform one or more layers of the radio interface protocol.

[0058] Herein, the processor 202 and the memory 204 may be a part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through one or more antennas 208. Each of the transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be interchangeably used with RF unit. In the present disclosure, the second wireless device 200 may represent a communication modem / circuit / chip.

[0059] Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as Physical (PHY) layer, Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Service Data Adaptation Protocol (SDAP) layer). The one or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs), one or more Service Data Unit (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure.

[0060] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors 102 and 202. For example, the one or more processors 102 and 202 may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a memory control processor.

[0061] The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104 and 204 may be configured by Random Access Memory (RAM), Dynamic RAM (DRAM), Read-Only Memory (ROM), electrically Erasable Programmable Read-Only Memory (EPROM), flash memory, volatile memory, non-volatile memory, hard drive, register, cash memory, computer-readable storage medium, and / or combinations thereof. The one or more memories 104 and 204 may be located at the interior and / or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.

[0062] The one or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.

[0063] The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208. Additionally and / or alternatively, the one or more transceivers 106 and 206 may include one or more antennas 108 and 208. The one or more transceivers 106 and 206 may be adapted to transmit and receive user data, control information, and / or radio signals / channels, mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure, through the one or more antennas 108 and 208. In the present disclosure, the one or more antennas 108 and 208 may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0064] The one or more transceivers 106 and 206 may convert received user data, control information, radio signals / channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals / channels, etc., using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals / channels, etc., processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, the one or more transceivers 106 and 206 can up-convert OFDM baseband signals to OFDM signals by their (analog) oscillators and / or filters under the control of the one or more processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency. The one or more transceivers 106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and / or filters under the control of the one or more processors 102 and 202.

[0065] Although not shown in FIG. 2, the wireless devices 100 and 200 may further include additional components. The additional components 140 may be variously configured according to types of the wireless devices 100 and 200. For example, the additional components 140 may include at least one of a power unit / battery, an Input / Output (I / O) device (e.g., audio I / O port, video I / O port), a driving device, and a computing device. The additional components 140 may be coupled to the one or more processors 102 and 202 via various technologies, such as a wired or wireless connection.

[0066] In the implementations of the present disclosure, a UE may operate as a transmitting device in UL and as a receiving device in DL. In the implementations of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device 100 acts as the UE, and the second wireless device 200 acts as the BS. For example, the processor(s) 102 connected to, mounted on or launched in the first wireless device 100 may be adapted to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behavior according to an implementation of the present disclosure. The processor(s) 202 connected to, mounted on or launched in the second wireless device 200 may be adapted to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behavior according to an implementation of the present disclosure.

[0067] In the present disclosure, a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB.

[0068] FIG. 3 shows an example of UE to which implementations of the present disclosure are applied.

[0069] Referring to FIG. 3, a UE 100 may correspond to the first wireless device 100 of FIG. 2.

[0070] A UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 141, a battery 142, a display 143, a keypad 144, a Subscriber Identification Module (SIM) card 145, a speaker 146, and a microphone 147.

[0071] The processor 102 may be adapted to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The processor 102 may be adapted to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include ASIC, other chipset, logic circuit and / or data processing device. The processor 102 may be an application processor. The processor 102 may include at least one of DSP, CPU, GPU, a modem (modulator and demodulator). An example of the processor 102 may be found in SNAPDRAGONTMseries of processors made by QUALCOMM®, EXYNOSTMseries of processors made by SAMSUNG®, A series of processors made by APPLE®, HELIOTMseries of processors made by MEDIATEK®, ATOMTMseries of processors made by INTEL®or a corresponding next generation processor.

[0072] The memory 104 is operatively coupled with the processor 102 and stores a variety of information to operate the processor 102. The memory 104 may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. The modules can be stored in the memory 104 and executed by the processor 102. The memory 104 can be implemented within the processor 102 or external to the processor 102 in which case those can be communicatively coupled to the processor 102 via various means as is known in the art.

[0073] The transceiver 106 is operatively coupled with the processor 102, and transmits and / or receives a radio signal. The transceiver 106 includes a transmitter and a receiver. The transceiver 106 may include baseband circuitry to process radio frequency signals. The transceiver 106 controls the one or more antennas 108 to transmit and / or receive a radio signal.

[0074] The power management module 141 manages power for the processor 102 and / or the transceiver 106. The battery 142 supplies power to the power management module 141.

[0075] The display 143 outputs results processed by the processor 102. The keypad 144 receives inputs to be used by the processor 102. The keypad 144 may be shown on the display 143.

[0076] The SIM card 145 is an　integrated circuit　that is intended to　securely store the　International Mobile Subscriber Identity　(IMSI) number and its related　key, which are used to identify and authenticate subscribers on　mobile telephony　devices (such as　mobile phones　and　computers). It is also possible to store contact information on many SIM cards.

[0077] The speaker 146 outputs sound-related results processed by the processor 102. The microphone 147 receives sound-related inputs to be used by the processor 102.

[0078] FIGS. 4 and 5 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.

[0079] In particular, FIG. 4 illustrates an example of a radio interface user plane protocol stack between a UE and a BS and FIG. 5 illustrates an example of a radio interface control plane protocol stack between a UE and a BS. The control plane refers to a path through which control messages used to manage call by a UE and a network are transported. The user plane refers to a path through which data generated in an application layer, for example, voice data or Internet packet data are transported. Referring to FIG. 4, the user plane protocol stack may be divided into Layer 1 (i.e., a PHY layer) and Layer 2. Referring to FIG. 5, the control plane protocol stack may be divided into Layer 1 (i.e., a PHY layer), Layer 2, Layer 3 (e.g., an RRC layer), and a Non-Access Stratum (NAS) layer. Layer 1, Layer 2 and Layer 3 are referred to as an Access Stratum (AS).

[0080] In the 3GPP LTE system, the Layer 2 is split into the following sublayers: MAC, RLC, and PDCP. In the 3GPP NR system, the Layer 2 is split into the following sublayers: MAC, RLC, PDCP and SDAP. The PHY layer offers to the MAC sublayer transport channels, the MAC sublayer offers to the RLC sublayer logical channels, the RLC sublayer offers to the PDCP sublayer RLC channels, the PDCP sublayer offers to the SDAP sublayer radio bearers. The SDAP sublayer offers to 5G core network Quality of Service (QoS) flows.

[0081] In the 3GPP NR system, the main services and functions of the MAC sublayer include: mapping between logical channels and transport channels; multiplexing / de-multiplexing of MAC SDUs belonging to one or different logical channels into / from Transport Blocks (TB) delivered to / from the physical layer on transport channels; scheduling information reporting; error correction through Hybrid Automatic Repeat reQuest (HARQ) (one HARQ entity per cell in case of Carrier Aggregation (CA)); priority handling between UEs by means of dynamic scheduling; priority handling between logical channels of one UE by means of logical channel prioritization; padding. A single MAC entity may support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritization control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use.

[0082] Different kinds of data transfer services are offered by MAC. To accommodate different kinds of data transfer services, multiple types of logical channels are defined, i.e., each supporting transfer of a particular type of information. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used for the transfer of control plane information only, and traffic channels are used for the transfer of user plane information only. Broadcast Control Channel (BCCH) is a downlink logical channel for broadcasting system control information, Paging Control Channel (PCCH) is a downlink logical channel that transfers paging information, system information change notifications and indications of ongoing Public Warning Service (PWS) broadcasts, Common Control Channel (CCCH) is a logical channel for transmitting control information between UEs and network and used for UEs having no RRC connection with the network, and Dedicated Control Channel (DCCH) is a point-to-point bi-directional logical channel that transmits dedicated control information between a UE and the network and used by UEs having an RRC connection. Dedicated Traffic Channel (DTCH) is a point-to-point logical channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. In downlink, the following connections between logical channels and transport channels exist: BCCH can be mapped to Broadcast Channel (BCH); BCCH can be mapped to Downlink Shared Channel (DL-SCH); PCCH can be mapped to Paging Channel (PCH); CCCH can be mapped to DL-SCH; DCCH can be mapped to DL-SCH; and DTCH can be mapped to DL-SCH. In uplink, the following connections between logical channels and transport channels exist: CCCH can be mapped to Uplink Shared Channel (UL-SCH); DCCH can be mapped to UL-SCH; and DTCH can be mapped to UL-SCH.

[0083] The RLC sublayer supports three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC configuration is per logical channel with no dependency on numerologies and / or transmission durations. In the 3GPP NR system, the main services and functions of the RLC sublayer depend on the transmission mode and include: transfer of upper layer PDUs; sequence numbering independent of the one in PDCP (UM and AM); error correction through ARQ (AM only); segmentation (AM and UM) and re-segmentation (AM only) of RLC SDUs; reassembly of SDU (AM and UM); duplicate detection (AM only); RLC SDU discard (AM and UM); RLC re-establishment; protocol error detection (AM only).

[0084] In the 3GPP NR system, the main services and functions of the PDCP sublayer for the user plane include: sequence numbering; header compression and decompression using Robust Header Compression (ROHC); transfer of user data; reordering and duplicate detection; in-order delivery; PDCP PDU routing (in case of split bearers); retransmission of PDCP SDUs; ciphering, deciphering and integrity protection; PDCP SDU discard; PDCP re-establishment and data recovery for RLC AM; PDCP status reporting for RLC AM; duplication of PDCP PDUs and duplicate discard indication to lower layers. The main services and functions of the PDCP sublayer for the control plane include: sequence numbering; ciphering, deciphering and integrity protection; transfer of control plane data; reordering and duplicate detection; in-order delivery; duplication of PDCP PDUs and duplicate discard indication to lower layers.

[0085] In the 3GPP NR system, the main services and functions of SDAP include: mapping between a QoS flow and a data radio bearer; marking QoS Flow ID (QFI) in both DL and UL packets. A single protocol entity of SDAP is configured for each individual PDU session.

[0086] In the 3GPP NR system, the main services and functions of the RRC sublayer include: broadcast of system information related to AS and NAS; paging initiated by 5G Core network (5GC) or Next-Generation Radio Access Network (NG-RAN); establishment, maintenance and release of an RRC connection between the UE and NG-RAN; security functions including key management; establishment, configuration, maintenance and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs); mobility functions (including: handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of the reporting; detection of and recovery from radio link failure; NAS message transfer to / from NAS from / to UE.

[0087] FIG. 6 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure are applied.

[0088] The frame structure shown in FIG. 6 is purely exemplary and the number of subframes, the number of slots, and / or the number of symbols in a frame may be variously changed. In the 3GPP based wireless communication system, OFDM numerologies (e.g., SCS, Transmission Time Interval (TTI) duration) may be differently configured between a plurality of cells aggregated for one UE. For example, if a UE is configured with different SCSs for cells aggregated for the cell, an (absolute time) duration of a time resource (e.g., a subframe, a slot, or a TTI) including the same number of symbols may be different among the aggregated cells. Herein, symbols may include OFDM symbols (or Cyclic Prefix (CP)-OFDM symbols), SC-FDMA symbols (or Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbols).

[0089] Referring to FIG. 6, downlink and uplink transmissions are organized into frames. Each frame has Tf= 10ms duration. Each frame is divided into two half-frames, where each of the half-frames has 5ms duration. Each half-frame consists of 5 subframes, where the duration Tsfper subframe is 1ms. Each subframe is divided into slots and the number of slots in a subframe depends on a subcarrier spacing. Each slot includes 14 or 12 OFDM symbols based on a CP. In a normal CP, each slot includes 14 OFDM symbols and, in an extended CP, each slot includes 12 OFDM symbols. The numerology is based on exponentially scalable subcarrier spacing Δf = 2u*15 kHz.

[0090] Table 3 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frameNframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the normal CP, according to the subcarrier spacing Δf = 2u*15 kHz.

[0091] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016

[0092] Table 4 shows the number of OFDM symbols per slot Nslotsymb, the number of slots per frameNframe,uslot, and the number of slots per subframe Nsubframe,uslotfor the extended CP, according to the subcarrier spacing Δf = 2u*15 kHz.

[0093] uNslotsymbNframe,uslotNsubframe,uslot212404

[0094] A slot includes plural symbols (e.g., 14 or 12 symbols) in the time domain. For each numerology (e.g., subcarrier spacing) and carrier, a resource grid ofNsize,ugrid,x*NRBscsubcarriers andNsubframe,usymbOFDM symbols is defined, starting at Common Resource Block (CRB)Nstart,ugridindicated by higher-layer signaling (e.g., RRC signaling), whereNsize,ugrid,xis the number of Resource Blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink.NRBscis the number of subcarriers per RB. In the 3GPP based wireless communication system,NRBscis 12 generally. There is one resource grid for a given antenna portp, subcarrier spacing configurationu, and transmission direction (DL or UL). The carrier bandwidthNsize,ugridfor subcarrier spacing configurationuis given by the higher-layer parameter (e.g., RRC parameter). Each element in the resource grid for the antenna portpand the subcarrier spacing configurationuis referred to as a Resource Element (RE) and one complex symbol may be mapped to each RE. Each RE in the resource grid is uniquely identified by an indexkin the frequency domain and an indexlrepresenting a symbol location relative to a reference point in the time domain. In the 3GPP based wireless communication system, an RB is defined by 12 consecutive subcarriers in the frequency domain.

[0095] In the 3GPP NR system, RBs are classified into CRBs and Physical Resource Blocks (PRBs). CRBs are numbered from 0 and upwards in the frequency domain for subcarrier spacing configurationu. The center of subcarrier 0 of CRB 0 for subcarrier spacing configurationucoincides with 'point A' which serves as a common reference point for resource block grids. In the 3GPP NR system, PRBs are defined within a BandWidth Part (BWP) and numbered from 0 toNsizeBWP,i-1, where i is the number of the bandwidth part. The relation between the physical resource block nPRBin the bandwidth part i and the common resource block nCRBis as follows: nPRB= nCRB+NsizeBWP,i, whereNsizeBWP,iis the common resource block where bandwidth part starts relative to CRB 0. The BWP includes a plurality of consecutive RBs. A carrier may include a maximum of N (e.g., 5) BWPs. A UE may be configured with one or more BWPs on a given component carrier. Only one BWP among BWPs configured to the UE can active at a time. The active BWP defines the UE's operating bandwidth within the cell's operating bandwidth.

[0096] In the present disclosure, the term "cell" may refer to a geographic area to which one or more nodes provide a communication system, or refer to radio resources. A "cell" as a geographic area may be understood as coverage within which a node can provide service using a carrier and a "cell" as radio resources (e.g., time-frequency resources) is associated with bandwidth which is a frequency range configured by the carrier. The "cell" associated with the radio resources is defined by a combination of downlink resources and uplink resources, for example, a combination of a DL Component Carrier (CC) and a UL CC. The cell may be configured by downlink resources only, or may be configured by downlink resources and uplink resources. Since DL coverage, which is a range within which the node is capable of transmitting a valid signal, and UL coverage, which is a range within which the node is capable of receiving the valid signal from the UE, depends upon a carrier carrying the signal, the coverage of the node may be associated with coverage of the "cell" of radio resources used by the node. Accordingly, the term "cell" may be used to represent service coverage of the node sometimes, radio resources at other times, or a range that signals using the radio resources can reach with valid strength at other times.

[0097] In CA, two or more CCs are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs. When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment / re-establishment / handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment / handover, one serving cell provides the security input. This cell is referred to as the Primary Cell (PCell). The PCell is a cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Depending on UE capabilities, Secondary Cells (SCells) can be configured to form together with the PCell a set of serving cells. An SCell is a cell providing additional radio resources on top of Special Cell (SpCell). The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. For Dual Connectivity (DC) operation, the term SpCell refers to the PCell of the Master Cell Group (MCG) or the Primary SCell (PSCell) of the Secondary Cell Group (SCG). An SpCell supports Physical Uplink Control Channel (PUCCH) transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node, comprised of the SpCell (PCell) and optionally one or more SCells. The SCG is the subset of serving cells associated with a secondary node, comprised of the PSCell and zero or more SCells, for a UE configured with DC. For a UE in RRC_CONNECTED not configured with CA / DC, there is only one serving cell comprised of the PCell. For a UE in RRC_CONNECTED configured with CA / DC, the term "serving cells" is used to denote the set of cells comprised of the SpCell(s) and all SCells. In DC, two MAC entities are configured in a UE: one for the MCG and one for the SCG.

[0098] FIG. 7 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure are applied.

[0099] Referring to FIG. 7, "RB" denotes a radio bearer, and "H" denotes a header. Radio bearers are categorized into two groups: DRBs for user plane data and SRBs for control plane data. The MAC PDU is transmitted / received using radio resources through the PHY layer to / from an external device. The MAC PDU arrives to the PHY layer in the form of a transport block.

[0100] In the PHY layer, the uplink transport channels UL-SCH and Random Access Channel (RACH) are mapped to their physical channels Physical Uplink Shared Channel (PUSCH) and Physical Random Access Channel (PRACH), respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to Physical Downlink Shared Channel (PDSCH), Physical Broadcast Channel (PBCH) and PDSCH, respectively. In the PHY layer, Uplink Control Information (UCI) is mapped to PUCCH, and Downlink Control Information (DCI) is mapped to Physical Downlink Control Channel (PDCCH). A MAC PDU related to UL-SCH is transmitted by a UE via a PUSCH based on an UL grant, and a MAC PDU related to DL-SCH is transmitted by a BS via a PDSCH based on a DL assignment.

[0101] Cell level mobility requires explicit RRC signaling to be triggered, i.e., handover.

[0102] FIG. 8 shows an example of inter-gNB handover procedures to which implementations of the present disclosure are applied.

[0103] For inter-gNB handover, the signaling procedures consist of at least the following elemental components described in FIG. 8.

[0104] 1. Step 1: The source gNB initiates handover and issues a HANDOVER REQUEST over the Xn interface.

[0105] 2. Step 2: The target gNB performs admission control and provides the new RRC configuration as part of the HANDOVER REQUEST ACKNOWLEDGE.

[0106] 3. Step 3: The source gNB provides the RRC configuration to the UE by forwarding theRRCReconfigurationmessage received in the HANDOVER REQUEST ACKNOWLEDGE. TheRRCReconfigurationmessage includes at least cell ID and all information required to access the target cell so that the UE can access the target cell without reading system information. For some cases, the information required for contention-based and contention-free random access can be included in theRRCReconfigurationmessage. The access information to the target cell may include beam specific information, if any.

[0107] 4. Step 4: The UE moves the RRC connection to the target gNB and replies with theRRCReconfigurationComplete.

[0108] User data may also be sent in step 4 if the grant allows.

[0109] Beam level mobility does not require explicit RRC signaling to be triggered. Beam level mobility can be within a cell, or between cells, the latter is referred to as Inter-Cell Beam Management (ICBM). For ICBM, a UE can receive or transmit UE dedicated channels / signals via a Transmission / Reception Point (TRP) associated with a Physical Cell ID (PCI) different from the PCI of a serving cell, while non-UE-dedicated channels / signals can only be received via a TRP associated with a PCI of the serving cell. The gNB provides via RRC signaling the UE with measurement configuration containing configurations of Synchronization Signal Block (SSB) / Channel State Information (CSI) resources and resource sets, reports and trigger states for triggering channel and interference measurements and reports. In case of ICBM, a measurement configuration includes SSB resources associated with PCIs different from the PCI of a serving cell. Beam level mobility is then dealt with at lower layers by means of physical layer and MAC layer control signaling, and RRC is not required to know which beam is being used at a given point in time.

[0110] SSB-based beam level mobility is based on　the SSB associated to the initial DL BWP and can only be　configured for　the initial DL BWPs and for　DL BWPs　containing the SSB associated to the initial DL BWP. For　other DL BWPs, beam level mobility can only be performed based on CSI-Reference Signal (RS).

[0111] A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution condition(s) upon receiving the CHO configuration, and stops evaluating the execution condition(s) once a handover is executed.

[0112] The following principles apply to CHO:

[0113] - The CHO configuration contains the configuration of CHO candidate cell(s) generated by the candidate gNB(s) and execution condition(s) generated by the source gNB.

[0114] - An execution condition may consist of one or two trigger condition(s) (CHO events A3 / ). Only single RS type is supported and at most two different trigger quantities (e.g., Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ), RSRP and Signal-to-Interference plus Noise Ratio (SINR), etc.) can be configured simultaneously for the evaluation of CHO execution condition of a single candidate cell.

[0115] - Before any CHO execution condition is satisfied, upon reception of HO command (without CHO configuration), the UE executes the HO procedure, regardless of any previously received CHO configuration.

[0116] - While executing CHO, i.e., from the time when the UE starts synchronization with target cell, the UE does not monitor source cell.

[0117] L1 / L2 Triggered Mobility (LTM) is a procedure in which a gNB receives L1 measurement report(s) from a UE, and on their basis the gNB changes UE's serving cell by a cell switch command signaled via a MAC CE. The cell switch command indicates an LTM candidate cell configuration that the gNB previously prepared and provided to the UE through RRC signaling. Then the UE switches to the target cell according to the cell switch command. The LTM procedure can be used to reduce the mobility latency.

[0118] When configured by the network, it is possible to activate Transmission Configuration Index (TCI) states of one or multiple cells that are different from the current serving cell. For instance, the TCI states of the LTM candidate cells can be activated in advance before any of those cells become the serving cell. This allows the UE to be DL synchronized with those cells, thereby facilitating a faster cell switch to one of those cells when cell switch is triggered.

[0119] When configured by the network, it is possible to initiate UL Timing Advance (TA) acquisition procedure to one or multiple cells that are different from the current serving cell. For instance, the network may request the UE to perform early TA acquisition of a candidate cell before a cell switch. The early TA acquisition is triggered by PDCCH order or realized through UE-based TA measurement. In the former case, the gNB to which the candidate cell belongs calculates the TA value and sends it to the gNB to which the serving cell belongs. The serving cell sends the TA value in the LTM cell switch command MAC CE when triggering LTM cell switch. In the latter case, the UE applies the TA value measured by itself and performs RACH-less LTM upon receiving the cell switch command.

[0120] If UE-based TA measurement is configured, the UE performs RACH-less LTM upon receiving the cell switch command. Otherwise, the UE determines whether to access the target cell with the RA procedure depending on whether a TA value is provided in the cell switch command. For RACH-less LTM, the UE accesses the target cell via a configured grant provided in the LTM candidate cell configuration and selects the configured grant occasion associated with the beam indicated in the cell switch command. If the LTM candidate cell configuration does not include a configured grant, the UE may monitor PDCCH for dynamic scheduling from the target cell upon LTM cell switch. Before RACH-less LTM procedure completion, the UE may not trigger random access procedure if it does not have a valid PUCCH resource for triggered Scheduling Requests (SRs).

[0121] The following principles apply to LTM:

[0122] - The UE does not update its security key after an intra-gNB LTM cell switch.

[0123] - Subsequent LTM is supported.

[0124] LTM supports both intra-gNB-Distributed Unit (DU) and intra-gNB-Centralized Unit (CU) inter-gNB-DU mobility. LTM supports both intra-frequency and inter-frequency mobility, including mobility to inter-frequency cell that is not a current serving cell. The following scenarios are supported:

[0125] - PCell change in non-CA scenario and non-DC scenario,

[0126] - PCell change in CA scenario,

[0127] - DC scenario, MCG PCell change and SCG PSCell change without MN involvement case (i.e., intra-SN PSCell change).

[0128] While the UE has stored LTM candidate cell configurations, the UE can also execute any L3 handover command sent by the network.

[0129] FIG. 9 shows an example of signaling procedure for LTM to which implementations of the present disclosure are applied.

[0130] Cell switch command is conveyed in a MAC Control Element (CE), which contains the necessary information to perform the LTM cell switch.

[0131] Subsequent LTM is done by repeating the early synchronization, LTM cell switch execution, and LTM cell switch completion steps without releasing other LTM candidate cell configurations after each LTM cell switch completion.

[0132] The signaling procedure for LTM is as follows.

[0133] 1. Step 1: The UE sends aMeasurementReportmessage to the gNB. The gNB decides to configure LTM and initiates candidate cell(s) preparation.

[0134] 2. Step 2: The gNB transmits anRRCReconfigurationmessage to the UE including the LTM candidate cell configurations of one or multiple candidate cells.

[0135] 3. Step 3: The UE stores the LTM candidate cell configurations and transmits anRRCReconfigurationCompletemessage to the gNB.

[0136] 4a. Step 4a: The UE may perform DL synchronization with the candidate cell(s) before receiving the cell switch command.

[0137] 4b. Step 4b: When UE-based TA measurement is configured, the UE may acquire the TA value(s) of the candidate cell(s) by measurement. Otherwise, the UE may perform early TA acquisition with the candidate cell(s) as requested by the network before receiving the cell switch command. This may be done via Contention-Free Random Access (CFRA) triggered by a PDCCH order from the source cell, following which the UE may send preamble towards the indicated candidate cell. In order to minimize the data interruption of the source cell due to CFRA towards the candidate cell(s), the UE may not receive random access response from the network for the purpose of TA value acquisition and the TA value of the candidate cell is indicated in the cell switch command. The UE may not maintain the TA timer for the candidate cell and relies on network implementation to guarantee the TA validity.

[0138] 5. Step 5: The UE performs L1 measurements on the configured candidate cell(s) and transmits L1 measurement reports to the gNB. L1 measurement should be performed as long as RRC reconfiguration (step 2) is applicable.

[0139] 6. Step 6: The gNB decides to execute cell switch to a target cell and transmits a MAC CE triggering cell switch by including the candidate configuration index of the target cell. The UE switches to the target cell and applies the configuration indicated by candidate configuration index.

[0140] 7. Step 7: The UE may perform the random access procedure towards the target cell, if the UE does not have valid TA of the target cell. The UE may perform CFRA if the LTM cell switch command MAC CE contains information for CFRA.

[0141] 8. Step 8: The UE completes the LTM cell switch procedure by sendingRRCReconfigurationCompletemessage to target cell. If the UE has performed a random access procedure in step 7, the UE considers that LTM cell switch execution is successfully completed when the random access procedure is successfully completed. For RACH-less LTM, the UE considers that LTM cell switch execution is successfully completed when the UE determines that the network has successfully received its first UL data. The UE determines successful reception of its first UL data by receiving a PDCCH addressing the UE's Cell Radio Network Temporary Identity (C-RNTI) in the target cell, which schedules a new transmission following the first UL data. The PDCCH carries either a DL assignment or an UL grant addressing the same HARQ process as the first UL data.

[0142] The steps 4-8 can be performed multiple times for subsequent LTM using the LTM candidate cell configuration(s) provided in step 2.

[0143] Table 5 shows an example ofLTM-ConfigInformation Element (IE). TheLTM-ConfigIE may be used to provide LTM candidate configurations.

[0144] -- ASN1START-- TAG-LTM-CONFIG-STARTLTM-Config-r18 ::= SEQUENCE {ltm-ReferenceConfiguration-r18 SetupRelease {ReferenceConfiguration-r18} OPTIONAL, -- Need Mltm-CandidateToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF LTM-CandidateId-r18 OPTIONAL, -- Need Nltm-CandidateToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF LTM-Candidate-r18 OPTIONAL, -- Need Nltm-ServingCellNoResetID-r18 INTEGER (1..maxNrofLTM-Configs-r18-plus-1) OPTIONAL, -- Cond FirstLTM-Onlyltm-CSI-ResourceConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ResourceConfigurations-r18)) OF LTM-CSI-ResourceConfig-r18 OPTIONAL, -- Need Nltm-CSI-ResourceConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ResourceConfigurations-r18)) OF LTM-CSI-ResourceConfigId-r18 OPTIONAL, -- Need NattemptLTM-Switch-r18 ENUMERATED {true} OPTIONAL, -- Cond LTM-MCGltm-ServingCellUE-MeasuredTA-ID-r18 INTEGER (1..maxNrofLTM-Configs-r18-plus-1) OPTIONAL, -- Cond LTM...}-- TAG-LTM-CONFIG-STOP-- ASN1STOP

[0145] Table 6 shows an example ofLTM-CandidateIE. The IELTM-Candidateconcerns a LTM candidate configuration to add or modify.

[0146] -- ASN1START-- TAG-LTM-CANDIDATE-STARTLTM-Candidate-r18 ::= SEQUENCE {ltm-CandidateId-r18 LTM-CandidateId-r18,ltm-CandidatePCI-r18 PhysCellId,ltm-SSB-Config-r18 LTM-SSB-Config-r18 OPTIONAL, -- Need Mltm-CandidateConfig-r18 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Need Mltm-ConfigComplete-r18 ENUMERATED {true} OPTIONAL, -- Need Rltm-EarlyUL-SyncConfig-r18 SetupRelease { EarlyUL-SyncConfig-r18 } OPTIONAL, -- Need Mltm-EarlyUL-SyncConfigSUL-r18 SetupRelease { EarlyUL-SyncConfig-r18 } OPTIONAL, -- Need Mltm-NoResetID-r18 INTEGER (1..maxNrofLTM-Configs-r18-plus-1) OPTIONAL, -- Need Mltm-DL-OrJointTCI-StateToAddModList-r18 SEQUENCE (SIZE (1..maxNrofCandidateTCI-State-r18)) OF CandidateTCI-State-r18 OPTIONAL, -- Need Nltm-DL-OrJointTCI-StateToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofCandidateTCI-State-r18)) OF TCI-StateId OPTIONAL, -- Need Nltm-UL-TCI-StatesToAddModList-r18 SEQUENCE (SIZE (1..maxNrofCandidateUL-TCI-r18)) OF CandidateTCI-UL-State-r18 OPTIONAL, -- Need Nltm-UL-TCI-StatesToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofCandidateUL-TCI-r18)) OF TCI-UL-StateId-r17 OPTIONAL, -- Need Nltm-nzp-CSI-RS-ResourceToAddModList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-Resource OPTIONAL, -- Need Nltm-nzp-CSI-RS-ResourceToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-ResourceId OPTIONAL, -- Need Nltm-nzp-CSI-RS-ResourceSetToAddModList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSet OPTIONAL, -- Need Nltm-nzp-CSI-RS-ResourceSetToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, -- Need NpathlossReferenceRS-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-r17 OPTIONAL, -- Need NpathlossReferenceRS-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-Id-r17 OPTIONAL, -- Need Nltm-UE-MeasuredTA-ID-r18 INTEGER (1..maxNrofLTM-Configs-r18-plus-1) OPTIONAL, -- Need M...}LTM-SSB-Config-r18 ::= SEQUENCE {ssbFrequency-r18 ARFCN-ValueNR,subcarrierSpacing-r18 SubcarrierSpacing,ssb-Periodicity-r18 ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1} OPTIONAL, -- Need Rssb-PositionsInBurst-r18 CHOICE {shortBitmap BIT STRING (SIZE (4)),mediumBitmap BIT STRING (SIZE (8)),longBitmap BIT STRING (SIZE (64))} OPTIONAL, -- Need Rss-PBCH-BlockPower-r18 INTEGER (-60..50) OPTIONAL, -- Need R...}-- TAG-LTM-CANDIDATE-STOP-- ASN1STOP

[0147] Table 7 shows an example ofLTM-CandidateIdIE. The IELTM-CandidateIdis used to identify an LTM candidate configuration.

[0148] -- ASN1START-- TAG-LTM-CANDIDATEID-STARTLTM-CandidateId-r18 ::= INTEGER (1..maxNrofLTM-Configs-r18)-- TAG-LTM-CANDIDATEID-STOP-- ASN1STOP

[0149] Table 8 shows an example ofLTM-CSI-ReportConfigIE. The IELTM-CSI-ReportConfigis used to configure report on the cell in which theLTM-CSI-ReportConfigis included.

[0150] -- ASN1START-- TAG-LTM-CSI-REPORTCONFIG-STARTLTM-CSI-ReportConfig-r18 ::= SEQUENCE {ltm-CSI-ReportConfigId-r18 LTM-CSI-ReportConfigId-r18,ltm-ResourcesForChannelMeasurement-r18 LTM-CSI-ResourceConfigId-r18,ltm-ReportConfigType-r18 CHOICE {periodic-r18 SEQUENCE {reportSlotConfig-r18 CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUCCH-r18 SEQUENCE {reportSlotConfig-r18 CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource},semiPersistentOnPUSCH-r18 SEQUENCE {reportSlotConfig-r18 CSI-ReportPeriodicityAndOffset,reportSlotOffsetList-r18 SEQUENCE (SIZE (1..maxNrofUL-Allocations-r16)) OF INTEGER (0..128),reportSlotOffsetListDCI-0-2-r18 SEQUENCE (SIZE (1..maxNrofUL-Allocations-r16)) OF INTEGER (0..128),reportSlotOffsetListDCI-0-1-r18 SEQUENCE (SIZE (1..maxNrofUL-Allocations-r16)) OF INTEGER (0..128),p0alpha P0-PUSCH-AlphaSetId},aperiodic-r18 SEQUENCE {reportSlotOffsetList-r18 SEQUENCE (SIZE (1..maxNrofUL-Allocations-r16)) OF INTEGER (0..128),reportSlotOffsetListDCI-0-2-r18 SEQUENCE (SIZE (1..maxNrofUL-Allocations-r16)) OF INTEGER (0..128),reportSlotOffsetListDCI-0-1-r18 SEQUENCE (SIZE (1..maxNrofUL-Allocations-r16)) OF INTEGER (0..128)}},ltm-ReportContent-r18 LTM-ReportContent-r18,...}LTM-ReportContent-r18 ::= SEQUENCE {nrOfReportedCells-r18 ENUMERATED {n1,n2,n3,n4},nrOfReportedRS-PerCell-r18 ENUMERATED {n1,n2,n3,n4},spCellInclusion-r18 ENUMERATED {true} OPTIONAL -- Need R}-- TAG-LTM-CSI-REPORTCONFIG-STOP-- ASN1STOP

[0151] Table 9 shows an example ofLTM-CSI-ReportConfigIdIE. The IELTM-CSI-ReportConfigIdis used to identify anLTM-CSI-ReportConfig.

[0152] -- ASN1START-- TAG-LTM-CSI-REPORTCONFIGID-STARTLTM-CSI-ReportConfigId-r18 ::= INTEGER (0..maxNrofLTM-CSI-ReportConfigurations-1-r18)-- TAG-LTM-CSI-REPORTCONFIGID-STOP-- ASN1STOP

[0153] Table 10 shows an example ofLTM-CSI-ResourceConfigIE. TheLTM-CSI-ResourceConfigIE defines a group of one or more CSI resources for one or more LTM candidate configurations.

[0154] -- ASN1START-- TAG-LTM-CSI-RESOURCECONFIG-STARTLTM-CSI-ResourceConfig-r18 ::= SEQUENCE {ltm-CSI-ResourceConfigId-r18 LTM-CSI-ResourceConfigId-r18,ltm-CSI-SSB-ResourceSet-r18 LTM-CSI-SSB-ResourceSet-r18,...}LTM-CSI-SSB-ResourceSet-r18 ::= SEQUENCE {ltm-CSI-SSB-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-SSB-ResourcesPerSet-r18)) OF SSB-Index,ltm-CandidateIdList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-SSB-ResourcesPerSet-r18)) OF LTM-CandidateId-r18,...}-- TAG-LTM-CSI-RESOURCECONFIG-STOP-- ASN1STOP

[0155] Table 11 shows an example ofLTM-CSI-ResourceConfigIdIE. The IELTM-CSI-ResourceConfigIdis used to identify anLTM-CSI-ResourceConfig.

[0156] -- ASN1START-- TAG-LTM-CSI-RESOURCECONFIGID-STARTLTM-CSI-ResourceConfigId-r18 ::= INTEGER (0..maxNrofLTM-CSI-ResourceConfigurations-r18-1)-- TAG-LTM-CSI-RESOURCECONFIGID-STOP-- ASN1STOP

[0157] The UE may be configured with one or more measurement resources / targets / objects (e.g., cell, beam, RS, etc.). The UE may be configured with one or more report conditions. Each report condition may be associated with at least one measurement resource. The UE may evaluate the report condition by performing measurement of the associated measurement resource. If the report condition is met for the associated measurement resource, the UE may trigger a measurement report procedure. Upon initiating the measurement report, the UE may transmit a measurement report including measurement results related to the measurement resource. For example, the measurement results related to the measurement resource may include beam identifier, beam quality and / or report condition information.

[0158] In the measurement reporting triggered by beam-related event condition, measurement report may be triggered frequently due to multiple beams satisfying the event condition at different times.

[0159] FIG. 10 shows an example of measurement reporting triggered by beam-related event condition to which implementations of the present disclosure are applied.

[0160] Referring to FIG. 10, beam A may satisfy an entering condition related to a first event and a first TTT corresponding to the first event may start accordingly. While the first TTT is running, beam B may also satisfy an entering condition related to a second event (which may be same as the first event or different from the first event) and a second TTT corresponding to the second event may start accordingly.

[0161] Then, the entering condition related to the first event may be continuously met for the first TTT, and upon expiry of the first TTT, a first measurement reporting including beam A as triggering beam may be triggered. But, shortly after, the entering condition related to the second event may also be continuously met for the second TTT, and upon expiry of the second TTT, a second measurement reporting including beam B as triggering beam may also be triggered. Consequently, signaling overhead may be increased.

[0162] In addition, in event triggered measurement reporting for LTM, when multiple L1 measurement reports are triggered by the same report configuration, the UE may create and transmit L1 measurement report MAC CEs corresponding to the triggered measurement reports. In this case, the two L1 measurement report MAC CEs may contain a lot of common information, resulting in signaling waste.

[0163] To address the problem described above, a method for controlling triggering of measurement reporting based on beam related event condition and Time-To-Trigger (TTT) associated with a pair of event instance and measurement target resource is proposed in the present disclosure.

[0164] In the present disclosure, a Measurement Target Resource (MTR) may be defined. An RS may be MTR. Additionally and / or alternatively, a set of RSs may be MTR. Additionally and / or alternatively, a beam may be MTR. Additionally and / or alternatively, a set of beams may be MTR. Additionally and / or alternatively, a cell may be MTR. Additionally and / or alternatively, a set of cells may be MTR. The MTR may be replaced with other names, such as a measurement target, a measurement resource, or a measurement object.

[0165] According to implementations of the present disclosure, the UE may receive a configuration related to measurement reporting. The configuration may include information related to one or more events to be evaluated. Each event may be associated with at least one MTR. The event may be associated with at least one MTR. The UE may evaluate the configured event for the associated measurement resources.

[0166] According to implementations of the present disclosure, an MTR may satisfy an entering condition of the event. In this case, at least one of the following operations may be performed.

[0167] 1) The UE may include the MTR in the entered MTR list.

[0168] 2) For the MTR included in the entered MTR list, the UE may further include MTR state information. For example, the MTR state information may indicate that TTT is not yet expired for the MTR (i.e. the MTR is not a triggering MTR but entered MTR).

[0169] 3) The UE may start TTT for the MTR. Regarding whether to start TTT, following alternatives may be considered.

[0170] - Alt S1: The UE may always start TTT for the MTR.

[0171] - Alt S2: The UE may start TTT for the MTR if TTT for other MTR associated with the same event is not running. The UE may not start TTT for the MTR if TTT for other MTR associated with the same event is already running.

[0172] - Alt S3: The UE may start TTT for the MTR if periodical timer for the event is not running. The UE does not start TTT for the MTR if periodical timer for the event is already running.

[0173] According to implementations of the present disclosure, the MTR included in the entered MTR list may not satisfy the entering condition of the event anymore. In this case, at least one of the following operations may be performed.

[0174] 1) The UE may stop the TTT associated with the MTR and the event.

[0175] 2) The UE may remove the MTR from the entered MTR list.

[0176] According to implementations of the present disclosure, in the MTR included in the triggered MTR list may satisfy a leaving condition of the event for a duration of TTT. In this case, at least one of the following operations may be performed.

[0177] 1) The UE may remove the MTR from the triggered MTR list.

[0178] 2) The UE may trigger / initiate measurement reporting.

[0179] 3) If a network configuration to enable / disablereportingUponLeaving(orreportOnLeave) is applied, the UE may trigger / initiate measurement reporting only if thereportingUponLeavingis enabled by the network configuration.

[0180] 4) The UE may trigger / initiate measurement reporting only when a measurement report was previously sent to the network for the concerned MTR (entering condition).

[0181] According to implementations of the present disclosure, the MTR may have satisfied the entering condition of the event for a duration of TTT (i.e., TTT expiry). In this case, at least one of the following operations may be performed.

[0182] 1) For the MTR associated with the expired TTT within the entered MTR list, the UE may change the MTR state information, if included. For example, the MTR state information may indicate that the TTT is expired for the MTR (Previously, the MTR state information may indicate that TTT is not expired for the MTR). That is, the MTR is now a triggering MTR.

[0183] 2) The UE may trigger / initiate a measurement reporting.

[0184] 3) If periodical reporting is configured for the event, the UE may start a periodical reporting timer.

[0185] According to implementations of the present disclosure, with respect to handling of other running TTT associated with the same event, upon expiry of TTT associated with the event, the following alternatives may be considered.

[0186] - Alt T1: The UE may keep running all the running TTTs associated with the same event.

[0187] - Alt T2: The UE may stop running TTT associated with the same event. The UE may stop all the running TTT associated with the same event. Or, the UE may stop a running TTT if the information related to the MTR associated with the running TTT is included in the measurement report triggered by the TTT expiry. If the information related to the MTR associated with the running TTT is not included in the measurement reporting triggered by the expiry of the TTT, the UE may keep the running TTT. The stopping of running TTT associated with the same event due to expiry of other TTT may be executed based on remaining time of the running TTT until expiry. For example, if the remaining time is less than a threshold, the UE may stop the running TTT, and if not, the UE may not stop the running TTT.

[0188] The network may configure which alternative should be applied, e.g., by configuring the UE whether to keep the other running TTT or not upon expiry of TTT.

[0189] According to implementations of the present disclosure, upon expiry of other TTT associated with the same event, at least one of the following operations may be performed.

[0190] 1) The UE may include the MTR associated with the expired TTT in the triggered MTR list.

[0191] 2) The UE may trigger / initiate a measurement reporting. Regarding whether to trigger / initiate a measurement reporting, the following alternatives may be considered:

[0192] - Alt E1: The UE may trigger / initiate a measurement reporting.

[0193] - Alt E2: The UE may trigger / initiate / transmit a measurement reporting if periodical reporting timer is not running for the same event. The UE may not trigger / initiate / transmit a measurement reporting if periodical reporting timer is already running for the same event.

[0194] When Alt T1 mentioned above, i.e., keep running all the running TTTs associated with the same event, is applied, applying Alt E2 may be more desirable to restrict triggering / initiating an unnecessary / non-essential measurement reporting.

[0195] Upon expiry of the periodic reporting timer, the UE may trigger / initiated a measurement reporting.

[0196] According to implementations of the present disclosure, upon triggering / initiating the measurement reporting, the UE may transmit a measurement report.

[0197] The measurement report may include information related to the MTR associated with the expired TTT. The information related to the MTR associated with the expired TTT may be derived based on information within the entered MTR list (i.e., based on triggered MTR list).

[0198] The information related to the MTR associated with the expired TTT may include at least one of the followings.

[0199] - Resource identification information indicating the MTR;

[0200] - Quality of the MTR (e.g., RSRP, RSRQ, SINR, etc.);

[0201] - Information indicating the event associated with the TTT;

[0202] - Information indicating that TTT is expired for the MTR (or information indicating that the MTR is a triggering MTR); or

[0203] - Information related to time when the TTT is expired for the MTR.

[0204] The measurement report may further include information related to other MTR. The other MTR may be associated with a running TTT, but not with the expired TTT. The running TTT and the expired TTT may be associated with the same event, for which the entering condition of the event is met. The other MTR may be an MTR for which TTT is running (Alt 1), or an MTR for which TTT just stops (Alt 2). The network may configure the UE with whether to include the information related to the other MTR associated with the running TTT.

[0205] The information related to the other MTR associated with the running TTT may include at least one of the followings.

[0206] - Resource identification information indicating the other MTR;

[0207] - Quality of the other MTR (e.g., RSRP, RSRQ, SINR, etc.);

[0208] - Information indicating the event associated with the TTT;

[0209] - Information indicating that TTT is not expired for the other MTR (or information indicating that the other MTR is not a triggering MTR but entered MTR); or

[0210] - Time information indicating the remaining time of the running TTT until expiry (or equivalently the elapsed time of the TTT running since the TTT initiation), possibly in quantized manners.

[0211] The measurement report may include information related to the other MTR only if the remaining time of the running until expiry is less than a threshold. The threshold may be configured by the network.

[0212] The measurement report may be transmitted via at least one of UCI, MAC CE or RRC message.

[0213] The following drawings are created to explain specific embodiments of the present disclosure. The names of the specific devices or the names of the specific signals / messages / fields shown in the drawings are provided by way of example, and thus the technical features of the present disclosure are not limited to the specific names used in the following drawings.

[0214] An embodiment of the present disclosure related to a specific drawing described below may be combined with various embodiments of the present disclosure related to other drawings, and some descriptions, functions, procedures, proposals, methods and / or operations of the embodiment may be omitted.

[0215] FIG. 11 shows an example of a method to which implementations of the present disclosure are applied.

[0216] In step S1100, the method comprises receiving one or more measurement target resources and one or more report configuration including one or more event conditions related to the one or more measurement target resources from a network.

[0217] In step S1110, the method comprises performing measurements based on one or more measurement targets. A first measurement reporting is considered to be triggered based on a first event condition associated with a first report configuration being fulfilled for a first measurement target, and a second measurement reporting is considered to be triggered based on a second event condition associated with the first report configuration being fulfilled for a second measurement target.

[0218] In step S1120, based on the first measurement reporting and the second measurement reporting which have been considered to be triggered for the first report configuration, the method comprises transmitting a measurement report MAC CE to the network based on the first report configuration.

[0219] In some implementations, a third measurement reporting may be considered to be triggered based on an event condition associated with a second report configuration being fulfilled for a third measurement target, and a second measurement report MAC CE may be transmitted to the network based on the second report configuration. That is, when measurement reporting is considered to be triggered for different report configurations (i.e., the first report configuration and the second report configuration), different / separate measurement report MAC CEs may be transmitted.

[0220] In some implementations, the first event condition may be fulfilled for a first duration (e.g., first TTT). The second event condition may be fulfilled for a second duration (e.g., second TTT).

[0221] In some implementations, the first measurement target may be included in a triggered beam list (e.g.,MR_LIST) based on the first event condition being fulfilled for the first measurement target. The second measurement target may be included in a triggered beam list (e.g.,MR_LIST) based on the second event condition being fulfilled for the second measurement target.

[0222] In some implementations, a periodical reporting timer may start upon the first measurement reporting being considered to be triggered. A measurement reporting may be considered to be triggered upon expiry of the periodical reporting timer.

[0223] In some implementations, the measurement report MAC CE may include information related to at least one of the first measurement target or the second measurement target. The information related to at least one of the first measurement target or the second measurement target may include resource identification information indicating the first measurement target or the second measurement target. The information related to at least one of the first measurement target or the second measurement target may include a quality of the first measurement target or the second measurement target. The information related to at least one of the first measurement target or the second measurement target may include event information indicating an event related to the first event condition or the second condition.

[0224] In some implementations, the first event condition or the second condition may be any one of an entering condition or a leaving condition.

[0225] In some implementations, the one or more measurement targets includes one or more RSs or one or more cells.

[0226] Furthermore, the wireless device may be implemented by the first wireless device 100 shown in FIG. 2 and / or the UE 100 shown in FIG. 3. The wireless device may be in communication with at least one of a mobile device, a network, and / or autonomous vehicles other than the wireless device.

[0227] The wireless device may comprise at least one transceiver, at least one processor, and at least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the wireless device to perform the method described in FIG. 11.

[0228] More specifically, the wireless device receives one or more measurement target resources and one or more report configuration including one or more event conditions related to the one or more measurement target resources from a network.

[0229] The wireless device performs measurements based on one or more measurement targets. A first measurement reporting is considered to be triggered based on a first event condition associated with a first report configuration being fulfilled for a first measurement target, and a second measurement reporting is considered to be triggered based on a second event condition associated with the first report configuration being fulfilled for a second measurement target.

[0230] Based on the first measurement reporting and the second measurement reporting which have been considered to be triggered for the first report configuration, the wireless device transmits a measurement report MAC CE to the network based on the first report configuration.

[0231] In some implementations, a third measurement reporting may be considered to be triggered based on an event condition associated with a second report configuration being fulfilled for a third measurement target, and a second measurement report MAC CE may be transmitted to the network based on the second report configuration. That is, when measurement reporting is considered to be triggered for different report configurations (i.e., the first report configuration and the second report configuration), different / separate measurement report MAC CEs may be transmitted.

[0232] In some implementations, the first event condition may be fulfilled for a first duration (e.g., first TTT). The second event condition may be fulfilled for a second duration (e.g., second TTT).

[0233] In some implementations, the first measurement target may be included in a triggered beam list (e.g.,MR_LIST) based on the first event condition being fulfilled for the first measurement target. The second measurement target may be included in a triggered beam list (e.g.,MR_LIST) based on the second event condition being fulfilled for the second measurement target.

[0234] In some implementations, a periodical reporting timer may start upon the first measurement reporting being considered to be triggered. A measurement reporting may be considered to be triggered upon expiry of the periodical reporting timer.

[0235] In some implementations, the measurement report MAC CE may include information related to at least one of the first measurement target or the second measurement target. The information related to at least one of the first measurement target or the second measurement target may include resource identification information indicating the first measurement target or the second measurement target. The information related to at least one of the first measurement target or the second measurement target may include a quality of the first measurement target or the second measurement target. The information related to at least one of the first measurement target or the second measurement target may include event information indicating an event related to the first event condition or the second condition.

[0236] In some implementations, the first event condition or the second condition may be any one of an entering condition or a leaving condition.

[0237] In some implementations, the one or more measurement targets includes one or more RSs or one or more cells.

[0238] Furthermore, the method described above in FIG. 11 may be performed by control of a processing apparatus. The processing apparatus may be implemented by the processor 102 included in the first wireless device 100 shown in FIG. 2 and / or the processor 102 included in the UE 100 shown in FIG. 3.

[0239] The processing apparatus comprises at least one processor that is integrated with a wireless device, and at least one memory comprising processor-executable instructions stored thereon that are configured to cause the at least one processor to perform the method described in FIG. 11.

[0240] Furthermore, the method described above in FIG. 11 may be performed by a software code 105 stored in the memory 104 included in the first wireless device 100 shown in FIG. 2.

[0241] The technical features of the present disclosure may be embodied directly in hardware, in a software executed by a processor, or in a combination of the two. For example, a method performed by a wireless device in a wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, a software may reside in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable disk, a CD-ROM, or any other storage medium.

[0242] Some example of storage medium may be coupled to the processor such that the processor can read information from the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. For other example, the processor and the storage medium may reside as discrete components.

[0243] The computer-readable medium may include a tangible and non-transitory computer-readable storage medium.

[0244] For example, non-transitory computer-readable media may include RAM such as Synchronous DRAM (SDRAM), ROM, Non-Volatile RAM (NVRAM), EEPROM, flash memory, magnetic or optical data storage media, or any other medium that can be used to store instructions or data structures. Non-transitory computer-readable media may also include combinations of the above.

[0245] In addition, the method described herein may be realized at least in part by a computer-readable communication medium that carries or communicates code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer.

[0246] According to some implementations of the present disclosure, a non-transitory Computer-Readable Medium (CRM) stores instructions that, based on being executed by at least one processor, perform the method described in FIG. 11.

[0247] FIG. 12 shows an example of another method to which implementations of the present disclosure are applied.

[0248] In step S1200, the method comprises transmitting one or more measurement target resources and one or more report configuration including one or more event conditions related to the one or more measurement target resources to a network. Measurements are performed based on one or more measurement targets. A first measurement reporting is considered to be triggered based on a first event condition associated with a first report configuration being fulfilled for a first measurement target, and a second measurement reporting is considered to be triggered based on a second event condition associated with the first report configuration being fulfilled for a second measurement target.

[0249] In step S1210, based on the first measurement reporting and the second measurement reporting which have been considered to be triggered for the first report configuration, the method comprises receiving a measurement report MAC CE from the wireless device based on the first report configuration.

[0250] Furthermore, the method described above in FIG. 12 may be performed by a base station. The base station may be implemented by the second wireless device 200 shown in FIG. 2.

[0251] The base station may comprise at least one transceiver, at least one processor, and at least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the base station to perform the method described in FIG. 12.

[0252] More specifically, the base station transmits one or more measurement target resources and one or more report configuration including one or more event conditions related to the one or more measurement target resources to a network. Measurements are performed based on one or more measurement targets. A first measurement reporting is considered to be triggered based on a first event condition associated with a first report configuration being fulfilled for a first measurement target, and a second measurement reporting is considered to be triggered based on a second event condition associated with the first report configuration being fulfilled for a second measurement target.

[0253] Based on the first measurement reporting and the second measurement reporting which have been considered to be triggered for the first report configuration, the base station receives a measurement report MAC CE from the wireless device based on the first report configuration.

[0254] According to implementations of the present disclosure, the followings may be provided.

[0255] The network may configure an RRC_CONNECTED UE to perform L1 beam level measurements for LTM candidate cell(s) and / or serving cell, and report the corresponding measurement results in accordance with the event triggered L1 measurement configuration. The measurement report may be used for indicating to serving gNB of the L1 measurement results from the serving cell and / or candidate cell(s). The measurement configuration may be provided by means of RRC dedicated signaling.

[0256] The network may configure the UE to report the following measurement information based on SS / PBCH block(s):

[0257] - Measurement results per SS / PBCH block;

[0258] - SS / PBCH block(s) resource indicator (SSBRI).

[0259] The network may configure the UE to report the following measurement information based on CSI-RS resources:

[0260] - Measurement results per CSI-RS resource;

[0261] - CSI-RS resource indicator (CRI).

[0262] RRC may configure the following parameters in theLTM-CSI-ReportConfigfor L1 measurement and event triggered L1 measurement reporting:

[0263] -ltm-ResourcesForChannelMeasurementfor the LTM resource configuration containing the RS(s) of LTM candidate cell(s) that may be measured for the event;

[0264] -eventTriggeredfor the event-triggered measurement report;

[0265] -eventLTM2,eventLTM3,eventLTM4,eventLTM5: events for the event-triggered measurement report;

[0266] -timeToTrigger(TTT): time during which an entering / leaving condition needs to be consistently satisfied for reporting event triggered L1 measurement report or for cell switch execution to be met;

[0267] -ltm-CandidateReportConfigList: List of report configurations for LTM candidate IDs;

[0268] -ltm-EventTriggeredPeriodicReport: whether the event triggered L1 measurement report is sent periodically if an LTM event is triggered;

[0269] -reportOnLeave: whether the event triggered L1 measurement report shall be triggered when the leaving condition for an event is satisfied;

[0270] -ltm-EventTriggeredReportContent: the content of the event triggered L1 measurement report;

[0271] -candidateSpecificOffset: offset for event condition that is applicable for all the reference signals belonging to the candidate cell with the candidate cell IDltm-CandidateReportConfigId;

[0272] -servingSpecificOffsetS: offset for event condition that is applicable for all the reference signals belonging to the serving cell.

[0273] For L1 measurement and event triggered L1 measurement reporting, if anltm-CSI-ReportConfigor anltm-CSI-ResourceConfigassociated with thatltm-CSI-ReportConfigis removed or modified from the current UE configuration, the MAC entity shall:

[0274] 1> remove the measurement reporting entry for the correspondingltm-CSI-ReportConfigIdfrom theMR_LIST, if included;

[0275] 1> stop the periodical reporting timer, if running, and reset the associated information (e.g., TTT and variables) for the correspondingltm-CSI-ReportConfigId;

[0276] 1> cancel, if any, triggered event triggered L1 measurement report for the correspondingltm-CSI-ReportConfigId.

[0277] An RRC_CONNECTED UE may obtain L1 beam level measurement results by measuring one or multiple RSs as configured by the network for the LTM candidate cell(s) with the candidate ID configured inltm-CandidateReportConfigListfor evaluation of reporting criteria or evaluation of execution condition.

[0278] For L1 measurements performed for evaluation of reporting criteria or evaluation of execution condition, the MAC entity may apply the layer 1 filtering by implementation, before using the measured results for evaluation of reporting criteria and measurement reporting or evaluation of execution condition.

[0279] The UE may maintain the following UE variables for event triggered L1 measurement and report procedure:

[0280] -MR_LIST: includes the list ofltm-CSI-ReportConfigIdfor which the L1 measurement report entering or leaving condition has been met for TTT for at least one applicable RS and, for eachltm-CSI-ReportConfigId, the RS resource index, and L1 measurement result of each measured applicable RS;

[0281] -MR_SENT_COUNTER: the number of event triggered L1 measurement report(s) sent by UE if a triggering condition for the corresponding event is met for TTT for eachltm-CSI-ReportConfigId;

[0282] -BEAM_ENTERING_LIST: list of RS resource index(es) of applicable RS(s) for eachltm-CSI-ReportConfigId, for which the L1 measurement report entering condition has been met for TTT;

[0283] -BEAM_LEAVING_LIST: list of RS resource index(es) of applicable RS(s) for eachltm-CSI-ReportConfigId, which have been reported in the (Truncated) event triggered L1 measurement report MAC CE, and for which the L1 measurement report leaving condition has been met for TTT;

[0284] -BEAM_REPORTED_LIST: list of RS resource index(es) of applicable RS(s) for eachltm-CSI-ReportConfigId, which have been reported in the (Truncated) event triggered L1 measurement report MAC CE, and the L1 measurement report leaving condition has not been met for TTT.

[0285] The MAC entity may:

[0286] 1> for eachltm-CSI-ReportConfigIdincluded in the SpCell for L1 measurement and event triggered measurement report:

[0287] 2> if the correspondingltm-ReportConfigTypeis set toeventTriggeredand there isltm-EventTriggeredReportContentconfiguration:

[0288] 3> if theeventLTM2is configured in the correspondingltm-CSI-ReportConfigId:

[0289] 4> if the associatedLTM-CSI-ResourceConfigincludesltm-NZP-CSI-RS-ResourceSet:

[0290] 5> consider the RS configured in the indicated TCI State of the SpCell to be applicable.

[0291] 4> else:

[0292] 5> consider the SSB QCLed with the RS configured in the indicated TCI State of the SpCell to be applicable.

[0293] 3> if theeventLTM3,eventLTM4, oreventLTM5is configured in the correspondingltm-CSI-ReportConfigId:

[0294] 4> ifltm-CandidateReportConfigListis configured:

[0295] 5> consider any RS configured in the associatedLTM-CSI-ResourceConfigof an LTM candidate cell other than the SpCell listed inltm-CandidateReportConfigList, to be applicable.

[0296] 4> else:

[0297] 5> consider any RS configured in the associatedLTM-CSI-ResourceConfigof an LTM candidate cell other than the SpCell listed, to be applicable.

[0298] 2> derive L1 measurement results for the applicable RS;

[0299] 2> if the entry condition for the event associated withltm-CSI-ReportConfigIdis fulfilled for the measurement from lower layer during TTT for one or more applicable RSs, which is not in theBEAM_ENTERING_LISTand not in theBEAM_REPORTED_LIST:

[0300] 3> if theMR_LISTdoes not include a measurement reporting entry for theltm-CSI-ReportConfigId(a first RS triggers the event):

[0301] 4> include a measurement reporting entry in theMR_LISTfor thisltm-CSI-ReportConfigId;

[0302] 3> for each applicable RS for which the entry condition is fulfilled during TTT and that is not inBEAM_LEAVING_LIST:

[0303] 4> include the RS resource index of the concerned RS in theBEAM_ENTERING_LISTfor thisltm-CSI-ReportConfigId;

[0304] 3> for each applicable RS for which the entry condition is fulfilled during TTT and that is inBEAM_LEAVING_LIST:

[0305] 4> remove the concerned RS in theBEAM_LEAVING_LISTfor thisltm-CSI-ReportConfigId;

[0306] 4> if the RS resource index of the concerned RS has been removed fromBEAM_REPORTED_LIST:

[0307] 5> include the RS resource index of the concerned RS in theBEAM_REPORTED_LISTfor thisltm-CSI-ReportConfigId.

[0308] 3> consider L1 measurement reporting to be triggered for theltm-CSI-ReportConfigId.

[0309] 2> else if the leaving condition for the event associated withltm-CSI-ReportConfigIdis fulfilled for the measurement from lower layer during TTT for one or more applicable RSs included in theBEAM_ENTERING_LISTorBEAM_REPORTED_LIST:

[0310] 3> for each applicable RS for which the leaving condition is fulfilled during TTT and that is inBEAM_ENTERING_LIST:

[0311] 4> remove the concerned RS in theBEAM_ENTERING_LISTfor thisltm-CSI-ReportConfigId.

[0312] 3> for each applicable RS for which the leaving condition is fulfilled during TTT and that is inBEAM_REPORTED_LIST:

[0313] 4> remove the concerned RS in theBEAM_REPORTED_LISTfor thisltm-CSI-ReportConfigId;

[0314] 4> include the RS resource index of the concerned RS in theBEAM_LEAVING_LISTfor thisltm-CSI-ReportConfigId.

[0315] 3> ifreportOnLeaveis set totruefor thisltm-CSI-ReportConfigId:

[0316] 4> consider L1 measurement reporting to be triggered for theltm-CSI-ReportConfigId.

[0317] 2> upon expiry of the periodical reporting timer for thisltm-CSI-ReportConfigId:

[0318] 3> consider L1 measurement reporting to be triggered for theltm-CSI-ReportConfigId.

[0319] TTT is not restarted if the RS configured in the indicated TCI state of serving cell changes and the entry condition is still met with the RS configured in the newly indicated TCI state.

[0320] To evaluate the L1 measurement reporting triggering event, the UE uses the latestL1-RSRPmeasurement from lower layer.

[0321] For eachltm-CSI-ReportConfigIdincluded in the SpCell cell for L1 measurement and event triggered measurement report, the MAC entity may:

[0322] 1> if at least one L1 measurement report has been triggered for theltm-CSI-ReportConfigIdand not cancelled:

[0323] 2> if UL-SCH resources are available for a new transmission in the serving cell and these UL-SCH resources can accommodate the event triggered L1 measurement report MAC CE plus its subheader as a result of logical channel prioritization:

[0324] 3> instruct the Multiplexing and Assembly procedure to generate the event triggered L1 measurement report MAC CE associated with theltm-CSI-ReportConfigIdaccording to the measurement report information in theMR_LIST;

[0325] FIG. 13 shows an example of a L1 measurement report MAC CE to which implementations of the present disclosure are applied.

[0326] Event triggered L1 measurement report MAC CE consists of either:

[0327] - event triggered L1 measurement report format (variable size); or

[0328] - truncated event triggered L1 measurement report format (variable size).

[0329] The event triggered L1 measurement report formats are identified by MAC subheaders with an eLCIDs.

[0330] For a truncated event triggered L1 measurement report MAC CE, at least the following fields should be included: report ID field, at least one triggered RS with corresponding measured quantity, and the current RS of serving cell with corresponding measured quantity, if the UE is configured to report the measurement result of current RS of the serving cell byreportCurrentBeam.

[0331] The fields in the (truncated) event triggered L1 measurement report MAC CE are defined as follows:

[0332] - Report ID: This field indicates corresponding measurement report ID for thisltm-CSI-ReportConfigIdassociated with this event triggered measurement report. The length of the Report ID field is 6 bits;

[0333] - Typei: This field indicates the type of the RS i of LTM candidate cell included in the event triggered L1 measurement report. The field is set to 00 to indicate the RS(s) that have satisfied the entry condition of the event associated with the report ID for TTT, and trigger this measurement report MAC CE, which are included in theBEAM_ENTERING_LISTassociated with the report ID when the MAC CE is generated; it is set to 01 to indicate the RS(s) that have satisfied the leaving condition of the event associated with the report ID for TTT, and trigger this measurement report MAC CE, which are included in theBEAM_LEAVING_LISTassociated with the report ID when the MAC CE is generated; it is set to 10 to indicate the RS(s) have been previously reported in the (Truncated) event triggered L1 measurement report MAC CE, which are included in theBEAM_REPORTED_LISTassociated with the report ID when the MAC CE is generated; it is set to 11 to indicate the RS(s) none of theBEAM_ENTERING_LIST / BEAM_REPORTED_LIST / BEAM_LEAVING_LIST, ifallowReportAnyBeamis configured. The RS(s) not satisfying the event for TTT are selected by decreasing value of measurement results. The RS(s) included in the truncated event triggered L1 measurement report MAC CE are selected based on the Type of RS(s), with the following priorities in decreasing order: 00, 01, 10, 11. If the (Truncated) event triggered L1 measurement report MAC CE cannot accommodate all RS(s) with the same priority, the RS(s) are selected by decreasing value of measurement results. The length of the field is 2 bits;

[0334] - RSRIi: This field indicates the reference signaling resource index of the beam i of LTM candidate cell for the event triggered L1 measurement report (i.e., SS / PBCH Block Resource indicator (SSBRI) or CSI-RS resource indicator (CRI)). The maximum number of non-serving RS reported, i.e., M value, is configured bymaxNumberOfReportedBeamsif the measurement of current RS of serving cell is not included, or ismaxNumberOfReportedBeams-1 if the measurement of current RS of serving cell is included. The first RS is the RS with the highest measured quality for non-serving RS in this measurement report MAC CE. The length of the RSRI index field is 9 bits;

[0335] - RSRP1: This field indicates the measured quantity of the first beam based on SS / PBCH block or CSI-RS (i.e., the L1-RSRP). The length of the RSRP1field is 7 bits;

[0336] - DiffRSRPi: This field indicates the derived differential measured quantity for the beam i of LTM candidate cell based on SS / PBCH block or CSI-RS (i.e., the L1-RSRP), with the reference of measured quality of the first beam. The length of the DiffRSRPifield is 4 bits;

[0337] - RSRPserving: This field indicates the measured quantity based on SS / PBCH block or CSI-RS (i.e., the L1-RSRP) for current RS of serving cell used for LTM event evaluation, if the UE is configured to report the measurement result of current RS of the serving cell byreportCurrentBeam. The length of the RSRPservingfield is 7 bits;

[0338] - R: Reserved bit, set to 0.

[0339] FIG. 14 shows an example of controlling triggering of measurement reporting based on beam related event condition to which implementations of the present disclosure are applied.

[0340] FIG. 14 shows an example with Alt S1 + Alt T1 + Alt E2 mentioned above.

[0341] (1) TTT for MTR1 is initiated. After that, TTT for MTR2 is also initiated. TTTs for MTR1 and MTR2 are initiated for the same event configuration.

[0342] (2) When TTT for MTR1 is expired at t0, the UE includes MTR1 into the triggered MTR list and MTR2 into the entered MTR list. The UE triggers / initiates a first measurement reporting and transmits a measurement report. The measurement report includes information related to MTR1 included in the triggered MTR list as triggering MTR. The measurement report also includes information related to MTR2 included in the entered MTR list as entered MTR. The UE starts a periodic reporting timer.

[0343] (3) When TTT for MTR2 is expired while the periodic reporting timer is running, the UE does not trigger / initiate / transmit a measurement report. The UE keeps evaluating the event for MTR2 and other MTRs if available.

[0344] (4) When the periodic reporting timer is expired at t1, MTR2 has satisfied the event for TTT, and hence MTR2 is included into the triggered MTR list and excluded from the entered MTR list. The UE triggers / initiates a second measurement reporting and transmits a measurement report. The measurement report includes information related to MTR1 and MTR2 included in the triggered MTR list. The UE starts a periodic reporting timer.

[0345] (5) When the leaving condition for MTR1 has been satisfied for TTT at t2, the UE excludes MTR1 from the triggered MTR list. At t2, MTR2 has not satisfied leaving condition of the event for TTT, making MTR2 still present in the triggered MTR list. Hence, the UE triggers / initiates a third measurement reporting and transmits a measurement report. The measurement report includes information related to MTR2 included as triggering MTR. Since the triggered MTR list is not empty, the UE starts a periodic reporting timer.

[0346] (6) When the periodic reporting timer is expired at t3, MTR2 has not satisfied the leaving condition of the event for TTT, making MTR2 still remain in the triggered MTR list. Hence, the UE triggers / initiates a fourth measurement report and transmits a measurement report. The measurement report includes information related to MTR2 as triggering MTR. Since the triggered MTR list is not empty, the UE starts a periodic reporting timer.

[0347] In this example, once a measurement report round is triggered / initiated / transmitted by MTR1 for the concerned event instance, another measurement report round may not be triggered / initiated / transmitted by other MTRs for the same event instance. But any MTR that has satisfied the entering condition of the event for a duration of TTT may be included in the measurement report round initiated by MTR1.

[0348] FIG. 15 shows another example of controlling triggering of measurement reporting based on beam related event condition to which implementations of the present disclosure are applied.

[0349] FIG. 15 shows an example with Alt S2 + Alt T2 + Alt E1 mentioned above.

[0350] (1) TTT for MTR1 is initiated. After that, TTT for MTR2 is also initiated. TTTs for MTR1 and MTR2 are initiated for the same event configuration.

[0351] (2) When TTT for MTR1 is expired at t0, the UE includes MTR1 into the triggered MTR list and MTR2 into the entered MTR list. The UE triggers / initiates a first measurement and transmits a measurement report. The measurement report includes information related to MTR1 as triggering MTR and information related to MTR2 as entered MTR. In addition:

[0352] - The UE stops TTT for MTR2;

[0353] - The UE starts a periodic reporting timer for the event;

[0354] - While the periodic reporting timer is running for the event, the UE does not start TTT for MTR2;

[0355] - While the periodic reporting timer is running for the event, the UE does not start TTT for other MTRs associated with the same event configuration.

[0356] That is, upon detecting that MTR1 has satisfied the entering condition of the event for TTT while MTR2 is satisfying the entering condition of the event, evaluation of whether MTR2 will have satisfied the entering condition of the event for TTT and / or transmission of a measurement report triggered by MTR2 until termination of the measurement report round triggered by MTR1 may be suspended. The suspension may be enabled by stopping a timer corresponding to TTT, and / or by skipping triggering of measurement report upon expiry of a timer corresponding to TTT.

[0357] (3) While the periodic reporting timer is running, the UE evaluates whether MTR2 satisfies the entering condition of the event. If MTR2 satisfies the entering condition of the event, the UE includes MTR2 into the entered MTR list. If MTR2 does not satisfy the entering condition of the event, MTR2 is excluded from the entered MTR list.

[0358] (4) When the periodic reporting timer is expired at t1, the UE triggers / initiates a second measurement reporting and transmits a measurement report. The measurement report includes information related to MTR1 as triggering MTR. The measurement report also includes information related to MTR2 as entered MTR. Since the triggered MTR list is not empty, the UE starts a periodic reporting timer.

[0359] (5) At t2, the leaving condition for MTR1 has been satisfied for TTT. So, the UE excludes MTR1 from the triggered MTR list, and triggers a third measurement reporting and transmit a measurement report. The measurement report may include information related to MTR1 as leaving MTR. The measurement report may also include information related to MTR2 as entered MTR. Since the triggered MTR list is now empty, the UE does not start a periodic reporting timer. The measurement reporting procedure initiated by MTR1 is now terminated.

[0360] In this example, once a measurement report round is initiated / initiated / transmitted by MTR1 for the concerned event instance, another measurement report round may not be initiated / initiated / transmitted by other MTRs for the same event instance. But any MTR that is satisfying the entering condition of the event may be included in the measurement report round initiated by MTR1.

[0361] In the above disclosure, implementations in which triggering of the measurement reporting is determined based on whether the quality of RS satisfies an event are mainly described. However, this is just exemplary, and the present disclosure can be applied to implementations in which a cell quality is derived based on measurements of one or more RSs, and triggering of the measurement reporting is determined based on whether the quality of cell satisfies an event.

[0362] The present disclosure may have various advantageous effects.

[0363] For example, the unnecessary triggering of measurement reporting can be reduced.

[0364] For example, in event triggered measurement reporting for LTM, if an L1 measurement reporting is triggered for an event and another L1 measurement reporting is triggered for the same event, only one L1 measurement reporting MAC CE can be transmitted, which prevents unnecessary signaling overhead.

[0365] Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and / or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.

[0366] Claims in the present disclosure can be combined in a various way. For instance, technical features in method claims of the present disclosure can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. Other implementations are within the scope of the following claims.

Claims

A method comprising:receiving one or more measurement target resources and one or more report configuration including one or more event conditions related to the one or more measurement target resources from a network;performing measurements based on one or more measurement targets,wherein a first measurement reporting is considered to be triggered based on a first event condition associated with a first report configuration being fulfilled for a first measurement target, andwherein a second measurement reporting is considered to be triggered based on a second event condition associated with the first report configuration being fulfilled for a second measurement target; andbased on the first measurement reporting and the second measurement reporting which have been considered to be triggered for the first report configuration, transmitting a measurement report media access control (MAC) control element (CE) to the network based on the first report configuration.The method of claim 1, wherein a third measurement reporting is considered to be triggered based on an event condition associated with a second report configuration being fulfilled for a third measurement target, andwherein a second measurement report MAC CE is transmitted to the network based on the second report configuration.The method of claim 1 or 2, wherein the first event condition is fulfilled for a first duration.The method of any claims 1 to 3, wherein the second event condition is fulfilled for a second duration.The method of any claims 1 to 4, wherein the first measurement target is included in a triggered beam list based on the first event condition being fulfilled for the first measurement target.The method of any claims 1 to 5, wherein the second measurement target is included in a triggered beam list based on the second event condition being fulfilled for the second measurement target.The method of any claims 1 to 6, wherein a periodical reporting timer starts upon the first measurement reporting being considered to be triggered.The method of claim 7, wherein a measurement reporting is considered to be triggered upon expiry of the periodical reporting timer.The method of any claims 1 to 8, wherein the measurement report MAC CE includes information related to at least one of the first measurement target or the second measurement target.The method of claim 9, wherein the information related to at least one of the first measurement target or the second measurement target includes resource identification information indicating the first measurement target or the second measurement target.The method of claim 9 or 10, wherein the information related to at least one of the first measurement target or the second measurement target includes a quality of the first measurement target or the second measurement target.The method of any claims 9 to 11, wherein the information related to at least one of the first measurement target or the second measurement target includes event information indicating an event related to the first event condition or the second condition.The method of any claims 1 to 12, wherein the first event condition or the second condition is any one of an entering condition or a leaving condition.The method of any claims 1 to 13, wherein the one or more measurement targets includes one or more reference signals (RSs) or one or more cells.The method of any claims 1 to 14, wherein the method is performed by a wireless device in communication with at least one of a mobile device, a network, and / or autonomous vehicles other than the wireless device.A wireless device comprising:at least one transceiver;at least one processor; andat least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the wireless device to perform the method of any claims 1 to 15.A processing apparatus comprising:at least one processor that is integrated with a wireless device; andat least one memory comprising processor-executable instructions stored thereon that are configured to cause the at least one processor to perform the method of any claims 1 to 15.A non-transitory Computer Readable Medium (CRM) storing instructions that, based on being executed by at least one processor, cause a wireless device to perform the method of any claims 1 to 15.A method comprising:transmitting one or more measurement target resources and one or more report configuration including one or more event conditions related to the one or more measurement target resources to a network,wherein measurements are performed based on one or more measurement targets,wherein a first measurement reporting is considered to be triggered based on a first event condition associated with a first report configuration being fulfilled for a first measurement target, andwherein a second measurement reporting is considered to be triggered based on a second event condition associated with the first report configuration being fulfilled for a second measurement target; andbased on the first measurement reporting and the second measurement reporting which have been considered to be triggered for the first report configuration, receiving a measurement report media access control (MAC) control element (CE) from the wireless device based on the first report configuration.A base station comprising:at least one transceiver;at least one processor; andat least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, cause the base station to perform the method of claim 19.

Images