AIML functionality during LTM continues

Abstract

Various embodiments of this disclosure relate to the continuation of AIML functionality during LTM. According to aspects of this disclosure, a method includes: a user equipment (UE) transmitting a message indicating UE capability information to a network node supporting a Layer 2 protocol of a radio access network, the capability information relating to stored prior applicability information for a set of lower-layer mobility candidate cells; the UE receiving a signal from the network node including network-side conditions; the UE transmitting a message to the network node including information related to artificial intelligence and machine learning (AIML) functions / models / features / configuration and UE assistance information (UAI); and the UE receiving subsequent mobility configuration from the network node.

Description

Technical Field

[0001] Various example embodiments generally relate to supporting a mobility (LTM) process triggered by a layer 1 / layer 2 (L1 / L2), and more specifically, to apparatus, methods, and computer program products that support the continuation of artificial intelligence / machine learning (AI / ML) functionality within an LTM process. Background Technology

[0002] Wireless networks offer significant advantages to user mobility. The ability to maintain connectivity while on the move not only benefits the user but also contributes to greater efficiency and productivity for society as a whole. As expectations for connection reliability, data speed, and low power consumption become more demanding, the technologies used in wireless networks must keep pace. Therefore, there is a sustained interest in improving wireless networking technologies. Summary of the Invention

[0003] According to various aspects of this disclosure, a method includes: a user equipment (UE) transmitting a message indicating UE capability information to a network node supporting a Layer 2 protocol of a radio access network, the capability information relating to stored prior applicability information for a set of lower-layer mobility candidate cells; the UE receiving a signal from the network node, wherein the signal includes network-side conditions; the UE transmitting a message to the network node, the message including information related to artificial intelligence and machine learning (AIML) functions / models / features / configurations and UE assistance information (UAI); and the UE receiving subsequent mobility configuration from the network node.

[0004] According to various aspects of this disclosure, a method includes: a user equipment (UE) receiving a message indicating UE capability information from a first network node supporting a Layer 2 protocol of a radio access network, the capability information relating to stored prior applicability information for a set of lower-layer mobility candidate cells; the first network node forwarding the message indicating UE capability information to a second network node supporting at least one of a Central Cell Control Plane (CU-CP) function or a Layer 3 protocol of a radio access network; the first network node transmitting a signal to the UE, wherein the signal includes network-side conditions associated with serving cell configuration and / or supported functions; the first network node receiving a message from the UE, the message including information related to artificial intelligence and machine learning (AIML) functions / models / features / configurations and UE assistance information (UAI); the first network node forwarding the message to the second network node; and the second network node transmitting subsequent mobility configuration to the UE.

[0005] The independent claims provide the subject matter for several aspects. Additional aspects are defined in the dependent claims. Attached Figure Description

[0006] Some exemplary embodiments will now be described with reference to the accompanying drawings.

[0007] Figure 1 This is an illustration of an example embodiment of wireless networking between a network system and a user equipment (UE) according to an aspect of this disclosure; Figure 2 This is a diagram illustrating an example component of a network system according to an aspect of this disclosure; Figure 3A and 3B This is an illustration of an example of an operation for signaling UE capability information to the Serving Distributed Unit (S-DU), Serving Central Unit (S-CU), and candidate cells, according to one aspect of this disclosure; Figures 4A to 4D This is an illustration of an example of an operation for signaling UE capability information to the S-DU, S-CU and candidate cells, according to one aspect of this disclosure; Figure 5A and 5B This is an illustration illustrating an example of an operation for signaling UE capability information to the S-DU, S-CU, and candidate cells according to one aspect of this disclosure; and Figure 6 This is an illustration of an example block diagram of a UE or radio access network node (e.g., gNB) according to one aspect of this disclosure. Detailed Implementation

[0008] This disclosure relates to products supporting Layer 1 / Layer 2 (L1 / L2) triggered Mobility Transaction (LTM) procedures, and more specifically, to products supporting the continuation of Artificial Intelligence / Machine Learning (AI / ML) functions within an LTM procedure. When LTM is configured, a UE can perform handovers between different cells belonging to different network nodes (e.g., gNBs). This disclosure relates to systems and methods for informing a UE to continue configured AI / ML functions across different cells while minimizing Radio Resource Control (RRC) level involvement.

[0009] In the following description, certain specific details are set forth in order to provide a thorough understanding of the disclosed aspects. However, those skilled in the art will recognize that the aspects can be practiced without one or more of these specific details or using other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring the description of the aspects.

[0010] Throughout this specification, the reference to "an aspect" or "aspect" means that a particular feature, structure, or characteristic described in connection with that aspect is included in at least one aspect. Therefore, the phrases "in an aspect" or "in one respect" appearing in various places throughout this specification do not necessarily refer to the same aspect. Furthermore, a particular feature, structure, or characteristic may be combined in one or more aspects in any suitable manner.

[0011] The embodiments described in this disclosure can be implemented in wireless networking devices, such as, but not limited to, devices utilizing Global Microwave Access Interoperability (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE, Enhanced LTE (eLTE), 5G New Radio (5GNR), Advanced 5G, 6G (and above), and 802.11ax (Wi-Fi 6), and other wireless networking systems. The term "eLTE" here refers to LTE evolution connected to a 5G core. LTE is also referred to as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN).

[0012] This disclosure may use the term "serving network device" to refer to a network node or network device (or part thereof) serving a UE. As used herein, the terms "transmitting toward," "transmitting to," "receiving from," and "cooperating with" (and variations thereof) include communication that may or may not involve communication through one or more intermediate devices or nodes. The term "acquiring" (and variations thereof) includes acquiring in a first instance or re-acquiring after a first instance. The term "connection" may mean a physical connection or a logical connection.

[0013] This disclosure uses 5G NR as an example of a wireless network, and may use smartphones and / or extended reality headsets as examples of UEs. It is intended and should be understood that such examples are merely illustrative, and this disclosure applies to other wireless networks and user equipment.

[0014] Figure 1This is a diagram illustrating an example of wireless networking between network system 100 and user equipment (UE) 150. Network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network devices 130 (e.g., test equipment). Network node 120 will be described in more detail below. As used herein, the term "network apparatus" may refer to any component of network system 100, such as server 110, network node 120, network apparatus 130, any of the foregoing components(s), and / or any of the other components(s) of network system 100. Examples of network apparatus include, but are not limited to, apparatuses for implementing various aspects of 5G NR. This disclosure describes embodiments related to 5G NR and embodiments relating to aspects defined by the 3rd Generation Partnership Project (3GPP). However, it is contemplated that embodiments related to other wireless network technologies are included within the scope of this disclosure.

[0015] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as a gNB) may include, for example, a node that provides New Radio (NR) user plane and control plane protocol terminals toward the UE and is connected to the 5G core (5GC) via an NG interface, for example, according to Section 3.2 of 3GPP TS 38.300 V 16.6.0 (2021-06), which is incorporated herein by reference.

[0016] gNB supports various protocol layers, such as Layer 1 (L1) - the physical layer, Layer 2 (L2) and Layer 3 (L3).

[0017] NR's Layer 2 (L2) is divided into the following sublayers: Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), among which, for example: The physical layer provides a transmission channel to the MAC sublayer; The MAC sublayer provides logical channels to the RLC sublayer; The RLC sublayer provides RLC channels to the PDCP sublayer; The PDCP sublayer provides radio bearers to the SDAP sublayer; The SDAP sublayer provides Quality of Service (QoS) flows to 5GC; The control channels include the Broadcast Control Channel (BCCH) and the Physical Control Channel (PCCH).

[0018] Layer 3 (L3) includes, for example, the Radio Resource Control (RRC) according to Section 6 of 3GPP TS 38.300 V 16.6.0 (2021-06), which is incorporated herein by reference.

