Beam measurement reporting including entering beam and leaving beam indicators

Abstract

A method and apparatus for a beam measurement reporting including entering beam and leaving beam indicators is provided. A wireless device transmits a measurement report related to the at least one beam to a network. The measurement report includes i) identification information related to the measurement report, ii) type information related to the at least one beam, iii) identification information related to the at least one beam, and iv) a measurement result of the at least one beam.

Description

BEAM MEASUREMENT REPORTING INCLUDING ENTERING BEAM AND LEAVING BEAM INDICATORS

[0001] The present disclosure relates to a beam measurement reporting including entering beam and leaving beam indicators.

[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 transmitting a measurement report related to the at least one beam to a network. The measurement report includes i) identification information related to the measurement report, ii) type information related to the at least one beam, iii) identification information related to the at least one beam, and iv) a measurement result of the at least one beam.

[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 a method to which the implementation 1 of the present disclosure is applied.

[0016] FIG. 11 shows an example of another method to which the implementation 1 of the present disclosure is applied.

[0017] FIG. 12 shows an example of an event triggered L1 measurement report MAC CE to which implementation 1 of the present disclosure is applied.

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

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

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

[0021] 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".

[0022] 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".

[0023] 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".

[0024] 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".

[0025] 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".

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

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

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

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

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

[0031] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0060] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0076] 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).

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

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

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

[0080] 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).

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

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

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

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

[0085] 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).

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

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

[0088] uNslotsymbNframe,uslotNsubframe,uslot01410111420221440431480841416016

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

[0090] uNslotsymbNframe,uslotNsubframe,uslot212404

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0107] 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).

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

[0109] The following principles apply to CHO:

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

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

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

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

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

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

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

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

[0118] The following principles apply to LTM:

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

[0120] - Subsequent LTM is supported.

[0121] 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:

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

[0123] - PCell change in CA scenario,

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0154] To achieve high robustness and short interruption for mobility, a Conditional LTM (CLTM) will be introduced in 5G NR Rel-19. For example, the UE may be configured with a CLTM configuration related to one or more candidate cells in advance, and the CLTM configuration for a candidate cell may include one or more execution conditions. When an execution condition related to a candidate cell is met, the UE may execute the CLTM cell switch toward the candidate cell (i.e., target cell). CLTM may be referred to as event LTM.

[0155] In order to perform the CLTM, the UE may need to report measurement report to the network. The measurement report for the CLTM may be referred to as L1 measurement report and / or event LTM report. Considering that the event LTM report may be frequently triggered, it may be desirable to reduce the size of the event LTM report. On the other hand, one event LTM report should be able to provide sufficient information such that the network can make optimal decision based on information included in the event LTM report. Efficient construction of the event LTM report may be needed.

[0156] In addition, once the event LTM report is initially triggered by satisfaction an entry condition related to the corresponding event, subsequent periodical reporting may be triggered. Efficient UL scheduling for the subsequent periodical reporting may be desirable.

[0157] Hereinafter, various implementations of the present disclosure related to the event LTM report will be described in detail.

[0158] 1. Implementation 1: Reporting contents

[0159] If the network receives the event LTM report, the network should be able to identify at least one of, from the content of the event LTM report, which event has been met (i.e., entry condition of the event is met) or unmet (i.e., leaving condition of the event is met), which beam (e.g., Refence Signal (RS)) has triggered the reporting, and / or quality of the beam that has triggered the reporting.

[0160] (1) For example, the event LTM report may include report identification information. The report identification information may enable the network to identify at least one of a triggered event, report configuration, and / or entry / leaving condition being satisfied. The report identification information may include at least one of the following information.

[0161] - Report configuration identification information (e.g.,reportConfigID): This information may inform based on which report configuration this event LTM report has been triggered.

[0162] - Entry / leaving indicator: This information may inform which event has triggered this event LTM report. That is, this information may inform type of the event LTM report. When the entry indicator is included in the event LTM report, it may mean that the corresponding event LTM report is triggered by satisfaction of entry condition. When the leaving indicator is included in the event LTM report, it may mean that the corresponding event LTM report is triggered by satisfaction of leaving condition.

[0163] In case multiple RS IDs are included in the event LTM report, the entry / leaving indicator may be included per RS ID.

[0164] (2) For example, the event LTM report may include beam information related to a triggering beam. The beam information may include at least one of the following information.

[0165] - RS ID of triggering beam: This information may inform which beam / RS satisfies entry / leaving condition of the event LTM. RS ID may not be needed in case the RS ID can be derived from the report configuration identification information (e.g.,reportConfigID). For example, if the network receives event LTM2 report triggered by Quasi-Co-Located (QCL) RS of indicated TCI state, the network can figure out, from thereportConfigID included in the event LTM2 report, that the QCL RS of the latest indicated TCI State has triggered the event LTM2 report. For beam satisfying the leaving condition, RS ID may not be included.

[0166] - Quality of triggering beam (i.e., quality of beam / RS indicated by the RS ID): This information may include filtered L1 Reference Signal Received Power (RSRP) as baseline. This information may also include unfiltered L1 RSRP, if the network configures the UE to report unfiltered L1 RSRP via DCI or RRC signaling.

