WO2025234715A1

WO2025234715A1 - Method and apparatus for reporting stored measurement results

Info

Publication number: WO2025234715A1
Application number: PCT/KR2025/006047
Authority: WO
Inventors: Myoungsoo Kim
Original assignee: LG Electronics Inc
Current assignee: LG Electronics Inc
Priority date: 2024-05-08
Filing date: 2025-05-07
Publication date: 2025-11-13
Anticipated expiration: 2026-11-08

Abstract

A method and apparatus for reporting stored measurement results is provided. The method comprises: performing, by the wireless device, measurements for a signal block and/or a reference signal; counting, by the wireless device, a number of measurement results for the signal block and/or the reference signal; and transmitting, by the wireless device, a message including information informing that the number of the measurement results are available, based on that the number of the measurement results is equal to or greater than the count threshold.

Description

METHOD AND APPARATUS FOR REPORTING STORED MEASUREMENT RESULTS

The present disclosure relates to a method and apparatus for reporting stored measurement results.

3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.

Work has started in international telecommunication union (ITU) and 3GPP to develop requirements and specifications for new radio (NR) systems. 3GPP has to identify and develop the technology components needed for successfully standardizing the new RAT timely satisfying both the urgent market needs, and the more long-term requirements set forth by the ITU radio communication sector (ITU-R) international mobile telecommunications (IMT)-2020 process. 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.

The 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.

Beam management use case is discussed for the spatial prediction and temporal prediction. To train the model for this use case, L1-RSRP and/or beam index are considered as data for training/inference/monitoring purpose.

Considering the heavy data is required for training purpose in NW side, if the UE sends the L1-RSRP results whenever performing measurement, it can cause excessive reporting, thereby leading to resource waste and power consumption in UE side. Therefore, the UE should send measurement results over multiple time instance, and considering the message size, it can be sent through RRC.

Logged MDT and immediate MDT can be considered as existing mechanism for data collection. In the case of the existing Logged MDT, the logged measurement result in RRC_IDLE or RRC_INACTIVE is notified to the NW when RRC connection is established. The UE can report the logged measurement results only when the NW request it. However, in AIML, the UE should store measurement results in the RRC connection state. Therefore, logged MDT is not suitable RRC Connected use case. In the case of the existing immediate MDT, measurement results can be delivered when the results satisfy the reporting condition, but there is no logging mechanism for measurement results.

Since there has been no mechanism for reporting logged measurement results in RRC_CONNECTED, a new procedure for logged results report is required for AIML purpose.

Thus, studies for reporting stored measurement results are required.

In an aspect, a method is provided. The method comprises: receiving, by a wireless device, a report configuration including information related to a count threshold; performing, by the wireless device, measurements for a signal block and/or a reference signal; counting, by the wireless device, a number of measurement results for the signal block and/or the reference signal; and transmitting, by the wireless device, a message including information informing that the number of the measurement results are available, based on that the number of the measurement results is equal to or greater than the count threshold.

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

The present disclosure can have various advantageous effects.

According to some embodiments of the present disclosure, a wireless device could efficiently report stored measurement results based on a number of stored measurement results.

For example, with respect to amount to stored measurement results in UE side, it can avoid UE's memory issue while the UE can send measurement result in time.

For example, considering the amount of measurement results stored in the UE, the UE can avoid memory problems. In addition, the UE can transmit the measurement results at an appropriate timing.

According to some embodiments of the present disclosure, the wireless communication system could provide an efficient solution for reporting stored measurement results.

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.

FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.

FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.

FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.

FIG. 4 shows another example of wireless devices to which implementations of the present disclosure is applied.

FIG. 5 shows an example of UE to which implementations of the present disclosure is applied.

FIGS. 6 and 7 show an example of protocol stacks in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

FIG. 8 shows a frame structure in a 3GPP based wireless communication system to which implementations of the present disclosure is applied.

FIG. 9 shows a data flow example in the 3GPP NR system to which implementations of the present disclosure is applied.

FIG. 10 shows an example of a Functional Framework for RAN Intelligence.

FIG. 11 shows an example of an AI/ML Model Training in OAM and AI/ML Model Inference in NG-RAN node.

FIG. 12 shows an example of Model Training and Model Inference both located in RAN node.

FIGS. 13 and 14 show an example of an architecture of neuron and neural network.

FIG. 15 shows an example of an AI/ML inference.

FIG. 16 shows an example of an MLP DNN model.

FIG. 17 shows an example of a CNN model.

FIG. 18 shows an example of an RNN model.

FIG. 19 shows an example of Reinforcement learning.

FIG. 20 shows an example of a logged measurement configuration.

FIG. 21 shows an example of UE information procedure.

FIG. 22 shows an example of measurement reporting.

FIG. 23 shows an example of location measurement indication.

FIG. 24 shows an example of a method for reporting stored measurement results.

FIG. 25 shows an example of a method for reporting stored measurement results.

FIG. 26 shows an example of resource sets mapped to report configuration.

FIG. 27 shows an example of a method for reporting the stored measurement results.

FIG. 28 shows an example of a method for reporting the stored measurement results.

FIG. 29 shows an example of a method for reporting the stored measurement results.

FIG. 30 shows an example of a method for reporting stored measurement results based on count threshold.

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 multicarrier 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 DL and SC-FDMA in UL. LTE-advanced (LTE-A) is an evolved version of 3GPP LTE.

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.

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.

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".

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".

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".

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".

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".

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

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.

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.

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.

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).

Partial use cases may require a plurality of categories for optimization and other use cases may focus only upon one key performance indicator (KPI). 5G supports such various use cases using a flexible and reliable method.

eMBB far surpasses basic mobile Internet access and covers abundant bidirectional work and media and entertainment applications in cloud and augmented reality. Data is one of 5G core motive forces and, in a 5G era, a dedicated voice service may not be provided for the first time. In 5G, it is expected that voice will be simply processed as an application program using data connection provided by a communication system. Main causes for increased traffic volume are due to an increase in the size of content and an increase in the number of applications requiring high data transmission rate. A streaming service (of audio and video), conversational video, and mobile Internet access will be more widely used as more devices are connected to the Internet. These many application programs require connectivity of an always turned-on state in order to push real-time information and alarm for users. Cloud storage and applications are rapidly increasing in a mobile communication platform and may be applied to both work and entertainment. The cloud storage is a special use case which accelerates growth of uplink data transmission rate. 5G is also used for remote work of cloud. When a tactile interface is used, 5G demands much lower end-to-end latency to maintain user good experience. Entertainment, for example, cloud gaming and video streaming, is another core element which increases demand for mobile broadband capability. Entertainment is essential for a smartphone and a tablet in any place including high mobility environments such as a train, a vehicle, and an airplane. Other use cases are augmented reality for entertainment and information search. In this case, the augmented reality requires very low latency and instantaneous data volume.

In addition, one of the most expected 5G use cases relates a function capable of smoothly connecting embedded sensors in all fields, i.e., mMTC. It is expected that the number of potential Internet-of-things (IoT) devices will reach 204 hundred million up to the year of 2020. An industrial IoT is one of categories of performing a main role enabling a smart city, asset tracking, smart utility, agriculture, and security infrastructure through 5G.

URLLC includes a new service that will change industry through remote control of main infrastructure and an ultra-reliable/available low-latency link such as a self-driving vehicle. A level of reliability and latency is essential to control a smart grid, automatize industry, achieve robotics, and control and adjust a drone.

5G is a means of providing streaming evaluated as a few hundred megabits per second to gigabits per second and may complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS). Such fast speed is needed to deliver TV in resolution of 4K or more (6K, 8K, and more), as well as virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include almost immersive sports games. A specific application program may require a special network configuration. For example, for VR games, gaming companies need to incorporate a core server into an edge network server of a network operator in order to minimize latency.

Automotive is expected to be a new important motivated force in 5G together with many use cases for mobile communication for vehicles. For example, entertainment for passengers requires high simultaneous capacity and mobile broadband with high mobility. This is because future users continue to expect connection of high quality regardless of their locations and speeds. Another use case of an automotive field is an AR dashboard. The AR dashboard causes a driver to identify an object in the dark in addition to an object seen from a front window and displays a distance from the object and a movement of the object by overlapping information talking to the driver. In the future, a wireless module enables communication between vehicles, information exchange between a vehicle and supporting infrastructure, and information exchange between a vehicle and other connected devices (e.g., devices accompanied by a pedestrian). A safety system guides alternative courses of a behavior so that a driver may drive more safely drive, thereby lowering the danger of an accident. The next stage will be a remotely controlled or self-driven vehicle. This requires very high reliability and very fast communication between different self-driven vehicles and between a vehicle and infrastructure. In the future, a self-driven vehicle will perform all driving activities and a driver will focus only upon abnormal traffic that the vehicle cannot identify. Technical requirements of a self-driven vehicle demand ultra-low latency and ultra-high reliability so that traffic safety is increased to a level that cannot be achieved by human being.

A smart city and a smart home/building mentioned as a smart society will be embedded in a high-density wireless sensor network. A distributed network of an intelligent sensor will identify conditions for costs and energy-efficient maintenance of a city or a home. Similar configurations may be performed for respective households. All of temperature sensors, window and heating controllers, burglar alarms, and home appliances are wirelessly connected. Many of these sensors are typically low in data transmission rate, power, and cost. However, real-time HD video may be demanded by a specific type of device to perform monitoring.

Consumption and distribution of energy including heat or gas is distributed at a higher level so that automated control of the distribution sensor network is demanded. The smart grid collects information and connects the sensors to each other using digital information and communication technology so as to act according to the collected information. Since this information may include behaviors of a supply company and a consumer, the smart grid may improve distribution of fuels such as electricity by a method having efficiency, reliability, economic feasibility, production sustainability, and automation. The smart grid may also be regarded as another sensor network having low latency.

Mission critical application (e.g., e-health) is one of 5G use scenarios. A health part contains many application programs capable of enjoying benefit of mobile communication. A communication system may support remote treatment that provides clinical treatment in a faraway place. Remote treatment may aid in reducing a barrier against distance and improve access to medical services that cannot be continuously available in a faraway rural area. Remote treatment is also used to perform important treatment and save lives in an emergency situation. The wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

Wireless and mobile communication gradually becomes important in the field of an industrial application. Wiring is high in installation and maintenance cost. Therefore, a possibility of replacing a cable with reconstructible wireless links is an attractive opportunity in many industrial fields. However, in order to achieve this replacement, it is necessary for wireless connection to be established with latency, reliability, and capacity similar to those of the cable and management of wireless connection needs to be simplified. Low latency and a very low error probability are new requirements when connection to 5G is needed.

Logistics and freight tracking are important use cases for mobile communication that enables inventory and package tracking anywhere using a location-based information system. The use cases of logistics and freight typically demand low data rate but require location information with a wide range and reliability.

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.

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.