[0019] The gNB Central Unit (gNB-CU) includes, for example, logical nodes that administer, for example, the gNB's Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols, or the en-gNB's RRC and PDCP protocols, and control the operation of one or more gNB Distributed Units (gNB-DUs). The gNB-CU terminates the F1 interface connected to the gNB-DU. The gNB-CU may also be referred to herein as a CU, Central Unit, Centralized Unit, or Control Unit.

[0020] A gNB Distributed Unit (gNB-DU) includes, for example, a logical node that carries, for example, the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layers of the gNB or en-gNB, and its operation is partially controlled by the gNB-CU. A gNB-DU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU. The gNB-DU may also be referred to herein as a DU or Distributed Unit.

[0021] The gNB-CU-Control Plane (gNB-CU-CP) includes, for example, logical nodes that carry, for example, the RRC and control plane portions of the PDCP protocol for the gNB-CU of the en-gNB or gNB. The gNB-CU-CP terminates the E1 interface connected to the gNB-CU-User Plane (gNB-CU-UP) and the F1-C interface connected to the gNB-DU.

[0022] The gNB-CU-User Plane (gNB-CU-UP) includes, for example, logical nodes that carry, for example, the user plane portion of the PDCP protocol for the gNB-CU of the en-gNB, and the user plane portions of the PDCP and SDAP protocols for the gNB-CU of the gNB. The gNB-CU-UP terminates the E1 interface connected to the gNB-CU-CP and the F1-U interface connected to the gNB-DU, for example, according to Section 3.1 of 3GPP TS 38.401 V 16.6.0 (2021-07), which is incorporated herein by reference.

[0023] As used herein, the term "network node" may refer to any one or any combination of gNB, gNB-CU, gNB-DU, gNB-CU-CP, or gNB-CU-UP.

[0024] RAN (Radio Access Network) nodes or network nodes (such as, for example, gNB, gNB-CU, or gNB-DU, or portions thereof) can be implemented using, for example, means having at least one processor and / or at least one memory having processor-readable instructions (“programs”) configured to support and / or provide and / or process functions and / or features associated with the CU and / or DU, and / or at least one protocol (sub)layer (e.g., layer 2 and / or layer 3) of the RAN (Radio Access Network). Different functional splits between central and distributed units are possible. The following will combine... Figure 6 Examples describing such devices and components.

[0025] The gNB-CU and gNB-DU portions can be co-located or physically separated, for example. The gNB-DU can even be further divided into, for example, two parts, one including processing equipment and the other including an antenna. The Central Unit (CU) can also be referred to as a Baseband Unit / Radio Equipment Controller / Cloud-RAN / Virtual-RAN (BBU / REC / C-RAN / V-RAN), Open-RAN (O-RAN), or a portion thereof. The Distributed Unit (DU) can also be referred to as a Remote Radio Head / Remote Radio Unit / Radio Equipment / Radio Unit (RRH / RRU / RE / RU), or a portion thereof. In the various example embodiments of this disclosure below, a network node supporting at least one of the Central Unit functions or Layer 3 protocols of a radio access network can be, for example, a gNB-CU. Similarly, a network node supporting at least one of the Distributed Unit functions or Layer 2 protocols of a radio access network can be, for example, a gNB-DU.

[0026] A gNB-CU can support one or more gNB-DUs. A gNB-DU can support one or more cells, and therefore can support serving cells for user equipment (UE), or candidate cells for handover, dual connectivity and / or carrier aggregation and other procedures.

[0027] User equipment (UE) 150 may be or include wireless or mobile devices, devices having a radio interface for interacting with a RAN (Radio Access Network), smartphones, in-vehicle devices, IoT devices, or M2M devices, and other types of user equipment. Such a UE 150 may include: at least one processor; and at least one memory; the at least one memory includes program code, wherein the at least one memory and the computer program code are configured, together with the at least one processor, to cause the device to perform at least certain operations, such as, for example, an RRC connection to the RAN. Figure 6Examples of components describing a UE are provided below. In an embodiment, UE 150 may be configured to generate messages (e.g., including a cell ID) to be transmitted via radio to the RAN (e.g., to reach and communicate with the serving cell). In an embodiment, UE 150 may generate, transmit, and receive RRC messages including one or more RRC PDUs (Packet Data Units). Those skilled in the art will understand the RRC protocol and other processes that the UE may perform.

[0028] Continue to refer to Figure 1 In an example of a 5G NR network, network system 100 provides one or more cells that define the coverage area of ​​network system 100. As described above, network system 100 may include a gNB of the 5G NR network, or may include any other means configured to control radio communications and manage radio resources within the cells. As used herein, the term "resource" may refer to radio resources such as resource blocks (RBs), physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. In embodiments, network node 120 may be referred to as a base station.

[0029] Figure 1 Examples are provided, and only network system 100 and UE 150 are illustrated. Those skilled in the art will understand that network system 100 includes... Figure 1 Components not shown in the diagram, and it will be understood that other user equipment can communicate with network system 100.

[0030] Figure 2 yes Figure 1 A block diagram of example components of network system 100. A 5G NR network can be described as an example of network system 100, and the aspects described below should also be applicable to other types of network systems. The network system can be configured according to... Figure 1 The signals and connections shown operate to enable UE 150 to communicate with network system 100 via radio access network (RAN) 225. Additionally, the network system can be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless otherwise stated, the terms “component,” “function,” and “service” are used interchangeably herein and can refer to instructions executed by and implemented by one or more processors.

[0031] The following describes example functionality of the components. This example functionality is merely illustrative, and it should be understood that additional operations and functions can be performed by the components described herein. Furthermore, connections between components can be virtual connections based on service interfaces, allowing any component to communicate with any other component. In this way, any component can act as a service "producer" for any other component that is a service "consumer," providing services for network functions.

[0032] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an Authentication Server Function (AUSF) 211, an Access and Mobility Management Function (AMF) 212, and a Session Management Function (SMF) 213. The core network 210 may also include a Network Slice Selection Function (NSSF) 214, a Network Open Function (NEF) 215, a Network Repository Function (NRF) 216, and a Unified Data Management Function (UDM) 217, which may include a Unified Data Repository (UDR) 224.

[0033] Additional components and functions of the core network 210 may include application functions (AF) 218, policy control functions (PCF) 219, network data analysis functions (NWDAF) 220, analytical data repository functions (ADRF) 221, management data analysis functions (MDAF) 222, and operation and management functions (OAM) 223.

[0034] The user plane includes UE 150, Radio Access Network (RAN) 225, User Plane Function (UPF) 226, and Data Network (DN) 227. RAN 225 may include a combination of Figure 1 The RAN 225 describes one or more components, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connectivity for data transmitted over the RAN 225. For example, the UPF 226 identifies services from service providers, internet access, and third-party services.

[0035] AMF 212 handles connectivity and mobility tasks. AUSF 211 receives authentication requests from AMF 212 and interacts with UDM 217 to authenticate and verify network responses for determining successful authentication. SMF 213 performs Packet Data Unit (PDU) session management and manages session context with UPF 226.

[0036] NSSF 214 can select a Network Slice Instance (NSI) and determine the allowed Network Slice Selection Auxiliary Information (NSSAI). This selection and determination are used to configure AMF 212 to provide services to UE 150. NEF 215 ensures third-party access to network services to create private network services. NRF 216 acts as a repository for storing network functions to allow functions to register and discover each other.

[0037] UDM 217 generates authentication vectors for use by AUSF 211 and AMF 212 and provides user identity processing. UDM 217 can be connected to UDR 224, which stores data associated with authentication, applications, etc. AF 218 provides application services (e.g., streaming services) to users. PCF 219 provides policy control functions. For example, PCF 219 can assist in network slicing and mobility management, as well as provide Quality of Service (QoS) and accounting functions.

