User equipment switching and configuration changes for sensing services

Abstract

Various aspects of this disclosure relate generally to wireless communications. Some aspects relate to mobility processes for user equipment (UE) configured as a sensing unit (SU) for integrated sensing and communication (ISAC) services. In some aspects, mobility service network nodes can be configured to facilitate coordination of configuration changes due to handover. For example, mobility service network nodes can interact with network function entities (referred to herein as sensing management function (SnMF) network nodes) to facilitate rapid reconfiguration of UEs moving from a source cell to a target cell and / or radio access network (RAN) nodes associated with the target cell.

Description

Cross-references to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 534,177, filed December 8, 2023, entitled “USER EQUIPMENT HANDOVER AND CONFIGURATION CHANGE FOR SENSING SERVICE”, assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0002] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods associated with UE handover for sensing services and related changes in UE configuration. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution.

[0005] In some examples, wireless communication networks may support sensing services such as Integrated Sensing and Communication (ISAC) services. ISAC uses the same systems and infrastructure used for wireless communication to provide sensing capabilities (e.g., RF sensing capabilities). One or more devices in the wireless communication network (which may be referred to as sensing units (SUs)) can perform RF sensing via the resources of the wireless communication network (e.g., using one or more RF signals). RF sensing enables wireless communication devices to acquire information about the characteristics of the environment and / or objects within the environment. In some examples, RF sensing can be used to determine the distance (range), angle, and / or instantaneous linear velocity of objects in the environment.

[0006] A sensing service can be associated with one or more Subscriber Units (SUs) configured to perform RF sensing in response to one or more sensing requests. In a given wireless communication network, various different devices can be able to act as SUs. For example, a User Equipment (UE) can be used as an SU and can be configured as a transmitter or receiver for RF sensing operations. A UE can be configured by a Radio Access Network (RAN) to perform sensing tasks as part of RF sensing operations. A UE configured to perform sensing tasks can be referred to as a sensing UE. When a UE connects to a serving cell, it can be configured to perform sensing tasks, sometimes in conjunction with a Transmit Receive Point (TRP). In some cases, a UE can also move from a serving cell (e.g., a source cell) to another cell (e.g., a target cell), which becomes the new serving cell. In some cases, when a UE leaves a source cell, the existing sensing configuration becomes irrelevant, and once connected to the target cell, the UE is configured with a new sensing configuration associated with the target cell, resulting in gaps in the sensing tasks being performed by the UE.

[0007] In some examples, a network function entity (referred to herein as a Sensing Management Function (SnMF) network node or SnMF entity) may be configured to interface with one or more other network function entities (such as Access and Mobility Function (AMF) network nodes) to perform one or more control operations for sensing services. In some examples, a network function entity (referred to as a Sensing Repository (SR)) may also be configured to interface with one or more other network function entities to perform one or more control operations for sensing services. For example, the SR may maintain logs of which sensing UEs are associated with which sensing sessions and / or cells, etc. In some examples, the mobility service may be configured to interact with the SnMF network node and / or the SR. A UE leaving a source cell and / or the network node providing the source cell (e.g., a Radio Access Network (RAN) node) may notify the SnMF network node and / or the SR that the UE is leaving the source cell. Upon connection to a new cell, the UE providing the new cell and / or the RAN node may update the SnMF and / or the SR using the UE's new location. Based on the UE's location and / or other factors, the SnMF may decide to reconfigure the UE for sensing in the new cell. The transition to a new cell, the reporting of new UE locations, and the decision of whether to reconfigure the UE can all lead to the interruption of sensing operations. Summary of the Invention

[0008] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include a processing system comprising one or more processors and one or more memories coupled to the processors. The processing system is configured to cause the UE to receive first sensing configuration information associated with a source cell, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session. The processing system is configured to cause the UE to perform one or more sensing measurements based on the first sensing configuration. The processing system is configured to cause the UE to receive a handover command associated with a handover operation to hand over the UE from the source cell to a target cell, the handover command including second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell. The processing system is configured to cause the UE to perform the handover operation associated with the handover command. The processing system is configured to cause the UE to perform one or more additional sensing measurements based on the second sensing configuration.

[0009] Some aspects described herein relate to a first network node for wireless communication. The first network node may include a processing system comprising one or more processors and one or more memories coupled to the processors. The processing system may be configured to cause the first network node to send to a UE first sensing configuration information associated with a source cell provided by the first network node, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session. The processing system may be configured to cause the first network node to receive from the UE mobility measurement information associated with at least one of the source cell or a target cell. The processing system may be configured to cause the first network node to send to a second network node a handover request indicating sensing session request information associated with the sensing session.

[0010] The processing system can be configured to cause the first network node to receive from the second network node a handover request associated with a handover operation that switches the UE from a source cell to a target cell provided by the first network node. The processing system can also be configured to cause the first network node to receive sensing session information associated with a sensing session, wherein the sensing session is associated with the UE. Finally, the processing system can be configured to cause the first network node to perform the handover operation based on the handover request.

[0011] The processing system can be configured to cause the first network node to receive a sensing configuration request associated with a sensing session, which is associated with a UE, from a second network node. The processing system can also be configured to cause the first network node to send a sensing configuration response, indicating sensing session information associated with the sensing session, to the second network node in association with the sensing configuration request.

[0012] The processing system can be configured to cause the first network node to receive from the second network node a first handover request associated with a handover operation that involves switching a UE from a source cell provided by the second network node to a target cell provided by a third network node, wherein the UE is associated with a sensing session. The processing system can also be configured to cause the first network node to send a handover command associated with the handover operation to the second network node in association with the handover request.

[0013] Some aspects described herein relate to a method for wireless communication by a UE. The method may include receiving first sensing configuration information associated with a source cell, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session. The method may include performing one or more sensing measurements based on the first sensing configuration. The method may include receiving a handover command associated with a handover operation to hand over the UE from the source cell to a target cell, the handover command including second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell. The method may include performing the handover operation associated with the handover command. The method may include performing one or more additional sensing measurements based on the second sensing configuration.

[0014] Some aspects described herein relate to a method for wireless communication by a first network node. The method may include sending to a UE first sensing configuration information associated with a source cell provided by the first network node, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session. The method may include receiving from the UE mobility measurement information associated with at least one of the source cell or a target cell. The method may include sending to a second network node a handover request indicating sensing session request information associated with the sensing session.

[0015] Some aspects described herein relate to a method for wireless communication by a first network node. The method may include receiving from a second network node a handover request associated with a handover operation to hand over a UE from a source cell to a target cell provided by the first network node. The method may include receiving sensing session information associated with a sensing session, wherein the sensing session is associated with the UE. The method may include performing the handover operation based on the handover request.

[0016] Some aspects described herein relate to a method for wireless communication by a first network node. The method may include receiving a sensing configuration request associated with a sensing session, wherein the sensing session is associated with a UE, from a second network node. The method may also include sending a sensing configuration response, indicating sensing session information associated with the sensing session, to the second network node in association with the sensing configuration request.

[0017] Some aspects described herein relate to a method for wireless communication by a first network node. The method may include receiving from a second network node a first handover request associated with a handover operation of a UE (User Equipment) switching from a source cell provided by the second network node to a target cell provided by a third network node, wherein the UE is associated with a sensing session. The method may include sending a handover command associated with the handover operation to the second network node in connection with the handover request.

[0018] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions causes the UE to receive first sensing configuration information associated with a source cell, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session. When executed by one or more processors of the UE, the set of instructions causes the UE to perform one or more sensing measurements according to the first sensing configuration. When executed by one or more processors of the UE, the set of instructions causes the UE to receive a handover command associated with a handover operation to switch the UE from the source cell to a target cell, the handover command including second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell. When executed by one or more processors of the UE, the set of instructions causes the UE to perform the handover operation associated with the handover command. When executed by one or more processors of the UE, the set of instructions causes the UE to perform one or more additional sensing measurements according to the second sensing configuration.

[0019] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a first network node. When executed by one or more processors of the first network node, the set of instructions enables the first network node to send to a UE first sensing configuration information associated with a source cell provided by the first network node, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session. When executed by one or more processors of the first network node, the set of instructions enables the first network node to receive from the UE mobility measurement information associated with at least one of the source cell or the target cell. When executed by one or more processors of the first network node, the set of instructions enables the first network node to send to a second network node a handover request indicating sensing session request information associated with the sensing session.

[0020] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a first network node. When executed by one or more processors of the first network node, the set of instructions enables the first network node to receive from a second network node a handover request associated with a handover operation involving a UE from a source cell to a target cell provided by the first network node. When executed by one or more processors of the first network node, the set of instructions enables the first network node to receive sensing session information associated with a sensing session, wherein the sensing session is associated with the UE. When executed by one or more processors of the first network node, the set of instructions enables the first network node to perform the handover operation according to the handover request.

[0021] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a first network node. When executed by one or more processors of the first network node, the set of instructions enables the first network node to receive a sensing configuration request associated with a sensing session, which is associated with a UE, from a second network node. When executed by one or more processors of the first network node, the set of instructions enables the first network node to send a sensing configuration response, in association with the sensing configuration request, to the second network node indicating sensing session information associated with the sensing session.

[0022] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a first network node. When executed by one or more processors of the first network node, the set of instructions enables the first network node to receive from a second network node a first handover request associated with a handover operation involving a UE (User Equipment) from a source cell provided by the second network node to a target cell provided by a third network node, wherein the UE is associated with a sensing session. When executed by one or more processors of the first network node, the set of instructions enables the first network node to send a handover command associated with the handover operation to the second network node in connection with the handover request.

[0023] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving first sensing configuration information associated with a source cell, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session. The apparatus may include components for performing one or more sensing measurements based on the first sensing configuration. The apparatus may include components for receiving a handover command associated with a handover operation to hand over the UE from the source cell to a target cell, the handover command including second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell. The apparatus may include components for performing the handover operation associated with the handover command. The apparatus may include components for performing one or more additional sensing measurements based on the second sensing configuration.

[0024] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting to a UE first sensing configuration information associated with a source cell provided by the apparatus, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session. The apparatus may include components for receiving from the UE mobility measurement information associated with at least one of the source cell or a target cell. The apparatus may include components for transmitting to a second network node a handover request indicating sensing session request information associated with the sensing session.

[0025] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving from a network node a handover request associated with a handover operation to hand over a UE from a source cell to a target cell provided by the apparatus. The apparatus may include components for receiving sensing session information associated with a sensing session, wherein the sensing session is associated with the UE. The apparatus may include components for performing the handover operation according to the handover request.

[0026] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a sensing configuration request associated with a sensing session, which is associated with a UE, from a network node. The apparatus may also include components for transmitting a sensing configuration response, in association with the sensing configuration request, to the network node indicating sensing session information associated with the sensing session.

[0027] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving from a first network node a first handover request associated with a handover operation of switching a UE from a source cell provided by the first network node to a target cell provided by a second network node, wherein the UE is associated with a sensing session. The apparatus may include components for transmitting, in association with the handover request, a handover command associated with the handover operation to the first network node.

[0028] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0029] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0030] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0031] Figure 1 This is a diagram illustrating an example of a wireless communication network according to the present disclosure.

[0032] Figure 2 This is a diagram illustrating communication between an example network node and an example UE in a wireless network according to this disclosure.

[0033] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0034] Figure 4A and Figure 4B This is a diagram illustrating an example of RF sensing according to the present disclosure.

[0035] Figure 5 This is an example of a core network configured to provide sensing services according to this disclosure.

[0036] Figure 6 This is an example of a control plane architecture for sensing services based on this disclosure.

[0037] Figure 7 This is an example of a SnMF entity for sensing services according to this disclosure.

[0038] Figure 8 This is a diagram illustrating example operations associated with UE handover according to this disclosure.

[0039] Figure 9 This is a diagram illustrating example operations associated with UE handover for sensing services and related changes in UE configuration in accordance with this disclosure.

[0040] Figure 10 This is a diagram illustrating example operations associated with UE handover for sensing services and related changes in UE configuration in accordance with this disclosure.

[0041] Figure 11 This is a diagram illustrating example operations associated with UE handover for sensing services and related changes in UE configuration in accordance with this disclosure.

[0042] Figure 12 This is a flowchart illustrating an example process of supporting sensing operations performed, for example, at a UE or a device of a UE, according to this disclosure.

[0043] Figure 13 This is a flowchart illustrating an example process for supporting sensing operations performed, for example, at a first network node or at a device of the first network node, according to the present disclosure.

[0044] Figure 14 This is a flowchart illustrating an example process for supporting sensing operations performed, for example, at a first network node or at a device of the first network node, according to the present disclosure.

[0045] Figure 15 This is a flowchart illustrating an example process for supporting sensing operations performed, for example, at a first network node or at a device of the first network node, according to the present disclosure.

[0046] Figure 16 This is a flowchart illustrating an example process for supporting sensing operations performed, for example, at a first network node or at a device of the first network node, according to the present disclosure.

[0047] Figure 17 This is a diagram of an example device for wireless communication that supports sensing operation according to the present disclosure.

[0048] Figure 18 This is a diagram of an example device for wireless communication that supports sensing operation according to the present disclosure. Detailed Implementation

