Applicability reporting during handover
By enabling UE to report applicability information for ML functionalities, the system optimizes handover processes, reducing signaling complexity and ensuring smooth transitions in telecommunications systems.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-09-23
- Publication Date
- 2026-04-09
AI Technical Summary
Existing telecommunications systems face challenges in efficiently reporting and managing machine learning (ML) functionalities during handovers, leading to increased signaling complexity and inefficiencies in handover processes.
Implementing a system where user equipment (UE) reports applicability information for ML functionalities associated with candidate cells, allowing for optimized handover decisions based on stored applicability information and reduced signaling.
Enhances handover efficiency by reducing signaling overhead and ensuring seamless continuity of ML functionalities during handovers, thereby improving network performance.
Smart Images

Figure EP2025077141_09042026_PF_FP_ABST
Abstract
Description
APPLICABILITY REPORTING DURING HANDOVERTECHNOLOGICAL FIELD
[0001] The present disclosure relates generally to telecommunications and, in particular, to layer 1 measurement reporting in a telecommunications system.BACKGROUND
[0002] A telecommunications system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations and / or other nodes by providing carriers between the various entities involved in the communications path. A telecommunications system can be provided for example by means of a communication network and one or more compatible communication devices. The communication sessions may comprise, for example, communication of data for carrying communications such as voice, video, electronic mail (email), text message, multimedia and / or content data and so on. Non-limiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.
[0003] In a wireless telecommunications system, at least a part of a communication session between at least two stations occurs over a wireless link. Examples of wireless telecommunications systems comprise public land mobile networks (PLMN), satellite based communication systems and different wireless local networks, for example wireless local area networks (WLAN). Some wireless systems can be divided into cells, and are therefore often referred to as cellular systems.
[0004] A user can access the telecommunications system by means of an appropriate communication device or terminal. A communication device of a user may be referred to as user equipment (UE) or user device. A communication device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly withother users. The communication device may access a carrier provided by a station, for example a base station of a cell, and transmit and / or receive communications on the carrier.
[0005] The telecommunications system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the communication system are permitted to do and how operations should be achieved. Communication protocols and / or parameters which shall be used for connection of the various entities are also typically defined. One example of a telecommunications system is the Universal Mobile Telecommunications System (UMTS). Other examples of telecommunications systems are Long-Term Evolution (LTE), LTE Advanced and the so-called 5G or New Radio (NR) networks. NR is being standardized by the 3rd Generation Partnership Project (3GPP).BRIEF SUMMARY
[0006] Example implementations of the present disclosure are directed to telecommunications and, in particular, to layer 1 measurement reporting in a telecommunications system. The present disclosure includes, without limitation, the following example implementations.
[0007] Some example implementations provide an apparatus implementing a user equipment (UE), the apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to at least: receive a configuration from a serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; report to the serving cell applicability information for one or more applicable ML functionalities associated with at least one candidate cell according to the configuration, the at least one candidate cell being a previous serving cell for the UE, and for which the applicability information is stored by the UE; receive a handover command message from the serving cell that includes a configuration for a target cell among the at least one candidate cell, the configuration including configuration information on the one or more applicable ML functionalities associated with the target cell; and execute ahandover of the UE from the serving cell to the target cell triggered by the handover command message and based on the configuration including the configuration information.
[0008] Some example implementations provide a method performed by a user equipment (UE), the method comprising: receiving a configuration from a serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; reporting to the serving cell applicability information for one or more applicable ML functionalities associated with at least one candidate cell according to the configuration, the at least one candidate cell being a previous serving cell for the UE, and for which the applicability information is stored by the UE; receiving a handover command message from the serving cell that includes a configuration for a target cell among the at least one candidate cell, the configuration including configuration information on the one or more applicable ML functionalities associated with the target cell; and executing a handover of the UE from the serving cell to the target cell triggered by the handover command message and based on the configuration including the configuration information.
[0009] Some example implementations provide an apparatus implementing a radio access node providing a serving cell for a user equipment (UE), the apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to at least: send a configuration to the UE from the serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; receive from the UE applicability information for one or more applicable ML functionalities associated with at least one candidate cell according to the configuration, the at least one candidate cell being a previous serving cell for the UE, and for which the applicability information is stored by the UE; prepare a target cell among the at least one candidate cell for a handover of the UE, wherein a configuration for the target cell is determined, and the configuration includes configuration information on the one or more applicable ML functionalities associated with the target cell; and send a handover command message tothe UE that includes the configuration for the target cell to trigger the handover of the UE to the target cell based on the configuration information.
[0010] Some example implementations provide a method performed by a radio access node providing a serving cell for a user equipment (UE), the method comprising: sending a configuration to the UE from the serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; receiving from the UE applicability information for one or more applicable ML functionalities associated with at least one candidate cell according to the configuration, the at least one candidate cell being a previous serving cell for the UE, and for which the applicability information is stored by the UE; preparing a target cell among the at least one candidate cell for a handover of the UE, wherein a configuration for the target cell is determined, and the configuration includes configuration information on the one or more applicable ML functionalities associated with the target cell; and sending a handover command message to the UE that includes the configuration for the target cell to trigger the handover of the UE to the target cell based on the configuration information.
[0011] Some example implementations provide an apparatus implementing a user equipment (UE), the apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to at least: receive a configuration from a serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; send to the serving cell a measurement report of measurements on one or more candidate cells triggered by a determination that a measurement reporting event of the configuration is satisfied, wherein the measurement report includes applicability information for one or more applicable ML functionalities associated with at least one candidate cell among the one or more candidate cells; receive a handover command message from the serving cell that includes a configuration for a target cell among the at least one candidate cell for a handover of the UE decided by the serving cell based on the measurements, the configuration including configuration information on the one or more applicable ML functionalities associated with the target cell; execute a handover of theUE from the serving cell to the target cell triggered by the handover command message and based on the configuration.
[0012] Some example implementations provide a method performed by a user equipment (UE), the method comprising: receiving a configuration from a serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; sending to the serving cell a measurement report of measurements on one or more candidate cells triggered by a determination that a measurement reporting event of the configuration is satisfied, wherein the measurement report includes applicability information for one or more applicable ML functionalities associated with at least one candidate cell among the one or more candidate cells; receiving a handover command message from the serving cell that includes a configuration for a target cell among the at least one candidate cell for a handover of the UE decided by the serving cell based on the measurements, the configuration including configuration information on the one or more applicable ML functionalities associated with the target cell; executing a handover of the UE from the serving cell to the target cell triggered by the handover command message and based on the configuration.
[0013] Some example implementations provide an apparatus implementing a radio access node providing a serving cell for a user equipment (UE), the apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to at least: send a configuration to the UE from the serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; receive from the UE a measurement report of measurements on one or more candidate cells triggered by a determination that a measurement reporting event of the configuration is satisfied, wherein the measurement report includes applicability information for one or more applicable ML functionalities associated with at least one candidate cell among the one or more candidate cells; prepare a target cell among the at least one candidate cell for a handover of the UE, wherein a configuration for the target cell is determined, and the configuration includes configuration information on the one or more applicable MLfunctionalities associated with the target cell; and send a handover command message to the UE that includes the configuration for the target cell to trigger the handover of the UE to the target cell based on the configuration information.
[0014] Some example implementations provide a method performed by a radio access node providing a serving cell for a user equipment (UE), the method comprising: sending a configuration to the UE from the serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; receiving from the UE a measurement report of measurements on one or more candidate cells triggered by a determination that a measurement reporting event of the configuration is satisfied, wherein the measurement report includes applicability information for one or more applicable ML functionalities associated with at least one candidate cell among the one or more candidate cells; preparing a target cell among the at least one candidate cell for a handover of the UE, wherein a configuration for the target cell is determined, and the configuration includes configuration information on the one or more applicable ML functionalities associated with the target cell; and sending a handover command message to the UE that includes the configuration for the target cell to trigger the handover of the UE to the target cell based on the configuration information.
[0015] These and other features, aspects, and advantages of the present disclosure will be apparent from a reading of the following detailed description together with the accompanying figures, which are briefly described below. The present disclosure includes any combination of two, three, four or more features or elements set forth in this disclosure, regardless of whether such features or elements are expressly combined or otherwise recited in a specific example implementation described herein. The present disclosure is intended to be read holistically such that any separable features or elements of the disclosure, in any of its aspects and example implementations, should be viewed as combinable unless the context of the disclosure clearly dictates otherwise.
[0016] It will therefore be appreciated that this Brief Summary is provided merely for purposes of summarizing some example implementations so as to provide a basic understanding of some aspects of the disclosure. Accordingly, it will be appreciated that the above described example implementations are merely examples and should not beconstrued to narrow the scope or spirit of the disclosure in any way. Other example implementations, aspects and advantages will become apparent from the following detailed description taken in conjunction with the accompanying figures which illustrate, by way of example, the principles of some described example implementations.BRIEF DESCRIPTION OF THE FIGURE(S)
[0017] Having thus described example implementations of the disclosure in general terms, reference will now be made to the accompanying figures, which are not necessarily drawn to scale, and wherein:
[0018] FIG. 1 illustrates a telecommunications system that includes one or more public land mobile networks (PLMNs) coupled to one or more external data networks, according to some example implementations of the present disclosure;
[0019] FIG. 2 illustrates a 5G deployment of a PLMN, according to some example implementations;
[0020] FIGS. 3 A, 3B and 3C illustrate a signaling chart for mobility of a user equipment (UE) in a CU-DU split architecture, according to some example implementations;
[0021] FIGS. 4A, 4B and 4C are flowcharts illustrating various steps in a method performed by a UE, according to various example implementations;
[0022] FIGS. 5 A and 5B are flowcharts illustrating various steps in a method performed by a radio access node providing a serving cell for a UE, according to various example implementations;
[0023] FIGS. 6A, 6B and 6C are flowcharts illustrating various steps in a method performed by a UE, according to various example implementations;
[0024] FIGS. 7Aand 7B are flowcharts illustrating various steps in a method performed by a radio access node providing a serving cell for a UE, according to various example implementations; and
[0025] FIG. 8 illustrates an apparatus according to some example implementations.DETAILED DESCRIPTION
[0026] Some implementations of the present disclosure will now be described more fully hereinafter with reference to the accompanying figures, in which some, but not all implementations of the disclosure are shown. Indeed, various implementations of the disclosure may be embodied in many different forms and should not be construed as limited to the implementations set forth herein; rather, these example implementations are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Like reference numerals refer to like elements throughout.
[0027] Unless specified otherwise or clear from context, references to first, second or the like should not be construed to imply a particular order. A feature described as being above another feature (unless specified otherwise or clear from context) may instead be below, and vice versa; and similarly, features described as being to the left of another feature else may instead be to the right, and vice versa. Also, while reference may be made herein to quantitative measures, values, geometric relationships or the like, unless otherwise stated, any one or more if not all of these may be absolute or approximate to account for acceptable variations that may occur, such as those due to engineering tolerances or the like.
[0028] As used herein, unless specified otherwise or clear from context, the “or” of a set of operands is the “inclusive or” and thereby true if and only if one or more of the operands is true, as opposed to the “exclusive or” which is false when all of the operands are true. Thus, for example, “[A] or [B]” is true if [A] is true, or if [B] is true, or if both [A] and [B] are true. Further, the articles “a” and “an” mean “one or more,” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, it should be understood that unless otherwise specified, the terms “data,” “content,” “digital content,” “information,” and similar terms may be at times used interchangeably. The term “network” may refer to a group of interconnected computers including clients and servers; and within a network, these computers may be interconnected directly or indirectly by various means including via one or more switches, routers, gateways, access points or the like.
[0029] Reference may be made herein to terms specific to a particular system, architecture or the like, but it should be understood that example implementations of the present disclosure may be equally applicable to any of a number of systems, architectures and the like. For example, reference may be made to 3 GPP technologies such as Global System for Mobile Communications (GSM), UMTS, LTE, LTE Advanced, 5GNR, 5G Advanced and 6G; however, it should be understood that example implementations of the present disclosure may be equally applicable to non-3GPP technologies such as IEEE 802, Bluetooth and Bluetooth Low Energy.
[0030] Further, as used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry); (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); or (c) hardware circuit(s) and / or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0031] The above definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0032] FIG. 1 illustrates a telecommunications system 100 according to various example implementations of the present disclosure. The telecommunications system generally includes one or more telecommunications networks. As shown, for example, the system includes one or more PLMNs 102 coupled to one or more other external data networks 104 - notably including a wide area network (WAN) such as the Internet. Eachof the PLMNs includes a core network (CN) 106 backbone such as the Evolved Packet Core (EPC) of LTE, the 5G core network (5GC) or the like; and each of the core networks and the Internet are coupled to one or more RANs 108, air interfaces or the like that implement one or more radio access technologies (RATs). As used herein, a “network device” refers to any suitable device at a network side of a telecommunications network. Examples of suitable network devices are described in greater detail below.
[0033] In addition, the system includes one or more radio units that may be varyingly known as user equipment (UE) 110, terminal device, terminal equipment, mobile station or the like. The UE is generally a device configured to communicate with a network device or a further UE in a telecommunications network. The UE may be a portable computer (e.g., laptop, notebook, tablet computer), mobile phone (e.g., cell phone, smartphone), wearable computer (e.g., smartwatch), or the like. In other examples, the UE may be an Internet of things (loT) device, an industrial loT (IIoT device), a vehicle equipped with a vehicle-to-everything (V2X) communication technology, or the like. In some examples, as referenced by 3 GPP, the UE may be a narrowband loT (NB-IoT) device, an enhanced machine-type communication (eMTC) device, a reduced capability (RedCap) device, an ambient loT device, or the like.
[0034] In operation, these UEs 110 may be configured to connect to one or more of the RANs 108 according to their particular radio access technologies to thereby access a particular CN 106 of a PLMN 102, or to access one or more of the external data networks 104 (e.g., the Internet). The external data network may be configured to provide Internet access, operator services, 3rd party services, etc. For example, the International Telecommunication Union (ITU) has classified 5G mobile network services into three categories: enhanced mobile broadband (eMBB), ultra- reliable and low-latency communications (URLLC), and massive machine type communications (mMTC) or massive internet of things (MIoT).
[0035] Examples of radio access technologies include 3 GPP radio access technologies such as GSM, UMTS, LTE, LTE Advanced, 5GNR, 5G Advanced, and 6G. Other examples of radio access technologies include IEEE 802 technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.15 (including 802.15.1 (WPAN / Bluetooth), 802.15.4 (Zigbee) and 802.15.6 (WBAN)), Bluetooth, Bluetooth Low Energy (BLE), ultrawideband (UWB), and the like. Generally, a radio access technology may refer to any 2G, 3G, 4G, 5G, 6G or higher generation mobile communication technology and their different versions, as well as to any other wireless radio access technology that may be arranged to interwork with such a mobile communication technology to provide access to the CN 106 of a mobile network operator (MNO).
[0036] In various examples, a RAN 108 may be configured as one or more macrocells, microcells, picocells, femtocells or the like. The RAN may generally include one or more radio access nodes that are configured to interact with UEs 110. In various examples, a radio access node may be referred to as a base station (BS), access point (AP), base transceiver station (BTS), Node B (NB), evolved NB (eNB), macro BS, NB (MNB) or eNB (MeNB), home BS, NB (HNB) or eNB (HeNB), next generation NB (gNB), enhanced gNB (en-gNB), next generation eNB (ng-eNB), or the like. The RAN may include some type of network controlling / governing entity responsible for control of the radio access nodes. The network controlling / governing entity and radio access node may be separate or integrated into a single apparatus. The network controlling / governing entity may include processing circuity configured to carry out various management functions, etc. The processing circuity may be associated with a memory, computer- readable storage medium or database for maintaining information required in the management functions.
[0037] A RAN 108 may be centralized or distributed. In various examples, components of a RAN may be interconnected by Ethernet, Gigabit Ethernet, Asynchronous Transfer Mode (ATM), optical fiber, dark fiber, passive wavelength division multiplexing (WDM), WDM passive optical network (WDM-PON), optical transport network (OTN), time sensitive networking (TSN) and / or any other data link layer network, possibly including radio links. The RAN may be connected to a CN 106 through one or more gateways, network functions or the like.
[0038] As will be appreciated, a PLMN 102 may be deployed in a number of different manners. In a 4GLTE deployment, the EPC is the CN 106, and the evolved UMTS terrestrial radio access network (E-UTRAN) is the RAN 108; and the E-UTRAN includes one or more eNBs (radio access nodes) configured to connect UEs 110 to the E- UTRAN to thereby access the EPC. As shown in FIG. 2, in a 5G deployment 200, the5GC 202 is the CN, and the next generation (NG) radio access network (NG-RAN) 204 is the RAN; and the NG-RAN includes one or more gNBs 206 (radio access nodes) configured to connect UEs 110 to the NG-RAN to thereby access the 5GC (at times referred to as the NGC). The term ‘gNB’ in 5G may correspond to the eNB in 4G LTE.
[0039] Some deployments of 4G LTE and 5G in particular are considered standalone (SA) deployments. Other deployments combine 4G LTE and 5G technologies, and are referred to as non-standalone (NSA) deployments. In some deployments, the E-UTRAN includes one or more ng-eNBs that are configured to communicate with the 5GC, and that may also be configured to communicate with one or more gNBs. Similarly, in another deployment, the NG-RAN may include one or more en-gNBs that are configured to communicate with the EPC, and that may also be configured to communicate with one or more eNBs. In various instances, a single UE 110, a dual-mode or multimode UE, may support multiple (two or more) RANs — thereby being configured to connect to multiple RANs, such as 4G LTE and 5G.
[0040] In some deployments, operations of a gNB 206 or other radio access node may be distributed or functionally split into components including one or more remote radio head (RRHs) or radio units (RUs) 208, and a baseband unit (BBU); and in some architectures, the BBU may be split into a distributed unit (DU) 210 and a central / centralized unit (CU) 212, such as a server, host or node. In some architectures, the RRH / RU and DU may be co-located. It is also possible that node operations may be distributed among a plurality of servers, hosts or nodes. It should also be understood that the distribution of work between CN operations and radio access node operations may vary depending on implementation.
[0041] As shown and described, for example, some 5G deployments may be based on a so-called CU-DU split including one or more DUs 210 and a CU 212. One gNB-CU (central node) may control one or more gNB-DUs. The gNB-CU may control a plurality of spatially separated gNB-DUs, acting at least as transmit / receive (Tx / Rx) nodes. In some example implementations, however, the gNB-DUs (also called DU) may include, for example, a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the gNB-CU (also called a CU) may include the layers above the RLC layer, such as a packet data convergence protocol (PDCP) layer, a radioresource control (RRC), and an internet protocol (IP) layer. Other functional splits are also possible. It is considered that a skilled person is familiar with the open systems interconnection (OSI) model and the functionalities within each layer.
[0042] In some example implementations, the server or CU 212 may generate a virtual network through which the server communicates with the radio node. In general, virtual networking may involve a process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Such virtual network may provide flexible distribution of operations between the server and the radio head / node. In practice, any digital signal processing task may be performed in either the CU or the DU 210, and the boundary where the responsibility is shifted between the CU and the DU may be selected according to implementation.
[0043] In 3 GPP, an investigation is ongoing regarding the use of artificial intelligence (Al) / machine learning (ML) technologies and algorithms for enhanced performance and / or reduced complexity / overhead by cementing the foundation for future air-interface use cases. Initial use cases under investigation include channel state information (CSI) feedback enhancement (e.g., overhead reduction, improved accuracy), beam management (e.g., beam prediction in time, and / or spatial domain for overhead and latency reduction), positioning accuracy enhancements, and mobility.
[0044] A general AI / ML framework has been provided that identifies common notation and terminology for AI / ML-related functions, procedures and interfaces. The stages of AI / ML include model generation (e.g., model training, model validation, model testing, etc.) and inference operation (e.g., input / output, pre- / post-process, etc.). In this regard, life cycle management (LCM) of an AI / ML model may include, for example, model training, model deployment, model inference, model monitoring and model updating. For an LCM procedure, it may be the case that an AI / ML model (at times more generally referred to as a “model”) has a model identifier (ID) with associated information. Additionally or alternatively, it may be the case that a given functionality is provided by some AI / ML operations.
[0045] For UE-side models and the UE-part of two-sided models, UE capability reporting may be taken as a starting point for the identification of AI / ML functionality (attimes more simply referred to as ML functionality). For AI / ML functionality identification and functionality-based LCM of UE-side models and / or UE-part of two- sided models, functionality refers to an AI / ML-enabled feature or feature group (FG) enabled by one or more configurations supported based on conditions indicated by UE capability. Likewise, functionality-based LCM operates based on at least one configuration of AI / ML-enabled feature / FG or specific configurations of an AI / ML- enabled feature / FG. For AI / ML model identification and model-ID-based LCM of UE- side models and / or UE-part of two-sided models, model-ID-based LCM operates based on identified models. In this regard, a model may be associated with specific configurations / conditions associated with UE capability of an AI / ML-enabled feature / FG and additional conditions (e.g., scenarios, sites, and datasets) as determined / identified between UE-side and network (NW)-side.
[0046] In the general AI / ML framework, functionalities may be distinguished between supported functionalities, applicable functionalities and activated functionalities. Supported functionalities refer to functionalities that a UE 110 can indicate to the network (e.g., gNB 206 of NG-RAN 204) by using UE capability information (via RRC signaling / LTE positioning protocol (LPP) signaling). These are the AI / ML-enabled features / FGs that a UE is capable of supporting. Applicable functionalities refer to functionalities that the UE is ready to apply for inference. Applicable functionalities are a subset of the supported functionalities that are relevant and suitable for current network conditions or use case. Activated functionalities refer to functionalities already enabled for performing inference. The activated functionalities are a subset of the applicable functionalities that are currently in use or enabled on the UE.
[0047] Conditions that identify AL / ML features / functionalities may be signaled through a UE capability message (in the RRC configuration), and are currently under the refinement within the 3GPP. Some proposals have been made on their structure (e.g., general-level conditions that are applicable regardless of the enabled use case, and usecase specific conditions) and contents. In particular, some proposals have been made for general conditions, as well as for CSI compression enhancement, beam management, and positioning specific conditions. As these proposals have demonstrated, the number of conditions and their potential content / values are extensive, and they are expected to onlyprogress as new AI / ML use cases and functionalities are introduced. This will make it even more laborious to signal conditions through the UE capability message and the corresponding synchronization from the network side to process.
[0048] The general AI / ML framework defines additional conditions for an AI / ML- enabled feature / FG. In this regard, additional conditions refer to any aspects that are assumed for the training of the model but are not a part of UE capability for the AI / ML- enabled feature / FG. It does not imply that additional conditions are necessarily specified. Additional conditions can be divided into two categories: NW-side additional conditions and UE-side additional conditions. For inference for UE-side models, to ensure consistency between training and inference regarding NW-side additional conditions (if identified), a number of options may be taken as potential approaches (when feasible and necessary). In one of these options, information and / or indication on NW-side additional conditions is provided to the UE 110 by the network.
[0049] In some contexts, the UE 110 may need to determine whether a supported functionality is applicable (an applicable functionality) for a given condition. The UE may determine an applicable functionality based on NW-side additional conditions (if identified), UE-side additional conditions (the UE’s internal condition), and model availability. While the determination of UE-side additional conditions and model availability are up to UE implementation, NW-side additional conditions are network provided information to maintain the consistency between training and inference assumption. One example of a NW-side additional condition is an associated ID. The associated ID serves to align the assumptions made across training and at least inference, and may be monitoring of a model. Through this ID, the UE can detect the consistency across training and inference. For instance, the associated ID may impact the UE’s assumption on beams of set A / set B in beam management use case 1 and case 2. The format of the associated ID may be a sequence of bits representing network’s codebook configurations during training, such as antenna direction. Once UE is able to determine the applicable functionality with this information, the UE may need to report an indication of the applicable functionality(ies) to the network.
[0050] In view of the foregoing, example implementations of the present disclosure provide a solution for applicability reporting that enables the reporting of applicablefunctionality associated with neighbor cells, which may be candidate cells for mobility of a UE 110. The solution of some example implementations may also provide a means for reducing signaling associated with the reporting of applicable functionality.
[0051] According to some example implementations, as UE 110 may report applicability information for one or more candidate cells, such as applicable functionality or NW-side additional conditions associated with the candidate cell(s). The applicability information may be reported in a number of different manners, such as through RRC, MAC control element (CE) or uplink control information (UCI) signaling. Some example implementations may provide UE behavior associated with storing applicability information of candidate cells which were previous serving cells (e.g., in cases of ping- pong scenarios). Some example implementations may also provide for activation / deactivation of one or more functionalities during handover (HO) of the UE to a target cell among the candidate cell(s).
[0052] Some example implementations of the present disclosure provide an enhancement to a handover request message or a handover preparation message to also include applicability information. Similarly, some example implementations may provide an enhancement to a handover request acknowledge message to also include information about functionality continuity during and after handover of a UE from a serving cell to a target cell.
[0053] FIGS. 3A, 3B and 3C illustrate a signaling chart 300 for mobility of a UE 110 in a CU-DU split architecture, according to some example implementations. As shown, a serving CU of a serving gNB 206 is denoted as S-CU 212A, and the serving cell is provided by a serving DU denoted as S-DU 210A. The S-DU and another DU, denoted DU2 210B, belong to the serving CU. This other DU may provide a target cell for intra- CU handover. A target CU of a target gNB for inter-CU handover is denoted as CU2 212B, and another DU, denoted DU3 210C, belongs to the target CU and provides the target cell for the inter-CU handover.
[0054] As shown in FIG. 3A, the S-CU 212A at step 301 sends a measurement configuration to the UE 110. As an example, this measurement configuration may be sent to the UE via RRC signaling. As part of the measurement configuration, the S-CU may indicate to the UE that the UE can report applicability information for one or more(neighbor) candidate cells on which the UE performs measurements according to the measurement configuration. This indication can be part of the same RRC signaling, or through a new message, which can be signaled again through RRC signaling, MAC CE or downlink control information (DCI).
[0055] As shown at steps 302, 303, the UE 110 is connected to serving cell (provided by S-DU 210A) to which the UE has reported one or more applicable functionalities (via applicability reporting signaled through, e.g., RRC, MAC CE, DCI), and for which the UE has activated a functionality from the applicable functionality(ies). The measurement configuration may configure the UE to report measurements performed on the candidate cell(s) (e.g., DU2 210B, DU3 210C), and the measurement configuration may include one or more measurement reporting events (e.g., A3, A4 or A5 event).
[0056] The UE 110 may perform measurements on the candidate cell(s), perform an evaluation of the measurement reporting event(s), and determine when a measurement reporting event is satisfied for at least one of the candidate cell(s) based on the measurements. The UE may then prepare and send a measurement report to the S-DU 210A report the measurements to the serving cell triggered by the determination that the measurement event is satisfied. The S-DU may forward the measurement report to the S- CU 212A.
[0057] If the UE 110 has prior applicability information (e.g., applicable functionality(ies), NW-side additional conditions) about at least one of the candidate cell(s) (e.g., as a previous serving cell for the UE), the UE may also report the applicability information for the candidate cell, when stored by the UE. This may be the case, for example, in a ping-pong scenario in which the UE is handed over between a cell A and a cell B in the following order: cell A cell B A cell A. In this case, UE may have stored applicability information associated with cell A when the UE was served by cell A. Upon switching back to cell A (from cell B), rather than restarting an applicability exchange procedure, the UE may instead report the previous applicability information for cell A. In some examples, the UE 110 may expose the ability to store NW-side additional conditions associated with different gNBs 206 as a part of its UE capability reporting. The UE may also expose a capability to store applicability information for different gNBs, as well as functionality(ies) previously configured and / or applicable in a gNB thatpreviously served the UE. As part of this capability reporting, the UE may also indicate to the network a maximum amount of information that the UE can store. In one example, this may be indicated as storage space in the UE. In another example, this may be indicated as the maximum number of gNBs and / or cells for which the UE is able to store applicability information (e.g., applicable functionality(ies)).
[0058] As an example, assume the UE 110 supports functionalities A, B, C, D, E. The UE may indicate the supported functionalities in UE capability information provided to its current serving gNB 206, namely gNB2, or the UE may indicate a maximum capability the UE can support. Assume gNB2 then configures functionalities A, C, E to the UE. The UE may then determine which of A, C, and E is applicable for the current UE situation. Say model(s) for functionality A are not available in the UE, and the power level of the UE is too low to use functionality C. In this case, the UE may indicate that functionality E is applicable, and gNB2 may then activate functionality E for inference operation.
[0059] Assume the UE previously operated under another gNB, namely gNBl, with functionalities A and C, and that the UE was handed over from gNBl to gNB2. The UE may store applicability information for functionalities A and B with which the UE previously operated under gNBl. In this case, if the UE is handed back over to gNBl (e.g., in a ping-pong scenario), and functionalities A and C are still applicable, the UE may provide the applicability information for gNBl to gNB2 (the current serving gNB). In one example, the applicability information may be provided through dedicated signaling, such as UE assistance information (UAI). In another example, the applicability information may be provided together with the measurement report sent from the UE to gNB2. In yet another example, this can be provided through dedicated UL signaling, such as RRC, MAC or DCI.
[0060] As shown at steps 304 and 305 for intra-CU mobility, the S-CU 212A decides to initiate a handover procedure for mobility of the UE 110, such as based on the measurement report from the UE. The S-CU decides to prepare DU2 210B as a candidate for mobility. In some examples in which the UE did not report applicability information for cell(s) provided by DU2, the S-CU may in step 304 request applicable functionality(ies) determined by NW-side additional conditions associated with DU2,which the DU2 may send to the S-CU in step 305. As an example, assume that DU2 has NW-side additional conditions (e.g., associated ID 2 + some other extra information 2). The S-CU may collect the associated ID (ID2) and extra information (info2).
[0061] In some examples in which the UE 110 did report applicability information for cell(s) provided by DU2 210B, the S-CU 212A may forward the applicability information to DU2. The S-CU may also inform DU2 about the current active functionality in the UE. In return, DU2 may indicate to the S-CU whether the active functionality associated with the serving cell may be continued during and / or after the handover.
[0062] If the active functionality associated with the serving cell cannot be continued during the handover, DU2 210B may indicate a functionality to which the UE 110 can switch. This functionality may be, for example, a fallback functionality associated with the NW-side additional conditions (e.g., associated ID), or a functionality ID (e.g., RRC ID, RACS ID, or other type of unique ID associated with a functionality configuration sent to the UE by the gNB). In some other examples, DU2 may send its associated ID to the S-CU 212A, which may forward the associated ID to the UE. If none of the functionalities that DU2 can configure match functionalities that the S-DU can configure, DU2 may send its own NW-side additional conditions and new associated ID to the S- CU.
[0063] As shown in FIG. 3B, at steps 306, 307, 308 and 309 for inter-CU mobility, the S-CU 212A may choose to prepare DU3 210C under CU2 212B as a candidate for mobility. In this case, under a handover request message, the S-CU can send to CU2 applicability information reported by the UE 110. The S-CU can also inform CU2 about the functionality(ies) configured in the UE. Similar to steps 303 and 304 described above, in some examples in which the UE did not report applicability information for cell(s) provided by DU3, the S-CU may request from CU2 NW-side additional conditions pertaining to DU3, and CU2 may contact DU3 to request the NW-side additional conditions (as requested by the S-CU). DU3 may return the NW-side additional conditions to CU2, which may in turn forward the NW-side additional conditions to the S-CU, as shown in steps 308 and 309.
[0064] In some examples in which the UE 110 did report applicability information for cell(s) provided by DU3 210C, the S-CU 212A may forward (via CU2 212B) theapplicability information to DU3. The S-CU may also inform (via CU2) DU3 about the current active functionality in the UE. In return, DU3 may indicate to the S-CU (via CU2) whether the active functionality associated with the serving cell may be continued during and / or after the handover.
[0065] If the active functionality associated with the serving cell cannot be continued during the handover, DU3 210C may indicate (via CU2 212B) a functionality to which the UE 110 can switch. This functionality may be, for example, a fallback functionality associated with the NW-side additional conditions (e.g., associated ID), or a functionality ID (e.g., RRC ID, RACS ID, or other type of unique ID associated with a functionality configuration sent to the UE by the gNB). In some other examples, DU3 may send its associated ID to CU2, and CU2 may forward the associated ID to the S-CU 212A, which may forward the associated ID to the UE. If none of the functionalities that DU3 can configure matches functionalities that the S-DU can configure, DU3 may send its own NW-side additional conditions and new associated ID to CU2, and CU2 may forward the NW-side additional conditions and the new associated ID to the S-CU.
[0066] In some examples, CU2 212 may make one or more of the above decisions described above as being made by DU3 210C. In this regard, CU2 may inform DU3 about the NW-side additional conditions CU2 expects DU3 to support. Alternatively, CU2 may inform DU3 about functionality(ies) that DU3 should support. In some examples, DU3 may accept the configuration from CU2. In other examples, DU3 may reject the configuration from CU2. In these other examples, CU2 may inform the S-DU that DU3 has rejected the configuration.
[0067] As shown, CU2212B at step 309 then sends the configuration for the target cell under DU3 210C to the S-CU 212A as part of a handover request acknowledge message.
[0068] The S-CU 212A at step 310 consolidates the target cell configuration, and sends the configuration to the UE, such as in a handover command message (e.g., RRC reconfiguration message). The configuration may include configuration information on applicable functionality(ies) associated with the target cell. In some examples, the S-CU may send NW-side additional conditions associated with the target cell. In other examples, S-CU informs UE to deactivate the active functionality during and afterhandover upon determining the NW-side additional conditions reported by the S-DU 210A and target DU (e.g., DU2 210B, DU3 210C) do not have any common NW-side additional conditions. In some examples, the configuration information may be sent to the UE by an information element (IE) in the RRC reconfiguration message that indicates to the UE that the UE should reset its functionality(ies) and / or features.
[0069] In some examples, the S-CU 212A can inform the UE 110 that the UE can reuse the previously applicable functionalities. This can be done either by dedicated signaling, or implicitly (e.g., S-CU gives no indication of new AI / ML functionalities, but indicates simply that UE can use AI / ML functionalities). Upon reception of such indication, the UE may understand that the UE can re-use the functionality that was previously configured for that gNB. For instance, in case of handover from gNBl at a first time instance to gNB2 at a later, second time instance, and back to gNBl at an even later, third time instance, if the UE receives such indication upon returning to gNBl, the UE may understand that the UE may re-use the functionality that was already configured when the UE was connected to gNBl at the first time.
[0070] In some examples, the S-CU 212A may send (to the UE 110) NW-side additional conditions associated with the target cell, and the UE may determine whether to deactivate the active functionality based on the NW-side additional conditions. The S- CU may also configure a timer-based mechanism, upon the expiry of which the UE may determine that the UE should deactivate the active functionality. In another example, the S-CU can provide a timer based mechanism based on which the UE may understand that the UE should release any configuration associated with previously configured functionalities. That is, upon this timer expiry, the UE would no longer store any applicable functionality information about previous serving gNBs 206. In yet other examples, the S-CU may indicate to the UE that the UE may continue the active functionality during and / or after handover. The S-CU may also indicate to the UE the functionality that the UE should use during and / or after the handover. In yet other examples, the S-CU can indicate to the UE information on whether applicable conditions need to be reported to the target cell.
[0071] As shown in FIG. 3C, at steps 311, 312 and 313 for handover with deactivated functionality, the UE 110 deactivates the active functionality and executes a legacyhandover procedure without any active functionality. During the handover procedure, the UE may inform the network about the UE-side additional conditions and / or applicable functionality(ies). In one example, the UE may report this information during a random access (RA) procedure towards the target cell (e.g., in msg3). In another example, the UE may report the information piggybacked into a buffer status report (BSR). In yet another example, the UE may report the information together with the RRC reconfiguration complete message. Upon reception of the UE-side additional conditions and / or applicable functionality(ies), the network may reconfigure functionality(ies) in the UE.
[0072] As shown at steps 314, 315 and 316 for handover with changed functionality, the UE may deactivate the active functionality associated with the serving cell, and switch to a functionality associated with the target cell, as may be indicated in the handover command message (RRC reconfiguration message). In some example, the indicated functionality may be the fallback functionality or a different functionality indicated by the network.
[0073] In some examples, the UE 110 may deactivate the active functionality and switch to the indicated functionality during handover, and then deactivate the newly active (indicated) functionality after the handover is complete. In other examples, the UE may continue using the new functionality also after the handover is complete. In other examples, the UE may deactivate the active functionality during handover, and switch to the indicated functionality after the handover is complete.
[0074] Similar to before, during the handover procedure, the UE 110 may inform the network about the UE-side additional conditions and / or applicable functionality(ies). In one example, the UE may report this information during a RA procedure towards the target cell (e.g., in msg3). In another example, the UE may report the information piggybacked into a BSR. In yet another example, the UE may report the information together with the RRC reconfiguration complete message. Upon reception of the UE-side additional conditions and / or applicable functionality (ies), the network may reconfigure functionality(ies) in the UE.
[0075] In some examples, the UE 110 may report non-applicable functionality(ies) via UAI or RRC reconfiguration message in the S-DU 210A or S-CU 212A. Additionally or alternatively, the UE may report non-applicable functionality(ies) to the target DU(e.g., DU2 210B, DU3 210C), such as part of a RRC reconfiguration complete message after the UE successfully accesses the target DU. Once the target DU knows the non- applicable functionality(ies), after the successful handover, the target DU may send a request to the UE for supported functionality(ies).
[0076] FIGS. 4A - 4C are flowcharts illustrating various steps in a method 400 performed by a user equipment (UE), according to various example implementations. The method includes receiving a configuration from a serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell, as shown at block 402 of FIG. 4A. The method includes reporting to the serving cell applicability information for one or more applicable ML functionalities associated with at least one candidate cell according to the configuration, the at least one candidate cell being a previous serving cell for the UE, and for which the applicability information is stored by the UE, as shown at block 404. The method includes receiving a handover command message from the serving cell that includes a configuration for a target cell among the at least one candidate cell, the configuration including configuration information on the one or more applicable ML functionalities associated with the target cell, as shown at block 406. And the method includes executing a handover of the UE from the serving cell to the target cell triggered by the handover command message and based on the configuration including the configuration information, as shown at block 408.
[0077] In some examples, the applicability information for the one or more applicable ML functionalities associated with the at least one candidate cell is reported in a measurement report of measurements performed by the UE on one or more candidate cells including the at least one candidate cell.
[0078] In some examples, the configuration information includes an indication for the UE to continue the activated ML functionality associated with the serving cell as an applicable ML functionality associated with the target cell.
[0079] In some examples, the configuration information includes an indication of one or more network-side additional conditions associated with the target cell. In some of these examples, the method further includes determining whether to deactivate theactivated ML functionality based on the one or more network-side additional conditions associated with the target cell.
[0080] In some examples, the configuration information includes an indication for the UE to reuse the one or more applicable ML functionalities associated with the target cell.
[0081] In some examples, the method 400 further includes receiving an indication from the serving cell to release any applicable ML functionality associated with another cell upon expiration of a timer.
[0082] In some examples, the configuration information includes an indication for the UE to switch from the activated ML functionality associated with the serving cell to an applicable ML functionality associated with the target cell.
[0083] In some examples, the applicable ML functionality associated with the target cell is indicated by an identifier of the applicable ML functionality, or one or more network-side additional conditions associated with the target cell from which the applicable ML functionality associated with the target cell is determinable by the UE.
[0084] In some examples, executing the handover at block 408 includes deactivating the activated ML functionality associated with the serving cell, as shown at block 410 of FIG. 4B. And the method includes activating the applicable ML functionality associated with the target cell, as shown at block 412.
[0085] In some examples, the configuration information includes an indication for the UE to deactivate the activated ML functionality associated with the serving cell. In some of these examples, executing the handover at block 408 includes deactivating the activated ML functionality associated with the serving cell, as shown at block 414 of FIG. 4C. And the method includes executing the handover without any activated ML functionality, as shown at block 416.
[0086] In some examples, the applicability information reported to the serving cell includes at least one non-applicable ML functionality, and the configuration received in the handover command excludes configuration information on the at least one non- applicable ML functionality.
[0087] FIGS. 5 A and 5B are flowcharts illustrating various steps in a method 500 performed by a radio access node (e.g., gNB, gNB-CU) providing a serving cell for auser equipment (UE), according to various example implementations. The method includes sending a configuration to the UE from the serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell, as shown at block 502 of FIG. 5 A. The method includes receiving from the UE applicability information for one or more applicable ML functionalities associated with at least one candidate cell according to the configuration, the at least one candidate cell being a previous serving cell for the UE, and for which the applicability information is stored by the UE, as shown at block 504. The method includes preparing a target cell among the at least one candidate cell for a handover of the UE, In some of these examples, a configuration for the target cell is determined, and the configuration includes configuration information on the one or more applicable ML functionalities associated with the target cell, as shown at block 506. And the method includes sending a handover command message to the UE that includes the configuration for the target cell to trigger the handover of the UE to the target cell based on the configuration information, as shown at block 508.
[0088] In some examples, the applicability information for the one or more applicable ML functionalities associated with the at least one candidate cell is received in a measurement report of measurements performed by the UE on one or more candidate cells including the at least one candidate cell.
[0089] In some examples, preparing the target cell at block 506 includes determining the configuration information, and the configuration information includes an indication for the UE to continue the activated ML functionality associated with the serving cell as an applicable ML functionality associated with the target cell.
[0090] In some examples, the configuration information includes an indication of one or more network-side additional conditions associated with the target cell for the UE to determine whether to deactivate the activated ML functionality based on the one or more network-side additional conditions associated with the target cell.
[0091] In some examples, the configuration information includes an indication for the UE to reuse the one or more applicable ML functionalities associated with the target cell.
[0092] In some examples, the method 500 further includes sending an indication to the UE to release any applicable ML functionality associated with another cell upon expiration of a timer.
[0093] In some examples, preparing the target cell at block 506 includes determining the configuration information, and the configuration information includes an indication for the UE to switch from the activated ML functionality associated with the serving cell to an applicable ML functionality associated with the target cell.
[0094] In some examples, the applicable ML functionality associated with the target cell is indicated by an identifier of the applicable ML functionality, or one or more network-side additional conditions associated with the target cell from which the applicable ML functionality associated with the target cell is determinable by the UE.
[0095] In some examples, preparing the target cell at block 506 includes determining the configuration information, and the configuration information includes an indication for the UE to deactivate the activated ML functionality associated with the serving cell, and execute the handover without any activated ML functionality.
[0096] In some examples, the applicability information received from the UE includes at least one non-applicable ML functionality, and the configuration determined for the target cell excludes configuration information on the at least one non-applicable ML functionality.
[0097] In some examples, preparing the target cell at block 506 includes sending a message towards the target cell that includes the applicability information for the one or more applicable ML functionalities associated with the target cell, as shown at block 510 of FIG. 5B. And the method includes receiving an acknowledge message in response to the message that includes the configuration information on the one or more applicable ML functionalities associated with the target cell, as shown at block 512.
[0098] In some examples, the message sent towards the target cell includes an indication of the activated ML functionality, and the configuration information in the acknowledge message includes an indication for the UE to continue the activated ML functionality or switch from the activated functionality to an applicable ML functionality associated with the target cell.
[0099] In some examples, the radio access node is implemented by distributed units (DU) and a central unit (CU), and the handover is an intra-CU handover in which the DUs provide respective cells including the serving cell and the target cell. In some of these examples, the message sent towards the target cell is sent to one of the DUs that provides the target cell, and the acknowledge message is received from the one of the DUs.
[0100] In some examples, the radio access node is implemented by one or more distributed units (DU) and a central unit (CU), and the handover is an inter-CU handover in which the one or more DUs provide respective cells including the serving cell, and the target cell is provided by a second DU of a second radio access node that also includes a second CU. In some of these examples, the message sent towards the target cell is sent to the second CU for the second DU, and the acknowledge message is received from the second CU that received the acknowledge message from the second DU.
[0101] FIGS. 6A ~~ 6C are flowcharts illustrating various steps in a method 600 performed by a user equipment (UE), according to various example implementations. The method includes receiving a configuration from a serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell, as shown at block 602 of FIG. 6A. The method includes sending to the serving cell a measurement report of measurements on one or more candidate cells triggered by a determination that a measurement reporting event of the configuration is satisfied, In some of these examples, the measurement report includes applicability information for one or more applicable ML functionalities associated with at least one candidate cell among the one or more candidate cells, as shown at block 604. The method includes receiving a handover command message from the serving cell that includes a configuration for a target cell among the at least one candidate cell for a handover of the UE decided by the serving cell based on the measurements, the configuration including configuration information on the one or more applicable ML functionalities associated with the target cell, as shown at block 606. The method includes executing a handover of the UE from the serving cell to the target cell triggered by the handover command message and based on the configuration, as shown at block 608.
[0102] In some examples, the configuration information includes an indication for the UE to continue the activated ML functionality associated with the serving cell as an applicable ML functionality associated with the target cell.
[0103] In some examples, the configuration information includes an indication of one or more network-side additional conditions associated with the target cell. In some of these examples, the method further includes determining whether to deactivate the activated ML functionality based on the one or more network-side additional conditions associated with the target cell.
[0104] In some examples, the configuration information includes an indication for the UE to reuse the one or more applicable ML functionalities associated with the target cell.
[0105] In some examples, the method 600 further includes receiving an indication from the serving cell to release any applicable ML functionality associated with another cell upon expiration of a timer.
[0106] In some examples, the configuration information includes an indication for the UE to switch from the activated ML functionality associated with the serving cell to an applicable ML functionality associated with the target cell.
[0107] In some examples, the applicable ML functionality associated with the target cell is indicated by an identifier of the applicable ML functionality.
[0108] In some examples, the applicable ML functionality associated with the target cell is indicated by one or more network-side additional conditions associated with the target cell. In some of these examples, the method further includes determining the applicable ML functionality associated with the target cell based on the one or more network-side additional conditions, one or more UE-side additional conditions, and ML model availability in the UE.
[0109] In some examples, executing the handover at block 608 includes deactivating the activated ML functionality associated with the serving cell, as shown at block 610 of FIG. 6B. And the method includes activating the applicable ML functionality associated with the target cell, as shown at block 612.
[0110] In some examples, the configuration information includes an indication for the UE to deactivate the activated ML functionality associated with the serving cell. In someof these examples, executing the handover at block 608 includes deactivating the activated ML functionality associated with the serving cell, as shown at block 614 of FIG. 6C. And the method includes executing the handover without any activated ML functionality, as shown at block 616.
[0111] FIGS. 7 A and 7B are flowcharts illustrating various steps in a method 700 performed by a radio access node (e.g., gNB, gNB-CU) providing a serving cell for a user equipment (UE), according to various example implementations. The method includes sending a configuration to the UE from the serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell, as shown at block 702 of FIG. 7A. The method includes receiving from the UE a measurement report of measurements on one or more candidate cells triggered by a determination that a measurement reporting event of the configuration is satisfied, In some of these examples, the measurement report includes applicability information for one or more applicable ML functionalities associated with at least one candidate cell among the one or more candidate cells, as shown at block 704. The method includes preparing a target cell among the at least one candidate cell for a handover of the UE, In some of these examples, a configuration for the target cell is determined, and the configuration includes configuration information on the one or more applicable ML functionalities associated with the target cell, as shown at block 706. And the method includes sending a handover command message to the UE that includes the configuration for the target cell to trigger the handover of the UE to the target cell based on the configuration information, as shown at block 708.
[0112] In some examples, preparing the target cell at block 706 includes determining the configuration information, and the configuration information includes an indication for the UE to continue the activated ML functionality associated with the serving cell as an applicable ML functionality associated with the target cell.
[0113] In some examples, the configuration information includes an indication of one or more network-side additional conditions associated with the target cell for the UE to determine whether to deactivate the activated ML functionality based on the one or more network-side additional conditions associated with the target cell.
[0114] In some examples, the configuration information includes an indication for the UE to reuse the one or more applicable ML functionalities associated with the target cell.
[0115] In some examples, the method 700 further includes sending an indication to the UE to release any applicable ML functionality associated with another cell upon expiration of a timer.
[0116] In some examples, preparing the target cell at block 706 includes determining the configuration information, and the configuration information includes an indication for the UE to switch from the activated ML functionality associated with the serving cell to an applicable ML functionality associated with the target cell.
[0117] In some examples, the applicable ML functionality associated with the target cell is indicated by an identifier of the applicable ML functionality, or one or more network-side additional conditions associated with the target cell from which the applicable ML functionality associated with the target cell is determinable by the UE.
[0118] In some examples, preparing the target cell at block 706 includes determining the configuration information, and the configuration information includes an indication for the UE to deactivate the activated ML functionality associated with the serving cell, and execute the handover without any activated ML functionality.
[0119] In some examples, preparing the target cell at block 706 includes sending a message towards the target cell that includes the applicability information for the one or more applicable ML functionalities associated with the target cell, as shown at block 710 of FIG. 7B. And the method includes receiving an acknowledge message in response to the message that includes the configuration information on the one or more applicable ML functionalities associated with the target cell, as shown at block 712.
[0120] In some examples, the message sent towards the target cell includes an indication of the activated ML functionality, and the configuration information in the acknowledge message includes an indication for the UE to continue the activated ML functionality or switch from the activated functionality to an applicable ML functionality associated with the target cell.
[0121] In some examples, the radio access node is implemented by distributed units (DU) and a central unit (CU), and the handover is an intra-CU handover in which theDUs provide respective cells including the serving cell and the target cell. In some of these examples, the message sent towards the target cell is sent to one of the DUs that provides the target cell, and the acknowledge message is received from the one of the DUs.
[0122] In some examples, the radio access node is implemented by one or more distributed units (DU) and a central unit (CU), and the handover is an inter-CU handover in which the one or more DUs provide respective cells including the serving cell, and the target cell is provided by a second DU of a second radio access node that also includes a second CU. In some of these examples, the message sent towards the target cell is sent to the second CU for the second DU, and the acknowledge message is received from the second CU that received the acknowledge message from the second DU.
[0123] According to example implementations of the present disclosure, a telecommunications system 100 or PLMN 102, and its components such as a UE 110, gNB 206, RU 208, DU 210, 210A, 210B, 210C, and / or CU 212, 212A, 212B, may be implemented by various means. Means for implementing the system and its components may include hardware, firmware, software, or combinations thereof. In some examples, one or more apparatuses may be configured to function as or otherwise implement the system and its components shown and described herein. In examples involving more than one apparatus, the respective apparatuses may be connected to or otherwise in communication with one another in a number of different manners, such as directly or indirectly via a wired or wireless network or the like.
[0124] According to some example implementations, at least some of the method 400 described with respect to FIGS. 4A-4C may be carried out by an apparatus comprising means for performing functions corresponding steps of the method. Similarly, at least some of the method 500 described with respect to FIGS. 5 A and 5B may be carried out by an apparatus comprising means for performing functions corresponding steps of the method. And at least some of the methods 600, 700 described with respect to FIGS. 6A- 6C, and FIGS. 7A and 7B, may be carried out by apparatuses comprising means for performing functions corresponding steps of respective ones of the methods. Examples of a suitable apparatus may a user equipment, user device, user terminal or the like. Otherexamples of a suitable apparatus may include a gNB (e.g., gNB-DU, gNB-CU), ng-eNB or any suitable apparatus, such as a server, host or node.
[0125] FIG. 8 illustrates an apparatus 800 in which means for performing various functions includes hardware, alone or under direction of one or more computer programs from a computer-readable storage medium or other memory, such as computer memory, according to some example implementations of the present disclosure. Generally, an apparatus of example implementations of the present disclosure may comprise, include or be embodied in one or more fixed or portable electronic devices. Examples of suitable electronic devices include a wearable computer, mobile phone, portable computer, desktop computer, workstation computer, server (server computer) or the like. The apparatus may include one or more of each of a number of components such as, for example, processing circuitry 802 connected to computer-readable storage medium or other memory 804.
[0126] The processing circuitry 802 may be composed of one or more processors alone or in combination with one or more computer-readable storage media. The processing circuitry is generally any piece of computer hardware that is capable of processing information such as, for example, data, computer programs and / or other suitable electronic information. The processing circuitry is composed of a collection of electronic circuits some of which may be packaged as an integrated circuit or multiple interconnected integrated circuits (an integrated circuit at times more commonly referred to as a “chip”). The processing circuitry may be configured to execute computer programs, which may be stored onboard the processing circuitry or otherwise stored in the memory 804 (of the same or another apparatus).
[0127] The processing circuitry 802 may be a number of processors, a multi-core processor or some other type of processor, depending on the particular implementation. Further, the processing circuitry may be implemented using a number of heterogeneous processor systems in which a main processor is present with one or more secondary processors on a single chip. As another illustrative example, the processing circuitry may be a symmetric multi-processor system containing multiple processors of the same type. In yet another example, the processing circuitry may be embodied as or otherwise include one or more ASICs, FPGAs or the like. Thus, although the processing circuitry may becapable of executing a computer program to perform one or more functions, the processing circuitry of various examples may be capable of performing one or more functions without the aid of a computer program. In either instance, the processing circuitry may be appropriately programmed to perform functions or operations according to example implementations of the present disclosure.
[0128] The memory 804 is generally any piece of computer hardware that is capable of storing information such as, for example, data, computer programs, instructions 806 (e.g., computer-readable program code) and / or other suitable information either on a temporary basis and / or a permanent basis. The memory may include volatile and / or nonvolatile memory, and may be fixed or removable. Examples of suitable memory include recording media, random access memory (RAM), read-only memory (ROM), a hard drive, a flash memory, a thumb drive, a removable computer diskette, an optical disk or some combination thereof.
[0129] The memory 804 is a non-transitory device capable of storing information. One example of a suitable memory is a computer-readable storage medium, which is distinguishable from a computer-readable transmission medium capable of carrying information from one location to another. Examples of suitable computer-readable transmission media comprise electronic carrier signals, telecommunications signals, or some combination thereof. As used herein, the term “non-transitory” is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM versus ROM). A computer-readable medium as described herein generally refers to a computer-readable storage medium or computer-readable transmission medium. A computer-readable medium is any entity or device capable in which information, such as one or more computer programs or portions thereof, may be stored and carried.
[0130] In addition to the memory 804 (e.g., computer-readable storage medium), the processing circuitry 802 may also be connected to one or more interfaces for displaying, transmitting and / or receiving information. The interfaces may include a communications interface 808 and / or one or more user interfaces, such as a display 810 and / or one or more user input interfaces 812. The communications interface may be configured to transmit and / or receive information, such as to and / or from other apparatus(es),network(s) or the like. The communications interface may be configured to transmit and / or receive information by physical (wired) and / or wireless communications links. Examples of suitable communication interfaces include a network interface controller (NIC), wireless NIC (WNIC) or the like.
[0131] Execution of the instructions 806 by the processing circuitry 802, or storage of the instructions in the memory 804, supports combinations of operations for implementing example implementations of the present disclosure. In this manner, an apparatus 800 may comprise at least one processing circuitry and at least one memory coupled to the at least one processing circuitry, where the at least one processing circuitry is configured to execute instructions stored in the at least one memory. It will also be understood that one or more functions, and combinations of functions, may be implemented by special purpose hardware-based computer systems and / or processing circuitry which perform the specified functions, or combinations of special purpose hardware and program code instructions.
[0132] Some example implementations of the present disclosure may also be carried out in the form of a computer process defined by one or more computer programs or portions thereof. Example implementations of the present disclosure may be carried out by executing at least one portion of a computer program comprising instructions. The computer program may be in source code form, object code form, or in some intermediate form. The computer program may be stored in a computer-readable medium that is readable by a computer, processing circuitry or other suitable apparatus. As indicated above, for example, the computer program may be stored in a memory, such as a computer-readable storage medium. Additionally or alternatively, for example, the computer program may be stored in a computer-readable transmission medium. The coding of software for carrying out example implementations of the present disclosure is well within the scope of a person of ordinary skill in the art.
[0133] As will be appreciated, any suitable instructions may be loaded onto a computer, a processing circuitry or other programmable apparatus from a memory or a computer-readable medium (e.g., computer-readable storage medium, computer-readable transmission medium) to produce a particular machine, such that the particular machine becomes a means for implementing the functions specified herein. The instructions mayalso be stored in a computer-readable medium that can direct a computer, a processing circuitry or other programmable apparatus to function in a particular manner to thereby generate a particular machine or particular article of manufacture. In some examples, the instructions stored in the computer-readable medium may produce an article of manufacture, where the article of manufacture becomes a means for implementing functions described herein. The instructions may be retrieved from a computer-readable medium and loaded into a computer, processing circuitry or other programmable apparatus to configure the computer, processing circuitry or other programmable apparatus to execute operations to be performed on or by the computer, processing circuitry or other programmable apparatus.
[0134] Retrieval, loading and execution of instructions comprising program code instructions may be performed sequentially such that one instruction is retrieved, loaded and executed at a time. In some example implementations, retrieval, loading and / or execution may be performed in parallel such that multiple instructions are retrieved, loaded, and / or executed together. Execution of the program code instructions may produce a computer-implemented process such that the instructions executed by the computer, processing circuitry or other programmable apparatus provide operations for implementing functions described herein.
[0135] As explained above and reiterated below, the present disclosure includes, without limitation, the following example implementations.
[0136] Clause 1. A method performed by a user equipment (UE), the method comprising: receiving a configuration from a serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; reporting to the serving cell applicability information for one or more applicable ML functionalities associated with at least one candidate cell according to the configuration, the at least one candidate cell being a previous serving cell for the UE, and for which the applicability information is stored by the UE; receiving a handover command message from the serving cell that includes a configuration for a target cell among the at least one candidate cell, the configuration including configuration information on the one or more applicable ML functionalities associated with the target cell; and executing a handover of the UE from the serving cellto the target cell triggered by the handover command message and based on the configuration including the configuration information.
[0137] Clause 2. The method of clause 1, wherein the applicability information for the one or more applicable ML functionalities associated with the at least one candidate cell is reported in a measurement report of measurements performed by the UE on one or more candidate cells including the at least one candidate cell.
[0138] Clause 3. The method of clause 1 or clause 2, wherein the configuration information includes an indication for the UE to continue the activated ML functionality associated with the serving cell as an applicable ML functionality associated with the target cell.
[0139] Clause 4. The method of any of clauses 1 to 3, wherein the configuration information includes an indication of one or more network-side additional conditions associated with the target cell, and wherein the method further comprises determining whether to deactivate the activated ML functionality based on the one or more networkside additional conditions associated with the target cell.
[0140] Clause 5. The method of any of clauses 1 to 4, wherein the configuration information includes an indication for the UE to reuse the one or more applicable ML functionalities associated with the target cell.
[0141] Clause 6. The method of any of clauses 1 to 5, wherein the method further comprises receiving an indication from the serving cell to release any applicable ML functionality associated with another cell upon expiration of a timer.
[0142] Clause 7. The method of any of clauses 1 to 6, wherein the configuration information includes an indication for the UE to switch from the activated ML functionality associated with the serving cell to an applicable ML functionality associated with the target cell.
[0143] Clause 8. The method of clause 7, wherein the applicable ML functionality associated with the target cell is indicated by an i dentifier of the applicable ML functionality, or one or more network-side additional conditions associated with the target cell from which the applicable ML functionality associated with the target cell is determinable by the UE.
[0144] Clause 9. The method of clause 7 or clause 8, wherein executing the handover comprises: deactivating the activated ML functionality associated with the serving cell; and activating the applicable ML functionality associated with the target cell.
[0145] Clause 10. The method of any of clauses 1 to 9, wherein the configuration information includes an indication for the UE to deactivate the activated ML functionality associated with the serving cell, and executing the handover comprises: deactivating the activated ML functionality associated with the serving cell; and executing the handover without any activated ML functionality.
[0146] Clause 11. The method of any of clauses 1 to 10, wherein the applicability information reported to the serving cell includes at least one non-applicable ML functionality, and the configuration received in the handover command excludes configuration information on the at least one non-applicable ML functionality.
[0147] Clause 12. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to perform the method of any of clauses 1 to 11.
[0148] Clause 13. An apparatus comprising means for performing the method of any of clauses 1 to 11.
[0149] Clause 14. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 1 to 11.
[0150] Clause 15. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 1 to 11.
[0151] Clause 16. A computer program comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 1 to 11.
[0152] Clause 17. A method performed by a radio access node providing a serving cell for a user equipment (UE), the method comprising: sending a configuration to the UE from the serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the servingcell; receiving from the UE applicability information for one or more applicable ML functionalities associated with at least one candidate cell according to the configuration, the at least one candidate cell being a previous serving cell for the UE, and for which the applicability information is stored by the UE; preparing a target cell among the at least one candidate cell for a handover of the UE, wherein a configuration for the target cell is determined, and the configuration includes configuration information on the one or more applicable ML functionalities associated with the target cell; and sending a handover command message to the UE that includes the configuration for the target cell to trigger the handover of the UE to the target cell based on the configuration information.
[0153] Clause 18. The method of clause 17, wherein the applicability information for the one or more applicable ML functionalities associated with the at least one candidate cell is received in a measurement report of measurements performed by the UE on one or more candidate cells including the at least one candidate cell.
[0154] Clause 19. The method of clause 17 or clause 18, wherein preparing the target cell includes determining the configuration information, and the configuration information includes an indication for the UE to continue the activated ML functionality associated with the serving cell as an applicable ML functionality associated with the target cell.
[0155] Clause 20. The method of any of clauses 17 to 19, wherein the configuration information includes an indication of one or more network-side additional conditions associated with the target cell for the UE to determine whether to deactivate the activated ML functionality based on the one or more network-side additional conditions associated with the target cell
[0156] Clause 21. The method of any of clauses 17 to 20, wherein the configuration information includes an indication for the UE to reuse the one or more applicable ML functionalities associated with the target cell.
[0157] Clause 22. The method of any of clauses 17 to 21, wherein the method further comprises sending an indication to the UE to release any applicable ML functionality associated with another cell upon expiration of a timer.
[0158] Clause 23. The method of any of clauses 17 to 22, wherein preparing the target cell includes determining the configuration information, and the configurationinformation includes an indication for the UE to switch from the activated ML functionality associated with the serving cell to an applicable ML functionality associated with the target cell.
[0159] Clause 24. The method of clause 23, wherein the applicable ML functionality associated with the target cell is indicated by an identifier of the applicable ML functionality, or one or more network-side additional conditions associated with the target cell from which the applicable ML functionality associated with the target cell is determinable by the UE.
[0160] Clause 25. The method of any of clauses 17 to 24, wherein preparing the target cell includes determining the configuration information, and the configuration information includes an indication for the UE to deactivate the activated ML functionality associated with the serving cell, and execute the handover without any activated ML functionality.
[0161] Clause 26. The method of any of clauses 17 to 25, wherein the applicability information received from the UE includes at least one non-applicable ML functionality, and the configuration determined for the target cell excludes configuration information on the at least one non-applicable ML functionality.
[0162] Clause 27. The method of any of clauses 17 to 26, wherein preparing the target cell comprises: sending a message towards the target cell that includes the applicability information for the one or more applicable ML functionalities associated with the target cell; and receiving an acknowledge message in response to the message that includes the configuration information on the one or more applicable ML functionalities associated with the target cell.
[0163] Clause 28. The method of clause 27, wherein the message sent towards the target cell includes an indication of the activated ML functionality, and the configuration information in the acknowledge message includes an indication for the UE to continue the activated ML functionality or switch from the activated functionality to an applicable ML functionality associated with the target cell.
[0164] Clause 29. The method of clause 27 or clause 28, wherein the radio access node is implemented by distributed units (DU) and a central unit (CU), and the handover is an intra-CU handover in which the DUs provide respective cells including the servingcell and the target cell, and wherein the message sent towards the target cell is sent to one of the DUs that provides the target cell, and the acknowledge message is received from the one of the DUs.
[0165] Clause 30. The method of any of clauses 27 to 29, wherein the radio access node is implemented by one or more distributed units (DU) and a central unit (CU), and the handover is an inter-CU handover in which the one or more DUs provide respective cells including the serving cell, and the target cell is provided by a second DU of a second radio access node that also includes a second CU, and wherein the message sent towards the target cell is sent to the second CU for the second DU, and the acknowledge message is received from the second CU that received the acknowledge message from the second DU.
[0166] Clause 31. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to perform the method of any of clauses 17 to 30.
[0167] Clause 32. An apparatus comprising means for performing the method of any of clauses 17 to 30.
[0168] Clause 33. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 17 to 30.
[0169] Clause 34. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 17 to 30.
[0170] Clause 35. A computer program comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 17 to 30.
[0171] Clause 36. A method performed by a user equipment (UE), the method comprising: receiving a configuration from a serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; sending to the serving cell a measurement report of measurements on one or more candidate cells triggered by a determination that ameasurement reporting event of the configuration is satisfied, wherein the measurement report includes applicability information for one or more applicable ML functionalities associated with at least one candidate cell among the one or more candidate cells; receiving a handover command message from the serving cell that includes a configuration for a target cell among the at least one candidate cell for a handover of the UE decided by the serving cell based on the measurements, the configuration including configuration information on the one or more applicable ML functionalities associated with the target cell; executing a handover of the UE from the serving cell to the target cell triggered by the handover command message and based on the configuration.
[0172] Clause 37. The method of clause 36, wherein the configuration information includes an indication for the UE to continue the activated ML functionality associated with the serving cell as an applicable ML functionality associated with the target cell.
[0173] Clause 38. The method of clause 36 or clause 37, wherein the configuration information includes an indication of one or more network-side additional conditions associated with the target cell, and wherein the method further comprises determining whether to deactivate the activated ML functionality based on the one or more networkside additional conditions associated with the target cell.
[0174] Clause 39. The method of any of clauses 36 to 38, wherein the configuration information includes an indication for the UE to reuse the one or more applicable ML functionalities associated with the target cell.
[0175] Clause 40. The method of any of clauses 36 to 39, wherein the method further comprises receiving an indication from the serving cell to release any applicable ML functionality associated with another cell upon expiration of a timer.
[0176] Clause 41. The method of any of clauses 36 to 40, wherein the configuration information includes an indication for the UE to switch from the activated ML functionality associated with the serving cell to an applicable ML functionality associated with the target cell.
[0177] Clause 42. The method of clause 41, wherein the applicable ML functionality associated with the target cell is indicated by an identifier of the applicable ML functionality.
[0178] Clause 43. The method of clause 41 or clause 42, wherein the applicable ML functionality associated with the target cell is indicated by one or more network-side additional conditions associated with the target cell, and wherein the method further comprises determining the applicable ML functionality associated with the target cell based on the one or more network-side additional conditions, one or more UE-side additional conditions, and ML model availability in the UE.
[0179] Clause 44. The method of any of clauses 41 to 43, wherein executing the handover comprises: deactivating the activated ML functionality associated with the serving cell; and activating the applicable ML functionality associated with the target cell.
[0180] Clause 45. The method of any of clauses 36 to 44, wherein the configuration information includes an indication for the UE to deactivate the activated ML functionality associated with the serving cell, and executing the handover comprises: deactivating the activated ML functionality associated with the serving cell; and executing the handover without any activated ML functionality.
[0181] Clause 46. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to perform the method of any of clauses 36 to 45.
[0182] Clause 47. An apparatus comprising means for performing the method of any of clauses 36 to 45.
[0183] Clause 48. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 36 to 45.
[0184] Clause 49. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 36 to 45.
[0185] Clause 50. A computer program comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 36 to 45.
[0186] Clause 51. A method performed by a radio access node providing a serving cell for a user equipment (UE), the method comprising: sending a configuration to the UE from the serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; receiving from the UE a measurement report of measurements on one or more candidate cells triggered by a determination that a measurement reporting event of the configuration is satisfied, wherein the measurement report includes applicability information for one or more applicable ML functionalities associated with at least one candidate cell among the one or more candidate cells; preparing a target cell among the at least one candidate cell for a handover of the UE, wherein a configuration for the target cell is determined, and the configuration includes configuration information on the one or more applicable ML functionalities associated with the target cell; and sending a handover command message to the UE that includes the configuration for the target cell to trigger the handover of the UE to the target cell based on the configuration information.
[0187] Clause 52. The method of clause 51, wherein preparing the target cell includes determining the configuration information, and the configuration information includes an indication for the UE to continue the activated ML functionality associated with the serving cell as an applicable ML functionality associated with the target cell.
[0188] Clause 53. The method of clause 51 or clause 52, wherein the configuration information includes an indication of one or more network-side additional conditions associated with the target cell for the UE to determine whether to deactivate the activated ML functionality based on the one or more network-side additional conditions associated with the target cell.
[0189] Clause 54. The method of any of clauses 51 to 53, wherein the configuration information includes an indication for the UE to reuse the one or more applicable ML functionalities associated with the target cell.
[0190] Clause 55. The method of any of clauses 51 to 54, wherein the method further comprises sending an indication to the UE to release any applicable ML functionality associated with another cell upon expiration of a timer.
[0191] Clause 56. The method of any of clauses 51 to 55, wherein preparing the target cell includes determining the configuration information, and the configuration information includes an indication for the UE to switch from the activated ML functionality associated with the serving cell to an applicable ML functionality associated with the target cell.
[0192] Clause 57. The method of clause 56, wherein the applicable ML functionality associated with the target cell is indicated by an identifier of the applicable ML functionality, or one or more network-side additional conditions associated with the target cell from which the applicable ML functionality associated with the target cell is determinable by the UE.
[0193] Clause 58. The method of any of clauses 51 to 57, wherein preparing the target cell includes determining the configuration information, and the configuration information includes an indication for the UE to deactivate the activated ML functionality associated with the serving cell, and execute the handover without any activated ML functionality.
[0194] Clause 59. The method of any of clauses 51 to 58, wherein preparing the target cell comprises: sending a message towards the target cell that includes the applicability information for the one or more applicable ML functionalities associated with the target cell; and receiving an acknowledge message in response to the message that includes the configuration information on the one or more applicable ML functionalities associated with the target cell.
[0195] Clause 60. The method of clause 59, wherein the message sent towards the target cell includes an indication of the activated ML functionality, and the configuration information in the acknowledge message includes an indication for the UE to continue the activated ML functionality or switch from the activated functionality to an applicable ML functionality associated with the target cell.
[0196] Clause 61. The method of clause 59 or clause 60, wherein the radio access node is implemented by distributed units (DU) and a central unit (CU), and the handover is an intra-CU handover in which the DUs provide respective cells including the serving cell and the target cell, and wherein the message sent towards the target cell is sent to oneof the DUs that provides the target cell, and the acknowledge message is received from the one of the DUs.
[0197] Clause 62. The method of any of clauses 59 to 61, wherein the radio access node is implemented by one or more distributed units (DU) and a central unit (CU), and the handover is an inter-CU handover in which the one or more DUs provide respective cells including the serving cell, and the target cell is provided by a second DU of a second radio access node that also includes a second CU, and wherein the message sent towards the target cell is sent to the second CU for the second DU, and the acknowledge message is received from the second CU that received the acknowledge message from the second DU.
[0198] Clause 63. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to perform the method of any of clauses 51 to 62.
[0199] Clause 64. An apparatus comprising means for performing the method of any of clauses 51 to 62.
[0200] Clause 65. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 51 to 62.
[0201] Clause 66. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 51 to 62.
[0202] Clause 67. A computer program comprising instructions that, in response to execution by at least one processing circuitry, causes an apparatus to perform the method of any of clauses 51 to 62.
[0203] Many modifications and other implementations of the disclosure set forth herein will come to mind to one skilled in the art to which the disclosure pertains having the benefit of the teachings presented in the foregoing description and the associated figures. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Moreover, although theforegoing description and the associated figures describe example implementations in the context of certain example combinations of elements and / or functions, it should be appreciated that different combinations of elements and / or functions may be provided by alternative implementations without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and / or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Claims
WHAT IS CLAIMED IS:
1. An apparatus implementing a user equipment (UE), the apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to at least: receive a configuration from a serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; report to the serving cell applicability information for one or more applicable ML functionalities associated with at least one candidate cell according to the configuration, the at least one candidate cell being a previous serving cell for the UE, and for which the applicability information is stored by the UE; receive a handover command message from the serving cell that includes a configuration for a target cell among the at least one candidate cell, the configuration including configuration information on the one or more applicable ML functionalities associated with the target cell; and execute a handover of the UE from the serving cell to the target cell triggered by the handover command message and based on the configuration including the configuration information.
2. The apparatus of claim 1, wherein the applicability information for the one or more applicable ML functionalities associated with the at least one candidate cell is reported in a measurement report of measurements performed by the UE on one or more candidate cells including the at least one candidate cell.
3. The apparatus of claim 1, wherein the configuration information includes an indication for the UE to continue the activated ML functionality associated with the serving cell as an applicable ML functionality associated with the target cell.
4. The apparatus of claim 1, wherein the configuration information includes an indication of one or more network-side additional conditions associated with the target cell, and wherein the at least one processing circuitry is configured to execute the instructions to cause the apparatus to further determine whether to deactivate the activated ML functionality based on the one or more network-side additional conditions associated with the target cell.
5. The apparatus of claim 1, wherein the configuration information includes an indication for the UE to reuse the one or more applicable ML functionalities associated with the target cell.
6. The apparatus of claim 1, wherein the at least one processing circuitry is configured to execute the instructions to cause the apparatus to further receive an indication from the serving cell to release any applicable ML functionality associated with another cell upon expiration of a timer.
7. The apparatus of claim 1, wherein the configuration information includes an indication for the UE to switch from the activated ML functionality associated with the serving cell to an applicable ML functionality associated with the target cell.
8. The apparatus of claim 7, wherein the applicable ML functionality associated with the target cell is indicated by an identifier of the applicable ML functionality, or one or more network-side additional conditions associated with the target cell from which the applicable ML functionality associated with the target cell is determinable by the UE.
9. The apparatus of claim 7, wherein the apparatus caused to execute the handover includes the apparatus caused to: deactivate the activated ML functionality associated with the serving cell; and activate the applicable ML functionality associated with the target cell.-48-10. The apparatus of claim 1, wherein the configuration information includes an indication for the UE to deactivate the activated ML functionality associated with the serving cell, and the apparatus caused to execute the handover includes the apparatus caused to: deactivate the activated ML functionality associated with the serving cell; and execute the handover without any activated ML functionality.
11. The apparatus of claim 1, wherein the applicability information reported to the serving cell includes at least one non-applicable ML functionality, and the configuration received in the handover command excludes configuration information on the at least one non-applicable ML functionality.
12. An apparatus implementing a radio access node providing a serving cell for a user equipment (UE), the apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory, and execute the instructions to cause the apparatus to at least: send a configuration to the UE from the serving cell for which the UE has an activated machine learning (ML) functionality of one or more applicable ML functionalities associated with the serving cell; receive from the UE applicability information for one or more applicable ML functionalities associated with at least one candidate cell according to the configuration, the at least one candidate cell being a previous serving cell for the UE, and for which the applicability information is stored by the UE; prepare a target cell among the at least one candidate cell for a handover of the UE, wherein a configuration for the target cell is determined, and the configuration includes configuration information on the one or more applicable ML functionalities associated with the target cell; and-49-send a handover command message to the UE that includes the configuration for the target cell to trigger the handover of the UE to the target cell based on the configuration information.
13. The apparatus of claim 12, wherein the applicability information for the one or more applicable ML functionalities associated with the at least one candidate cell is received in a measurement report of measurements performed by the UE on one or more candidate cells including the at least one candidate cell.
14. The apparatus of claim 12, wherein the apparatus caused to prepare the target cell includes the apparatus caused to determine the configuration information, and the configuration information includes an indication for the UE to continue the activated ML functionality associated with the serving cell as an applicable ML functionality associated with the target cell.
15. The apparatus of claim 12, wherein the configuration information includes an indication of one or more network-side additional conditions associated with the target cell for the UE to determine whether to deactivate the activated ML functionality based on the one or more network-side additional conditions associated with the target cell.
16. The apparatus of claim 12, wherein the configuration information includes an indication for the UE to reuse the one or more applicable ML functionalities associated with the target cell.
17. The apparatus of claim 12, wherein the at least one processing circuitry is configured to execute the instructions to cause the apparatus to further send an indication to the UE to release any applicable ML functionality associated with another cell upon expiration of a timer.
18. The apparatus of claim 12, wherein the apparatus caused to prepare the target cell includes the apparatus caused to determine the configuration information, and-50-the configuration information includes an indication for the UE to switch from the activated ML functionality associated with the serving cell to an applicable ML functionality associated with the target cell.
19. The apparatus of claim 18, wherein the applicable ML functionality associated with the target cell is indicated by an identifier of the applicable ML functionality, or one or more network-side additional conditions associated with the target cell from which the applicable ML functionality associated with the target cell is determinable by the UE.
20. The apparatus of claim 12, wherein the apparatus caused to prepare the target cell includes the apparatus caused to determine the configuration information, and the configuration information includes an indication for the UE to deactivate the activated ML functionality associated with the serving cell, and execute the handover without any activated ML functionality.
21. The apparatus of claim 12, wherein the applicability information received from the UE includes at least one non-applicable ML functionality, and the configuration determined for the target cell excludes configuration information on the at least one non- applicable ML functionality.
22. The apparatus of claim 12, wherein the apparatus caused to prepare the target cell includes the apparatus caused to: send a message towards the target cell that includes the applicability information for the one or more applicable ML functionalities associated with the target cell; and receive an acknowledge message in response to the message that includes the configuration information on the one or more applicable ML functionalities associated with the target cell.
23. The apparatus of claim 22, wherein the message sent towards the target cell includes an indication of the activated ML functionality, and the configurationinformation in the acknowledge message includes an indication for the UE to continue the activated ML functionality or switch from the activated functionality to an applicable ML functionality associated with the target cell.
24. The apparatus of claim 22, wherein the radio access node is implemented by distributed units (DU) and a central unit (CU), and the handover is an intra-CU handover in which the DUs provide respective cells including the serving cell and the target cell, and wherein the message sent towards the target cell is sent to one of the DUs that provides the target cell, and the acknowledge message is received from the one of the DUs.
25. The apparatus of claim 22, wherein the radio access node is implemented by one or more distributed units (DU) and a central unit (CU), and the handover is an inter-CU handover in which the one or more DUs provide respective cells including the serving cell, and the target cell is provided by a second DU of a second radio access node that also includes a second CU, and wherein the message sent towards the target cell is sent to the second CU for the second DU, and the acknowledge message is received from the second CU that received the acknowledge message from the second DU.
Citation Information
Patent Citations
Communication method and apparatus, terminal, and network device
US20240267800A1
Communication system for machine learning metadata
WO2022034259A1