WO2026005259A1

WO2026005259A1 - Method and apparatus for lcm instruction in disaggregated architecture

Info

Publication number: WO2026005259A1
Application number: PCT/KR2025/005878
Authority: WO
Inventors: Daewook BYUN; Myoungsoo Kim; Seokjung KIM
Original assignee: LG Electronics Inc
Current assignee: LG Electronics Inc
Priority date: 2024-06-28
Filing date: 2025-04-30
Publication date: 2026-01-02
Anticipated expiration: 2026-12-28

Abstract

A method and apparatus for LCM instruction in disaggregated architecture is provided. The first DU of the first RAN node receives, from a first CU of the RAN node, a first message including an applicability indication informing whether at least one AI/ML model and/or AI/ML functionality of a wireless device is applicable or not. The first DU transmits, to the wireless device, a MAC CE and/or a DCI including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality, based on the applicability indication.

Description

METHOD AND APPARATUS FOR LCM INSTRUCTION IN DISAGGREGATED ARCHITECTURE

The present disclosure relates to a method and apparatus for LCM instruction in disaggregated architecture.

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.

In NR, studies for Artificial Intelligence (AI)/Machine Learning (ML) for NR Air Interface are in progress.

For example, study for signalling and protocol aspects of Life Cycle Management (LCM) enabling functionality and model (if justified) selection, activation, deactivation, switching, fallback is in progress.

For example, study for Signalling mechanism of applicable functionalities/models is in progress.

For example, information related to applicability of AI/ML functionality and/or ML models of UE can be provided by the UE to the base station.

However, based on the provided information, there is no plan for how the base station, which is configured with CU-DU split, should perform LCM instructions (activation/deactivation of AI/ML functionality/model). Therefore, a specific plan for this may be required.

Therefore, studies for support of LCM instruction in disaggregated architecture are required.

In an aspect, a method is provided. The method comprises: receiving, by a first Distributed Unit (DU) of a first Radio Access Network (RAN) node from a first Central Unit (CU) of the RAN node, a first message including an applicability indication informing whether at least one Artificial Intelligence (AI)/Machine Learning (ML) model and/or AI/ML functionality of a wireless device is applicable or not; and transmitting, by the first DU to the wireless device, a Medium Access Control (MAC) Control Element (CE) and/or a Downlink Control Indicator (DCI) including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality, based on the applicability indication.

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, the wireless device could efficiently perform the AIML based dynamic coverage change.

The base station, which is configured with CU-DU split, could determine (de)activation of AI/ML functionality/model, based on the information related to AI/ML functionality and applicability of AI/ML model provided by the UE. The base station could provide the determined information to the UE.

Therefore, even when the UE is moving, the UE can receive better quality service.

In other words, according to some embodiments of the present disclosure, since a gNB-DU provides LCM instruction to a UE by using a MAC CE or a DCI, instead of gNB-CU using an RRC message, the base station can manage resources efficiently. In addition, the base station can provide better quality of service to the UE during handover.

According to some embodiments of the present disclosure, the wireless network system could provide efficient solutions for the AIML based dynamic coverage change.

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 an example of UE to which implementations of the present disclosure is applied.

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

FIG. 7 shows an example of the overall architecture of an NG-RAN to which technical features of the present disclosure can be applied.

FIG. 8 shows an interface protocol structure for F1-C to which technical features of the present disclosure can be applied.

FIG. 9 shows an example of a successful operation for Handover Preparation.

FIG. 10 shows an example of a successful operation for UE Context Setup Request procedure.

FIG. 11 shows an example of a successful operation for UE Context Modification procedure.

FIG. 12 shows an example of a method for LCM instruction in disaggregated architecture, according to some embodiments of the present disclosure.

FIG. 13 shows a flow chart for support of LCM instruction in CU-DU split.