[0049] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a method of practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods of practice using those other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0050] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various boxes, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0051] The various aspects generally involve user equipment (UE) handover for sensing services and associated changes in UE configuration. Some aspects more specifically involve the mobility process of UEs configured as sensing units (SUs) for integrated sensing and communication (ISAC) services. In some aspects, mobility service network nodes may be configured to facilitate the coordination of configuration changes resulting from handover. For example, mobility service network nodes may interact with network function entities (referred to herein as sensing management function (SnMF) network nodes) to facilitate rapid reconfiguration of UEs moving from a source cell to a target cell and / or radio access network (RAN) nodes associated with the target cell. In some aspects, the network node providing the source cell may send (e.g., routable or forwardable) a handover request to the mobility service, which includes information associated with a sensing session, such as, for example, a sensing session identifier (ID), SnMF address, sensing configuration, and / or sensing configuration requirements, etc. The mobility service may use the provided information to select a target RAN node that supports the sensing service. The mobility service may forward the handover request to the selected target RAN node, which may provide a handover instruction to the SnMF. SnMF can provide information to the target RAN node, which can be used by the target RAN node to configure itself and / or the UE for continued sensing operations in association with the target cell provided by the target RAN node.

[0052] In some aspects, the source RAN node may provide sensing configuration and / or sensing configuration requirement information to the mobility service in the handover request, and the mobility service may provide this information to the SnMF for receiving sensing configuration requirements from the target RAN node. In other aspects, the mobility service may be configured to obtain sensing configuration requirements associated with the target RAN node. For example, the mobility service may not receive sensing configuration and / or sensing configuration requirement information in the handover request; in this case, the mobility service may request the sensing configuration requirements from the SnMF (e.g., by including the target cell ID and UE ID in the request to the SnMF). The mobility service may include the sensing configuration requirements in the handover request provided to the target RAN node.

[0053] In some aspects, the target RAN node can provide the SnMF with a set of parameters associated with its supported sensing configurations and the allowed range of values ​​for each parameter. The SnMF can provide the target RAN node with the value of each parameter. In some aspects, the target RAN node can be configured using a set of supported profiles and an associated set of sensing quality of service (QoS). The target RAN node can indicate to the SnMF the set of supported profiles, which can be used to select the sensing profile for the sensing session when the UE operates in the target cell. The SnMF can provide the target RAN node with a response message indicating the selected sensing profile.

[0054] In some aspects, the wireless communication network may not include mobility services. In this case, the target RAN node may perform one or more of the operations described as being performed by the aforementioned mobility services. For example, the source RAN node may send a handover request to the target RAN node including information associated with the ongoing sensing service (e.g., sensing session ID, SnMF ID, and / or SnMF address). The target RAN node may send a handover indication to the SnMF, which includes the UE ID, sensing session information, and / or supported sensing configurations, etc. The SnMF may respond with a sensing configuration request, and the target RAN node may use the sensing configuration request to prepare resources to support the sensing service. The target RAN node may notify the source RAN node of a new sensing configuration associated with the target RAN node. The source RAN node may initiate a UE handover by sending a handover command to the UE including the new sensing configuration.

[0055] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques can be used to ensure that a handover in which a UE moves from a source cell to a target cell is performed while minimizing disruption to the sensing session. For example, by using mobility services to facilitate coordination of configuration changes resulting from the handover, the described techniques can be used to reduce the likelihood of disruption to the sensing session based on a UE handover from a source cell to a target cell. In some aspects, by configuring mobility services to obtain sensing configuration requirements associated with a target RAN node, the described techniques can be used to reduce signaling overhead, processing overhead, and / or latency associated with the target RAN node when preparing for a UE handover to the target cell, where the sensing session continues.

[0056] In some aspects, by providing the SnMF with a set of sensing configuration parameters supported by the target RAN node, the described techniques can be used to reduce signaling overhead associated with the target RAN node during preparation for UE handover to the target cell, where the sensing session continues because the SnMF can be configured to provide only the values ​​of the parameters, rather than configuration information defining the parameters themselves. In some aspects, by configuring the target RAN node to perform configuration change management functions for mobility services, the described techniques enable the implementation of one or more aspects of the efficient UE handover techniques described herein in networks lacking configured mobility service network nodes, thereby expanding the applicability of UE handover techniques and positively impacting network performance and versatility in conjunction with integrated sensing and communication scenarios.

[0057] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0058] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. These technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0059] Figure 1This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0060] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific radio access technology (RAT) (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RAT, 5G / NR RAT, and / or 6G RAT, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0061] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0062] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may also be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0063] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0064] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0065] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0066] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0067] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may be mobile based on the location of the associated mobile network node 110 (e.g., a train, satellite base station, unmanned aerial vehicle, or non-terrestrial network (NTN) network node).

[0068] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0069] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0070] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). UE 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0071] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. In some examples, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0072] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0073] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an extended reality (XR) device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0074] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0075] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0076] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be collectively referred to as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0077] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or lower cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs capable of ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), and / or precise positioning, etc., within the wireless communication network 100. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between UEs 120 in the first category and UEs 120 in the second category). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0078] In some examples, UE 120 in the third category (RedCap UE) can support lower latency communication than UE 120 in the first category (NB-IoT UE or eMTC UE), and UE 120 in the second category (mission-critical IoT UE or premium UE) can support lower latency communication than UE 120 in the third category. Additionally or alternatively, in some examples, UE 120 in the third category (RedCap UE) can support higher wireless communication throughput than UE 120 in the first category (NB-IoT UE or eMTC UE), and UE 120 in the second category (mission-critical IoT UE or premium UE) can support higher wireless communication throughput than UE 120 in the third category. Additionally or alternatively, in some examples, the UE 120 in the first category (NB-IoT UE or eMTC UE) may support a longer battery life than the UE 120 in the third category (RedCap UE), and the UE 120 in the third category may support a longer battery life than the UE 120 in the second category (mission-critical IoT UE or premium UE).

[0079] In some examples, a Category 3 UE 120 (RedCap UE) may have the capability to meet a first device or performance requirement but not a second device or performance requirement (such as parameters specified for NR UE 120 other than Category 3 UE 120), while a Category 2 UE 120 (mission-critical IoT UE or premium UE) may have the capability to meet the second device or performance requirement (and in some examples, also the first device or performance requirement). For example, a Category 3 UE 120 may support a maximum MCS lower than that supported by a Category 2 UE 120 (e.g., a modulation scheme such as 256 Quadrature Amplitude Modulation (QAM)). As another example, a Category 3 UE may support a maximum transmit power lower than that of a Category 2 UE. As another example, a Category 3 UE 120 may have beamforming capabilities that are less advanced than those of a Category 2 UE 120 (e.g., a RedCap UE may not be able to form as many beams as a premium UE). As another example, a Category 3 UE 120 may require longer processing times than a Category 2 UE 120. As yet another example, a Category 3 UE 120 may include less hardware or less complex hardware (such as fewer antennas, fewer transmit antennas, and / or fewer receive antennas) compared to a Category 2 UE 120. Furthermore, a Category 3 UE 120 may not be able to communicate on a maximum BWP as wide as that of a Category 2 UE 120.

[0080] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0081] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0082] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO technology typically utilizes multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some radio access technologies (RATs) can employ advanced MIMO techniques such as mTRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0083] In some examples, wireless communication network 100 may support Integrated Sensing and Communication (ISAC) services. ISAC can refer to a system that uses the same systems and infrastructure used for communication (e.g., wireless communication network 100) to provide sensing capabilities (e.g., RF sensing capabilities). ISAC may sometimes be referred to as Joint Communications and Radar (JCR). One or more devices in wireless communication network 100 (such as UE 120, network node 110, and / or SU 160) may perform RF sensing via wireless communication network 100 (e.g., using one or more RF signals). RF sensing is a technique that enables wireless communication devices to acquire information about the environment and / or the characteristics of objects within the environment. RF sensing uses RF signals to determine the distance (range), angle, and / or instantaneous linear velocity of an object, etc. RF sensing can provide a range of functionalities for wireless communication devices, such as object detection, object recognition (e.g., vehicles, humans, or animals), object tracking, environmental monitoring, motion detection, high-accuracy positioning, health monitoring, immersive XR applications, home monitoring, weather monitoring, vehicle operation (e.g., maneuvering, navigation, and / or parking), pedestrian and / or obstacle detection for roads and / or railways, unmanned aerial vehicle (UAV) operation (e.g., UAV intrusion detection, UAV tracking, and / or collision avoidance), industrial operation (e.g., automated guided vehicles (AGVs), automated robots, and / or pedestrian detection), tracking and / or activity recognition, and more.

[0084] RF sensing can include communication-assisted sensing and / or sensing-assisted communication. Communication-assisted sensing can refer to a wireless communication device (such as the SU 160) using one or more hardware components and / or radio resources associated with communication to perform RF sensing. For example, the SU 160 can use RF signals (e.g., NR RF signals or other RF signals associated with wireless communication) to obtain information indicating the characteristics of the environment and / or objects within the environment. Sensing-assisted communication can refer to a wireless communication device using the sensing results to perform one or more communication operations. For example, the sensing results can improve communication performance, such as by enabling more accurate beamforming, faster beam fault recovery, and / or reducing channel state information (CSI) tracking overhead, etc.

[0085] For example, wireless communication network 100 may include one or more SU 160s. SU 160 may include UE 120, network node 110, TRP, IAB node, RAN node, and / or another wireless communication device capable of performing RF sensing. In some examples, SU 160 may acquire sensing data (sometimes referred to as 3GPP sensing data, 5G wireless sensing data, 6G wireless sensing data, or wireless sensing data) via radio signals. Additionally or alternatively, SU 160 may acquire sensing data via one or more sensors (such as cameras, video recorders, light detection and ranging (LiDAR) sensors, radar and / or sonar sensors, etc.). For example, SU 160 may acquire sensing data via Wi-Fi sensing, radar sensing, and / or another type of sensing. Sensing data acquired via sensors (sometimes referred to as non-3GPP sensing data) may be used by SU 160 (or another device) to determine the characteristics of objects and / or the characteristics of the environment. Non-3GPP sensing data may be used to achieve improved sensing results from wireless sensing performed by SU 160.

[0086] Wireless communication network 100 may include one or more network nodes 170. Network node 170 may include core network nodes, core network entities, and / or core network functions, etc. Network node 170 may include SnMF entities, AMF entities, gateways, network repository functions (e.g., one or more SRs), etc. SnMF entities may perform one or more operations for configuring, managing, and / or maintaining sensor configurations for one or more sensing requests. For example, network node 170 may receive a sensing request from a client device (e.g., a server device or a sensing client) and configure one or more SUs 160 to perform RF sensing to obtain sensing data according to the sensing request, as described in more detail elsewhere herein. Figure 1 As shown, network node 170 can communicate with SU 160 (e.g., directly and / or via network node 110) to configure and / or manage RF sensing operations.

[0087] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive first sensing configuration information associated with a source cell, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session; perform one or more sensing measurements according to the first sensing configuration; receive a handover command associated with a handover operation to hand over the UE from the source cell to a target cell, the handover command including second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell; perform the handover operation associated with the handover command; and perform one or more additional sensing measurements according to the second sensing configuration. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0088] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send to a user equipment (UE) first sensing configuration information associated with a source cell provided by the first network node, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session; receive from the UE mobility measurement information associated with at least one of the source cell or the target cell; and send to a second network node a handover request indicating sensing session request information associated with the sensing session. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0089] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive from a second network node a handover request associated with a handover operation to switch a user equipment (UE) from a source cell to a target cell provided by the first network node; receive sensing session information associated with a sensing session, wherein the sensing session is associated with the UE; and perform the handover operation in accordance with the handover request. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0090] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a sensing configuration request associated with a sensing session, wherein the sensing session is associated with a user equipment (UE), from a second network node; and, in association with the sensing configuration request, send a sensing configuration response to the second network node indicating sensing session information associated with the sensing session. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0091] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive from a second network node a first handover request associated with a handover operation to switch a user equipment (UE) from a source cell provided by the second network node to a target cell provided by a third network node, wherein the UE is associated with a sensing session; and send a handover command associated with the handover operation to the second network node in connection with the handover request. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0092] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0093] like Figure 2 As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0094] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as referring to a combination of... Figure 2Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0095] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The processors in the first set and the processors in the second set can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to mean any one or more memories of the corresponding device, such as combined... Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0096] For downlink communication from network node 110 to UE 120, transmit processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmit processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) based on the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmit processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0097] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., T A set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., [missing information]) together via a set of corresponding antennas 234. T (One downlink signal).

