Condition based l1 measurement and reporting

Abstract

A method performed at a source network node distributed unit (S-DU) is provided. The method comprises receiving, from a terminal device, information related to its position; transmitting, to a network node central unit (CU), said information; receiving, from the network node CU, a configuration including one or more position-related conditions, and information related to one or more candidate target cells; receiving, from the network node CU, a current position of the terminal device; and evaluating the one or more position-related conditions against a position of the terminal device. Upon evaluating that at least one of the one or more position-related conditions is fulfilled, transmitting, to the terminal device, a message indicating the terminal device to activate L1 measurement and reporting; receiving, from the terminal device, an L1 measurement report including updated position-related information; and determining, based on the L1 measurement report, a target cell and configuring the terminal device to initiate a handover (HO) to the determined target cell.

Description

CONDITION BASED LI MEASUREMENT AND REPORTINGFIELD

[0001] Various example embodiments generally relate to mobile / wireless communication networks, and more particularly to lower layer mobility.BACKGROUND

[0002] Various example embodiments relate to considerations in a (e.g. mobile / wireless) communication system or network, such as a 5G / NR system, and a next-generation system beyond 5G. For example, various example embodiments are applicable in a 3rd Generation Partnership Project (3 GPP) standardized mobile / wireless communication system or network.LIST OF ABBREVIATIONS

[0003] In the present disclosure, the following abbreviations are used and should be understood in accordance with the given definitions:3 GPP 3rdGeneration Partnership Project5G 5thGeneration (Mobile Communication Network)BS Base StationCHO Conditional HandoverCN Core NetworkCSI Channel State InformationCU Central UnitDL DownlinkDU Distributed Unit eNB Evolved NodeB gNB Next Generation Node B / 5G Base StationHO HandoverLI Layer 1 / Physical LayerL3 Layer 3 / Network LayerLTE Long Term EvolutionLTM Lower Layer Triggered MobilityMAC Medium Access ControlMAC CE MAC Control ElementMN Main NodeNR New Radio / 5GNW NetworkPDCCH Physical Downlink Control ChannelPDU Protocol Data UnitPLMN Public Land Mobile NetworkRAN Radio Access NetworkRAT Radio Access TechnologyRRC Radio Resource ControlRRM Radio Resource ManagementRS SI Received Signal Strength Indicator.RSRP Reference Signal Received PowerRSRQ Reference Signal Received QualitySAPC Service Application PLMN CodeSINR Signal-to-Interference-plus-Noise RatioSN Secondary NodeSS Synchronization SignalTA Timing AdvanceUE User Equipment / Mobile TerminalUL UplinkSUMMARY

[0004] According to a first aspect, a method performed at a source network node distributed unit (S-DU) is provided. The method comprises receiving, from a terminal device, information related to a position of the terminal device; and transmitting, to a network node central unit (CU), said information. The method further comprises receiving, from the network node CU, a configuration including one or more position-related conditions, and information related to one or more candidate target network node distributed units (T-DUs); receiving, from the network node CU, a current position of the terminal device; and evaluating the one or more position-related conditions against the current position of the terminal device. Upon evaluating that at least one of the one or more position-related conditions is fulfilled, transmitting, to the terminal device, a message indicating the terminal device to activate layer 1 (LI) measurement and reporting; receiving, from the terminal device, an LI measurement report including updated position-related information; and determining, based on the LI measurement report, a target network node distributed unit (T-DU) and configuring the terminal device to initiate a handover (HO) to the determined T-DU.

[0005] In some embodiments, the method further comprises, when at least one of the position-related conditions is fulfilled: transmitting, to the terminal device, a Medium Access Control (MAC) Control Element (CE) to trigger the LI measurement; and receiving, from the terminal device, the LI measurement report including updated information related to a position of the terminal device.

[0006] In some embodiments, the method further comprises periodically receiving, from the CU, updates of the current position of the terminal device.

[0007] In some embodiments, the method further comprises receiving, from the CU, one or more previous positions of the terminal device; and predicting, based on at least one of the information related to a position of the terminal device and the one or more previous positions of the terminal device, a future position of the terminal device. The one or more position-related conditions are evaluated against the future position of the terminal device.

[0008] In some embodiments, the one or more position-related conditions are evaluated against the current position of the terminal device.

[0009] In some embodiments, the method further comprises, when at least one of the position-related conditions is fulfilled: transmitting, to the terminal device, a Physical Downlink Control Channel (PDCCH) order to trigger uplink (UL) sync.

[0010] In some embodiments, the method further comprises transmitting, to the terminal device, an Artificial Intelligence (Al) activation indication.

[0011] In some embodiments, the information related to a position of the terminal device includes at least one of a speed, a bearing, a current position, and a time stamp of the terminal device.

[0012] In some embodiments, at least one of the position-related conditions includes that the terminal device is located within a predetermined distance from one or more of the candidate target network node distributed units (T-DUs).

[0013] In some embodiments, the information related to a position of the terminal device is received via a layer 3 (L3) measurement report.

[0014] In some embodiments, the information related to a position of the terminal device is transmitted to the CU via a Radio Resource Control (RRC) message.

[0015] According to a second aspect, a method performed at a source network node distributed unit (S-DU) is provided. The method comprises receiving, from a terminal device, information related to a position of the terminal device; and transmitting, to a network node central unit (CU), said information. The method further comprises receiving, from the network node CU, a configuration including one or more position-related conditions, and information related to one or more candidate target network node distributed units (T-DUs); transmitting,to the terminal device, a message including the one or more position-related conditions and the information related to one or more candidate T-DUs to activate, at the terminal device, evaluation of the one or more position-related conditions. Upon evaluating that at least one of the one or more position-related conditions is fulfilled, receiving, from the terminal device, a layer 1 (LI) measurement report; determining, based on the LI measurement report, a target network node distributed unit (T-DU); transmitting, to the terminal device, a message indicating the T-DU and configuring the terminal device to initiate a handover (HO) to the determined T- DU.

[0016] In some embodiments, the method further comprises receiving, from the CU, an updated configuration including the one or more position-related conditions.

[0017] In some embodiments, the method further comprises transmitting, to the terminal device, a Physical Downlink Control Channel (PDCCH) order to trigger uplink (UL) sync; and upon evaluating that at least one of the one or more position-related conditions is fulfilled, receiving, from the terminal device, the UL sync.

[0018] In some embodiments, the method further comprises transmitting, to the terminal device, an Artificial Intelligence (Al) activation indication.

[0019] In some embodiments, the information related to a position of the terminal device includes at least one of a speed, a bearing, a current position, and a time stamp of the terminal device.

[0020] In some embodiments, at least one of the position-related conditions includes that the terminal device is located within a predetermined distance from one or more of the candidate target network node distributed units (T-DUs).