The wireless devices 100a to 100f represent devices performing communication using radio access technology (RAT) (e.g., 5G new RAT (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 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 AR/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.

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.

The UAV may be, for example, an aircraft aviated by a wireless control signal without a human being onboard.

The VR device may include, for example, a device for implementing an object or a background of the virtual world. The AR device may include, for example, a device implemented by connecting an object or a background of the virtual world to an object or a background of the real world. The MR device may include, for example, a device implemented by merging an object or a background of the virtual world into an object or a background of the real world. The hologram device may include, for example, a device for implementing a stereoscopic image of 360 degrees by recording and reproducing stereoscopic information, using an interference phenomenon of light generated when two laser lights called holography meet.

The public safety device may include, for example, an image relay device or an image device that is wearable on the body of a user.

The MTC device and the IoT device may be, for example, devices that do not require direct human intervention or manipulation. For example, the MTC device and the IoT device may include smartmeters, vending machines, thermometers, smartbulbs, door locks, or various sensors.

The medical device may be, for example, a device used for the purpose of diagnosing, treating, relieving, curing, or preventing disease. For example, the medical device may be a device used for the purpose of diagnosing, treating, relieving, or correcting injury or impairment. For example, the medical device may be a device used for the purpose of inspecting, replacing, or modifying a structure or a function. For example, the medical device may be a device used for the purpose of adjusting pregnancy. For example, the medical device may include a device for treatment, a device for operation, a device for (in vitro) diagnosis, a hearing aid, or a device for procedure.

The security device may be, for example, a device installed to prevent a danger that may arise and to maintain safety. For example, the security device may be a camera, a closed-circuit TV (CCTV), a recorder, or a black box.

The FinTech device may be, for example, a device capable of providing a financial service such as mobile payment. For example, the FinTech device may include a payment device or a point of sales (POS) system.

The weather/environment device may include, for example, a device for monitoring or predicting a weather/environment.

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.

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.

Here, the radio communication technologies implemented in the wireless devices in the present disclosure may include narrowband internet-of-things (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 machine type communication (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.

Referring to FIG. 2, a first wireless device 100 and a second wireless device 200 may transmit/receive radio signals to/from an external device through a variety of RATs (e.g., LTE and NR). In FIG. 2, {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 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and/or one or more antennas 108. The processor(s) 102 may control the memory(s) 104 and/or the transceiver(s) 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor(s) 102 may process information within the memory(s) 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) 106. The processor(s) 102 may receive radio signals including second information/signals through the transceiver(s) 106 and then store information obtained by processing the second information/signals in the memory(s) 104. The memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102. For example, the memory(s) 104 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. Herein, the processor(s) 102 and the memory(s) 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 106 may be connected to the processor(s) 102 and transmit and/or receive radio signals through one or more antennas 108. Each of the transceiver(s) 106 may include a transmitter and/or a receiver. The transceiver(s) 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.

The second wireless device 200 may include one or more processors 202 and one or more memories 204 and additionally further include one or more transceivers 206 and/or one or more antennas 208. The processor(s) 202 may control the memory(s) 204 and/or the transceiver(s) 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor(s) 202 may process information within the memory(s) 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s) 206. The processor(s) 202 may receive radio signals including fourth information/signals through the transceiver(s) 106 and then store information obtained by processing the fourth information/signals in the memory(s) 204. The memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202. For example, the memory(s) 204 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. Herein, the processor(s) 202 and the memory(s) 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 206 may be connected to the processor(s) 202 and transmit and/or receive radio signals through one or more antennas 208. Each of the transceiver(s) 206 may include a transmitter and/or a receiver. The transceiver(s) 206 may be interchangeably used with RF unit(s). In the present disclosure, the second wireless device 200 may represent a communication modem/circuit/chip.

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) and/or one or more service data unit (SDUs) 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 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.

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. descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and/or a set of commands.

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 read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, 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.

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.

The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured 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 may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

The one or more transceivers 106 and 206 may convert received 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 transceivers 106 and 206 can up-convert OFDM baseband signals to a carrier frequency by their (analog) oscillators and/or filters under the control of the processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency. The 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 transceivers 102 and 202.

In the implementations of the present disclosure, a UE may operate as a transmitting device in uplink (UL) and as a receiving device in downlink (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 configured 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 configured 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.

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

The wireless device may be implemented in various forms according to a use-case/service (refer to FIG. 1).

Referring to FIG. 3, wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit 110 may include a communication circuit 112 and transceiver(s) 114. For example, the communication circuit 112 may include the one or more processors 102 and 202 of FIG. 2 and/or the one or more memories 104 and 204 of FIG. 2. For example, the transceiver(s) 114 may include the one or more transceivers 106 and 206 of FIG. 2 and/or the one or more antennas 108 and 208 of FIG. 2. The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140 and controls overall operation of each of the wireless devices 100 and 200. For example, the control unit 120 may control an electric/mechanical operation of each of the wireless devices 100 and 200 based on programs/code/commands/information stored in the memory unit 130. The control unit 120 may transmit the information stored in the memory unit 130 to the exterior (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface or store, in the memory unit 130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit 110.

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, input/output (I/O) unit (e.g., audio I/O port, video I/O port), a driving unit, and a computing unit. The wireless devices 100 and 200 may be implemented in the form of, without being limited to, the robot (100a of FIG. 1), the vehicles (100b-1 and 100b-2 of FIG. 1), the XR device (100c of FIG. 1), the hand-held device (100d of FIG. 1), the home appliance (100e of FIG. 1), the IoT device (100f of FIG. 1), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a FinTech device (or a finance device), a security device, a climate/environment device, the AI server/device (400 of FIG. 1), the BSs (200 of FIG. 1), a network node, etc. The wireless devices 100 and 200 may be used in a mobile or fixed place according to a use-example/service.

In FIG. 3, the entirety of the various elements, components, units/portions, and/or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit/portion, and/or module within the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may be configured by a set of one or more processors. As an example, the control unit 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory 130 may be configured by a RAM, a DRAM, a ROM, a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.

Referring to FIG. 4, wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units/portions, and/or modules.

The first wireless device 100 may include at least one transceiver, such as a transceiver 106, and at least one processing chip, such as a processing chip 101. The processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. 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 software code 105 which implements 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 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 software code 105 may control the processor 102 to perform one or more protocols. For example, the software code 105 may control the processor 102 may perform one or more layers of the radio interface protocol.

The second wireless device 200 may include at least one transceiver, such as a transceiver 206, and at least one processing chip, such as a processing chip 201. The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. 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 software code 205 which implements 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 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 software code 205 may control the processor 202 to perform one or more protocols. For example, the software code 205 may control the processor 202 may perform one or more layers of the radio interface protocol.

Referring to FIG. 5, a UE 100 may correspond to the first wireless device 100 of FIG. 2 and/or the first wireless device 100 of FIG. 4.

A UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 110, a battery 1112, a display 114, a keypad 116, a subscriber identification module (SIM) card 118, a speaker 120, and a microphone 122.

The processor 102 may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The processor 102 may be configured 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 a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem (modulator and demodulator). An example of the processor 102 may be found in SNAPDRAGON^TM series of processors made by Qualcomm^®, EXYNOS^TM series of processors made by Samsung^®, A series of processors made by Apple^®, HELIO^TM series of processors made by MediaTek^®, ATOM^TM series of processors made by Intel^® or a corresponding next generation processor.

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.

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.

The power management module 110 manages power for the processor 102 and/or the transceiver 106. The battery 112 supplies power to the power management module 110.

The display 114 outputs results processed by the processor 102. The keypad 116 receives inputs to be used by the processor 102. The keypad 16 may be shown on the display 114.

The SIM card 118 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.

The speaker 120 outputs sound-related results processed by the processor 102. The microphone 122 receives sound-related inputs to be used by the processor 102.

In particular, FIG. 6 illustrates an example of a radio interface user plane protocol stack between a UE and a BS and FIG. 7 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. 6, the user plane protocol stack may be divided into Layer 1 (i.e., a PHY layer) and Layer 2. Referring to FIG. 7, 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).

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.

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.

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.

The RLC sublayer supports three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged node (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).

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.

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.

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 5GC or 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.

The frame structure shown in FIG. 8 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., subcarrier spacing (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 CP-OFDM symbols), SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols).

Referring to FIG. 8, downlink and uplink transmissions are organized into frames. Each frame has T_f = 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 T_sf per 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 cyclic prefix (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 = 2^u*15 kHz.

Table 1 shows the number of OFDM symbols per slot N^slot _symb, the number of slots per frame N^frame,u _slot, and the number of slots per subframe N^subframe,u _slot for the normal CP, according to the subcarrier spacing △f = 2^u*15 kHz.

u	N ^slot _symb	N ^frame,u _slot	N ^subframe,u _slot
0	14	10	1
1	14	20	2
2	14	40	4
3	14	80	8
4	14	160	16

Table 2 shows the number of OFDM symbols per slot N^slot _symb, the number of slots per frame N^frame,u _slot, and the number of slots per subframe N^subframe,u _slot for the extended CP, according to the subcarrier spacing △f = 2^u*15 kHz.

u	N ^slot _symb	N ^frame,u _slot	N ^subframe,u _slot
2	12	40	4

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 of N ^size,u _grid,x*N ^RB _sc subcarriers and N ^subframe,u _symb OFDM symbols is defined, starting at common resource block (CRB) N ^start,u _grid indicated by higher-layer signaling (e.g., RRC signaling), where N ^size,u _grid,x is the number of resource blocks (RBs) in the resource grid and the subscript x is DL for downlink and UL for uplink. N ^RB _sc is the number of subcarriers per RB. In the 3GPP based wireless communication system, N ^RB _sc is 12 generally. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). The carrier bandwidth N ^size,u _grid for subcarrier spacing configuration u is given by the higher-layer parameter (e.g., RRC parameter). Each element in the resource grid for the antenna port p and the subcarrier spacing configuration u is 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 index k in the frequency domain and an index l representing 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.

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 configuration u. The center of subcarrier 0 of CRB 0 for subcarrier spacing configuration u coincides 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 to N ^size _BWP,i-1, where i is the number of the bandwidth part. The relation between the physical resource block n_PRB in the bandwidth part i and the common resource block n_CRB is as follows: n_PRB = n_CRB + N ^size _BWP,i, where N ^size _BWP,i is 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.

The NR frequency band may be defined as two types of frequency range, i.e., FR1 and 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 3 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).

Frequency Range designation	Corresponding frequency range	Subcarrier Spacing
FR1	450MHz - 6000MHz	15, 30, 60kHz
FR2	24250MHz - 52600MHz	60, 120, 240kHz

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 4 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).

Frequency Range designation	Corresponding frequency range	Subcarrier Spacing
FR1	410MHz - 7125MHz	15, 30, 60kHz
FR2	24250MHz - 52600MHz	60, 120, 240kHz

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.

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 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.

Referring to FIG. 9, "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.

In the PHY layer, the uplink transport channels UL-SCH and RACH are mapped to their physical channels PUSCH and PRACH, respectively, and the downlink transport channels DL-SCH, BCH and PCH are mapped to PDSCH, PBCH and PDSCH, respectively. In the PHY layer, uplink control information (UCI) is mapped to PUCCH, and downlink control information (DCI) is mapped to 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.

Hereinafter, technical features related to AI/ML are described.

The application of AI/ML to wireless communications has been thus far limited to implementation-based approaches, both, at the network and the UE sides. A study on enhancement for data collection for NR and ENDC (FS_NR_ENDC_data_collect) has examined the functional framework for RAN intelligence enabled by further enhancement of data collection through use cases, examples etc. and identify the potential standardization impacts on current NG -RAN nodes and interfaces. In SA WG2 AI/ML related study, a network functionality NWDAF (Network Data Analytics Function) was introduced in Rel-15 and has been enhanced in Rel-16 and Rel-17.

In this study, we explore the benefits of augmenting the air-interface with features enabling improved support of AI/ML based algorithms for enhanced performance and/or reduced complexity/overhead. Enhanced performance here depends on the use cases under consideration and could be, e.g., improved throughput, robustness, accuracy or reliability, etc.

Through studying a few carefully selected use cases, assessing their performance in comparison with traditional methods and the associated potential specification impacts that enable their solutions, this SI will　lay the foundation for future air-interface use cases leveraging AI/ML techniques.

The goal is that sufficient use cases will be considered to enable the identification of a common AI/ML framework, including functional requirements of AI/ML architecture, which could be used in subsequent projects. The study should also identify areas where AI/ML could improve the performance of air-interface functions.

The study will serve identifying what is required for an adequate AI/ML model characterization and description establishing pertinent notation for discussions and subsequent evaluations. Various levels of collaboration between the gNB and UE are identified and considered.

Evaluations to exercise the attainable gains of AI/ML based techniques for the use cases under consideration will be carried out with the corresponding identification of KPIs with the goal to have a better understanding of the attainable gains and associated complexity requirements.

Finally, specification impact will be assessed in order to improve the overall understanding of what would be required to enable AI/ML techniques for the air-interface.

For the study on AI/ML for air-interface, the basic framework and principles agreed for FS _ NR _ ENDC _data_collect should be taken into consideration for possible applicability.

Study the 3GPP framework for AI/ML for air-interface corresponding to each target use case regarding aspects such as performance, complexity, and potential specification impact.

Use cases to focus on:

1> Initial set of use cases includes:

a) CSI feedback enhancement, e.g., overhead reduction, improved accuracy, prediction