[0167] To reduce signaling overhead of the event LTM report, the event LTM report may include one full value and difference value (e.g., delta value) for the other value. For example, when multiple RS IDs are included in the event LTM report, the event LTM report may include i) RSRP related to the first RS and ii) difference between the RSRP related to the first RS and the RSRP related to the second RS (i.e., delta value). For example, to reduce signaling overhead of the event LTM report in reporting both filtered value and unfiltered value, the event LTM report may include one value (e.g., filtered value) and difference between the filtered L1 RSRP and unfiltered L1 RSRP for the other value (e.g., unfiltered value).

[0168] (3) For example, the event LTM report may include additional beam information related to a non-triggering beam. The additional beam information may include {RS ID, L1-RSRP} for other non-triggering beams. The additional beam information may include additional beam information up to N beams. The additional beam information may include filtered L1 RSRP as baseline, and may optionally include unfiltered L1-RSRP based on size constraint of the event LTM report. The additional beam information may be included only when there is other beam / RS candidate than the triggering beam / RS (e.g., a triggering beam / RS is selected from the set of beams / RSs based on the entry / leaving condition).

[0169] (4) For example, the event LTM report may include additional L3 measurement results. The additional L3 measurement results may be included in the event LTM report if the network configures the UE to report the via DCI or RRC signaling. The additional L3 measurement results may include at least one of the following information.

[0170] - L3 measurement result of the candidate cell with which the RS ID being reported is associated.

[0171] - L3 measurement result of serving cell

[0172] - L3 quality difference between serving cell and the candidate cell.

[0173] Quantization (or any size reduction) may be beneficial.

[0174] (5) For example, the event LTM report may include information related to subsequent periodical reporting. This information may inform whether subsequent periodical reporting is necessary or not. This information may be used by the network to choose and / or provide optimal UL resources.

[0175] (6) For example, the event LTM report may include information related to report termination. This information may inform that the event-triggered LTM report is terminated due to the triggering beam set being empty. This information may be combined with the leaving indicator. This information may be implicit by not including any RS ID of the triggering beam / RS in the event LTM report.

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

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

[0178] FIG. 10 shows an example of a method to which the implementation 1 of the present disclosure is applied.

[0179] In step S1000, the method comprises evaluating an event related to at least one beam.

[0180] In step S1010, the method comprises transmitting a measurement report related to the at least one beam to a network. The measurement report includes i) identification information related to the measurement report, ii) type information related to the at least one beam, iii) identification information related to the at least one beam, and iv) a measurement result of the at least one beam.

[0181] In some implementations, the measurement report may be triggered based on the at least one beam satisfying at least one of an entry condition or a leaving condition of the event configured by a report configuration. The event may be considered to be satisfied based on at least one of i) the at least one beam satisfying the entry condition or the leaving condition of the event for a time duration, or ii) the at least one beam satisfying the entry condition or the leaving condition of the event more than N times for a time duration.

[0182] In some implementations, the type information may inform that the at least one beam has satisfied an entry condition or a leaving condition of the event. The type information may be included in the measurement report per RS ID.

[0183] In some implementations, the identification information related to the measurement report may include a report configuration ID. The identification information related to the measurement report may inform which report configuration triggers the measurement report. The identification information related to the at least one beam may include a RS ID of the at least one beam.

[0184] In some implementations, the identification information related to the at least one beam may inform which beam satisfies the event.

[0185] In some implementations, the measurement result of the at least one beam may include a RSRP of the at least one beam. The measurement result of the at least one beam may include at least one of a filtered measurement result or an unfiltered measurement result of the at least one beam.

[0186] In some implementations, the measurement result of the at least one beam may be represented based on at least one of a full RSRP value of the at least one beam, or a difference between an RSRP of the at least one beam and a RSRP of a first beam included in the measurement report.

[0187] In some implementations, the measurement report may further include additional beam information related to non-triggering beams. The additional beam information related to non-triggering beams may be implicitly included in the measurement report as one type of the type information included in the measurement report. For example, the additional beam information related to the non-triggering beams may be indicated as neither of a beam type satisfying an entering condition nor a beam type satisfying a leaving condition.

[0188] In some implementations, the measurement report may further include an additional L3 measurement result.

[0189] In some implementations, the measurement report may further include information related to a subsequent periodic reporting.

[0190] In some implementations, the measurement report may further include information related to termination of the measurement report.

[0191] In some implementations,the measurement report may correspond to a L1 measurement report MAC CE.

[0192] In some implementations, the method may be 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.

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

[0194] The wireless device comprises 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. 10.

[0195] More specifically, the wireless device evaluates an event related to at least one beam.

[0196] The wireless device transmits a measurement report related to the at least one beam to a network. The measurement report includes i) identification information related to the measurement report, ii) type information related to the at least one beam, iii) identification information related to the at least one beam, and iv) a measurement result of the at least one beam.