[0021] In some embodiments, the position of the terminal device is at least one of a current position of the terminal device and one or more predicted future positions of the terminal device.

[0022] In some embodiments, the one or more future positions of the terminal device are predicted based on at least one of the information related to a position of the terminal device and one or more previous positions of the terminal device.

[0023] In some embodiments, the message including the one or more position-related conditions and the information related to one or more candidate T-DUs is transmitted to the terminal device via a Medium Access Control (MAC) Control Element (CE).

[0024] In some embodiments, the information related to a position of the terminal device is received via a layer 3 (L3) measurement report.

[0025] In some embodiments, the information related to a position of the terminal device is transmitted to the CU via a Radio Resource Control (RRC) message.

[0026] According to a third aspect, an apparatus is provided. The apparatus comprises at least one processor; and at least one memory including instructions that, when executed by the at least one processor, cause the apparatus at least to perform the method according to the first aspect.

[0027] According to a fourth aspect, an apparatus is provided. The apparatus comprises at least one processor; and at least one memory including instructions that, when executed by the at least one processor, cause the apparatus at least to perform the method according to the second aspect.

[0028] In some embodiments, the apparatus according to the third or fourth aspect comprises a source network node distributed unit (S-DU).

[0029] In some embodiments, the apparatus comprises a network node central unit (CU).BRIEF DESCRIPTION OF THE FIGURES

[0030] In the following embodiments will be described in greater detail with reference to the attached drawings, in which:

[0031] FIG. 1 shows a schematic diagram of an example (mobile / wireless) communication system or network;

[0032] FIG. 2 shows a schematic diagram of an example wireless device or entity;

[0033] FIG. 3 shows a schematic diagram of an example network node or entity;

[0034] FIGs. 4A-4D show a flow diagram of a method according to an example embodiment.

[0035] In particular, FIG. 4A shows a flow diagram of the preparation phase of the example method.

[0036] FIG. 4B shows a flow diagram of the early sync phase of the example method.

[0037] FIG. 4C shows a flow diagram of the execution phase of a method according to an example embodiment.

[0038] FIG. 4D shows a flow diagram of the completion phase of the example method.

[0039] FIGs. 5A-5E show a flow diagram of a method according to another example embodiment.

[0040] In particular, FIGs. 5 A and 5B show a flow diagram of the preparation phase of the example method.

[0041] FIG. 5C shows a flow diagram of the early sync phase of the example method.

[0042] FIG. 5D shows a flow diagram of the execution phase of a method according to an example embodiment.

[0043] FIG. 5E shows a flow diagram of the completion phase of the example method.DETAILED DESCRIPTION

[0044] The examples and embodiments set forth below represent information to enable those skilled in the art to practice the subject disclosure. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the description and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the description.

[0045] References in the specification to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0046] It is to be noted that the detailed description, at times, refers to one or more specifications being used as non-limiting and illustrative examples for certain architectures, network configurations and system deployments. More specifically, the detailed description refers to 3GPP standards, being used as non-limiting and illustrative examples. As such, the example embodiments provided herein can specifically employ terminology which is directly related thereto. Such terminology is only used in the context of the non-limiting and illustrative examples and is not intended to limit the example embodiments in any way. Rather, any other system configuration or deployment may be utilized while complying with what is described herein and / or example embodiments are applicable to it.

[0047] For example, various example embodiments are applicable in any (e.g., mobile / wireless) communication system, such as a 5G / NR system and a next-generation system beyond 5G. For example, various example embodiments are applicable in a 3 GPP-standardized mobile / wireless communication system of Release 18 onwards.

[0048] Hereinafter, various example embodiments are described using several variants and / or alternatives. It is generally to be noted that, according to certain implementations or constraints, all the described variants and / or alternatives may be provided alone or in any conceivable combination (e.g., also including combinations of individual features of these various variants and / or alternatives).

[0049] As used herein, the words "comprising" and "including" should be understood as not limiting the example embodiments to consist of only those features that have been mentioned, and example embodiments may also contain, among other things, e.g., features, structures, units, modules, or the like, that have not been specifically mentioned.

[0050] As used herein, "at least one of the following: " and "at least one of " and similar wording, like "one or more of, where the list of two or more elements are joined by "and" or "or", mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0051] As used herein, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry), and (b) combinations of hardware circuits and software, such as: (i) a combination of analog and / or digital hardware circuit(s) with software / firmware, and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and hardware circuit(s) and or processor(s), such as a microprocessor s) or a portion of a microprocessor s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0052] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0053] In the drawings, it is to be noted that lines / arrows interconnecting individual blocks or entities are generally meant to illustrate an operational coupling there-b etween, which may be a physical and / or logical coupling, which on the one hand is implementation-independent (e.g., wired, or wireless) and on the other hand may also comprise an arbitrary number of intermediary functional blocks or entities not shown. In flowcharts or sequence diagrams, the illustrated order of operations or actions is generally non-limiting and illustrative, and any other order of respective operations or actions is conceivable, if feasible.

[0054] Before explaining example embodiments in detail, certain general principles of a (mobile / wireless) communication system or network are briefly explained with reference to FIGS. 1 to 3 to assist in understanding the technology underlying the described example embodiments.

[0055] FIG. 1 illustrates an example of a (mobile / wireless) communication system or network 100, for example a 5G new radio (NR) network, that may be used for wireless communications. Communication system or network 100 includes wireless communication devices or entities 110, such as UEs (e.g., UEs 110A-110C), and network nodes or entities, such as radio access nodes 120 (e.g., 120A-120B) (e.g., eNBs, gNBs, etc.), connected to one or more network nodes or entities 130 via an interconnecting network 125. Communication system or network 100 may use any suitable deployment scenarios. UEs 110 within coverage area 115 may each be capable of communicating directly with radio access nodes 120 over a wireless interface.

[0056] As an example, UE 110A may communicate with radio access node 120A over a wireless interface. That is, UE 110A may transmit wireless signals to and / or receive wireless signals from radio access node 120A. The wireless signals may contain voice traffic, data traffic, control signals, and / or any other suitable information.

[0057] As used herein, the term "user equipment" (UE) has the full breadth of its ordinary meaning and may refer to any type of wireless device or entity which can communicate with a network node or entity and / or with another UE in a cellular or mobile or wireless / mobile communication system. Examples of UE are target device, personal digital assistant (PDA), tablet, mobile terminal, smartphone, laptop embedded equipped (LEE), laptop mounted equipment (LME), vehicle-to-vehicle (V2V) UE, narrow band loT (NB-IoT) UE, etc. Example embodiments of a UE are described in more detail below with respect to FIG. 2.

[0058] In some embodiments, an area of wireless signal coverage 115 associated with a radio access node 120 may be referred to as a cell. However, particularly with respect to the 5G / New Radio (NR) mobile communication concepts, beams may be used instead of cells and, as such, it is important to note that concepts described herein are equally applicable to both cells and beams.