b) Beam management, e.g., beam prediction in time, and/or spatial domain for overhead and latency reduction, beam selection accuracy improvement

c) Positioning accuracy enhancements for different scenarios including, e.g., those with heavy NLOS conditions

2> Finalize representative sub use cases for each use case for characterization and baseline performance evaluations

a) The AI/ML approaches for the selected sub use cases need to be diverse enough to support various requirements on the gNB-UE collaboration levels

- the selection of use cases for this study solely targets the formulation of a framework to apply AI/ML to the air-interface for these and other use cases. The selection itself does not intend to provide any indication of the prospects of any future normative project.

AI/ML model, terminology and description to identify common and specific characteristics for framework investigations:

3> Characterize the defining stages of AI/ML related algorithms and associated complexity:

a) Model generation, e.g., model training (including input/output, pre-/post-process, online/offline as applicable), model validation, model testing, as applicable

b) Inference operation, e.g., input/output, pre-/post-process, as applicable

4> Identify various levels of collaboration between UE and gNB pertinent to the selected use cases, e.g.,

a) No collaboration: implementation-based only AI/ML algorithms without information exchange [for comparison purposes]

b) Various levels of UE/gNB collaboration targeting at separate or joint ML operation.

5> Characterize lifecycle management of AI/ML model: e.g., model training, model deployment , model inference, model monitoring, model updating

6> Dataset(s) for training, validation, testing, and inference

7> Identify common notation and terminology for AI/ML related functions, procedures and interfaces

8> Note: Consider the work done for FS_NR_ENDC_data_collect when appropriate

For the use cases under consideration:

- Evaluate performance benefits of AI/ML based algorithms for the agreed use cases in the final representative set:

a) Methodology based on statistical models, for link and system level simulations.

i. Extensions of 3GPP evaluation methodology for better suitability to AI/ML based techniques should be considered as needed.

ii. Whether field data are optionally needed to further assess the performance and robustness in real-world environments should be discussed as part of the study.

iii. Need for common assumptions in dataset construction for training, validation and test for the selected use cases.

iv. Consider adequate model training strategy, collaboration levels and associated implications

v. Consider agreed-upon base AI model(s) for calibration

vi. AI model description and training methodology used for evaluation should be reported for information and cross-checking purposes

b) KPIs: Determine the common KPIs and corresponding requirements for the AI/ML operations. Determine the use-case specific KPIs and benchmarks of the selected use-cases.

i. Performance, inference latency and computational complexity of AI/ML based algorithms should be compared to that of a state-of-the-art baseline

ii. Overhead, power consumption (including computational), memory storage, and hardware requirements (including for given processing delays) associated with enabling respective AI/ML scheme, as well as generalization capability should be considered.

- Assess potential specification impact, specifically for the agreed use cases in the final representative set and for a common framework:

c) PHY layer aspects,

i. Consider aspects related to, e.g., the potential specification of the AI Model lifecycle management, and dataset construction for training, validation and test for the selected use cases

ii. Use case and collaboration level specific specification impact, such as new signalling, means for training and validation data assistance, assistance information, measurement, and feedback

d) Protocol aspects, e.g., (RAN2) - RAN2 only starts the work after there is sufficient progress on the use case study in RAN1

i. Consider aspects related to, e.g., capability indication, configuration and control procedures (training/inference), and management of data and AI/ML model, per RAN1 input

ii. Collaboration level specific specification impact per use case

e) Interoperability and testability aspects, e.g., (RAN4) - RAN4 only starts the work after there is sufficient progress on use case study in RAN1 and RAN2

i. Requirements and testing frameworks to validate AI/ML based performance enhancements and ensuring that UE and gNB with AI/ML meet or exceed the existing minimum requirements if applicable

ii. Consider the need and implications for AI/ML processing capabilities definition

- specific AI/ML models are not expected to be specified and are left to implementation. User data privacy needs to be preserved.

- The study on AI/ML for air interface is based on the current RAN architecture and new interfaces shall not be introduced.

With existing L3 handover mechanism, handover is triggered and executed based on reported historical measurement result and/or measurement event(s) i.e., it is kind of reactive scheme by its nature. It may work well among macro cells when UE's mobility is low for existing services. But it could be problematic when either UE's mobility is high or among micro cells of high density or both for existing services or future services e.g. XR, where such reactive scheme may result in more unintended event e.g., handover failure, radio link failure, Ping-Pong phenomenon, throughput loss or too early/late handover etc. To improve handover robustness conditional handover is introduced in Rel-16. And to reduce interruption time of frequent handover among small cells LTM HO is introduced in Rel-18. However, these two mechanisms are not sufficient because they are still reactive scheme by design. On the other hand, mechanism based on AI/ML algorithm has the potential to enable proactive scheme.

In Rel-18 SID called FS_NR_AIML_air was studied extensively on physical layer centric use cases including spatial and temporal beam prediction. Temporal prediction within serving cell is mainly to predict the best or top-K beam(s) or beam pair(s) in time domain in order to improve UE throughput. While predict the best or top-K beam(s) or beam pair(s) among a set of beams by measuring a smaller set of beams could help reduce RS signalling overhead, measurement efforts and UE power consumption etc. By extended L1 beam measurement from serving cell to neighbouring cell, majority of the RAN1 work can be reused for e.g. LTM HO study. Since L3 measurement is based on filtering of L1 measurement, the study of AI/ML for air can be leveraged for mobility purpose e.g., temporal prediction can also be used to predict beam(s)/cell(s) becoming worse so that unintended event like radio link failure or short-stay handover can be avoided.

Mobility enhancement was also studied in RAN3 in Rel-17 in SID called FS_NR_ENDC_data_collect and is now specified in Rel-18 WID NR_AIML_NGRAN-Core. In these RAN3 items the study and normative work on mobility enhancement is based on information available in network side e.g. handover and stay of time in history among cells to predict UE's trajectory in single hop and hence potential candidates. In Rel-19 RAN3 will further work on UE's trajectory for multiple hops. The predicted UE's trajectory could be helpful for study on AI/ML mobility over air interface to some extent.

Based on progress made in RAN1 and RAN3 so far and assumption on UE's trajectory it is feasible to predict RRM measurement and/or event and hence candidate target cell in UE side. In network side new assistant information, if necessary, and statistics information based on measurement report from UE and/or neighbouring nodes can be also used for smart prediction. If some prediction information could be known by network, handover and/or RRM performance can be improved by proactive measures to either make a better decision or avoid unintended event.

For AI/ML model identification and model-ID-based LCM of UE-side models and/or UE-part of two-sided models, model-ID-based LCM operates based on identified models, where a model may be associated with specific configurations/conditions associated with UE capability of an AI/ML-enabled Feature/FG and additional conditions (e.g., scenarios, sites, and datasets) as determined/identified between UE-side and NW-side.

For an AI/ML-enabled feature/FG, additional conditions refer to any aspects that are assumed for the training of the model but are not a part of UE capability for the AI/ML-enabled feature/FG. It does not imply that additional conditions are necessarily specified. Additional conditions can be divided into two categories: NW-side additional conditions and UE-side additional conditions. Note: whether specification impact is needed is a separate discussion.

From RAN1 perspective, an AI/ML model identified by a model ID may be logical, and how it maps to physical AI/ML model(s) may be up to implementation. When distinction is necessary for discussion purposes, companies may use the term a logical AI/ML model to refer to a model that is identified and assigned a model ID, and physical AI/ML model(s) to refer to an actual implementation of such a model.

After model identification, necessity, mechanisms, for UE to report updates on applicable UE part/UE-side model(s), where the applicable models may be a subset of all identified models are studied.

For inference for UE-side models, to ensure consistency between training and inference regarding NW-side additional conditions (if identified), the following options can be taken as potential approaches (when feasible and necessary):

- Model identification to achieve alignment on the NW-side additional condition between NW-side and UE-side

- Model training at NW and transfer to UE, where the model has been trained under the additional condition

- Information and/or indication on NW-side additional conditions is provided to UE

- Consistency assisted by monitoring (by UE and/or NW, the performance of UE-side candidate models/functionalities to select a model/functionality)

- Other approaches are not precluded

Reporting applicability-related information

AI/ML models for a given use case may be tailored towards and applicable to specific scenarios, locations, configuration, deployments, among other factors. In this regard, it is acknowledged that AI/ML models may undergo updates, such as model changes, as an inherent part of their development. Therefore, to ensure efficient network control and management, especially associated to what concerns the UE-side, UEs might have the ability to indicate relevant information about their supported AI/ML models and concerning AI/ML functionalities to the network. This can allow the network to perform decisions regarding, e.g., the (de)activation, or switching of AI/ML functionalities and AI/ML models.

The previously mentioned information could in principle be understood as "applicability-related information" in which the UE could, for example, report to the network conditions under which a model/functionality is applicable/suitable, or whether model(s)/functionality(es) are (non)applicable under the current context. Note, however, that the existing UE capability reporting framework cannot be used for such purposes.

Note: How and whether there is a need to enable UEs to report applicability-related information can be further discussed and defined in a normative phase. Mechanisms such as UE Assistance Information can eventually be used as example.

Two UE reporting types are identified to convey this additional information:

- "reactive" reporting, and - "proactive" reporting.

A reactive reporting would involve the UE to provide information to the network upon receiving an action from it.

While a proactive reporting would involve the UE to provide information to the network without necessarily receiving an action from it. For example, the UE might proactively inform the RAN of updates/changes to its supported model(s) or functionality(es).

- Whether necessary signalling from network is needed for proactive UE reporting can be discussed in a normative phase.

- Whether there is a need for the network to report to the UE applicability-related information of AI/ML models and/or AI/ML functionalities can be discussed in a normative phase.

FIG. 10 shows an example of a Functional Framework for RAN Intelligence.

> Data Collection is a function that provides input data to Model training and Model inference functions. AI/ML algorithm specific data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) is not carried out in the Data Collection function.

Examples of input data may include measurements from UEs or different network entities, feedback from Actor, output from an AI/ML model.

>> Training Data: Data needed as input for the AI/ML Model Training function.

>> Inference Data: Data needed as input for the AI/ML Model Inference function.

> Model Training is a function that performs the AI/ML model training, validation, and testing which may generate model performance metrics as part of the model testing procedure. The Model Training function is also responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on Training Data delivered by a Data Collection function, if required.

>> Model Deployment/Update: Used to initially deploy a trained, validated, and tested AI/ML model to the Model Inference function or to deliver an updated model to the Model Inference function.

> Model Inference is a function that provides AI/ML model inference output (e.g., predictions or decisions). Model Inference function may provide Model Performance Feedback to Model Training function when applicable. The Model Inference function is also responsible for data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on Inference Data delivered by a Data Collection function, if required.

>> Output: The inference output of the AI/ML model produced by a Model Inference function.

>>> Note: Details of inference output are use case specific.

>> Model Performance Feedback: It may be used for monitoring the performance of the AI/ML model, when available.

> Actor is a function that receives the output from the Model Inference function and triggers or performs corresponding actions. The Actor may trigger actions directed to other entities or to itself.

>> Feedback: Information that may be needed to derive training data, inference data or to monitor the performance of the AI/ML Model and its impact to the network through updating of KPIs and performance counters.

Hereinafter, technical features related to Mobility Optimization are described.

Mobility management is the scheme to guarantee the service-continuity during the mobility by minimizing the call drops, RLFs, unnecessary handovers, and ping-pong. For the future high-frequency network, as the coverage of a single node decreases, the frequency for UE to handover between nodes becomes high, especially for high-mobility UE. In addition, for the applications characterized with the stringent QoS requirements such as reliability, latency etc., the QoE is sensitive to the handover performance, so that mobility management should avoid unsuccessful handover and reduce the latency during handover procedure. However, for the conventional method, it is challengeable for trial-and-error-based scheme to achieve nearly zero-failure handover. The unsuccessful handover cases are the main reason for packet dropping or extra delay during the mobility period, which is unexpected for the packet-drop-intolerant and low-latency applications. In addition, the effectiveness of adjustment based on feedback may be weak due to randomness and inconstancy of transmission environment. Besides the baseline case of mobility, areas of optimization for mobility include dual connectivity, CHO, and DAPS, which each has additional aspects to handle in the optimization of mobility.