[0197] In some implementations, the measurement report may be triggered based on the at least one beam satisfying at least one of an entry condition or a leaving condition of the event configured by a report configuration. The event may be considered to be satisfied based on at least one of i) the at least one beam satisfying the entry condition or the leaving condition of the event for a time duration, or ii) the at least one beam satisfying the entry condition or the leaving condition of the event more than N times for a time duration.

[0198] In some implementations, the type information may inform that the at least one beam has satisfied an entry condition or a leaving condition of the event. The type information may be included in the measurement report per RS ID.

[0199] In some implementations, the identification information related to the measurement report may include a report configuration ID. The identification information related to the measurement report may inform which report configuration triggers the measurement report. The identification information related to the at least one beam may include a RS ID of the at least one beam.

[0200] In some implementations, the identification information related to the at least one beam may inform which beam satisfies the event.

[0201] In some implementations, the measurement result of the at least one beam may include a RSRP of the at least one beam. The measurement result of the at least one beam may include at least one of a filtered measurement result or an unfiltered measurement result of the at least one beam.

[0202] In some implementations, the measurement result of the at least one beam may be represented based on at least one of a full RSRP value of the at least one beam, or a difference between an RSRP of the at least one beam and a RSRP of a first beam included in the measurement report.

[0203] In some implementations, the measurement report may further include additional beam information related to non-triggering beams. The additional beam information related to non-triggering beams may be implicitly included in the measurement report as one type of the type information included in the measurement report. For example, the additional beam information related to the non-triggering beams may be indicated as neither of a beam type satisfying an entering condition nor a beam type satisfying a leaving condition.

[0204] In some implementations, the measurement report may further include an additional L3 measurement result.

[0205] In some implementations, the measurement report may further include information related to a subsequent periodic reporting.

[0206] In some implementations, the measurement report may further include information related to termination of the measurement report.

[0207] In some implementations,the measurement report may correspond to a L1 measurement report MAC CE.

[0208] Furthermore, the method described above in FIG. 10 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.

[0209] 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. 10.

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

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

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

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

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

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

[0216] 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. 10.

[0217] FIG. 11 shows an example of another method to which the implementation 1 of the present disclosure is applied.

[0218] In step S1100, the method comprises receiving a measurement report related to at least one beam from a wireless device. The measurement report includes i) identification information related to the measurement report, ii) type information related to the at least one beam, iii) identification information related to the at least one beam, and iv) a measurement result of the at least one beam.

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

[0220] The base station comprises 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. 11.

[0221] More specifically, the base station receives a measurement report related to at least one beam from a wireless device. The measurement report includes i) identification information related to the measurement report, ii) type information related to the at least one beam, iii) identification information related to the at least one beam, and iv) a measurement result of the at least one beam.

[0222] FIG. 12 shows an example of an event triggered L1 measurement report MAC CE to which implementation 1 of the present disclosure is applied.

[0223] The event triggered L1 measurement report MAC CE consists of either:

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

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

[0226] The event triggered L1 measurement report formats are identified by MAC subheaders with an enhanced Logical Channel IDs (eLCIDs).

[0227] For truncated event triggered L1 measurement report MAC CE, report ID field and at least one triggered beam with corresponding measured quantity are included.

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

[0229] - 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;

[0230] - Typei: This field indicates the type of the beam i of LTM candidate cell included in the event triggered L1 measurement report. The field is set to 00 to indicate the beam(s) that has satisfied the entry condition of the event associated with the report ID for Time-To-Trigger (TTT) and triggers this measurement report MAC CE; it is set to 01 to indicate the beam(s) that has satisfied the leaving condition of the event associated with the report ID for TTT and triggers this measurement report MAC CE; it is set to 10 to indicate the beam(s) in theBEAM_TRIGGERED_LISTassociated with the report ID other than the beam(s) with Type set to 00; it is set to 11 to indicate the beam(s) not satisfying the event for TTT, if configured by network byallowReportAnyBeam. The beam(s) not satisfying the event for TTT is selected based on the descending order of measured quantity / quality. The length of the field is 2 bits.

[0231] - 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 beams reported is configured bymaxNumberOfReportedBeams. The first beam is the beam with the best / highest measured quality in this measurement report MAC CE. The length of the RSRI index field is 9 bits.

[0232] - [MR1or RSRP1]: This field indicates the measured quantity of the first beam based on SS / PBCH block or CSI-RS (i.e., the L1-RSRP or Signal-to-Interference and Noise Ratio (SINR)). The length of the [MR1or RSRP1] field is 7 bits.

[0233] - [DiffMRior 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 or SINR), with the reference of measured quality of the first beam. The length of the [DiffMRior DiffRSRPi] field is 4 bits.

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

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

[0236] Furthermore, operations related to CLTM and / or event LTM may be as follows.

[0237] For L1 measurement and event triggered report, the network may configure an RRC_CONNECTED UE to perform L1 beam level measurements for LTM candidate cell(s), including L1 RSRP and / or SINR. The network may configure the UE to report them in accordance with the event triggered L1 measurement configuration. The measurement report is used for indicating to serving gNB of the L1 measurement results from the serving cell and / or candidate cell(s) when an event trigger L1 condition is satisfied. The measurement configuration is provided by means of RRC dedicated signaling.