[0059] The interconnecting network 125 may refer to any interconnecting system capable of transmitting audio, video, signals, data, messages, etc., or any combination of the preceding. The interconnecting network 125 may include all or a portion of a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communication or computer network such as the Internet, a wireline or wireless network, an enterprise intranet, or any other suitable communication link, including combinations thereof.

[0060] In some embodiments, the network node 130 may be a core network node, managing the establishment of communication sessions and other various other functionalities for UEs 110. Examples of network node 130 may include mobile switching center (MSC), MME, serving gateway (SGW), packet data network gateway (PGW), operation and maintenance (O&M), operations support system (OSS), SON, positioning node (e.g., EnhancedServing Mobile Location Center, E-SMLC), location server node, MDT node, etc. UEs 110 may exchange certain signals with the network node 130 using the non-access stratum (NAS) layer. In non-access stratum signaling, signals between UEs 110 and the network node 130 may be transparently passed through the radio access network. In some embodiments, radio access nodes 120 may interface with one or more network nodes 130 over an internode interface.

[0061] In some embodiments, radio access node 120 may be a distributed radio access node. The components of the radio access node 120, and their associated functions, may be separated into two main units (or sub-radio network nodes) which may be referred to as the central unit (CU) and the distributed unit (DU). Different distributed radio network node architectures are possible. For instance, in some architectures, a DU may be connected to a CU via dedicated wired or wireless link (e.g., an optical fiber cable) while in other architectures, a DU may be connected a CU via a transport network. Also, how the various functions of the radio access node 120 are separated between the CU(s) and DU(s) may vary depending on the chosen architecture.

[0062] Exemplary wireless communication systems are architectures standardized by the 3GPP. A latest 3GPP based development is often referred to as the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology (RAT). The various development stages of the 3GPP specifications are referred to as releases. More recent developments of the LTE are often referred to as LTE Advanced (LTE-A). The LTE (LTE- A) employs a radio mobile architecture known as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a core network known as the Evolved Packet Core (EPC). Base stations of such systems are known as evolved or enhanced Node Bs (eNBs) and provide E-UTRAN features such as user plane Packet Data Convergence / Radio Link Control / Medium Access Control / Physical layer protocol (PDCP / RLC / MAC / PHY) and control plane Radio Resource Control (RRC) protocol terminations towards the communication devices.

[0063] An example of a suitable communications system is the 5G or NR concept. Network architecture in NR may be similar to that of LTE-A. Base stations of NR systems may be known as next generation Node Bs (gNBs). An example 5G core network (CN) comprises functional entities. The CN is connected to a UE via the radio access network (RAN). An UPF (User Plane Function) whose role is called PSA (PDU Session Anchor) may be responsible for forwarding frames back and forth between the DN (data network) and the tunnels established over the 5G towards the UEs exchanging traffic with the data network (DN). The UPF is controlled by an SMF (Session Management Function) that receives policies from a PCF (Policy Control Function). The CN may also include an AMF (Access & Mobility Function).

[0064] At least in some embodiments, the 5G NR network 100 may comprise one or more massive machine-to-machine (M2M) network(s), massive machine type communications (mMTC) network(s), internet of things (loT) network(s), industrial intemet-of-things (IIoT)network(s), enhanced mobile broadband (eMBB) network(s), ultra-reliable low-latency communication (URLLC) network(s), and / or the like. In other words, the 5G NR network 100 may be configured to serve diverse service types and / or use cases, and may logically be seen as comprising one or more networks.

[0065] Generally, all concepts disclosed herein may be applicable to different communication networks, comprising but not limited to LTE, LTE-A, 5G, 5G advanced, 6G, and other future or already implemented networks.

[0066] FIG. 2 is a schematic diagram of an example wireless communication device 110 according to certain example embodiments. Such a wireless communication device 110 is often referred to as User Equipment (UE), user device or terminal device. An appropriate wireless communication device 110 may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a mobile station (MS) or mobile device, such as a mobile phone (e.g., smartphone), a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), or any combinations of these or the like.

[0067] UE 110 may also or alternatively be configured to communicate using one or more Global Navigational Satellite Systems (GNSS such as, e.g., GPS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0068] UE 110 may include one or more of at least one transceiver 210, at least one processor 220, at least one memory 230, and at least one network interface 240. In certain example embodiments, the transceiver 210 facilitates transmitting wireless signals to and receiving wireless signals from radio access node 120 (e.g., via transmitter(s) (Tx), receiver(s) (Rx) and antenna(s)). The processor 220 executes instructions to provide some or all of the functionalities described herein as being provided by a wireless device / entity or UE, and the memory 230 stores the instructions executed by the processor 220. In some embodiments, the processor 220 and the memory 230 form processing circuitry

[0069] The processor 220 may include any suitable combination of hardware to execute instructions and manipulate data to perform some or all the described functions of a wireless device or entity, such as the functions of UE 110 described herein. In some embodiments, the processor 220 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs) and / or other logic.

[0070] Generally, the wireless communication device 110 illustrated in FIG. 2 includes a set of components configured to perform core functions. For example, this set of components may be implemented as a system on chip (SoC), which may include portions for various purposes. Alternatively, this set of components may be implemented as separate componentsor groups of components for the various purposes. The set of components may be (communicatively) coupled (e.g., directly or indirectly) to various other circuits of the wireless communication device 110.

[0071] The memory 230 is generally operable to store instructions, such as a computer program, software, an application including one or more of logic, rules, algorithms, code, tables, etc. and / or other instructions capable of being executed by a processor 220. Examples of memory 230 include computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or or any other volatile or non-volatile, non- transitory computer-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processor 220 of UE 110. For example, the memory 230 includes instructions causing the processor 220 to perform processing according to any corresponding methods described herein.

[0072] The network interface 240 is communicatively coupled to the processor 220 and may refer to any suitable device operable to receive input for UE 110, send output from UE 110, perform suitable processing of the input or output or both, communicate to other devices, or any combination thereof. The network interface 240 may include appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilities, to communicate through a network.

[0073] Other embodiments of UE 110 may include additional components beyond those shown in FIG. 2 that may be responsible for providing certain aspects of the wireless device’s functionalities, including any of the functionalities described herein and / or any additional functionalities (including any functionality necessary to support the mechanisms according to the subject disclosure). As an example, UE 110 may include input devices and circuits, output devices, and one or more synchronization units or circuits, which may be part of the processor 220. Input devices include mechanisms for entry of data into UE 110. For example, input devices may include input mechanisms, such as a microphone, input elements, a display, etc. Output devices may include mechanisms for outputting data in audio, video and / or hard copy format. For example, output devices may include a speaker, a display, etc.