Mobility aspects of SON that can be enhanced by the use of AI/ML include

- Reduction of the probability of unintended events

- UE Location/Mobility/Performance prediction

- Traffic Steering

Reduction of the probability of unintended events associated with mobility.

Examples of such unintended events are:

- Intra-system Too Late Handover: A radio link failure (RLF) occurs after the UE has stayed for a long period of time in the cell; the UE attempts to re-establish the radio link connection in a different cell.

- Intra-system Too Early Handover: An RLF occurs shortly after a successful handover from a source cell to a target cell or a handover failure occurs during the handover procedure; the UE attempts to re-establish the radio link connection in the source cell.

- Intra-system Handover to Wrong Cell: An RLF occurs shortly after a successful handover from a source cell to a target cell or a handover failure occurs during the handover procedure; the UE attempts to re-establish the radio link connection in a cell other than the source cell and the target cell.

- Successful Handover: During a successful handover, there is underlying issue.

RAN Intelligence could observe multiple HO events with associated parameters, use this information to train its ML model and try to identify sets of parameters that lead to successful Hos and sets of parameters that lead to unintended events.

UE Location/Mobility/Performance Prediction

Predicting UE's location is a key part for mobility optimisation, as many RRM actions related to mobility (e.g., selecting handover target cells) can benefit from the predicted UE location/trajectory. UE mobility prediction is also one key factor in the optimization of early data forwarding particularly for CHO. UE Performance prediction when the UE is served by certain cells is a key factor in determining which is the best mobility target for maximisation of efficiency and performance.

Traffic Steering

Efficient resource handling can be achieved adjusting handover trigger points and selecting optimal combination of Pcell/PSCell/Scells to serve a user.

Existing traffic steering can also be improved by providing a RAN node with information related to mobility or dual connectivity.

For example, before initiating a handover, the source gNB could use feedbacks on UE performance collected for successful handovers occurred in the past and received from neighbouring gNBs.

Similarly, for the case of dual connectivity, before triggering the addition of a secondary gNB or triggering SN change, an eNB could use information (feedbacks) received in the past from the gNB for successfully completed SN Addition or SN Change procedures.

In the two reported examples, the source RAN node of a mobility event, or the RAN node acting as Master Node (a eNB for EN-DC, a gNB for NR-DC) can use feedbacks received from the other RAN node, as input to an AI/ML function supporting traffic related decisions (e.g., selection of target cell in case of mobility, selection of a PSCell / Scell(s) in the other case), so that future decisions can be optimized.

Locations for AI/ML Model Training and AI/ML Model Inference

Considering the locations of AI/ML Model Training and AI/ML Model Inference for mobility solution, the following two options are considered:

- The AI/ML Model Training function is deployed in OAM, while the Model Inference function resides within the RAN node

- Both the AI/ML Model Training function and the AI/ML Model Inference function reside within the RAN node

Furthermore, for CU-DU split scenario, following option is possible:

- AI/ML Model Training is located in CU-CP or OAM, and AI/ML Model Inference function is located in CU-CP

gNB is also allowed to continue model training based on AI/ML model trained in the OAM.

Step 0. NG-RAN node 2 is assumed to optionally have an AI/ML model, which can generate required input such as resource status and utilization prediction/estimation etc.

Step 1. The NG-RAN node configures the measurement information on the UE side and sends configuration message to UE including configuration information.

Step 2. The UE collects the indicated measurement, e.g., UE measurements related to RSRP, RSRQ, SINR of serving cell and neighbouring cells.

Step 3. The UE sends measurement report message to NG-RAN node 1 including the required measurement.

Step 4. The NG-RAN node 1 sends the input data for training to OAM, where the input data for training includes the required input information from the NG-RAN node 1 and the measurement from UE.

Step 5. The NG-RAN node 2 sends the input data for training to OAM, where the input data for training includes the required input information from the NG-RAN node 2. If the NG-RAN node 2 executes the AI/ML model, the input data for training can include the corresponding inference result from the NG-RAN node 2.

Step 6. Model Training. Required measurements are leveraged to training AI/ML model for UE mobility optimization.

Step 7. OAM sends AI/ML Model Deployment Message to deploy the trained/updated AI/ML model into the NG-RAN node(s). The NG-RAN node can also continue model training based on the received AI/ML model from OAM.

Step 8. The NG-RAN node 1 obtains the measurement report as inference data for UE mobility optimization.

Step 9. The NG-RAN node 1 obtains the input data for inference from the NG-RAN node 2 for UE mobility optimization, where the input data for inference includes the required input information from the NG-RAN node 2. If the NG-RAN node 2 executes the AI/ML model, the input data for inference can include the corresponding inference result from the NG-RAN node 2.

Step 10. Model Inference. Required measurements are leveraged into Model Inference to output the prediction, e.g., UE trajectory prediction, target cell prediction, target NG-RAN node prediction, etc.

Step 11. The NG-RAN 1 sends the model performance feedback to OAM if applicable.

Note: This step is out of RAN3 scope.

Step 12: According to the prediction, recommended actions or configuration, the NG-RAN node 1, the target NG-RAN node (represented by NG-RAN node 2 of this step in the flowchart), and UE perform the Mobility Optimization / handover procedure to hand over UE from NG-RAN node 1 to the target NG-RAN node.

Step 13. The NG-RAN node 1 sends the feedback information to OAM.

Step 14. The NG-RAN node 2 sends the feedback information to OAM.

Step 1. NG-RAN node1 configures the measurement information on the UE side and sends configuration message to UE including configuration information.

Step 2. UE collects the indicated measurement, e.g., UE measurements related to RSRP, RSRQ, SINR of serving cell and neighbouring cells.

Step 3. UE sends measurement report message to NG-RAN node1 including the required measurement.

Step 4. The NG-RAN node 1 obtains the input data for training from the NG-RAN node2, where the input data for training includes the required input information from the NG-RAN node 2. If the NG-RAN node 2 executes the AI/ML model, the input data for training can include the corresponding inference result from the NG-RAN node 2.

Step 5. Model training. Required measurements are leveraged to training AI/ML model for mobility optimization.

Step 6. NG-RAN node1 obtains the measurement report as inference data for real-time UE mobility optimization.

Step 7. The NG-RAN node 1 obtains the input data for inference from the NG-RAN node 2 for UE mobility optimization, where the input data for inference includes the required input information from the NG-RAN node 2. If the NG-RAN node 2 executes the AI/ML model, the input data for inference can include the corresponding inference result from the NG-RAN node 2.

Step 8. Model Inference. Required measurements are leveraged into Model Inference to output the prediction, including e.g., UE trajectory prediction, target cell prediction, target NG-RAN node prediction, etc.

Step 9: According to the prediction, recommended actions or configuration, the NG-RAN node 1, the target NG-RAN node (represented by NG-RAN node 2 of this step in the flowchart), and UE perform the Mobility Optimization / handover procedure to hand over UE from NG-RAN node 1 to the target NG-RAN node.

Step 10. The NG-RAN node 2 sends feedback information after mobility optimization action to the NG-RAN node 1.

For example, UE mobility information for training purposes is only sent to gNBs that requested such information or when triggered.

Input of AI/ML-based Mobility Optimization

The following data is required as input data for mobility optimization.

From the UE:

- UE location information (e.g., coordinates, serving cell ID, moving velocity) interpreted by gNB implementation when available.

- Radio measurements related to serving cell and neighbouring cells associated with UE location information, e.g., RSRP, RSRQ, SINR.

- UE Mobility History Information.

From the neighbouring RAN nodes:

- UE's history information from neighbour

- Position, QoS parameters and the performance information of historical HO-ed UE (e.g., loss rate, delay, etc.)

- Current/predicted resource status

- UE handovers in the past that were successful and unsuccessful, including too-early, too-late, or handover to wrong (sub-optimal) cell, based on existing SON/RLF report mechanism.

From the local node:

- UE trajectory prediction

- Current/predicted resource status

- Current/predicted UE traffic

Output of AI/ML-based Mobility Optimization

AI/ML-based mobility optimization can generate following information as output:

- UE trajectory prediction (Latitude, longitude, altitude, cell ID of UE over a future period of time)

Note: Whether the UE trajectory prediction is an external output to the node hosting the Model Inference function should be discussed during the normative work phase.

- Estimated arrival probability in CHO and relevant confidence interval

- Predicted handover target node, candidate cells in CHO, may together with the confidence of the predication

- Priority, handover execution timing, predicted resource reservation time window for CHO.

- UE traffic prediction (will be used by the RAN node internally and the details are left to normative work phase)

- Model output validity time will be discussed during R18 normative work per inference output.

Feedback of AI/ML-based Mobility Optimization

The following data is required as feedback data for mobility optimization.

- QoS parameters such as throughput, packet delay of the handed-over UE, etc.

- Resource status information updates from target NG-RAN.

- Performance information from target NG-RAN. The details of performance information are to be discussed during normative work phase.

Standard impact

To improve the mobility decisions at a gNB (gNB-CU), a gNB can request mobility feedback from a neighbouring node. Details of the procedure will be determined during the normative phase.

If existing UE measurements are needed by a gNB for AI/ML-based mobility optimization, RAN3 shall reuse the existing framework (including MDT and RRM measurements). Whether new UE measurements are needed is left to normative phase based on the use case description.

MDT procedure enhancements should be discussed during the normative phase.

Potential Xn interface impact:

- Predicted resource status info and performance info from candidate target NG-RAN node to source NG-RAN node

- New signaling procedure or existing procedure to retrieve input information via Xn interface.

- New signaling procedure or existing procedure to retrieve feedback information via Xn interface.

Hereinafter, technical features related to AI and ML are described.

Artificial Intelligence (AI)/Machine Learning (ML) is being used in a range of application domains across industry sectors, realizing significant productivity gains. In particular, in mobile communications systems, mobile devices (e.g. smartphones, smart vehicles, UAVs, mobile robots) are increasingly replacing conventional algorithms (e.g. speech recognition, machine translation, image recognition, video processing, user behaviour prediction) with AI/ML models to enable applications like enhanced photography, intelligent personal assistants, VR/AR, video gaming, video analytics, personalized shopping recommendation, autonomous driving/navigation, smart home appliances, mobile robotics, mobile medicals, as well as mobile finance.

Artificial Intelligence (AI) is the science and engineering to build intelligent machines capable of carrying out tasks as humans do.

Deep neural network

Within the ML field, there is an area that is often referred to as brain-inspired computation, which is a program aiming to emulate some aspects of how we understand the brain to operate. Since it is believed that the main computational elements a human brain are 86 billion neurons, the two subareas of brain-inspired computation are both inspired by the architecture of a neuron, as shown in FIG. 13.

Compared to spiking computing approaches, the more popular ML approaches are using "neural network" as the model. Neural networks (NN) take their inspiration from the notion that a neuron's computation involves a weighted sum of the input values. But instead of simply outputting the weighted sum, a NN applies a nonlinear function to generate an output only if the inputs cross some threshold, as shown in FIG. 13.

FIG. 14 shows a diagrammatic picture of a computational neural network. The neurons in the input layer receive some values and propagate them to the neurons in the middle layer of the network, which is also called a "hidden layer". The weighted sums from one or more hidden layers are ultimately propagated to the output layer, which presents the final outputs of the network.

Neural networks having more than three layers, i.e., more than one hidden layer are called deep neural networks (DNN). In contrast to the conventional shallow-structured NN architectures, DNNs, also referred to as deep learning, made amazing breakthroughs since 2010s in many essential application areas because they can achieve human-level accuracy or even exceed human accuracy. Deep learning techniques use supervised and/or unsupervised strategies to automatically learn hierarchical representations in deep architectures for classification. With a large number of hidden layers, the superior performance of DNNs comes from its ability to extract high-level features from raw sensory data after using statistical learning over a large amount of data to obtain an effective representation of an input space. In recent years, thanks to the big data obtained from the real world, the rapidly increased computation capacity and continuously-evolved algorithms, DNNs have become the most popular ML models for many AI applications.

Training and inference