[0038] NWDAF 220 collects data (e.g., from UE 150 and network systems) to perform network analytics and provide insights into the capabilities that leverage analytics when providing services. ADRF 221 allows consumers to store, retrieve, and remove data and perform analytics. MDAF 222 provides additional data analytics services for network functions. OAM 223 provides provisioning and management processing capabilities to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0039] Figure 2 These are merely examples of components of a network system, and variations are contemplated within the scope of this disclosure. In embodiments, the network system may include... Figure 2 Other components not shown. In embodiments, the network system may not include... Figure 2 Each component is shown. In an embodiment, components and connections can be used with... Figure 2 Different connections are implemented as shown. These and other embodiments are considered to be within the scope of this disclosure.

[0040] Figure 3A and 3B This is a flowchart illustrating a method for notifying a user equipment (UE) to continue configured AI / ML functions across different cells, wherein each cell is configured with AI / ML functions independently. Figure 3A and 3B This is a diagram illustrating example operations for signaling UE capability information to the Serving Distributed Unit (S-DU), Serving Central Unit (S-CU), and candidate cells. These operations are performed by... Figure 3A and 3BThe components shown at the top perform the operation, including the UE, S-DU, S-CU, and candidate cells. Candidate cells can be a second distributed unit (DU2), a target central unit (CU2), and a third distributed unit (DU3). S-DU and DU2 can belong to the S-CU, and CU2 can control DU3. Such components can be, for example, combined... Figure 1 and Figure 2 The same component described above or otherwise.

[0041] At operation 301, the UE transmits and stores the capability related to the suitability information for LTM candidate cells, and the S-DU receives this capability.

[0042] Applicability is a framework used for AIML purposes that aligns assumptions on both the UE and NW sides with the model being deployed. For example, the network can send the UE an AIML function / model / feature / configuration that includes multiple functionalities and network-side (e.g., additional) conditions, such as an identifier of the configuration currently deployed in the gNB. Based on the UE's internal conditions, the UE will inform the network which functions (or configurations) can be supported from the UE. The network can then transmit the final configuration to the UE accordingly.

[0043] This capability includes the ability to store prior applicability information for a set of lower-level mobility candidate cells. Applicability information includes artificial intelligence and machine learning (AIML) functions / models / features / configurations. For example, consider the following scenario: 1) LTM is configured for cells 1, 2, 3, and 4.

[0044] 2) The UE is served by cell 1 and has certain applicability information, such as A1.

[0045] 3) When the UE goes to cell 2, it will have applicability information, such as A2.

[0046] 4) The UE returns to cell 1. This raises the question of what the UE did using A1. There are two options for what the UE did using A1: i) the UE stores A1, or ii) the UE refreshes A1, which can be the default behavior. Although LTM is used as an example, any subsequent mobility configuration can be used.

[0047] At operation 302, the S-DU transmits capabilities to the S-CU, and the S-CU receives capabilities. These capabilities include the number of cells the UE can store for applicability information of different AIML functions / models / features / configurations. In other aspects, the UE can also transmit the types and quantities of network-side additional conditions that the UE can store, for example, the S-CU and additional CUs whose additional conditions are known to the S-CU. In a further aspect, the UE can inform the S-CU of the total storage space the UE has for storing AI / ML-related information, including applicable AIML function / model / feature / configuration information and / or network-side additional conditions. Network-side additional conditions can be used by the UE to identify and align with configurations being used by the network.

[0048] At operation 303, based on the received UE capabilities, the S-CU transmits permission for measurement configuration and reporting suitability information to the S-DU. The S-DU receives permission for measurement configuration and reporting suitability information from the S-CU.

[0049] At operation 304, the S-DU transmits permission to the UE to provide measurement configuration and reporting applicability information. The UE receives permission to provide measurement configuration and reporting applicability information from the S-DU. As part of the measurement configuration, the S-CU may include additional conditions. In various aspects, the S-CU may configure the number of cells on which the UE can store / report applicable functional information and / or UE-side additional conditions (e.g., associated IDs).

[0050] The UE connects to the serving cell, has reported applicable functions (via an suitability report) to the serving cell, and has activated AIML functions / models / features / configurations. The UE observes that a handover event has occurred, such as an A3 event, which occurs when the signal quality of a neighboring cell is better than that of the current serving cell, triggering a measurement report. At operation 305, the UE transmits the measurement report and stored suitability information to the S-DU. The S-DU receives the measurement report and stored suitability information from the UE. At operation 306, the S-DU transmits the measurement report and stored suitability information to the S-CU (if available). The S-CU receives the measurement report and stored suitability information from the S-DU. If the UE has prior information about candidate cells, for example, if the UE was previously in one of the candidate gNB's cells, the UE may also report additional conditions for suitability reports (if previously stored) for one or more functions associated with the target cell and / or neighboring cells.

[0051] For example, when a UE is handing over from cell A to cell B and then back to cell A, the UE can store the features applicable to cell A when the UE is in cell A. When handing over from cell B back to cell A, the UE can report the previously applicable features to cell A instead of restarting the applicability switching process. In various aspects, the UE can publicly store the ability to store network-side additional conditions associated with different gNBs as part of the UE capability report.

[0052] The UE can also publicly store information about the applicability conditions associated with different gNBs, as well as the AIML functions / models / features / configurations configured and / or applicable in gNBs previously accessed by the UE. For example, suppose the UE supports functions A, B, C, D, and E and provides capability information to the gNB, which then configures functions A, C, and E for the UE. The UE can then determine which of the AIML functions / models / features / configurations A, C, and E is applicable to the current UE situation. For example, if the UE does not have a model for function A and lacks sufficient power to use function C, the UE will indicate that function E is applicable, and the gNB will then activate function E for inferential operation. If the UE has previously operated under another gNB with functions A and C, the UE can store such information. In this case, if the UE switches back to another gNB and functions A and C are still applicable, the UE can indicate this to the serving gNB. In some respects, this indication can be made via dedicated signaling (e.g., UE Assistance Information (UAI)). In others, this indication can be sent along with a measurement report sent from the UE to the serving gNB.

[0053] At operation 307, the S-CU decides to configure LTM for the UE. The candidate cells belong to DU2 (intra-CU LTM) and DU3 (inter-CU LTM).

[0054] In operation 308, the S-CU prepares DU2 as a mobility candidate. In all aspects, if the UE does not report applicability information for the cell under DU2, the S-CU requests an applicability report for the function determined by the provided network-side additional conditions related to DU2. At operation 309, after considering UE-side AI / ML related information (e.g., applicable function information, UE-side additional conditions, associated ID, etc.), DU2 determines that the UE can continue to use the function activated when the UE is served by the S-DU. The S-DU transmits a UE context establishment response to the S-CU, and the S-CU receives the UE context establishment response from the S-DU. In this case, as part of the LTM candidate configuration, DU2 includes an indication that the UE can continue to use the function. In all aspects, this indication can be implemented by using the flag ContinueFunctionality=True. In all aspects, both the S-DU and DU2 can belong to the same network provider and can both support the same measurement prediction mode. In this case, DU2 can indicate to the UE that the UE can continue to use the measurement prediction function configured in DU2. The DU2 configuration may include at least the following information: indications that the UE can provide information about its functional status as part of uplink (UL) authorization, configuration authorization (CG) or dynamic authorization (DG), and / or buffer status report (BSR); and indications that the UE is permitted to switch to backoff functionality, for example, in the case of measurement prediction, the UE is permitted to measure and report all reference signals. The LTM configuration may also provide corresponding reporting configurations for the UE to provide such information to the network.