FIG. 14 shows a flow chart for support of LCM instruction in inter-gNB-DU mobility.

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. Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and/or 5G NR (new radio).

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 (for example, 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, for example, 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.

AI refers to the field of studying artificial intelligence or the methodology that can create it, and machine learning refers to the field of defining various problems addressed in the field of AI and the field of methodology to solve them. Machine learning is also defined as an algorithm that increases the performance of a task through steady experience on a task.

Robot means a machine that automatically processes or operates a given task by its own ability. In particular, robots with the ability to recognize the environment and make self-determination to perform actions can be called intelligent robots. Robots can be classified as industrial, medical, home, military, etc., depending on the purpose or area of use. The robot can perform a variety of physical operations, such as moving the robot joints with actuators or motors. The movable robot also includes wheels, brakes, propellers, etc., on the drive, allowing it to drive on the ground or fly in the air.

Autonomous driving means a technology that drives on its own, and autonomous vehicles mean vehicles that drive without user's control or with minimal user's control. For example, autonomous driving may include maintaining lanes in motion, automatically adjusting speed such as adaptive cruise control, automatic driving along a set route, and automatically setting a route when a destination is set. The vehicle covers vehicles equipped with internal combustion engines, hybrid vehicles equipped with internal combustion engines and electric motors, and electric vehicles equipped with electric motors, and may include trains, motorcycles, etc., as well as cars. Autonomous vehicles can be seen as robots with autonomous driving functions.

Extended reality is collectively referred to as VR, AR, and MR. VR technology provides objects and backgrounds of real world only through computer graphic (CG) images. AR technology provides a virtual CG image on top of a real object image. MR technology is a CG technology that combines and combines virtual objects into the real world. MR technology is similar to AR technology in that they show real and virtual objects together. However, there is a difference in that in AR technology, virtual objects are used as complementary forms to real objects, while in MR technology, virtual objects and real objects are used as equal personalities.

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

The NR frequency band may be defined as two types of frequency range, for example, 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 1 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean "sub 6 GHz range", FR2 may mean "above 6 GHz range," and may be referred to as millimeter wave (mmW).

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 2 below. For example, 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

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 at least one transceiver, such as a transceiver 106, at least one processing chip, such as a processing chip 101, and/or one or more antennas 108.

The processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. It is exemplarily shown in FIG. 2 that the memory 104 is included in the processing chip 101. Additional and/or alternatively, the memory 104 may be placed outside of the processing chip 101.

The processor 102 may control the memory 104 and/or the transceiver 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 102 may process information within the memory 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver 106. The processor 102 may receive radio signals including second information/signals through the transceiver 106 and then store information obtained by processing the second information/signals in the memory 104.

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 to perform one or more layers of the radio interface protocol.

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

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

The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. It is exemplarily shown in FIG. 2 that the memory 204 is included in the processing chip 201. Additional and/or alternatively, the memory 204 may be placed outside of the processing chip 201.

The processor 202 may control the memory 204 and/or the transceiver 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 202 may process information within the memory 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver 206. The processor 202 may receive radio signals including fourth information/signals through the transceiver 106 and then store information obtained by processing the fourth information/signals in the memory 204.

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 to perform one or more layers of the radio interface protocol.

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

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

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 unit 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 unit 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, a UE 100 may correspond to the first wireless device 100 of FIG. 2 and/or the wireless device 100 or 200 of FIG. 3.

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

Referring to FIG. 7, a gNB may include a gNB-CU (hereinafter, gNB-CU may be simply referred to as CU) and at least one gNB-DU (hereinafter, gNB-DU may be simply referred to as DU).

The gNB-CU is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or an RRC and PDCP protocols of the en-gNB. The gNB-CU controls the operation of the at least one gNB-DU.

The gNB-DU is a logical node hosting RLC, MAC, and physical layers of the gNB or the en-gNB. The operation of the gNB-DU is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU.

The gNB-CU and gNB-DU are connected via an F1 interface. The gNB-CU terminates the F1 interface connected to the gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU. One gNB-DU is connected to only one gNB-CU. However, the gNB-DU may be connected to multiple gNB-CUs by appropriate implementation. The F1 interface is a logical interface. For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For E-UTRAN-NR dual connectivity (EN-DC), the S1-U and X2-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

Functions of the F1 interface includes F1 control (F1-C) functions as follows.

(1) F1 interface management function

The error indication function is used by the gNB-DU or gNB-CU to indicate to the gNB-CU or gNB-DU that an error has occurred.

The reset function is used to initialize the peer entity after node setup and after a failure event occurred. This procedure can be used by both the gNB-DU and the gNB-CU.

The F1 setup function allows to exchange application level data needed for the gNB-DU and gNB-CU to interoperate correctly on the F1 interface. The F1 setup is initiated by the gNB-DU.

The gNB-CU configuration update and gNB-DU configuration update functions allow to update application level configuration data needed between gNB-CU and gNB-DU to interoperate correctly over the F1 interface, and may activate or deactivate cells.

The F1 setup and gNB-DU configuration update functions allow to inform the single network slice selection assistance information (S-NSSAI) supported by the gNB-DU.

The F1 resource coordination function is used to transfer information about frequency resource sharing between gNB-CU and gNB-DU.

(2) System Information management function

Scheduling of system broadcast information is carried out in the gNB-DU. The gNB-DU is responsible for transmitting the system information according to the scheduling parameters available.

The gNB-DU is responsible for the encoding of NR master information block (MIB). In case broadcast of system information block type-1 (SIB1) and other SI messages is needed, the gNB-DU is responsible for the encoding of SIB1 and the gNB-CU is responsible for the encoding of other SI messages.

(3) F1 UE context management function

The F1 UE context management function supports the establishment and modification of the necessary overall UE context.

The establishment of the F1 UE context is initiated by the gNB-CU and accepted or rejected by the gNB-DU based on admission control criteria (e.g., resource not available).

The modification of the F1 UE context can be initiated by either gNB-CU or gNB-DU. The receiving node can accept or reject the modification. The F1 UE context management function also supports the release of the context previously established in the gNB-DU. The release of the context is triggered by the gNB-CU either directly or following a request received from the gNB-DU. The gNB-CU request the gNB-DU to release the UE Context when the UE enters RRC_IDLE or RRC_INACTIVE.

This function can be also used to manage DRBs and SRBs, for example, establishing, modifying and releasing DRB and SRB resources. The establishment and modification of DRB resources are triggered by the gNB-CU and accepted/rejected by the gNB-DU based on resource reservation information and QoS information to be provided to the gNB-DU. For each DRB to be setup or modified, the S-NSSAI may be provided by gNB-CU to the gNB-DU in the UE context setup procedure and the UE context modification procedure.

The mapping between QoS flows and radio bearers is performed by gNB-CU and the granularity of bearer related management over F1 is radio bearer level. For NG-RAN, the gNB-CU provides an aggregated DRB QoS profile and QoS flow profile to the gNB-DU, and the gNB-DU either accepts the request or rejects it with appropriate cause value. To support packet duplication for intra-gNB-DU carrier aggregation (CA), one data radio bearer should be configured with two GPRS tunneling protocol (GTP)-U tunnels between gNB-CU and a gNB-DU.

With this function, gNB-CU requests the gNB-DU to setup or change of the special cell (SpCell) for the UE, and the gNB-DU either accepts or rejects the request with appropriate cause value.

With this function, the gNB-CU requests the setup of the secondary cell(s) (SCell(s)) at the gNB-DU side, and the gNB-DU accepts all, some or none of the SCell(s) and replies to the gNB-CU. The gNB-CU requests the removal of the SCell(s) for the UE.

(4) RRC message transfer function

This function allows to transfer RRC messages between gNB-CU and gNB-DU. RRC messages are transferred over F1-C. The gNB-CU is responsible for the encoding of the dedicated RRC message with assistance information provided by gNB-DU.

(5) Paging function

The gNB-DU is responsible for transmitting the paging information according to the scheduling parameters provided.

The gNB-CU provides paging information to enable the gNB-DU to calculate the exact paging occasion (PO) and paging frame (PF). The gNB-CU determines the paging assignment (PA). The gNB-DU consolidates all the paging records for a particular PO, PF and PA, and encodes the final RRC message and broadcasts the paging message on the respective PO, PF in the PA.

(6) Warning messages information transfer function

This function allows to cooperate with the warning message transmission procedures over NG interface. The gNB-CU is responsible for encoding the warning related SI message and sending it together with other warning related information for the gNB-DU to broadcast over the radio interface.

A transport network layer (TNL) is based on Internet protocol (IP) transport, comprising a stream control transmission protocol (SCTP) layer on top of the IP layer. An application layer signaling protocol is referred to as an F1 application protocol (E1AP).

Hereinafter, technical features related to handover are described. Sections of 3GPP TS 38.423 v18.1.0 may be referred.

Handover Preparation

This procedure is used to establish necessary resources in an NG-RAN node for an incoming handover. If the procedure concerns a conditional handover, parallel transactions are allowed. Possible parallel requests are identified by the target cell ID when the source UE AP IDs are the same.

The procedure uses UE-associated signalling.

FIG. 9 shows an example of a successful operation for Handover Preparation.

The source NG-RAN node initiates the procedure by sending the HANDOVER REQUEST message to the target NG-RAN node. When the source NG-RAN node sends the HANDOVER REQUEST message, it shall start the timer TXn_RELOCprep _.

If the Conditional Handover Information Request IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall consider that the request concerns a conditional handover and shall include the Conditional Handover Information Acknowledge IE in the HANDOVER REQUEST ACKNOWLEDGE message.

If the Target NG -RAN node UE XnAP ID IE is contained in the Conditional Handover Information Request IE included in the HANDOVER REQUEST message, then the target NG-RAN node shall remove the existing prepared conditional HO identified by the Target NG -RAN node UE XnAP ID IE and the Target Cell Global ID IE. It is up to the implementation of the target NG-RAN node when to remove the HO information.

Upon reception of the HANDOVER REQUEST ACKNOWLEDGE message, the source NG-RAN node shall stop the timer TXn_RELOCprep and terminate the Handover Preparation procedure. If the procedure was initiated for an immediate handover, the source NG-RAN node shall start the timer TXn_RELOCoverall. The source NG-RAN node is then defined to have a Prepared Handover for that Xn UE-associated signalling.

For each E- RAB ID IE included in the QoS Flows To Be Setup List IE in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, store the content of the IE in the UE context and use it for subsequent inter-system handover.

If the Masked IMEISV IE is contained in the HANDOVER REQUEST message the target NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling.

At reception of the HANDOVER REQUEST message the target NG-RAN node shall prepare the configuration of the AS security relation between the UE and the target NG-RAN node by using the information in the UE Security Capabilities IE and the AS Security Information IE in the UE Context Information IE.

Upon reception of the PDU Session Resources To Be Setup List IE, contained in the HANDOVER REQUEST message, the target NG-RAN node shall behave for the PDU Session Resource Setup procedure. The target NG-RAN node shall report in the HANDOVER REQUEST ACKNOWLEDGE message the successful establishment of the result for all the requested PDU session resources. When the target NG-RAN node reports the unsuccessful establishment of a PDU session resource, the cause value should be precise enough to enable the source NG-RAN node to know the reason for the unsuccessful establishment.

For each PDU session if the PDU Session Aggregate Maximum Bit Rate IE is included in the PDU Session Resources To Be Setup List IE contained in the HANDOVER REQUEST message, the target NG-RAN node shall store the received PDU Session Aggregate Maximum Bit Rate in the UE context and use it when enforcing traffic policing for Non-GBR QoS flows for the concerned UE.

For each QoS flow for which the source NG-RAN node proposes to perform forwarding of downlink data, the source NG-RAN node shall include the DL Forwarding IE set to "DL forwarding proposed" within the Data Forwarding and Offloading Info from source NG -RAN node IE in the PDU Session Resources To Be Setup List IE in the HANDOVER REQUEST message. The source NG-RAN node shall include the DL Forwarding IE set to "DL forwarding proposed" for all the QoS flows mapped to a DRB, if it requests a DAPS handover for that DRB.

Interaction with SN Status Transfer procedure:

If the UE Context Kept Indicator IE set to "True" and the DRBs transferred to MN IE are included in the HANDOVER REQUEST ACKNOWLEDGE message, the source NG-RAN node shall, if supported, include the uplink/downlink PDCP SN and HFN status received from the S-NG-RAN node in the SN Status Transfer procedure towards the target NG-RAN node.

Interaction with the Data Collection Reporting and the Data Collection Reporting Initiation procedures:

If the Data Collection ID IE is contained in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, report to the source NG-RAN node after successful handover, via the Data Collection Reporting procedure, the requested information configured via the previous Data Collection Reporting Initiation procedure corresponding to the NG -RAN node1 Measurement ID IE, allocated by the source NG-RAN node, and the NG -RAN node2 Measurement ID IE, allocated by the target NG-RAN node.

Hereinafter, technical features related to UE Context are described. Sections of 3GPP TS 38. 473 v18.1.0 may be referred.

UE Context Setup

The purpose of the UE Context Setup procedure is to establish the UE Context including, among others, SRB, DRB, BH RLC channel, Uu Relay RLC channel, PC5 Relay RLC channel, and SL DRB configuration. The procedure uses UE-associated signalling.

The gNB-CU initiates the procedure by sending UE CONTEXT SETUP REQUEST message to the gNB-DU. If the gNB-DU succeeds to establish the UE context, it replies to the gNB-CU with UE CONTEXT SETUP RESPONSE. If no UE-associated logical F1-connection exists, the UE-associated logical F1-connection shall be established as part of the procedure. Except for RACH based SDT and UE configured with BWP specific ServingCellMO, the gNB-CU shall perform RRC Reconfiguration or RRC connection resume to send UE to the RRC_CONNECTED state, and in this case, the CellGroupConfig IE shall transparently be signaled to the UE. In the cases of RACH based SDT procedure and UE configured with BWP specific ServingCellMO, the CellGroupConfig IE shall be ignored by the gNB-CU.

If the UE - CapabilityRAT - ContainerList IE is included in the UE CONTEXT SETUP REQUEST, the gNB-DU shall take this information into account for UE specific configurations.

If the servingCellMO IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SpCell accordingly.

If the servingCellMO List IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, select servingCellMO after determining the list of BWPs for the UE and include the list of servingCellMOs that have been encoded in CellGroupConfig IE as ServingCellMO -encoded-in-CGC List IE in the UE CONTEXT SETUP RESPONSE message.

If the Configured BWP List IE is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, take it into account when requesting the gNB-DU for generating preconfigured measurement GAP for the indicated BWPs.

If the SpCell UL Configured IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure UL for the indicated SpCell accordingly.

If the SCell To Be Setup List IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall consider it as a list of candidate SCells to be set up. If the SCell UL Configured IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure UL for the indicated SCell accordingly. If the servingCellMO IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SCell accordingly.

If the DRX Cycle IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall use the provided value from the gNB-CU.

If the UL Configuration IE in DRB to Be Setup Item IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall take it into account for UL scheduling.

Interaction with UE Inactivity Notification procedure

If the SDT Volume Threshold IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use the information during an SDT transaction to inform the gNB-CU via the UE INACTIVITY NOTIFICATION message.

UE Context Modification ( gNB -CU initiated)

The purpose of the UE Context Modification procedure is to modify the established UE Context, e.g., establishing, modifying and releasing radio resources or sidelink resources. This procedure is also used to command the gNB-DU to stop data transmission for the UE for mobility. The procedure uses UE-associated signalling.

The UE CONTEXT MODIFICATION REQUEST message is initiated by the gNB-CU.

Upon reception of the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall perform the modifications, and if successful reports the update in the UE CONTEXT MODIFICATION RESPONSE message.

If the SpCell ID IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall replace any previously received value and regard it as a reconfiguration with sync as defined in TS 38.331 [8]. If the ServCellIndex IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall take this into account for the indicated SpCell. If the SpCell UL Configured IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure UL for the indicated SpCell accordingly. If the servingCellMO IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SpCell accordingly. If the servingCellMO List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, configure servingCellMO after determining the list of BWPs for the UE and include the list of servingCellMOs that have been encoded in CellGroupConfig IE as ServingCellMO-encoded-in-CGC List IE in the UE CONTEXT MODIFICATION RESPONSE message.

If the Configured BWP List IE is included in the UE CONTEXT MODIFICATION RESPONSE message the gNB-CU shall, if supported, take it into account when requesting the gNB-DU for generating preconfigured measurement GAP for the indicated BWPs.

If the Preconfigured Measurement GAP Request IE is present in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATON REQUEST message, the gNB-DU shall, if supported, consider that the content of the previous CellGroupConfig IE was not sent to the UE and generate the pre-configured measurement GAP for the indicated BWPs in the MeasConfig IE. If the gNB-DU successfully generates pre-configured measurement GAP for the indicated BWPs, the gNB-DU shall update the CellGroupConfig IE with the content of the previous CellGroupConfig IE and the preconfigured measurement GAP configuration in the UE CONTEXT MODIFICATION RESPONSE message.

If the SCell To Be Setup List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider it as a list of candidate SCells to be set up. If the SCell To Be Setup List IE is included in the UE CONTEXT MODIFICATION REQUEST message and the indicated SCell(s) are already setup, the gNB-DU shall replace any previously received value. If the SCell UL Configured IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure UL for the indicated SCell accordingly. If the servingCellMO IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SCell accordingly.

If the SCell To Be Removed List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider it as a list of SCells to be removed.

If the DRX Cycle IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall use the provided value from the gNB-CU. If the DRX configuration indicator IE is contained in the UE CONTEXT MODIFICATION REQUEST message and set to "release", the gNB-DU shall release DRX configuration.

If the SL DRX Cycle list IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use the provided value from the gNB-CU for the indicated RX UE of this UE. If the SL DRX configuration indicator IE is contained in the UE CONTEXT MODIFICATION REQUEST message and set to "release", the gNB-DU shall, if supported, release SL DRX configuration for the indicated RX UE of this UE.

Interaction with UE Inactivity Notification procedure

If the SDT Volume Threshold IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use the information during an SDT transaction to inform the gNB-CU via the UE INACTIVITY NOTIFICATION message.

Interaction with UE Context Setup or UE Context Modification ( gNB -CU initiated) procedures

If the UE CONTEXT MODIFICATION REQUEST message is sent for a UE context set up for S-CPAC and contains the Transmission Action Indicator IE set to "stop", the gNB-DU shall, if supported, reset the UE context for the included SpCell ID IE, prepare for subsequent CPAC. The gNB-DU shall include the SpCell ID IE as the Requested Target Cell ID IE in the UE CONTEXT MODIFICATION RESPONSE message.

Meanwhile, in NR, studies for Artificial Intelligence (AI)/Machine Learning (ML) for NR Air Interface are in progress.

For example, provide specification support for the following aspects:

> AI/ML general framework for one-sided AI/ML models within the realm of what has been studied in the FS_NR_AIML_Air project [RAN2]:

>> Signalling and protocol aspects of Life Cycle Management (LCM) enabling functionality and model (if justified) selection, activation, deactivation, switching, fallback

>>> Identification related signalling is part of the above objective

>> Necessary signalling/mechanism(s) for LCM to facilitate model training, inference, performance monitoring, data collection (except for the purpose of CN/OAM/OTT collection of UE-sided model training data) for both UE-sided and NW-sided models

>> Signalling mechanism of applicable functionalities/models

> Beam management - DL Tx beam prediction for both UE-sided model and NW-sided model, encompassing [RAN1/RAN2]:

>> Spatial-domain DL Tx beam prediction for Set A of beams based on measurement results of Set B of beams ("BM-Case1")

>> Temporal DL Tx beam prediction for Set A of beams based on the historic measurement results of Set B of beams ("BM-Case2")

>> Specify necessary signalling/mechanism(s) to facilitate LCM operations specific to the Beam Management use cases, if any

>> Enabling method(s) to ensure consistency between training and inference regarding NW-side additional conditions (if identified) for inference at UE

- Strive for common framework design to support both BM-Case1 and BM-Case2

> Positioning accuracy enhancements, encompassing [RAN1/RAN2/RAN3]:

>> Direct AI/ML positioning:

>>> (1st priority) Case 1: UE-based positioning with UE-side model, direct AI/ML positioning

>>> (2nd priority) Case 2b: UE-assisted/LMF-based positioning with LMF-side model, direct AI/ML positioning

>>> (1st priority) Case 3b: NG-RAN node assisted positioning with LMF-side model, direct AI/ML positioning

>> AI/ML assisted positioning

>>> (2nd priority) Case 2a: UE-assisted/LMF-based positioning with UE-side model, AI/ML assisted positioning

>>> (1st priority) Case 3a: NG-RAN node assisted positioning with gNB-side model, AI/ML assisted positioning

>> Specify necessary measurements, signalling/mechanism(s) to facilitate LCM operations specific to the Positioning accuracy enhancements use cases, if any

>> Investigate and specify the necessary signalling of necessary measurement enhancements (if any)

>> Enabling method(s) to ensure consistency between training and inference regarding NW-side additional conditions (if identified) for inference at UE for relevant positioning sub use cases

> Core requirements for the above two use cases for AI/ML LCM procedures and UE features [RAN4]:

>> Specify necessary RAN4 core requirements for the above two use cases.

>> Specify necessary RAN4 core requirements for LCM procedures including performance monitoring.

Study objectives with corresponding checkpoints in RAN#105 (Sept '24):

> CSI feedback enhancement [RAN1]:

>> For CSI compression (two-sided model), further study ways to:

>>> Improve trade-off between performance and complexity/overhead

>>> e.g., considering extending the spatial/frequency compression to spatial/temporal/frequency compression, cell/site specific models, CSI compression plus prediction (compared to Rel-18 non-AI/ML based approach), etc.

>>> Alleviate/resolve issues related to inter-vendor training collaboration.

>> while addressing other aspects requiring further study/conclusion.

>> For CSI prediction (one-sided model), further study performance gain over Rel-18 non-AI/ML based approach and associated complexity, while addressing other aspects requiring further study/conclusion (e.g., cell/site specific model could be considered to improve performance gain).

> Necessity and details of model Identification concept and procedure in the context of LCM [RAN2/RAN1]

> CN/OAM/OTT collection of UE-sided model training data [RAN2/RAN1]:

>> For the FS_NR_AIML_Air study use cases, identify the corresponding contents of UE data collection

>> Analyse the UE data collection mechanisms identified during the FS_NR_AIML_Air study along with the implications and limitations of each of the methods

> Model transfer/delivery [RAN2/RAN1]:

>> Determine whether there is a need to consider standardised solutions for transferring/delivering AI/ML model(s) considering at least the solutions identified during the FS_NR_AIML_Air study

> Testability and interoperability [RAN4]:

>> Finalize the testing framework and procedure for one-sided models and further analyse the various testing options for two-sided models, in collaboration with RAN1, and including at least:

>>> Relation to legacy requirements

>>> Performance monitoring and LCM aspects considering use-case specifics

>>> Generalization aspects

>>> Static/non-static scenarios/conditions and propagation conditions for testing (e.g., CDL, field data, etc.)

>>> UE processing capability and limitations

>>> Post-deployment validation due to model change/drift

>> RAN5 aspects related to testability and interoperability to be addressed on a request basis

Hereinafter, a method for LCM instruction in disaggregated architecture, 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).

