Method and apparatus for integrated sensing and communication
ISAC systems integrate sensing and communication functions within 5G networks by establishing connections and tunnels for efficient data exchange, enhancing spectrum efficiency and reliability in wireless communication systems.
Patent Information
- Application Number
- PCT/CN2026/073640
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2026-01-20
- Publication Date
- 2026-11-19
AI Technical Summary
Current wireless communication systems primarily focus on data transmission and lack efficient integration of sensing and communication functions, leading to suboptimal spectrum efficiency, latency, and reliability in applications requiring both.
The integration of sensing and communication (ISAC) capabilities within 5G, B5G, or 6G systems, enabling RAN nodes, core networks, and user equipment to establish connections and tunnels for simultaneous sensing and communication through protocols like SCTP and UP tunnels, using protocols such as SCTP and UP tunnels to facilitate the exchange of sensing data.
Enhances spectrum efficiency, reduces latency, and improves reliability by integrating sensing and communication functions, supporting various sensing modes and enabling high-quality wireless connectivity for applications like smart industries and vehicular networks.
Smart Images

Figure CN2026073640_19112026_PF_FP_ABST
Abstract
Description
METHOD AND APPARATUS FOR INTEGRATED SENSING AND COMMUNICATIONTECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to wireless communication technology, and more particularly to integrated sensing and communication (ISAC) .BACKGROUND
[0002] A wireless communication system may include one or multiple network communication devices, such as radio access network (RAN) nodes (e.g., base stations (BSs) ) , which may support wireless communication for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology. The wireless communication system may support wireless communication with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like) ) . Additionally, the wireless communication system may support wireless communication across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) (which is also known as new radio (NR) or next generation (NG) ) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .
[0003] Current wireless communication system design focuses primarily on data transmission. ISAC involves the simultaneous use of radio frequency (RF) signals for both sensing and communication purposes. This integration can lead to improved spectrum efficiency, reduced latency, and enhanced reliability in various applications. 3GPP TS 22.137 V19.1.0 specifies service requirements for ISAC. "5G-Advanced communication and sensing network architecture research report" published by IMT-2020 (5G) promotion group in 2022 provides a systematic study of ISAC technologies.SUMMARY
[0004] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ” Further, as used herein, including in the claims, a “set” , a “group” or a “list” may include one or more elements.
[0005] Some embodiments of the present disclosure provide a RAN node. The RAN node may include at least one memory; and at least one processor coupled with the at least one memory and configured to cause the RAN node to: receive, from a network function for access and mobility management of a core network (CN) node, first information for establishing a connection with a sensing function (SF) of the CN node, wherein the first information includes at least one of an identifier (ID) of the SF, a transport network layer (TNL) address of the SF or a first internet protocol (IP) address of the SF; establish a stream control transmission protocol (SCTP) association and a control plane (CP) connection with the SF based on the first information; and transmit sensing data to the SF via a user plane (UP) tunnel between the RAN node and the SF or the CP connection.
[0006] In some embodiments, the at least one processor is configured to cause the RAN node to establish the SCTP association and the CP connection with the SF in response to a receipt of the first information or an indication to initiate the establishment from the network function.
[0007] In some embodiments, to establish the CP connection with the SF, the at least one processor is configured to cause the RAN node to: transmit a connection setup request message to the SF, wherein the connection setup request message indicates at least one of a global RAN node ID of the RAN node, a first sensing area supported by the RAN node, or capability information of the RAN node.
[0008] In some embodiments, the capability information of the RAN node indicates that the RAN node supports sensing functionality only or both sensing functionality and communication functionality.
[0009] In some embodiments, to establish the CP connection with the SF, the at least one processor is configured to cause the RAN node to: receive a connection setup response message from the SF, wherein the connection setup response message indicates at least one of the ID of the SF, a name of the SF, or a second sensing area served by the SF.
[0010] In some embodiments, the CP connection is an NG connection and the at least one processor is configured to cause the RAN node to ignore inapplicable information elements in the connection setup response message.
[0011] In some embodiments, the at least one processor is configured to cause the RAN node to receive, from a UE, UE capability information indicating that the UE supports at least one of sensing functionality, communication functionality, sensing data processing, or a level of the sensing data processing.
[0012] In some embodiments, the at least one processor is configured to cause the RAN node to transmit the UE capability information to the network function or the SF.
[0013] In some embodiments, the at least one processor is configured to cause the RAN node to: receive, from the SF via the CP connection, at least one of a second IP address or a tunnel endpoint identifier (TEID) of the SF; and establish the UP tunnel based on the at least one of the second IP address or the TEID, wherein the UP tunnel is established per RAN node or per sensing task.
[0014] In some embodiments, the at least one processor is configured to cause the RAN node to: transmit, to the network function or a session management function (SMF) , a session establishment request for establishing a session terminated at the RAN node; receive, from the network function or the SMF, information related to a user plane function (UPF) and quality of service (QoS) rules for the session; and establish the UP tunnel over the session via the UPF.
[0015] In some embodiments, the sensing data is received from a UE via at least one of: a signal radio bearer (SRB) for sensing data reporting; a first data protocol data unit (PDU) of a sensing layer; a second data PDU of a service data adaptation protocol (SDAP) layer; or a third data PDU of a packet data convergence protocol (PDCP) layer.
[0016] In some embodiments, the at least one processor is configured to cause the RAN node to: process the sensing data received from a UE or sensed by the RAN node; and transmit the processed sensing data to the SF via the UP tunnel or the CP connection.
[0017] In some embodiments, a header of the first data PDU indicates at least one of a coded format of the sensing data or an ID of the sensing task associated with the sensing data. In some embodiments, a header of the second data PDU or third data PDU indicates at least one of a sensing data reporting indication or the coded format of the sensing data. In some embodiments, the at least one processor is configured to cause the RAN node to receive the coded format of the sensing data from the network function.
[0018] In some embodiments, the sensing data is received from a UE via a data radio bearer (DRB) for sensing data reporting, via a logical channel (LCH) for sensing data reporting, or via an uplink (UL) packet associated with a quality of service (QoS) flow identifier for sensing data reporting.
[0019] In some embodiments, the sensing data is received from a UE. In some embodiments, a header of an uplink (UL) sensing data packet, transmitted via the UP tunnel, indicates an ID of the UE. In some embodiments, the at least one of the second IP address or the TEID is configured for each UE or each sensing task.
[0020] Some embodiments of the present disclosure provide a CN. The CN may include at least one memory; and at least one processor coupled with the at least one memory and configured to cause the CN to: transmit, from a network function for access and mobility management of the CN to a RAN node, first information for establishing a connection between an SF of the CN and the RAN node, wherein the first information includes at least one of an ID of the SF, a TNL address of the SF or a first IP address of the SF; establish, at the SF, an SCTP association and a CP connection with the RAN node; and receive, at the SF, sensing data from the RAN node via a UP tunnel between the RAN node and the SF or the CP connection.
[0021] In some embodiments, to establish the CP connection with the RAN node, the at least one processor is configured to cause the SF of the CN to: receive a connection setup request message from the RAN node, wherein the connection setup request message indicates at least one of a global RAN node ID of the RAN node, a first sensing area supported by the RAN node, or capability information of the RAN node.
[0022] In some embodiments, the capability information of the RAN node indicates that the RAN node supports sensing functionality only or both sensing functionality and communication functionality.
[0023] In some embodiments, the capability information of the RAN node indicates that the RAN node supports sensing functionality only and the CP connection is an NG connection, and the at least one processor is configured to cause the SF of the CN to ignore inapplicable information elements in the connection setup request message.
[0024] In some embodiments, to establish the CP connection with the RAN node, the at least one processor is configured to cause the SF of the CN to: transmit a connection setup response message to the RAN node, wherein the connection setup response message indicates at least one of the ID of the SF, a name of the SF, or a second sensing area served by the SF.
[0025] In some embodiments, the at least one processor is configured to cause the SF of the CN to receive, from a UE served by the RAN node, UE capability information indicating that the UE supports at least one of sensing functionality, communication functionality, sensing data processing or a level of the sensing data processing. In some embodiments, the UE capability information is received from the UE via the RAN node or via a UL non-access stratum (NAS) message.
[0026] In some embodiments, the at least one processor is configured to cause the SF of the CN to: transmit, to the RAN node via the CP connection, at least one of a second IP address or a TEID of the SF; and establish the UP tunnel with the RAN node based on the at least one of the second IP address or the TEID, wherein the UP tunnel is established per RAN node or per sensing task.
[0027] In some embodiments, the sensing data is received from a UE served by the RAN node. In some embodiments, a header of a UL sensing data packet, received via the UP tunnel, indicates an ID of the UE. In some embodiments, the at least one of the second IP address or the TEID is configured for each UE or each sensing task.
[0028] In some embodiments, the UP tunnel is established via a UPF for a session terminated at the RAN node.
[0029] Some embodiments of the present disclosure provide a UE. The UE may include at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive a sensing command, from a RAN node serving the UE or an SF, to perform a measurement for a sensing task; and transmit sensing data associated with the sensing task to the SF via a UP tunnel between the RAN node and the SF.
[0030] In some embodiments, the at least one processor is configured to cause the UE to transmit, to the RAN node or to the SF via the RAN node or via a UL NAS message, UE capability information indicating that the UE supports at least one of sensing functionality, communication functionality, sensing data processing or a level of the sensing data processing.
[0031] In some embodiments, the at least one processor is configured to cause the UE to transmit the sensing data to the RAN node via at least one of: an SRB for sensing data reporting; a first data PDU of a sensing layer; a second data PDU of an SDAP layer; or a third data PDU of a PDCP layer.
[0032] In some embodiments, the priority of the SRB is configured for the UE by the RAN node or is predefined. In some embodiments, a header of the first data PDU indicates at least one of a coded format of the sensing data or an ID of the sensing task, and the at least one processor is configured to cause the UE to receive a mapping relation between the ID of the sensing task and a QoS flow identifier (QFI) associated with the sensing task. In some embodiments, a header of the second data PDU or third data PDU indicates at least one of a sensing data reporting indication or the coded format of the sensing data.
[0033] In some embodiments, the at least one processor is configured to cause the UE to transmit the sensing data to the RAN node via a DRB for sensing data reporting, via an LCH for sensing data reporting, or via a UL packet associated with a QFI for sensing data reporting.
[0034] Some embodiments of the present disclosure provide a processor. The processor may include at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a network function for access and mobility management of a CN node, first information for establishing a connection with an SF of the CN node, wherein the first information includes at least one of an ID of the SF, a TNL address of the SF or a first IP address of the SF; establish an SCTP association and a CP connection with the SF based on the first information; and transmit sensing data to the SF via a UP tunnel between a RAN node and the SF or the CP connection.
[0035] Some embodiments of the present disclosure provide a processor. The processor may include at least one controller coupled with at least one memory and configured to cause the processor to: transmit, from a network function for access and mobility management of a CN to a RAN node, first information for establishing a connection between an SF of the CN and the RAN node, wherein the first information includes at least one of an ID of the SF, a TNL address of the SF or a first IP address of the SF; establish, at the SF, an SCTP association and a CP connection with the RAN node; and receive, at the SF, sensing data from the RAN node via a UP tunnel between the RAN node and the SF or the CP connection.
[0036] Some embodiments of the present disclosure provide a processor. The processor may include at least one controller coupled with at least one memory and configured to cause the processor to: receive a sensing command, from a RAN node serving a UE or an SF, to perform a measurement for a sensing task; and transmit sensing data associated with the sensing task to the SF via a UP tunnel between the RAN node and the SF.
[0037] Some embodiments of the present disclosure provide a method performed by a RAN node for wireless communication, the method including: receiving, from a network function for access and mobility management of a CN node, first information for establishing a connection with an SF of the CN node, wherein the first information includes at least one of an ID of the SF, a TNL address of the SF or a first IP address of the SF; establishing an SCTP association and a CP connection with the SF based on the first information; and transmitting sensing data to the SF via a UP tunnel between the RAN node and the SF or the CP connection.
[0038] Some embodiments of the present disclosure provide a method performed by a CN for wireless communication, the method including: transmitting, from a network function for access and mobility management of the CN to a RAN node, first information for establishing a connection between an SF of the CN and the RAN node, wherein the first information includes at least one of an ID of the SF, a TNL address of the SF or a first IP address of the SF; establishing, at the SF, an SCTP association and a CP connection with the RAN node; and receiving, at the SF, sensing data from the RAN node via a UP tunnel between the RAN node and the SF or the CP connection.
[0039] Some embodiments of the present disclosure provide a method performed by a UE for wireless communication, the method including: receive a sensing command, from a RAN node serving the UE or an SF, to perform a measurement for a sensing task; and transmit sensing data associated with the sensing task to the SF via a UP tunnel between the RAN node and the SF.
[0040] Some embodiments of the present disclosure provide an apparatus. According to some embodiments of the present disclosure, the apparatus may include: at least one non-transitory computer-readable medium having stored thereon computer-executable instructions; at least one receiving circuitry; at least one transmitting circuitry; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiving circuitry and the at least one transmitting circuitry, wherein the at least one non-transitory computer-readable medium and the computer executable instructions may be configured to, with the at least one processor, cause the apparatus to perform a method according to some embodiments of the present disclosure.BRIEF DESCRIPTION OF THE DRAWINGS
[0041] In order to describe the manner in which the advantages and features of the disclosure can be obtained, a description of the disclosure is rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. These drawings depict only exemplary embodiments of the disclosure and are not therefore to be considered limiting of its scope.
[0042] FIG. 1 illustrates a schematic diagram of a wireless communication system in accordance with some embodiments of the present disclosure;
[0043] FIG. 2 illustrates a schematic diagram of network structure supporting sensing functions in accordance with some embodiments of the present disclosure;
[0044] FIG. 3 illustrates an exemplary procedure for establishing a connection between a RAN node and an SF in accordance with some embodiments of the present disclosure;
[0045] FIGs. 4A and 4B illustrate example direct and indirect UP tunnels between a RAN node and an SF in accordance with some embodiments of the present disclosure;
[0046] FIG. 5 illustrates an exemplary procedure for reporting UE sensing data in accordance with some embodiments of the present disclosure;
[0047] FIG. 6A illustrates an example protocol stack for a UE and a RAN node in accordance with some embodiments of the present disclosure;
[0048] FIG. 6B illustrates an example sensing layer PDU in accordance with some embodiments of the present disclosure;
[0049] FIG. 6C illustrates an example SDAP PDU in accordance with some embodiments of the present disclosure;
[0050] FIGs. 7-9 illustrate flowcharts of wireless communication methods in accordance with some embodiments of the present disclosure;
[0051] FIG. 10 illustrates an example of an apparatus in accordance with some embodiments of the present disclosure; and
[0052] FIG. 11 illustrates an example of a processor in accordance with some embodiments of the present disclosure.DETAILED DESCRIPTION
[0053] The detailed description of the appended drawings is intended as a description of the preferred embodiments of the present disclosure and is not intended to represent the only form in which the present disclosure may be practiced. It should be understood that the same or equivalent functions may be accomplished by different embodiments that are intended to be encompassed within the spirit and scope of the present disclosure.
[0054] Reference will now be made in detail to some embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under a specific network architecture (s) and new service scenarios, such as the 3rd generation partnership project (3GPP) 5G NR or 6G, 3GPP LTE, and so on. It is contemplated that along with the development of network architectures and new service scenarios, all embodiments in the present disclosure are also applicable to similar technical problems; and moreover, the terminologies recited in the present disclosure may change, which should not affect the principles of the present disclosure.
[0055] Wireless sensing technologies enable the acquisition of information about characteristics of the environment and / or objects within the environment without physical contact. These technologies utilize perception data of the object, allowing for analysis and obtaining meaningful information about the object and its characteristics. An example of wireless sensing technologies is radar, which uses radio waves to determine various aspects of objects, such as distance (range) , angle or instantaneous linear velocity. Another example of wireless sensing technologies is non-radio frequency (RF) sensors, which have been supported in applications in different fields. Examples of such sensors are time-of-flight (ToF) cameras, accelerometers, gyroscopes and LiDARs.
[0056] Integrated sensing and communication (ISAC) may refer to the provision of sensing capabilities within the same wireless communication system and infrastructure, such as 5G, beyond 5G (B5G) or 6G, that is used for communication purposes. For many emerging applications, such as smart industries, next-generation vehicular networks and remote health-caring, high-quality wireless connectivity and high-accuracy sensing capability are required. Therefore, it is desirable to introduce ISAC into wireless communication systems, such as 5G, B5G or 6G systems.
[0057] ISAC provides communication as well as sensing functions (e.g., location and environment-aware functions) . In some embodiments, both a UE and a RAN node (e.g., a BS) may serve as a sensing entity to perform a sensing task. In some embodiments, ISAC may support the following different sensing modes: (1) RAN node-based monostatic sensing; (2) RAN node-based bistatic sensing; (3) UE-RAN node bistatic sensing, where the UE transmits and the RAN node receives; (4) UE-RAN node bistatic sensing, where the BS transmits and the UE receives; (5) UE based monostatic sensing; and (6) UE based bistatic sensing.
[0058] Monostatic sensing refers to the case where the sensing transmitter and sensing receiver are co-located in the same entity. Bistatic sensing refers to the case where the sensing receiver and sensing transmitter are in different entities. In some embodiments, multistatic sensing with multiple sensing transmitters and receivers is also supported. In some embodiments, a sensing entity (e.g., UE or RAN node) may support more than one sensing mode, for example, a RAN node may support both monostatic sensing and bistatic sensing.
[0059] A sensing receiver refers to an entity that receives the sensing signal which the sensing service will use in its operation. A sensing receiver can be a part of a RAN node or a UE. A sensing receiver can be located in the same or different entity as the sensing transmitter. A sensing transmitter refers to the entity that transmits the sensing signal which the sensing service will use in its operation. A sensing transmitter can be a part of a RAN node or a UE. A sensing transmitter can be located in the same or different entity as the sensing receiver. A sensing signal can refer to a transmission on a 3GPP radio interface or a non-3GPP signal that can be used for sensing purposes. A sensing entity can be either a sensing transmitter or a sensing receiver, or both. For example, the sensing receiver may receive the reflections of the sensing signal sent from the sensing transmitter and process the received sensing signal to obtain characteristics of the sensed object and its environment (e.g., location) . For example, in mode (1) , the same BS transmits and receives the sensing signal. For example, in mode (2) , a BS (also called a transmit (Tx) sensing BS) transmits a sensing signal while a different BS (also called a receive (Rx) sensing BS) receives the sensing signal. RAN node-based sensing may refer to either mode (1) or mode (2) . Similarly, UE-based sensing may refer to either mode (5) or mode (6) .
[0060] The present disclosure provides solutions for addressing various issues in an ISAC system. For example, solutions are provided for establishing a connection between a RAN node and an SF. Solutions are provided for establishing a UP tunnel between a RAN node and an SF. Solutions are provided for reporting BS sensing data and UE sensing data.
[0061] FIG. 1 illustrates a schematic diagram of wireless communication system 100 in accordance with some embodiments of the present disclosure.
[0062] The wireless communication system 100 may include one or more network elements (NEs) 102 (e.g., one or more RAN nodes such as BSs) , one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 3G network, such as a universal terrestrial radio access-frequency division duplex (UTRA-FDD) network. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network, an LTE-Advanced (LTE-A) network, a terrestrial radio access-frequency division duplex (TRA-FDD) network or an evolved universal terrestrial radio access (E-UTRA) network. In some other implementations, the wireless communication system 100 may be an NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultra-wideband (5G-UWB) network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communication system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
[0063] The one or more NEs 102 may be dispersed throughout a geographic region to form the wireless communication system 100. One or more of the NEs 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN) node, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. In some implementations, the one or more NEs 102 may include different types of BSs (e.g., macro BS, pico BS, femto BS, relay BS, etc. ) . These different types of BSs may have different transmit power levels and different coverage areas. For example, a macro BS may have a relatively high transmit power level, while pico BSs, femto BSs, and relay BSs may have relatively low transmit power levels. In some embodiments of the present disclosure, an NE 102 may include a CU and one or more DUs. An F1 interface or the like (e.g., network interfaces beyond 5G) may be established between the DU of NE 102 and the CU of NE 102.
[0064] An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
[0065] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN) . In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with a different NE 102.
[0066] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communication system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples.
[0067] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
[0068] A relaying function based on a sidelink may be supported in the wireless communication system 100. For example, a UE 104 supporting sidelink communication may function as a relay node to extend the coverage of an NE 102 (e.g., a BS) . An out-of-coverage or in-coverage UE may communicate with a BS via a relay node (e.g., a relay UE) . In some implementations, a UE, which functions as a relay between another UE and a BS, may be referred to as a UE-to-network (U2N) relay.
[0069] An NE 102 may support communication with the CN 106, or with another NE 102 or both. For example, an NE 102 may interface with another NE 102 or the CN 106 through one or more backhaul links (e.g., S1, X2, NG, Xn or another network interfaces) . In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other indirectly (e.g., via the CN 106) . In some implementations, one or more NEs 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads, or transmission-reception points (TRPs) .
[0070] In some implementations, an NE 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more NEs 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, an NE 102 may include one or more of a centralized unit (CU) , a distributed unit (DU) , a radio unit (RU) (e.g., a TRP) , a RAN intelligent controller (RIC) (e.g., a near-real time RIC (Near-RT RIC) , a non-real time RIC (Non-RT RIC) ) , a service management and orchestration (SMO) system, or any combination thereof. One or more components of the NEs 102 in a disaggregated RAN architecture may be co-located, or one or more components of the NEs 102 may be located in distributed locations (e.g., separate physical locations) . In some implementations, one or more NEs 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) or a virtual DU (VDU) ) .
[0071] Split of functionality between a CU and a DU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU or a DU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host higher protocol layers (e.g., L3 (e.g., radio resource control (RRC) layer) and parts of L2 (e.g., service data adaption protocol (SDAP) layer and packet data convergence protocol (PDCP) layer) functionality and signaling. The CU may be connected to one or more DUs, which may host lower protocol layers (e.g., L1 (e.g., physical (PHY) layer) and parts of L2 (e.g., radio link control (RLC) layer and medium access control (MAC) layer) ) functionality and signaling, and be at least partially controlled by the CU. A DU may support one or multiple different cells. A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
[0072] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC) , a 5G core (5GC) , or a 6G core (6GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) function or a mobility management function in future generations such as 6G) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and QoS flow and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more NEs 102 associated with the CN 106. In some implementations, the CN may include a location management function (LMF) or a sensing function (SF) . The SF may be located in a CN node such as the LMF or the AMF or may be an independent network node in the CN. Both the SF and the LMF may be in communication with the mobility management function. In some implementations, the SF may be a part of the NE 102.
[0073] In some implementations, a network function for access and mobility management of the CN, e.g., the AMF, or the mobility management function in future generations may include the following functionality: registration management; connection management; reachability management; mobility management; and UE mobility event notification. Some or all of the AMF functionalities may be supported in a single instance of an AMF.
[0074] In some implementations, the NE 102 (e.g., a RAN node) may host the following functions. Some or all of the functionalities / services may be supported in a single NE. -Functions for Radio Resource Management: Radio Bearer Control, Radio Admission Control, Connection Mobility Control, Dynamic allocation of resources to UEs in both uplink and downlink (scheduling) ; -IP and Ethernet header compression, uplink data decompression, encryption and integrity protection of data; -Connection setup and release; -Scheduling and transmission of paging messages; -Scheduling and transmission of system broadcast information (originated from the AMF or operation, administration and maintenance (OAM) ) ; and -Measurement and measurement reporting configuration for mobility and scheduling.
[0075] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an N6 or another network interface) . The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106) .
[0076] In the wireless communication system 100, the NEs 102 and the UEs 104 may use resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communication) . In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies such as 6G, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.
[0077] In some embodiments, the NEs 102 may include one or more relay nodes, integrated access and backhaul (IAB) nodes or wireless access backhaul (WAB) nodes which can provide wireless access services for UEs 104. A relay node (or an IAB node or a WAB node) can directly connect to a BS or hop through one or more relay nodes (or one or more IAB or WAB nodes) before reaching the BS.
[0078] One or more numerologies may be supported in the wireless communication system 100, and a numerology may include subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ =1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix. A sixth numerology (e.g., μ =5) may be associated with a sixth subcarrier spacing (e.g., 480 kHz) and a normal cyclic prefix. A seventh numerology (e.g., μ=6) may be associated with a seventh subcarrier spacing (e.g., 960 kHz) and a normal cyclic prefix. For ambient IoT communication, additional numerologies (e.g., μ=-1 or μ =-2) may be introduced corresponding to 7.5 kHz or 3.75 kHz, respectively.
[0079] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.
[0080] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communication system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings (SCSs) of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., orthogonal frequency-division multiplexing (OFDM) symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0081] In the wireless communication system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communication system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the NEs 102 and the UEs 104 may perform wireless communication over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communication traffic (e.g., control information, data) . In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
[0082] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ =0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ =1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least two numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.
[0083] A UE 104 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , vehicles or the like. According to some embodiments of the present disclosure, a UE 104 may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network. In some embodiments of the present disclosure, a UE 104 includes wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, a UE 104 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art. A UE 104 may communicate with an NE 102 (e.g., a BS) via uplink (UL) communication signals. An NE 102 may communicate with a UE 104 via downlink (DL) communication signals.
[0084] In some embodiments of the present disclosure, an NE 102 and a UE 104 may communicate over licensed spectrums, whereas in some other embodiments, an NE 102 and a UE 104 may communicate over unlicensed spectrums. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. Persons skilled in the art should understand that as technology develops and advances, the terminologies described in the present disclosure may change, but should not affect or limit the principles and spirit of the present disclosure. For example, although the terminologies used in the present disclosure (e.g., names of network functions, network nodes, and interfaces) may be described in the context of a specific telecommunication generation (e.g., 5G or 6G) , those skilled in the art will appreciate that equivalent terminologies corresponding to other generations or telecommunication technologies may be substituted without departing from the scope of the present disclosure.
[0085] Embodiments of the present disclosure provide solutions for implementing the sensing function and the sensing modes as described above. In some embodiments, a sensing related network function (referred to as an SF or by any other name) is introduced to enable sensing in a communication network. This sensing related network function is mainly responsible for sensing control and sensing data processing, and may be referred to as an SF or by any other name. For illustrative purposes in this disclosure, the term 'SF' is used and can be replaced by other equivalent terminology without departing from the scope of the present disclosure. In some embodiments, the SF is an independent network element or network function in the CN. In some embodiments, the SF is located in another network function (e.g., an AMF or a location management function (LMF) ) . In some embodiments, the SF can be split into a user plane function of the SF (referred to as SF-U) , control plane function of the SF (referred to as SF-C or SCF) and / or processing function of the SF (referred to as SF-P or SPF) . For example, embodiments of the present disclosure provide solutions for setting up a connection between a RAN node and an SF. For example, embodiments of the present disclosure provide solutions for establishing a UP tunnel between a RAN node and an SF. In some examples, this UP tunnel can be used for BS-based sensing. In some examples, this UP tunnel can be used for both BS-based sensing and UE-based sensing. For example, embodiments of the present disclosure provide solutions for reporting sensing data to the CN. More details on the embodiments of the present disclosure will be illustrated in the following text in combination with the appended drawings.
[0086] FIG. 2 illustrates a schematic diagram of network structure 200 supporting sensing functions in accordance with some embodiments of the present disclosure.
[0087] Referring to FIG. 2, in some cases (e.g., for RAN node-based sensing) , a RAN node may establish a connection (e.g., an NG connection in 5G or a newly defined connection in a future generation) with a network function for access and mobility management (e.g., the AMF in 5G or a new network function in a future generation) when it powers on. In some embodiments, the RAN node may further establish a connection (denoted as Nx connection for clarity) with the SF, if needed. For example, the RAN node may be integrated with the functionalities of communication and sensing, and may establish the connection with the SF for the sensing functionality. In some examples, Nx connection may reuse the connection between, for example, the RAN node and the network function for access and mobility management. In some examples, the Nx connection may be a new connection defined between the RAN node and the SF.
[0088] For illustrative purposes, the present disclosure may employ generation-specific terminology (e.g., NG, AMF) . Persons skilled in the art should understand that such terminology can be replaced by its functional equivalent defined in 6G or any subsequent generation. For example, the AMF can be replaced by a network function for access and mobility management. An NG interface (or connection) can be replaced by an interface (or connection) between a network function for access and mobility management and a RAN node, or between a network function for sensing and a RAN node.
[0089] FIG. 3 illustrates exemplary procedure 300 for establishing an Nx connection between a RAN node and an SF in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiment shown in FIG. 3.
[0090] In exemplary procedure 300, RAN node 302 can maintain an NG connection (e.g., a control plane (CP) connection NG-C) with AMF 306 and an Nx connection (e.g., a CP connection Nx-C) with SF 308 at the same time.
[0091] At 311, RAN node 302 may establish an SCTP association and an NG connection with AMF 306 when, for example, RAN node 302 powers on. For example, the establishment of the SCTP association and the NG connection may be based on a pre-configuration. The pre-configuration may include at least one TNL address of AMF 306.
[0092] RAN node 302 may establish the first TNL association (TNLA) with AMF 306 using the configured TNL address. RAN node 302 may use a different source and / or destination IP end point (s) if the TNL establishment towards one IP end point fails. RAN node 302 may obtain the remote IP end point (s) and its own IP address from an OAM configuration or a pre-configuration.
[0093] In response to the establishment of the TNLA, RAN node 302 may initiate an NG setup procedure with AMF 306. For example, RAN node 302 may transmit an NG setup request message to AMF 306, which may respond with an NG setup response message or an NG setup failure message to RAN node 302.
[0094] In some embodiments, at 315, RAN node 302 may establish an SCTP association and an Nx connection (e.g., a CP connection Nx-C) with SF 308.
[0095] In some embodiments, RAN node 302 may perform the establishment based on an OAM configuration or a pre-configuration. For example, an OAM entity may specify the SF (s) to which RAN node 302 can connect.
[0096] In some embodiments, a CN node (e.g., AMF 306) may indicate the SF (s) to which RAN node 302 can connect. For example, AMF 306 may transmit, to RAN node 302, information for establishing a connection with at least one SF. For each SF, the information may include at least one of an ID of the SF, a TNL address of the SF or an IP address (e.g., a CP IP address) of the SF. For example, the information may be transmitted in the NG setup response message. In some examples, the ID of the SF may not be indicated. In some examples, the TNL address or the IP address may be emphasized to be used (e.g., explicitly specified for use) for an SCTP association for an Nx connection with an SF. RAN node 302 may perform the SCTP association and Nx connection establishment with SF 308 based on the above information.
[0097] In some embodiments, the establishment of the SCTP association and Nx connection with SF 308 may be performed in response to receiving the information for establishing a connection with at least one SF (e.g., the TNL address or the IP address) . In some embodiments, the establishment of the SCTP association and Nx connection with SF 308 may be performed in response to an indication from the CN (e.g., AMF 306) . For example, the CN may select a proper SF; and based on the relationship between the SF and RAN nodes, AMF 306 transmit the indication to RAN node 302 via, for example, the NG setup response message.
[0098] For example, at 315, RAN node 302 may first establish the SCTP association with SF 308. Then, RAN node 302 may transmit a connection setup request message (e.g., an Nx setup request message) to SF 308, which may respond with a connection setup response message (e.g., an Nx setup response message) or a connection setup failure message (e.g., an Nx setup failure message) to RAN node 302. The Nx setup request message may include at least one of a global RAN node ID of RAN node 302 or a sensing area supported by RAN node 302. The Nx setup response message may include at least one of at least one of the ID of SF 308 (e.g., in "SF Identifier" IE) , the name of SF 308 (e.g., in "SF Name" IE) or a sensing area served by SF 308. In some embodiments, a sensing area may be indicated by a tracking area code (TAC) , a cell global identity (CGI) , a sensing zone ID or a sensing area ID. In some embodiments, the Nx connection may reuse the NG connection, and the Nx setup request message and the Nx setup response message can be replaced by the NG setup request message and the NG setup response message.
[0099] In some embodiments, RAN node 302 may ignore inapplicable information elements (IEs) in the Nx setup response message. For example, the Nx connection may reuse the NG connection; and the NG setup response message may include certain mandatory IEs (e.g., the AMF ID) for the NG setup, but these are not applicable to a connection setup between a RAN node and an SF.
[0100] In some embodiments, RAN node 302 may transmit sensing data (processed or raw) corresponding to a sensing task to the CN (e.g., AMF 306 or SF 308) . For example, RAN node 302 may transmit the sensing data to SF 308 via the Nx connection therebetween. For example, RAN node 302 may transmit the sensing data to SF 308 via a UP tunnel therebetween.
[0101] It should be appreciated by persons skilled in the art that the sequence of the operations in exemplary procedure 300 may be changed and that some of the operations in exemplary procedure 300 may be eliminated or modified, without departing from the spirit and scope of the disclosure.
[0102] In some embodiments, a RAN node can maintain only one of an NG connection (e.g., a CP connection NG-C) with an AMF and an Nx connection (e.g., a CP connection Nx-C) with an SF at the same time. For example, the RAN node can only set up an NG connection with either an AMF or an SF. The RAN node may transmit sensing data (processed or raw) corresponding to a sensing task to either the AMF or the SF. For example, the RAN node may transmit the sensing data to the SF via the NG connection therebetween. For example, the RAN node may transmit the sensing data to the SF via a UP tunnel therebetween.
[0103] In some examples, the RAN node may only set up an NG connection with the AMF, and can connect to the SF via the AMF (sub-scenario 1) . For example, a RAN node can support both communication functionalities with UEs and sensing functionalities. In this scenario, the RAN node needs to set up the NG connection with the AMF. In some examples, the RAN node may not set up an NG connection with the AMF, and may set up a direct NG connection with the SF (sub-scenario 2) . For example, a RAN node can support only sensing functionalities. In this scenario, the RAN node only needs to set up the direct connection with the SF.
[0104] The NG setup procedure between the RAN node and the SF may be similar to the Nx setup procedure described above with respect to operation 315 in FIG. 3. For example, the RAN node may initiate the NG setup procedure by transmitting an NG setup request message to the SF. The SF may respond with an NG setup response message including at least one of the ID of the SF or the name of the SF. The RAN node may ignore inapplicable IEs (e.g., an AMF ID) in the NG setup response message.
[0105] In some embodiments, during the connection setup procedure between the RAN node and either one of the SF and the AMF, the RAN node may transmit its capability information via, for example, an NG setup request message. For example, the NG setup request message may indicate whether the RAN node supports sensing functionalities only, or both sensing functionalities and communication functionalities.
[0106] For instance, a RAN node supporting sensing functionalities may trigger an NG setup procedure with either an AMF or an SF. The NG setup request message transmitted by the RAN node may include a "sensing Support" IE which can be set to "sensing only" (i.e., the RAN node supports sensing functionalities only) or "sensing and Uu" (i.e., the RAN node supports both sensing functionalities and communication functionalities) . For example, the SF may receive an NG setup request message indicating "sensing only" . The SF may consider that the RAN node only supports sensing radio, and may ignore inapplicable IEs (e.g., the "Supported TA List" IE) in the setup request message. For example, the AMF may receive an NG setup request message indicating "sensing and Uu" . The AMF may consider that the RAN node only supports both sensing radio and Uu radio.
[0107] In some embodiments, UE capability information (e.g., sensing capability) may be transmitted to the RAN node or the CN (e.g., the AMF or the SF) to facilitate sensing functionalities, such as the selection of a sensing entity (SE) . For example, the UE capability information may indicate that a UE supports at least one of a sensing functionality or communication functionality. For example, the UE capability IE may include a codepoint for sensing only, and / or a codepoint for sensing and communication. For example, the UE capability IE may include a codepoint for whether support sensing or not and / or a codepoint for whether support communication or not.
[0108] In some embodiments, the termination point (e.g., either a RAN node a CN) of the UE capability information may depend on which entity is responsible for selecting the UEs for a sensing task. For example, the CN may only select RAN nodes for a sensing task, and the selected RAN nodes may select UEs for the sensing task based on UE capability information. A UE may report its sensing capability to a RAN node via, for example, an RRC message. The RAN node may transmit its sensing capability to a sensing-related CN node (e.g., an AMF or an SF) . The sensing capability of a RAN node may take the UE capability information into account, for example, by merging the UE sensing capability with the sensing capability of the RAN node itself. The CN node may select the sensing RAN node. Selection of a UE for sensing, for example, whether to select and which UE (s) to select, may depend on the implementation of the selected RAN node. For example, the CN may select UEs for a sensing task. A UE may report its sensing capability to the sensing-related CN node (e.g., the AMF or the SF) via a RAN node, which may only forward the report to the CN node without decoding it. Alternatively, the UE sensing capability is transparent to the RAN node. For example, a UE may report its sensing capability to the CN node (e.g., the AMF or the SF) via a UL NAS message. In this case, the CN node can directly determine the sensing UE for performing the sensing task.
[0109] In some embodiments, a UP tunnel may be established between a RAN node and an SF for RAN node-based sensing. However, this UP tunnel may not be necessarily dedicated to only RAN node-based sensing, and may be used for other sensing modes, such as UE-based sensing. The UP tunnel between a RAN node and an SF may be a direct UP tunnel (e.g., established without any intermediate node) or an indirect UP tunnel (e.g., established via another CN node) .
[0110] FIG. 4A illustrates an example direct UP tunnel protocol stack 400A between a RAN node and an SF in accordance with some embodiments of the present disclosure. Referring to FIG. 4A, protocol stack 400A comprises, but is not limited to, layer 1 (i.e., L1 i.e., a physical layer) , layer 2 (L2) , an IP layer, a UDP layer, a general packet radio service (GPRS) tunnelling protocol (GTP) for a user plane (GTP-U) layer and a sensing layer (which may be referred to as a sensing data layer) . According to protocol stack 400A, the sensing data PDU generated by the sensing layer of the RAN node can be transmitted to the SF via the direct UP tunnel (i.e., GTP-U tunnel in FIG. 4A) therebetween. As will be described later, this direct UP tunnel can be used not only for RAN node-based sensing (e.g., for transmitting the sensing data sensed by the RAN node) but also for UE-based sensing. In some other examples, there is no sensing layer or sensing data layer for the UP tunnel protocol, and the sensing data PDU is generated by the implementation of the RAN node and transmitted to the SF via the direct UP tunnel therebetween.
[0111] In some examples, the direct UP tunnel between the RAN node and the SF may be a unidirectional tunnel from the RAN node to the SF for sensing data reporting. In some examples, the tunnel may be a non-UE-associated GTP-U based tunnel, and in this case, it cannot be used for UE-based sensing. In some examples, the tunnel may have a granularity of per RAN node or per sensing task. For example, one tunnel (e.g., the same TEID / IP) is shared by all sensing traffic originating from the same RAN node, regardless of how many distinct sensing tasks are running. For example, a separate tunnel (e.g., different TEID / IP) is established for each individual sensing task.
[0112] In some embodiments, the direct UP tunnel may be established based on the Nx or NG connection between the RAN node and the SF. For example, the RAN node or the SF may trigger a tunnel establishment procedure (e.g., a sensing tunnel setup procedure) via the Nx application protocol (NxAP) or NGAP. For example, the RAN node may receive at least one of the following information from the SF via the NxAP or NGAP: an IP address (e.g., a UP IP address) of the SF or a TEID of the SF. In some embodiments, the SF-C, SMF or AMF or other network function of the CN may select the proper SF-U (or SF-P) , and indicate the IP address and / or TEID of the SF-U (SF-P) to the RAN node via the NxAP or NGAP. The RAN node may establish the UP tunnel with the SF based on the received information. In some examples, the IP address or the TEID may be associated with a sensing task ID or per sensing task tunnel. In this way, the tunnel can be established with per sensing task granularity.
[0113] Compared to the indirect UP tunnel as described below, the direct UP tunnel can bypass the UPF, thereby achieving low latency and high transmission efficiency.
[0114] FIG. 4B illustrates an example indirect UP tunnel protocol stack 400B between a RAN node and an SF in accordance with some embodiments of the present disclosure. The indirect UP tunnel between the RAN node and the SF is established via a UPF. Referring to FIG. 4B, a GTP-U tunnel is established between the RAN node and the UPF, which can route sensing data from the RAN node to the SF, or vice versa. This indirect UP tunnel may only be used for RAN node-based sensing, not for UE-based sensing.
[0115] In some examples, the indirect UP tunnel between the RAN node and the SF may be unidirectional from the RAN node to the SF for sensing data reporting. In some examples, the GTP-U tunnel between the RAN node and the UPF is not for a specific UE PDU session (e.g., terminated at the UE) , but for a session for non-UE traffic (e.g., terminated at the RAN node) .
[0116] For example, the RAN node may trigger at least one session establishment specific for sensing to the CN (e.g., the AMF or SMF in the CN) . For example, the RAN node may transmit, to the AMF or the SMF, a session establishment request for establishing a session terminated at the RAN node. Then, the CN (e.g., the AMF or SMF) may establish a session (e.g., a PDU session, a sensing session or a session with a different name) for the RAN node, and transmit the corresponding configuration to the RAN node. For example, the RAN node may receive, from the AMF or the SMF, information related to at least one of the anchor UPF or QoS rules for the session. The RAN node may establish the UP tunnel between the RAN node and the SF over the session via the UPF. Alternatively, this session establishment may be triggered by the CN node.
[0117] FIG. 5 illustrates exemplary procedure 500 for reporting UE sensing data in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiments shown in FIG. 5.
[0118] Referring to FIG. 5, UE 504 may perform a sensing task and obtain sensing data (also referred to as sensing measurement data) corresponding to the sensing task. UE 504 may or may not process the sensing data. In the case that UE 504 has the sensing data processing capability, the sensing data report includes the processing sensing data; otherwise, the sensing data report includes the raw sensing data. For example, UE 504 may report the sensing data to SF 508. In some embodiments, UE 504 may report the sensing data to other CN nodes.
[0119] In some embodiments, UE 504 may access RAN node 502. That is, RAN node 502 is the serving RAN node of UE 504. A PDU session may be established between (e.g., terminated at) UE 504 and a UPF (not shown in FIG. 5) . For example, UE 504 may perform a PDU session establishment procedure with the UPF based on the air interface between UE 504 and RAN node 502. UE 504 may transmit the sensing data to the UPF via the PDU session. RAN node 502 transparently forwards the sensing data without inspecting or decoding it. The UPF may route the sensing date to SF 508.
[0120] In some embodiments, the UP tunnel between RAN node 502 and SF 508 may be used for transmitting the UE sensing data. For example, as described above, a direct UP tunnel may be established between a RAN node and an SF (e.g., RAN node 502 and SF 508) . The sensing data reporting may be implemented based on this direct UP tunnel. This is beneficial because using the direct UP tunnel between the RAN node and the SF for reporting UE sensing data reduces latency due to fewer hops in the entire routing path. In addition, RAN node 502 can process the sensing data from UE 504, and then report the processed sensing data to SF 508.
[0121] For example, at 511, UE 504 may transmit the sensing data to RAN node 502 via the Uu interface therebetween. Then, at 515, RAN node 502 may transmit the sensing data to SF 508 via the UP tunnel (e.g., the direct UP tunnel) therebetween. RAN node 502 may or may not process the sensing data from UE 504. In the case that RAN node 502 processes the received sensing data (e.g., at 513 (denoted by a dotted block as an option) ) , the sensing data report to SF 508 includes the processing sensing data. Otherwise, the sensing data report includes the sensing data received from UE 504. Processing sensing data at a RAN node can alleviate the data volume of sensing reporting, considering that the UE may not have enough capability to handle massive amounts of data.
[0122] In some embodiments, UE 504 may transmit the sensing data to RAN node 502 via RRC. For example, all sensing measurement parameters are included in a UL RRC message. In some cases, due to the potentially large size of the sensing report, it may be segmented into several parts and each part is included in a UL RRC message for transmission. For example, UE 504 may transmit the sensing data to RAN node 502 via an SRB. The SRB may be an SRB (denoted as SRB #x) dedicated for sensing data reporting. SRB #x may have a priority lower than the priority of normal UL UE traffic, e.g., SRB #x with a priority of 9 and normal UL UE traffic with a priority of 8. However, for sensing data of a latency-sensitive task, UE 504 may transmit the sensing data to RAN node 502 via another SRB (denoted as SRB #y) having a priority higher than the priority of the UL normal UE traffic. The priority of SRB #x and / or SRB #y may be predefined or pre-configured in 3GPP specification or configured via RRC signaling.
[0123] In some embodiments, UE 504 may piggyback the sensing data in the UP data. For example, UE 504 may transmit the sensing data to RAN node 502 via data PDUs such as data PDU of the sensing layer, SDAP layer or PDCP layer. This is appropriate given the potentially large size of the sensing report.
[0124] FIG. 6A illustrates an example protocol stack 600A between a UE and a RAN node in accordance with some embodiments of the present disclosure. Referring to FIG. 6A, protocol stack 600A may include a physical layer (PHY) , a MAC layer, a RLC layer, a PDCP layer and a SDAP layer.
[0125] In some embodiments, protocol stack 600A may further include a sensing layer (denoted by a dotted block as an option) . The sensing layer may be located above the SDAP layer of the UE and the RAN node. The data PDU of the sensing layer may at least include a header and the sensing data to be reported. The header may include at least one of the coded format of the sensing data or an ID of the sensing task associated with the sensing data. The coded format can facilitate successful decoding of the sensing data reported from the UE by the RAN node or CN node. In some embodiments, the coded format may be indicated by the CN (e.g., an AMF or an SF) . The UE may be configured with the relationship between a sensing task ID and a QFI by the RAN node or the CN (e.g., an AMF or an SF) . Based on the relationship, the UE may add a QFI corresponding to the sensing task ID in the data PDU of the sensing layer to the PDU header of a lower layer (e.g., the SDAP layer) .
[0126] FIG. 6B illustrates an example data PDU 600B of a sensing layer in accordance with some embodiments of the present disclosure. Data PDU 600B may include an 8-bit header followed by a payload including the sensing data, the payload length being an integer multiple of 8 bits. It should be noted that data PDU 600B is illustrative only and are non-limiting. For example, the length of any field is not limited.
[0127] In some embodiments, the sensing data can be transmitted via data PDUs of the SDAP layer or PDCP layer. In this case, protocol stack 600A in FIG. 6A may not include the sensing layer. The header of the data PDU of the SDAP layer or PDCP layer may indicate at least one of a sensing data reporting indication or the coded format of the sensing data. Based on this indication, the RAN node can recognize that the payload is the sensing data, and deliver it to the SF, rather than the UPF. The sensing data reporting indication may include at least one bit. For example, a one-bit indication can indicate whether the data PDU carries sensing data or not. For example, more than one bit may be used for indicating the sensing data type, e.g., the particular sensing service or sensing task. The coded format can facilitate successful decoding of the sensing data reported from the UE by the RAN node or CN node. In some embodiments, the coded format may be indicated by the CN (e.g., an AMF or an SF) .
[0128] FIG. 6C illustrates an example PDU 600C of a SDAP layer in accordance with some embodiments of the present disclosure. PDU 600C may include an 8-bit header followed by a payload with a length that is an integer multiple of 8 bits. It should be noted that PDU 600C is illustrative only and are non-limiting. For example, the length of any field and the sequence of the fields are not limited. Referring to FIG. 6C, the header of PDU 600C may include a D / C field, an R field and a QFI field. The D / C field may indicate the type of the PDU, for example, whether it is a data PDU or a control PDU. The R field may be reserved for future use. The QFI field may be used for identifying the QoS flow of the payload data.
[0129] In some embodiments, the sensing data indication may use the one-bit R field. For example, a bit value of "1" indicates that PDU 600C carries sensing data, while a bit value of "0" indicates that PDU 600C does not carry sensing data, or vice versa. In some embodiments, the QFI field can be used to indicate the specific sensing service or task. For example, a specific QFI value may be used to indicate a specific sensing task. In these embodiments, the R field may or may not be used for sensing data reporting indication.
[0130] Referring back to FIG. 5, in some embodiments, UE 504 may transmit the sensing data via a DRB for sensing data reporting, via an LCH for sensing data reporting, or via a UL packet associated with a QFI for sensing data reporting. For example, RAN node 502 may configure UE 504 with a specific DRB (e.g., a specific DRB ID denoted as DRB #s) for sensing data reporting, or a specific LCH (e.g., a specific LCH ID) for sensing data reporting, or a specific QoS flow (i.e., a specific QFI) for sensing data reporting.
[0131] For example, RAN node 502 can determine whether the received data is sensing data based on the QFI in the SDAP header of the uplink packet. For example, RAN node 502 can determine whether the received data is sensing data based on the DRB ID of the uplink packet. The AMF may initiate the setup of the sensing DRB (e.g., DRB #s) based on a request from SF 508 or RAN node 502 (when there is a UE (e.g., UE 504) is selected as a sensing entity) . Alternatively, SF 508 may trigger the DRB setup to RAN node 502. For example, RAN node 502 can determine whether the received data is sensing data based on the LCH ID of the uplink packet.
[0132] At 513, RAN node 502 may process the sensing data received from UE 504. In some embodiments, for UE-based sensing, the sensing results may be processed by at least one of the UE, RAN node or SF. For example, each of these three entities can handle the sensing result individually. In some embodiments, RAN node 502 may process the sensing data sensed by itself or received from UE 504.
[0133] For example, UE 504 may process the raw sensing data (e.g., time-domain samples or subcarrier-domain samples of the channel response from each antenna port, or equivalents) and convert it to initial sensing data comprising delay, Doppler, angle, and power information, and then report the initial sensing data to RAN node 502.
[0134] RAN node 502 may process the sensing data received from UE 504 and convert it to, for example, sensing data per point, and then report it to SF 508. In some examples, a point is defined by one range / delay, one Doppler and one angle; and for a given time stamp, the sensing data per point includes range, velocity, angle, and power. In some examples, a point is defined by one location and one velocity; and for a given time stamp, the sensing data per point includes position, velocity, and power.
[0135] SF 508 may process the received sensing data into the final sensing result, for example, a tuple including position, velocity, and target ID for an unmanned aerial vehicle (UAV) detection, or some other sensing result related to environmental detection and intelligent transportation. Then, SF 508 may expose the result to the sensing consumer.
[0136] Because more than one entity may participate in the sensing processing, the sensing processing capability and division of sensing processing need to be coordinated among the entities. The sensing processing capability of an entity may include at least one of whether the entity supports sensing data processing or a level of the sensing data processing (e.g., the level at which the node can refine the sensing data) .
[0137] In some embodiments, a UE and a RAN node each report their respective sensing processing capabilities to an SF, and the SF distributes the sensing processing tasks to the UE and the RAN node accordingly. In some embodiments, the UE sensing processing capabilities are terminated at the RAN node, and the RAN node reports sensing processing capability to the SF on a per-RAN-node basis. In the latter case, the SF may distribute the sensing processing task to the RAN node, and the RAN node may further subdivide and assign the sensing processing task to the UE.
[0138] At 515, RAN node 502 may transmit the sensing data to SF 508 via the UP tunnel therebetween. For example, the UP tunnel may be established according to the embodiments described with respect to FIG. 4A. The header of the UL data packet (e.g., GTP-U header) carrying the sensing data may include the UE ID (e.g., ID of UE 504) to distinguish the UE sensing data from the RAN node sensing data. In the case that the UP tunnel between RAN node 502 and SF 508 has a granularity of per RAN node, the UE ID in the GTP-U header is sufficient for distinguishing the data. In the case that the UP tunnel between RAN node 502 and SF 508 has a granularity of per sensing task, the IP address and / or the TEID of SF 508 provided to RAN node 502 for UP tunnel establishment may be per UE or per sensing task, and thus there is no need to include the UE ID in the GTP-U header.
[0139] It should be appreciated by persons skilled in the art that the sequence of the operations in exemplary procedure 500 may be changed and that some of the operations in exemplary procedure 500 may be eliminated or modified, without departing from the spirit and scope of the disclosure.
[0140] FIG. 7 illustrates a flowchart of method 700 for wireless communication in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiments shown in FIG. 7. In some examples, method 700 may be performed by a network node such as a BS or a RAN node. In some embodiments, the RAN node may execute a set of instructions to control the functional elements of the RAN node to perform the described functions or operations. In some examples, a processor of the RAN node may cause the RAN node to perform method 700.
[0141] At 711, a RAN node may receive, from a network function for access and mobility management of a CN node, first information for establishing a connection with an SF of the CN node, wherein the first information includes at least one of an ID of the SF, a TNL address of the SF or a first IP address of the SF.
[0142] At 713, the RAN node may establish an SCTP association and a CP connection with the SF based on the first information. At 715, the RAN node may transmit sensing data to the SF via a UP tunnel between the RAN node and the SF or the CP connection.
[0143] In some embodiments, the RAN node may establish the SCTP association and the CP connection with the SF in response to a receipt of the first information or an indication to initiate the establishment from the network function.
[0144] In some embodiments, to establish the CP connection with the SF, the RAN node may: transmit a connection setup request message to the SF, wherein the connection setup request message indicates at least one of a global RAN node ID of the RAN node, a first sensing area supported by the RAN node, or capability information of the RAN node.
[0145] In some embodiments, the capability information of the RAN node indicates that the RAN node supports sensing functionality only or both sensing functionality and communication functionality.
[0146] In some embodiments, to establish the CP connection with the SF, the RAN node may: receive a connection setup response message from the SF, wherein the connection setup response message indicates at least one of the ID of the SF, a name of the SF, or a second sensing area served by the SF.
[0147] In some embodiments, the CP connection is an NG connection. The RAN node may ignore inapplicable information elements in the connection setup response message.
[0148] In some embodiments, the RAN node may receive, from a UE, UE capability information indicating that the UE supports at least one of sensing functionality, communication functionality, sensing data processing, or a level of the sensing data processing.
[0149] In some embodiments, the RAN node may transmit the UE capability information to the network function or the SF.
[0150] In some embodiments, the RAN node may: receive, from the SF via the CP connection, at least one of a second IP address or a TEID of the SF; and establish the UP tunnel based on the at least one of the second IP address or the TEID, wherein the UP tunnel is established per RAN node or per sensing task.
[0151] In some embodiments, the RAN node may: transmit, to the network function or an SMF, a session establishment request for establishing a session terminated at the RAN node; receive, from the network function or the SMF, information related to a UPF and QoS rules for the session; and establish the UP tunnel over the session via the UPF.
[0152] In some embodiments, the sensing data is received from a UE via at least one of: an SRB for sensing data reporting; a first data PDU of a sensing layer; a second data PDU of an SDAP layer; or a third data PDU of a PDCP layer.
[0153] In some embodiments, the RAN node may: process the sensing data received from a UE or sensed by the RAN node; and transmit the processed sensing data to the SF via the UP tunnel or the CP connection.
[0154] In some embodiments, a header of the first data PDU indicates at least one of a coded format of the sensing data or an ID of the sensing task associated with the sensing data. In some embodiments, a header of the second data PDU or third data PDU indicates at least one of a sensing data reporting indication or the coded format of the sensing data. In some embodiments, the RAN node may receive the coded format of the sensing data from the network function.
[0155] In some embodiments, the sensing data is received from a UE via a DRB for sensing data reporting, via an LCH for sensing data reporting, or via a UL packet associated with a QoS flow identifier for sensing data reporting.
[0156] In some embodiments, the sensing data is received from a UE. In some embodiments, a header of a UL sensing data packet, transmitted via the UP tunnel, indicates an ID of the UE. In some embodiments, the at least one of the second IP address or the TEID is configured for each UE or each sensing task.
[0157] It should be appreciated by persons skilled in the art that the sequence of the operations in exemplary method 700 may be changed and some of the operations in exemplary method 700 may be eliminated or modified, without departing from the spirit and scope of the disclosure.
[0158] FIG. 8 illustrates a flowchart of method 800 for wireless communication in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiments shown in FIG. 8. In some examples, method 800 may be performed by a CN. In some embodiments, the CN may execute a set of instructions to control the functional elements (e.g., a network function for access and mobility management and a sensing function) of the CN to perform the described functions or operations. In some examples, a processor of the CN may cause the CN (e.g., functional elements of the CN) to perform method 800.
[0159] At 811, a CN may transmit, from a network function for access and mobility management of the CN to a RAN node, first information for establishing a connection between an SF of the CN and the RAN node, wherein the first information includes at least one of an ID of the SF, a TNL address of the SF or a first IP address of the SF. At 813, the CN may establish, at the SF, an SCTP association and a CP connection with the RAN node. At 815, the CN may receive, at the SF, sensing data from the RAN node via a UP tunnel between the RAN node and the SF or the CP connection.
[0160] In some embodiments, to establish the CP connection with the RAN node, the SF of the CN may: receive a connection setup request message from the RAN node, wherein the connection setup request message indicates at least one of a global RAN node ID of the RAN node, a first sensing area supported by the RAN node, or capability information of the RAN node.
[0161] In some embodiments, the capability information of the RAN node indicates that the RAN node supports sensing functionality only or both sensing functionality and communication functionality.
[0162] In some embodiments, the capability information of the RAN node indicates that the RAN node supports sensing functionality only and the CP connection is an NG connection. The SF of the CN may ignore inapplicable information elements in the connection setup request message.
[0163] In some embodiments, to establish the CP connection with the RAN node, the SF of the CN may: transmit a connection setup response message to the RAN node, wherein the connection setup response message indicates at least one of the ID of the SF, a name of the SF, or a second sensing area served by the SF.
[0164] In some embodiments, the SF of the CN may receive, from a UE served by the RAN node, UE capability information indicating that the UE supports at least one of sensing functionality, communication functionality, sensing data processing or a level of the sensing data processing. In some embodiments, the UE capability information is received from the UE via the RAN node or via a UL NAS message.
[0165] In some embodiments, the SF of the CN may: transmit, to the RAN node via the CP connection, at least one of a second IP address or a TEID of the SF; and establish the UP tunnel with the RAN node based on the at least one of the second IP address or the TEID, wherein the UP tunnel is established per RAN node or per sensing task.
[0166] In some embodiments, the sensing data is received from a UE served by the RAN node. In some embodiments, a header of a UL sensing data packet, received via the UP tunnel, indicates an ID of the UE. In some embodiments, the at least one of the second IP address or the TEID is configured for each UE or each sensing task.
[0167] In some embodiments, the UP tunnel is established via a UPF for a session terminated at the RAN node.
[0168] It should be appreciated by persons skilled in the art that the sequence of the operations in exemplary method 800 may be changed and some of the operations in exemplary method 800 may be eliminated or modified, without departing from the spirit and scope of the disclosure.
[0169] FIG. 9 illustrates a flowchart of method 900 for wireless communication in accordance with some embodiments of the present disclosure. Details described in all of the foregoing embodiments of the present disclosure are applicable for the embodiments shown in FIG. 9. In some examples, method 900 may be performed by a UE. In some embodiments, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions or operations. In some examples, a processor of the UE may cause the UE to perform method 900.
[0170] At 911, a UE may receive a sensing command, from a RAN node serving the UE or an SF, to perform a measurement for a sensing task. At 913, the UE may transmit sensing data associated with the sensing task to the SF via a UP tunnel between the RAN node and the SF.
[0171] In some embodiments, the UE may transmit, to the RAN node or to the SF via the RAN node or via a UL NAS message, UE capability information indicating that the UE supports at least one of sensing functionality, communication functionality, sensing data processing or a level of the sensing data processing.
[0172] In some embodiments, the UE may transmit the sensing data to the RAN node via at least one of: an SRB for sensing data reporting; a first data PDU of a sensing layer; a second data PDU of an SDAP layer; or a third data PDU of a PDCP layer.
[0173] In some embodiments, the priority of the SRB is configured for the UE by the RAN node or is predefined. In some embodiments, a header of the first data PDU indicates at least one of a coded format of the sensing data or an ID of the sensing task. The UE may receive a mapping relation between the ID of the sensing task and a QFI associated with the sensing task. In some embodiments, a header of the second data PDU or third data PDU indicates at least one of a sensing data reporting indication or the coded format of the sensing data.
[0174] In some embodiments, the UE may transmit the sensing data to the RAN node via a DRB for sensing data reporting, via an LCH for sensing data reporting, or via a UL packet associated with a QFI for sensing data reporting.
[0175] It should be appreciated by persons skilled in the art that the sequence of the operations in exemplary method 900 may be changed and some of the operations in exemplary method 900 may be eliminated or modified, without departing from the spirit and scope of the disclosure.
[0176] FIG. 10 illustrates an example of apparatus 1000 in accordance with aspects of the present disclosure. Apparatus 1000 may be a UE. Apparatus 1000 may be a network node, an NE, a BS or any types of RAN node. Apparatus 1000 may be a component of a RAN node such as a CU or a DU. Apparatus 1000 may be a CN, a CN node, a CN entity, a CN module, or a CN function. Apparatus 1000 may include a processor 1002, a memory 1004, a controller 1006, and a transceiver 1008. The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
[0177] The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, or various combinations or components thereof may be implemented in hardware (e.g., circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
[0178] The processor 1002 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, a field programmable gate array (FPGA) , or any combination thereof) . In some implementations, the processor 1002 may be configured to operate the memory 1004. In some other implementations, the memory 1004 may be integrated into the processor 1002. The processor 1002 may be configured to execute computer-readable instructions stored in the memory 1004 to cause apparatus 1000 to perform various functions of the present disclosure.
[0179] The memory 1004 may include volatile or non-volatile memory. The memory 1004 may store computer-readable, computer-executable code including instructions when executed by the processor 1002 cause apparatus 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 1004 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
[0180] In some implementations, the processor 1002 and the memory 1004 coupled with the processor 1002 may be configured to cause apparatus 1000 to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004) . For example, the processor 1002 may support wireless communication at apparatus 1000 in accordance with examples as disclosed herein. For example, apparatus 1000 may be configured to support means for performing the operations as described with respect to FIGs. 1-9.
[0181] For example, apparatus 1000 may be configured to or operable to support: a means for receiving, from a network function for access and mobility management of a CN node, first information for establishing a connection with an SF of the CN node, wherein the first information includes at least one of an ID of the SF, a TNL address of the SF or a first IP address of the SF; a means for establishing an SCTP association and a CP connection with the SF based on the first information; and a means for transmitting sensing data to the SF via a UP tunnel between apparatus 1000 and the SF or the CP connection.
[0182] For example, apparatus 1000 may be configured to or operable to support: a means for transmitting, from a network function for access and mobility management of apparatus 1000 to a RAN node, first information for establishing a connection between an SF of apparatus 1000 and the RAN node, wherein the first information includes at least one of an ID of the SF, a TNL address of the SF or a first IP address of the SF; a means for establishing, at the SF, an SCTP association and a CP connection with the RAN node; and a means for receiving, at the SF, sensing data from the RAN node via a UP tunnel between the RAN node and the SF or the CP connection.
[0183] For example, apparatus 1000 may be configured to or operable to support: a means for receive a sensing command, from a RAN node serving apparatus 1000 or an SF, to perform a measurement for a sensing task; and a means for transmit sensing data associated with the sensing task to the SF via a UP tunnel between the RAN node and the SF.
[0184] The controller 1006 may manage input and output signals for apparatus 1000. The controller 1006 may also manage peripherals not integrated into apparatus 1000. In some implementations, the controller 1006 may utilize an operating system such as or other operating systems. In some implementations, the controller 1006 may be implemented as part of the processor 1002.
[0185] In some implementations, apparatus 1000 may include at least one transceiver 1008. In some other implementations, apparatus 1000 may have more than one transceiver 1008. The transceiver 1008 may represent a wireless transceiver. The transceiver 1008 may include one or more receiver chains 1010, one or more transmitter chains 1012, or a combination thereof.
[0186] A receiver chain 1010 may be configured to receive signals (e.g., control information, data, or packets) over a wireless medium. For example, the receiver chain 1010 may include one or more antennas for receiving the signal over the air or wireless medium. The receiver chain 1010 may include at least one amplifier (e.g., an LNA) configured to amplify the received signal. The receiver chain 1010 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1010 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.
[0187] A transmitter chain 1012 may be configured to generate and transmit signals (e.g., control information, data, or packets) . The transmitter chain 1012 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as AM, FM, or digital modulation schemes like PSK or QAM. The transmitter chain 1012 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1012 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0188] It should be appreciated by persons skilled in the art that the components in exemplary apparatus 1000 may be changed, for example, some of the components in exemplary apparatus 1000 may be omitted or modified or a new component (s) may be added to exemplary apparatus 1000, without departing from the spirit and scope of the disclosure. For example, in some embodiments, apparatus 1000 may not include the controller 1006.
[0189] FIG. 11 illustrates an example of processor 1100 in accordance with aspects of the present disclosure. The processor 1100 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1100 may include a controller 1102 configured to perform various operations in accordance with examples as described herein. The processor 1100 may optionally include at least one memory 1104, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 1100 may optionally include one or more arithmetic-logic units (ALUs) 1106. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
[0190] The processor 1100 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1100) ) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .
[0191] The controller 1102 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein. For example, the controller 1102 may operate as a control unit of the processor 1100, generating control signals that manage the operation of various components of the processor 1100. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0192] The controller 1102 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1104 and determine a subsequent instruction (s) to be executed to cause the processor 1100 to support various operations in accordance with examples as described herein. The controller 1102 may be configured to track memory address of instructions associated with the memory 1104. The controller 1102 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1102 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1102 may be configured to manage flow of data within the processor 1100. The controller 1102 may be configured to control transfer of data between registers, ALUs, and other functional units of the processor 1100.
[0193] The memory 1104 may include one or more caches (e.g., memory local to or included in the processor 1100) or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 1104 may reside within or on a processor chipset (e.g., local to the processor 1100) . In some other implementations, the memory 1104 may reside external to the processor chipset (e.g., remote to the processor 1100) .
[0194] The memory 1104 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1100, cause the processor 1100 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1102 and / or the processor 1100 may be configured to execute computer-readable instructions stored in the memory 1104 to cause the processor 1100 to perform various functions. For example, the processor 1100 and / or the controller 1102 may be coupled with or to the memory 1104, the processor 1100, the controller 1102, and the memory 1104 may be configured to perform various functions described herein. In some examples, the processor 1100 may include multiple processors and the memory 1104 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
[0195] The one or more ALUs 1106 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 1106 may reside within or on a processor chipset (e.g., the processor 1100) . In some other implementations, the one or more ALUs 1106 may reside external to the processor chipset (e.g., the processor 1100) . One or more ALUs 1106 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1106 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1106 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1106 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1106 to handle conditional operations, comparisons, and bitwise operations.
[0196] The processor 1100 may support wireless communication in accordance with examples as disclosed herein. For example, the processor 1100 may be configured to support means for performing the operations as described with respect to FIGs. 1-9.
[0197] For example, processor 1100 may be configured to or operable to support: a means for receiving, from a network function for access and mobility management of a CN node, first information for establishing a connection with an SF of the CN node, wherein the first information includes at least one of an ID of the SF, a TNL address of the SF or a first IP address of the SF; a means for establishing an SCTP association and a CP connection with the SF based on the first information; and a means for transmitting sensing data to the SF via a UP tunnel between a RAN node including processor 1100 and the SF or the CP connection.
[0198] For example, processor 1100 may be configured to or operable to support: a means for transmitting, from a network function for access and mobility management of a CN to a RAN node, first information for establishing a connection between an SF of the CN and the RAN node, wherein the first information includes at least one of an ID of the SF, a TNL address of the SF or a first IP address of the SF; a means for establishing, at the SF, an SCTP association and a CP connection with the RAN node; and a means for receiving, at the SF, sensing data from the RAN node via a UP tunnel between the RAN node and the SF or the CP connection.
[0199] For example, processor 1100 may be configured to or operable to support: a means for receive a sensing command, from a RAN node serving a UE including processor 1100 or an SF, to perform a measurement for a sensing task; and a means for transmit sensing data associated with the sensing task to the SF via a UP tunnel between the RAN node and the SF.
[0200] It should be appreciated by persons skilled in the art that the components in exemplary processor 1100 may be changed, for example, some of the components in exemplary processor 1100 may be omitted or modified or a new component (s) may be added to exemplary processor 1100, without departing from the spirit and scope of the disclosure. For example, in some embodiments, the processor 1100 may not include the ALUs 1106.
[0201] Those having ordinary skill in the art would understand that the operations or steps of the methods described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. Additionally, in some aspects, the operations or steps of the methods may reside as one or any combination or set of codes and / or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.
[0202] While this disclosure has been described with specific embodiments thereof, it is evident that many alternatives, modifications, and variations may be apparent to those skilled in the art. The disclosure is not limited to the examples and designs described herein but is to be accorded with the broadest scope consistent with the principles and novel features disclosed herein. For example, various components of the embodiments may be interchanged, added, or substituted in other embodiments. Also, all of the elements of each figure are not necessary for the operation of the disclosed embodiments. For example, one of ordinary skill in the art of the disclosed embodiments would be enabled to make and use the teachings of the disclosure by simply employing the elements of the independent claims. Accordingly, embodiments of the disclosure as set forth herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the disclosure.
[0203] In this document, the terms "includes, " "including, " or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. The terms "handover" and "cell switch" can be used interchangeably. An element proceeded by "a, " "an, " or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element. Also, the term "another" is defined as at least a second or more. The term "having" or the like, as used herein, is defined as "including. " Expressions such as "A and / or B" , "at least one of A or B" or "at least one of A and B" may include any and all combinations of words enumerated along with the expression. For instance, the expression "A and / or B" , "at least one of A or B" or "at least one of A and B" may include A, B, or both A and B. The wording "the first, " "the second" or the like is only used to clearly illustrate the embodiments of the present disclosure, but is not used to limit the substance of the present disclosure.
Claims
1.A radio access network (RAN) node, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the RAN node to:receive, from a network function for access and mobility management of a core network (CN) node, first information for establishing a connection with a sensing function (SF) of the CN node, wherein the first information comprises at least one of an identifier (ID) of the SF, a transport network layer (TNL) address of the SF or a first internet protocol (IP) address of the SF;establish a stream control transmission protocol (SCTP) association and a control plane (CP) connection with the SF based on the first information; andtransmit sensing data to the SF via a user plane (UP) tunnel between the RAN node and the SF or the CP connection.2.The RAN node of claim 1, wherein the at least one processor is configured to cause the RAN node to establish the SCTP association and the CP connection with the SF in response to a receipt of the first information or an indication to initiate the establishment from the network function.3.The RAN node of claim 1, wherein, to establish the CP connection with the SF, the at least one processor is configured to cause the RAN node to:transmit a connection setup request message to the SF, wherein the connection setup request message indicates at least one of a global RAN node ID of the RAN node, a first sensing area supported by the RAN node, or capability information of the RAN node.4.The RAN node of claim 3, wherein, to establish the CP connection with the SF, the at least one processor is configured to cause the RAN node to:receive a connection setup response message from the SF, wherein the connection setup response message indicates at least one of the ID of the SF, a name of the SF, or a second sensing area served by the SF.5.The RAN node of claim 1, wherein the at least one processor is configured to cause the RAN node to receive, from a user equipment (UE) , UE capability information indicating that the UE supports at least one of sensing functionality, communication functionality, sensing data processing, or a level of the sensing data processing.6.The RAN node of claim 1, wherein the at least one processor is configured to cause the RAN node to:receive, from the SF via the CP connection, at least one of a second IP address or a tunnel endpoint identifier (TEID) of the SF; andestablish the UP tunnel based on the at least one of the second IP address or the TEID, wherein the UP tunnel is established per RAN node or per sensing task.7.The RAN node of claim 1, wherein the sensing data is received from a user equipment (UE) via at least one of:a signal radio bearer (SRB) for sensing data reporting;a first data protocol data unit (PDU) of a sensing layer;a second data PDU of a service data adaptation protocol (SDAP) layer; ora third data PDU of a packet data convergence protocol (PDCP) layer.8.The RAN node of claim 1 or 7, wherein the at least one processor is configured to cause the RAN node to:process the sensing data received from a user equipment (UE) or sensed by the RAN node; andtransmit the processed sensing data to the SF via the UP tunnel or the CP connection.9.The RAN node of claim 7, wherein a header of the first data PDU indicates at least one of a coded format of the sensing data or an ID of the sensing task associated with the sensing data; orwherein a header of the second data PDU or third data PDU indicates at least one of a sensing data reporting indication or the coded format of the sensing data; orwherein the at least one processor is configured to cause the RAN node to receive the coded format of the sensing data from the network function.10.The RAN node of claim 1, wherein the sensing data is received from a user equipment (UE) via a data radio bearer (DRB) for sensing data reporting, via a logical channel (LCH) for sensing data reporting, or via an uplink (UL) packet associated with a quality of service (QoS) flow identifier for sensing data reporting.11.The RAN node of claim 6, wherein the sensing data is received from a user equipment (UE) , and wherein:a header of an uplink (UL) sensing data packet, transmitted via the UP tunnel, indicates an ID of the UE, orthe at least one of the second IP address or the TEID is configured for each UE or each sensing task.12.A core network (CN) , comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the CN to:transmit, from a network function for access and mobility management of the CN to a radio access network (RAN) node, first information for establishing a connection between a sensing function (SF) of the CN and the RAN node, wherein the first information comprises at least one of an identifier (ID) of the SF, a transport network layer (TNL) address of the SF or a first internet protocol (IP) address of the SF;establish, at the SF, a stream control transmission protocol (SCTP) association and a control plane (CP) connection with the RAN node; andreceive, at the SF, sensing data from the RAN node via a user plane (UP) tunnel between the RAN node and the SF or the CP connection.13.The CN of claim 12, wherein, to establish the CP connection with the RAN node, the at least one processor is configured to cause the SF of the CN to:receive a connection setup request message from the RAN node, wherein the connection setup request message indicates at least one of a global RAN node ID of the RAN node, a first sensing area supported by the RAN node, or capability information of the RAN node.14.The CN of claim 13, wherein the capability information of the RAN node indicates that the RAN node supports sensing functionality only and the CP connection is an NG connection, and the at least one processor is configured to cause the SF of the CN to ignore inapplicable information elements in the connection setup request message.15.The CN of claim 13 or 14, wherein, to establish the CP connection with the RAN node, the at least one processor is configured to cause the SF of the CN to:transmit a connection setup response message to the RAN node, wherein the connection setup response message indicates at least one of the ID of the SF, a name of the SF, or a second sensing area served by the SF.16.The CN of claim 12, wherein the at least one processor is configured to cause the SF of the CN to receive, from a user equipment (UE) served by the RAN node, UE capability information indicating that the UE supports at least one of sensing functionality, communication functionality, sensing data processing or a level of the sensing data processing; andwherein the UE capability information is received from the UE via the RAN node or via an uplink (UL) non-access stratum (NAS) message.17.The CN of claim 12, wherein the at least one processor is configured to cause the SF of the CN to:transmit, to the RAN node via the CP connection, at least one of a second IP address or a tunnel endpoint identifier (TEID) of the SF; andestablish the UP tunnel with the RAN node based on the at least one of the second IP address or the TEID, wherein the UP tunnel is established per RAN node or per sensing task.18.The CN of claim 17, wherein the sensing data is received from a user equipment (UE) served by the RAN node, and wherein:a header of an uplink (UL) sensing data packet, received via the UP tunnel, indicates an ID of the UE, orthe at least one of the second IP address or the TEID is configured for each UE or each sensing task.19.A method performed by a radio access network (RAN) node for wireless communication, the method comprising:receiving, from a network function for access and mobility management of a core network (CN) node, first information for establishing a connection with a sensing function (SF) of the CN node, wherein the first information comprises at least one of an identifier (ID) of the SF, a transport network layer (TNL) address of the SF or a first internet protocol (IP) address of the SF;establishing a stream control transmission protocol (SCTP) association and a control plane (CP) connection with the SF based on the first information; andtransmitting sensing data to the SF via a user plane (UP) tunnel between the RAN node and the SF or the CP connection.20.A method performed by a core network (CN) for wireless communication, the method comprising:transmitting, from a network function for access and mobility management of the CN to a radio access network (RAN) node, first information for establishing a connection between a sensing function (SF) of the CN and the RAN node, wherein the first information comprises at least one of an identifier (ID) of the SF, a transport network layer (TNL) address of the SF or a first internet protocol (IP) address of the SF;establishing, at the SF, a stream control transmission protocol (SCTP) association and a control plane (CP) connection with the RAN node; andreceiving, at the SF, sensing data from the RAN node via a user plane (UP) tunnel between the RAN node and the SF or the CP connection.