[0074] In certain example embodiments, the wireless device UE 110 may comprise a series of modules configured to implement the functionalities of the wireless device described herein.

[0075] It will be appreciated that the various modules may be implemented as combination of hardware and software, for instance, the processor, memory, and transceiver(s) of UE 110 shown in FIG. 2. Certain example embodiments may also include additional modules to support additional and / or optional functionalities.

[0076] UE 110 may also include one or more mechanisms for sharing and / or obtaining data. For example, UE 110 may include a short-range radio frequency (RF) transceiver and / orinterrogator, so data may be shared with and / or obtained from electronic devices in accordance with RF techniques. UE 110 may include other short-range transceivers, such as an infrared (IR) transceiver, a Bluetooth™ (BT) transceiver operating using Bluetooth™ wireless technology, a wireless Universal Serial Bus (USB) transceiver, a Bluetooth™ Low Energy transceiver, a ZigBee transceiver, an ANT transceiver, a cellular device-to-device transceiver, a wireless local area link transceiver, and / or any other short-range radio technology. UE 110 and more specifically, the short-range transceiver may be capable of transmitting data to and / or receiving data from electronic devices within the proximity of the apparatus, such as within 10 meters, for example. UE 110 including the Wi-Fi or WLAN modem may also be capable of transmitting and / or receiving data from electronic devices according to various wireless networking techniques, including 6L0WPAN, Wi-Fi, Wi-Fi low power, WLAN techniques such as IEEE 802.11 techniques, IEEE 802.15 techniques, IEEE 802.16 techniques, and / or the like.

[0077] Some of the embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside on the memory, the processor, or electronic components, for example. In some example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer- readable media. In the context of this document, a "computer-readable medium" may be any non-transitory media that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry, with examples depicted at FIG. 3, computer-readable medium may comprise a non-transitory computer-readable storage medium that may be any media that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

[0078] FIG. 3 is a schematic diagram of an example radio access node 120 or network node or entity 130 according to certain example embodiments. Radio access node 120 or network node or entity 130 may include one or more of at least one transceiver 310, at least one processor 320, at least one memory 330, and at least one network interface 340. In certain example embodiments, the transceiver 310 facilitates transmitting wireless signals to and receiving wireless signals from wireless devices, such as UE 110 (e.g., via transmitter(s) (Tx), receiver(s) (Rx), and antenna(s)). The processor 320 executes instructions to provide some or all the functionalities described herein as being provided by the radio access node 120 or the network node or entity 130, the memory 330 stores the instructions executed by the processor 320. In some embodiments, the processor 320 and the memory 330 form processing circuitry. The network interface 340 can communicate signals to backend network components, such as a gateway, switch, router, Internet, Public Switched Telephone Network (PSTN), core network nodes or radio network controllers, etc.

[0079] The processor 320 can include any suitable combination of hardware to execute instructions and manipulate data to perform some or all the described functions of the radio access node 120 or the network node or entity 130, such as those described herein. In some embodiments, the processor 320 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs) and / or other logic.

[0080] The memory 330 is generally operable to store instructions, such as a computer program, software, an application including one or more of logic, rules, algorithms, code, tables, etc. and / or other instructions capable of being executed by a processor 320. Examples of memory 330 include computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or or any other volatile or non-volatile, non- transitory computer-readable and / or computer-executable memory devices that store information. For example, the memory 330 includes instructions causing the processor 320 to perform processing according to any corresponding methods described herein.

[0081] In certain example embodiments, the network interface 340 is communicatively coupled to the processor 320 and may refer to any suitable device operable to receive input for the radio access node 120 or the network node or entity 130, send output from the radio access node 120 or the network node or entity 130, perform suitable processing of the input or output or both, communicate to other devices, or any combination of the preceding. The network interface 340 may include appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilities, to communicate through a network.

[0082] Other example embodiments of the radio access node 120 or the network node or entity 130 can include additional components beyond those shown in FIG. 3 that may be responsible for providing certain aspects of the node’s functionalities, including any of the functionalities described herein and / or any additional functionalities (including any functionality necessary to support the solutions described herein). The various different types of radio access nodes or network nodes may include components having the same physical hardware but configured (e.g., via programming) to support different radio access technologies, or may represent partly or entirely different physical components.

[0083] Processors, interfaces, and memory similar to those described with respect to FIG. 3 may be included in other nodes or entities (such as UE 110, radio access node 120, etc.). Other nodes or entities may optionally include or not include a wireless interface (such as the transceiver described in FIG. 3).

[0084] In certain example embodiments, the radio access node 120 or the network node or entity 130 may comprise a series of modules configured to implement the functionalities of the radio access node 120 or the network node or entity 130 described herein.

[0085] It will be appreciated that the various modules may be implemented as combination of hardware and software, for instance, the processor, memory, and transceiver(s) of the radio access node 120 or the network node or entity 130 shown in FIG. 3. Certain example embodiments may also include additional modules to support additional and / or optional functionalities.

[0086] For example, in 5G / NR, the RAN node (i.e., the gNB) can be logically split into two entities which may be referred to as the central unit (CU) and the distributed unit (DU). More specifically, the RAN node may be logically split into a gNB-central unit (gNB-CU) and one or more gNB -distributed units (gNB-DU). Further-more, the gNB-CU may be logically split into a control plane (CP) part or entity (gNB-CU-CP) and one or more user plane (UP) parts or entities (gNB-CU-UP). Accordingly, gNB 120 may provide 5G user plane and control plane protocol termination towards UE 110. UP may be used to carry user traffic, such as voice, and Internet traffic, whereas CP may be used to carry e.g., control messages used for signaling in the system 100.

[0087] The gNB-CU is a logical node that may host higher layer protocols, such as radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP). The SDAP layer will not be present if the CU is connected to a 4G Core network, as at least a 5G core network is necessary to support SDAP. The gNB-DUs are logical nodes that may host lower layer protocols, e.g., radio link control (RLC), medium access control (MAC), and higher physical (PHY) layers.

[0088] That is, there is a single CU for each gNB, but one CU controls multiple DUs, for example more than 100 DUs can be connected to one CU. Each DU is able to support one or more cells, so one gNB can control hundreds of cells (unlike the 4G base station).

[0089] Having thus introduced a suitable but non-limiting technical context for the practice of the example embodiments, the example embodiments are now described with greater specificity.

[0090] In general, the present disclosure is related to Lower Layer Triggered Mobility (LTM). LTM is a concept related to, e.g., 5G and 6G networks. It involves the use of lower network layers to initiate handover procedures, reducing latency and interruption time during device mobility. LTM enables serving cell changes via the resetting of lower network layers, such as MAC and PHY, leading to improved mobility performance. This approach is being introduced to enhance the efficiency of mobility management in advanced wireless networks, particularly in the context of 5G-Advanced and future 6G technologies.