In particular, FIG. 12 shows an example of a method performed by a first Distributed Unit (CU) of a first Radio Access Network (RAN) node.

In step S1201, the first DU may receive, from a first Central Unit (CU) of the RAN node, a first message including an applicability indication informing whether at least one Artificial Intelligence (AI)/Machine Learning (ML) model and/or AI/ML functionality of a wireless device is applicable or not.

In step S1202, the first DU may transmit, to the wireless device, a Medium Access Control (MAC) Control Element (CE) and/or a Downlink Control Indicator (DCI) including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality, based on the applicability indication.

For example, the first DU may determine whether to activate or deactivate the at least one AI/ML model and/or AI/ML functionality of the wireless device based on the applicability indication. The activation command or the deactivation command for the at least one AI/ML model and/or AI/ML functionality may be determined by the first DU.

For example, activation or deactivation of the at least one AI/ML model and/or AI/ML functionality of the wireless device may be determined by the first CU. Information related to the activation or deactivation of the at least one AI/ML model and/or AI/ML functionality determined by the first CU may be included in the applicability indication.

In other words, the first CU may determine whether to activate or deactivate of the at least one AI/ML model and/or AI/ML functionality of the wireless device. The first CU may include the determination whether to activate or deactivate the at least one AI/ML model and/or AI/ML functionality of the wireless device in the applicability indication.