[0055] The S-CU can optionally prepare DU3 as a mobility candidate under CU2. At operation 310, the S-CU transmits a handover request to CU2, and CU2 receives the handover request from the S-CU. In the handover request message, the S-CU may send information about applicable conditions reported by the UE. The S-CU may also notify CU2 of AI / ML functions configured in the UE. At operation 311, CU2 may transmit a UE context establishment request to DU3. DU3 may receive the UE context establishment request from CU2. In all aspects, if the UE does not report applicable information for the cell under DU3, the S-CU may request additional conditions related to DU3 via CU2. DU3 may send the additional conditions to the S-CU via CU2. At operation 312, DU3 transmits a UE context establishment response to CU2, and CU2 receives the UE context establishment response from DU3. As part of the LTM candidate cell configuration for DU3, DU3 may include flags instructing the UE that the UE should discontinue functions activated in the S-DU prior to LTM execution. At operation 313, CU2 transmits a handover request confirmation to S-CU, and S-CU receives the handover request confirmation from CU2.

[0056] In all aspects, the UE can interrupt AI / ML functions after being separated from the S-DU and continue in traditional operating mode. After connecting to a new serving cell, the UE can then use the pre-configured LTM prediction function. The DU3 can belong to a different network provider and support different measurement prediction functions. In this case, continuation of AI / ML functions is not possible, and reconfiguration is necessary. The configuration generated by the DU3 can provide at least the following information: an indication that the UE can provide information about the functional status as part of the UL authorization (CG or DG) and / or BSR; and an indication that the UE is allowed to switch to fallback functions (e.g., in the case of measurement prediction, the UE is allowed to measure and report all reference signals). This configuration can also provide corresponding reporting configurations for the UE to provide such information to the network.

[0057] At operation 314, the S-CU merges the LTM configuration and transmits it to the UE. The UE receives the LTM configuration from the S-CU. The LTM configuration sent to the UE provides at least the following information: an indication that the UE can provide information about the functional state as part of the UL authorization (CG or DG) and / or BSR; and an indication that the UE is permitted to switch to fallback functionality (e.g., in the case of measurement prediction, the UE is permitted to measure and report all reference signals). Each LTM candidate configuration may include an indicator of whether to continue functionality when function switching is enabled, as well as the new functional configuration. The LTM configuration may also provide a corresponding reporting configuration for the UE to provide such information to the network. In various respects, such indications are given as part of each LTM candidate cell configuration. In another embodiment, these are given as part of a reference configuration.

[0058] At operation 315, the UE transmits a measurement report to the S-DU, and the S-DU receives the measurement report from the UE. In some aspects, the measurement report may include Layer 3 (L3) measurements, and in others, the measurement report may include L1 measurements. At operation 316, the S-DU performs an LTM cell handover to another candidate cell. At operation 317, the S-DU transmits a cell handover command to the UE, and the UE receives the cell handover command from the S-DU.

[0059] Operations 318 to 321 provide a first option for not continuing the handover execution of the function. In operation 318, the UE deactivates the AI / ML function and performs LTM. At operation 318, the UE transmits a Radio Resource Control (RRC) reconfiguration complete message to CU2, and CU2 receives the RRC reconfiguration complete message. At operation 320, after the LTM cell handover is complete, the UE activates the function pre-configured as part of the LTM candidate configuration. At operation 321, the UE, S-DU, DU2, S-CU, and CU2 indicate that the RRC reconfiguration is complete and the new function is active. During the handover process, the UE may notify the network UE side of additional conditions and / or applicable functions. Notification can be made using the UL authorization (CG or DG) provided by the candidate cell.

[0060] Operations 322 and 323 provide a second option for handover execution with a function change during handover. At operation 322, the UE deactivates the function and switches to the function specified in the RRC reconfiguration message. In some aspects, this could be a fallback function. In others, it could be a different function indicated by the network. In some aspects, the UE can deactivate the function and switch to the indicated function during LTM execution, and then deactivate it again after LTM execution is complete. In a further aspect, the UE can continue using the new function after LTM execution is complete. In an even further aspect, the UE can deactivate the function during LTM execution and switch to the indicated function after LTM completion. If the UE does not support handover to the new function, for example, if UE-side conditions change during handover, the UE can fall back to the legacy function and notify the network. This can be done by including an indication in the UL authorization (CG or DG). In one embodiment, the UE indicates this via a flag in the RRC reconfiguration completion message. In some aspects, the UE can send dedicated signaling (e.g., UAI, Downlink Control Information (DCI), Media Access Control (MAC), and / or RRC signaling) to notify the network of the fallback. In others, the UE can provide such information to the target as part of the BSR. At operation 323, the UE transmits an RRC reconfiguration complete message to CU2, and CU2 receives the RRC reconfiguration complete message from the UE.

[0061] Figure 3A and 3B The operations described are merely examples, and variations are considered to be within the scope of this disclosure. In embodiments, the operations may include... Figure 3A and 3B Other operations not shown. In embodiments, operations may not include... Figure 3A and 3B Each operation is shown. In an embodiment, the operation can be performed in conjunction with... Figure 3A and 3BThe different sequences shown are implemented. These and other embodiments are considered to be within the scope of this disclosure.

[0062] Figures 4A to 4D A second solution is presented for notifying the UE to continue the configured AI / ML functions across different cells, where the ID is used to indicate the continuation of the function relative to the current serving cell. Figures 4A to 4D This is a diagram illustrating example operations for signaling UE capability information to the S-DU, S-CU, and candidate cells. These operations are performed by... Figures 4A to 4D The components shown at the top perform the operation, including the UE, S-DU, S-CU, and candidate cells. Candidate cells can be DU2, CU2, and DU3. S-DU and DU2 can belong to the S-CU, and CU2 can control DU3. Such components can be, for example, combined... Figure 1 and Figure 2 The same component described above or otherwise.

[0063] Operations 401 to 407 basically correspond to operations 301 to 307 mentioned above.

[0064] At operation 408, the S-CU decides to prepare DU2 as a mobility candidate and transmits a UE context establishment request to DU2. DU2 receives the UE context establishment request from the S-CU. The UE context establishment request may include applicability configuration information and additional condition requests. At operation 409, DU2 transmits a UE context establishment response to the S-CU, and may also transmit the requested additional conditions. The S-CU receives the UE context establishment response and the requested additional conditions. On one hand, if the UE does not report applicability information for the cell under DU2, the S-CU may request an applicability report for the function determined by the provided network-side additional conditions related to DU2. Taking into account UE-side AI / ML related information, such as applicable function information, UE-side additional conditions, associated IDs, etc., DU2 may determine that the UE can continue to use the function that was active when the UE was served by the S-DU. In this case, as part of the LTM candidate configuration, DU2 may include an indication that the UE can continue to use the function. This can be achieved by setting its own ID, for example, ltm-ContinueFunctionalityNoResetID as the serving cell continuation function ID = ltm-ServingCellContinueFunctionalityNoResetID. For instance, if the S-DU supports a certain measurement prediction configuration, the target DU (e.g., DU2 or DU3) supports the same measurement prediction configuration. If the target DU does not support that measurement prediction configuration, the target DU sets ltm-ContinueFunctionalityNoResetID to a different value than ltm-ServingCellContinueFunctionalityNoResetID. In all aspects, the target DU informs the S-CU of the measurement prediction configurations supported by the target DU, and the S-CU assigns values ​​for such IDs in such a way that when they are equal, the UE is allowed to use the serving cell configuration. The DU2 configuration also includes at least the following information: an indication that the UE can provide information about the functional status as part of the UL authorization (CG or DG) and / or BSR; and an indication that the UE is allowed to switch to a fallback function (e.g., in the case of measurement prediction, the UE is allowed to measure and report all RSs); the new AI / ML configuration / function that the UE can switch to (before, during, or after the handover); and an AI / ML function / configuration identifier that the UE can compare with the serving cell AI / ML function / configuration identifier to determine whether the UE can reuse the serving cell AI / ML function / configuration after switching to a new serving cell. The LTM configuration can also provide corresponding reporting configurations for the UE to provide such information to the network.