[0091] Currently, in 3 GPP, mobility procedures include LTM based on LI measurement,L3 handover (HO) based on L3 measurement, including baseline HO and conditional HO (CHO), and selective activation of SN, which procedure is determined by gNB-CU based on LI measurements from UE. The difference between LI and L3 measurements lies in the layers at which the measurements are performed and the associated processing. LI measurements, or Layer 1 measurements, are performed at the physical layer of the network stack. They are useful for procedures that require minimal delay, such as beam management, and are filtered at Layer 1 to remove the impact of noise and improve measurement. LI measurements include parameters such as SS-RSRP and CSLRSRP.

[0092] On the other hand, L3 measurements, or Layer 3 measurements, involve filtering the values and doing the final reporting at the network stack’s higher layer. L3 measurements can be either “beam level” or “cell level” and include parameters like RSRP, RSRQ, SINR, and RS SI. They are used for tracking rapidly changing channel conditions to support mobility and beam management. L3 measurements filter the impact of fast fading and help reduce short-term variations in the measurements.

[0093] In summary, LI measurements are performed at the physical layer and are filtered to improve accuracy, while L3 measurements involve higher-layer processing and filtering to track rapidly changing channel conditions for mobility and beam management, for example in 5G networks.

[0094] LTM can be divided into four phases: (i) Preparation, (ii) Early Synchronization (Early sync), (iii) Execution, and (iv) Completion.

[0095] During the Preparation phase, the serving CU identifies the potential target cells based on the L3 measurement reports, prepares the target cells and shares the target cell configurations with the UE.

[0096] During the Early sync phase, the source DU indicates to the UE to perform Timing Advance (TA) acquisition for a specific target cell. In the context of, e.g., GSM and LTE, TA is a parameter used to control the timing of uplink transmissions from the mobile station (MS) to the base transceiver station (BTS) or evolved NodeB (eNB). It is necessary due to the finite speed of radio wave propagation, which causes a delay in the transmission reaching the base station. The TA value is adjusted to ensure that the uplink transmissions from different mobile stations arrive at the base station without interfering with each other.

[0097] During the Execution phase, the source DU decides on the target cell and indicates to the UE to switch to that target cell. The UE then switches to the target cell and starts receiving data from it.

[0098] During the Completion phase, the UE context may be released from the prepared cells (optionally), or the UE context may be kept in case of Dynamic Switching. It is up to the CU to decide on how long the UE context will be maintained.

[0099] Conditional Handover (CHO) was specified in Release 16 for NR and LTE. Main differences of CHO compared to baseline HO are- Early preparation of multiple target cells;- UE evaluates the CHO execution condition (Measurement ID in measurement configuration of serving PCell) associated with the prepared target cells;- UE executes the handover once the CHO condition is met; and- As source gNB is unaware of the time instant the UE executes CHO, two types of data forwarding have been defined: o Early data forwarding: Source gNB forwards the data to the target cell at the time of preparation. Early Secondary Node (SN) Status Transfer message can be sent from source gNB to inform target gNB about the received packets by the UE such that the target gNB can discard them; and o Late data forwarding: Target gNB sends HO Success after receiving RRC Reconfiguration Complete from the UE and the source gNB starts data forwarding to the target gNB (causes additional interruption).

[0100] Selective activation is about selectively adding secondary node to shorten the handover interruption in L3 level. Multiple secondary nodes configurations are prepared and sent to UE, such that UE can switch among these configured secondary nodes without RRC reconfiguration command.

[0101] CHO can be viewed as a conditional HO about primary nodes, while selective activation as selectively activation of secondary nodes. Both CHO and selective activation constitute L3 HO.

[0102] In non-terrestrial networks, location-based triggering condition is supported, upon which the UE may execute CHO to a candidate cell, as described by the 3 GPP Technical Specification (TS) 38.300. A location-based triggering condition is always configured together with one of the measurement-based triggering conditions (CHO events A3 / A4 / A5) as defined in TS 38.331. It is up to UE implementation how the UE evaluates the location-based trigger condition together with the measurement-based event (cf. TS 38.300). The configured locationbased triggering conditions involve the distance of the UE from reference points associated with the source and target cells. Since satellite trajectories are known a priori and UEs are relatively static, a series of sequential CHOs can be configured / prepared in a single procedure.

[0103] For example, an A3 event is triggered when a neighboring cell becomes better than the serving cell by a specified offset, and it can be used to initiate an intra- or inter-frequency handover procedure. On the other hand, an A5 event is triggered when the measurement of the signal received from the serving cell falls below a first threshold, while the measurement of the signal received from a neighboring cell becomes greater than a second threshold. This event can also be used to initiate handover procedures. The specific parameter ranges and values for these events are also defined, such as Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ) thresholds for Al, A2, A4, A5, and Bl events.

[0104] In Release 19, event based triggered measurement and reporting has been included in Work Item Description (WID). Though A3 / A5 event are the focus, it doesn’t exclude other condition for event triggered measurement and reporting. Positioning information is an example of such a condition. This positioning information includes the current position and / or predicted future position.

[0105] Using the current UE position alone may not justify over the channel quality in terms of the metric in triggering handover. However, the predicted position based on the current position could provide a guidance when measurement and reporting to candidate cells which UE could have the potential to switch to in the near future are triggered.

[0106] In the present disclosure, it is assumed that gNB has the positioning information of the UE and gNB can predict the movement path of the UE based on UE information such as speed and bearing. With this, gNB is allowed to configure and / or trigger LI measurement and reporting based on predicted location information and trigger cell change. The prediction reduces the reporting frequency (e.g., the frequency of LI measurement reporting). For example, the gNB may predict the future position of the UE by using a prediction algorithm. The prediction algorithm may be, e.g., a Kalman filter or a deep learning model.

[0107] In particular, CU could prepare the LTM candidate cells based on predicted UE positioning information together with the measurement values in the L3 report. CU could also trigger RRC reconfiguration of new set of candidate cells if CU predicts UE will move out of the old candidate cells range.

[0108] Furthermore, based on the position information of the UE, the network can configure location-based triggering of LI measurement reports for LTM to reduce reporting overhead. More specifically, the UE shall report LI measurements of the candidate cell only if its location and the locations of reference points associated with the serving and the said candidate cell satisfy a (pre-)configured condition. For the evaluation of such condition, the network needs to signal the location of the reference points to the UE during the HO preparation.

[0109] Two possible cases can be distinguished, namely (a) source DU triggered LI measurements, and (b) UE triggered LI measurements.

[0110] In case (a), the source DU evaluates a location-based condition and if this is satisfied, it sends a MAC-CE to the UE to activate its LI measurement reporting. The locationbased event configuration needs to be provided from the CU to the source DU. Furthermore, the locations of candidate cells need to be provided to the source DU, e.g., by the CU.

