RRM mobility handling based on beam management reports

Abstract

A method, system, and apparatus are disclosed. A network node for communicating with a wireless device in a first cell is provided. The network node is configured to receive a measurement report associated with a first cell from a wireless device. The network node is further configured to estimate at least one radio resource management (RRM) metric for the first cell and the at least one second cell based on the measurement report and the history information. The network node is further configured to perform an RRM mobility procedure based on the estimated RRM metric.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and more particularly, to radio resource management (RRM) mobility processing based on beam management reports. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) has developed and is developing standards for the 4th (4G) (also known as Long Term Evolution (LTE)) and 5th (5G) (also known as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communications between network nodes (such as base stations) and mobile wireless devices (WDs), as well as communications between network nodes and between wireless devices. The 6th (6G) wireless communication systems are also under development.

[0003] General Radio Resource Management (RRM) measurements and reporting

[0004] In some existing systems, the wireless device may be configured with event-based reporting, where the wireless device sends one or more RRM reports (eg, triggered by an event). The network node determines whether a handover (HO) (also referred to as a "handoff") is required and, if so, triggers the HO.

[0005] Machine Learning (ML) Enhanced RRM Measurements:

[0006] The wireless device may learn upcoming events / HO situations based on previous RRM measurements. For example, during normal operation, the learned RRM measurements and experience of time series relationships of candidate cells are combined with current RRM measurements to improve RRM measurements and event reporting (e.g., to make it more robust).

[0007] Condition HO

[0008] In some existing systems, the wireless device can be configured with RRM measurement conditions for initiating HO to another cell, and the current serving cell (e.g., network node) can inform the cell of the upcoming HO. If the wireless device detects that the condition is met, it autonomously accesses and connects to the new serving cell.

[0009] In conventional RRM measurements and reports, HO can be triggered based on reported RRM mobility events that are directly observed by the wireless device and reported to the network node. In some scenarios, this may lead to a lack of robustness, for example, if the RRM measurement rate is relatively slow and the current link degrades rapidly before or around the time the event is reported. This event signaling consumes uplink (UL) resources and generates interference in the network.

[0010] Using ML-enhanced RRM measurements, robustness may be improved, but full RRM measurements of the wireless device may still be required and the associated wireless device energy consumption may not be reduced.

[0011] With conditional HO, the reporting of the wireless device can be minimized, but full measurements continue and the resulting HO robustness may be lower because the HO decision is made by the wireless device based on one or a few individual measurements. The RRM measurements in the wireless device remain unchanged.

[0012] Therefore, existing systems lack configuration for robust and low-overhead RRM mobility handling. Summary of the invention

[0013] Various aspects are provided by the independent claims and embodiments thereof are provided in the dependent claims.

[0014] Some embodiments of the present disclosure advantageously provide methods, systems, and apparatus for mobility processing, in which, for example, compared to existing systems, HO decisions can be made robustly / proactively, UL signaling for RRM can be minimized, and / or wireless device energy consumption due to RRM measurements can be reduced.

[0015] For example, in some embodiments, during a learning phase of the ML model, a network node (e.g., a gNB) may establish a relationship between layer 1 (L1) (e.g., open system interconnection (OSI) layer 1) reports from its cell (e.g., channel state information reference signal (CSI-RS) for beam management (BM) (BM CSI-RS)) and corresponding RRM reports (e.g., synchronization signal blocks (SSBs)) of the cell and additional cells (e.g., by training an ML model). The training may be based on regular wireless device event reports and / or extended RRM reports during the learning phase, and may be achieved, for example, by training an ML model and / or preparing a lookup table.

[0016] For example, in some embodiments of the present disclosure, during normal operation, a network node (e.g., gNB) continuously receives BM reports for a serving cell from a wireless device and uses these reports as input (e.g., input to ML inference) to estimate RRM cell / beam quality metrics for the serving cell and / or other cells (e.g., neighboring cells). Thus, the network node can foresee mobility events for the wireless device (including, for example, the remaining time for an upcoming event) and can proactively initiate HO. The network node can set an internal HO trigger threshold, so that HO is triggered before the wireless device detects the corresponding event and reports it.

[0017] In some embodiments, using the ML model approach for RRM metric prediction may include taking into account wireless device trajectories, which may lead to better estimates, for example, compared to single events or other RRM measurement reports.

[0018] In some embodiments, the wireless device may still be configured with regular event-based reporting as a fallback and supplement training data to improve the ML model, but the measurement / reporting occasions are more sparse to save wireless device energy and UL resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] A more complete understanding of the embodiments of the present application and the attendant advantages and features thereof will be more readily appreciated by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which:

[0020] Figure 1 is a schematic diagram illustrating an example network architecture of a communication system connected to a host computer via an intermediate network according to the principles of the present disclosure;

[0021] Figure 2 is a block diagram of a host computer communicating with a wireless device via a network node over an at least partially wireless connection according to some embodiments of the present disclosure;

[0022] Figure 3 is a flow chart illustrating an example method for executing a client application at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0023] Figure 4 is a flow chart illustrating an example method for receiving user data at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0024] Figure 5 is a flow chart illustrating an example method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data from a wireless device at a host computer according to some embodiments of the present disclosure;

[0025] Figure 6 is a flow chart illustrating an example method for receiving user data at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0026] Figure 7 is a flow chart of an example process of RRM mobility processing based on beam management reporting in a network node according to some embodiments of the present disclosure;

[0027] Figure 8is a flow chart of an example process of RRM mobility processing based on beam management reporting in a wireless device according to some embodiments of the present disclosure;

[0028] Fig. 9A and Fig. 9B is a sequence diagram of an example process of RRM mobility processing based on beam management reporting according to some embodiments of the present disclosure;

[0029] Fig. 10A and Fig. 10B is a sequence diagram of an example process of RRM mobility processing based on beam management reporting according to some embodiments of the present disclosure;

[0030] Fig.11 is a schematic diagram of an example scenario of RRM mobility processing based on beam management reporting according to some embodiments of the present disclosure; and

[0031] Fig.12 is a flow chart of an example process of RRM mobility processing based on beam management reports in a network node according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0032] Before describing the example embodiments in detail, it is noted that the embodiments reside primarily in a combination of apparatus components and processing steps related to RRM mobility processing based on beam management reports. Therefore, components are appropriately represented in the drawings by conventional symbols, and only those specific details associated with understanding the embodiments are shown so as not to obscure the present disclosure with details that are obvious to those of ordinary skill in the art having the benefit of the description herein. Throughout the specification, like numerals refer to like elements.

[0033] The relational terms used herein (such as "first" and "second", "top" and "bottom", etc.) may be used only to distinguish one entity or element from another entity or element, without necessarily requiring or implying any physical or logical relationship or order between these entities or elements. The terms used herein are only used for the purpose of describing specific embodiments, not for limiting the concepts described herein. Unless the context clearly indicates the contrary, the singular forms "one", "an" and "the" as used herein are intended to also include plural forms. It will also be understood that the terms "including", "having" and / or "comprising" when used herein indicate the presence of stated features, elements, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, elements, steps, operations, elements, components and / or combinations thereof.

[0034] In the embodiments described herein, the connection terms "in communication with..." and the like may be used to indicate electrical communication or data communication, which may be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will appreciate that multiple components may interoperate and that modifications and variations may be implemented for electrical and data communications.

[0035] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate a connection, although not necessarily directly indicated, and may include wired and / or wireless connections.

[0036] The term "network node" used herein may be any type of network node included in a radio network, and the network node may also include any of a base station (BS), a radio base station, a base transceiver station (BTS), a base station controller (BSC), a radio network controller (RNC), a gNodeB (gNB), an evolved NodeB (eNB or eNodeB), a NodeB, a multi-standard radio (MSR) radio node (such as an MSR BS), a multi-cell / multicast coordination entity (MCE), an integrated access and backhaul (IAB) node, a relay node, a donor node controlled relay, a radio access point (AP), a transmission point, a transmission node, a remote radio unit (RRU) remote radio head (RRH), a core network node (e.g., a mobility management entity (MME), a self-organizing network (SON) node, a coordination node, a positioning node, an MDT node, etc.), an external node (e.g., a third-party node, a node outside the current network), a node in a distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also include a test device. As used herein, the term "radio node" may also be used to denote a wireless device (WD), such as a wireless device (WD) or a radio network node.