For example, a wireless device may include one or more AI/ML models and/or AI/ML functionalities. The MAC CE and/or the DCI may include multiple activation commands or deactivation commands for each AI/ML model and/or AI/ML functionality of the wireless device.

According to some embodiments of the present disclosure, the wireless device may transmit, to the first DU, a third message (for example, UE Assistance Information message) including applicability of the AI/ML model and/or the AI/ML functionality of the wireless device. The first DU may forward the applicability of the AI/ML model and/or the AI/ML functionality of the wireless device to the first CU via the first message. The first message may be a UE Context Modification Request message. The first DU may transmit, to the first CU, a UE Context Modification Response message.

According to some embodiments of the present disclosure, the first message may be a UE Context Setup Request message. The UE Context Setup Request message may include information for creating a context for the wireless device and configuring one or more data bearers. The second message may be a UE Context Setup Response message.

For example, the wireless device may change a serving CU from the source CU to the first CU. (For example, the source CU may belong to a source RAN node, which is different from the first RAN node.) The applicability indication may be transmitted from the source CU to the first CU (target CU) via a Handover Request message. In other words, the source CU may transmit the applicability indication for the wireless device to the first CU (target CU). The first CU may forward the applicability indication to the first DU (target DU).

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, technical features related to a method for support of LCM instruction in disaggregated architecture are described.