Training is a process in which a AI/ML model learns to perform its given tasks, more specifically, by optimizing the value of the weights in the DNN. A DNN is trained by inputting a training set, which are often correctly-labelled training samples. Taking image classification for instance, the training set includes correctly-classified images. When training a network, the weights are usually updated using a hill-climbing optimization process called gradient descent. The gradient indicates how the weights should change in order to reduce the loss (the gap between the correct outputs and the outputs computed by the DNN based on its current weights). The training process is repeated iteratively to continuously reduce the overall loss. Until the loss is below a predefined threshold, the DNN with high precision is obtained.

There are multiple ways to train the network for different targets. The introduced above is supervised learning which uses the labelled training samples to find the correct outputs for a task. Unsupervised learning uses the unlabelled training samples to find the structure or clusters in the data. Reinforcement learning can be used to output what action the agent should take next to maximize expected rewards. Transfer learning is to adjust the previously-trained weights (e.g. weights in a global model) using a new training set, which is used for a faster or more accurate training for a personalized model.

FIG. 15 shows an example of an AI/ML inference.

After a DNN is trained, it can perform its task by computing the output of the network using the weights determined during the training process, which is referred to as inference. In the model inference process, the inputs from the real world are passed through the DNN. Then the prediction for the task is output, as shown in FIG. 15. For instance, the inputs can be pixels of an image, sampled amplitudes of an audio wave or the numerical representation of the state of some system or game. Correspondingly, the outputs of the network can be a probability that an image contains a particular object, the probability that an audio sequence contains a particular word or a bounding box in an image around an object or the proposed action that should be taken.

The performance of DNNs is gained at the cost of high computational complexity. Hence more efficient compute engines are often used, e.g. graphics processing units (GPU) and network processing units (NPU). Compared to the inference which only involves the feedforward process, the training often requires more computation and storage resources because it involves also the backpropagation process.

Widely-used DNN models and algorithms

FIG. 16 shows an example of an MLP DNN model.

Many DNN models have been developed over the past two decades. Each of these models has a different "network architecture" in terms of number of layers, layer types, layer shapes (i.e., filter size, number of channels and filters), and connections between layers. FIG. 16 presents three popular structures of DNNs: multilayer perceptrons (MLPs), convolution neural networks (CNNs), and recurrent neural networks (RNNs). Multilayer perceptrons (MLP) model is the most basic DNN, which is composed of a series of fully connected layers. In a fully connected layer, all outputs are connected to all inputs, as shown in FIG. 16. Hence MLP requires a significant amount of storage and computation.

FIG. 17 shows an example of a CNN model.

An approach to limiting the number of weights that contribute to an output is to calculate the output only using a function of a fixed-size window of inputs. An extremely popular window-based DNN model uses a convolution operation to structure the computation, hence is named as convolution neural network (CNN). A CNN is composed of multiple convolutional layers, as shown in FIG. 17. Applying various convolutional filters, CNN models can capture the high-level representation of the input data, making it popular for image classification and speech recognition tasks.

FIG. 18 shows an example of an RNN model.

Recurrent neural network (RNN) models are another type of DNNs, which use sequential data feeding. The input of RNN consists of the current input and the previous samples. Each neuron in an RNN owns an internal memory that keeps the information of the computation from the previous samples. As shown in FIG. 18, the basic unit of RNN is called cell, and further, each cell consists of layers and a series of cells enables the sequential processing of RNN models. RNN models have been widely used in the natural language processing task on mobile devices, e.g., language modelling, machine translation, question answering, word embedding, and document classification.

FIG. 19 shows an example of Reinforcement learning.

Deep reinforcement learning (DRL) is not another DNN model. It is composed of DNNs and reinforcement learning. As illustrated in FIG. 19, the goal of DRL is to create an intelligent agent that can perform efficient policies to maximize the rewards of long-term tasks with controllable actions. The typical application of DRL is to solve various scheduling problems, such as decision problems in games, rate selection of video transmission, and so on.

Hereinafter, technical features related to logged measurements are described. Section 5.5a of 3GPP TS 38.331 v17.5.0 may be referred.

FIG. 20 shows an example of a logged measurement configuration.

The purpose of this procedure is to configure the UE to perform logging of measurement results while in RRC_IDLE and RRC_INACTIVE. The procedure applies to logged measurements capable UEs that are in RRC_CONNECTED.

For example, NG-RAN may retrieve stored logged measurement information by means of the UE information procedure.

NG-RAN initiates the logged measurement configuration procedure to UE in RRC_CONNECTED by sending the LoggedMeasurementConfiguration message.

Reception of the LoggedMeasurementConfiguration by the UE

Upon receiving the LoggedMeasurementConfiguration message the UE shall:

1> discard the logged measurement configuration as well as the logged measurement information;

1> store the received loggingDuration, reportType and areaConfiguration, if included, in VarLogMeasConfig;

1> if the LoggedMeasurementConfiguration message includes plmn -IdentityList:

2> set plmn - IdentityList in VarLogMeasReport to include the RPLMN as well as the PLMNs included in plmn - IdentityList;

1> else:

2> set plmn - IdentityList in VarLogMeasReport to include the RPLMN;

1> store the received absoluteTimeInfo, traceReference , traceRecordingSessionRef, and tce -Id in VarLogMeasReport;

1> store the received bt - NameList, if included, in VarLogMeasConfig;

1> store the received wlan - NameList, if included, in VarLogMeasConfig;

1> store the received sensor- NameList, if included, in VarLogMeasConfig;

1> start timer T330 with the timer value set to the loggingDuration;

1> store the received sigLoggedMeasType , if included, in VarLogMeasReport;

1> store the received earlyMeasIndication , if included, in VarLogMeasConfig;

Release of Logged Measurement Configuration

The purpose of this procedure is to release the logged measurement configuration as well as the logged measurement information.

The UE shall initiate the procedure upon receiving a logged measurement configuration in same or another RAT. The UE shall also initiate the procedure upon power off or upon deregistration.

The UE shall:

1> stop timer T330, if running;

1> if stored, discard the logged measurement configuration as well as the logged measurement information, i.e. release the UE variables VarLogMeasConfig and VarLogMeasReport

Measurements logging

This procedure specifies the logging of available measurements by a UE in RRC_IDLE and RRC_INACTIVE that has a logged measurement configuration. The actual process of logging within the UE, takes place in RRC IDLE state could continue in RRC INACTIVE state or vice versa.

While T330 is running and SDT procedure is not ongoing, the UE shall:

1> if measurement logging is suspended:

2> if during the last logging interval the IDC problems detected by the UE is resolved, resume measurement logging;

1> if not suspended, perform the logging in accordance with the following:

2> if the reportType is set to periodical in the VarLogMeasConfig:

3> if the UE is in any cell selection state:

4> perform the logging at regular time intervals, as defined by the loggingInterval in the VarLogMeasConfig;

3> if the UE is in camped normally state on an NR cell and if the RPLMN is included in plmn - IdentityList stored in VarLogMeasReport:

4> if areaConfiguration is not included in VarLogMeasConfig; or

4> if the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig:

5> perform the logging at regular time intervals, as defined by the loggingInterval in the VarLogMeasConfig;

2> else if the reportType is set to eventTriggered, and eventType is set to outOfCoverage:

3> perform the logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig only when the UE is in any cell selection state;

3> upon transition from any cell selection state to camped normally state in NR:

4> if the RPLMN is included in plmn - IdentityList stored in VarLogMeasReport; and

4> if areaConfiguration is not included in VarLogMeasConfig or if the current camping cell is part of the area indicated by areaConfig of areaConfiguration in VarLogMeasConfig:

5> perform the logging;

2> else if the reportType is set to eventTriggered and eventType is set to eventL1:

4> if areaConfiguration is not included in VarLogMeasConfig; or

4> if the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig;

5> perform the logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig only when the conditions indicated by the eventL1 are met;

2> when performing the logging:

3> if InterFreqTargetInfo is configured and if the UE detected IDC problems on at least one of the frequencies included in InterFreqTargetInfo or any inter-RAT frequency during the last logging interval, or

3> if InterFreqTargetInfo is not configured and if the UE detected IDC problems during the last logging interval:

4> if measResultServingCell in the VarLogMeasReport is not empty:

5> include inDeviceCoexDetected;

5> suspend measurement logging from the next logging interval;

4> else:

5> suspend measurement logging;

3> set the relativeTimeStamp to indicate the elapsed time since the moment at which the logged measurement configuration was received;

3> if location information became available during the last logging interval, set the content of the locationInfo:

3> if the UE is in any cell selection state:

4> set anyCellSelectionDetected to indicate the detection of no suitable or no acceptable cell found;

4> if the reportType is set to eventTriggered in the VarLogMeasConfig; and

4> if the RPLMN at the time of entering the any cell selection state is included in plmn - IdentityList stored in VarLogMeasReport; and

4> if areaConfiguration is not included in VarLogMeasConfig or if the last suitable cell that the UE was camping on is part of the area indicated by areaConfig of areaConfiguration in VarLogMeasConfig:

5> set the servCellIdentity to indicate global cell identity of the last suitable cell that the UE was camping on;

5> set the measResultServingCell to include the quantities of the last suitable cell the UE was camping on;

4> else if the reportType is set to periodical in the VarLogMeasConfig:

5> set the servCellIdentity to indicate global cell identity of the last logged cell that the UE was camping on;

5> set the measResultServingCell to include the quantities of the last logged cell the UE was camping on;

3> else:

4> set the servCellIdentity to indicate global cell identity of the cell the UE is camping on;

4> set the measResultServingCell to include the quantities of the cell the UE is camping on;

3> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-selection, to include measurements of neighbouring cell that became available during the last logging interval and according to the following:

4> include measurement results for at most 6 neighbouring cells on the NR serving frequency and for at most 3 cells per NR neighbouring frequency and for the NR neighbouring frequencies in accordance with the following:

5> if interFreqTargetInfo is included in VarLogMeasConfig:

6> if earlyMeasIndication is included in VarLogMeasConfig;

7> include measurement results for NR neighbouring frequencies that are included in both interFreqTargetInfo and either in measIdleCarrierListNR (within the VarMeasIdleConfig) or SIB4;

6> else:

7> include measurement results for NR neighbouring frequencies that are included in both interFreqTargetInfo and SIB4;

5> else:

6> if earlyMeasIndication is included in VarLogMeasConfig;

7> include measurement results for NR neighbouring frequencies that are included in either measIdleCarrierListNR (within the VarMeasIdleConfig) or SIB4;

6> else:

7> include measurement results for NR neighbouring frequencies that are included in SIB4;

4> include measurement results for at most 3 neighbours per inter-RAT frequency in accordance with the following:

5> if earlyMeasIndication is included in VarLogMeasConfig:

6> include measurement results for inter-RAT neighbouring frequencies that are included in either measIdleCarrierListEUTRA (within the VarMeasIdleConfig) or SIB5;

5> else:

6> include measurement results for inter-RAT frequencies that are included in SIB5;

4> for each neighbour cell included, include the optional fields that are available;

For example, the UE includes the latest results of the available measurements as used for cell reselection evaluation in RRC_IDLE or RRC_INACTIVE, which are performed in accordance with the performance requirements.

For logging the measurements on frequencies (indicated in measIdleCarrierListNR/ measIdleCarrierListEUTRA) in the logged measurement, the qualityThreshold in measIdleConfig should not be applied, and how the UE logs the measurements on the frequencies is left to the UE implementation.

2> when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330.

UE information Procedure

FIG. 21 shows an example of UE information procedure.

The UE information procedure is used by the network to request the UE to report information.

The network initiates the procedure by sending the UEInformationRequest message. The network should initiate this procedure only after successful security activation.

Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:

1> if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored VarMeasIdleReport that contains measurement information concerning cells other than the PCell:

2> set the measResultIdleEUTRA in the UEInformationResponse message to the value of measReportIdleEUTRA in the VarMeasIdleReport , if available;

2> set the measResultIdleNR in the UEInformationResponse message to the value of measReportIdleNR in the VarMeasIdleReport, if available;

2> discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;

1> if the logMeasReportReq is present and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

2> if VarLogMeasReport includes one or more logged measurement entries, set the contents of the logMeasReport in the UEInformationResponse message as follows:

3> include the absoluteTimeStamp and set it to the value of absoluteTimeInfo in the VarLogMeasReport;