[0037] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. The WD in this article can be any type of wireless device capable of communicating with a network node or another WD via a radio signal, such as a wireless device (WD). The WD can also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine type WD or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smart phone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB adapter or a client terminal device (CPE), an Internet of Things (IoT) device or a narrowband IoT (NB-IOT) device, etc.

[0038] In addition, in some embodiments, the general term "radio network node" is used. It can be any type of radio network node, including any of a base station, a radio base station, a base transceiver station, a base station controller, a network controller, an RNC, an evolved NodeB (eNB), a NodeB, a gNB, a multi-cell / multicast coordination entity (MCE), an IAB node, a relay node, an access point, a radio access point, a remote radio unit (RRU), and a remote radio head (RRH).

[0039] Note that although terminology from one particular wireless system (e.g., 3GPP LTE and / or New Radio (NR)) may be used in the present disclosure, this should not be viewed as limiting the scope of the present disclosure to only the aforementioned systems. Other wireless systems (including but not limited to Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM)) may also benefit from utilizing the concepts encompassed within the present disclosure.

[0040] Also note that the functions performed by a wireless device or network node described herein may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device and may in fact be distributed across several physical devices.

[0041] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will be further understood that the terms used herein should be interpreted as being consistent with their meanings in the context of this specification and the relevant art, and not interpreted as ideal or overly formal meanings, unless so explicitly defined herein.

[0042] Note also that references herein to cell measurements (or measurements of a cell) may refer to measurements of one or more network node signals of one or more network nodes serving that cell.

[0043] Some embodiments provide RRM mobility handling based on beam management reports.

[0044] Referring now to the drawings, in which like elements are referred to by like reference numerals, Figure 1, a schematic diagram of a communication system 10 according to an embodiment is shown, for example, a 3GPP-type cellular network that can support standards such as LTE and / or NR (5G), which includes an access network (e.g., a radio access network) 12 and a core network 14. The access network 12 includes a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs or other types of radio access points, each of which defines a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c can be connected to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in the coverage area 18a is configured to be wirelessly connected to the corresponding network node 16a or to be paged by the corresponding network node 16a. A second WD 22b in the coverage area 18b can be wirelessly connected to the corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where only a single WD is located in the coverage area or a single WD is connected to a corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include more WDs 22 and network nodes 16.

[0045] Additionally, it is contemplated that the WD 22 may communicate simultaneously and / or be configured to communicate individually with more than one network node 16 and more than one type of network node 16. For example, the WD 22 may have dual connectivity with a network node 16 that supports LTE and the same or different network nodes 16 that support NR. For example, the WD 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0046] The communication system 10 itself may be connected to a host computer 24, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 24 may be owned or under the control of a service provider, or may be operated by or on behalf of a service provider. The connections 26, 28 between the telecommunications system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24, or may extend through an optional intermediate network 30. The intermediate network 30 may be one or a combination of more than one of a public network, a private network, or a managed network; the intermediate network 30 (if any) may be a backbone network or the Internet; in some embodiments, the intermediate network 30 may include two or more sub-networks (not shown).

[0047] Figure 1The communication system as a whole implements a connection between one of the connected WD 22a, WD 22b and the host computer 24. The connection can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WD 22a, WD 22b are configured to send data and / or signaling via the OTT connection using the access network 12, the core network 14, any intermediate network 30 and possible other intermediate infrastructure (not shown). At least some of the participating communication devices through which the OTT connection passes do not know the routing of the uplink and downlink communications, and in this sense, the OTT connection can be transparent. For example, the network node 16 may not be informed or need not be informed of the past routing of the incoming downlink communication, which has data originating from the host computer 24 and to be forwarded (e.g., handed over) to the connected WD 22a. Similarly, the network node 16 does not need to know the future routing of the uplink communication originating from the WD 22a and toward the output of the host computer 24.

[0048] The network node 16 is configured to include a mobile unit 32 configured for RRM mobility handling based on beam management reports. The wireless device 22 is configured to include a reporting unit 34 configured for RRM mobility handling based on beam management reports.

[0049] Now refer to Figure 2 An example implementation according to an embodiment of the WD 22, network node 16, and host computer 24 discussed in the previous paragraphs is described. In the communication system 10, the host computer 24 includes hardware (HW) 38, which includes a communication interface 40, which is configured to establish and maintain a wired or wireless connection with the interface of different communication devices of the communication system 10. The host computer 24 also includes a processing circuit 42, which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and a memory 46. Specifically, as a supplement or alternative to a processor (e.g., a central processing unit) and a memory, the processing circuit 42 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits) suitable for executing instructions. The processor 44 may be configured to access (e.g., write to or read from) a memory 46, which may include any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read Only Memory).

[0050] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein, and / or cause these methods and / or processes to be performed, for example, by host computer 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host computer 24 described herein. Host computer 24 includes memory 46, which is configured to store data, program software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuitry 42, cause processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host computer 24. These instructions may be software associated with host computer 24.

[0051] The software 48 can be executed by the processing circuit 42. The software 48 includes a host application 50. The host application 50 can be operated to provide services to a remote user, such as a WD 22 connected via an OTT connection 52, which is terminated at the WD 22 and the host computer 24. When providing services to the remote user, the host application 50 can provide user data sent using the OTT connection 52. "User data" can be data and information described herein to implement the described functions. In one embodiment, the host computer 24 can be configured to provide control and functions to a service provider and can be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 can enable the host computer 24 to observe, monitor, control, send to and / or receive from the network node 16 and / or the wireless device 22. The processing circuit 42 of the host computer 24 may include a configuration unit 54, which is configured to enable the service provider to observe / monitor / control the network nodes 16 and / or wireless devices 22, send to the network nodes 16 and / or wireless devices 22, and / or receive from the network nodes 16 and / or wireless devices 22, etc.

[0052] The communication system 10 also includes a network node 16 disposed in the communication system 10, the network node 16 including hardware 58 that enables it to communicate with the host computer 24 and the WD 22. The hardware 58 may include: a communication interface 60 for establishing and maintaining a wired or wireless connection with the interface of different communication devices of the communication system 10; and a radio interface 62 for establishing and maintaining at least a wireless connection 64 with the WD 22 located in the coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 with the host computer 24. The connection 66 may be direct, or it may be through the core network 14 of the communication system 10 and / or through one or more intermediate networks 30 external to the communication system 10.

[0053] In the illustrated embodiment, the hardware 58 of the network node 16 also includes a processing circuit 68. The processing circuit 68 may include a processor 70 and a memory 72. Specifically, as a supplement or alternative to a processor (e.g., a central processing unit) and a memory, the processing circuit 68 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to or read from) the memory 72, which may include any type of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0054] Therefore, the network node 16 also has software 74 stored internally, for example, in the memory 72 or stored in an external memory (e.g., a database, a storage array, a network storage device, etc.) that can be accessed by the network node 16 via an external connection. The software 74 can be executed by the processing circuit 68. The processing circuit 68 can be configured to control any method and / or process described herein, and / or cause these methods and / or processes to be performed, for example, by the network node 16. The processor 70 corresponds to one or more processors 70 for performing the network node 16 functions described herein. The memory 72 is configured to store data, program software code, and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or the processing circuit 68, cause the processor 70 and / or the processing circuit 68 to perform the process described herein with respect to the network node 16. For example, the processing circuit 68 of the network node 16 may include a mobile unit 32, and the mobile unit 32 is configured for RRM mobility processing based on beam management reports.

[0055] The communication system 10 also includes the already mentioned WD 22. The WD 22 may have hardware 80, which may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0056] The hardware 80 of the WD 22 also includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. Specifically, as a supplement or alternative to a processor (e.g., a central processing unit) and a memory, the processing circuit 84 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) suitable for executing instructions. The processor 86 may be configured to access (e.g., write to or read from) the memory 88, which may include any type of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0057] Therefore, WD 22 may also include software 90, which is stored in a memory 88 at, for example, WD 22, or in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by WD 22. The software 90 may be executed by the processing circuit 84. The software 90 may include a client application 92. The client application 92 may be operated to provide services to human or non-human users via WD 22 with the support of the host computer 24. In the host computer 24, the executing host application 50 may communicate with the executing client application 92 via an OTT connection 52, which is terminated at WD 22 and the host computer 24. When providing services to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transmit both request data and user data. The client application 92 may interact with the user to generate the user data it provides.