[0238] The network may configure the UE to perform event triggered L1 measurement for the following LTM purpose:

[0239] - Select the candidate beam and cell for early synchronization;

[0240] - Select the target beam and cell for an LTM cell switch procedure.

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

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

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

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

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

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

[0247] The RRC configures the following parameters in theLTM-CSI-ReportConfigand / orLTM-CSI-ResourceConfigfor event triggered L1 measurement and corresponding report procedure:

[0248] -LTM-CSI-ReportConfigfor the event-triggered measurement report;

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

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

[0251] -timeToTrigger: time during which an entering / leaving condition needs to be consistently satisfied for event triggered L1 measurement reporting;

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

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

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

[0255] -ltm-ReportContent: the content of the LTM L1 measurement report.

[0256] An RRC_CONNECTED UE obtains L1 beam level measurement results by measuring one or multiple beams as configured by the network for the LTM candidate cell(s) with the candidate ID configured inltm-CandidateReportConfigList. For each L1 beam level measurement result in RRC_CONNECTED, the UE applies the layer 1 filtering by implementation, before using the measured results for evaluation of reporting criteria and measurement reporting. The MAC entity performs the evaluation of reporting criteria based on the L1 measurement results from lower layer. For the LTM candidate cell(s) with the candidate ID not configured inltm-CandidateReportConfigList, the UE is not required to perform measurement and event evaluation on the reference signaling belonging to the candidate ID for the corresponding event.

[0257] For L1 beam level event triggered measurements report, the network can configure SS / PBCH block(s) or CSI-RS as event evaluation RS type, and L1-RSRP and / or SINR as trigger quantity. Reporting quantities is the same as the trigger quantity.

[0258] The UE maintains the following UE variables for event triggered L1 measurement and report procedure:

[0259] -MR_LIST: includes the event triggered L1 measurement report information, for which the L1 measurement report triggering conditions have been met for TTT;

[0260] -MR_SENT_COUNTER: represents the number of event triggered L1 measurement report performed by UE if the triggering condition for the corresponding event is met for TTT for eachltm-CSI-ReportConfigId;

[0261] -BEAM_TRIGGERED_LIST: includes the reference signaling resource index of LTM candidate cell(s) for eachltm-CSI-ReportConfigId, for which the L1 measurement report triggering conditions have been met for TTT.

[0262] The MAC entity shall for the serving cell configured for LTM event evaluation procedure:

[0263] 1> for eachltm-CSI-ReportConfigIdof the serving cell included in theLTM-CSI-ReportConfig:

[0264] 2> if the correspondingltm-ReportConfigTypeis set toeventTriggered:

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

[0266] 4> consider only the current beam of serving cell, i.e. the beam corresponds to the RS configured in the indicated TCI State or the RS QCL-ed with the RS configured in the indicated TCI State indicated by TCI State in the serving cell, to be applicable;

[0267] 3> if theeventLTM3oreventLTM5is configured in the correspondingltm-CSI-ReportConfigId:

[0268] 4> consider any beam of LTM candidate cell, i.e. the RSs configured inLTM-CSI-ResourceConfigwhich associated with thisltm-CSI-ReportConfigId, to be applicable;

[0269] 3> if theeventLTM4is configured in the correspondingltm-CSI-ReportConfigId:

[0270] 4> consider any beam of LTM candidate cell, i.e. the RS configured inLTM-CSI-ResourceConfigwhich associated with thisltm-CSI-ReportConfigId, to be applicable;

[0271] 2> if the entry condition for the event associated withltm-CSI-ReportConfigIdis fulfilled for one or more applicable beams, i.e. reference signalling associated withLTM-CSI-SSB-ResourceConfigIdorLTM-CSI-RS-ResourceConfigIdin theLTM-CSI-ReportConfig, for the measurement from lower layer duringtimeToTriggerdefined for this event:

[0272] 3> if theMR_LISTdoes not include a measurement reporting entry for thisltm-CSI-ReportConfigId(a first beam triggers the event):

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

[0274] 3> include the SSBRI or CRI of the concerned beam(s) in theBEAM_TRIGGERED_LISTfor thisltm-CSI-ReportConfigId;

[0275] 3> ifreportAmountis configured in theLTM-EventTriggeredPeriodicReportby RRC:

[0276] 4> set theMR_SENT_COUNTERto 0 for thisltm-CSI-ReportConfigIdand reference signaling resource index;

[0277] 3> initiate the measurement reporting procedure.

[0278] 2> else if the leaving condition for the event associated withltm-CSI-ReportConfigIdis fulfilled for one or more applicable beams included in theMR_LISTfor the measurement from lower layer duringtimeToTriggerdefined for this event:

[0279] 3> remove the concerned beam(s) in theMR_LISTfor thisltm-CSI-ReportConfigId;

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

[0281] 4> initiate the measurement reporting procedure;

[0282] 3> if theBEAM_TRIGGERED_LISTfor thisltm-CSI-ReportConfigIdis empty:

[0283] 4> remove the measurement reporting entry within theMR_LISTfor thisltm-CSI-ReportConfigId;

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

[0285] 3> initiate the measurement reporting procedure.

[0286] timeToTriggeris not restarted if the current beam of serving cell changes and the entry condition is still met with the new current beam.

[0287] To evaluate the L1 measurement reporting triggering event, the UE uses the latestL1-RSRPand / or L1-SINRmeasurement from lower layer.

[0288] Event LTM2 means that beam of serving cell becomes worse than threshold. The UE shall:

[0289] 1> consider the entering condition for this event to be satisfied when condition LTM2-1, as specified below, is fulfilled;

[0290] 1> consider the leaving condition for this event to be satisfied when condition LTM2-2, as specified below, is fulfilled;

[0291] - Inequality LTM2-1 (Entering condition)

[0292] Ms + Hys < Thresh

[0293] - Inequality LTM2-2 (Leaving condition)

[0294] Ms - Hys > Thresh

[0295] The variables in the formula are defined as follows:

[0296] -Msis the beam measurement quantity of the serving cell based on SS / PBCH block or CSI-RS, not taking into account any offsets. The beam associated with this event is the current beam, i.e. corresponding to the RS configure in the indicated TCI state or the RS QCL-ed with the RS configured in the indicated TCI state in the serving cell.

[0297] -Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinLTM-CSI-ReportConfigfor this event).

[0298] -Threshis the threshold parameter for this event (i.e.ltm2-Thresholdas defined withinLTM-CSI-ReportConfigfor this event).

[0299] Msis expressed in dBm in case of RSRP, and / or in dB in case of SINR.

[0300] Hysis expressed in dB.

[0301] Threshis expressed in the same unit asMs.

[0302] Event LTM3 means that beam of candidate cell becomes offset better than beam of serving cell. The UE shall:

[0303] 1> consider the entering condition for this event to be satisfied when condition LTM3-1, as specified below, is fulfilled;

[0304] 1> consider the leaving condition for this event to be satisfied when condition LTM3-2, as specified below, is fulfilled;

[0305] 1> for this measurement, consider the current beam, i.e. corresponding to the RS configured in the indicated TCI state or the RS QCLed with the RS configured in the indicated TCI state in the serving cell, with the same RS type as the beam of candidate cell, associated with this event.

[0306] - Inequality LTM3-1 (Entering condition)

[0307] Mn + Obn- Hys > Ms + Obs + Off

[0308] - Inequality LTM3-2 (Leaving condition)

[0309] Mn + Obn + Hys < Ms + Obs + Off

[0310] The variables in the formula are defined as follows:

[0311] -Mnis the beam measurement quantity of the LTM candidate cell based on SS / PBCH block or CSI-RS, not taking into account any offsets.

[0312] -Obnis the offset of the LTM candidate cell (i.e. [beamIndividualOffsetN] as defined inLTM-CSI-ReportConfigfor this event). One offset is applied to all beam(s) associated with the LTM candidate cell.

[0313] -Msis the beam measurement quantity of the serving cell based on SS / PBCH block or CSI-RS, not taking into account any offsets. The beam associated with this event is the current beam, i.e corresponding to the RS configured in the indicated TCI state or the RS QCL-ed with the RS configured in the indicated TCI State indicated by TCI State in the serving cell the serving cell.

[0314] -Obsis the offset of the beam of the serving cell (i.e. [beamIndividualOffsetS] as defined inLTM-CSI-ReportConfigfor this event).]

[0315] -Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinLTM-CSI-ReportConfigfor this event).

[0316] -Offis the offset parameter for this event (i.e.ltm3-Offsetas defined withinLTM-CSI-ReportConfigfor this event).

[0317] Mn, Msare expressed in dBm in case of RSRP, and / or in dB in case of SINR.

[0318] Obn,Obs,Hys,Offare expressed in dB.

[0319] Event LTM4 means that beam of candidate cell becomes better than absolute threshold. The UE shall:

[0320] 1> consider the entering condition for this event to be satisfied when condition LTM4-1, as specified below, is fulfilled;

[0321] 1> consider the leaving condition for this event to be satisfied when condition LTM4-2, as specified below, is fulfilled.

[0322] - Inequality LTM4-1 (Entering condition)

[0323] Mn + Obn- Hys > Thresh

[0324] - Inequality LTM4-2 (Leaving condition)

[0325] Mn + Obn+ Hys < Thresh

[0326] The variables in the formula are defined as follows:

[0327] -Mnis the beam measurement quantity of the LTM candidate cell based on SS / PBCH block or CSI-RS, not taking into account any offsets.

[0328] -Obnis the offset of the beam of the LTM candidate cell (i.e. [beamIndividualOffsetN] as defined inLTM-CSI-ReportConfigfor this event). One offset is applied to all beam(s) associated with the LTM candidate cell.

[0329] -Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinLTM-CSI-ReportConfigfor this event).

[0330] -Offis the offset parameter for this event (i.e.ltm4-Offsetas defined withinLTM-CSI-ReportConfigfor this event).