[0111] In case (b), the UE evaluates a location-based condition and if this is satisfied, it provides a LI measurement report to the source DU. For the UE to be able to evaluate such conditions, the location of the target cell has to be provided to the UE. This may be provided to the UE within the candidate RRC configuration in the handover preparation phase.

[0112] Additionally, in case of UE-triggered LI measurements, DU may send the condition to UE during RRC reconfiguration message, or as MAC-CE for update. These conditions can be the same or different for different purposes. The update of the condition can be the same or different for different purpose.

[0113] Described herein is an efficient procedure that enables condition-based layer 1 (LI) measurement and reporting, or, more specifically, position based LI measurement and reporting.

[0114] In a first embodiment, illustrated in Figs. 4A to 4D, a given source network node distributed unit (source DU) triggers the LI measurement and reporting.

[0115] In a second embodiment, illustrated in Figs. 5 A to 5E, a terminal device, such as a user equipment (UE), triggers the LI measurement and reporting.

[0116] Moreover, in some examples, a cell change, i.e., a lower layer triggered handover, may be performed based on the LI measurement and reporting.

[0117] Fig. 4A-4D show a flow diagram of a method according to an example embodiment including the following steps.

[0118] More particularly, Fig. 4A illustrates the preparation phase of the network operation, the serving CU identifies potential candidate target network node distributed units (T-DUs) based on the L3 measurement reports and prepares the T-DUs (target cells) and shares the configurations of the target cell with other members of the network.

[0119] At 401, the source DU may send an Al activation indication, (e.g. an Al command) to the UE. The Al activation indication may be sent via a MAC-CE. The Al activation indication may allow to evaluate the position-related conditions against a predicted future position of the terminal device, not only against the current position of the terminal device. For example, the Al indication signals to the UE that additional information related to speed, bearing and time stamp are provided to the central unit (e.g. gNB), if this is not activated no additional information is needed.

[0120] Upon receiving this activation, the UE will report, at 402, information related to its position, such as, e.g., UE speed, bearing and time stamp, to its measurement report. The measurement report may be an L3 measurement report. The measurement report may be sent to the source DU. In some examples, the measurement report may be sent to the CU.

[0121] In case the measurement report has been sent to the source DU, the source DU forward, at 403, the L3 measurement report to the CU.

[0122] At 404, the CU may send a UE context setup request to a target DU.

[0123] In response to this context setup request, the CU may receive, at 405, a UE context setup response from the target DU.

[0124] At 406, the CU may generate an RRC Lower Layer Triggered Mobility (LTM) configuration for candidate cells. For example, the CU may generate a measurement configuration of LI cell change. The CU may further generate a configuration of prepared cells, e.g., prepared target cells.

[0125] At 407, the CU may decide on the positioning related condition. For example, such condition could be whether UE is within a predetermined distance (e.g., 10 m, 100 m, 1000 m or 10000 m) from the target cell. There may be one or more conditions for LI measurement, reporting or UL sync. These conditions could be different.

[0126] At 408, the CU sends a configuration to the source DU. The configuration may include the one or more positioning conditions information.

[0127] At 409, the CU sends an RRC Reconfiguration to the source DU. The RRC message may be sent via a DL RRC message transfer.

[0128] At 410, the source DU forwards the RRC Reconfiguration to the UE.

[0129] At 411, the source DU receives a RRC Reconfiguration complete from the UE in response to the RRC Reconfiguration sent at 410.

[0130] At 412, the source DU forwards the RRC Reconfiguration complete to the CU.

[0131] Upon receiving the RRCReconfigurationComplete message from the UE, the CU transfers, at 413, one or more previous UE positions to the source DU. These previous UE positions may the positions of the UE up to a number N of previous seconds. The CU may also transfer the current UE position to the source DU.

[0132] Fig. 4B illustrates the “Early Sync” phase of the network operation, which means DL / UL synchronization with candidate cells.

[0133] At 414, the source DU may send a MAC-CE to trigger LI measurement when at least one of the positioning related conditions is fulfilled.

[0134] At 415, the UE sends an LI measurement report to the source DU. The LI measurement report may include LI Reference Signal Received Power (RSRP). In addition, thereto, the UE may update the source DU about UE speed, bearing and the time stamp when these information are captured.

[0135] At 416, the CU may send updates of the current UE position to the source DU. In some examples, these updates may be sent periodically.

[0136] In some examples, the source DU has received the current UE position from the CU. In some examples, the source DU has received the current UE position from the UE. In some examples, the source DU has additionally received information related to the UE position, such as, e.g., UE speed, bearing and time stamp. For example, the source DU may have received these position related information when these information were logged.

[0137] At 417, the source DU predicts a future UE position based on at least one of the information related to the UE position and the one or more previous positions of the UE. The prediction could reduce the reporting frequency.

[0138] At 418, the source DU evaluates the one or more conditions configured by the CU and received in at 413 against the current UE position or the predicted future UE position. The CU could also update the condition when there is a dynamic change to the setup, such as a preferred candidate cell is overloaded. The CU may re-direct the UE to another cell which may require a new condition.

[0139] At 419, the source DU may send a PDCCH order to trigger UL sync when the condition is fulfilled.

[0140] Fig. 4C illustrates the “Execution” phase of the network operation.

[0141] At 420, the source DU may activate the LI reporting and / or the LI measurement when the condition is fulfilled. This activation may be performed by transmitting, from the source DU, a MAC-CE to the UE.

[0142] In response to this activation, the UE may send, at 421, an LI measurement report to the source DU. The LI measurement report may include LI Reference Signal Received Power (RSRP). In addition, thereto, the UE may update the source DU about UE speed, bearing and the time stamp when these information are captured.

[0143] At 422, the CU may send updates of the current UE position to the source DU. In some examples, these updates may be sent periodically.

[0144] At 423, the source DU determines a serving cell change based on the LI measurement. The source DU may further determine the best target cell, i.e., the best target DU, based on the predicted future UE position or on the current UE position and the position relatedinformation. For example, the source DU may determine the probability for a possible candidate target cell based on the current UE position and the position related information.

[0145] At 424, the source DU may send a cell change command to the UE. The cell change command may be sent via a MAC-CE.

[0146] At 425 to 431, the UE may perform the cell change.

[0147] In particular, at 425, the UE may detach from the source DU. At 426, the UE may send a Random Access request to the determined target DU. In response thereto, the UE may receive, at 427, a Random Access response from the target DU. At 428, the UE may send an RRC Reconfiguration Complete to the target DU.

[0148] In Fig. 4D, which illustrates the “Completion phase” of the network operation, the CU may receive, at 429, an UL RRC message transfer from the target DU. At 430, the CU may send, to the source DU, a UE context release request. In response thereto, the CU may receive, at 431, a UE context release complete from the source DU.