[0065] The S-CU can optionally prepare DU3 as a mobility candidate under CU2. At operation 410, the S-CU transmits a handover request to CU2, and CU2 receives the handover request from the S-CU. At operation 411, CU2 transmits a UE context establishment request to DU3, and DU3 receives the UE context establishment request from CU2. Under the handover request, the S-CU can send information about applicable conditions reported by the UE. The S-CU can also additionally inform CU2 about AI / ML functions configured in the UE. The S-CU can also inform CU2 of the serving cell function / configuration continuation ID and the IDs of other candidate cells. These IDs are intended for comparison during subsequent LTM periods when any of these candidates becomes the serving cell.

[0066] For example, if Candidate 2 under DU2 becomes the serving cell, the UE replaces the ltm-ServingCellContinuectionalityNoResetID with the value of ltm-ContinuectionalityNoResetID used for Candidate 2. If the UE also switches from Candidate 2 under DU2 to Candidate 3 under DU3, the UE compares the new ltm-ServingCellContinueFunctionalityNoResetID with the ltm-ContinueFunctionalityNoResetID configured by DU3. If they have the same value, the UE can continue to use the AI / ML functions / configurations used by the UE under DU2. Otherwise, the UE stops using the AI / ML functions / configurations.

[0067] In various aspects, the S-CU can inform CU2 of the AI / ML configurations supported by the S-CU. In one aspect, in the case of measurement prediction, the S-CU can inform CU2 of the measurement prediction configurations supported by the S-CU in different cells belonging to different DUs. DU3 can then assign AI / ML function / configuration IDs accordingly. CU2 can forward this information to DU3. DU3 can then generate AI / ML function / configuration IDs and send the AI / ML function / configuration to the S-CU via CU2. In another aspect, DU3 can inform CU2 of the AI / ML functions / configurations supported by DU3, and CU2 can merge LTM candidate configurations by assigning the corresponding IDs. The configuration generated by DU3 can also provide at least the following information: indications that the UE can provide information about the functional status as part of the UL authorization (CG or DG) and / or BSR; indications that the UE is allowed to switch to a fallback function (e.g., in the case of measurement prediction, the UE is allowed to measure and report all RSs); the new AI / ML configuration / function that the UE can switch to (before, during, or after the handover); and an AI / ML function / configuration identifier that the UE can compare with the serving cell AI / ML function / configuration identifier to determine whether the UE can reuse the serving cell AI / ML function / configuration after switching to a new serving cell. This configuration can also provide corresponding reporting configurations for the UE to provide such information to the network.

[0068] At operation 412, DU3 transmits a UE context setting response to CU2. This response includes an LTM candidate configuration that includes the function / configuration continuation ID associated with the candidate cell, and may include new function configurations. CU2 receives a UE context establishment response from DU3. At operation 413, CU2 transmits a handover request confirmation to S-CU, and S-CU receives a handover request confirmation from CU2. The handover request confirmation incorporates the candidate configuration that includes the function / configuration ID associated with the candidate cell, and may include new function configurations.

[0069] At operation 414, the S-CU merges the LTM candidate configurations and transmits them to the UE, and the UE receives the LTM candidate configurations from the S-CU. When function / configuration handover is enabled, each LTM candidate configuration includes an AI / ML function configuration ID. New function configurations can be given within the LTM candidate configuration. The LTM candidate configuration sent to the UE provides at least the following information: an indication that the UE can provide information about the function status as part of the UL authorization (CG or DG) and / or BSR; an indication that the UE is permitted to switch to a fallback function (e.g., in the case of measurement prediction, allowing the UE to measure and report all RSs); and an AI / ML function / configuration identifier, which the UE can compare with the serving cell AI / ML function / configuration identifier to determine whether the UE can reuse the serving cell AI / ML function / configuration after handover to a new serving cell. The LTM candidate configuration may also provide a corresponding reporting configuration for the UE to provide such information to the network. In some respects, such indications are given as part of each LTM candidate cell configuration. In other respects, these are given as part of a reference configuration.

[0070] At operation 415, the UE transmits a measurement report to the S-DU, and the S-DU receives the measurement report from the UE. The measurement report may include L3 or L1 measurements. At operation 416, the SD decides to hand over the UE to a different candidate cell. At operation 417, the S-DU transmits a cell handover command to the UE, and the UE receives the cell handover command from the S-DU.

[0071] Operations 418 to 421 provide a first option for handover execution without functional changes. In operation 418, upon receiving the cell handover command, the UE compares the ltt-ServingCellContinuationalityNoResetID with the ltt-ContinuationalityNoResetID of the candidate cell. If they have the same value, the UE continues to use the AI / ML functions / configurations / features used in the source cell and performs LTM. At operation 419, the UE transmits an RRC reconfiguration complete message to CU2, and CU2 receives the RRC reconfiguration complete message from the UE. During the handover process, the UE may notify CU2 of additional UE-side conditions and / or applicable functions. This can be done by using the UL authorization (CG or DG) provided by the candidate cell. At operation 420, after the LTM cell handover is complete, the UE replaces its serving cell AI / ML function / configuration continuation ID with the ID found in the candidate cell configuration. If indicated that a new AI / ML function / configuration should be used after the handover, the UE may apply the new AI / ML function / configuration. At operation 421, UE, S-DU, DU2, S-CU, and CU2 indicate that the RRC reconfiguration is complete and that the new function is active.

[0072] Operations 422 and 423 provide a second option for handover execution with functional changes during handover. At operation 422, upon receiving the handover command, the UE compares the ltm-ServingCellContinueFunctionalityNoResetID with the ltm-ContinueFunctionalityNoResetID of the candidate cell. If these two values ​​differ, the UE stops using the AI / ML functions / configurations / features used in the source cell and performs LTM. At operation 423, the UE transmits an RRC reconfiguration complete message to CU2, and CU2 receives the RRC reconfiguration complete message from the UE.

[0073] Figures 4A to 4D The operations described are merely examples, and variations are considered to be within the scope of this disclosure. In embodiments, the operations may include... Figures 4A to 4D Other operations not shown. In an embodiment, the operations may not include each of the operations shown in 4A to 4D. In an embodiment, the operations may be in conjunction with... Figures 4A to 4D The different sequences shown are implemented. These and other embodiments are considered to be within the scope of this disclosure.

[0074] Figure 5A and 5B This is a diagram illustrating an example operation for signaling UE capability information to the S-DU, S-CU, and candidate cells (including DU2, CU2, and CU3). Such components can be, for example, combined with... Figure 1 and Figure 2 The same component described above or otherwise. Figure 5A and 5B An example involving candidate cells at the MAC address.

[0075] At operation 501, the UE transmits an L1 measurement report to the S-DU, and the S-DU receives the L1 measurement report. As part of the L1 measurement report, or in a separate L1 / L2 message (e.g., a MAC control element (CE)), the UE also provides information about updated additional conditions. In one embodiment, the UE reports the set of additional conditions again. In various aspects, the additional conditions may be given as an increment of previously reported additional conditions. For example, the UE may only report additional conditions that have changed relative to earlier reported conditions. In another aspect, the UE may update the associated ID reported to the network. This may be a completely new report of the associated ID. In various aspects, the new associated ID may be signaled as an increment of the previously associated ID. Similar to the previous embodiments, the UE may also signal updated AI / ML feature information. For example, in the context of measurement prediction, the updated information may consist of new measurement prediction modes that the UE can support. This may include new observation and / or prediction windows that the UE can support.