According to some embodiments of the present disclosure, in case the base station is configured with CU-DU split, in order to support LCM instruction for the UE, the gNB-CU can provide, to gNB-DU, the applicability of AI/ML functionality/model received from the UE.

After receiving this, the gNB-DU can send a (de)activation command to the UE using MAC or DCI. When the gNB-CU determines (de)activation based on the applicability of the AI/ML functionality/model received from the UE, the gNB-CU may transmit a (de)activation command to the UE through the gNB-DU.

FIG. 13 shows a flow chart for support of LCM instruction in CU-DU split.

In particular, FIG. 13 presents a method for supporting LCM instruction when the base station is configured with CU-DU split.

In step S1301, the UE performs the UE Initial Access procedure with the gNB-CU through the gNB-DU and enters the RRC_CONNECTED state.

In step S1302, the UE informs the gNB-CU whether the AI/ML functionality/model is applicable.

After the UE determines whether the AI/ML functionality/model is applicable, in order to inform the gNB-CU of the determined information, the UE sends a UEAssitanceInformation message including the corresponding information to the gNB-DU.

The UEAssistanceInformation message may include information for applicability of one or more AI/ML functionality/models.

For example, if the UE receives an RRCReconfiguration message, the UE may transmit an RRCReconfigurationComplete message including the information for applicability of one or more AI/ML functionality/models.