[0058] The processing circuit 84 may be configured to control any method and / or process described herein, and / or cause such a method and / or process to be performed, for example, by the WD 22. The processor 86 corresponds to one or more processors 86 for performing the WD 22 functions described herein. The WD 22 includes a memory 88 configured to store data, program software code, and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or the processing circuit 84, cause the processor 86 and / or the processing circuit 84 to perform the process described herein with respect to the WD 22. For example, the processing circuit 84 of the wireless device 22 may include a reporting unit 34 that is configured for RRM mobility processing based on beam management reports.

[0059] In some embodiments, the internal workings of network node 16, WD 22, and host computer 24 may be as follows: Figure 2 shown, and independently, the surrounding network topology can be Figure 1 network topology.

[0060] exist Figure 2 , an OTT connection 52 is abstractly depicted to illustrate communications between a host computer 24 and a wireless device 22 via a network node 16, without explicitly involving any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the WD 22 or the service provider operating the host computer 24, or both. The network infrastructure can also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network) while the OTT connection 52 is active.

[0061] The wireless connection 64 between the WD 22 and the network node 16 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improves the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the final part. More specifically, the teachings of some of these embodiments may improve data rates, latency, and / or power consumption, thereby providing benefits such as reduced user waiting time, relaxed restrictions on file size, better responsiveness, extended battery life, and the like.

[0062] In some embodiments, a measurement process may be provided for monitoring data rates, latency, and other factors that are the subject of improvement of one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22 in response to changes in the measurement results. The measurement process and / or the network function for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 52 passes; the sensor may participate in the measurement process by providing the values ​​of the monitored quantities exemplified above, or providing the values ​​of other physical quantities from which the software 48, 90 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the network node 16, and the network node 16 may be unknown or imperceptible to this. Some such processes and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary WD signaling that facilitates the host computer 24 to measure throughput, propagation time, latency, etc. In some embodiments, the measurements may be accomplished by the software 48, 90 using the OTT connection 52 to send messages (particularly empty messages or "dummy" messages) while monitoring propagation time, errors, etc.

[0063] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data, and a communication interface 40 configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 and / or the processing circuitry 68 of the network node 16 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending transmissions to the WD 22, and / or preparing / terminating / maintaining / supporting / ending receiving transmissions from the WD 22.

[0064] In some embodiments, host computer 24 includes processing circuitry 42 and communication interface 40 configured to receive user data originating from transmissions from WD 22 to network node 16. In some embodiments, WD 22 is configured to, and / or includes a radio interface 82 and / or processing circuitry 84 configured to, perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending transmissions to network node 16, and / or preparing / terminating / maintaining / supporting / ending receiving transmissions from network node 16.

[0065] although Figure 1 and Figure 2 Various "units" such as the mobile unit 32 and the reporting unit 34 are shown as being within respective processors, but it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuit. In other words, these units may be implemented within the processing circuit in hardware or a combination of hardware and software.