[0076] In operation 502, the updated information may include updated additional conditions, updated associated IDs, and / or updated applicable function information. This updated information is transmitted from the S-DU to the S-CU and received by the S-CU from the S-DU. In operation 503, the updated information is transmitted from the S-CU to CU2 and received by CU2 from the S-CU. In operation 504, the updated information is transmitted from CU2 to DU3 and received by DU3 from CU2. The corresponding configuration is prepared by DU3. In operation 505, the updated functions, as part of the LTM candidate configuration, are transmitted from DU3 to CU2 and received by CU2 from DU3. In operation 506, the updated functions are transmitted from CU2 to the S-CU and received by the S-CU from CU2. In operation 507, the updated functions are transmitted from the S-CU to the S-DU and received by the S-DU from the S-CU.

[0077] At operation 508, the S-DU transmits a MAC CE to update the UE's LTM candidate configuration, and the UE receives the MAC CE from the S-DU. The MAC CE can update any part of the LTM-Config included in the RRC configuration already received by the UE. This can include information about new measurement prediction modes, observations, and prediction window lengths.

[0078] At operation 509, the UE updates its RRC configuration based on the received MAC CE. In one aspect, the UE can begin using the newly configured measurement prediction mode. In another aspect, the UE can begin monitoring the configured observation and / or prediction window.

[0079] At operation 510, the UE uses lower-layer signaling to notify the S-DU UE that the RRC configuration has been updated. At operation 511, the S-CU transmits dedicated signaling to notify the S-DU UE that the RRC configuration has been updated.

[0080] Figure 5A and 5B The operations described are merely examples, and variations are considered to be within the scope of this disclosure. In embodiments, the operations may include... Figure 5A and 5B Other operations not shown. In embodiments, operations may not include... Figure 5A and 5B Each operation is shown. In an embodiment, the operation can be performed in conjunction with... Figure 5A and 5B The different sequences shown are implemented. These and other embodiments are considered to be within the scope of this disclosure.

[0081] Figure 6 This is a block diagram of a wireless station or node (e.g., UE, user equipment, AP, BS, eNB, gNB, RAN node, network node, Transmitter Receiver Point (TRP) or other node) 600 according to an exemplary aspect of this disclosure. The wireless station 600 may include, for example, one or more (e.g., such as...) Figure 6 The two RF (radio frequency) or wireless transceivers 602A and 602B shown are provided, each of which includes a transmitter for transmitting signals and a receiver for receiving signals. The wireless station also includes a processor or control unit / entity (controller) 608 for executing instructions or software and controlling the transmission and reception of signals, and a memory 606 for storing data and / or instructions.

[0082] Processor 604 may also make decisions or determinations, generate frames, packets, or messages for transmission, decode received frames or messages for further processing, and perform other tasks or functions described herein. For example, processor 604, which may be a baseband processor, may generate messages, packets, frames, or other signals for transmission via wireless transceiver 602 (602A or 602B). Processor 604 may control the transmission of signals or messages on a wireless network and may control the reception of signals or messages via a wireless network (e.g., after down-conversion by wireless transceiver 602). Processor 604 may be programmable and capable of executing software or other instructions stored in memory or other computer media to perform one or more of the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 604 may be (or may include) hardware, programmable logic, a programmable processor executing software or firmware, and / or any combination of these. Using other terms, processor 604 and transceiver 602 together may be considered, for example, a wireless transmitter / receiver system.

[0083] Additionally, refer to Figure 6 The controller (or processor) 608 can execute software and instructions, and can provide overall control for station 600, and can provide... Figure 6 Other systems, not shown, provide control, such as controlling input / output devices (e.g., a display, a keypad), and / or can execute software that can perform one or more applications available on the wireless station 600, such as, for example, an email program, an audio / video application, a word processor, a VoIP application, or other applications or software.

[0084] Additionally, a storage medium may be provided that includes stored instructions, which, when executed by a controller or processor, may cause processor 604 or other controllers or processors to perform one or more of the functions or tasks described above.

[0085] According to another example embodiment, the RF or (multiple) wireless transceivers 602 A / 602 B can receive signals or data and / or transmit or send signals or data. The processor 604 (and possibly the transceivers 602 A / 602 B) can control the RF or wireless transceivers 602 A or 602 B to receive, transmit, broadcast, or transmit signals or data.