3> include the traceReference and set it to the value of traceReference in the VarLogMeasReport;

3> include the traceRecordingSessionRef and set it to the value of traceRecordingSessionRef in the VarLogMeasReport ;

3> include the tce -Id and set it to the value of tce -Id in the VarLogMeasReport;

3> include the logMeasInfoList and set it to include one or more entries from the VarLogMeasReport starting from the entries logged first, and for each entry of the logMeasInfoList that is included, include all information stored in the corresponding logMeasInfoList entry in VarLogMeasReport;

3> if the VarLogMeasReport includes one or more additional logged measurement entries that are not included in the logMeasInfoList within the UEInformationResponse message:

4> include the logMeasAvailable;

4> if bt - LocationInfo is included in locationInfo of one or more of the additional logged measurement entries in VarLogMeasReport that are not included in the logMeasInfoList within the UEInformationResponse message:

5> include the logMeasAvailableBT;

4> if wlan - LocationInfo is included in locationInfo of one or more of the additional logged measurement entries in VarLogMeasReport that are not included in the logMeasInfoList within the UEInformationResponse message:

5> include the logMeasAvailableWLAN;

1> if ra- ReportReq is set to true and the UE has random access related information available in VarRA -Report and if the RPLMN is included in plmn -IdentityList stored in VarRA -Report:

2> set the ra- ReportList in the UEInformationResponse message to the value of ra- ReportList in VarRA -Report;

2> discard the ra- ReportList from VarRA -Report upon successful delivery of the UEInformationResponse message confirmed by lower layers;

1> if rlf - ReportReq is set to true:

2> if the UE has radio link failure information or handover failure information available in VarRLF -Report and if the RPLMN is included in plmn -IdentityList stored in VarRLF -Report:

3> set timeSinceFailure in VarRLF -Report to the time that elapsed since the last radio link failure or handover failure in NR;

3> set the rlf -Report in the UEInformationResponse message to the value of rlf -Report in VarRLF -Report;

3> discard the rlf -Report from VarRLF -Report upon successful delivery of the UEInformationResponse message confirmed by lower layers;

2> else if the UE is capable of cross-RAT RLF reporting and has radio link failure information or handover failure information available in VarRLF -Report and if the RPLMN is included in plmn - IdentityList stored in VarRLF -Report:

3> set timeSinceFailure in VarRLF -Report to the time that elapsed since the last radio link failure or handover failure in EUTRA;

3> set failedPCellId-EUTRA in the rlf -Report in the UEInformationResponse message to indicate the PCell in which RLF was detected or the source PCell of the failed handover in the VarRLF -Report;

3> set the measResult - RLF -Report- EUTRA in the rlf -Report in the UEInformationResponse message to the value of rlf -Report in VarRLF -Report;

1> if connEstFailReportReq is set to true and the UE has connection establishment failure or connection resume failure information in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList:

2> set timeSinceFailure in VarConnEstFailReport to the time that elapsed since the last connection establishment failure or connection resume failure in NR;

2> set the connEstFailReport in the UEInformationResponse message to the value of connEstFailReport in VarConnEstFailReport;

2> if the UE supports multiple CEF report:

3> for each connEstFailReport in the connEstFailReportList in VarConnEstFailReportList:

4> set timeSinceFailure to the time that elapsed since the associated connection establishment failure or connection resume failure in NR;

2> for each connEstFailReport in the connEstFailReportList in the UEInformationResponse message, set the value to the value of connEstFailReport in VarConnEstFailReport in VarConnEstFailReportList;

2> discard the connEstFailReport from VarConnEstFailReport and VarConnEstFailReportList upon successful delivery of the UEInformationResponse message confirmed by lower layers;

1> if the mobilityHistoryReportReq is set to true:

2> include the mobilityHistoryReport and set it to include visitedCellInfoList from VarMobilityHistoryReport;

2> include in the mobilityHistoryReport an entry for the current PCell, possibly after removing the oldest entry if required, and set its fields as follows:

3> set visitedCellId to the global cell identity or the physical cell identity and carrier frequency of the current PCell:

3> set field timeSpent to the time spent in the current PCell;

3> if the UE supports PSCell mobility history information and if visitedPSCellInfoList is present in VarMobilityHistoryReport:

4> for the newest entry of the PCell in the mobilityHistoryReport, include visitedPSCellInfoList from VarMobilityHistoryReport;

4> if the UE is configured with a PSCell:

5> for the newest entry of the PCell in the mobilityHistoryReport, include the current PSCell information in the visitedPSCellInfoListReport , possibly after removing the oldest PSCell entry of a PCell in the mobilityHistoryReport, if required, and set its fields as follows:

6> set visitedCellId to the global cell identity or the physical cell identity and carrier frequency of the current PSCell:

6> set field timeSpent to the time spent in the current PSCell while being connected to the current PCell;

4> else:

5> for the newest entry of the PCell in the mobilityHistoryReport, include a new entry in the visitedPSCellInfoListReport , possibly after removing the oldest PSCell entry of a PCell in the mobilityHistoryReport, if required, and set its fields as follows:

6> set field timeSpent to the time spent without PSCell in the current PCell since last PSCell release since connected to the current PCell in RRC_CONNECTED;

3> else if the UE supports PSCell mobility history information:

4> if the UE is configured with a PSCell:

4> else:

6> set field timeSpent to the time spent without PSCell in the current PCell since connected to the current PCell in RRC_CONNECTED;

1> if the successHO - ReportReq is set to true and if the UE has successful handover related information available in VarSuccessHO -Report and if the RPLMN is included in the plmn - IdentityList stored in VarSuccessHO -Report:

2> if the successHO -Report in the VarSuccessHO -Report concerns a DAPS handover and if a PDCP PDU has been received from the source cell of the concerned HO and a non-duplicated PDCP PDU has been received from the target cell of the concerned HO:

3> set upInterruptionTimeAtHO in VarSuccessHO -Report to include the time elapsed between the time of arrival of the last PDCP PDU received from the source cell of the concerned handover and the time of arrival of the first non-duplicate PDCP PDU received from the target cell of the concerned handover, as measured at the time of arrival of the first non-duplicate PDCP PDU received from the target cell;

2> set the successHO -Report in the UEInformationResponse message to the value of successHO -Report in the VarSuccessHO -Report, if available;

2> discard the VarSuccessHO -Report upon successful delivery of the UEInformationResponse message confirmed by lower layers;

1> if the coarseLocationRequest is set to true:

2> include coarseLocationInfo , if available;

1> if the logMeasReport is included in the UEInformationResponse:

2> submit the UEInformationResponse message to lower layers for transmission via SRB2;

2> discard the logged measurement entries included in the logMeasInfoList from VarLogMeasReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;

1> else:

2> submit the UEInformationResponse message to lower layers for transmission via SRB1.

Hereinafter, technical features related to measurements are described. Sections of 3GPP TS 38.331 v17.5.0 may be referred.

The network may configure an RRC_CONNECTED UE to perform measurements. The network may configure the UE to report them in accordance with the measurement configuration or perform conditional reconfiguration evaluation in accordance with the conditional reconfiguration. The measurement configuration is provided by means of dedicated signalling i.e. using the RRCReconfiguration or RRCResume .

The network may configure the UE to perform the following types of measurements:

- NR measurements;

- Inter-RAT measurements of E-UTRA frequencies;

- Inter-RAT measurements of UTRA-FDD frequencies;

- NR sidelink measurements of L2 U2N Relay UEs.

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

- Measurement results per SS/PBCH block;

- Measurement results per cell based on SS/PBCH block(s);

- SS/PBCH block(s) indexes.

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

- Measurement results per CSI-RS resource;

- Measurement results per cell based on CSI-RS resource(s);

- CSI-RS resource measurement identifiers.

The network may configure the UE to perform the following types of measurements for NR sidelink and V2X sidelink:

- CBR measurements.

The network may configure the UE to report the following CLI measurement information based on SRS resources:

- Measurement results per SRS resource;

- SRS resource(s) indexes.

The network may configure the UE to report the following CLI measurement information based on CLI-RSSI resources:

- Measurement results per CLI-RSSI resource;

- CLI-RSSI resource(s) indexes.

The network may configure the UE to report the following Rx-Tx time difference measurement information based on CSI-RS for tracking or PRS:

- UE Rx-Tx time difference measurement result.

The measurement configuration includes the following parameters:

1. Measurement objects: A list of objects on which the UE shall perform the measurements.

- For intra-frequency and inter-frequency measurements a measurement object indicates the frequency/time location and subcarrier spacing of reference signals to be measured. Associated with this measurement object, the network may configure a list of cell specific offsets, a list of 'exclude-listed' cells and a list of 'allow-listed' cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting. Allow-listed cells are the only ones applicable in event evaluation or measurement reporting.

- The measObjectId of the MO which corresponds to each serving cell is indicated by servingCellMO within the serving cell configuration.

- For inter-RAT E-UTRA measurements a measurement object is a single E-UTRA carrier frequency. Associated with this E-UTRA carrier frequency, the network can configure a list of cell specific offsets and a list of 'exclude-listed' cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting.

- For inter-RAT UTRA-FDD measurements a measurement object is a set of cells on a single UTRA-FDD carrier frequency.

- For NR sidelink measurements of L2 U2N Relay UEs, a measurement object is a single NR sidelink frequency to be measured.

- For CBR measurement of NR sidelink communication, a measurement object is a set of transmission resource pool(s) on a single carrier frequency for NR sidelink communication.

- For CBR measurement of NR sidelink discovery, a measurement object is a set of discovery dedicated resource pool(s) or transmission resource pool(s) also used for NR sidelink discovery on a single carrier frequency for NR sidelink discovery.

- For CLI measurements a measurement object indicates the frequency/time location of SRS resources and/or CLI-RSSI resources, and subcarrier spacing of SRS resources to be measured.

2. Reporting configurations: A list of reporting configurations where there can be one or multiple reporting configurations per measurement object. Each measurement reporting configuration consists of the following:

- Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be periodical or a single event description.

- RS type: The RS that the UE uses for beam and cell measurement results (SS/PBCH block or CSI-RS).

- Reporting format: The quantities per cell and per beam that the UE includes in the measurement report (e.g. RSRP) and other associated information such as the maximum number of cells and the maximum number beams per cell to report.

In case of conditional reconfiguration, each configuration consists of the following:

- Execution criteria: The criteria the UE uses for conditional reconfiguration execution.

- RS type: The RS that the UE uses for obtaining beam and cell measurement results (SS/PBCH block-based or CSI-RS-based), used for evaluating conditional reconfiguration execution condition.

3. Measurement identities: For measurement reporting, a list of measurement identities where each measurement identity links one measurement object with one reporting configuration. By configuring multiple measurement identities, it is possible to link more than one measurement object to the same reporting configuration, as well as to link more than one reporting configuration to the same measurement object. The measurement identity is also included in the measurement report that triggered the reporting, serving as a reference to the network. For conditional reconfiguration triggering, one measurement identity links to exactly one conditional reconfiguration trigger configuration. And up to 2 measurement identities can be linked to one conditional reconfiguration execution condition.

4. Quantity configurations: The quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement. For NR measurements, the network may configure up to 2 quantity configurations with a reference in the NR measurement object to the configuration that is to be used. In each configuration, different filter coefficients can be configured for different measurement quantities, for different RS types, and for measurements per cell and per beam.

5. Measurement gaps: Periods that the UE may use to perform measurements.

A UE in RRC_CONNECTED maintains a measurement object list, a reporting configuration list, and a measurement identities list according to signalling and procedures in this specification. The measurement object list possibly includes NR measurement object(s), CLI measurement object(s), inter-RAT objects, and L2 U2N Relay objects. Similarly, the reporting configuration list includes NR, inter-RAT, and L2 U2N Relay reporting configurations. Any measurement object can be linked to any reporting configuration of the same RAT type. Some reporting configurations may not be linked to a measurement object. Likewise, some measurement objects may not be linked to a reporting configuration.

The measurement procedures distinguish the following types of cells:

1. The NR serving cell(s) - these are the SpCell and one or more SCells.

2. Listed cells - these are cells listed within the measurement object(s).