[0098] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0099] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0100] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use for transmitting and / or receiving communication with RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0101] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0102] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0103] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0104] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0105] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a Channel Quality Indicator (CQI) parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of RSRP, RSSI, RSRQ, CQI, TPC, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0106] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink SRS, and / or another type of reference signal. Symbols from transmit processor 264 may be pre-decoded by TX MIMO processor 266 where applicable, and further processed by an assembly of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can (where applicable) perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, and can provide an output symbol stream set (e.g., ...) to the assembly of modems 254. U Each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0107] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0108] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0109] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0110] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0111] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0112] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330s via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340s via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120s via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0113] Each component of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0114] In some respects, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0115] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0116] The non-RT RIC 350 may include or implement logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0117] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0118] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with UE handover for sensing configuration, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with UE handover for sensing configuration, as described in more detail elsewhere herein. Figure 2 Any other component, CU310, DU 330, or RU 340, may (alone or in combination with one or more other processors) perform or direct, for example... Figure 12 Process 1200 Figure 13 Process 1300 Figure 14 Process 1400 Figure 15The operation of process 1500 or other processes as described herein. Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing instruction sets (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the instruction set may be made to be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 12 Process 1200 Figure 13 Process 1300 Figure 14 Process 1400 Figure 15 The process 1500 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0119] In some aspects, the UE (e.g., UE 120) includes: means for receiving first sensing configuration information associated with a source cell, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session; means for performing one or more sensing measurements according to the first sensing configuration; means for receiving a handover command associated with a handover operation to hand over the UE from the source cell to a target cell, the handover command including second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell; means for performing the handover operation associated with the handover command; and / or means for performing one or more additional sensing measurements according to the second sensing configuration. The means for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0120] In some aspects, the first network node (e.g., network node 110) includes: means for sending to a user equipment (UE) first sensing configuration information associated with a source cell provided by the first network node, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session; means for receiving from the UE mobility measurement information associated with at least one of the source cell or the target cell; and / or means for sending to a second network node a handover request indicating sensing session request information associated with the sensing session.

[0121] In some aspects, the first network node (e.g., network node 110) includes: components for receiving from a second network node a handover request associated with a handover operation to hand over a user equipment (UE) from a source cell to a target cell provided by the first network node; components for receiving sensing session information associated with a sensing session, wherein the sensing session is associated with the UE; and / or components for performing the handover operation according to the handover request.

[0122] In some aspects, the first network node (e.g., network node 110) includes: components for receiving a sensing configuration request associated with a sensing session from a second network node, wherein the sensing session is associated with a user equipment (UE); and / or components for sending a sensing configuration response to the second network node in association with the sensing configuration request, indicating sensing session information associated with the sensing session.

[0123] In some aspects, the first network node (e.g., network node 110) includes: components for receiving from a second network node a first handover request associated with a handover operation to switch a user equipment (UE) from a source cell provided by the second network node to a target cell provided by a third network node, wherein the UE is associated with a sensing session; and / or components for sending a handover command associated with the handover operation to the second network node in connection with the handover request. Components for the first network node to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0124] Figure 4A and Figure 4BThis is a diagram illustrating an example of RF sensing according to this disclosure. Wireless communication signals (e.g., RF signals configured to carry OFDM symbols) transmitted between UE 120 and network node 110 can be reused for RF sensing. RF sensing using wireless communication signals can be considered as consumer-grade radar with advanced detection capabilities, enabling contactless / device-free interaction with devices / systems, etc. "RF sensing" can be radar operation performed by wireless communication devices (such as UEs, network entities, or another device (such as wireless local area network (WLAN) access points)) using wireless communication signals.

[0125] RF sensing can also be referred to as environmental sensing, radar sensing, WLAN sensing, Wi-Fi sensing, and / or wireless sensing, etc. The wireless communication signal used to perform RF sensing can be a cellular communication signal (e.g., LTE signal, NR signal, and / or 6G signal) or a WLAN signal (e.g., a Wi-Fi signal), etc. As an example, the wireless communication signal can be an OFDM waveform as used in wireless communication network 100. High-frequency communication signals (such as millimeter-wave signals) can be advantageously used as RF sensing signals because higher frequencies provide more accurate range (e.g., distance) detection and / or motion detection. As another example, a WLAN signal (e.g., a WLAN or Wi-Fi signal that would otherwise be used for wireless communication) can be used to perform RF sensing (e.g., to save power compared to using a higher frequency range signal). In such examples, RF sensing can be referred to as WLAN sensing or Wi-Fi sensing.

[0126] RF sensing can be performed using various frequency bands or ranges, such as millimeter wave bands or sub-6 GHz bands. In some examples, wireless communication devices performing RF sensing can sequentially use different frequencies (e.g., first using sub-6 GHz frequencies, then using millimeter wave frequencies) to change resolution (e.g., from coarse to fine), change detection range (e.g., from large to narrow), and / or change power consumption (e.g., from low to high), etc.

[0127] like Figure 4A and Figure 4B As shown, one or more SUs can detect and / or monitor target objects by sending and / or measuring wireless communication signals. Figure 4A An example of a single-station sensing 400 is depicted. For example, one or more SUs may be included in a wireless communication system 410 (such as a wireless communication network 100). A sensing transmitter 415 and a sensing receiver 420 may communicate RF signals (e.g., wireless communication signals) to perform RF sensing. In some examples, the sensing transmitter 415 and the sensing receiver 420 may be co-located, such as within a single SU (e.g., as in...). Figure 4A(As shown). An example of a sensor transmitter 415 and a sensor receiver 420 being co-located can be referred to as "single-station sensing". Figure 4B An example of a dual-site sensing 405 is depicted. For example, the sensing transmitter 415 and the sensing receiver 420 may not be co-located (e.g., as shown in the image). Figure 4B (As depicted). For example, the sensing transmitter 415 and the sensing receiver 420 may be included in a separate device, such as in a separate unit. An example where the sensing transmitter 415 and the sensing receiver 420 are not co-located (e.g., included in different entities) may be referred to as "dual-station sensing". In some examples, RF sensing may be associated with obtaining sensor data indicating characteristics of the target object 425. In other examples, RF sensing operation may include multiple sensing transmitters 415 and / or multiple sensing receivers 420 (e.g., referred to as "multi-station sensing").

[0128] like Figure 4A and Figure 4B As shown, the sensing transmitter 415 can transmit one or more signals 430. The one or more signals 430 can be RF signals, wireless communication signals, OFDM signals, and / or sensing reference signals, etc. One or more signals can be reflected from the target object 425, resulting in a reflection 435 of the signal 430. Reflection 435 can be a reflection of the signal 430, a refraction of the signal 430, a diffraction of the signal 430, and / or a deflected version of the signal 430, etc. The sensing receiver 420 can receive and / or detect the reflection 435. The sensing receiver 420 can perform one or more measurements of the reflection 435 to obtain sensing data 440. Sensing data 440 can include information indicating one or more characteristics of the target object 425. For example, sensing data 440 can include signal strength (e.g., RSRP), received raw signal samples, channel delay distribution, one or more Doppler measurements (e.g., Doppler per channel tap), CSI, CQI, time delay measurements, and / or angle of arrival (AoA) (e.g., AoA per channel tap), etc.

[0129] like Figure 4A and Figure 4BAs shown, sensing data 440 can be used to perform sensing processing 445 to obtain sensing result 450. In some examples, a SU (e.g., which includes a sensing receiver 420) can perform sensing processing 445. In such examples, the SU can send sensing result 450 to network node 110. In other examples, another device (such as network node 110) can perform sensing processing 445. In such examples, the SU (e.g., which includes a sensing receiver 420) can send sensing data 440, and network node 110 can receive the sensing data. Sensing result 450 may include information about one or more characteristics of target object 425. For example, sensing result 450 may include location information, velocity information, sensing resolution, object detection information, and / or other information determined using transmitted data 440. Sensing result 450 may be provided to sensing service 455 of wireless communication system 410. Sensing service 455 may include one or more core network nodes or entities, such as one or more network nodes 170. For example, sensing service 455 may include SnMF entities, as described in more detail elsewhere herein. Sensing service 455 may provide sensing result 460 to client device 465. Sensing result 460 may be sensing result 450, or may be based on sensing result 450. Client device 465 may be a server device or an application running on the device. For example, client device 465 may provide a sensing request to sensing service 455. Sensing service 455 may configure, manage, and / or otherwise maintain sensing operations for fulfilling sensing requests (e.g., in a manner similar to that described herein).

[0130] Potential use cases for RF sensing include health monitoring (such as heart rate detection and / or respiratory rate monitoring), gesture recognition (such as human activity recognition, keystroke detection and / or sign language recognition), contextual information acquisition (such as location detection / tracking, direction finding and / or distance estimation), and / or automotive radar (such as intelligent cruise control and / or collision avoidance), among others.

[0131] Similar to conventional radar (e.g., frequency modulated continuous waveform (FMCW) radar), signal 430 can be used to estimate the range (e.g., range), velocity (e.g., Doppler spread), and / or angle (e.g., AoA) of target object 425. Unlike conventional radar, RF sensing can use the PHY layer for both RF sensing measurements and wireless communication. Signal 430 can be transmitted within a beam (e.g., using beamforming) and can be reflected from nearby objects within the beam. A portion of the transmitted RF signal is reflected back to the sensing receiver 420, i.e., reflection 435 (e.g., via reflection of the transmitted signal).