[0331] Mnis expressed in dBm in case of RSRP, and / or in dB in case of SINR.

[0332] Obn, Hysare expressed in dB.

[0333] Threshis expressed in the same unit asMn.

[0334] Event LTM5 means thatbeam of serving cell becomes worse than threshold1 and beam of candidate cell becomes better than threshold2. The UE shall:

[0335] 1> consider the entering condition for this event to be satisfied when both condition LTM5-1 and condition LTM5-2, as specified below, are fulfilled;

[0336] 1> consider the leaving condition for this event to be satisfied when condition LTM5-3 or condition LTM5-4, i.e. at least one of the two, as specified below, is fulfilled;

[0337] - Inequality LTM5-1 (Entering condition 1)

[0338] Ms + Hys < Thresh1

[0339] - Inequality LTM5-2 (Entering condition 2)

[0340] Mn + Obn- Hys > Thresh2

[0341] - Inequality LTM5-3 (Leaving condition 1)

[0342] Ms - Hys > Thresh1

[0343] - Inequality LTM5-4 (Leaving condition 2)

[0344] Mn + Obn+ Hys < Thresh2

[0345] The variables in the formula are defined as follows:

[0346] -Msis the beam measurement quantity of the serving cell based on SS / PBCH block or CSI-RS, not taking into account any offsets. The beam associated with this event is the current beam, i.e corresponding to the RS configured in the indicated TCI state or the RS QCL-ed with the RS configured in the indicated TCI State indicated by TCI State in the serving cell.

[0347] -Mnis the beam measurement quantity of the LTM candidate cell based on SS / PBCH block or CSI-RS, not taking into account any offsets.

[0348] -Obnis the offset of the LTM candidate cell (i.e. [beamIndividualOffsetN] as defined inLTM-CSI-ReportConfigfor this event). One offset is applied to all beam(s) associated with the LTM candidate cell.

[0349] -Hysis the hysteresis parameter for this event (i.e.hysteresisas defined withinLTM-CSI-ReportConfigfor this event).

[0350] -Thresh1is the threshold parameter for this event (i.e. ltm5-Threshold1as defined withinLTM-CSI-ReportConfigfor this event).

[0351] -Thresh2is the threshold parameter for this event (i.e. ltm5-Threshold2as defined withinLTM-CSI-ReportConfigfor this event).

[0352] Mn, Msare expressed in dBm in case of RSRP, and / or in dB in case of SINR.

[0353] Obn,Hysare expressed in dB.

[0354] Thresh1is expressed in the same unit asMs.

[0355] Thresh2is expressed in the same unit asMn.

[0356] The purpose of the measurement report procedure is to transfer L1 measurement results from the UE to the network. RRC controls the event triggered L1 beam level measurement reporting by configuring the following parameter:

[0357] -reportInterval: the periodicity of the event-triggered periodic measurement report;

[0358] -reportAmount: number of measurement reports needs to be transmitted after the event is triggered;

[0359] -maxNumberOfReportedBeams: number of beams whose measurements can be reported in the event triggered L1 measurement report by MAC CE;

[0360] -allowReportAnyBeam: whether the UE could report the measurement results for the beams not satisfying the conditions of the events;

[0361] -reportCurrentBeam: whether the UE could report the measurement result of the current beam;

[0362] -ltm-CandidateReportConfigId: LTM candidate cell ID for which the UE is required to measure reference signal and perform LTM event evaluation;

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

[0364] -reportQuantity: the report quantity for the CSI report

[0365] For the event triggered L1 measurement reporting, for eachltm-CSI-ReportConfigIdof the serving cell included in theLTM-CSI-ReportConfig, the MAC entity shall:

[0366] 1> if at least one L1 measurement report has been triggered and not cancelled:

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

[0368] 3> instruct the Multiplexing and Assembly procedure to generate the L1 measurement report MAC CE associated with theltm-CSI-ReportConfigId;

[0369] 3> increment theMR_SENT_COUNTERassociated with theltm-CSI-ReportConfigIdfor the RS triggered the report by 1;

[0370] 3> stop the periodical reporting timer, if running;

[0371] 3> ifreportAmountis configured in RRC, and theMR_SENT_COUNTERas defined for thisltm-CSI-ReportConfigIdis less thanreportAmount:

[0372] 4> start the periodical reporting timer with the value ofreportIntervalfor thisltm-CSI-ReportConfigIdas defined within the correspondingLTM-CSI-reportConfig;

[0373] 3> cancel the triggered L1 measurement report;

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

[0375] 3> instruct the Multiplexing and Assembly procedure to generate the Truncated L1 measurement report MAC CE associated with theltm-CSI-ReportConfigId;

[0376] 3> increment theMR_SENT_COUNTERassociated with theltm-CSI-ReportConfigIdfor the RS triggered the report by 1;

[0377] 3> stop the periodical reporting timer, if running;

[0378] 3> ifreportAmountis configured in RRC, and theMR_SENT_COUNTERas defined for thisltm-CSI-ReportConfigIdis less thanreportAmount:

[0379] 4> start the periodical reporting timer with the value ofreportIntervalfor thisltm-CSI-ReportConfigIdas defined within the correspondingLTM-CSI-reportConfig;

[0380] 2> else:

[0381] 3> if the dedicated SR configuration for L1 measurement report MAC CE transmission is configured:

[0382] 4> trigger the SR using the dedicated SR configuration for L1 measurement report;

[0383] 3> else:

[0384] 4> trigger the SR using the common SR configuration.

[0385] For the CLTM procedure, the network may configure an RRC_CONNECTED UE to perform L1 beam level measurements for SpCell and conditional LTM candidate cell(s), including L1 RSRP and / or SINR. The UE may use the L1 measurement for LTM cell switch conditions evaluation in accordance with the reconfiguration for conditional LTM. The network may configure the UE to report the L1 measurement results for conditional LTM, e.g., to trigger PDCCH ordered early RACH or early TCI state activation.

[0386] The RRC configures the following parameters in theCLTM-ExecutionConditionsfor L1 trigger condition for CLTM procedure:

[0387] -cltm-ExecutionConditionsandcltm-ServingCellExecutionConditionsfor conditional LTM cell switch execution condition;

[0388] -ltm-CandidateId: indicates the LTM candidate configuration IDs.

[0389] Upon indication from upper layers to initiate the LTM cell switch conditions evaluation based on L1 measurements according to the indicated fieldcltm-ServingCellExecutionConditions, the MAC entity shall for the PCell configured for conditional LTM procedure:

[0390] 1> for each entry within theCLTM-ExecutionConditions:

[0391] 2> if theLTM3orLTM5is configured in the correspondingltm-CSI-ReportConfigIdforl1-Conditions:

[0392] 3> consider all beams of LTM candidate cell indicated by theltm-CandidateIdwithin thisCLTM-ExecutionConditionsto be applicable;

[0393] 3> if the entry condition for the event associated withltm-CSI-ReportConfigIdis fulfilled for TTT for one or more applicable beams, i.e. reference signalling associated withLTM-CSI-SSB-ResourceConfigIdorLTM-CSI-RS-ResourceConfigIdin theLTM-CSI-ReportConfig, for the measurement from lower layer duringtimeToTriggerdefined for this event;

[0394] 4> consider the event associated withLTM-CSI-ReportConfigIdto be fulfilled for theltm-CandidateIdassociated withLTM-CSI-ReportConfigId;

[0395] 4> perform the CLTM execution procedure for the LTM candidate configuration associated withltm-CandidateId;

[0396] The conditional LTM cell switch procedure is triggered when:

[0397] - the MAC entity determines that the event for conditional LTM is satisfied based on L1 measurements;

[0398] - the event for conditional LTM is satisfied based on L3 measurements indicated by upper layers.

[0399] The MAC entity shall:

[0400] 1> if the MAC entity determines that the event for conditional LTM is satisfied based on L1 measurements:

[0401] 2>indicate to upper layers that the event for the LTM cell switch procedure is triggered, and the Target Configuration ID, corresponding toltm-CandidateIdminus 1, for which the associated L1 measurement based event is satisfied.

[0402] 1> if the MAC reset operation is performed, as requested by upper layers:

[0403] 2> acquire the Target Configuration ID from upper layers, if any, for the satisfied L3 measurement based event;

[0404] 2> if theltm-Candidate-TimeAlignmentTimerassociated with the Target Configuration ID is running in the first available CG occasion for initial CG transmission in case two Timing Advance Groups (TAGs) are not configured for the CLTM candidate cell; or

[0405] 2> if theltm-Candidate-TimeAlignmentTimerassociated with the Target Configuration ID for the TAG associated with the selected SSB or selected CSI-RS is running in the first available CG occasion for initial CG transmission in case in case two TAGs are configured for the CLTM candidate cell:

[0406] 3> process the stored Timing Advance Command associated with theltm-Candidate-TimeAlignmentTimer;

[0407] 3> consider the RACH-less CLTM cell switch to be ongoing;

[0408] 2> else if the UE is configured with UE-based Timing Advance measurement and the UE has successfully measured the Timing Advance for the SpCell of the LTM target configuration in the first available CG occasion for initial CG transmission:

[0409] 3> process the measured Timing Advance;

[0410] 3> consider the RACH-less CLTM cell switch to be ongoing;

[0411] 2> ifcg-RRC-Configurationis configured and the RACH-less CLTM cell switch is considered to be ongoing:

[0412] 3> attempt to select a configured uplink grant for initial uplink transmission;

[0413] 3> if a valid configured uplink grant is selected:

[0414] 4> perform initial uplink transmission in the first available CG occasion for RACH-less CLTM cell switch.

[0415] According to the implementation 1 of the present disclosure, CLTM procedure can be performed more efficiently. the event LTM report can be constructed efficiently.

[0416] 2. Implementation 2: Transmission procedure for event LTM report

[0417] For UE-initiated (UEI) and / or event-driven beam reporting in MIMO, both dynamically scheduled transmission and pre-configure resource based transmission may be supported. Considering the similarity between UEI / event-driven beam reporting for MIMO and report triggered by event LTM, transmission of event LTM report may be transmitted via dynamic scheduling or pre-configured resource.