3. Detected cells - these are cells that are not listed within the measurement object(s) but are detected by the UE on the SSB frequency(ies) and subcarrier spacing(s) indicated by the measurement object(s).

For NR measurement object(s), the UE measures and reports on the serving cell(s)/serving Relay UE (for L2 U2N Remote UE), listed cells and/or detected cells. For inter-RAT measurements object(s) of E-UTRA, the UE measures and reports on listed cells and detected cells and, for RSSI and channel occupancy measurements, the UE measures and reports on the configured resources on the indicated frequency. For inter-RAT measurements object(s) of UTRA-FDD, the UE measures and reports on listed cells. For CLI measurement object(s), the UE measures and reports on configured measurement resources (i.e. SRS resources and/or CLI-RSSI resources). For L2 U2N Relay object(s), the UE measures and reports on the serving NR cell(s), as well as the discovered L2 U2N Relay UEs.

Whenever the procedural specification, other than contained in clause 5.5.2, refers to a field it concerns a field included in the VarMeasConfig unless explicitly stated otherwise i.e. only the measurement configuration procedure covers the direct UE action related to the received measConfig.

In NR-DC, the UE may receive two independent measConfig:

- a measConfig, associated with MCG, that is included in the RRCReconfiguration message received via SRB1; and

- a measConfig, associated with SCG, that is included in the RRCReconfiguration message received via SRB3, or, alternatively, included within a RRCReconfiguration message embedded in a RRCReconfiguration message received via SRB1.

In this case, the UE maintains two independent VarMeasConfig and VarMeasReportList, one associated with each measConfig, and independently performs all the procedures in clause 5.5 for each measConfig and the associated VarMeasConfig and VarMeasReportList, unless explicitly stated otherwise.

The configurations related to CBR measurements are only included in the measConfig associated with MCG.

The configurations related to Rx-Tx time difference measurement are only included in the measConfig associated with MCG.

Examples of events for measurement reporting are described.

Event A1 (Serving becomes better than threshold)

Event A2 (Serving becomes worse than threshold)

Event A3 (Neighbour becomes offset better than SpCell)

Event A4 (Neighbour becomes better than threshold)

Event A5 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2)

Event A6 (Neighbour becomes offset better than SCell)

Event B1 (Inter RAT neighbour becomes better than threshold)

Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2)

Event I1 (Interference becomes higher than threshold)

Event C1 (The NR sidelink channel busy ratio is above a threshold)

Event C2 (The NR sidelink channel busy ratio is below a threshold)

Event D1 (Distance between UE and referenceLocation1 is above threshold1 and distance between UE and referenceLocation2 is below threshold2)

CondEvent T1 (Time measured at UE is within a duration from threshold)

Event X1 (Serving L2 U2N Relay UE becomes worse than threshold1 and NR Cell becomes better than threshold2)

Event X2 (Serving L2 U2N Relay UE becomes worse than threshold)

Event Y1 (PCell becomes worse than threshold1 and candidate L2 U2N Relay UE becomes better than threshold2)

Event Y2 (Candidate L2 U2N Relay UE becomes better than threshold)

FIG. 22 shows an example of measurement reporting.

The purpose of this procedure is to transfer measurement results from the UE to the network. The UE shall initiate this procedure only after successful AS security activation.

FIG. 23 shows an example of location measurement indication.

The purpose of this procedure is to indicate to the network that the UE is going to start/stop location related measurements towards E-UTRA or NR (eutra-RSTD, nr-RSTD, nr-UE-RxTxTimeDiff, nr-PRS-RSRP) which require measurement gaps or start/stop detection of subframe and slot timing towards E-UTRA (eutra-FineTimingDetection) which requires measurement gaps. UE shall initiate this procedure only after successful AS security activation.

Meanwhile, beam management use case is discussed for the spatial prediction and temporal prediction. To train the model for this use case, L1-RSRP and/or beam index are considered as data for training/inference/monitoring purpose.

Therefore, studies for reporting stored measurement results are required.

Hereinafter, a method for reporting stored measurement results, according to some embodiments of the present disclosure, will be described with reference to the following drawings.

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. Herein, a wireless device may be referred to as a user equipment (UE).

FIG. 24 shows an example of a method for reporting stored measurement results.

In particular, FIG. 24 shows an example of a method performed by a wireless device in a wireless communication system.

In step S2401, a wireless device may receive a report configuration including information related to a count threshold.

For example, the wireless device may enter into a radio resource control (RRC) connected state. For example, a wireless device may receive a report configuration while in the RRC connected state.

In step S2402, a wireless device may perform measurements for a signal block and/or a reference signal.

For example, the measurements for the signal block and/or the reference signal may be performed while in the RRC connected state. For example, the wireless device may perform measurements for a signal block and/or a reference signal, while in the RRC connected state.

In step S2403, a wireless device may count a number of measurement results for the signal block and/or the reference signal.

For example, the wireless device may increment a counter upon performing the measurements for a signal block and/or a reference signal. For example, the wireless device may increment a counter upon performing the measurements for a set of a signal block and/or a set of a reference signal.

In step S2404, a wireless device may transmit a message including information informing that the number of the measurement results are available, based on that the number of the measurement results is equal to or greater than the count threshold.

For example, the message may include (i) information related to the number of measurement results and (ii) indication informing that the number of the measurement results are available.

For example, the wireless device may receive a request of the stored measurement results from the network. The wireless device may transmit, to the network, a message including the stored measurement results (or the requested measurement results).

For example, the message including information informing that the number of the measurement results are available may be transmitted while in the RRC connected state. For example, the wireless device may transmit the message including information informing that the number of the measurement results are available, while in the RRC connected state.

According to some embodiments of the present disclosure, the report configuration may include information related to at least one reporting condition for measurement reporting.

For example, the wireless device may determine whether at least one reporting condition for measurement reporting is satisfied. For example, the wireless device may increment a reporting condition counter upon determining that the at least one reporting condition for measurement reporting is satisfied.

For example, the wireless device may transmit a message including information informing that the measurement results are available, based on that the reporting condition counter is equal to or greater than the count threshold.

According to some embodiments of the present disclosure, the wireless device may perform measurements for a first resource set and a second resource set.

For example, the wireless device may count a first number of measurement results for the first resource set. The wireless device may count a second number of measurement results for the second resource set.

For example, the wireless device may transmit a message including information informing that the first number of the measurement results are available, based on that the first number of the measurement results for the first resource set is equal to or greater than the count threshold. In this case, the wireless device may transmit a message including information informing that sum of the first number and the second number of the measurement results are available, based on that the sum of the first number and the second number is equal to or greater than the count threshold.

For another example, the wireless device may count a number of measurement windows for the first resource set and/or the second resource set. In this case, the wireless device may transmit a message including information informing that the number of measurement windows for the first resource set and/or the second resource set are available, based on that the number of measurement windows is equal to or greater than the count threshold.

According to some embodiments of the present disclosure, the wireless device may be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

Hereinafter, some embodiments of a method for reporting stored measurement results based on count threshold are provided.

For example, a method of reporting stored measurement results based on count threshold is provided. To this end, the network can configure a count value to trigger report, such as a number of triggering contents. The UE receives the measurement results from the lower layer and stores the results. If the number of stored measurement results is lower equal to or larger than the count value, the UE can trigger the report with stored measurement results.

FIG. 25 shows an example of a method for reporting stored measurement results.

In step S2501, the UE may receive a measurement related configuration and a count value from the network.

The network configures measurement related configuration and a count value (a number of triggering contents).

In step S2502, the UE evaluates measurement results.

From RRC point of view, RRC receives L1 measurement results from lower layer, and store the L1 measurement results.

In step S2503, if the number of L1 measurement results is equal to or larger than the count value, the UE triggers report with stored measurement results

Regarding step S2501,

1> NW may configure measurement related configuration

2> Configuration may include resource/resource set information in time/frequency/spatial domain

3> Resource information may include downlink radio resource related information, such as Synchronization signal block (SSB), Channel state information reference signal (CSI-RS), Phase Tracking reference signal (PTRS), Tracking reference signal (TRS), PRS (Positioning reference signal)

3> Resource information may include uplink radio resource related information, such as Sounding reference signal (SRS)

3> Each resource/resource set may have a resource/resource set ID

2> Configuration may include report related configuration

3> report periodicity

3> report event, for example, radio quality threshold

3> report duration, for example time information to determine logging start/stop time

3> report location, for example, location information to determine logging start/stop location

3> network information for report, for example, PLMN/TA(tracking area)/RNA(ran based notification area)/cell/frequency band/frequency/reference signal(for example, CSI-RS)/SSB, BWP

3> report additional condition, for example, data usage (data amount, QOS, etc) information, radio resource (RB, MCS, etc) information, sensing (Bluetooth, wifi, etc) information, etc

3> report amount of resource in one report (for example, nrofReportedRS)

2> Configuration may link resource(s)/resource set(s) to report related configuration

3> For example, resource set 1 is mapped to resource configuration #1 as described in FIG. 26.

FIG. 26 shows an example of resource sets mapped to report configuration.

2> Configuration may include a first number of triggering contents, denoted by N_c_1

2> Configuration may include a second number of triggering contents, denoted by N_c_2

2> Configuration may include a timer value, denoted by T_c

Regarding step S2502,

1> From RRC point of view, RRC may receives measurement results from lower layer

2> Before receiving measurement results from lower layer

3> UE may receive report command from the NW

4> NW commands may include an indication indicating a specific report config ID

4> NW command may include an indication indicating a specific resource/resource set ID

3> UE may evaluate measurement results for the radio resource configured

2> The measurement results may include one or more than one measurement results for one or more than one resource/resource set

3> The measurement results may include resource/resource set ID and/or report config ID

3> The measurement results may include measurement results for up to nrofReportedRS as many resources.

3> The measurement results may include the highest measurement result only for a resource

1> UE may store measurement result received from lower layer

Regarding step S2503,

1> UE may count the number of stored measurement results

2> UE may count the number of stored measurement results per report config ID; and/or

2> UE may count the number of stored measurement results for all report config

1> Alternative 1. If the number of stored measurement results associated with a report config ID is more than N_c_1, the UE may send a report with stored measurement results

1> Alternative 2. If the number of stored measurement results for all report config ID received from lower layer is more than N_c_2, the UE may send a report for the stored measurement results

2> for example, count the number of sets of measurement results for all report config ID

2> for example, count the number of report config ID received from lower layer

1> Alternative 3. UE may count the number of different radio resource in stored measurement results