[0132] In some examples, OFDM waveforms can be used for both wireless communication (e.g., via wireless networks) and RF sensing. To use an OFDM waveform as a signal for RF sensing, a specific reference signal may be required, which will be referred to herein as a sensing reference signal. RF sensing performance (e.g., resolution and maximum values ​​for distance, velocity, and / or angle) can depend on the design of the sensing reference signal. For example, for gesture recognition use cases, a coarse distance / velocity estimate may be sufficient for RF sensing. That is, it may be sufficient for the wireless communication device to detect a movement pattern relative to the current location of a target object 425 (e.g., a user's hand or head). In such examples, a low-density (e.g., sparse) sensing reference signal with short wavelengths and narrow bandwidth may be sufficient to provide the necessary range and velocity resolution. For vibration detection use cases, such as for respiratory monitoring, accurate Doppler estimation may be important, while accurate distance estimation may be less important. In such examples, a high-density sensing reference signal with a long duration in the time domain may be beneficial. For position detection use cases, such as for object detection, accurate distance estimation may be important, while accurate Doppler estimation may be less important. In such examples, a high-density broadband sensing reference signal in the frequency domain may be beneficial. Therefore, network entities can configure one or more sensing reference signals depending on the use case of RF sensing to improve RF sensing performance. In some examples, the sensing reference signal can be a sounding reference signal (SRS), a wireless communication reference signal, or a WLAN signal, etc.

[0133] Figure 5 This is an example of a core network 500 configured to provide sensing services according to this disclosure. The core network 500 enables communication via a data network 505 and a RAN 510. The core network 500 can be a 5G core network, a 6G core network, a next-generation (NG) core network, or another type of core network. The RAN 510 can be a wireless communication network 100. The data network 505 can include one or more wired and / or wireless data networks. For example, the data network 505 can include an IP Multimedia Subsystem (IMS), a Public Land Mobile Network (PLMN), a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a private network (such as an enterprise intranet), an ad hoc network, the Internet, a fiber-optic-based network, a cloud computing network, a third-party service network, an operator service network, and / or combinations of such or other types of networks.

[0134] The core network 500 may include example functional architectures in which the systems and / or methods described herein can be implemented. For example... Figure 5As shown, the core network 500 may include one or more functional elements (e.g., one or more functions or entities) configured to provide sensing services 515 (e.g., RF sensing services or ISAC services). For example, the core network 505 may include a SnMF entity 520. The SnMF entity 520 may be configured to perform SU discovery, SU configuration, collection of sensing data from one or more SUs, processing of sensing data and / or opening of sensing results, etc. The core network 500 may include one or more sensing repositories 525. SR 525 may be a repository configured to store information about one or more SUs (such as SU location and / or SU capabilities, etc.). In some examples, one or more SR 525 may include a UE sensing repository configured to store information about UEs capable of operating as SUs (e.g., configured to operate in RAN 510). Additionally, one or more SR 525 may include a TRP sensing repository configured to store information about TRPs and / or network nodes capable of operating as SUs (e.g., configured to operate in RAN 510). In some examples, SR 525 may include information for both the UE and TRP capable of operating as a SU. In some examples, one or more SR 525s may be a dedicated service within SnMF 520. In other examples, one or more SR 525s may be part of another network function, such as AMF or Network Storehouse Function (NRF) 545. In other examples, SR 525 may be a standalone network function. Core network 500 may include sensor data function 530. Sensor data function 530 may be configured to perform processing of sensor data (e.g., collected via one or more SUs in RAN 510) to produce sensing results, as described in more detail elsewhere herein.

[0135] The core network 500 may include one or more RF sensors 535 configured to acquire sensor data. The one or more RF sensors 535 may include cameras, LiDAR sensors, radar sensors, sonar sensors, and / or Wi-Fi sensors, etc. The one or more RF sensors 535 may be referred to as non-3GPP sensors. The core network 500 may include a service discovery function 540. The service discovery function 540 may be configured to store information about one or more services supported by the core network 500 and / or RAN 510. In some examples, the service discovery function 540 may be configured to (e.g., to provide indications to one or more devices in RAN 510, such as one or more network nodes 110) of one or more services supported by the core network 500, such as the sensing services described herein. For example, the service discovery function 540 may include one or more devices that support the opening of capabilities and / or events in the wireless telecommunications system to help other entities in the wireless telecommunications system discover network services. The service discovery function 540 may also be referred to as a Network Opening Function (NEF).

[0136] The core network 500 may include an NRF 545. The NRF 545 may be configured as a centralized repository for one or more network functions supported by the core network 500 and / or RAN 510. For example, other functional elements of the core network 500 may access the NRF 545 to obtain information about functions or services provided by the core network 500, such as the sensing services described herein. The core network 500 may include a topology entity 550. The topology entity 550 may be configured to store and / or manage information for network topology, such as the topology of RAN 510. The core network 500 may include a capability entity 555. The capability entity 555 may store information indicating the capabilities of a corresponding node or device (e.g., in RAN 510). The core network 500 may include a Network Data Analysis Function (NWDAF) 560. The NWDAF 560 may include one or more devices that collect information associated with UE 120, SU, and / or RAN 510. The NWDAF 560 may perform analyses based on the collected information. Different parts of the core network 500 can subscribe to receive analytics updates from the NWDAF 560. In some examples, the sensor data function 530 may be a component of the NWDAF 560. The core network 500 may include a data function entity 565. The data function entity 565 may be configured to determine, acquire, and / or provide data for the RAN 510.

[0137] The core network 500 may include those not in Figure 5Other functional elements described include Network Slice Selection Function (NSSF), Network Open Function (NEF), Authentication Server Function (AUSF), Unified Data Management (UDM) component, Policy Control Function (PCF), Application Function (AF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and / or User Plane Function (UPF), etc. Figure 5 As shown, the functional elements of the core network 500 can communicate via a message bus 570. The message bus 570 can be a logical communication structure and / or a physical communication structure for communication between functional elements. Therefore, the message bus 570 can permit communication between two or more functional elements, whether logically (e.g., using one or more application programming interfaces (APIs) and / or physically (e.g., using one or more wired and / or wireless connections).

[0138] Figure 6 This is an example of a control plane architecture 600 for sensing services according to this disclosure. For example... Figure 6 As shown, the control plane architecture 600 may include a client device 605. The client device 605 may be a location service (LCS) client or a sensing service client. The client device 605 can provide sensing requests associated with the sensing service.

[0139] Control plane architecture 600 may include sensing gateway 610. Sensing gateway 610 may be configured as a gateway between client device 605 and a core network (such as core network 500). Sensing gateway 610 may implement one or more network functions, such as traffic routing, policy enforcement, charging, quality of service (QoS) management, and / or security. For example, sensing gateway 610 may route sensing requests from client device 605 to AMF 615 and / or SnMF 620. In other examples, AMF 615 may route sensing requests to the appropriate SnMF 620. Sensing gateway 610 and AMF 615 may communicate via an interface (shown as an NL2 interface). AMF 615 may communicate with one or more SnMF 620s. For example, AMF 615 and SnMF 620 may communicate via an interface (such as an NLx interface) (e.g., as defined by a wireless communication standard such as 3GPP or otherwise fixed). SnMF can be configured to operate as a trusted application service provider (ASP) entity for commissioning non-3GPP-RF sensors (in... Figure 6 (As shown in the image).

[0140] The control plane architecture 600 may include one or more SR 625s. As described elsewhere herein, the SR 625 may be a logical control function configured to store the identity, location, and / or capabilities of available Units (SUs) within the wireless communication network. The SR 625 may provide indication of available SUs to one or more SnMF 620s (e.g., expose the available SU). In some examples, the functionality of the SR may be provided by another network function (such as AMF 615, NRF ( Figure 6 (not shown) and / or SnMF 620) to perform. The control plane architecture 600 may include UDM 630. UDM 630 may include one or more devices for storing user data and profiles in the wireless telecommunications system. In some respects, UDM 630 may be used for fixed access and / or mobile access in the core network, etc.

[0141] The control plane architecture may include one or more UEs 120 and / or one or more network nodes 110. As described elsewhere herein, UE 120 may be configured to operate as a SU for sensing services (e.g., by SnMF 620, AMF 615, and / or network node 110). Additionally, network node 110 may be configured to operate as a SU (e.g., an application function (AF) SU) for sensing services (e.g., by SnMF 620, AMF 615, and / or another network node 110). The control plane architecture may include a NEF 635 communicating with one or more AFs 640. AF 640 may be an RF sensor, such as a camera, LiDAR sensor, radar sensor, sonar sensor, Wi-Fi sensor, or another non-3GPP RF sensor.

[0142] Figure 7 This is an example of a SnMF entity 700 for sensing services according to this disclosure. SnMF entity 700 may include one or more functional components configured to perform operations for sensing services, as described herein. For example, SnMF entity 700 may be configured to perform SU discovery and / or configuration, collection of sensing data, processing of sensing data and / or opening of sensing results, etc. SnMF entity 700 may include a sensing management component 705, a processing component 710, a UE sensing store 715 and / or a TRP sensing store 720, etc.

[0143] Sensing management component 705 may be configured to perform one or more operations for discovering and / or configuring SUs, as described in more detail elsewhere herein. Processing component 710 may be configured to generate or determine sensing results based on, in response to, or otherwise associated with collected sensor data (e.g., collected from one or more SUs). Processing component 710 may be physically executed at different (distributed) locations depending on the computing architecture of SnMF entity 700. UE sensing store 715 may store information about one or more UEs configured to operate as SUs, such as the UE's identifier, UE's location, and / or one or more UE capabilities, etc. TRP store 720 may store information about one or more TRPs configured to operate as SUs, such as the TRP's identifier, TRP's location, and / or one or more TRP capabilities, etc. UE sensing store 715 and / or TRP store 720 may be dedicated services within SnMF entity 700. Alternatively, UE sensing store 715 and / or TRP store 720 may be included in another network function, such as AMF or NRF. In some examples, SnMF entity 700 may include an SR that stores information about one or more TRPs and one or more UEs configured to operate as SUs.

[0144] In some examples, the wireless communication network may be associated with a single SnMF entity 700 for each PLMN. In such examples, the SnMF entity 700 may be configured as a single entry and exit point for sensing services. In such examples, a single logical SnMF entity 700 may exist, which can be implemented via multiple (distributed) SnMF instances. In other examples, multiple SnMF entities 700 may be defined and / or may be accessible. For example, SnMF entities 700 may be defined for corresponding service areas and / or corresponding service types. For example, a given SnMF entity 700 may be associated with a supported service area (e.g., the geographical area on which the SnMF manages sensing services), one or more supported service types, one or more supported QoS parameters for each supported service type, and / or one or more other capabilities. In some examples, one or more SnMF functionalities may be shared across multiple SnMF entities 700. For example, one or more SRs may be accessible by multiple SnMF entities 700.

[0145] In a wireless communication network, a User Equipment (UE) can be used as a Substitute and configured as a transmitter or receiver within an RF sensing operation. The UE can be configured by the Radio Access Network (RAN) to perform sensing tasks as part of an RF sensing operation. When the UE connects to a serving cell, it can be configured to perform sensing tasks, sometimes in conjunction with a Transmit Receive Point (TRP). In some cases, the UE can also move from a serving cell (e.g., a source cell) to another cell (e.g., a target cell), which becomes the new serving cell. In some cases, when the UE leaves the source cell, the existing sensing configuration becomes irrelevant, and once connected to the target cell, the UE is configured using a new sensing configuration associated with the target cell, resulting in gaps in the sensing tasks the UE is performing.

[0146] Figure 8 This is a diagram illustrating an example operation 800 associated with UE handover according to this disclosure. For example... Figure 8 As shown, UE 802, source network node 804, target network node 806, mobility service 808, and SnMF network node and / or UE storage network node (shown as SnMF / UE storage) 810 can communicate with each other. UE 802, source network node 804, target network node 806, mobility service 808, and SnMF / UE storage 810 can communicate via one or more network interfaces. The one or more network interfaces may include wired connections, wireless connections, and / or logical connections.

[0147] In some aspects, SnMF network nodes can be configured to interface with one or more other network function entities (such as Access and Mobility Function (AMF) network nodes) to perform one or more control operations for sensing services. In some aspects, network function entities (referred to as UE Repository Function Network Nodes or Sensing Repository (SR)) can be configured to interface with one or more other network function entities to perform one or more control operations for sensing services. For example, UE Repository Function Network Nodes can maintain logs of which UEs are associated with which sensing sessions and / or cells, etc. In some aspects, mobility services can be configured to interact with SnMF network nodes and / or UE Repository Network Nodes.

[0148] As shown in the figure, UE 802, connected to the source cell via source network node 804, can perform UE sensing operation 812. In operation 814, source network node 804 can make a handover decision. For example, source network node 804 can decide that UE 802 will be handed over to the target cell provided by target network node 806. Source network node 804, target network node 806, mobility service 808, and / or SnMF / UE store 810 can perform handover operation 816. In operation 818, mobility service 808 can send a handover command to source network node 804. In operation 820, source network node 804 can forward the handover command to UE 802. In operation 822, UE 802 (which is leaving the source cell) and / or source network node 804 can notify SnMF / UE store 810 that UE 802 is leaving the source cell (shown as "UE Leave Notification"). In operation 824, UE 802 can access the target cell via target network node 806. In operation 826, upon connection to the target cell, UE 802, source network node 802, and / or target network node 804 can update the SnMN / UE store using the new location of UE 802. Based on the UE location and / or other factors, the SnMN / UE store may decide to reconfigure UE 802 for sensing in the target cell, and in operation 828, UE 802 can re-establish sensing operations. The transition to the target cell, the reporting of the new UE location, and the decision on whether to reconfigure UE 802 can all potentially lead to interruptions in the sensing process.

[0149] Some aspects of the technology described herein can provide mobility procedures for UEs configured as SUs for ISAC services. In some aspects, mobility service network nodes can be configured to facilitate the coordination of configuration changes resulting from handover. For example, mobility service network nodes can interact with SnMF network nodes to facilitate rapid reconfiguration of UEs moving from a source cell to a target cell and / or RAN nodes associated with the target cell. In some aspects, the network node providing the source cell can send (e.g., routable or forwardable) a handover request to the mobility service, which includes information associated with a sensing session, such as, for example, a sensing session ID, SnMF address, sensing configuration, and / or sensing configuration requirements, etc. The mobility service can use the provided information to select a target RAN node that should support the sensing service. The mobility service can forward the handover request to the selected target RAN node, which can provide a handover indication to the SnMF. The SnMF can provide information to the target RAN node that can be used by the target RAN node to configure itself and / or the UE for continuing sensing operations associated with the target cell provided by the target RAN node.

[0150] Figure 9This is a diagram illustrating an example operation 900 associated with UE handover for sensing configuration according to this disclosure. Figure 9 As shown, UE 902, source network node 904, target network node 906, mobility service 908, and SnMF 910 can communicate with each other. UE 902, source network node 904, target network node 906, mobility service 908, and SnMF 910 can communicate via one or more network interfaces. The one or more network interfaces may include wired connections, wireless connections, and / or logical connections.

[0151] In Example 900, Mobility Service 908 may communicate with SnMF 910 to ensure rapid reconfiguration of UE 902 and / or target network node 906. In some aspects, the source network node may transmit a handover request to Mobility Service 908. The handover request may include a sensing session ID and SnMF address (e.g., associated with SnMF 910) for each sensing session. In some aspects, if the source network node 904 has multiple associated Transmit / Receive Points (TRPs), the source network node 904 may include a sensing configuration associated with each TRP. Mobility Service 908 may use the above information, along with other handover-related information, to select a target network node 906 that should support the sensing service. Mobility Service 908 may forward the handover request to the selected target network node 906. Target network node 906 may transmit a handover indication to SnMF 910. The handover indication may include, for example, a target cell ID and / or UE ID. Additionally, for each sensing session, the handover indication may include a sensing session ID and / or sensing-related information. In some aspects, SnMF 910 can transmit sensing configuration requests to target network node 906, and based on those requests, target network node 906 can determine whether it can accept UE 902. Based on this determination, target network node 906 can accept or reject the request. Target network node 906 can determine the sensing configuration for TRP and / or UE 902 based on the received requests. Target network node 906 provides this information to SnMF 910 for reference. After the handover is completed, UE 902 and / or target network node 905 can update SnMF 910 to indicate a successful handover and configuration.

[0152] In operation 912, UE 902 may perform UE sensing operations in conjunction with source network node 904. That is, for example, UE 902 may perform sensing measurements and provide them to source network node 904. In operation 914, UE 902 may send a Radio Resource Control (RRC) measurement report, and source network node 904 may receive the RRC measurement report. The RRC measurement report may include measurements associated with signal quality provided by source network node 904 and / or target network node 906. For example, the measurements may include mobility measurement information indicating one or more channel measurements. Based on the RRC measurements, source network node 904 may determine whether to perform a handover (in Figure 9 This is illustrated as a "handover decision" and a handover request may be sent to the mobility service 908 in operation 918. In some aspects, the handover request may indicate one or more target cell IDs, a list of active sensing services, a UE ID associated with the UE, and a list of sensing session IDs associated with active sensing sessions. In some aspects, the handover request may indicate the current sensing configuration, sensing configuration requirements, and / or quality of service (QoS) requirements, etc.

[0153] In operation 920, mobility service 908 may select target network node 906. For example, mobility service 908 may select target network node 906 based on an active sensing session and / or configuration requirements associated therewith. In some aspects, configuration requirements may include QoS requirements. In operation 922, mobility service 908 may send a handover request, and target network node 906 may receive the handover request. In some aspects, the handover request may include a target cell ID associated with a cell provided by target network node 906 and / or a UE ID associated with UE 902, etc. In some aspects, for each sensing session, the handover request may include sensing configuration requirements, sensing configuration parameters, and / or one or more sensing configurations associated with the sensing session.

[0154] In some operations, the target network node 906 may send a handover instruction, and the SnMF 910 may receive the handover instruction. In some aspects, the handover instruction may include a target cell ID associated with a cell provided by the target network node 906 and / or a UE ID associated with the UE 902, etc. In some aspects, for each sensing session, the handover instruction may include sensing configuration requirements, sensing configuration parameters, and / or one or more sensing configurations associated with the sensing session. In some aspects, the handover request may include sensing session request information. In some aspects, the sensing session request information may indicate at least one of the following: a target cell ID associated with a target cell, a sensing session ID associated with a sensing session, an additional sensing session ID associated with an additional sensing session, a UE ID associated with the UE, or an active service associated with the UE.

[0155] In operation 926, SnMF 910 may send a sensing configuration request, and the target network node 906 may receive the sensing configuration request. The sensing configuration request may include, for example, sensing session information. The sensing session information may indicate at least one set of parameter values ​​corresponding to at least one set of sensing configuration parameters. The at least one set of sensing configuration parameters may include multiple sets of sensing configuration parameters. Each of the multiple sets of sensing configuration parameters may be associated with a corresponding transmit / receive point (TRP) of the source network node 904.

[0156] In some aspects, the target network node 906 may provide a set of parameters (e.g., sensing reference signal bandwidth and / or sensing reference signal periodicity, etc.) associated with the sensing configuration supported by the target network node 906 in the handover indication. In some aspects, a set of parameters may be provided for each TRP of the target network node 906. Then, in operation 926, SnMF 910 may provide a value for each parameter. In some aspects, the provided values ​​may be provided for each TRP of the target network node 906.

[0157] In operation 928, the target network node 906 may perform admission control to allow UE 902 to enter the target cell, and in operation 930, the target network node 906 may send a sensing configuration response, and SnMF 910 may receive the sensing configuration response. The sensing configuration response may include the target cell ID, the UE ID, and, for each sensing session, a sensing session ID and sensing configuration.

[0158] In operation 932, the target network node 906 may send a handover request confirmation, and the mobility service 908 may receive the handover request confirmation (represented as "handover req. ack."). In operation 934, the mobility service 908 may send a handover command, and the source network node 904 may receive the handover command. In some aspects, the handover command may include the target cell ID, sensing session ID, and / or sensing configuration, etc. In operation 936, the source network node 904 may forward the handover command to the UE 902. In operation 938, the UE 902 may access the target cell via access communication operations with the target network node 906, and in operation 940, the target network node 906 may provide a handover confirmation to SnMF 910.

[0159] In some aspects, mobility service 908 may communicate directly with SnMF 910 to obtain the sensing configuration of target network node 906. For example, in operation 918, mobility service 908 may not receive sensing configuration or sensing configuration requests. In such cases, after operation 918, mobility service 908 may contact SnMF 910 to request the sensing configuration request of target network node 906. Mobility service 908 may include the target cell ID or target DU ID and UE ID in the request to SnMF 910. In some aspects, the sensing configuration request may depend on DU location, and therefore, SnMF 910 may provide different configuration requirements for target source node 906 compared to source network node 904. In some other aspects, SnMF 910 may determine that the sensing session will not be performed in association with target network node 906. In some aspects, mobility service 908 may select the target network node based on the sensing configuration request. In some aspects, mobility service 908 may include the sensing configuration request in the handover request of operation 922. In such cases, operations 924 and 926 can be omitted.

[0160] In some aspects, SnMF 910 can select a sensing configuration for target network node 906 from multiple predefined profiles. In some aspects, for example, a network operator service management entity (e.g., SMO), which may be an external entity of the wireless network, can provide target network node 906 with a list of possible configurations that target network node 906 can support (e.g., in the form of (sensing configuration, sensing QoS requirement) pairs). In the handover instruction of operation 924, the supported profiles can be provided to SnMF 910. For each sensing session, SnMF 910 can select the sensing profile to be used when UE 902 operates in the target cell. The selected configuration can be selected in association with the QoS requirements of the sensing session. SnMF 910 can send a response message to target network node 906 that includes the target cell sensing profile for each sensing session. SnMF 910 can provide the target cell sensing configuration associated with the target cell sensing profile in the handover request confirmation of operation 932.

[0161] Figure 10 This is a diagram illustrating an example operation 1000 associated with UE handover for sensing configuration according to this disclosure. For example... Figure 10As shown, UE 1002, source network node 1004, target network node 1006, and SnMF and / or UE storage (referred to as "SnMF / UE storage", where the UE storage is sometimes referred to as "sensor storage (SR)") 1008 can communicate with each other. UE 1002, source network node 1004, target network node 1006, and / or SnMF / UE storage 1010 can communicate via one or more network interfaces. The one or more network interfaces may include wired connections, wireless connections, and / or logical connections.

[0162] In Example 1000, upon receiving a handover command, UE 1002 and source network node 1004 can stop ongoing sensing operations and perform a handover procedure to switch UE 1002 to a target cell provided by target network node 1006. Once connected to the target cell, UE 1002 can notify SnMF / UE store 1008 of its new cell ID. In some aspects, the sensor store can update the SnMF for the new UE location independently, and the SnMF can determine whether to configure UE 1002 and / or target network node 1006 for sensing.

[0163] In operation 1010, UE 902 may perform UE sensing operations in conjunction with source network node 1004. That is, for example, UE 1002 may perform sensing measurements and provide them to source network node 1004. In operation 1012, source network node 1004 may determine whether to perform a handover (in... Figure 10 (Illustrated as "Handover Decision"). Source network node 1004, target network node 1006, and SnMF / UE store 1008 can perform handover operations to prepare for UE handover. In operation 1016, source network node 1004 can send a handover command, and UE 1002 can receive the handover command. Associated with sending the handover command, in operation 1018, source network node 1004 can terminate sensing operations with UE 1002.

[0164] In operation 1020, UE 1002 and / or source network node 1004 may send a notification that UE 1002 is leaving the source cell provided by source network node 1004, and SnMF / UE storage 1008 may receive this notification. In operation 1022, UE 1002 may access the target cell provided by target network node 1006 (e.g., using any number of access procedures). In operation 1024, UE 1002 and / or source network node 1004 may send a UE location notification indicating the location of UE 1002, and SnMF / UE storage 1008 may receive this UE location notification. In some aspects, in operation 1026, changes to the SnMF serving UE 1002 may occur based on the UE location. In operation 1028, UE 1002, target network node 1006, and SnMF / UE storage 1008 may reconstruct the sensing operation.

[0165] Figure 11 This is a diagram illustrating an example operation 1100 associated with UE handover for sensing configuration according to this disclosure. Figure 11 The example operation 1100 shown can be similar to Figure 9 As shown and combined above Figure 9 The example operation is described, but the target network node is described as being executed by... Figure 9 One or more of the operations performed by the mobility service 908 as described in the text.

[0166] like Figure 11 As shown, UE 1102, source network node 1104, target network node 1106, and SnMF 1108 can communicate with each other. UE 1102, source network node 1104, target network node 1106, and SnMF 1108 can communicate via one or more network interfaces. The one or more network interfaces may include wired connections, wireless connections, and / or logical connections.

[0167] In Example 1100, source network node 1104 may transmit a handover request to target network node 1106, the handover request including information associated with the ongoing sensing service (e.g., sensing session ID and / or SnMF ID). Target network node 1106 may transmit a handover indication to SnMF 1108, the handover indication including the UE ID, sensing session information, and one or more supported configurations. SnMF 1108 may provide target network node 1106 with appropriate sensing configuration requirements and / or provide an indication that target network node 1106 cannot support sensing. Network node 1106 may determine whether target network node 1106 can accept UE 1102 and / or whether target network node 1106 can support the sensing service. If target network node 1106 can support the service, target network node 1106 may prepare the necessary resources and notify source network node 1104. Source network node 1104 may initiate a handover, and after the handover is complete, UE 1102 and / or target network node 1106 may update SnMF 1108 regarding successful handover and sensing configuration. If the current SnMF 1108 determines that UE 1102 is not within the SnMF service area associated with SnMF 1108, SnMF 1108 may reject the request to support sensing services and / or may forward the request to the new SnMF, thereby conveying the associated context to facilitate the association between UE 1102 and the new SnMF.

[0168] In operation 1110, UE 1102 may perform UE sensing operations in conjunction with source network node 1104. That is, for example, UE 1102 may perform sensing measurements and provide them to source network node 1104. In operation 1112, UE 1102 may send an RRC measurement report, and source network node 1104 may receive the RRC measurement report. The RRC measurement report may include measurements associated with signal quality provided by source network node 1104 and / or target network node 1106. For example, the measurements may include mobility measurement information indicating one or more channel measurements. Based on the RRC measurements, in operation 1114, source network node 1104 may determine to perform a handover, and may send a handover request to mobility service 1108 in operation 1116. In some aspects, the handover request may indicate one or more target cell IDs, a list of active sensing services, and a list of sensing session IDs associated with active sensing sessions. In some aspects, the handover request may indicate the current sensing configuration, sensing configuration requirements, and / or QoS requirements, etc.

[0169] In operation 1118, target network node 1106 may send a handover instruction, and SnMF 1108 may receive the handover instruction. In some aspects, the handover instruction may include a target cell ID associated with a cell provided by target network node 1106 and / or a UE ID associated with UE 1102, etc. In some aspects, for each sensing session, the handover instruction may include sensing configuration requirements, sensing configuration parameters, and / or one or more sensing configurations associated with the sensing session. In some aspects, the handover request may include sensing session request information. In some aspects, the sensing session request information may indicate at least one of the following: a target cell ID associated with a target cell, a sensing session ID associated with a sensing session, an additional sensing session ID associated with an additional sensing session, a UE ID associated with a UE, or an active service associated with a UE. In operation 1120, SnMF 1108 may perform a SnMF change operation in association with the location of UE 1102.

[0170] In operation 1122, SnMF 1108 may send a sensing configuration request, and target network node 1106 may receive the sensing configuration request. The sensing configuration request may include, for example, sensing session information. The sensing session information may indicate at least one set of parameter values ​​corresponding to at least one set of sensing configuration parameters. The at least one set of sensing configuration parameters may include multiple sets of sensing configuration parameters. Each of the multiple sets of sensing configuration parameters may be associated with a corresponding TRP of source network node 1104. In operation 1124, target network node 1106 may perform admission control to allow UE 1102 to enter the target cell, and in operation 1126, target network node 1106 may send a sensing configuration response, and SnMF 1108 may receive the sensing configuration response. The sensing configuration response may include a target cell ID, a UE ID, and, for each sensing session, a sensing session ID and sensing configuration.

[0171] In operation 1128, the target network node 1106 may send a handover command, and the source network node 1104 may receive the handover command. In some aspects, the handover command may include the target cell ID, sensing session ID, and / or sensing configuration, etc. In operation 1130, the source network node 1104 may forward the handover command to the UE 1102. In operation 1132, the UE 1102 may access the target cell via access communication with the target network node 1106, and in operation 1134, the target network node 1106 may provide a handover confirmation to SnMF 1108.

[0172] Figure 12This is a flowchart illustrating an example process 1200 of supporting sensing operations performed, for example, at a UE or a device of a UE, according to the present disclosure. Example process 1200 is an example of a device or UE (e.g., UE 902, UE 1002, and / or UE 1102) performing operations associated with UE handover for sensing configuration.

[0173] like Figure 12 As shown, in some aspects, process 1200 may include receiving first sensing configuration information associated with a source cell, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session (block 1210). For example, a UE (such as by using...) Figure 17 The communication manager 1708 or receiving component 1702 depicted herein may receive first sensing configuration information associated with a source cell, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session, as described above.

[0174] like Figure 12 As further shown, in some aspects, process 1200 may include performing one or more sensing measurements according to a first sensing configuration (block 1220). For example, a UE (such as by using...) Figure 17 The communication manager 1708 and / or receiving component 1702 depicted herein may perform one or more sensing measurements according to a first sensing configuration, as described above.

[0175] like Figure 12 As further shown, in some aspects, process 1200 may include receiving a handover command associated with a handover operation to hand over the UE from the source cell to the target cell, the handover command including second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell (block 1230). For example, the UE (such as by using...) Figure 17 The communication manager 1708 or receiving component 1702 depicted herein may receive a handover command associated with a handover operation to hand over the UE from the source cell to the target cell, the handover command including second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell, as described above.

[0176] like Figure 12 As further shown, in some aspects, process 1200 may include performing a handover operation associated with a handover command (block 1240). For example, a UE (such as by using...) Figure 17 The communication manager 1708, receiving component 1702 and / or transmitting component 1704 depicted herein can perform switching operations in association with switching commands, as described above.

[0177] like Figure 12 As further shown, in some aspects, process 1200 may include performing one or more additional sensing measurements according to a second sensing configuration (block 1250). For example, a UE (such as by using...) Figure 17 The communication manager 1708 or receiver 1702 depicted herein may perform one or more additional sensing measurements according to a second sensing configuration, as described above.

[0178] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described in one or more other processes described below or in conjunction with other parts of this document.

[0179] In a first additional aspect, process 1200 includes obtaining one or more channel measurements associated with at least one of a source cell or a target cell; and sending mobility measurement information indicating the one or more channel measurements to a first network node providing the source cell, wherein receiving a handover command includes receiving a handover command in association with the mobility measurement information.

[0180] In a second additional aspect, either alone or in combination with the first aspect, the first sensing configuration information indicates a sensing session ID associated with the sensing session, and wherein the second sensing configuration information indicates the sensing session ID.

[0181] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, the first sensing configuration information indicates at least one additional sensing configuration associated with at least one additional sensing session, and wherein the second sensing configuration information indicates at least one additional sensing session ID associated with the at least one additional sensing session.

[0182] although Figure 12 An example box for process 1200 is shown, but in some respects, it differs from... Figure 12 Compared to the boxes depicted, process 1200 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1200 may be executed in parallel.

[0183] Figure 13 This is a flowchart illustrating an example process 1300 for supporting sensing operations performed, for example, at a first network node or a device of a first network node, according to the present disclosure. Example process 1300 is an example in which the device or the first network node (e.g., source network node 904, source network node 1004, or source network node 1104) performs operations associated with UE handover for sensing configuration.

[0184] like Figure 13As shown, in some aspects, process 1300 may include sending to the UE first sensing configuration information associated with a source cell provided by the first network node, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session (block 1310). For example, the first network node (such as by using...) Figure 18 The communication manager 1808 or transmission component 1804 depicted herein may transmit to the UE first sensing configuration information associated with a source cell provided by a first network node, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session, as described above.

[0185] like Figure 13 As further shown, in some aspects, process 1300 may include receiving mobility measurement information from the UE associated with at least one of the source cell or the target cell (box 1320). For example, a first network node (such as by using...) Figure 18 The communication manager 1808 or receiving component 1802 depicted herein can receive mobility measurement information associated with at least one of the source cell or the target cell from the UE, as described above.

[0186] like Figure 13 As further shown, in some aspects, process 1300 may include sending a switching request (box 1330) to a second network node indicating sensing session request information associated with the sensing session. For example, the first network node (such as by using...) Figure 18 The communication manager 1808 or transmitting component 1804 depicted above can send a switching request to a second network node, indicating sensing session request information associated with the sensing session, as described above.

[0187] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described in one or more other processes described below or in conjunction with other parts of this document.

[0188] In the first additional aspect, the second network node includes a RAN node that provides the target cell.

[0189] In a second additional aspect, either alone or in combination with the first aspect, the second network node includes a mobility service node that tracks mobility information associated with the UE.

[0190] In the third additional aspect, either alone or in combination with one or more of the first and second aspects, the sensing session request information indicates at least one of the following: the target cell ID associated with the target cell, the sensing session ID associated with the sensing session, the additional sensing session ID associated with the additional sensing session, the UE ID associated with the UE, or the active service associated with the UE.

[0191] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, process 1300 includes receiving from a second network node a handover command associated with a handover operation to hand over the UE from a source cell to a target cell; and sending the handover command to the UE.

[0192] In a fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, the handover command includes second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell.

[0193] although Figure 13 An example box for process 1300 is shown, but in some respects, it differs from... Figure 13 Compared to the boxes depicted, process 1300 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1300 may be executed in parallel.

[0194] Figure 14 This is a flowchart illustrating an example process 1400 for supporting sensing operations performed, for example, at a first network node or a device of a first network node, according to the present disclosure. Example process 1400 is an example in which the device or the first network node (e.g., target network node 906, target network node 1006, or target network node 1106) performs operations associated with UE handover for sensing configuration.

[0195] like Figure 14 As shown, in some aspects, process 1400 may include receiving from a second network node a handover request associated with a handover operation to hand over the UE from a source cell to a target cell provided by a first network node (block 1410). For example, the first network node (such as by using...) Figure 18 The communication manager 1808 or receiving component 1802 depicted above can receive from the second network node a handover request associated with a handover operation to switch the UE from the source cell to the target cell provided by the first network node, as described above.

[0196] like Figure 14 As further shown, in some aspects, process 1400 may include receiving sensing session information associated with a sensing session, wherein the sensing session is associated with the UE (box 1420). For example, a first network node (such as by using...) Figure 18 The communication manager 1808 or receiving component 1802 depicted herein can receive sensing session information associated with a sensing session, wherein the sensing session is associated with the UE, as described above.

[0197] like Figure 14As further shown, in some aspects, process 1400 may include performing a handover operation based on a handover request (box 1430). For example, a first network node (such as by using...) Figure 18 The communication manager 1808, receiving component 1802 and / or transmitting component 1804 depicted above can perform a switching operation based on a switching request, as described above.

[0198] Process 1400 may include additional aspects, such as any single aspect or any combination of aspects described in one or more other processes described below or in conjunction with other parts of this document.

[0199] In the first additional aspect, the second network node includes the RAN node that provides the source cell.

[0200] In a second additional aspect, either alone or in combination with the first aspect, process 1400 includes sending a switching instruction to a third network node including sensing session request information associated with the sensing session, wherein receiving the sensing session information includes receiving the sensing session information in association with the sensing session request information.

[0201] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, the sensing session request information indicates at least one set of sensing configuration parameters supported by the first network node, and wherein the sensing session information indicates at least one set of parameter values ​​corresponding to the at least one set of sensing configuration parameters.

[0202] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, the at least one set of sensing configuration parameters includes a plurality of sets of sensing configuration parameters, wherein each of the plurality of sets of sensing configuration parameters is associated with a corresponding TRP of the first network node.

[0203] In a fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, process 1400 includes sending sensing configuration response information to the third network node and in association with receiving the sensing session information.

[0204] In a sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, the sensing session information indicates a plurality of sensing sessions including the sensing session, and wherein the sensing configuration response information indicates at least one selected sensing session among the plurality of sensing sessions, the at least one selected sensing session including the sensing session.

[0205] In the seventh additional aspect, the third network node includes sensing service management functions, either alone or in combination with one or more of the first to sixth aspects.

[0206] In the eighth additional aspect, the switching request indicates the sensing session request information, either alone or in combination with one or more of the first to seventh aspects.

[0207] In the ninth additional aspect, either alone or in combination with one or more of the first to eighth aspects, the sensing session request information indicates at least one of the following: the target cell ID associated with the target cell, the sensing session ID associated with the sensing session, the additional sensing session ID associated with the additional sensing session, the UE ID associated with the UE, or the active service associated with the UE.

[0208] In the tenth additional aspect, alone or in combination with one or more of the first to ninth aspects, the second network node includes a mobility service node that tracks mobility information associated with the UE, and wherein the handover request includes the sensed session information.

[0209] In the eleventh additional aspect, either alone or in combination with one or more of the first to tenth aspects, process 1400 includes receiving an indication of a plurality of candidate sensing configurations from a network operator service management entity; and sending a switching indication to a third network node including sensing session request information associated with the sensing session, wherein the sensing session information indicates a selected sensing configuration among the plurality of candidate sensing configurations.

[0210] In the twelfth additional aspect, alone or in combination with one or more of the first to eleventh aspects, the sensing session information includes sensing configuration information associated with the target cell, wherein the sensing configuration information indicates a sensing configuration for continuing the sensing session in association with the target cell.

[0211] although Figure 14 An example box for process 1400 is shown, but in some respects, it differs from... Figure 14 Compared to the boxes depicted, process 1400 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1400 may be executed in parallel.

[0212] Figure 15 This is a flowchart illustrating an example process 1500 for supporting sensing operations performed, for example, at a first network node or a device of the first network node, according to the present disclosure. Example process 1500 is an example in which the device or the first network node (e.g., SnMF 910, SnMF / UE store 1008, or SnMF 1108) performs operations associated with UE handover for sensing configuration.

[0213] like Figure 15As shown, in some aspects, process 1500 may include receiving a sensing configuration request associated with a sensing session from a second network node, wherein the sensing session is associated with a UE (block 1510). For example, a first network node (such as by using...) Figure 18 The communication manager 1808 or receiving component 1802 depicted herein may receive a sensing configuration request associated with a sensing session, which is associated with the UE, as described above, from a second network node.

[0214] like Figure 15 As further shown, in some aspects, process 1500 may include sending a sensing configuration response (box 1520) to the second network node in association with the sensing configuration request, indicating sensing session information associated with the sensing session. For example, the first network node (such as by using...) Figure 18 The communication manager 1808 or transmitting component 1804 depicted herein may, in association with the sensing configuration request, send a sensing configuration response to the second network node indicating sensing session information associated with the sensing session, as described above.

[0215] Process 1500 may include additional aspects, such as any single aspect or any combination of aspects described in one or more other processes described below or in conjunction with other parts of this document.

[0216] In the first additional aspect, the second network node includes a RAN node that provides the target cell associated with the handover operation of switching the UE from the source cell to the target cell.

[0217] In a second additional aspect, either alone or in combination with the first aspect, the sensing configuration request includes a switching indication that includes sensing session request information associated with the sensing session, wherein the sensing configuration response includes sensing session information associated with the sensing session request information.

[0218] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, the sensing session request information indicates at least one set of sensing configuration parameters supported by the second network node, and wherein the sensing session information indicates at least one set of parameter values ​​corresponding to the at least one set of sensing configuration parameters.

[0219] In a fourth additional aspect, either alone or in combination with one or more of the first to third aspects, the at least one set of sensing configuration parameters includes a plurality of sets of sensing configuration parameters, wherein each of the plurality of sets of sensing configuration parameters is associated with a corresponding TRP of the second network node.

[0220] In the fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, the sensing session request information indicates at least one of the following: the target cell ID associated with the target cell, the sensing session ID associated with the sensing session, the additional sensing session ID associated with the additional sensing session, the UE ID associated with the UE, or the active service associated with the UE.

[0221] In a sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, the second network node includes a mobility service node that tracks mobility information associated with the UE, and wherein the sensing configuration request includes a handover request that includes sensing session request information.

[0222] In a seventh additional aspect, either alone or in combination with one or more of the first to sixth aspects, the sensing session information includes indications of a plurality of candidate sensing configurations, and the method further includes: selecting the sensing configuration from the plurality of candidate sensing configurations based on the sensing session request information.

[0223] In the eighth additional aspect, the second network node includes sensing service management functions, either alone or in combination with one or more of the first to seventh aspects.

[0224] although Figure 15 An example box for process 1500 is shown, but in some respects, it differs from... Figure 15 Compared to the boxes depicted, process 1500 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1500 may be executed in parallel.

[0225] Figure 16 This is a flowchart illustrating an example process 1600 of supporting sensing operations performed, for example, at a first network node or a device of the first network node, according to the present disclosure. Example process 1600 is an example in which a device or a first network node (e.g., mobility service 908) performs operations associated with UE handover for sensing configuration.

[0226] like Figure 16 As shown, in some aspects, process 1600 may include receiving from a second network node a first handover request associated with a handover operation to switch a UE from a source cell provided by the second network node to a target cell provided by a third network node, wherein the UE is associated with a sensing session (box 1610). For example, the first network node (such as by using...) Figure 18The communication manager 1808 or receiving component 1802 depicted herein may receive from a second network node a first handover request associated with a handover operation to switch a UE from a source cell provided by the second network node to a target cell provided by a third network node, wherein the UE is associated with a sensing session as described above.

[0227] like Figure 16 As further shown, in some aspects, process 1600 may include sending a handover command associated with the handover operation to a second network node in connection with the handover request (box 1620). For example, the first network node (such as by using...) Figure 18 The communication manager 1808 or sending component 1804 depicted in the diagram can send a handover command associated with the handover operation to the second network node in connection with the handover request, as described above.

[0228] Process 1600 may include additional aspects, such as any single aspect or any combination of aspects described in one or more other processes described below or in conjunction with other parts of this document.

[0229] In the first additional aspect, the switching request indicates sensing session request information associated with the sensing session.

[0230] In a second additional aspect, either alone or in combination with the first aspect, process 1600 includes selecting a third network node as the target network node from a plurality of candidate network nodes in association with sensing session request information.

[0231] In a third additional aspect, either alone or in combination with one or more of the first and second aspects, process 1600 includes sending a sensing configuration request associated with a sensing session to a fourth network node; receiving a sensing configuration response from the fourth network node in association with the sensing configuration request, indicating sensing session information associated with the sensing session; and sending a second handover request associated with a handover operation to a third network node, the second handover request including the sensing session information.

[0232] although Figure 16 An example box for process 1600 is shown, but in some respects, it differs from... Figure 16 Compared to the boxes depicted, process 1600 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1600 may be executed in parallel.

[0233] Figure 17This is a diagram of an example device 1700 for wireless communication supporting sensing operation according to the present disclosure. Device 1700 may be a UE, or a UE may include device 1700. In some aspects, device 1700 includes a receiving component 1702, a transmitting component 1704, and a communication manager 1708 that can communicate with each other (e.g., via one or more buses). As shown, device 1700 can use the receiving component 1702 and the transmitting component 1704 to communicate with another device 1706 (such as a UE, a network node, or another wireless communication device).

[0234] In some respects, device 1700 may be configured and / or capable of operating to perform the functions described herein. Figures 9 to 11 One or more operations described herein. Additionally or alternatively, the device 1700 may be configured and / or capable of operating to perform one or more processes described herein, such as Figure 12 The process 1200. In some aspects, the apparatus 1700 may include the above-described combination. Figure 2 One or more components of the UE as described.

[0235] Receiver 1702 may receive communications, such as reference signals, control information, and / or data communications, from device 1706. Receiver 1702 may provide the received communications to one or more other components of device 1700, such as communication manager 140. In some aspects, receiver 1702 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 1702 may include the combinations described above. Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers / processors, and / or one or more memories.

[0236] Transmitting component 1704 can transmit communications, such as reference signals, control information, and / or data communications, to device 1706. In some aspects, communication manager 140 can generate communications and send the generated communications to transmitting component 1704 for transmission to device 1706. In some aspects, transmitting component 1704 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and can transmit the processed signals to device 1706. In some aspects, transmitting component 1704 can include the combinations described above. Figure 2The described UE includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, and / or one or more memories. In some aspects, the transmit component 1704 may co-located with the receive component 1702 in one or more transceivers.

[0237] Communication manager 1708 may receive, or may cause receiving component 1702 to receive, first sensing configuration information associated with a source cell, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session. Communication manager 140 may perform one or more sensing measurements based on the first sensing configuration. Communication manager 140 may receive, or may cause receiving component 1702 to receive, a handover command associated with a handover operation to hand over the UE from the source cell to a target cell, the handover command including second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell. Communication manager 140 may perform the handover operation associated with the handover command. Communication manager 140 may perform one or more additional sensing measurements based on the second sensing configuration. In some aspects, communication manager 140 may perform one or more operations as described elsewhere herein by one or more components of communication manager 140.

[0238] Communication Manager 1708 may include the above-mentioned features. Figure 2 The described UE includes one or more controllers / processors and / or one or more memories. In some aspects, the communication manager 1708 includes a set of components. Alternatively, this set of components may be separate from and distinct from the communication manager 1708. In some aspects, one or more components in this set of components may include those described above. Figure 2 The described UE may have one or more controllers / processors and / or one or more memories, or may be implemented therein. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by one or more controllers or one or more processors to perform the function or operation of the component.

[0239] The receiving component 1702 may receive first sensing configuration information associated with a source cell, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session. The receiving component 1702 may perform one or more sensing measurements based on the first sensing configuration. The receiving component 1702 may receive a handover command associated with a handover operation to switch the UE from the source cell to a target cell, the handover command including second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell. The receiving component 1702 and / or the transmitting component 1704 may perform the handover operation in association with the handover command. The receiving component 1702 may perform one or more additional sensing measurements based on the second sensing configuration.

[0240] The receiving component 1702 can obtain one or more channel measurements associated with at least one of the source cell or the target cell.

[0241] The transmitting component 1704 may transmit mobility measurement information indicating the one or more channel measurements to a first network node providing the source cell, wherein receiving the handover command includes receiving the handover command in association with the mobility measurement information.

[0242] Figure 17 The number and arrangement of components shown are provided as an example. In reality, with... Figure 17 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 17 The two or more components shown can be implemented within a single component, or Figure 17 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 17 The collection of (one or more) components shown is executable and described as being composed of Figure 17 Another set of components shown performs one or more functions.

[0243] Figure 18 This is a diagram of an example device 1800 for wireless communication that supports sensing operation according to the present disclosure. Device 1800 may be a network node, or a network node may include device 1800. In some aspects, device 1800 includes a receiving component 1802, a transmitting component 1804, and a communication manager 1808 that can communicate with each other (e.g., via one or more buses). As shown, device 1800 can use the receiving component 1802 and the transmitting component 1804 to communicate with another device 1806 (such as a UE, a network node, or another wireless communication device).

[0244] In some respects, device 1800 may be configured and / or capable of operating to perform the functions described herein. Figures 9 to 11One or more operations described herein. Additionally or alternatively, the device 1800 may be configured and / or capable of operating to perform one or more processes described herein, such as Figure 13 Process 1300 Figure 14 Process 1400 Figure 15 Process 1500 and / or Figure 16 The process 1600. In some aspects, the apparatus 1800 may include the above-described combination. Figure 2 One or more components of the network node described.

[0245] Receiver 1802 may receive communications from device 1806, such as reference signals, control information, and / or data communications. Receiver 1802 may provide the received communications to one or more other components of device 1800, such as communication manager 150. In some aspects, receiver 1802 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components. In some aspects, receiver 1802 may include the combinations described above. Figure 2 The described network node includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, and / or one or more memories.

[0246] Transmitting component 1804 can transmit communications, such as reference signals, control information, and / or data communications, to device 1806. In some aspects, communication manager 150 can generate communications and send the generated communications to transmitting component 1804 for transmission to device 1806. In some aspects, transmitting component 1804 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and can transmit the processed signals to device 1806. In some aspects, transmitting component 1804 can include the combinations described above. Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, and / or one or more memories. In some aspects, the transmit component 1804 may co-located with the receive component 1802 in one or more transceivers.

[0247] The communication manager 1808 may send, or cause the transmitting component 1804 to send to the UE, first sensing configuration information associated with a source cell provided by the first network node, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session. The communication manager 1808 may receive, or cause the receiving component 1802 to receive from the UE, mobility measurement information associated with at least one of a source cell or a target cell. The communication manager 1808 may send, or cause the transmitting component 1804 to send to the second network node, a handover request indicating sensing session request information associated with a sensing session.

[0248] The communication manager 1808 may receive, or may cause the receiving component 1802 to receive from, a handover request associated with a handover operation to switch the UE from a source cell to a target cell provided by a first network node. The communication manager 1808 may receive, or may cause the receiving component 1802 to receive sensing session information associated with a sensing session, wherein the sensing session is associated with the UE. The communication manager 1808 may perform the handover operation based on the handover request.

[0249] The communication manager 1808 may receive, or may cause the receiving component 1802 to receive, a sensing configuration request associated with a sensing session, wherein the sensing session is associated with the UE. The communication manager 1808 may send, or may cause the sending component 1804 to send, a sensing configuration response indicating sensing session information associated with the sensing session to the second network node in association with the sensing configuration request.

[0250] The communication manager 1808 may receive, or may cause the receiving component 1802 to receive from, a second network node a first handover request associated with a handover operation to switch a UE from a source cell provided by the second network node to a target cell provided by a third network node, wherein the UE is associated with a sensing session. The communication manager 1808 may send, or may cause the transmitting component 1804 to send to the second network node in association with the handover request a handover command associated with the handover operation. In some aspects, the communication manager 1808 may perform one or more operations as described elsewhere herein by one or more components of the communication manager 150.

[0251] Communication Manager 1808 may include the above-mentioned features. Figure 2 The described network node includes one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units. In some aspects, the communication manager 1808 includes a set of components, alternatively, this set of components may be separate from and distinct from the communication manager 1808. In some aspects, one or more components in this set of components may include those described above. Figure 2 The described network node may include, or may contain, one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units. Additionally or alternatively, one or more components of this set may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of that component.

[0252] Transmitting component 1804 can send to the UE first sensing configuration information associated with a source cell provided by a first network node, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session. Receiving component 1802 can receive from the UE mobility measurement information associated with at least one of a source cell or a target cell. Transmitting component 1804 can send to a second network node a handover request indicating sensing session request information associated with a sensing session.

[0253] The receiving component 1802 can receive from the second network node a handover command associated with a handover operation that switches the UE from the source cell to the target cell.

[0254] The sending component 1804 can send a handover command to the UE.

[0255] The receiving component 1802 may receive from the second network node a handover request associated with a handover operation to switch the UE from the source cell to a target cell provided by the first network node. The receiving component 1802 may also receive sensing session information associated with a sensing session, wherein the sensing session is associated with the UE. The receiving component 1802 and / or the transmitting component 1804 may perform the handover operation based on the handover request.

[0256] The transmitting component 1804 can send a switching indication to a third network node, including sensing session request information associated with the sensing session, wherein receiving sensing session information includes receiving sensing session information in association with the sensing session request information.

[0257] The transmitting component 1804 can transmit sensing configuration response information to a third network node and in association with receiving sensing session information.

[0258] The receiving component 1802 can receive instructions for multiple candidate sensing configurations from the network operator service management entity.

[0259] The transmitting component 1804 may send a switching indication to a third network node, including sensing session request information associated with the sensing session, wherein the sensing session information indicates the selected sensing configuration among the plurality of candidate sensing configurations.

[0260] The receiving component 1802 can receive a sensing configuration request associated with a sensing session from a second network node, wherein the sensing session is associated with a UE. The transmitting component 1804 can send a sensing configuration response indicating sensing session information associated with the sensing session to the second network node in association with the sensing configuration request.

[0261] The receiving component 1802 may receive from a second network node a first handover request associated with a handover operation to switch a UE from a source cell provided by the second network node to a target cell provided by a third network node, wherein the UE is associated with a sensing session. The transmitting component 1804 may send a handover command associated with the handover operation to the second network node in association with the handover request.

[0262] The transmitting component 1804 can send a sensing configuration request associated with a sensing session to a fourth network node, and receive a sensing configuration response from the fourth network node in association with the sensing configuration request, indicating sensing session information associated with the sensing session.

[0263] The transmitting component 1804 may send a second handover request associated with the handover operation to a third network node, the second handover request including sensing session information.

[0264] Figure 18 The number and arrangement of components shown are provided as an example. In reality, with... Figure 18 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 18 The two or more components shown can be implemented within a single component, or Figure 18 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 18 The collection of (one or more) components shown is executable and described as being composed of Figure 18 Another set of components shown performs one or more functions.

[0265] The following provides an overview of some aspects of this disclosure:

[0266] Aspect 1: A method for wireless communication by a user equipment (UE), the method comprising: receiving first sensing configuration information associated with a source cell, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session; performing one or more sensing measurements according to the first sensing configuration; receiving a handover command associated with a handover operation to hand over the UE from the source cell to a target cell, the handover command including second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell; performing the handover operation associated with the handover command; and performing one or more additional sensing measurements according to the second sensing configuration.

[0267] Aspect 2: According to the method of aspect 1, the method further includes: obtaining one or more channel measurements associated with at least one of the source cell or the target cell; and sending mobility measurement information indicating the one or more channel measurements to a first network node providing the source cell, wherein receiving the handover command includes receiving the handover command in association with the mobility measurement information.

[0268] Aspect 3: The method according to any one of claims 1 or 2, wherein the first sensing configuration information indicates a sensing session identifier (ID) associated with the sensing session, and wherein the second sensing configuration information indicates the sensing session ID.

[0269] Aspect 4: According to the method of aspect 3, wherein the first sensing configuration information indicates at least one additional sensing configuration associated with at least one additional sensing session, and wherein the second sensing configuration information indicates at least one additional sensing session ID associated with the at least one additional sensing session.

[0270] Aspect 5: A method for wireless communication by a first network node, the method comprising: sending to a user equipment (UE) first sensing configuration information associated with a source cell provided by the first network node, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session; receiving from the UE mobility measurement information associated with at least one of the source cell or a target cell; and sending to a second network node a handover request indicating sensing session request information associated with the sensing session.

[0271] Aspect 6: According to the method of aspect 5, wherein the second network node includes a radio access network (RAN) node providing the target cell.

[0272] Aspect 7: The method according to any one of Aspects 5 to 6, wherein the second network node includes a mobility service node that tracks mobility information associated with the UE.

[0273] Aspect 8: The method according to any one of Aspects 5 to 7, wherein the sensing session request information indicates at least one of the following: a target cell identifier (ID) associated with the target cell, a sensing session ID associated with the sensing session, an additional sensing session ID associated with an additional sensing session, a UE ID associated with the UE, or an active service associated with the UE.

[0274] Aspect 9: The method according to any one of Aspects 5 to 8, the method further comprising: receiving from the second network node a handover command associated with a handover operation of switching the UE from the source cell to the target cell; and sending the handover command to the UE.

[0275] Aspect 10: According to the method of aspect 9, the handover command includes second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session in association with the target cell.

[0276] Aspect 11: A method for wireless communication by a first network node, the method comprising: receiving from a second network node a handover request associated with a handover operation of switching a user equipment (UE) from a source cell to a target cell provided by the first network node; receiving sensing session information associated with a sensing session, wherein the sensing session is associated with the UE; and performing the handover operation according to the handover request.

[0277] Aspect 12: According to the method of aspect 11, wherein the second network node includes a radio access network (RAN) node providing the source cell.

[0278] Aspect 13: The method of any one of claims 11 or 12, further comprising sending a switching indication to a third network node including sensing session request information associated with the sensing session, wherein receiving the sensing session information includes receiving the sensing session information in association with the sensing session request information.

[0279] Aspect 14: According to the method of aspect 13, wherein the sensing session request information indicates at least one set of sensing configuration parameters supported by the first network node, and wherein the sensing session information indicates at least one set of parameter values ​​corresponding to the at least one set of sensing configuration parameters.

[0280] Aspect 15: According to the method of aspect 14, the at least one set of sensing configuration parameters includes a plurality of sets of sensing configuration parameters, wherein each of the plurality of sets of sensing configuration parameters is associated with a corresponding transmit / receive point (TRP) of the first network node.

[0281] Aspect 16: The method according to any one of aspects 13 to 15, the method further comprising sending sensing configuration response information to the third network node and in association with receiving the sensing session information.

[0282] Aspect 17: According to the method of aspect 16, wherein the sensing session information indicates a plurality of sensing sessions including the sensing session, and wherein the sensing configuration response information indicates at least one selected sensing session among the plurality of sensing sessions, the at least one selected sensing session including the sensing session.

[0283] Aspect 18: The method according to any one of Aspects 13 to 17, wherein the third network node includes a sensing service management function.

[0284] Aspect 19: The method according to any one of Aspects 13 to 18, wherein the switching request indicates the sensing session request information.

[0285] Aspect 20: The method according to any one of Aspects 13 to 19, wherein the sensing session request information indicates at least one of the following: a target cell identifier (ID) associated with the target cell, a sensing session ID associated with the sensing session, an additional sensing session ID associated with an additional sensing session, a UE ID associated with the UE, or an active service associated with the UE.

[0286] Aspect 21: According to the method of aspect 11, wherein the second network node includes a mobility service node that tracks mobility information associated with the UE, and wherein the handover request includes the sensing session information.

[0287] Aspect 22: According to the method of aspect 21, the method further includes: receiving an indication of a plurality of candidate sensing configurations from a network operator service management entity; and sending a switching indication to a third network node including sensing session request information associated with the sensing session, wherein the sensing session information indicates a selected sensing configuration among the plurality of candidate sensing configurations.

[0288] Aspect 23: The method according to any one of Aspects 11 to 22, wherein the sensing session information includes sensing configuration information associated with the target cell, wherein the sensing configuration information indicates a sensing configuration for continuing the sensing session in association with the target cell.

[0289] Aspect 24: A method for wireless communication by a first network node, the method comprising: receiving from a second network node a sensing configuration request associated with a sensing session, wherein the sensing session is associated with a user equipment (UE); and sending to the second network node, in association with the sensing configuration request, a sensing configuration response indicating sensing session information associated with the sensing session.

[0290] Aspect 25: According to the method of aspect 24, the second network node includes a radio access network (RAN) node that provides a target cell associated with a handover operation to hand over the UE from the source cell to the target cell.

[0291] Aspect 26: According to the method of aspect 25, wherein the sensing configuration request includes a switching indication, the switching indication including sensing session request information associated with the sensing session, wherein the sensing configuration response includes sensing session information associated with the sensing session request information.

[0292] Aspect 27: According to the method of aspect 26, wherein the sensing session request information indicates at least one set of sensing configuration parameters supported by the second network node, and wherein the sensing session information indicates at least one set of parameter values ​​corresponding to the at least one set of sensing configuration parameters.

[0293] Aspect 28: According to the method of aspect 27, the at least one set of sensing configuration parameters includes a plurality of sets of sensing configuration parameters, wherein each of the plurality of sets of sensing configuration parameters is associated with a corresponding transmit / receive point (TRP) of the second network node.

[0294] Aspect 29: The method according to any one of Aspects 26 to 28, wherein the sensing session request information indicates at least one of the following: a target cell identifier (ID) associated with the target cell, a sensing session ID associated with the sensing session, an additional sensing session ID associated with an additional sensing session, a UE ID associated with the UE, or an active service associated with the UE.

[0295] Aspect 30: According to the method of aspect 24, wherein the second network node includes a mobility service node that tracks mobility information associated with the UE, and wherein the sensing configuration request includes a handover request that includes sensing session request information.

[0296] Aspect 31: According to the method of aspect 30, wherein the sensing session information includes an indication of a plurality of candidate sensing configurations, the method further includes selecting the sensing configuration from the plurality of candidate sensing configurations based on the sensing session request information.

[0297] Aspect 32: According to the method of aspect 24, the second network node includes sensing service management functionality.

[0298] Aspect 33: A method for wireless communication by a first network node, the method comprising: receiving from a second network node a first handover request associated with a handover operation of switching a user equipment (UE) from a source cell provided by the second network node to a target cell provided by a third network node, wherein the UE is associated with a sensing session; and sending a handover command associated with the handover operation to the second network node in connection with the handover request.

[0299] Aspect 34: According to the method of aspect 33, wherein the switching request indicates sensing session request information associated with the sensing session.

[0300] Aspect 35: According to the method of aspect 34, the method further includes selecting the third network node as the target network node from a plurality of candidate network nodes in association with the sensing session request information.

[0301] Aspect 36: The method according to any one of aspects 33 to 35, the method further comprising: sending a sensing configuration request associated with the sensing session to a fourth network node; and receiving a sensing configuration response from the fourth network node in association with the sensing configuration request, indicating sensing session information associated with the sensing session; and sending a second handover request associated with the handover operation to the third network node, the second handover request including the sensing session information.

[0302] Aspect 37: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 4.

[0303] Aspect 38: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 4.

[0304] Aspect 39: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 4.

[0305] Aspect 40: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 4.

[0306] Aspect 41: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 4.

[0307] Aspect 42: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 4.

[0308] Aspect 43: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 4.

[0309] Aspect 44: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 5 to 10.

[0310] Aspect 45: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 5 to 10.

[0311] Aspect 46: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 5 to 10.

[0312] Aspect 47: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 5 to 10.

[0313] Aspect 48: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 5 to 10.

[0314] Aspect 49: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 5 to 10.

[0315] Aspect 50: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 5 to 10.

[0316] Aspect 51: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 11 to 23.

[0317] Aspect 52: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 11 to 23.

[0318] Aspect 53: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 11 to 23.

[0319] Aspect 54: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 11 to 23.

[0320] Aspect 55: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 11 to 23.

[0321] Aspect 56: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 11 to 23.

[0322] Aspect 57: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 11 to 23.

[0323] Aspect 58: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform one or more of the methods according to aspects 24 to 32.

[0324] Aspect 59: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 24 to 32.

[0325] Aspect 60: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 24 to 32.

[0326] Aspect 61: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 24 to 32.

[0327] Aspect 62: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 24 to 32.

[0328] Aspect 63: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 24 to 32.

[0329] Aspect 64: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 24 to 32.

[0330] Aspect 65: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 33 to 36.

[0331] Aspect 66: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 33 to 36.

[0332] Aspect 67: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 33 to 36.

[0333] Aspect 68: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 33 to 36.

[0334] Aspect 69: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 33 to 36.

[0335] Aspect 70: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 33 to 36.

[0336] Aspect 71: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 33 to 36.

[0337] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0338] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0339] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0340] As used in this article, the phrase “at least one of the items” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0341] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0342] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the UE to: Receive first sensing configuration information associated with a source cell, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session; Perform one or more sensing measurements according to the first sensing configuration; Receive a handover command associated with a handover operation to switch the UE from the source cell to the target cell, the handover command including second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session associated with the target cell; The switching operation is performed in association with the switching command; and Perform one or more additional sensing measurements according to the second sensing configuration.

2. The UE of claim 1, wherein the processing system is further configured to cause the UE to: Obtain one or more channel measurements associated with at least one of the source cell or the target cell; and Sending mobility measurement information indicating the one or more channel measurements to a first network node providing the source cell, wherein receiving the handover command includes receiving the handover command in association with the mobility measurement information.

3. The UE of claim 1, wherein the first sensing configuration information indicates a sensing session identifier (ID) associated with the sensing session, and wherein the second sensing configuration information indicates the sensing session ID.

4. A first network node for wireless communication, the first network node comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, is configured to cause the first network node to: Send to the user equipment (UE) first sensing configuration information associated with the source cell provided by the first network node, wherein the first sensing configuration information indicates a first sensing configuration for a sensing session; The UE receives mobility measurement information associated with at least one of the source cell or the target cell; as well as Send a switching request to the second network node, indicating the sensing session request information associated with the sensing session.

5. The first network node according to claim 4, wherein the second network node includes a radio access network (RAN) node providing the target cell.

6. The first network node of claim 4, wherein the second network node includes a mobility service node that tracks mobility information associated with the UE.

7. The first network node of claim 4, wherein the sensing session request information indicates at least one of the following: a target cell identifier (ID) associated with the target cell, a sensing session ID associated with the sensing session, an additional sensing session ID associated with an additional sensing session, a UE ID associated with the UE, or an active service associated with the UE.

8. The first network node of claim 4, wherein the processing system is further configured to cause the first network node to: Receive from the second network node a handover command associated with the handover operation of switching the UE from the source cell to the target cell; and The handover command is sent to the UE.

9. The first network node of claim 8, wherein the handover command includes second sensing configuration information associated with the target cell, wherein the second sensing configuration information indicates a second sensing configuration for continuing the sensing session in association with the target cell.

10. A first network node for wireless communication, the first network node comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, is configured to cause the first network node to: Receive a handover request from the second network node associated with a handover operation to switch the user equipment (UE) from the source cell to the target cell provided by the first network node; Receive sensing session information associated with a sensing session, wherein the sensing session is associated with the UE; as well as The switching operation is performed according to the switching request.

11. The first network node of claim 10, wherein the second network node includes a radio access network (RAN) node providing the source cell.

12. The first network node of claim 10, wherein the processing system is further configured to cause the first network node to send a switching indication to the third network node including sensing session request information associated with the sensing session, wherein receiving the sensing session information includes receiving the sensing session information in association with the sensing session request information.

13. The first network node of claim 12, wherein the sensing session request information indicates at least one set of sensing configuration parameters supported by the first network node, and wherein the sensing session information indicates at least one set of parameter values ​​corresponding to the at least one set of sensing configuration parameters.

14. The first network node of claim 13, wherein the at least one set of sensing configuration parameters comprises a plurality of sets of sensing configuration parameters, wherein each of the plurality of sets of sensing configuration parameters is associated with a corresponding transmit / receive point (TRP) of the first network node.

15. The first network node of claim 14, wherein the processing system is further configured to cause the first network node to send sensing configuration response information to the third network node and in association with receiving the sensing session information.

16. The first network node of claim 15, wherein the sensing session information indicates a plurality of sensing sessions including the sensing session, and wherein the sensing configuration response information indicates at least one selected sensing session among the plurality of sensing sessions, the at least one selected sensing session including the sensing session.

17. The first network node of claim 12, wherein the third network node includes a sensing service management function.

18. The first network node of claim 12, wherein the switching request indicates the sensing session request information.

19. The first network node of claim 12, wherein the sensing session request information indicates at least one of the following: a target cell ID associated with the target cell, a sensing session ID associated with the sensing session, an additional sensing session ID associated with an additional sensing session, a UE ID associated with the UE, or an active service associated with the UE.

20. The first network node of claim 10, wherein the second network node includes a mobility service node that tracks mobility information associated with the UE, and wherein the handover request includes the sensing session information.

21. The first network node of claim 20, wherein the processing system is further configured to cause the first network node to: Receive instructions for multiple candidate sensing configurations from the network operator's service management entity; and A switching indication is sent to a third network node, including sensing session request information associated with the sensing session, wherein the sensing session information indicates the selected sensing configuration among the plurality of candidate sensing configurations.

22. The first network node of claim 10, wherein the sensing session information includes sensing configuration information associated with the target cell, wherein the sensing configuration information indicates a sensing configuration for continuing the sensing session in association with the target cell.

23. A first network node for wireless communication, the first network node comprising: A processing system, comprising one or more processors and one or more memories coupled to the one or more processors, is configured to cause the first network node to: Receive a sensing configuration request associated with a sensing session from a second network node, wherein the sensing session is associated with a user equipment (UE); as well as A sensing configuration response, indicating sensing session information associated with the sensing session, is sent to the second network node in association with the sensing configuration request.

24. The first network node of claim 23, wherein the second network node includes a radio access network (RAN) node that provides a target cell associated with the handover operation to hand over the UE from the source cell to the target cell.

25. The first network node of claim 24, wherein the sensing configuration request includes a handover indication, the handover indication including sensing session request information associated with the sensing session, and wherein the sensing configuration response includes sensing session information associated with the sensing session request information.

26. The first network node of claim 25, wherein the sensing session request information indicates at least one set of sensing configuration parameters supported by the second network node, and wherein the sensing session information indicates at least one set of parameter values ​​corresponding to the at least one set of sensing configuration parameters.

27. The first network node of claim 26, wherein the at least one set of sensing configuration parameters comprises a plurality of sets of sensing configuration parameters, wherein each of the plurality of sets of sensing configuration parameters is associated with a corresponding transmit / receive point (TRP) of the second network node.

28. The first network node of claim 27, wherein the sensing session request information indicates at least one of the following: a target cell identifier (ID) associated with the target cell, a sensing session ID associated with the sensing session, an additional sensing session ID associated with an additional sensing session, a UE ID associated with the UE, or an active service associated with the UE.

29. The first network node of claim 23, wherein the second network node includes a mobility service node that tracks mobility information associated with the UE, and wherein the sensing configuration request includes a handover request, the handover request including sensing session request information.

30. The first network node of claim 29, wherein the sensing session information includes indications of a plurality of candidate sensing configurations, and the method further includes selecting the sensing configuration from the plurality of candidate sensing configurations based on the sensing session request information.

Images