In step S1303, after receiving the UEAssitanceInformation message from the UE, the gNB-DU sends a UE RRC MESSAGE TRANSFER message including the received information to the gNB-CU.

In step S1304, after receiving the applicability of AI/ML functionality/model from gNB-DU, gNB-CU stores it. If gNB-CU receives changed information from UE later, gNB-CU can replace the stored information.

In order to inform the applicability of AI/ML functionality/model, the gNB-CU can send a UE CONTEXT MODIFICATION REQUEST message, a new F1AP message, or an existing F1AP message including Applicability Indication to gNB-DU.

For example, if the gNB-CU determines (de)activation, the determined (de)activation result may be included in the Applicability Indication for the corresponding AI/ML functionality/model. At this time, (de)activation commands for one or more AI/ML functionality/models may be included.

In step S1305, after receiving a message including Applicability Indication from the gNB-CU, the gNB-DU stores it. Based on the received information, the gNB-DU may transmit a (de)activation command to the UE using a MAC or a DCI. The MAC or DCI can include a (de)activation command for one or more AI/ML functionality/models.

If the gNB-DU subsequently receives changed information from the gNB-CU, the gNB-DU may replace the stored information.

If the received Applicability Indication includes the determined (de)activation result, the gNB-DU may store it. The gNB-DU may transmit the determined (de)activation result to the UE.

The gNB-DU sends a UE CONTEXT MODIFICATION RESPONSE message, a new F1AP message, or an existing F1AP message to the gNB-CU, in response.

According to some embodiments of the present disclosure, in the inter-gNB-DU mobility scenario, in order to continuously support the LCM instruction for the UE in the target gNB-DU, the gNB-CU may provide, to the target gNB-DU, the stored information for the applicability of the AI/ML functionality/model for the corresponding UE. After receiving the information, the target gNB-DU may transmit a (de)activation command to the UE using a MAC or a DCI.

If the gNB-CU determines (de)activation based on the applicability of the AI/ML functionality/model received from the UE, the gNB-CU may transmit a (de)activation command to the UE through the target gNB-DU.

If the gNB-CU changes due to the movement of the UE, information for the applicability of the AI/ML functionality/model for the UE stored in the source gNB-CU can be provided to the target gNB-CU. After receiving the information, the target gNB-CU provides the information to the target gNB-DU managed by the target gNB-CU. The target gNB-DU may transmit a (de)activation command to the UE by a MAC or a DCI.

If the target gNB-CU determines (de)activation based on the applicability of the AI/ML functionality/model received from the source gNB-CU, the target gNB-CU may transmit a (de)activation command to the UE through the target gNB-DU.

In particular, FIG. 14 presents a method for supporting continuous LCM instruction when the serving gNB-DU changes due to UE mobility.

In step S1401, the UE sends a MeasurementReport message to the source gNB-DU.

In step S1402, the source gNB-DU sends a UL RRC MESSAGE TRANSFER message including the MeasurementReport message to the gNB-CU.

In step S1403, in order to create a context for the UE and configure one or more data bearers, the gNB-CU sends a UE CONTEXT SETUP REQUEST message to the target gNB-DU.

This message may include information for an Applicability Indication to indicate whether the AI/ML functionality/model is applicable for the corresponding UE, which is stored in the gNB-CU. A new F1AP message or an existing F1AP message including the corresponding indication may be transmitted to the target gNB-DU.

For example, when the gNB-CU determines (de)activation, the Applicability Indication for the corresponding AI/ML functionality/model may include the result of the (de)activation determination. At this time, one or more (de)activation commands for the AI/ML functionality/model may be included.

For example, if the gNB-CU changes due to the movement of the UE, before performing step S1403, the source gNB-CU may send an XnAP HANDOVER REQUEST message to the target gNB-CU.

In order for the target gNB-CU or the target gNB-DU managed by the target gNB-CU to transmit a (de)activation command to the UE, this message may include an Applicability Indication to indicate whether the AI/ML functionality/model is applicable for the corresponding UE, which is stored in the source gNB-CU.

After receiving the indication, the target gNB-CU may perform step S1403 to the target gNB-DU.

In step S1404, after receiving a message including the Applicability Indication from gNB-CU, target gNB-DU stores it. Based on the received information, target gNB-DU may transmit a (de)activation command to UE using a MAC or a DCI.

At this time, a (de)activation command for one or more AI/ML functionality/model can be included.

If the target gNB-DU receives changed information from the gNB-CU later, the target gNB-DU could replace the stored information.

If the received Applicability Indication includes the determined (de)activation result, the target gNB-DU could store it and provide the received information to the UE.

In response, the target gNB-DU sends, to the gNB-CU, a UE CONTEXT SETUP RESPONSE message, a new F1AP message, or an existing F1AP message.

In step S1405, the gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message including the generated RRCReconfiguration message to the source gNB-DU, in order to stop data transmission to the UE.

In step S1406, the source gNB-DU forwards the received RRCReocnfiguration message to the UE.

In step S1407, the source gNB-DU sends a UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU in response.

In step S1408, the Random Access procedure is performed in the target gNB-DU.

In step S1409, the UE sends an RRCReconfigurationComplete message to the target gNB-DU in response.

In step S1410, the target gNB-DU sends a UL RRC MESSAGE TRANSFER message including the received RRCReconfigurationComplete message to the gNB-CU.

In step S1411, the gNB-CU sends a UE CONTEXT RELEASE COMMAND message to the source gNB-DU.

In step S1412, the source gNB-DU clears the UE context and sends a UE CONTEXT RELEASE COMPLETE message to the gNB-CU in response.

Hereinafter, some embodiments for supporting LCM instructions based on information related to applicability of AI/ML functionality and an AI/ML model of a UE are described.

For example, the gNB-CU may provide an Applicability Indication to the (target) gNB-DU so that the (target) gNB-DU transmit a (de)activation command for the AI/ML functionality/model.

For example, in order to inform the (de)activation decision for AI/ML functionality/model, the gNB-CU may provide an Applicability Indication to the (target) gNB-DU.