[0149] Fig. 5A-5E show a flow diagram of a method according to an example embodiment including the following steps.

[0150] Fig 5A and 5B show the preparation phase of the network operation, the serving CU identifies potential candidate target network node distributed units (T-DUs) based on the L3 measurement reports and prepares the T-DUs (target cells) and shares the configurations of the target cell with other members of the network.

[0151] In detail Fig. 5A shows the following steps.

[0152] At 501, in the preparation phase, the S-DU may transmit an Artificial Intelligence (Al) activation indication, (e.g. an Al command to the UE. The Al activation indication could, for example, be transmitted via a MAC-CE message. The Al activation indication may allow to evaluate the position-related conditions against a predicted future position of the terminal device, not only against the current position of the terminal device. For example, the Al indication signals to the UE that additional information related to speed, bearing and time stamp are provided to the CU (e.g. gNB), if this is not activated no additional information is needed.

[0153] At 502, upon receiving this Al activation, UE transmits information related to a position of the UE to the S-DU. Information related to a position of the UE may include at least one of a speed, a bearing, a current position, and a time stamp of the UE. The information related to a position of the UE may be transmitted via an L3 measurement report.

[0154] At 503, after receiving the information related to a position of the UE, the S-DU transmits a message including said information to the CU. The information related to a position of the UE may be transmitted, for example, via an UL RRC message transfer. The UL RRCmessage transfer may include at least a speed, a bearing, a current position, a time stamp of the UE and the L3 measurement report.

[0155] At 504, after receiving the message at the CU, the CU may derive a predicted future UE position based on at least one of the UE positions in the database of the CU up to N previous seconds and the received information related to a position of the UE. CU may also derive from the different position of the UE a predicted movement information of the UE.

[0156] At 505, based on at least one of the predicted position and the predicted movement information of the UE, the CU may configure a LTM. The CU may select target cells that are relevant based on the predicted position and the predicted movement information of the UE. Relevant target cells are those target cells of the network that are close to the predicted position of the UE and / or will be close to the position of the UE in view of the predicted movement information of the UE.

[0157] At 506, the CU may transmit a request to at least one of the selected target cells. The request is for example a UE context setup request.

[0158] At 507, at least one of the selected target cells may transmit a response to the CU. The response is for example a UE context setup response.

[0159] At 508, the CU may generate a LTM configuration for at least one of the target cells including a measurement configuration of LI cell change and the configuration of the target cells. The LTM configuration is for example a RRC LTM configuration.

[0160] At 509, the CU may define the position related condition for changing from the S-DU to one of the other T-DUs. For example, the CU determines a condition of how close the UE must be to the candidate target cell for a change to be instantiated, e.g. 10 m, 100 m, 1000 m or 10000 m.

[0161] The defined position related condition can be different for different operations in the network, e.g. reporting, measurement or UL sync operations. In addition, the positioning related condition defined by the CU, can also be updated or changed, if there is a dynamic change in the network functionality. Reasons for a dynamic change are for example that the candidate target cell is overloaded or has limited functionality. If one of these scenarios occurs, the CU can re-define the positioning related condition, meaning that the UE is redirected to another cell that is not overloaded or has full functionality. Those updates of the position related condition can be sent by the CU within this method as described below.

[0162] In detail Fig. 5B shows the following steps.

[0163] At 510, the CU transmits a message to the S-DU. The message is for example a DL RRC message transfer and includes a RRC configuration and a position related condition toperform an operation, e.g. a reporting, measurement or UL sync operation, as defined in 509. For example, the RRC configuration include the GPS-location of the candidate target cells.

[0164] At 511, the S-DU transmits the received message from the CU, to the UE. The message is for example a RRC configuration message.

[0165] At 512, the UE may transmit a message to the S-DU. For example, the message is a RRC Reconfiguration Complete message.

[0166] At 513, the S-DU may transmit a message to the CU. For example, the message is a UL RRC message transfer.

[0167] Fig 5C shows the early Sync phase of the network operation which means DL / UL synchronization with candidate cells.

[0168] At 514, the UE evaluates the received position related condition against the current UE position or the predicted UE position.

[0169] At 515, when the position related condition is fulfilled, the UE transmits a LI measurement report to the S-DU. Optionally, the UE may transmit together with the LI measurement report information related to a position of the UE, such as, e.g., speed, bearing, current position, and time stamp of the UE.

[0170] At 516, as discussed above, the CU may optionally transmit a message containing an update of the position related condition configuration to the S-DU about the condition at the UE when an operation is performed. The update could be applied to all different conditions, or it could be a different update for different conditions.

[0171] At 517, the S-DU transmits the received message from the CU, to the UE. The message is for example a MAC-CE message and contain the update of the position related condition configuration. For example, the S-DU updates the conditions which is sent to UE via MAC-CE. The update could be applied to all different conditions, or it could be a different update for different conditions.

[0172] At 518, optionally, the UE may evaluate the received updated position related condition against the current UE position or the predicted UE position.

[0173] At 519, the S-DU may transmit a PDCCH order UL sync to the UE.

[0174] At 520, the UE may perform an UL sync when the position related condition is fulfilled.

[0175] Fig 5D shows the execution phase of the network operation.

[0176] At 521, when the position related condition is fulfilled, the UE transmits a LI measurement report to the S-DU. Optional, the UE transmits together with the LI measurementreport information related to a position of the UE, like speed, bearing, current position, and time stamp of the UE.

[0177] At 522, the S-DU determines a serving cell change based on the LI measurement report and determines the best target cell based on the current position of the UE, the predicted position of the UE or the calculated probability.

[0178] At 523, the S-DU transmits a cell change message to the UE. The message is for example a MAC-CE message.

[0179] At 524 to 530, the UE may perform the cell change.

[0180] In particular, at 524, the UE may detach from S-DU.

[0181] At 525, the UE may transmit a message to the determined T-DU. The message is for example a Random-access message.

[0182] At 526, the T-DU may transmit a message to the UE. The message is for example a Random-response message.

[0183] At 527, the UE may transmit a further message to the determined T-DU. The further message is for example a RRC Reconfiguration Complete message.

[0184] Fig 5E shows the completion phase of the network operation.

[0185] At 528, the T-DU may transmit a message to the CU. The message is for example a UL RRC message transfer message.

[0186] At 529, the CU may transmit a message to the S-DU. The message is for example a UE context release request.

[0187] At 530, the S-DU may transmit a message to the CU. The message is for example UE context release complete message.

[0188] It is noted that whilst embodiments have been described in relation to 5G NR, similar principles can be applied in relation to other networks and communication systems, particularly next-generation systems beyond 5G. Therefore, although certain embodiments were described above by way of example with reference to certain example architectures for wireless networks, technologies and standards, embodiments may be applied to any other suitable forms of communication systems than those illustrated and described herein.

[0189] It is also noted herein that while the above describes exemplary embodiments, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the subject disclosure.

[0190] In general, the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects of thesubject disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the subject disclosure is not limited thereto. While various aspects of the subject disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0191] Example embodiments of the subject disclosure may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware. Computer software or program, also called program product, including software routines, applets and / or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks. A computer program product may comprise one or more computerexecutable components which, when the program is run, are configured to carry out embodiments. The one or more computer-executable components may be at least one software code or portions of it.