[0418] For example, the event LTM report may be transmitted over PUSCH via MAC CE. In addition to the MAC CE, the event LTM report may be transmitted via UCI as optimization for delay reduction. A container for the event LTM report may be selected between MAC CE and UCI.

[0419] If event-triggered periodical reporting is supported for event LTM, it may be beneficial to combine Mode A and Mode B such that when mode A is triggered for the first reporting of event-triggered periodical reporting, Mode B is automatically triggered for subsequent periodical reporting to reduce uplink signaling overhead.

[0420] The UE may be configured with a dedicated PUCCH Scheduling Request (SR) for the combined mode and normal PUCCH SR. The UE may also be configured with preconfigured UL resources that occur periodically. The UE may consider that the preconfigured UL resources are deactivated once they are configured.

[0421] If the UE detects that reporting condition is met for event for which subsequent periodical reporting needs to be triggered, the UE may transmit the PUCCH SR for the combined mode. Once the UE transmits the PUCCH SR for the combined mode, the UE may activate the preconfigured resources to transmit the subsequent periodical reporting, and in this case, for initial reporting, the UE may not use the preconfigured resources but use dynamically scheduled resources (i.e., the preconfigured resources are actually activated / used after the initial reporting). Alternatively, the UE may activate the preconfigured resources to transmit the subsequent periodical reporting if the UE receives DCI indicating UL grant for the Mode A transmission and activation of preconfigured resources, and in this case, for initial reporting, the UE may not use the preconfigured resources but use dynamically scheduled resources (i.e., the preconfigured resources are actually activated / used after the initial reporting). If the event-triggered reporting is terminated due to triggering beam set being empty, the UE may transmit PUCCH SR to indicate the termination (assuming that PUCCH SR for this purpose is configured to UE).

[0422] If the UE detects that reporting condition is met for event for which subsequent periodical reporting is not needed, the UE may transmit a normal PUCCH SR.

[0423] According to the implementation 2 of the present disclosure, the event LTM report can be reported to the network efficiently.

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

[0425] 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:evaluating an event related to at least one beam; andtransmitting a measurement report related to the at least one beam to a network;wherein the measurement report includes i) identification information related to the measurement report, ii) type information related to the at least one beam, iii) identification information related to the at least one beam, and iv) a measurement result of the at least one beam.The method of claim 1, wherein the measurement report is triggered based on the at least one beam satisfying at least one of an entry condition or a leaving condition of the event configured by a report configuration,wherein the event is considered to be satisfied based on at least one of i) the at least one beam satisfying the entry condition or the leaving condition of the event for a time duration, or ii) the at least one beam satisfying the entry condition or the leaving condition of the event more than N times for a time duration.The method of claim 1 or 2, wherein the type information informs that the at least one beam has satisfied an entry condition or a leaving condition of the event.The method of any claims 1 to 3, wherein the type information is included in the measurement report per reference signal (RS) identifier (ID).The method of any claims 1 to 4, wherein the identification information related to the measurement report includes a report configuration ID.The method of any claims 1 to 4, wherein the identification information related to the measurement report informs which report configuration triggers the measurement report.The method of any claims 1 to 6, wherein the identification information related to the at least one beam includes a RS ID of the at least one beam.The method of any claims 1 to 7, wherein the identification information related to the at least one beam informs which beam satisfies the event.The method of any claims 1 to 8, wherein the measurement result of the at least one beam includes a reference signal received power (RSRP) of the at least one beam.The method of any claims 1 to 9, wherein the measurement result of the at least one beam includes at least one of a filtered measurement result or an unfiltered measurement result of the at least one beam.The method of any claims 1 to 10, wherein the measurement result of the at least one beam is represented based on at least one of a full RSRP value of the at least one beam, or a difference between an RSRP of the at least one beam and a RSRP of a first beam included in the measurement report.The method of any claims 1 to 11, wherein the measurement report further includes additional beam information related to non-triggering beams.The method of claim 12, wherein the additional beam information related to the non-triggering beams is indicated as neither of a beam type satisfying an entering condition nor a beam type satisfying a leaving condition.The method of any claims 1 to 13, wherein the measurement report further includes an additional L3 measurement result.The method of any claims 1 to 14, wherein the measurement report further includes information related to a subsequent periodic reporting.The method of any claims 1 to 15, wherein the measurement report further includes information related to termination of the measurement report.The method of any claims 1 to 16, wherein the measurement report corresponds to a L1 measurement report media access control (MAC) control element (CE).The method of any claims 1 to 17, 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 18.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 18.A non-transitory Computer Readable Medium (CRM) storing instructions that, based on being executed by at least one processor, perform the method of any claims 1 to 18.A method comprising:receiving a measurement report related to at least one beam from a wireless device,wherein the measurement report includes i) identification information related to the measurement report, ii) type information related to the at least one beam, iii) identification information related to the at least one beam, and iv) a measurement result of the at least one beam.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 22.

Images