[0086] Example embodiments are provided or described for each example method, including: an apparatus (e.g., Figure 6 (600), including components for performing any method (e.g., Figure 6 The processor 604, RF transceiver 602 A and / or 602 B and / or memory 606; a non-transitory computer-readable storage medium (e.g., Figure 6Memory 606), including instructions stored thereon, which are processed by at least one processor ( Figure 6 The processor 604) is configured to cause the computing system (e.g., Figure 6 (600) executes any example method; and a device (e.g., Figure 6 (of the 600), including at least one processor (e.g., Figure 6 The processor 604) and at least one memory (e.g., Figure 6 The at least one memory (606) includes computer program code, and the at least one memory (606) and the computer program code are configured together with at least one processor (604) to enable the device (e.g., 600) to perform at least any of the example methods.

[0087] Other embodiments of this disclosure include the following examples.

[0088] Example 1.1 A user equipment (UE) includes: A component for transmitting messages indicating UE capability information from a user equipment (UE) to a network node supporting a Layer 2 protocol of a radio access network, the capability information relating to stored prior applicability information for a set of lower-layer mobility candidate cells; Components for receiving signals from a network node by a UE, wherein the signals include network-side conditions; A component used by the UE to transmit messages to the network node, including information related to Artificial Intelligence and Machine Learning (AIML) functions / models / features / configuration and UE Assistance Information (UAI); and A component used by the UE to receive subsequent mobility configuration from the network node.

[0089] Example 1.2 is based on the user equipment (UE) of Example 1.1, wherein the UE capability information also includes the type and number of network-side conditions that the UE can store.

[0090] Example 1.3 is based on the user equipment (UE) of Example 1.2, wherein the UE capability information also includes an indication of the storage space that the UE has for storing information related to AIML functions / models / features / configurations.

[0091] Example 1.4, according to any one of Examples 1.1 to 1.3, also includes: Components for transmitting at least one of a Layer 1 measurement report or a Layer 3 measurement report from the UE to a first network node; and A component used by the UE to receive handover commands from the first network node.

[0092] Example 1.5, based on the user equipment (UE) of Example 1.4, also includes: Components for deactivating AIML functions / models / features / configurations by the UE; and Components used by the UE to perform subsequent mobility procedures.

[0093] Example 1.6, according to any one of Examples 1.1 to 1.5, also includes: Components for deactivating AIML functions / models / features / configurations by the UE; and The component used for switching AIML functions / models / features / configurations by the UE.

[0094] Example 1.7, based on the user equipment (UE) of Example 1.6, also includes: Components used to deactivate AIML functions / models / features / configurations by the UE during the execution of subsequent mobility procedures; and A component used to switch to AIML features / models / features / configurations after the subsequent mobility process is completed.

[0095] Example 1.8 is a user equipment (UE) according to any one of Examples 1.1 to 1.7, wherein the UE capability information includes the number of cells that the UE is able to store for applicability information for different AIML functions / models / features / configurations.

[0096] Example 1.9 is a user equipment (UE) according to any one of Examples 1.1 to 1.8, wherein the subsequent mobility configuration includes the subsequent mobility configuration.

[0097] Example 1.10 is a user equipment (UE) according to Example 1.9, wherein the subsequent mobility configuration includes an indication that the UE can continue to use AIML functions / models / features / configurations, or a flag that indicates that the UE should terminate AIML functions / models / features / configurations that were activated in the network node prior to the subsequent mobility procedure.

[0098] Example 1.11, based on the user equipment (UE) of Example 1.10, wherein the subsequent mobility configuration further includes at least an indication of providing information about the status of the AIML function / model / feature / configuration, and an indication that the UE is allowed to switch to a fallback AIML function / model / feature / configuration.

[0099] Example 1.12 is based on the user equipment (UE) of Example 1.11, where the fallback AIML function / model / feature / configuration is provided as part of the target cell configuration.

[0100] Example 1.13 is based on the user equipment (UE) of Example 1.11, where the fallback AIML function / model / feature / configuration is provided outside the target cell configuration.

[0101] Example 1.14 is based on the user equipment (UE) of Example 1.11, wherein subsequent mobility configuration includes an indication that the UE is able to provide information about its state as part of uplink (UL) authorization and / or BSR.

[0102] In Example 1.15, for a user equipment (UE) such as any of Examples 1.1 to 1.14, the signal may include a measurement configuration, an RRC reconfiguration message, a MAC CE, and / or a DCI.

[0103] Example 1.16 is based on the user equipment (UE) of Example 1.15, where network-side conditions can be used by the UE to identify and align with the configuration being used by the network node.

[0104] Example 1.17, according to any one of Examples 1.1 to 1.16, also includes: Based on the UE's internal conditions, this is used by the UE to notify the network node which function is supported by the UE when the UE has previously accessed a subsequent mobility candidate.

[0105] Example 1.20 A network device comprising: A component for receiving a message indicating UE capability information from a first network node supporting a Layer 2 protocol of a radio access network, the capability information relating to stored prior applicability information for a set of lower-layer mobility candidate cells; A component for forwarding messages indicating UE capability information from a first network node to a second network node, wherein the second network node supports at least one of a Central Unit Control Plane (CU-CP) function or a Layer 3 protocol of a radio access network; Components for transmitting signals from a first network node to a UE, wherein the signals include network-side conditions associated with serving cell configuration and / or supported functions; The component used by the first network node to receive messages from the UE, including information related to artificial intelligence and machine learning (AIML) functions / models / features / configurations and UE assistance information (UAI). Components for forwarding messages from a first network node to a second network node; and A component used for transmitting subsequent mobility configurations from a second network node to the UE.

[0106] Example 1.21 A network device according to Example 1.20, wherein the UE capability information also includes the type and number of network-side conditions that the UE can store.

[0107] Example 1.22 A network device according to Example 1.21, wherein the UE capability information further includes an indication of the storage space that the UE has for storing AIML function / model / feature / configuration information.

[0108] Example 1.23 The network apparatus according to any one of Examples 1.20 to 1.22 further includes: A component for receiving at least one of a Layer 1 measurement report or a Layer 3 measurement report from a UE by a first network node; and A component used to transmit handover commands from the first network node to the UE.

[0109] Example 1.24 A network device according to any one of Examples 1.20 to 1.23, wherein the UE capability information includes the number of cells in which the UE is able to store applicability information for different AIML functions / models / features / configurations.

[0110] Example 1.25 The network apparatus according to any one of Examples 1.20 to 1.24 further includes: Components for merging subsequent mobility configurations by a second network node; and A component used for transmitting subsequent mobility configurations from a second network node to the UE.

[0111] Example 1.26 A network apparatus according to Example 1.25 wherein subsequent mobility configuration includes an indication that the UE can continue to use AIML functions / models / features / configurations, or a flag that indicates that the UE should terminate AIML functions / models / features / configurations activated in a second network node prior to performing the mobility procedure.

[0112] Example 1.27 A network device according to Example 1.26, wherein subsequent mobility configuration further includes at least an indication of providing information about the status of AIML function / model / feature / configuration, and an indication that the UE is allowed to switch to fallback AIML function / model / feature / configuration.

[0113] Example 1.28 A network device according to Example 1.27, wherein subsequent mobility configuration, or measurement report, or RRC reconfiguration completion message, or uplink (UL) authorization and / or BSR includes an indication that the indication is about the suitability status of the UE to provide AIML functions / models / features / configurations.

[0114] In Example 1.29, the network device according to any one of Examples 1.20 to 1.28 may include a measurement configuration, an RRC reconfiguration message, a MAC CE, and / or a DCI.

[0115] Example 1.30 is a network device according to Example 1.29, wherein network-side conditions can be identified by the UE and aligned with the configuration being used by the network node.

[0116] The embodiments and aspects disclosed herein are examples of this disclosure and may be embodied in various forms. For example, although some embodiments herein are described as separate embodiments, each embodiment herein may be combined with one or more other embodiments herein. The specific structural and functional details disclosed herein should not be construed as limiting, but rather serve as the basis for the claims and as a representative basis for teaching those skilled in the art to apply this disclosure differently with virtually any suitable detailed structure. Throughout the description of the accompanying drawings, the same reference numerals may refer to similar or identical elements.

[0117] The phrases “in one respect,” “in all respects,” “in multiple respects,” “in some respects,” or “in other respects” may each refer to one or more of the same or different respects under this disclosure. The phrase “multiple respects” may refer to two or more.

[0118] The phrases “in an embodiment,” “in various embodiments,” “in multiple embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments according to this disclosure. The phrase “A or B” means “(A), (B), or (A and B).” The phrase “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).”

[0119] Any method, program, algorithm, or code described herein can be translated into or expressed in a programming language or computer program. As used herein, the terms “programming language” and “computer program” each include any language used to specify instructions to a computer, and include (but are not limited to) the following languages ​​and their derivatives: assembly language, Basic, batch files, BCPL, C, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, meta-languages ​​that specify their own programs, and all first-, second-, third-, fourth-, fifth-, and more generation computer languages. Databases and other data schemas, and any other meta-languages, are also included. There is no distinction between languages ​​that are interpreted, compiled, or use compilation and interpretation methods. There is no distinction between compiled and source versions of a program. Therefore, a reference to a program in which a programming language can exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. A reference to a program can encompass the actual instructions and / or the intent of those instructions.

[0120] While various aspects of this disclosure have been shown in the accompanying drawings, they are not intended to be limited thereto, as the scope of this disclosure is intended to be as broad as would be permitted in the art, and the specification is to be understood in the same manner. Therefore, the above description should not be construed as restrictive, but merely as an example of particular aspects. Other modifications within the scope and spirit of the appended claims will be contemplated by those skilled in the art.

[0121] Furthermore, the various implementations of this disclosure can be described with reference to the following terms, and their features can be combined in any reasonable manner.

[0122] Clause 1. A method comprising: transmitting a message indicating UE capability information to a network node supporting a Layer 2 protocol of a radio access network, the capability information relating to stored prior applicability information for a set of lower-layer mobility candidate cells; receiving a signal from the network node by the UE, wherein the signal includes network-side conditions; transmitting a message from the UE to the network node, the message including information related to artificial intelligence and machine learning (AIML) functions / models / features / configurations and UE assistance information (UAI); and receiving subsequent mobility configuration from the network node by the UE.

[0123] Clause 2. The method described in Clause 1, wherein the UE capability information further includes: the type and number of network-side conditions that the UE can store.

[0124] Clause 3. The method according to Clause 2, wherein the UE capability information further includes an indication of the storage space that the UE has for storing information related to the AIML function / model / feature / configuration.

[0125] Clause 4. The method according to any one of Clauses 1 to 3 further includes: transmitting at least one of a Layer 1 measurement report or a Layer 3 measurement report from the UE to the first network node; and receiving a handover command from the first network node by the UE.

[0126] Clause 5. The method described in Clause 4 further includes: deactivating the AIML function / model / feature / configuration by the UE; and performing subsequent mobility procedures by the UE.

[0127] Clause 6. The method according to any one of Clauses 1 to 5 further includes: deactivating the AIML function / model / feature / configuration by the UE; and switching the AIML function / model / feature / configuration by the UE.

[0128] Clause 7. The method according to Clause 6 further includes: deactivating the AIML function / model / feature / configuration by the UE during the execution of the subsequent mobility procedure; and switching to the AIML function / model / feature / configuration after the completion of the subsequent mobility procedure.

[0129] Clause 8. The method according to any one of Clauses 1 to 7, wherein the UE capability information includes the number of cells in which the UE is capable of storing applicability information for different AIML functions / models / features / configurations.

[0130] Clause 9. The method according to any one of Clauses 1 to 8, wherein the subsequent mobility configuration includes the subsequent mobility configuration.

[0131] Clause 10. The method according to Clause 9, wherein the subsequent mobility configuration includes an indication that the UE is able to continue using the AIML function / model / feature / configuration, or a flag that indicates that the UE should terminate the AIML function / model / feature / configuration that was activated in the network node prior to the subsequent mobility procedure.

[0132] Clause 11. The method according to Clause 10, wherein the subsequent mobility configuration further includes at least an indication of providing information about the status of the AIML function / model / feature / configuration, and an indication that the UE is permitted to switch to a fallback AIML function / model / feature / configuration.

[0133] Clause 12. The method described in Clause 11, wherein the fallback AIML function / model / feature / configuration is provided as part of the target cell configuration.

[0134] Clause 13. The method described in Clause 11, wherein the fallback AIML function / model / feature / configuration is provided outside the target cell configuration.

[0135] Clause 14. The method according to Clause 11, wherein the subsequent mobility configuration includes an indication that the UE is able to provide information about the state as part of an uplink (UL) grant and / or BSR.

[0136] Clause 15. The signal may include a measurement configuration, an RRC reconfiguration message, a MAC CE, and / or a DCI, according to any one of Clauses 1 to 14.

[0137] Clause 16. The method according to Clause 15, wherein the network-side conditions can be identified by the UE and aligned with the configuration being used by the network node.

[0138] Clause 17. The method according to any one of Clauses 1 to 16 further comprises: based on internal conditions of the UE, when the UE has previously accessed a subsequent mobility candidate, the UE notifying the network node which function is supported by the UE.

[0139] Clause 18. A user equipment (UE) comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the UE to perform at least one method according to any one of Clauses 1 to 17.

[0140] Clause 19. A processor-readable medium storing instructions that, when executed by at least one processor of a user equipment (UE), cause the UE to perform at least the method according to any one of Clauses 1 to 17.

[0141] Clause 20. A method comprising: receiving, by a user equipment (UE), a message indicating UE capability information from a first network node supporting a Layer 2 protocol of a radio access network, the capability information relating to stored prior applicability information for a set of lower-layer mobility candidate cells; forwarding, by the first network node, the message indicating UE capability information to a second network node, the second network node supporting at least one of a Central Cell Control Plane (CU-CP) function or a Layer 3 protocol of the radio access network; transmitting, by the first network node, a signal to the UE, wherein the signal includes network-side conditions associated with serving cell configuration and / or supported functions; receiving, by the first network node, a message from the UE, the message including information related to artificial intelligence and machine learning (AIML) functions / models / features / configurations and UE assistance information (UAI); forwarding, by the first network node, the message to the second network node; and transmitting subsequent mobility configurations, by the second network node, to the UE.

[0142] Clause 21. The method described in Clause 20, wherein the UE capability information further includes: the type and number of network-side conditions that the UE can store.

[0143] Clause 22. The method according to Clause 21, wherein the UE capability information further includes an indication of the storage space the UE has for storing AIML function / model / feature / configuration information.

[0144] Clause 23. The method according to any one of Clauses 20 to 22 further includes: the first network node receiving at least one of a Layer 1 measurement report or a Layer 3 measurement report from the UE; and the first network node transmitting a handover command to the UE.

[0145] Clause 24. The method according to any one of Clauses 20 to 23, wherein the UE capability information includes the number of cells in which the UE is capable of storing applicability information for different AIML functions / models / features / configurations.

[0146] Clause 25. The method according to any one of Clauses 20 to 24 further includes: merging the subsequent mobility configuration by the second network node; and transmitting the subsequent mobility configuration to the UE by the second network node.

[0147] Clause 26. The method according to Clause 25, wherein the subsequent mobility configuration includes an indication that the UE is able to continue using the AIML function / model / feature / configuration, or a flag that indicates that the UE should discontinue the AIML function / model / feature / configuration that was activated in the second network node prior to the execution of the mobility procedure.

[0148] Clause 27. The method according to Clause 26, wherein the subsequent mobility configuration further includes at least an indication of providing information about the status of the AIML function / model / feature / configuration, and an indication that the UE is permitted to switch to a fallback AIML function / model / feature / configuration.

[0149] Clause 28. The method described in Clause 27, wherein the subsequent mobility configuration, or measurement report, or RRC reconfiguration completion message, or uplink (UL) authorization and / or BSR includes an indication regarding the suitability status of the UE for providing the AIML function / model / feature / configuration.

[0150] Clause 29. The method according to any one of Clauses 20 to 28, wherein the signal may include measurement configuration, RRC reconfiguration message, MAC CE and / or DCI.

[0151] Clause 30. The method according to Clause 29, wherein the network-side conditions can be identified by the UE and aligned with the configuration being used by the network node.

[0152] Clause 31. A network device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to perform at least one method according to any one of Clauses 20 to 30.

[0153] Clause 32. A processor-readable medium storing instructions that, when executed by at least one processor of a network device, cause the network device to perform at least one method according to any one of Clauses 20 to 31.

Claims

1. A method for communication, comprising: A message indicative of UE capability information is transmitted from a user equipment (UE) to a network node supporting a Layer 2 protocol of a radio access network. This capability information relates to stored prior applicability information for a set of lower-layer mobility candidate cells. The UE receives a signal from the network node, wherein the signal includes network-side conditions; The UE transmits messages to the network node, the messages including information related to Artificial Intelligence and Machine Learning (AIML) functions / models / features / configurations and UE Assistance Information (UAI); and The UE receives subsequent mobility configuration from the network node.

2. The method according to claim 1, wherein the UE capability information further includes: The UE can store the types and number of network-side conditions.

3. The method according to claim 2, wherein the UE capability information further includes an indication of the storage space that the UE has for storing information related to the AIML function / model / feature / configuration.

4. The method according to any one of claims 1 to 3, further comprising: The UE transmits at least one of a Layer 1 measurement report or a Layer 3 measurement report to the first network node; as well as The UE receives the handover command from the first network node.

5. The method according to claim 4, further comprising: The AIML function / model / feature / configuration is deactivated by the UE; as well as The UE then performs the subsequent mobility procedures.

6. The method according to any one of claims 1 to 3, further comprising: The AIML function / model / feature / configuration is deactivated by the UE; as well as Switch from the UE to the AIML function / model / feature / configuration.

7. The method of claim 6, further comprising: The AIML function / model / feature / configuration is deactivated by the UE during the execution of the subsequent mobility procedure; as well as After completing the subsequent mobility process, switch to the AIML function / model / feature / configuration.

8. The method according to any one of claims 1 to 3, wherein the UE capability information includes the number of cells in which the UE is capable of storing applicability information for different AIML functions / models / features / configurations.

9. The method according to any one of claims 1 to 3, wherein the subsequent mobility configuration includes the subsequent mobility configuration.

10. The method of claim 9, wherein the subsequent mobility configuration includes an indication that the UE can continue to use the AIML function / model / feature / configuration, or a flag indicating that the UE should terminate the AIML function / model / feature / configuration that was activated in the network node prior to the subsequent mobility procedure.

Images