[0066] Figure 3 is a diagram showing a communication system (eg, Figure 1 and Figure 2 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 2 The host computer 24, network node 16 and WD 22 described in the present disclosure are described. In the first step of the method, the host computer 24 provides user data (box S100). In an optional sub-step of the first step, the host computer 24 provides user data by executing a host application (e.g., host application 50) (box S102). In the second step, the host computer 24 initiates a transmission to the WD 22, which carries the user data (box S104). In the optional third step, in accordance with the teachings of the embodiments described throughout the present disclosure, the network node 16 sends the user data carried in the transmission initiated by the host computer 24 to the WD 22 (box S106). In the optional fourth step, the WD 22 executes a client application (e.g., client application 92) associated with the host application 50 executed by the host computer 24 (box S108).

[0067] Figure 4 is a diagram showing a communication system (eg, Figure 1 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 1 and Figure 2The host computer 24, network node 16 and WD 22 described in the method. In the first step of the method, the host computer 24 provides user data (box S110). In an optional sub-step (not shown), the host computer 24 provides user data by executing a host application (e.g., host application 50). In the second step, the host computer 24 initiates a transmission to the WD 22, which carries the user data (box S112). According to the teachings of the embodiments described throughout the present disclosure, the transmission can be transmitted via the network node 16. In an optional third step, the WD 22 receives the user data carried in the transmission (box S114).

[0068] Figure 5 is a diagram showing a communication system (eg, Figure 1 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 1 and Figure 2 The host computer 24, network node 16 and WD 22 described in the method. In the optional first step of the method, WD 22 receives input data provided by the host computer 24 (box S116). In the optional sub-step of the first step, WD 22 executes the client application 92, which provides user data in response to the received input data provided by the host computer 24 (box S118). Additionally or alternatively, in the optional second step, WD 22 provides user data (box S120). In the optional sub-step of the second step, WD provides user data by executing a client application (e.g., client application 92) (box S122). When providing user data, the executed client application can also consider user input received from the user. Regardless of the specific manner of providing user data, WD 22 can initiate transmission of user data to the host computer 24 in the optional third sub-step (box S124). In the fourth step of the method, according to the teachings of the embodiments described throughout the present disclosure, the host computer 24 receives user data sent from WD 22 (box S126).

[0069] Figure 6 is a diagram showing a communication system (eg, Figure 1 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 1 and Figure 21 . The host computer 24, network node 16, and WD 22 described herein are described. In an optional first step of the method, the network node 16 receives user data from the WD 22 (block S128) in accordance with the teachings of the embodiments described throughout the present disclosure. In an optional second step, the network node 16 initiates a transmission of the received user data to the host computer 24 (block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (block S132).

[0070] Figure 7 1 is a flow chart of an example process of RRM mobility processing based on beam management reports in the network node 16. One or more blocks described herein may be performed by one or more elements of the network node 16, such as by one or more of the processing circuit 68 (including the mobile unit 32), the processor 70, the radio interface 62, and / or the communication interface 60. The network node 16 is configured to receive (block S134) a measurement report associated with the first cell 18a from the wireless device 22. The network node 16 is configured to estimate (block S136) at least one radio resource management (RRM) metric of the first cell 18a and at least one second cell 18b based on the measurement report and historical information. The network node 16 is configured to perform (block S138) an RRM mobility process based on the estimated RRM metric.

[0071] In some embodiments, the first cell 18a is a serving cell, and the at least one second cell 18b comprises a neighboring cell of the first cell 18a. In some embodiments, the history information comprises at least one of: previously reported layer 1 (L1) measurements and / or beam management (BM) measurements associated with the first cell 18a and / or the at least one second cell 18b, and location information associated with at least one wireless device 22 in the first cell 18a and / or the at least one second cell 18b.

[0072] In some embodiments, estimating at least one RRM metric is based on a machine learning (ML) model, wherein the ML is trained based on historical information. In some embodiments, the network node 16 is further configured to determine location information associated with the wireless device 22, and estimating at least one RRM metric is also based on the determined location information. In some embodiments, the network node 16 is further configured to: configure an RRM report configuration including and / or indicating a first event criterion for the wireless device 22, wherein performing the RRM mobility procedure is initiated after the first event criterion is met based on the detection of a fault and / or an emergency (for example, a specific type of fault and / or emergency in this context can be determined based on the RRM report configuration and / or another configuration received by the network node 16 from another network node 16 and / or the wireless device 22 and / or pre-configured in the network node 16) or before the first event criterion is met based on the absence of a fault and / or an emergency. In some embodiments, the measurement report is based on at least one of a beam management BM measurement and a layer 1 (L1) quality measurement. In some embodiments, performing the RRM mobility procedure includes triggering a handover procedure from the first cell 18a to one of the at least one second cell 18b. In some embodiments, the measurement report does not include RRM measurements (eg, the RRM measurement report is limited to non-RRM measurements).

[0073] Figure 8 1 is a flowchart of an example process of RRM mobility processing based on beam management reporting in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, for example, by one or more of the processing circuit 84 (including the reporting unit 34), the processor 86, the radio interface 82, and / or the communication interface 60. The wireless device 22 is configured to perform a measurement of a first cell 18a (block S140). The wireless device 22 is configured to send (block S142) a measurement report based on the measurement of the first cell 18a to the network node 22. The wireless device 22 is configured to receive (block S144) an RRM mobility process indication from the network node 16, wherein the RRM mobility process indication is based on at least one RRM metric estimated for the first cell 18a and at least one second cell 18b, wherein the estimation is based on the measurement report and the historical information. The wireless device 22 is configured to perform (block S146) an RRM mobility process based on the estimated RRM metric.

[0074] In some embodiments, the first cell 18a is a serving cell, and the at least one second cell 18b comprises a neighboring cell of the first cell 18a. In some embodiments, the history information comprises at least one of: previously reported layer 1 (L1) measurements and / or beam management (BM) measurements associated with the first cell 18a and / or the at least one second cell 18b, and location information associated with at least one wireless device 22 in the first cell 18a and / or the at least one second cell 18b.

[0075] In some embodiments, estimating at least one RRM metric is based on a machine learning (ML) model, wherein the ML is trained based on historical information. In some embodiments, the wireless device 22 is further configured to send location information associated with the wireless device 22 to the network node 16, wherein estimating at least one RRM metric is further based on the location information.

[0076] In some embodiments, the wireless device 22 is further configured to receive an RRM reporting configuration including and / or indicating a first event criterion from the network node 16, wherein performing the RRM mobility procedure is initiated after the first event criterion is met based on the detection of a failure and / or emergency situation (e.g., the specific type of failure and / or emergency situation in this context can be determined based on the RRM reporting configuration and / or another configuration received by the network node 16 and / or preconfigured in the wireless device 22) or before the first event criterion is met based on the absence of a detected failure and / or emergency situation. In some embodiments, the measurement report is based on at least one of a beam management BM measurement and a layer 1 (L1) quality measurement. In some embodiments, performing the RRM mobility procedure includes performing a handover procedure from the first cell 18a to one of the at least one second cell 18b. In some embodiments, the measurement report does not include RRM measurements (e.g., the RRM measurement report is limited to non-RRM measurements).

[0077] Having described the general process flow of the arrangements of the present disclosure and provided examples of hardware and software arrangements for implementing the processes and functions of the present disclosure, the following section provides details and examples of arrangements for RRM mobility processing based on beam management reports.

[0078] For example, an embodiment of the present disclosure provides a method for RRM HO processing implemented in a network node 16. The method includes: determining a first relationship between one or more first L1 quality reports of a first cell and one or more first RRM quality reports of a first cell 18a and one or more second cells 18b (e.g., training an ML model); receiving one or more second L1 quality reports from a wireless device 22; estimating a second RRM quality metric of the first cell 18a and (one or more) second cells 18b of the wireless device 22 based on the second L1 quality report and the first relationship; and triggering a HO process from the first cell to the second cell of the wireless device 22, for example, based on the second RRM quality metric.

[0079] Alternatively, (eg, the network node 16) may provide an RRM reporting configuration to the wireless device 22, the RRM reporting configuration including, for example, a first event criterion, wherein the triggering includes initiating a HO procedure before the first event criterion is met.

[0080] Some embodiments of the present disclosure may advantageously provide a network node 16 (eg, gNB) that triggers a HO without having to receive an event report and / or an SSB quality report of a candidate cell 18 while receiving a BM report.

[0081] Some embodiments of the present disclosure can achieve one or more advantages that cannot be achieved by existing methods and systems, such as:

[0082] - For example, active HO triggering according to one or more embodiments of the present disclosure may improve mobility robustness;

[0083] - Predicting the remaining time for HO and initiating early preparations can reduce the time required for the actual HO process;

[0084] - Minimal event reporting may reduce interference in the UL and / or reduce UL resource usage; and

[0085] - Reduced RRM measurements and / or reduced reporting and / or no reporting by the wireless device 22 enables the wireless device 22 to save energy.

[0086] In some embodiments of the present disclosure, the network node 16 (e.g., gNB) may utilize a relationship in which multiple measurement processes in the same environment may generally provide correlated results, e.g., BM and RRM mobility measurements at a specific location may provide mutually consistent and / or correlated outputs. Therefore, when prior information about their relationship is available, for example, RRM measurement results may be predicted or estimated based on BM measurements in the same area, because BM measurements may provide a higher resolution spatial resolution from which lower resolution RRM related information may be extracted.

[0087] Based on this relationship, the network node 16 (e.g., gNB) may not need detailed RRM measurement information, but may make RRM decisions based on the BM measurements reported by the wireless device 22. The wireless device 22 may then use the prior information about the BM and RRM relationship to estimate corresponding RRM measurements, and may use these estimates as input to an RRM process (e.g., an RRM process according to known methods, or a modified RRM process as described herein).

[0088] Although in principle, according to some embodiments of the present disclosure, RRM measurements and reports can be completely omitted, some embodiments of the present disclosure (e.g., in actual implementations) may still use some RRM measurements and reports and / or other procedures (such as conditional HO) to configure the wireless device 22. For example, in at least one embodiment, events and conditions may still be set so that they are not usually (e.g., rarely) triggered, but can act as a safety net in addition to pre-trained RRM event predictions (e.g., event A3 (e.g., where the neighbor cell 18b becomes better than the offset relative to the serving cell 18a)). This can achieve energy savings for the wireless device 22 by reducing event reporting and / or reducing RRM measurements.

[0089] Fig. 9A and Fig. 9B Depicted are sequence diagrams illustrating two example embodiments of the present disclosure.

[0090] exist Fig. 9A In the example shown, the wireless device 22 communicates with the serving network node 16a and the target network node 16b (e.g., a serving base station and a target base station). The wireless device 22 monitors the signal strength of the serving cell 18a and the neighboring cells 18b, 18c, etc. (e.g., continuously, periodically, etc.), and the wireless device 22 sends a report to the serving network node 16a. In step 1, an A3 event occurs / triggers. In step 2, a trigger time (TTT) (which can be configured at the wireless device 22 and / or by the network node 16, for example) elapses. Once the time has elapsed, in step 3, the wireless device 22 sends a measurement report to the serving network node 16a. In step 4, the serving network node 16a determines a HO decision. In step 5, based on the determination, the serving network node 16a sends a HO request to the target network node 16b. In step 6, the target network node 16b responds to the serving network node 16a with a HO request acknowledgement (ACK). In step 7, the serving network node 16a sends a HO command to the wireless device 22.

[0091] exist Fig. 9BIn the example shown, the wireless device 22 communicates with the serving network node 16a and the target network node 16b (e.g., a serving base station and a target base station). The wireless device 22 monitors (e.g., continuously, periodically, etc.) the signal strength of the serving cell 18a and the neighboring cells 18b, 18c, etc., and the wireless device 22 sends a report to the serving network node 16a. In step 1, an A3 event occurs / triggers. In step 2, a trigger time (TTT) (which may be configured at the wireless device 22 and / or by the network node 16, for example) elapses. Fig. 9A The example is different. Fig. 9B The example may not include the wireless device 22 sending a measurement report to the serving network node 16a. Fig. 9B In step 3, the serving network node 16a determines a HO decision (e.g., based on the ML model). In step 4, based on the determination, the serving network node 16a sends a HO request to the target network node 16b. In step 5, the target network node 16b responds to the serving network node 16a with a HO request acknowledgement (ACK). In step 6, the serving network node 16a sends a HO command to the wireless device 22.

[0092] In some embodiments of the present disclosure, BM measurement information may alternatively or additionally be used to predict the mobility event occurrence time, and the HO process may be initiated in advance, which may result in a shorter transition time in some cases.

[0093] Fig. 10A and Fig. 10B is a sequence diagram illustrating an example embodiment of the present disclosure.

[0094] exist Fig. 10A In the example shown, during the 3GPP preparation phase of the conventional 5G handover process, the wireless device 22 measures the signals of the serving cell 18a and the neighboring cells 18b, 18c, etc., and evaluates whether any of the measured signals meets the entry criteria of the HO event. Before time T0, the wireless device 22 (e.g., continuously, periodically, etc.) monitors the signal strength of the serving cell 18a and the neighboring cells 18b, 18c, etc., and sends a report back to the serving network node 16a. In step 1, at time T0, an A3 event occurs. In step 2, the TTT timer elapses. In step 3, an A3 event completion message is sent from the wireless device 22 to the serving network node 16a, and the A3 event completion message may include a measurement report. In step 4, the serving network node 16a determines the HO decision. In step 5, the serving network node 16a sends a HO request to the target network node 16b. In step 5, the target network node 16b sends a HO request response ACK to the serving network node 16a. In step 7 , the serving network node 16 a sends a HO command to the wireless device 22 .

[0095] exist Fig. 10B In the illustrated example, reduced total HO processing time may be achieved by triggering the HO decision process early (step 1) using a configurable, ML-authorized Time to Event Criteria Satisfied (TTECF) parameter (sometimes referred to as a Time to Predicted Event (TTPEP) parameter, which indicates a predicted start point of a countdown to T0, where the HO event criteria are satisfied), the TTPEP parameter determining a start point of an early evaluation, indicated in the figure by a dashed arrow as an Early Scheduled Evaluation Time Frame (ESETF), earlier than the actual A3 event condition at time T0 is satisfied. Prior to time T0, the wireless device 22 monitors (e.g., continuously, periodically, etc.) the signal strength of the serving cell 18a and neighboring cells 18b, 18c, etc., and sends reports back to the serving network node 16a. In step 1, prior to time T0, a TTECF parameter determined based on the ML model begins to expire. In step 2, the serving network node 16a determines a HO decision. At time T0 (step 3), an A3 event occurs. In step 4, the TTT timer expires. In step 5, an A3 event complete message is sent from the wireless device 22 to the serving network node 16a, which may include a measurement report, and the serving network node 16a sends a HO request to the target network node 16b (e.g., as a continuation of step 2). In step 6, the target network node 16b sends a HO request ACK to the serving network node 16a. In step 7, the serving network node 16a sends a HO command to the wireless device 22.

[0096] In some embodiments, the RRM and BM measurements may belong to the same frequency band or frequency range (FR), or may belong to different frequency bands / FRs, for example, FR2 BM results may be used to control FR1 RRM mobility. The mapping of FR BM results to FR RRM mobility (e.g., FR3 BM results are used to control FR1 RRM mobility, FR4 BM results are used to control FR2 RRM mobility, etc.) may be configured, for example, at and / or by the network node 16 and / or the wireless device 22.

[0097] In some embodiments, RRM event predictions may be based on previously learned relationships between BM measurements of the serving cell 18a and RRM mobility measurements of the serving cell 18a and candidate cells 18b, 18c, etc., e.g., at a certain location or along a certain route (e.g., a road). This learning may be accomplished by training (e.g., a fingerprint-based ML model), and estimates of RRM outcomes in online operation may be derived from inference using the model.

[0098] Fig.11An example of a BM-RRM relationship according to some embodiments of the present disclosure is shown. In the RRM mobility measurement domain, a wireless device 22 at a particular location in its serving cell 18a can be associated with SSB measurements (e.g., RSRP) of cells 18a, 18b, and 18c. At the same time, in the BM measurement domain, the wireless device 22 is also associated with multiple CSI-RS metrics (e.g., L1-RSRP) in cell 18a. In some embodiments, the RRM mobility and BM measurement fingerprints of the wireless device 22 can be unique and / or distinguishable in different parts of the cell 18, and a specific RRM fingerprint can be linked to a BM fingerprint.

[0099] exist Fig.11 In the example, it is assumed that a single SSB is used per cell, but it should be understood that according to embodiments of the present disclosure, multiple SSBs may also be used, for example, which may create certain spatial resolutions that may still be coarser than the resolution captured from CSI-RS measurements.

[0100] Fig.12 is a flow chart illustrating an example process flow in a network node 16 (e.g., a gNB) according to some embodiments of the present disclosure (e.g., where the process is transparent to the wireless device 22). Some embodiments of the present disclosure may provide a method for RRM HO processing in the network node 16, including, for example, determining a first relationship between a first L1 quality report of a first cell 18a and a first RRM quality report of the first cell 18a and one or more second cells 18b. One or more second L1 quality reports may be received from the wireless device 22. A second RRM quality metric of the first cell 18a and the (one or more) second cell 18b of the wireless device 22 may be estimated based on the second L1 quality report and the first relationship. The network node 16a may trigger a HO process from the first cell 18a to the second cell 18b of the wireless device 22 based on the second RRM quality metric. In some embodiments, the network node 16 (and / or some other network entity, such as a host computer 24) provides an RRM report configuration including a first event criterion to the wireless device 22. The triggering may include initiating the HO process before the first event criterion is met.

[0101] Derivation of RRM mobility events

[0102] refer to Fig.12 In step 1100, the network node 16a (e.g., serving gNB) configures the wireless device 22 to perform a BM procedure, optionally including one or more of a CSI-RS resource description, a measurement plan, a reporting criteria description, a report signaling configuration, etc. The BM configuration may be equivalent to a conventional BM configuration, or it may be extended to obtain BM CSI-RS measurement reports with higher resolution and / or more frequent.

[0103] In step 1110, the network node 16 receives wireless device 22 reports from BM L1 measurements (or in general, measurements with higher spatial resolution) according to a separately provided BM measurement configuration. These measurements may use, for example, CSI-RS, whose resources are included in the BM measurement configuration in step 1110.

[0104] In step 1120, the network node 16 uses previously established / measured / received / determined / etc. information about the relationship of BM and RRM measurements for different possible wireless device 22 locations to derive / estimate / predict relevant RRM metrics from the BM measurement reports. In one embodiment, the network node 16 may estimate RRM measurements for the serving cell 18a and additional neighboring cells 18b, 18c, etc. In some embodiments, the wireless device 22 may estimate the occurrence of an RRM event (e.g., a reporting event or a conditional HO triggering event) according to a conventional / default / legacy HO criterion.

[0105] In some embodiments, the derivation / estimation can take the form of performing ML inference using a previously trained ML model. More details on how to prepare / generate / determine / configure / train / etc. such a model are provided herein.

[0106] Still reference Fig.12 In step 1130, the network node 16 uses the estimated RRM metric to trigger the execution of a conventional RRM mobility procedure, such as triggering a HO. The criteria or threshold used for the trigger may be the same or comparable / equivalent to conventional criteria used for mobility management. In one embodiment, the network node 16 may detect that the event has occurred and respond immediately and accordingly. In another embodiment, the network node 16 may detect that the event is about to occur and predict the remaining time for the event. The network node 16 may then initiate appropriate preparations, such as preparations for a HO procedure, including inter-network node 16 (e.g., inter-gNB) signaling, buffer content or signal flow replication, etc.

[0107] Note that steps 1100, 1110, and 1130 may include processes similar to those performed in conventional implementations, while in some embodiments the configuration of these processes may be modified, for example, to make them more suitable for exploiting learned BM-RRM relationships.

[0108] Conventional RRM mobility base layer

[0109] Embodiments of the present disclosure may include an optional second aspect, wherein the wireless device 22 may be configured with conventional RRM procedures (eg, measurements, reporting, and / or mobility events) as a backup or fallback mechanism to improve the robustness of the learning-based approach.

[0110] Still reference Fig.12 In optional step 1105, the network node 16 further configures the wireless device 22 to perform an RRM mobility procedure, optionally including one or more of an RRM measurement object description (e.g., SSBs in the serving cell 18a and neighboring cells 18b, 18c, etc.), a measurement plan, a reporting event / criteria description, a report signaling configuration, a conditional HO configuration, etc. The configuration may be determined / selected / etc. such that, for example, a mobility event may be triggered later than a regular / legacy mobility / HO configuration.

[0111] In optional step 1140, the network node 16 receives RRM reports from the wireless device 22 according to the configuration in step 1105, and in step 1150, the network node 16 may trigger RRM mobility procedures, such as HO, based on these reports. Steps 1140 to 1150 may differ from normal operation in that reports are received and / or procedures are triggered only when the need for, for example, HO is more urgent (e.g., based on one or more conditions / indications indicating a high priority / urgency HO). This may act as a safety net in that under normal conditions, steps 1120 to 1130 may ensure that the required procedures are triggered based on conventional inter-cell quality criteria, and steps 1140 to 1150 take effect only when steps 1120 to 1130 do not react appropriately (e.g., due to data drift relative to a previously trained ML model).

[0112] In some embodiments, wireless devices configured with a regular conditional HO configuration will be triggered accordingly.

[0113] ML model training

[0114] In some embodiments, the ML model of the network node 16 may be trained using measurement data from past / historical measurement occasions (e.g., Fig.12 The model used in step 1120 of the present invention is used to prepare it. The RRM measurement results of the current cell 18a and / or the neighboring cells 18b, 18c, etc. and the BM measurement results of the current cell 18a are used as training data, and the model is trained to, for example, minimize the loss function between the observed and estimated RRM measurement results of the serving cell and the neighboring cells when the BM measurement values ​​are provided as input. Alternatively or additionally, the training can be configured so that the ML model generates an event trigger signal for, for example, event reporting and / or conditional HO initiation.

[0115] In one set of embodiments, the ML model of the network node 16 may be trained cell-specifically. This may be achieved, for example, by collecting BM reports and RRM mobility reports from the wireless devices 22 in the cell 18a, which are used to train a cell-specific model representing the BM to RRM metric mapping of the cell 18, wherein the measurements and the ML model are associated with the corresponding cell 18.

[0116] In one embodiment, offline training is used, such as training performed at the network node 16 provider location or locally in the network node 16. In another embodiment, online training is used, where the network node 16 collects current BM and RRM mobility measurements and trains or retrains the model to improve the RRM measurement estimates. A combination of offline training and online training may be utilized.

[0117] Example scenarios according to embodiments of the present disclosure

[0118] For example, in one scenario (e.g., a legacy setup), the wireless device 22 may be configured with mobility events and RRM measurements every 40 ms, such that if the difference between the RSRP of the serving cell 18a and the candidate cell 18b is less than 3 dB, a report to the serving network node 16a is triggered. Thus, the wireless device 22 may perform measurements at a rate of 40 ms and report situations where the candidate cell 18b is within 3 dB or less of the serving cell 18a, and the network node 16a may determine that once the reported or otherwise estimated difference is less than 0 dB (i.e., the candidate cell 18b becomes stronger than the current serving cell 18a), the wireless device 22 should perform a HO to such a candidate cell 18b.

[0119] In some embodiments of the present disclosure, the wireless device 22 may be configured with BM measurements every 40ms with continuous best beam and / or additional beam L1-RSRP reporting. The wireless device 22 may not be configured with RRM mobility reporting. Using a previously trained ML model, the network node 16 uses the BM report of the wireless device 22 to determine that a mobility event corresponding to a certain serving cell 18a / candidate cell 18b RSRP relationship may have occurred. Based on the estimated event, the network node 16 may trigger a HO to the candidate cell 18b.

[0120] This scenario may illustrate advantages of embodiments of the present disclosure, such as: (1) the wireless device 22 does not need to perform RRM measurements, (2) the wireless device 22 does not need to perform event reporting, and / or (3) the HO decision may be made based on measurement data with higher spatial resolution.

[0121] In some embodiments, the wireless device 22 may additionally be configured with mobility events and RRM mobility measurements every 120 ms, such that a report to the serving network node 16 is triggered if the difference between the RSRP of the serving cell 18 a and the candidate cell 18 b is less than -1 dB (i.e., the candidate cell 18 b becomes at least 1 dB stronger than the current serving cell 18 a).

[0122] In some embodiments, for example: (1) the wireless device 22 performs less frequent RRM measurements (e.g., compared to existing systems) and / or (2) the wireless device 22 performs event reporting only in exceptional cases when BM-based reporting does not result in a HO under conditions that reach traditional event levels. The improved spatial resolution of the measurements can be maintained and a safety net (i.e., fallback / default backup process) can additionally be provided.

[0123] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Therefore, the concepts described herein may take the form of all-hardware embodiments, all-software embodiments, or embodiments combining hardware and software aspects, which are collectively referred to herein as "circuits" or "modules". Any process, step, action, and / or function described herein may be performed by and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. In addition, the present disclosure may take the form of a computer program product on a tangible computer-usable storage medium having a computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer-readable medium may be utilized, including a hard disk, a CD-ROM, an electrical storage device, an optical storage device, or a magnetic storage device.

[0124] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It will be understood that each block shown in the flowcharts and / or block diagrams, and combinations of multiple blocks shown in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer (thereby creating a special-purpose computer), a processor of a special-purpose computer, or other programmable data processing device for producing a machine, so that the instructions (executed via the processor of the computer or other programmable data processing device) create a computer program for implementing the flowcharts and / or block diagrams. Figure 1 means for performing the functions / actions specified in one or more boxes.

[0125] These computer program instructions may also be stored in a computer-readable memory or storage medium that instructs a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory generate instructions including implementing the flowcharts and / or block diagrams. Figure 1 An article of manufacture that instructs means for performing the functions / actions specified in one or more blocks.

[0126] Computer program instructions may also be loaded into a computer or other programmable data processing apparatus so that a series of operable steps are executed on the computer or other programmable apparatus to generate a computer-implemented process, so that the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions / actions specified in one or more boxes of the flowchart and / or block diagram.

[0127] It should be understood that the functions and / or actions marked in the blocks may not occur in the order marked in the operating instructions. For example, depending on the functions / actions involved, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in the opposite order. Although some figures include arrows on the communication paths to indicate the primary direction of communication, it will be understood that communication may occur in the opposite direction of the indicated arrows.

[0128] Computer program code for performing the operations of the concepts described herein may be written in an object-oriented programming language such as Python, Java® or C++. However, computer program code for performing the operations of the present disclosure may also be written in a conventional procedural programming language such as the "C" programming language. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter case, the remote computer may be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or an external computer may be connected (e.g., via the Internet using an Internet service provider).

[0129] In conjunction with the above description and the accompanying drawings, many different embodiments are disclosed herein. It will be understood that it would be unduly repetitive and confusing to describe and illustrate verbatim every combination and subcombination of these embodiments. Therefore, all embodiments may be combined in any manner and / or combination, and this specification including the accompanying drawings will be construed to construct a complete written description of all combinations and subcombinations of the embodiments described herein and the manner and process of making and using them, and will support the rights and interests claiming any such combination or subcombination.

[0130] Those skilled in the art will recognize that the embodiments described herein are not limited to what has been specifically shown and described above. In addition, unless otherwise mentioned above, it should be noted that all drawings are not drawn to scale. In view of the above teachings, various modifications and changes can be made.

[0131] Example :

[0132] Embodiment A1. A network node configured to communicate with a wireless device in a first cell, the network node being configured to and / or comprising a radio interface and / or comprising a processing circuit configured to:

[0133] receiving, from a wireless device, a measurement report associated with the first cell;

[0134] estimating at least one radio resource management (RRM) metric for the first cell and at least one second cell based on the measurement report and the historical information; and

[0135] The RRM mobility procedure is performed based on the estimated RRM metric.

[0136] Embodiment A2. The network node of embodiment A1, wherein the first cell is a serving cell and the at least one second cell comprises a neighboring cell of the first cell.

[0137] Embodiment A3. The network node of any one of Embodiments A1 and A2, wherein the historical information includes at least one of the following:

[0138] previously reported layer 1 (L1) measurements and / or beam management (BM) measurements associated with the first cell and / or at least one second cell; and

[0139] Location information associated with at least one wireless device in the first cell and / or at least one second cell.

[0140] Embodiment A4. A network node according to any one of embodiments A1 to A3, wherein estimating at least one RRM metric is based on a machine learning (ML) model, which is trained based on historical information.

[0141] Embodiment A5. The network node of embodiment A4, wherein the network node is further configured to:

[0142] determining location information associated with the wireless device; and

[0143] Estimating at least one RRM metric is also based on the determined location information.

[0144] Embodiment A6. The network node of any one of embodiments A1 to A5, wherein the network node is further configured to: configure an RRM reporting configuration including and / or indicating a first event criterion for the wireless device, and performing an RRM mobility procedure is one of:

[0145] Initiated after first event criteria are met based on detection of a fault and / or emergency situation; and

[0146] Initiated before said first event criteria are met based on no fault and / or emergency situation being detected.

[0147] Embodiment A7. The network node of any one of Embodiments A1 to A6, wherein the measurement report is based on at least one of:

[0148] Beam management BM measurements; and

[0149] Layer 1 (L1) quality measurement.

[0150] Embodiment A8. The network node of any one of Embodiments A1 to A7, wherein performing the RRM mobility procedure comprises triggering a handover procedure from the first cell to one of the at least one second cell.

[0151] Embodiment A9. The network node of any one of Embodiments A1 to A8, wherein the measurement report does not include RRM measurements.

[0152] Embodiment B1. A method implemented in a network node, the network node being configured to communicate with a wireless device in a first cell, the method comprising:

[0153] receiving (block S134 ) a measurement report associated with the first cell from the wireless device;

[0154] estimating (block S136) at least one radio resource management (RRM) metric for the first cell and at least one second cell based on the measurement report and the historical information; and

[0155] An RRM mobility procedure is performed (block S138) based on the estimated RRM metric.

[0156] Embodiment B2. The method according to embodiment B1, wherein the first cell is a serving cell and the at least one second cell includes a neighboring cell of the first cell.

[0157] Embodiment B3. The method of any one of embodiments B1 and B2, wherein the historical information includes at least one of the following items:

[0158] previously reported layer 1 (L1) measurements and / or beam management (BM) measurements associated with the first cell and / or at least one second cell; and

[0159] Location information associated with at least one wireless device in the first cell and / or at least one second cell.

[0160] Embodiment B4. A method according to any one of embodiments B1 to B3, wherein estimating at least one RRM metric is based on a machine learning (ML) model that is trained based on historical information.

[0161] Embodiment B5. The method according to embodiment B4, further comprising:

[0162] determining location information associated with the wireless device; and

[0163] Estimating at least one RRM metric is also based on the determined location information.

[0164] Embodiment B6. The method of any one of embodiments B1 to B5, further comprising: configuring an RRM report configuration for the wireless device including and / or indicating a first event criterion, performing an RRM mobility procedure is one of:

[0165] Initiated after first event criteria are met based on detection of a fault and / or emergency situation; and

[0166] Initiated before said first event criteria are met based on no fault and / or emergency situation being detected.

[0167] Embodiment B7. The method of any one of Embodiments B1 to B6, wherein the measurement report is based on at least one of:

[0168] Beam management BM measurements; and

[0169] Layer 1 (L1) quality measurement.

[0170] Embodiment B8. The method of any one of embodiments B1 to B7, wherein performing the RRM mobility procedure comprises triggering a handover procedure from the first cell to one of the at least one second cell.

[0171] Embodiment B9. A method as described in any one of embodiments B1 to B8, wherein the measurement report does not include RRM measurements.

[0172] Embodiment C1. A wireless device configured to communicate with a network node in a first cell, the wireless device configured to and / or comprising a radio interface and / or a processing circuit configured to:

[0173] performing measurement of a first cell;

[0174] sending a measurement report based on the measurement of the first cell to a network node;

[0175] receiving a radio resource management (RRM) mobility procedure indication from the network node, the RRM mobility procedure indication being based on at least one estimated RRM metric of the first cell and at least one second cell, the estimation being based on the measurement report and the history information; and

[0176] The RRM mobility procedure is performed based on the estimated RRM metric.

[0177] Embodiment C2. The wireless device of Embodiment C1, wherein the first cell is a serving cell and the at least one second cell comprises a neighboring cell of the first cell.

[0178] Embodiment C3. The wireless device of any one of Embodiments C1 and C2, wherein the history information includes at least one of the following:

[0179] previously reported layer 1 (L1) measurements and / or beam management (BM) measurements associated with the first cell and / or at least one second cell; and

[0180] Location information associated with at least one wireless device in the first cell and / or at least one second cell.

[0181] Embodiment C4. A wireless device according to any one of embodiments C1 to C3, wherein estimating at least one RRM metric is based on a machine learning (ML) model, which is trained based on historical information.

[0182] Embodiment C5. The wireless device of embodiment C4, wherein the wireless device is further configured to:

[0183] Location information associated with the wireless device is sent to the network node, and estimating at least one RRM metric is further based on the location information.

[0184] Embodiment C6. The wireless device of any one of embodiments C1 to C5, wherein the wireless device is further configured to receive an RRM reporting configuration including and / or indicating a first event criterion from a network node, and performing an RRM mobility procedure is one of:

[0185] Initiated after first event criteria are met based on detection of a fault and / or emergency situation; and

[0186] Initiated before said first event criteria are met based on no fault and / or emergency situation being detected.

[0187] Embodiment C7. The wireless device of any one of Embodiments C1 to C6, wherein the measurement report is based on at least one of:

[0188] Beam management BM measurements; and

[0189] Layer 1 (L1) quality measurement.

[0190] Embodiment C8. The wireless device of any one of embodiments C1 to C7, wherein performing the RRM mobility procedure comprises performing a handover procedure from the first cell to one of the at least one second cell.

[0191] Embodiment C9. The wireless device of any one of embodiments C1 to C8, wherein the measurement report does not include RRM measurements.

[0192] Embodiment D1. A method implemented in a wireless device, the wireless device being configured to communicate with a network node in a first cell, the method comprising:

[0193] Performing (block S140 ) measurement of the first cell;

[0194] sending (block S142) a measurement report based on the measurement of the first cell to a network node;

[0195] receiving (block S144) from the network node a radio resource management (RRM) mobility procedure indication based on an estimated at least one RRM metric of the first cell and at least one second cell, the estimation being based on the measurement report and the history information; and

[0196] An RRM mobility procedure is performed (block S146) based on the estimated RRM metric.

[0197] Embodiment D2. A method according to embodiment D1, wherein the first cell is a serving cell and the at least one second cell includes a neighboring cell of the first cell.

[0198] Embodiment D3. A method according to any one of embodiments D1 and D2, wherein the historical information includes at least one of the following:

[0199] previously reported layer 1 (L1) measurements and / or beam management (BM) measurements associated with the first cell and / or at least one second cell; and

[0200] Location information associated with at least one wireless device in the first cell and / or at least one second cell.

[0201] Embodiment D4. A method according to any one of embodiments D1 to D3, wherein estimating at least one RRM metric is based on a machine learning (ML) model that is trained based on historical information.

[0202] Embodiment D5. A method according to embodiment D4, wherein the method further comprises sending location information associated with the wireless device to a network node, and estimating at least one RRM metric is also based on the location information.

[0203] Embodiment D6. The method of any one of embodiments D1 to D5, wherein the method further comprises receiving an RRM report configuration including and / or indicating a first event criterion from a network node, and performing an RRM mobility procedure is one of:

[0204] Initiated after first event criteria are met based on detection of a fault and / or emergency situation; and

[0205] Initiated before first event criteria are met based on no fault and / or emergency conditions being detected.

[0206] Embodiment D7. The method of any one of embodiments D1 to D6, wherein the measurement report is based on at least one of the following:

[0207] Beam management BM measurements; and

[0208] Layer 1 (L1) quality measurement.

[0209] Embodiment D8. A method according to any one of embodiments D1 to D7, wherein performing the RRM mobility process includes: performing a handover process from the first cell to one of the at least one second cell.

[0210] Embodiment D9. A method according to any one of embodiments D1 to D8, wherein the measurement report does not include RRM measurements.

Claims

1. A network node (16a) configured to communicate with a wireless device (22a) in a first cell (18a), the network node (16a) being configured to: receiving a measurement report associated with the first cell (18a) from the wireless device (22a); estimating at least one radio resource management, RRM, metric of the first cell (18a) and at least one second cell (18b, 18c) based on the measurement report and the historical information; as well as performing RRM mobility procedures based on the estimated RRM metrics, and / or The network node (16a) comprises a radio interface (62) and / or comprises a processing circuit (68), the processing circuit (68) being configured to: receiving a measurement report associated with the first cell (18a) from the wireless device (22a); estimating at least one radio resource management, RRM, metric of the first cell (18a) and at least one second cell (18b, 18c) based on the measurement report and the historical information; as well as The RRM mobility procedure is performed based on the estimated RRM metric.

2. The network node (16a) according to claim 1, wherein: The first cell (18a) is a serving cell, and the at least one second cell (18b, 18c) comprises a neighboring cell of the first cell (18a).

3. The network node (16a) according to any one of claims 1 and 2, wherein: The historical information includes at least one of the following items: previously reported Layer 1 (L1) measurements and / or beam management BM measurements associated with said first cell (18a) and / or said at least one second cell (18b, 18c); and Location information associated with at least one wireless device (22a, 22b) in the first cell (18a) and / or the at least one second cell (18b, 18c).

4. The network node (16a) according to any one of claims 1 to 3, wherein: Estimating the at least one RRM metric is based on a machine learning (ML) model, the ML being trained based on the historical information.

5. The network node (16a) according to claim 4, wherein: The network node (16a) is further configured to: determining location information associated with the wireless device (22a); and Estimating the at least one RRM metric is also based on the determined location information.

6. The network node (16a) according to any one of claims 1 to 5, wherein: The network node (16a) is further configured to: configure an RRM report configuration including and / or indicating a first event criterion for the wireless device (22a), and performing the RRM mobility procedure complies with one of the following items: Initiated after the first event criteria are met based on detection of a fault and / or emergency situation; and Initiated before said first event criteria are met based on no fault and / or emergency situation being detected.

7. The network node (16a) according to any one of claims 1 to 6, wherein: The measurement report is based on at least one of the following: Beam management BM measurements; and Layer 1 "L1" quality measurement.

8. The network node (16a) according to any one of claims 1 to 7, wherein: Performing the RRM mobility procedure comprises triggering a handover procedure from the first cell (18a) to one of the at least one second cell (18b, 18c).

9. The network node (16a) according to any one of claims 1 to 8, wherein: The measurement report does not include RRM measurements.

10. A method implemented in a network node, the network node being configured to communicate with a wireless device in a first cell, the method comprising: receiving ( S134 ) a measurement report associated with the first cell from the wireless device; estimating (S136) at least one radio resource management, RRM, metric of the first cell and at least one second cell based on the measurement report and the historical information; as well as An RRM mobility procedure is performed (S138) based on the estimated RRM metric.

11. The method according to claim 10, wherein: The first cell is a serving cell, and the at least one second cell includes a neighboring cell of the first cell.

12. The method according to any one of claims 10 and 11, wherein: The historical information includes at least one of the following items: previously reported Layer 1 (L1) measurements and / or beam management BM measurements associated with said first cell and / or said at least one second cell; and Location information associated with at least one wireless device in the first cell and / or the at least one second cell.

13. The method according to any one of claims 10 to 12, wherein: Estimating ( S136 ) the at least one RRM metric is based on a machine learning (ML) model, the ML being trained based on the historical information.

14. The method according to claim 13, further comprising: determining location information associated with the wireless device; as well as Estimating (S136) the at least one RRM metric is also based on the determined location information.

15. The method according to any one of claims 10 to 14, further comprising: Configuring an RRM reporting configuration including and / or indicating a first event criterion for the wireless device, and performing the RRM mobility procedure complies with one of the following items: Initiated after the first event criteria are met based on detection of a fault and / or emergency situation; and Initiated before said first event criteria are met based on no fault and / or emergency situation being detected.

16. The method according to any one of claims 10 to 15, wherein: The measurement report is based on at least one of the following: Beam management BM measurements; and Layer 1 "L1" quality measurement.

17. The method according to any one of claims 10 to 16, wherein: Executing (S146) the RRM mobility procedure includes triggering a handover procedure from the first cell to one of the at least one second cell.

18. The method according to any one of claims 10 to 17, wherein: The measurement report does not include RRM measurements.

19. A wireless device (22a) configured to communicate with a network node (16a) in a first cell (18a), the wireless device (22a) being configured to: performing measurement on the first cell; sending a measurement report based on the measurement of the first cell (18a) to the network node (16a); receiving a radio resource management (RRM) mobility procedure indication from the network node (16a), the RRM mobility procedure indication being based on at least one RRM metric of the first cell (18a) and at least one second cell (18b, 18c) estimated based on the measurement report and history information; as well as performing RRM mobility procedures based on the estimated RRM metrics, and / or The wireless device (22a) comprises a radio interface (82) and / or a processing circuit (84), wherein the processing circuit (84) is configured to: performing measurement on the first cell; sending a measurement report based on the measurement of the first cell (18a) to the network node (16a); receiving a radio resource management (RRM) mobility procedure indication from the network node (16a), the RRM mobility procedure indication being based on at least one RRM metric of the first cell (18a) and at least one second cell (18b, 18c) estimated based on the measurement report and history information; as well as The RRM mobility procedure is performed based on the estimated RRM metric.

20. The wireless device (22a) of claim 19, wherein: The first cell (16a) is a serving cell, and the at least one second cell (18b, 18c) comprises a neighboring cell of the first cell (18a).

21. The wireless device (22a) according to any one of claims 19 and 20, wherein: The historical information includes at least one of the following items: previously reported Layer 1 (L1) measurements and / or beam management BM measurements associated with said first cell (18a) and / or said at least one second cell (18b, 18c); and Location information associated with at least one wireless device (22a, 22b) in the first cell (18a) and / or the at least one second cell (18b, 18c).

22. The wireless device (22a) according to any one of claims 19 to 21, wherein: Estimating the at least one RRM metric is based on a machine learning (ML) model, the ML being trained based on the historical information.

23. The wireless device (22a) of claim 22, wherein: The wireless device (22a) is further configured to: Location information associated with the wireless device (22a) is sent to the network node, wherein estimating the at least one RRM metric is further based on the location information.

24. The wireless device (22a) according to any one of claims 19 to 23, wherein: The wireless device (22a) is further configured to: receive an RRM report configuration including and / or indicating a first event criterion from the network node (16a), and performing the RRM mobility procedure complies with one of the following: Initiated after the first event criteria are met based on detection of a fault and / or emergency situation; and Initiated before said first event criteria are met based on no fault and / or emergency situation being detected.

25. The wireless device (22a) according to any one of claims 19 to 24, wherein The measurement report is based on at least one of the following: Beam management BM measurements; and Layer 1 "L1" quality measurement.

26. The wireless device (22a) according to any one of claims 19 to 25, wherein: Performing the RRM mobility procedure includes performing a handover procedure from the first cell (18a) to one of the at least one second cell (18b, 18c).

27. The wireless device (22a) according to any one of claims 19 to 26, wherein: The measurement report does not include RRM measurements.

28. A method implemented in a wireless device, the wireless device being configured to communicate with a network node in a first cell, the method comprising: Performing (S140) measurement of the first cell; sending (S142) a measurement report based on the measurement of the first cell to the network node; receiving (S144) a radio resource management, RRM, mobility procedure indication from a network node, the RRM mobility procedure indication being based on at least one RRM metric of the first cell and at least one second cell estimated, the estimation being based on the measurement report and history information; as well as An RRM mobility procedure is performed (S146) based on the estimated RRM metric.

29. The method according to claim 28, wherein: The first cell is a serving cell, and the at least one second cell includes a neighboring cell of the first cell.

30. The method according to any one of claims 28 and 29, wherein: The historical information includes at least one of the following items: previously reported Layer 1 (L1) measurements and / or beam management BM measurements associated with said first cell and / or said at least one second cell; and Location information associated with at least one wireless device in the first cell and / or the at least one second cell.

31. The method according to any one of claims 28 to 30, wherein: Estimating the at least one RRM metric is based on a machine learning (ML) model, the ML being trained based on the historical information.

32. The method according to claim 31, wherein: The method also includes sending location information associated with the wireless device to the network node, wherein estimating the at least one RRM metric is further based on the location information.

33. The method according to any one of claims 28 to 32, wherein: The method further comprises: receiving, from the network node, an RRM report configuration comprising and / or indicating a first event criterion, and performing the RRM mobility procedure complies with one of the following: Initiated after the first event criteria are met based on detection of a fault and / or emergency situation; and Initiated before said first event criteria are met based on no fault and / or emergency situation being detected.

34. A method according to any one of claims 28 to 33, wherein: The measurement report is based on at least one of the following: Beam management BM measurements; and Layer 1 "L1" quality measurement.

35. The method according to any one of claims 28 to 34, wherein: Performing (S146) the RRM mobility procedure includes performing a handover procedure from the first cell to one of the at least one second cell.

36. A method according to any one of claims 28 to 35, wherein: The measurement report does not include RRM measurements.

Images