2> for example, If the number of different radio resource in stored measurement results (for example,# of different radio resource : 5 if result set #1[csi-rs 0, 1, 2, 3], result set #2[csi-rs 0,1,2,4]) associated with a report config ID is larger than N_c_1, the UE may send a report for the stored measurement results

2> for example, If the number of different radio resource in stored measurement results (for example,# of different radio resource : 5 if result set #1[csi-rs 0, 1, 2, 3], result set #2[csi-rs 0,1,2,4]) for all report config ID is larger than N_c_2, the UE may send a report for the stored measurement results.,

1> Alternative 4. UE may count the number of measurement results based on both alternative 1 and alternative 2

2> for example,. If the number of stored measurement results associated with a report config ID is more than N_c_1 and if the number of stored measurement results for all report config ID received from lower layer is more than N_c_2, the UE may send a report for the stored measurement results

1> Alternative 5. When the number of measurement results does not satisfy the N_c_1 and/or N_c_2, UE may send a report for the stored measurement results if T_c is expired

1> All alternatives may be applied in a specific location/cell or based on report additional condition

1> In the report, UE may include measurement results related information only

2> UE may include amount of stored data (for example, the number of stored measurement results)

2> UE may include an indication indicating that it has stored data to report (for example, through UAI procedure)

2> UE may include resource/resource set ID and/or report config ID

2> In this case, UE may send stored measurement results when NW request the report to UE (for example, through UE information request/response procedure)

1> In the report, UE may include measurement results

2> UE may include resource/resource set ID and/or report config ID

1> The UE may remove the measurement results

2> when the results are sent

2> when a timer is expired

2> when the TA/cell/frequency is changed

2> when receiving a command from NW

In particular, FIG. 30 shows a method performed by a wireless device.

In step S3001, a wireless device may receive a report configuration.

The report configuration may include a count threshold.

In step S3002, a wireless device may receive measurement results from lower layer, and store the measurement results.

In step S3003, if the number of stored measurement results is equal to or more than the count threshold, a wireless device may report stored measurement results-related information.

Some of the detailed steps shown in the examples of FIGS. 24-30 may not be essential steps and may be omitted. In addition to the steps shown in FIGS. 24-30, other steps may be added, and the order of the steps may vary. Some of the above steps may have their own technical meaning.

Hereinafter, an apparatus for reporting stored measurement results, according to some embodiments of the present disclosure, will be described. Herein, the apparatus may be a wireless device (100 or 200) in FIGS. 2, 3, and 5.

For example, a wireless device may perform the methods described above. The detailed description overlapping with the above-described contents could be simplified or omitted.

Referring to FIG. 5, a wireless device 100 may include a processor 102, a memory 104, and a transceiver 106.

According to some embodiments of the present disclosure, the processor 102 may be configured to be coupled operably with the memory 104 and the transceiver 106.

The processor 102 may be adapted to perform operations.

The operations comprise: receiving a report configuration including information related to a count threshold; performing measurements for a signal block and/or a reference signal; counting a number of measurement results for the signal block and/or the reference signal; and transmitting a message including information informing that the number of the measurement results are available, based on that the number of the measurement results is equal to or greater than the count threshold.

For example, the operations further comprise: entering into a radio resource control (RRC) connected state.

For example, the measurements for the signal block and/or the reference signal are performed while in the RRC connected state.

For example, the message including information informing that the number of the measurement results are available is transmitted while in the RRC connected state.

For example, the report configuration includes information related to at least one reporting condition for measurement reporting.

For example, the operations further comprise: determining whether at least one reporting condition for measurement reporting is satisfied; and incrementing a reporting condition counter upon determining that the at least one reporting condition for measurement reporting is satisfied.

For example, the operations further comprise: transmitting a message including information informing that the measurement results are available, based on that the reporting condition counter is equal to or greater than the count threshold.

For example, the operations further comprise: performing, by the wireless device, measurements for a first resource set and a second resource set.

For example, the operations further comprise: counting a first number of measurement results for the first resource set; and counting a second number of measurement results for the second resource set.

For example, the operations further comprise: transmitting a message including information informing that the first number of the measurement results are available, based on that the first number of the measurement results for the first resource set is equal to or greater than the count threshold.

For example, the operations further comprise: transmitting a message including information informing that sum of the first number and the second number of the measurement results are available, based on that the sum of the first number and the second number is equal to or greater than the count threshold.

For example, the operations further comprise: counting a number of measurement windows for the first resource set and/or the second resource set.

For example, the operations further comprise: transmitting a message including information informing that the number of measurement windows for the first resource set and/or the second resource set are available, based on that the number of measurement windows is equal to or greater than the count threshold.

For example, the processor 102 may be configured to control the transceiver 106 to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

Hereinafter, a processor for a wireless device for reporting stored measurement results, according to some embodiments of the present disclosure, will be described.

The processor may be configured to control the wireless device to perform operations. The operations comprise: receiving a report configuration including information related to a count threshold; performing measurements for a signal block and/or a reference signal; counting a number of measurement results for the signal block and/or the reference signal; and transmitting a message including information informing that the number of the measurement results are available, based on that the number of the measurement results is equal to or greater than the count threshold.

For example, the processor may be configured to control the wireless device to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

Hereinafter, a non-transitory computer-readable medium has stored thereon a plurality of instructions for reporting stored measurement results, according to some embodiments of the present disclosure, will be described.

According to some embodiment of the present disclosure, the technical features of the present disclosure could 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 memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other storage medium.

Some example of storage medium is 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.

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

For example, non-transitory computer-readable media may include random access memory (RAM) such as synchronous dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (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.

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.

According to some embodiment of the present disclosure, a non-transitory computer-readable medium has stored thereon a plurality of instructions. The stored plurality of instructions may be executed by a processor of a wireless device.

The stored plurality of instructions may cause the wireless device to perform operations. The operations comprise: receiving a report configuration including information related to a count threshold; performing measurements for a signal block and/or a reference signal; counting a number of measurement results for the signal block and/or the reference signal; and transmitting a message including information informing that the number of the measurement results are available, based on that the number of the measurement results is equal to or greater than the count threshold.

According to some embodiments of the present disclosure, the stored plurality of instructions may cause the wireless device to be in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.

Hereinafter, a method performed by a base station (BS) for reporting stored measurement results, according to some embodiments of the present disclosure, will be described.

The method comprises: transmitting, by a base station to a wireless device, a report configuration including information related to a count threshold, wherein the wireless device performs measurements for a signal block and/or a reference signal, wherein the wireless device counts a number of measurement results for the signal block and/or the reference signal; and receiving, by the base station from the wireless device, a message including information informing that the number of the measurement results are available, wherein the message is transmitted based on that the number of the measurement results is equal to or greater than the count threshold.

Hereinafter, a base station (BS) for reporting stored measurement results, according to some embodiments of the present disclosure, will be described.

The BS may include a transceiver, a memory, and a processor operatively coupled to the transceiver and the memory.

The processor may be configured to perform operations. The operations comprise: transmitting, to a wireless device, a report configuration including information related to a count threshold, wherein the wireless device performs measurements for a signal block and/or a reference signal, wherein the wireless device counts a number of measurement results for the signal block and/or the reference signal; and receiving, from the wireless device, a message including information informing that the number of the measurement results are available, wherein the message is transmitted based on that the number of the measurement results is equal to or greater than the count threshold.

The present disclosure can have various advantageous effects.

For example, with respect to amount to stored measurement results in UE side, it can avoid UE's memory issue while the UE can send measurement result in time. `

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

Claims

A method, comprising:

receiving, by a wireless device, a report configuration including information related to a count threshold;

performing, by the wireless device, measurements for a signal block and/or a reference signal;

counting, by the wireless device, a number of measurement results for the signal block and/or the reference signal; and

transmitting, by the wireless device, a message including information informing that the number of the measurement results are available, based on that the number of the measurement results is equal to or greater than the count threshold.
The method of claim 1, wherein the method further comprising:

entering, by the wireless device, into a radio resource control (RRC) connected state.
The method of claim 2,

wherein the measurements for the signal block and/or the reference signal are performed while in the RRC connected state.
The method of claim 2,

wherein the message including information informing that the number of the measurement results are available is transmitted while in the RRC connected state.
The method of claim 1,

wherein the report configuration includes information related to at least one reporting condition for measurement reporting.
The method of claim 1, wherein the method further comprising:

determining, by the wireless device, whether at least one reporting condition for measurement reporting is satisfied; and

incrementing, by the wireless device, a reporting condition counter upon determining that the at least one reporting condition for measurement reporting is satisfied.
The method of claim 6, wherein the method further comprising:

transmitting, by the wireless device, a message including information informing that the measurement results are available, based on that the reporting condition counter is equal to or greater than the count threshold.
The method of claim 1, wherein the method further comprising:

performing, by the wireless device, measurements for a first resource set and a second resource set.
The method of claim 8, wherein the method further comprising:

counting, by the wireless device, a first number of measurement results for the first resource set; and

counting, by the wireless device, a second number of measurement results for the second resource set.
The method of claim 9, wherein the method further comprising:

transmitting, by the wireless device, a message including information informing that the first number of the measurement results are available, based on that the first number of the measurement results for the first resource set is equal to or greater than the count threshold.
The method of claim 9, wherein the method further comprising:

transmitting, by the wireless device, a message including information informing that sum of the first number and the second number of the measurement results are available, based on that the sum of the first number and the second number is equal to or greater than the count threshold.
The method of claim 8, wherein the method further comprising:

counting, by the wireless device, a number of measurement windows for the first resource set and/or the second resource set.
The method of claim 12, wherein the method further comprising:

transmitting, by the wireless device, a message including information informing that the number of measurement windows for the first resource set and/or the second resource set are available, based on that the number of measurement windows is equal to or greater than the count threshold.
The method of claim 1,

wherein the wireless device is in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.
A wireless device, comprising:

a transceiver;

a memory; and

at least one processor operatively coupled to the transceiver and the memory, and adapted to perform operations, the operations comprising:

receiving a report configuration including information related to a count threshold;

performing measurements for a signal block and/or a reference signal;

counting a number of measurement results for the signal block and/or the reference signal; and

transmitting a message including information informing that the number of the measurement results are available, based on that the number of the measurement results is equal to or greater than the count threshold.
The wireless device of claim 15, wherein the operations further comprising:

entering into a radio resource control (RRC) connected state.
The wireless device of claim 16,

wherein the measurements for the signal block and/or the reference signal are performed while in the RRC connected state.
The wireless device of claim 16,

wherein the message including information informing that the number of the measurement results are available is transmitted while in the RRC connected state.
The wireless device of claim 15,

wherein the report configuration includes information related to at least one reporting condition for measurement reporting.
The wireless device of claim 15, wherein the operations further comprising:

determining whether at least one reporting condition for measurement reporting is satisfied; and

incrementing a reporting condition counter upon determining that the at least one reporting condition for measurement reporting is satisfied.
The wireless device of claim 20, wherein the operations further comprising:

transmitting a message including information informing that the measurement results are available, based on that the reporting condition counter is equal to or greater than the count threshold.
The wireless device of claim 15, wherein the operations further comprising:

performing, by the wireless device, measurements for a first resource set and a second resource set.
The wireless device of claim 22, wherein the operations further comprising:

counting a first number of measurement results for the first resource set; and

counting a second number of measurement results for the second resource set.
The wireless device of claim 23, wherein the operations further comprising:

transmitting a message including information informing that the first number of the measurement results are available, based on that the first number of the measurement results for the first resource set is equal to or greater than the count threshold.
The wireless device of claim 23, wherein the operations further comprising:

transmitting a message including information informing that sum of the first number and the second number of the measurement results are available, based on that the sum of the first number and the second number is equal to or greater than the count threshold.
The wireless device of claim 22, wherein the operations further comprising:

counting a number of measurement windows for the first resource set and/or the second resource set.
The wireless device of claim 26, wherein the operations further comprising:

transmitting a message including information informing that the number of measurement windows for the first resource set and/or the second resource set are available, based on that the number of measurement windows is equal to or greater than the count threshold.
The wireless device of claim 15,

wherein the wireless device is in communication with at least one of a user equipment, a network, or an autonomous vehicle other than the wireless device.
A processor for a wireless device in a wireless communication system, wherein the processor is configured to control the wireless device to perform operations comprising:

receiving a report configuration including information related to a count threshold;

performing measurements for a signal block and/or a reference signal;

counting a number of measurement results for the signal block and/or the reference signal; and

transmitting a message including information informing that the number of the measurement results are available, based on that the number of the measurement results is equal to or greater than the count threshold.
A non-transitory computer-readable medium having stored thereon a plurality of instructions, which, when executed by a processor of a wireless device, cause the wireless device to perform operations, the operations comprises,

receiving a report configuration including information related to a count threshold;

performing measurements for a signal block and/or a reference signal;

counting a number of measurement results for the signal block and/or the reference signal; and

transmitting a message including information informing that the number of the measurement results are available, based on that the number of the measurement results is equal to or greater than the count threshold.
A method, comprising,

transmitting, by a base station to a wireless device, a report configuration including information related to a count threshold,

wherein the wireless device performs measurements for a signal block and/or a reference signal,

wherein the wireless device counts a number of measurement results for the signal block and/or the reference signal; and

receiving, by the base station from the wireless device, a message including information informing that the number of the measurement results are available,

wherein the message is transmitted based on that the number of the measurement results is equal to or greater than the count threshold.
A base station, comprising:

a transceiver;

a memory; and

a processor operatively coupled to the transceiver and the memory, and adapted to perform operations, the operations comprising:

transmitting, to a wireless device, a report configuration including information related to a count threshold,

wherein the wireless device performs measurements for a signal block and/or a reference signal,

wherein the wireless device counts a number of measurement results for the signal block and/or the reference signal; and

receiving, from the wireless device, a message including information informing that the number of the measurement results are available,

wherein the message is transmitted based on that the number of the measurement results is equal to or greater than the count threshold.