For example, the source gNB-CU may provide an Applicability Indication to the target gNB-CU so that the target gNB-DU managed by the target gNB-CU can transmit a (de)activation command for AI/ML functionality/model.

Additionally, the Applicability Indication may include information related to the applicability of the AI/ML functionality/model received from the UE.

Additionally, it may include a (de)activation command for one or more AI/ML functionality/models.

Some of the detailed steps shown in the examples of FIG. 12, FIG. 13, and FIG. 14 may not be essential steps and may be omitted. In addition to the steps shown in FIG. 12, FIG. 13, and FIG. 14, 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, a RAN node for support of LCM instruction in disaggregated architecture, according to some embodiments of the present disclosure, will be described.

The RAN node may be the gNB in FIG. 7. The RAN node may include a Central Unit (CU) and at least one Distributed Unit (DU). For example, a first gNB and a second gNB may be the gNB in FIG. 7.

A first Distributed Unit (DU) of a first Radio Access Network (RAN) node may include at least one transceiver, at least one memory, and at least one processor operatively coupled to the at least one transceiver and the at least one memory.

The at least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations comprising: receiving, from a first Central Unit (CU) of the RAN node, a first message including an applicability indication informing whether at least one Artificial Intelligence (AI)/Machine Learning (ML) model and/or AI/ML functionality of a wireless device is applicable or not; and transmitting, to the wireless device, a Medium Access Control (MAC) Control Element (CE) and/or a Downlink Control Indicator (DCI) including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality, based on the applicability indication.

For example, the operations further comprises: determining whether to activate or deactivate the at least one AI/ML model and/or AI/ML functionality of the wireless device based on the applicability indication.

For example, activation or deactivation of the at least one AI/ML model and/or AI/ML functionality of the wireless device is determined by the first CU.

For example, information related to the activation or deactivation of the at least one AI/ML model and/or AI/ML functionality determined by the first CU is included in the applicability indication.

For example, the first message is a UE Context Modification Request message.

For example, the operations further comprises: transmitting, to the first CU, a UE Context Modification Response message. The MAC CE and/or the DCI includes multiple activation commands or deactivation commands for each AI/ML model and/or AI/ML functionality of the wireless device.

For example, the first message is a UE Context Setup Request message. The UE Context Setup Request message includes information for creating a context for the wireless device and configuring one or more data bearers.

For example, the second message is a UE Context Setup Response message.

For example, the wireless device changes a serving CU from the source CU to the first CU, and the applicability indication is transmitted from the source CU to the first CU via a handover request message.

For example, the operations further comprises: receiving, from the wireless device, a third message including applicability of the AI/ML model and/or the AI/ML functionality of the wireless device. For example, the operations further comprises: forwarding, to the first CU, the applicability of the AI/ML model and/or the AI/ML functionality of the wireless device via the first message.

For example, 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.

Hereinafter, a processor for a first Distributed Unit (DU) of a first Radio Access Network (RAN) node for support of LCM instruction in disaggregated architecture, according to some embodiments of the present disclosure, will be described.

The processor may be adapted to control the first DU to perform operations comprising: receiving, from a first Central Unit (CU) of the RAN node, a first message including an applicability indication informing whether at least one Artificial Intelligence (AI)/Machine Learning (ML) model and/or AI/ML functionality of a wireless device is applicable or not; and transmitting, to the wireless device, a Medium Access Control (MAC) Control Element (CE) and/or a Downlink Control Indicator (DCI) including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality, based on the applicability indication.

For example, the first message is a UE Context Modification Request message.

For example, the second message is a UE Context Setup Response message.

Hereinafter, a non-transitory computer-readable medium has stored thereon a plurality of instructions for support of LCM instruction in disaggregated architecture, 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 another 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.

When executed by a processor of a first Distributed Unit (DU) of a first Radio Access Network (RAN) node, cause the first DU to perform operations, the operations comprising: receiving, from a first Central Unit (CU) of the RAN node, a first message including an applicability indication informing whether at least one Artificial Intelligence (AI)/Machine Learning (ML) model and/or AI/ML functionality of a wireless device is applicable or not; and transmitting, to the wireless device, a Medium Access Control (MAC) Control Element (CE) and/or a Downlink Control Indicator (DCI) including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality, based on the applicability indication.

For example, the first message is a UE Context Modification Request message.

For example, the second message is a UE Context Setup Response message.

Hereinafter, a method performed by a wireless device for support of LCM instruction in disaggregated architecture, according to some embodiments of the present disclosure, will be described.

The wireless device may transmit, to a first CU of a first RAN node, information related to applicability of the AI/ML model and/or the AI/ML functionality of the wireless device. The first CU may transmit, to a first DU of the first RAN node, a first message including an applicability indication informing the applicability of the AI/ML model and/or the AI/ML functionality of the wireless device. The wireless device may receive, from the first DU, a MAC CE and/or a DCI including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality.

Hereinafter, an apparatus for support of LCM instruction in disaggregated architecture, according to some embodiments of the present disclosure, will be described.

The wireless device may include a transceiver, a memory, and a processor operatively coupled to the transceiver and the memory. For example, the wireless device may be the first wireless device 100 or the second wireless device 200 of FIGS. 2 and 3, or the UE 100 of FIG. 4.

The processor may be configured to control the wireless device to transmit, to a first CU of a first RAN node, information related to applicability of the AI/ML model and/or the AI/ML functionality of the wireless device. The first CU may transmit, to a first DU of the first RAN node, a first message including an applicability indication informing the applicability of the AI/ML model and/or the AI/ML functionality of the wireless device. The processor may be configured to control the wireless device to receive, from the first DU, a MAC CE and/or a DCI including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality.

The present disclosure can have various advantageous effects.

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 first Distributed Unit (DU) of a first Radio Access Network (RAN) node from a first Central Unit (CU) of the RAN node, a first message including an applicability indication informing whether at least one Artificial Intelligence (AI)/Machine Learning (ML) model and/or AI/ML functionality of a wireless device is applicable or not; and

transmitting, by the first DU to the wireless device, a Medium Access Control (MAC) Control Element (CE) and/or a Downlink Control Indicator (DCI) including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality, based on the applicability indication.
The method of claim 1, further comprising:

determining, by the first DU, whether to activate or deactivate the at least one AI/ML model and/or AI/ML functionality of the wireless device based on the applicability indication.
The method of claim 1,

wherein activation or deactivation of the at least one AI/ML model and/or AI/ML functionality of the wireless device is determined by the first CU.
The method of claim 3,

wherein information related to the activation or deactivation of the at least one AI/ML model and/or AI/ML functionality determined by the first CU is included in the applicability indication.
The method of claim 1,

wherein the first message is a UE Context Modification Request message.
The method of claim 1, further comprising:

transmitting, by the first DU to the first CU, a UE Context Modification Response message.
The method of claim 1,

wherein the MAC CE and/or the DCI includes multiple activation commands or deactivation commands for each AI/ML model and/or AI/ML functionality of the wireless device.
The method of claim 1,

wherein the first message is a UE Context Setup Request message.
The method of claim 8,

wherein the UE Context Setup Request message includes information for creating a context for the wireless device and configuring one or more data bearers.
The method of claim 1,

wherein the second message is a UE Context Setup Response message.
The method of claim 1,

wherein the wireless device changes a serving CU from the source CU to the first CU, and

wherein the applicability indication is transmitted from the source CU to the first CU via a Handover Request message.
The method of claim 1, further comprising:

receiving, by the first DU from the wireless device, a third message including applicability of the AI/ML model and/or the AI/ML functionality of the wireless device.
The method of claim 12, further comprising:

forwarding, by the first DU to the first CU, the applicability of the AI/ML model and/or the AI/ML functionality of the wireless device via the first message.
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 first Distributed Unit (DU) of a first Radio Access Network (RAN) node, comprising:

at least one transceiver;

at least one processor; and

at least one memory operably connectable to the at least one processor and the at least one transceiver, and storing instructions that, based on being executed by the at least one processor, perform operations comprising:

receiving, from a first Central Unit (CU) of the RAN node, a first message including an applicability indication informing whether at least one Artificial Intelligence (AI)/Machine Learning (ML) model and/or AI/ML functionality of a wireless device is applicable or not; and

transmitting, to the wireless device, a Medium Access Control (MAC) Control Element (CE) and/or a Downlink Control Indicator (DCI) including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality, based on the applicability indication.
The first DU of the first RAN node of claim 15, wherein the operations further comprising:

determining whether to activate or deactivate the at least one AI/ML model and/or AI/ML functionality of the wireless device based on the applicability indication.
The first DU of the first RAN node of claim 15,

wherein activation or deactivation of the at least one AI/ML model and/or AI/ML functionality of the wireless device is determined by the first CU.
The first DU of the first RAN node of claim 15,

wherein information related to the activation or deactivation of the at least one AI/ML model and/or AI/ML functionality determined by the first CU is included in the applicability indication.
The first DU of the first RAN node of claim 15,

wherein the first message is a UE Context Modification Request message.
The first DU of the first RAN node of claim 15, wherein the operations further comprising:

transmitting, to the first CU, a UE Context Modification Response message.
The first DU of the first RAN node of claim 15,

wherein the MAC CE and/or the DCI includes multiple activation commands or deactivation commands for each AI/ML model and/or AI/ML functionality of the wireless device.
The first DU of the first RAN node of claim 15,

wherein the first message is a UE Context Setup Request message.
The first DU of the first RAN node of claim 22,

wherein the UE Context Setup Request message includes information for creating a context for the wireless device and configuring one or more data bearers.
The first DU of the first RAN node of claim 15,

wherein the second message is a UE Context Setup Response message.
The first DU of the first RAN node of claim 15,

wherein the wireless device changes a serving CU from the source CU to the first CU, and

wherein the applicability indication is transmitted from the source CU to the first CU via a Handover Request message.
The first DU of the first RAN node of claim 15, wherein the operations further comprising:

receiving, from the wireless device, a third message including applicability of the AI/ML model and/or the AI/ML functionality of the wireless device.
The first DU of the first RAN node of claim 26, wherein the operations further comprising:

forwarding, to the first CU, the applicability of the AI/ML model and/or the AI/ML functionality of the wireless device via the first message.
The first DU of the first RAN node 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 first Distributed Unit (DU) of a first Radio Access Network (RAN) node in a wireless communication system, wherein the processor is adapted to control the first DU to perform operations comprising:

receiving, from a first Central Unit (CU) of the RAN node, a first message including an applicability indication informing whether at least one Artificial Intelligence (AI)/Machine Learning (ML) model and/or AI/ML functionality of a wireless device is applicable or not; and

transmitting, to the wireless device, a Medium Access Control (MAC) Control Element (CE) and/or a Downlink Control Indicator (DCI) including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality, based on the applicability indication.
A non-transitory computer-readable medium having stored thereon a plurality of instructions, which, when executed by a processor of a first Distributed Unit (DU) of a first Radio Access Network (RAN) node, cause the first DU to perform operations, the operations comprising,

receiving, from a first Central Unit (CU) of the RAN node, a first message including an applicability indication informing whether at least one Artificial Intelligence (AI)/Machine Learning (ML) model and/or AI/ML functionality of a wireless device is applicable or not; and

transmitting, to the wireless device, a Medium Access Control (MAC) Control Element (CE) and/or a Downlink Control Indicator (DCI) including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality, based on the applicability indication.
A method, comprising:

transmitting, by a wireless device to a first CU of a first RAN node, information related to applicability of the AI/ML model and/or the AI/ML functionality of the wireless device,

wherein the first CU transmits, to a first DU of the first RAN node, a first message including an applicability indication informing the applicability of the AI/ML model and/or the AI/ML functionality of the wireless device; and

receiving, by the wireless device from the first DU, a MAC CE and/or a DCI including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality.
A wireless device, comprising:

at least one transceiver;

at least one processor; and

at least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations comprising:

transmitting, to a first CU of a first RAN node, information related to applicability of the AI/ML model and/or the AI/ML functionality of the wireless device,

wherein the first CU transmits, to a first DU of the first RAN node, a first message including an applicability indication informing the applicability of the AI/ML model and/or the AI/ML functionality of the wireless device; and

receiving, from the first DU, a MAC CE and/or a DCI including an activation command or a deactivation command for the at least one AI/ML model and/or AI/ML functionality.