[0192] Further in this regard it should be noted that any blocks of the logic flow as in the figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD. The physical media is a non-transitory media.

[0193] The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processors may be of any type suitable to the local technical environment, and may comprise one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), FPGA, gate level circuits and processors based on multicore processor architecture, as non-limiting examples.

[0194] Example embodiments of the subject disclosure may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0195] The foregoing description has provided by way of non-limiting examples a full and informative description of the exemplary embodiment of the subject disclosure. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of this disclosure will still fall within the scope of the subject disclosure as defined in the appended claims. Indeed, there is a further embodiment comprising a combination of one or more embodiments with any of the other embodiments previously discussed.

Claims

CLAIMS1. A method performed at a source network node distributed unit (S-DU), the method comprising: receiving, from a terminal device, information related to a position of the terminal device; transmitting, to a network node central unit (CU), said information; receiving, from the network node central unit (CU), a configuration including one or more position-related conditions, and information related to one or more candidate target network node distributed units (T-DUs); receiving, from the network node central unit (CU), a current position of the terminal device; evaluating the one or more position-related conditions against a position of the terminal device; upon evaluating that at least one of the one or more position-related conditions is fulfilled, transmitting, to the terminal device, a message indicating the terminal device to activate layer 1 (LI) measurement and reporting; receiving, from the terminal device, an LI measurement report including updated position-related information; and determining, based on the LI measurement report, a target network node distributed unit (T-DU) and configuring the terminal device to initiate a handover (HO) to the determined T-DU.

2. The method according to claim 1, further comprising, when at least one of the position-related conditions is fulfilled: transmitting, to the terminal device, a Medium Access Control (MAC) Control Element (CE) to trigger the LI measurement; and receiving, from the terminal device, the LI measurement report including updated information related to a position of the terminal device.

3. The method according to any of claims 1 and 2, further comprising: periodically receiving, from the CU, updates of the current position of the terminal device.

4. The method according to any of the previous claims, further comprising, transmitting, to the terminal device, an Artificial Intelligence (Al) activation indication.

5. The method according to any of the previous claims, further comprising: receiving, from the CU, one or more previous positions of the terminal device; predicting, based on at least one of the information related to a position of the terminal device and the one or more previous positions of the terminal device, a future position of the terminal device; and wherein the one or more position-related conditions are evaluated against the future position of the terminal device.

6. The method according to any of the claims 1-4, wherein the one or more position- related conditions are evaluated against the current position of the terminal device.

7. The method according to any of the previous claims, further comprising, when at least one of the position-related conditions is fulfilled: transmitting, to the terminal device, a Physical Downlink Control Channel (PDCCH) order to trigger uplink (UL) sync.

8. The method according to any of the previous claims, wherein the information related to a position of the terminal device includes at least one of a speed, a bearing, a current position, and a time stamp of the terminal device.

9. The method according to any of the previous claims, wherein at least one of the position-related conditions includes that the terminal device is located within a predetermined distance from one or more of the candidate target network node distributed units (T-DUs).

10. The method according to any of the previous claims, wherein the information related to a position of the terminal device is received via a layer 3 (L3) measurement report.

11. The method according to any of the previous claims, wherein the information related to a position of the terminal device is transmitted to the CU via a Radio Resource Control (RRC) message.

12. A method performed at a source network node distributed unit (S-DU), the method comprising: receiving, from a terminal device, information related to a position of the terminal device; transmitting, to a network node central unit (CU), said information; receiving, from the network node central unit (CU), a configuration including one or more position-related conditions, and information related to one or more candidate target network node distributed units (T-DUs); transmitting, to the terminal device, a message including the one or more position-related conditions and the information related to one or more candidate T- DUs to activate, at the terminal device, evaluation of the one or more position-related conditions; upon evaluating that at least one of the one or more position-related conditions is fulfilled, receiving, from the terminal device, a layer 1 (LI) measurement report; determining, based on the LI measurement report, a target network node distributed unit (T-DU); transmitting, to the terminal device, a message indicating the T-DU and configuring the terminal device to initiate a handover (HO) to the determined T-DU.

13. The method according to claim 11, further comprising receiving, from the CU, an updated configuration including the one or more position-related conditions.

14. The method according to any of claims 11 and 12, further comprising: transmitting, to the terminal device, a Physical Downlink Control Channel (PDCCH) order to trigger uplink (UL) sync; and upon evaluating that at least one of the one or more position-related conditions is fulfilled, receiving, from the terminal device, the UL sync.

15. The method according to any of the previous claims, further comprising transmitting, to the terminal device, an Artificial Intelligence (Al) activation indication.

16. The method according to any of the previous claims, wherein the information related to a position of the terminal device includes at least one of a speed, a bearing, a current position, and a time stamp of the terminal device.

17. The method according to any of the previous claims, wherein at least one of the position-related conditions includes that the terminal device is located within a predetermined distance from one or more of the candidate target network node distributed units (T-Dus).

18. The method according to any of the previous claims, wherein the position of the terminal device is at least one of a current position of the terminal device and one or more predicted future positions of the terminal device.

19. The method according to any of the previous claims, wherein the one or more future positions of the terminal device are predicted based on at least one of the information related to a position of the terminal device and one or more previous positions of the terminal device.

20. The method according to any of the previous claims, wherein the message including the one or more position-related conditions and the information related to one or more candidate T-DUs is transmitted to the terminal device via a Medium Access Control (MAC) Control Element (CE).

21. The method according to any of the previous claims, wherein the information related to a position of the terminal device is received via a layer 3 (L3) measurement report.

22. The method according to any of the previous claims, wherein the information related to a position of the terminal device is transmitted to the CU via a Radio Resource Control (RRC) message.

23. An apparatus, comprising at least one processor; and at least one memoryincluding instructions that, when executed by the at least one processor, cause the apparatus at least to perform the method according to any of claims 1-11.

24. An apparatus, comprising at least one processor; and at least one memory including instructions that, when executed by the at least one processor, cause the apparatus at least to perform the method according to any of claims 12-22.

25. The apparatus according to any of claims 23 and 24, wherein the apparatus comprises a source network node distributed unit (S-DU).

26. The apparatus according to any of claims 23 to 25, wherein the apparatus comprises a network node central unit (CU).

Images