Sensing data exchange

Abstract

Aspects of the present disclosure relate to sensing data exchange. In one aspect of the solution of the present disclosure, a network device receives, via a transceiver, sensing trigger information for sensing a protocol data unit (PDU) session for a terminal device. The network device then sends, via the transceiver, a request for sensing policy information to the network function, the sensing policy information associated with the sensing PDU session for the terminal device. In this manner, a sensing resource assignment process is triggered, and the network device obtains a sensing-related policy. Therefore, the communication performance is improved.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more particularly to devices, processors, methods, and computer-readable media for sensing data exchange. Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication with one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Furthermore, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] Wireless sensing technology aims to acquire information about remote objects or their environment and characteristics without physical contact. A new sensing function (SF) has been introduced to enable sensing in 5G system networks. The sensing process can be triggered by an application server, a 5G core (5GC) network function (NF), or a UE. The SF can assign sensing tasks to access nodes or UEs. If a sensing task is assigned to a UE, the UE can report sensing measurement data to the SF via the control plane or user plane. However, some issues still need to be addressed. Summary of the Invention

[0004] This disclosure relates to methods, apparatus, and systems that support the exchange of sensing data.

[0005] Some implementations of the methods and apparatus described herein may include receiving, via a transceiver, sensing trigger information for a sensing protocol data unit (PDU) session for an end device; and sending, via the transceiver, a request for sensing policy information associated with the sensing PDU session for the end device to a network function. In this manner, a sensing resource allocation process is triggered, and the network device acquires the sensing-related policy. This improves communication performance.

[0006] In some implementations of the methods and devices described herein, the sensing trigger information may include one of the following: a sensing indication; or a sensing task identifier (ID).

[0007] In some implementations of the methods and devices described herein, the network function may be a sensing function (SF), and the request may include one of the following: the ID of the terminal device; or the ID of the terminal device and the ID of the sensing task.

[0008] In some implementations of the methods and devices described herein, the network function may be a policy control function (PCF), and the request may include one of the following: the ID of the terminal device and SF information associated with the terminal device; or the ID of the terminal device, SF information, and sensing task ID.

[0009] In some implementations of the methods and devices described herein, SF information can be received from the Access and Mobility Management Function (AMF) via a transceiver through a request for SF information, wherein the request includes the ID of the terminal device.

[0010] Some implementations of the methods and apparatus described herein may also include: sending a request for SF information associated with a terminal device to a unified data management (UDM) via a transceiver, wherein the request includes the ID of the terminal device; and receiving the SF information associated with the terminal device from the UDM via the transceiver.

[0011] In some implementations of the methods and devices described herein, SF information may include one of the following: the SF's ID, the SF's Internet Protocol (IP) address, or the SF's Fully Qualified Domain Name (FQDN).

[0012] Some implementations of the methods and devices described herein may also include being configured to receive sensing trigger information via: receiving sensing trigger information from the terminal device via an uplink (UL) message via a transceiver; receiving sensing trigger information from the terminal device via a request to establish a sensing PDU session via a transceiver; or receiving sensing trigger information and SF information associated with the terminal device from an AMF via a transceiver.

[0013] Some implementations of the methods and apparatus described herein may further include: receiving a response to sensing policy information from an SF via a transceiver, wherein the response includes sensing policy information associated with a sensing PDU session for a terminal device.

[0014] In some implementations of the methods and devices described in this paper, the response may also include a sensing task ID.

[0015] Some implementations of the methods and apparatus described herein may also include: receiving a response from the PCF via a transceiver, including sensing control information associated with sensing strategy information.

[0016] In some implementations of the methods and devices described herein, the sensing policy information includes one of the following: at least one Quality of Service (QoS) parameter, at least one sensing requirement, user plane information of the terminal device, or transport network layer (TNL) information at the SF.

[0017] Some implementations of the methods and apparatus described herein may further include: sending a trigger message for an N4 session establishment procedure or an N4 session modification procedure to the User Plane Function (UPF) via a transceiver, wherein the trigger message includes a bidirectional tunnel indication; and receiving TNL information from the UPF for Radio Access Network (RAN) nodes and TNL information from the UPF for SF nodes via a transceiver.

[0018] Some implementations of the methods and devices described herein may also include: transmitting the ID of the sensing PDU session, TNL information at the SF or TNL information at the UPF, and second sensing control information to the RAN node via a transceiver.

[0019] In some implementations of the methods and devices described herein, the first sensing control information and the second sensing control information may include one of the following: a sensing task ID and a sensing mode of the terminal device; or a sensing task ID, a sensing mode of the terminal device, and at least one sensing requirement.

[0020] Some implementations of the methods and apparatus described herein may include: determining sensing function (SF) information associated with a sensing protocol data unit (PDU) session for a terminal device; and transmitting the SF information to a session management function (SMF) via a transceiver. This improves communication performance.

[0021] Some implementations of the methods and apparatus described herein may also include: receiving a sensing indication from a terminal device via a transceiver for determining SF information for the terminal device before determining SF information.

[0022] Some implementations of the methods and apparatus described herein may further include: receiving, via a transceiver, a sensing indication for determining the SF information and a request to establish a Sensing Protocol Data Unit (PDU) session from a terminal device before determining the SF information, wherein the SF information is sent to the SMF along with the establishment request.

[0023] Some implementations of the methods and devices described herein may also include being configured to determine SF information based on sensing indications.

[0024] Some implementations of the methods and devices described herein may also include receiving a request for SF information from the Session Management Function (SMF) via a transceiver before determining the SF information, wherein the request includes the ID of the terminal device.

[0025] Some implementations of the methods and apparatus described herein may also include: receiving a sensing registration request from a terminal device via a transceiver; selecting a sensing function (SF) for the terminal device; and sending a sensing registration request to the selected SF via the transceiver.

[0026] In some implementations of the methods and devices described herein, the sensing registration request may include information about sensing capabilities and the ID of the terminal device.

[0027] Some implementations of the methods and apparatus described herein include: receiving, via a transceiver, a request for sensing policy information from a second network device, the sensing policy information being associated with a sensing protocol data unit (PDU) session, wherein the request includes an identifier (ID) of a terminal device associated with the sensing PDU session; and transmitting the sensing policy information to the second network device via the transceiver. This improves communication performance.

[0028] In some implementations of the methods and devices described in this paper, the request may also include a sensing task ID.

[0029] In some implementations of the methods and devices described herein, the second network device may include Session Management Function (SMF) and Policy Control Function (PCF).

[0030] Some implementations of the methods and devices described herein may also include receiving a sensing registration request from a terminal device via a transceiver from an Access and Mobility Management Function (AMF).

[0031] Some implementations of the methods and devices described herein may also include: transmitting sensing function (SF) information associated with the terminal device to the Unified Data Management (UDM) via a transceiver.

[0032] Some implementations of the methods and apparatus described herein may also include assigning a sensing task to a terminal device by sending one of the following to the terminal device via a transceiver: a sensing task ID, at least one sensing request, and a user plane connectivity indication; or a sensing task ID, at least one sensing request, a user plane connectivity indication, and user plane information.

[0033] Some implementations of the methods and devices described in this paper include: determining to establish a user plane connection with the sensing function (SF); and transmitting sensing trigger information associated with a sensing protocol data unit (PDU) session to the network function via a transceiver. This improves communication performance.

[0034] In some implementations of the methods and devices described herein, the network function may be a Session Management Function (SMF), and the sensing trigger information may include one of the following: a sensing indication; or a sensing task identifier (ID).

[0035] In some implementations of the methods and devices described herein, the network function may be an Access and Mobility Management Function (AMF), and the sensing trigger information may include one of the following: a sensing indication; or a sensing task identifier (ID).

[0036] In some implementations of the methods and devices described herein, sensing trigger information may be sent along with a request to establish a sensing PDU session.

[0037] Some implementations of the methods and apparatus described herein may also include being configured to determine whether to establish a user plane connection with the SF by: receiving sensing task information from the SF; receiving sensing task information from a radio access network (RAN) node; or receiving sensing task information from an application on a terminal device.

[0038] In some implementations of the methods and devices described herein, sensing task information may include one of the following: a sensing task ID, at least one sensing request, a user plane connection indication, user plane information, or an indication to provide sensing results directly to the SF.

[0039] Some implementations of the methods and devices described herein may also include: receiving UE routing policy (URSP) rules for sensing from the PCF via a transceiver; and determining at least one attribute of the sensing PDU session based on the rules, wherein the at least one attribute includes the PDU session and service continuity (SSC) mode, the type of PDU session, network slice, data network name (DNN), and access type.

[0040] Some implementations of the methods and apparatus described herein may also include: sending a sensing registration request to the AMF via a transceiver, so that the AMF sends a sensing registration request to the SF; and receiving a sensing registration response from the AMF via a transceiver, wherein the AMF receives the sensing registration response from the SF.

[0041] Some implementations of the methods and apparatus described herein may also include receiving, via a transceiver, one of the following from a radio access network (RAN) node: user plane information of the terminal device; QoS flow identifier (QFI); data radio bearer (DRB) ID; logical channel ID, logical channel group ID; or at least one sensing resource corresponding to the sensing mode and at least one sensing requirement of the terminal device. Attached Figure Description

[0042] Figure 1A An example of a wireless communication system supporting sensing data exchange according to various aspects of this disclosure is illustrated.

[0043] Figure 1B An example of a user plane protocol for sensing a PDU session is illustrated according to various aspects of this disclosure.

[0044] Figure 1C The illustration shows an example session management (SM) policy association establishment process based on various aspects of this disclosure.

[0045] Figure 2 An example signaling diagram is shown, illustrating an example process according to various aspects of this disclosure.

[0046] Figure 3 An example sensing PDU session establishment process according to various aspects of this disclosure is illustrated.

[0047] Figure 4 The illustration shows another example of a sensing PDU session establishment process according to various aspects of this disclosure.

[0048] Figure 5 The illustration shows another example of a sensing PDU session establishment process according to various aspects of this disclosure.

[0049] Figure 6 The illustration shows yet another example of a sensing PDU session establishment process according to various aspects of this disclosure.

[0050] Figure 7 An example sensing registration process according to various aspects of this disclosure is illustrated.

[0051] Figures 8 to 11 An example of a device supporting sensing data exchange according to various aspects of this disclosure is illustrated.

[0052] Figures 12 to 15 An example of a processor supporting sensing data exchange according to various aspects of this disclosure is illustrated.

[0053] Figure 16 A flowchart illustrating a method for supporting sensing data exchange according to various aspects of this disclosure is shown.

[0054] Figure 17 A flowchart illustrating a method for supporting sensing data exchange according to various aspects of this disclosure is shown.

[0055] Figure 18 A flowchart illustrating a method for supporting sensing data exchange according to various aspects of this disclosure is shown.

[0056] Figure 19 A flowchart illustrating a method for supporting sensing data exchange according to various aspects of this disclosure is shown.

[0057] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0058] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not impose any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0059] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0060] References to "an embodiment," "an exemplary embodiment," and "an embodiment," etc., in this disclosure indicate that the described embodiments may include a particular feature, structure, or characteristic, but not every embodiment is required to include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment(s). Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will recognize that in conjunction with other embodiments (whether explicitly described or not) affecting such a feature, structure, or characteristic is within the scope of their knowledge.

[0061] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0062] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein also include the plural forms. Furthermore, it should be understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including”, when used herein, specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used herein, “at least one of the following: ” and “<at least one item in a list of two or more elements>” and similar wording (where a list of two or more elements is connected by “and” or “or”) means at least any one of these elements, or at least any two or more of these elements, or at least all of these elements.

[0063] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as 5G New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols and / or any other currently known or to be developed in the future. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will be future types of communication technologies and systems in which this disclosure can be embodied. This should not be construed as limiting the scope of this disclosure to the systems described above.

[0064] As used herein, the term "network device" generally refers to a node in a communication network through which terminal devices can access the network and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), Radio Access Network (RAN) nodes, Evolved Node B (eNodeB or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), Radio Header (RH), infrastructure equipment for V2X (Vehicle-to-Everything) communication, Transmitter Receiver Point (TRP), Receiver Point (RP), Remote Radio Header End (RRH), relay, Integrated Access and Backhaul (IAB) nodes, and low-power nodes (such as femtoBS, picoBS, etc.), depending on the terminology and technology applied. Network devices can also refer to network functions (NFs) in the core network, such as SMF, AMF, PCF, UPF, or devices with similar functions in future network architectures.

[0065] As used herein, the term "terminal device" generally refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), end-user equipment, user station (SS), unmanned aerial vehicle (UAV), portable user station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices (e.g., remote surgical equipment), industrial equipment (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal equipment", "communication equipment", "terminal", "user equipment" and "UE" are used interchangeably.

[0066] Wireless sensing technology aims to acquire information about remote objects or their environment and characteristics without physical contact. This can be achieved using cameras, radar, or lidar, among others. There are also surveys and solutions regarding how to utilize communication technologies (e.g., LTE or NR as defined by 3GPP, and WLAN) for sensing. There are also initiatives to enhance cellular wireless communication systems (e.g., 5G systems (5GS) as defined by 3GPP) to incorporate wireless sensing. In other words, in addition to traditional communication services, wireless systems can perform sensing tasks and report the results to applications, customers, or vertical industries interested in the sensing findings. Sensing can also be used within wireless communication systems to improve network performance.

[0067] A novel sensing function (SF) is introduced to enable sensing in 5GS networks. The SF can be a standalone 5GC NF or can be co-located with an existing 5GC NF, such as a Location Management Function (LMF). An application server, a 5GC NF, or a UE can trigger the sensing process. The SF can assign sensing tasks to an access node or a UE. If a sensing task is assigned to a UE, the UE can report sensing measurement data to the SF via the control plane or the user plane. This disclosure considers the UE reporting sensing measurement data via the user plane.

[0068] In traditional 3GPP networks, the UE triggers the establishment of a PDU session for newly detected applications or requested by the network by providing a Device Trigger Request message. The Device Trigger Request message contains application information on the UE side. The UE first evaluates the URSP rules and determines the attributes of the PDU session. Then, the UE determines whether an existing PDU session exists that matches all the attributes of the PDU session. If not, the URSP processing layer requests the UE's Non-Access Stratum (NAS) layer to establish a PDU session to provide the PDU session attributes. During the PDU session establishment or modification process, the PCF provides the SMF with SM policies applicable to the PDU session lifecycle. SM policies include session-related policies and Policy and Charging Control (PCC) rules. The Session Management Policy Control service can be used for charging control, policy control, application detection and control, and / or access service bootstrapping, handover, and splitting. Upon receiving the SM policy from the PCF, the SMF configures the User Plane Function (UPF) using N4 rules to enable packet processing on the UPF side. N4 rules include Packet Detection Rules (PDR), Forwarding Action Rules (FAR), and QoS Enforcement Rules (QER). The SMF configures QoS flows and corresponding QoS profiles for the RAN node to enable QoS processing on the RAN side. The SMF also configures QoS rules for the UE to enable uplink (UL) packet processing on the UE side. An N3 tunnel is established between the RAN node and the UPF for the PDU session. The UE exchanges data with the application server via the RAN node and the UPF.

[0069] Similarly, assume a sensing PDU session is established between the UE and the SF / SF-U (SF user plane). One option is to establish an N3 tunnel for the PDU session between the RAN and the UPF. Another option is to omit the UPF, meaning a user plane tunnel exists directly between the RAN and the SF / SF-U. Several issues need to be addressed regarding the establishment of the sensing PDU session. The UE-triggered PDU session establishment for sensing and the method by which the SMF acquires sensing-related policies are unclear. Furthermore, the triggering of RAN node assignment of sensing resources (e.g., downlink sensing resources for the UE to perform sensing and uplink resources for the UE to send sensing signaling) is also unclear.

[0070] In view of the foregoing discussion, embodiments of this disclosure provide a solution for sensing data exchange. In one aspect of the solution, a network device receives sensing trigger information for a sensing PDU session of a terminal device via a transceiver. The network device then sends a request for sensing policy information, associated with the sensing PDU session of the terminal device, to a network function via the transceiver. In this manner, a sensing resource allocation process is triggered, and the network device acquires the sensing-related policy. Therefore, communication performance is improved. Reference will be made below. Figures 1A to 19 The principles and implementation of the embodiments of this disclosure are described in detail.

[0071] Various aspects of this disclosure are described in the context of wireless communication systems.

[0072] Figure 1A An example of a wireless communication system 100A supporting sensed data exchange according to various aspects of this disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an Advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. Furthermore, 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).

[0073] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0074] Network entity 102 may provide a geographic coverage area 112 for which network entity 102 supports services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more wireless access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0075] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, user equipment, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine-Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0076] One or more UEs 104 can be devices of different forms or with different capabilities. Figure 1 illustrates some examples of UEs 104. UEs 104 are capable of communicating with various types of devices, such as network entities 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device), as shown in Figure 1. Additionally or alternatively, UEs 104 may support communication with other network entities 102 or UEs 104 that can act as relays in the wireless communication system 100.

[0077] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via 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, communication link 114 may be referred to as a sidechain. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0078] Network entity 102 may support communication with core network 106 or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). An ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs)).

[0079] In some implementations, network entity 102 can be configured with a decomposed architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or Virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of a Central Unit (CU), Distributed Unit (DU), Radio Unit (RU), RAN Intelligent Controller (RIC) (e.g., near real-time RIC, non-real-time RIC), Service Management and Orchestration (SMO) system, or any combination thereof.

[0080] An RU can also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a decomposed RAN architecture, one or more components of network entity 102 can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0081] The functional decomposition between CU, DU, and RU can be flexible and can support different functions based on the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, a protocol stack functional decomposition can be used between the CU and DU, allowing the CU to support one or more layers of the protocol stack and the DU to support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0082] Alternatively, a functional split of the protocol stack can be employed between the DU and RU, allowing the DU to support one or more layers of the protocol stack and the RU to support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and DU, or between the DU and RU, can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by different items in the CU, DU, or RU).

[0083] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via mid-range communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the mid-range or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by the respective network entity 102 communicating via such communication links.

[0084] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route 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 entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) of one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0085] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0086] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more digital technologies.

[0087] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefix. The first digital technology (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first digital technique (e.g., ...) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. Second digital technologies (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. The third digital technology (e.g., μ =2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ =3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ=4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0088] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0089] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ =4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the digital technique. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the digital technique. It should be understood that the first digital technique (e.g., quantity) associated with the first subcarrier spacing (e.g., 15kHz) can be... μ The reference of =0 can be used interchangeably between subframes and time slots.

[0090] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, along with other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, along with other devices or apparatuses, for short-range, high data rate capabilities.

[0091] FR1 can be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 can be associated with the following: a first digital technology (e.g., μ =0), which includes a 15kHz subcarrier spacing; second digital technology (e.g., μ =1), which includes a 30kHz subcarrier spacing; third digital technology (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 can be associated with a third digital technology (e.g., μ =2), which includes a 60kHz subcarrier spacing; fourth digital technology (e.g., μ =3), which includes a subcarrier spacing of 120kHz.

[0092] Figure 1B Examples of user plane protocols for sensing PDU sessions according to various aspects of this disclosure are illustrated. The user plane protocol is used for sensing between the UE and the SF. An NR Sensing Protocol Annex-U (NRSP-U) for the user plane is defined for exchanging user plane data between the UE and the SF; for example, the UE utilizes the NRSP-U layer to provide sensing measurement data to the SF.

[0093] Figure 1CThe illustration depicts an example SM policy association establishment process according to various aspects of this disclosure. During PDU session establishment, the SMF can perform PCF selection and trigger the SM policy association establishment process toward the selected PCF. The SMF invokes the Npcf_SMPolicyControl_Create operation, which includes information about the PDU session, such as the Subscription Permanent Identifier (SUPI), PDU session ID, DNN, Single Network Slice Selection Assistance Information (S-NSSAI), and RAT type. If the PCF does not have user subscription-related information, it sends a request to the Unified Data Repository (UDR) by invoking the Nudr_DM_Query (SUPI, DNN, S-NSSAI, Policy Data, PDU Session Policy Control Data, Remaining Allowed Usage Data) service to receive information related to the PDU session. The PCF then generates an SM policy containing session rules and PCC rules, and sends it to the SMF. During PDU session modification, the SMF or PCF can trigger the SM policy association modification process. For example, the AF can request to establish a data session with the UE with specific QoS (e.g., low latency or jitter) and priority processing. Based on the required QoS provided by AF, PCF triggers the SM policy association modification process to provide QoS parameters and QoS monitoring to SMF.

[0094] Figure 2 A signaling diagram is illustrated, which shows an example process 200 according to various aspects of this disclosure. Process 200 may relate to terminal device 104, SMF 120, AMF 130, SF 140, and PCF 150. It should be understood that although process 200 is applied to... Figure 1A The communication environment is 100A, but the process can also be applied to other communication scenarios with similar problems.

[0095] In process 200, terminal device 104 determines 201 to establish a user plane connection with SF. In some embodiments, terminal device 104 may determine to establish a user plane connection with SF in response to receiving sensing task information from SF. Sensing task information may refer to information associated with a sensing task assigned to terminal device 104. For example, terminal device 104 may be triggered to check whether a PDU session has been established for SF to assign a sensing task to terminal device 104 for sensing. In some embodiments, terminal device 104 may determine to establish a user plane connection with SF in response to receiving sensing task information from RAN node. For example, terminal device 104 may be triggered to check whether a PDU session has been established for RAN node to assign a sensing task to terminal device 104 for sensing. In some embodiments, terminal device 104 may determine to establish a user plane connection with SF in response to receiving sensing task information from an application on terminal device 104. For example, terminal device 104 may be triggered to check whether a PDU session has been established for application on terminal device 104 to assign a sensing task to terminal device 104 for sensing.

[0096] The sensing task information may include a sensing task ID, at least one sensing request, a user plane connection indication, user plane information, or an indication to directly provide sensing results to the SF, or any combination of two or more of the above items. For example, the sensing task information may include an indication to directly provide sensing results to the SF when the RAN node assigns a sensing task to the terminal device 104 and instructs the terminal device 104 to forward the sensing results to the SF. The user plane connection indication specifies that the SF supports a user plane connection with the UE, or instructs the UE to establish a user plane connection with the SF. The user plane information includes the SF's user plane address and security information.

[0097] In some scenarios, terminal device 104 can also receive URSP rules for sensing from PCF via a transceiver. Assuming the UE is a sensing UE, the UE triggers a sensing registration process with SF via AMF. AMF marks the UE as a sensing UE upon receiving a UL NAS message containing a sensing message container. AMF then triggers a UE policy association establishment / modification process toward PCF by including a sensing UE indicator. Upon receiving the sensing UE indicator, PCF generates URSP rules for sensing and sends them to the UE via AMF. Terminal device 104 then determines at least one attribute of the sensing PDU session based on the URSP rules. The at least one attribute includes Service Continuity Mode (SSC), PDU session type, network slice, Data Network Name (DNN), and access type. In some examples, terminal device 104 can use a default PDU session for sensing. In other examples, terminal device 104 can establish a new PDU session for sensing.

[0098] Continue to refer to Figure 2 Terminal device 104 sends 203 sensing trigger information 204 associated with the sensing PDU session. For example, the sensing trigger information may refer to information that triggers the sensing PDU session. The sensing PDU session may refer to a PDU session that sends sensing data. For example, terminal device 104 may send sensing measurement data via the sensing PDU session.

[0099] In some embodiments, terminal device 104 may send sensing trigger information 204 to SMF 120, and sensing trigger information 204 may include a sensing indication or a sensing task ID. For example, terminal device 104 may use a default PDU session for sensing and send a sensing indication or a sensing task ID to SMF 120. The sensing task ID may include a sensing transaction ID, a sensing process ID, or another ID used by the SF to identify which sensing task it is. In this case, the sensing trigger information may be transparent to AMF 130.

[0100] In some other embodiments, terminal device 104 may send sensing trigger information 204 along with a request to establish a sensing PDU session to SMF 120, and the sensing trigger information may include a sensing indication or a sensing task ID. For example, the sensing trigger information may be sent along with the request to establish a sensing PDU session. In this case, the sensing trigger information may be transparent to AMF 130.

[0101] In one example, terminal device 104 can use a default PDU session for sensing and send a sensing indication to AMF 130. In another example, terminal device 104 can establish a new PDU session for sensing and send a sensing indication or sensing task ID to AMF 130. AMF 130 then forwards the sensing indication or sensing task ID to SMF 120. The sensing indication or sensing task ID is carried in the request to establish the sensing PDU session. In yet another example, terminal device 104 can establish a new PDU session for sensing and send a sensing indication to AMF 130, and the sensing indication is sent along with the request to establish the sensing PDU session. In this case, the sensing trigger information may be opaque to AMF 130.

[0102] On the other side of the communication, SMF 120 receives, via transceiver 205, sensing trigger information 208 for a sensing PDU session for the terminal device. In some embodiments, SMF 120 may receive sensing trigger information from the terminal device via uplink (UL) messages, such as N1 SM information contained in a UL NAS message. In some embodiments, SMF 120 may receive sensing trigger information from the terminal device via a request to establish a sensing PDU session. In some embodiments, SMF 120 may receive sensing trigger information and SF information associated with the terminal device from AMF.

[0103] For example, SF information can be received from the access point and AMF via a transceiver through a request for SF information. This request may include the terminal device's ID. The terminal device's ID can be a SUPI, a Universal Public Subscription Identifier (GPSI), a 5G Globally Unique Temporary Identifier (GUTI), a 5G-S Temporary Mobile Subscription Identifier (TMSI), etc. In some cases, the SMF 120 can also send a request for SF information associated with the terminal device to the UDM via the transceiver, and this request includes the terminal device's ID. The SMF 120 can then receive the SF information associated with the terminal device from the UDM via the transceiver.

[0104] In some embodiments, SF information may include the SF's ID, the SF's IP address, the SF's FQDN, or any combination of two or more of the above items.

[0105] On the other side of the communication, AMF 130 can receive 209 sensing trigger information 208 from terminal device 104. AMF 130 determines 211 the SF information associated with the sensing PDU session of the terminal device. AMF 130 sends 213 SF information 214 to SMF 120 via transceiver.

[0106] In some embodiments, before determining the SF information, AMF 130 may also receive a sensing indication from the terminal device via a transceiver for determining the SF information of the terminal device. In some embodiments, before determining the SF information, AMF 130 may also receive a sensing indication for determining the SF information and an establishment request for a sensing PDU session from the terminal device via a transceiver, and the SF information is sent to SMF 120 along with the establishment request. In some embodiments, to determine the SF information, AMF 130 may determine the SF information based on the sensing indication. In this case, the sensing trigger information is opaque to AMF 130.

[0107] In some other embodiments, before determining the SF information, the AMF 130 may receive a request for the SF information from the SMF 120 via a transceiver, and the request may include the ID of the terminal device.

[0108] Continue to refer to Figure 2 SMF 120 sends a request 218 for sensing policy information associated with the sensing PDU session of terminal device 104. In some embodiments, SMF 120 may send a request 217 for sensing policy information to SF 140, and the request may include the terminal device ID, or the terminal device ID and sensing task ID. In some embodiments, SMF 120 may send a request 222 for sensing policy information to PCF 150, and the request may include the terminal device ID and SF information associated with the terminal device, or the terminal device ID, SF information and sensing task ID.

[0109] On the other side of the communication, SF 140 receives a request for sensing policy information from a second network device, and the request includes the ID of the terminal device associated with the sensing PDU session. In some embodiments, the request may also include a sensing task ID.

[0110] In some embodiments, SF 140 may receive 219 requests 218 for sensing policy information from SMF 120. In some embodiments, SF 140 may receive 227 requests 226 for sensing policy information from PCF 150 via a transceiver. On the PCF 150 side, PCF 150 may receive 223 requests 222 for sensing policy information from SMF 120, and then PCF 150 may send 225 requests 226 for sensing policy information to SF 140. In some embodiments, PCF 150 may receive 223 requests 222 for sensing policy information, along with the ID and SF information of the terminal device, from SMF 120. In some embodiments, PCF 150 may determine the sensing policy based on a DNN or a DNN and S-NSSAI provided by SMF 120.

[0111] Continue to refer to Figure 2 SF 140 sends sensing strategy information 230. In some embodiments, SF 140 may send sensing strategy information 230 229 to SMF 120. In some embodiments, SF 140 may send sensing strategy information 233 to PCF 150.

[0112] The SMF 120 can also receive a response to sensing policy information from the SF via a transceiver, and this response may include sensing policy information associated with a sensing PDU session for a terminal device. In some embodiments, the response may also include a sensing task ID. The SMF 120 can also receive a response from the PCF including first sensing control information associated with the sensing policy information. For example, the first sensing control information may be included in a PCC rule, and the first sensing control information may be associated with a service data stream. The sensing policy information may include at least one QoS parameter, at least one sensing requirement, user plane information of the terminal device, or TNL information at the SF. When receiving data from network devices (e.g., NG-RAN nodes or UPFs), the SF uses the TNL information at the SF to identify the associated UE (or associated user equipment and sensing PDU session).

[0113] The SMF 120 can also send trigger messages for the N4 session establishment or N4 session modification process to the User Plane Function (UPF) via a transceiver, and the trigger messages may include bidirectional tunnel indications. The SMF 120 can optionally receive TNL information from the UPF for the RAN node and TNL information from the UPF for the SF via the transceiver. The SMF 120 can also send the following to the RAN node: the ID of the sensing PDU session, TNL information at the SF or the UPF, and second sensing control information. For example, if sensing measurement data is forwarded from the RAN node to the UPF, the SMF 120 can send the TNL information from the UPF to the RAN node. If sensing measurement data is sent from the RAN node to the SF without being forwarded by the UPF, the SMF 120 can send the TNL information from the SF to the RAN node. The SMF 120 can also send NAS messages for the terminal device to the RAN node, which may contain user plane information for the terminal device.

[0114] The first and second sensing control information may include a sensing task ID and the sensing mode of the terminal device, or may include a sensing task ID, the sensing mode of the terminal device, and at least one sensing requirement. A sensing mode may refer to a method of performing sensing by transmitting signals between network devices and terminal devices, between network devices, or between terminal devices. For example, sensing modes include: Sensing Mode 1: RAN node transmits and receives sensing signals; Sensing Mode 2: RAN node A transmits sensing signals, and RAN node B receives sensing signals; Sensing Mode 3: UE transmits sensing signals, and RAN node receives sensing signals; Sensing Mode 4: UE A transmits sensing signals, and UE B receives sensing signals; Sensing Mode 5: RAN node transmits sensing signals, and UE receives sensing signals. Terminal device 110 may also receive from the RAN node: associated sensing resources, and any one of the following: QFI, DRB ID, logical channel ID, or logical channel group ID, and at least one sensing requirement, or any combination of two or more of the above items. Terminal device 110 may also receive NAS messages from the SMF via the RAN node.

[0115] Before sending the sensing trigger information, terminal device 110 may also send a sensing registration request to AMF 130, so that AMF 130 can forward the sensing registration request to SF 140 and receive a sensing registration response from AMF 130 via a transceiver. AMF 130 receives the sensing registration response from SF. In some embodiments, the sensing registration request may include sensing capability information and the ID of terminal device 104.

[0116] AMF 130 can also receive a sensing registration request from the terminal device via a transceiver. AMF 130 can then select a SF (Sensing Provider Interface) for the terminal device. Afterwards, AMF 130 can send a sensing registration request to the selected SF 140. Therefore, SF 140 can also receive the sensing registration request from the terminal device 104 via a transceiver from AMF 130. In some embodiments, SF 140 can also send SF information associated with the terminal device to the UDM (User Plane Module) via a transceiver. SF 140 can also assign sensing tasks to the terminal device by sending a sensing task ID, at least one sensing request, and a user plane connection indication, or a sensing task ID, at least one sensing request, a user plane connection indication, and user plane information.

[0117] Figure 3 The illustration shows a signaling diagram of an example process 300 according to some embodiments of the present disclosure. Process 300 may involve UE 301, RAN node 302, AMF 303, SF 304, SMF 305, PCF 306, UPF 307, and UDM 308. It should be understood that process 300 can be considered as... Figure 2 A more specific example of process 200.

[0118] In procedure 300, UE 301 checks whether a PDU session has been established for sensing, i.e., whether an existing sensing PDU session exists. This can be triggered by three reasons. As one reason, SF 304 assigns a 311 sensing task to UE 301. SF 304 provides UE 301 with a sensing task ID, and SF 304 may also provide UE 301 with sensing requirements, as well as user plane connectivity indications or user plane information (e.g., SF's user plane address and security-related information). Sensing requirements may include sensing service type, refresh rate, target detection rate, target false alarm rate, sensing area, sensing speed range, last sensing time, reporting period, latency, resolution and accuracy of the sensed object location, speed, and angle, etc.

[0119] For another reason, RAN node 302 assigns sensing task 313 to UE 301. For example, RAN node 302 provides UE 301 with a sensing task ID. RAN node 302 can also provide UE 301 with sensing requests and direct indication of sensing results to SF 304. It is assumed that UE 301 may have already negotiated with SF 304 to use a user plane connection to exchange sensing data.

[0120] As another reason, applications on UE 301 assign 315 sensing tasks to UE 301. For example, the UE's application layer provides a sensing task ID to the UE's NAS layer, and the UE's application layer can also provide sensing requests and user plane connectivity indications. Furthermore, it is assumed that the application server provides the sensing task ID to the UE's application layer, which is outside the scope of 3GPP. The application server can trigger a sensing task with a sensing task ID to SF 304.

[0121] UE 301 can decide to use a user plane connection for self-sensing, or be indicated by a user plane connection indication, or by user plane information. There are two main options for establishing a user plane between UE 301 and SF 304.

[0122] In one option, the default PDU session is used for sensing. In this way, it is assumed that the default PDU session is established as usual. Whenever UE 301 is triggered by a sensing task, UE 301 provides the SMF 305 with a 317 sensing task ID or sensing indication. That is, in another option, the sensing task ID or sensing indication may not be combined with the PDU session establishment request message. For example, the UE sends a UL NAS message to the AMF containing N1 SM information and sensing trigger information (e.g., sensing indication or sensing task ID). The AMF forwards the N1 SM information with sensing trigger information to the SMF associated with the default PDU session. In this case, the sensing trigger information is transparent to the AMF.

[0123] In another option, a PDU session is established specifically for sensing. UE 301 checks 319 whether a PDU session has been established for sensing. If no existing PDU session exists for sensing, UE 301 triggers 321 the PDU session establishment procedure. Assuming the UE performs a registration procedure in 5GC, PCF 306 can provide URSP rules for sensing. URSP rules for sensing can include any combination of dedicated DNN and S-NSSAI for sensing, application descriptors, and corresponding routing descriptors (RSDs). Alternatively, URSP sensing rules only include RSDs. That is, whenever the UE decides to use a user plane connection for sensing, it selects RSDs for sensing within the URSP rules according to the order of RSD preferences. When a valid RSD is found, the UE determines the attributes of the PDU session (e.g., SSC mode, PDU session type, network slice, DNN, and access type, etc.).

[0124] UE 301 sends a 321 PDU Session Establishment Request message to AMF 303. The PDU Session Establishment Request message includes a sensing task ID or a sensing indication. Other IDs used to identify the sensing task can be used instead of the sensing task ID, such as an event ID, correlation ID, etc. Alternatively, a sensing indication can be used. It is assumed that SF 304 knows UE 301's most recent sensing task. AMF 303 sends a 323 UE ID (e.g., SUPI) and PDU Session Establishment Request message to the selected SMF 305. For example, AMF 303 triggers an Nsmf_PDUSession_CreateSMContext request to SMF 305, which includes a SUPI and an N1SM container (PDU Session Establishment Request). In this case, the sensing triggering information is transparent to the AMF.

[0125] When the SMF305 receives a sensing task ID or sensing indication contained in a PDU session establishment request message from the UE 301, it requests 325 SF information. When requesting SF information, the SMF305 also sends the UE ID.

[0126] There are two options for requesting SF information. In one option, SMF 305 requests SF information 325 from AMF 303 by providing the UE ID. The UE ID can be SUPI (or GPSI, 5G-GUTI, 5G-S-TMSI) or a UE ID assigned by the AMF, such as the AMF UE XAP ID. It is assumed that the AMF assigns a UE ID (i.e., AMF UE XAPID) used through the X interface between the AMF and SF to identify the UE. In response, the SF will also assign a UE ID (i.e., SF UE XAPID) used through the X interface between the AMF and SF to identify the UE. AMF 303 responds to SMF 305 327 with SF information (e.g., the SF ID, IP address, or FQDN of SF 304). AMF 303 also responds to SMF 305 with the UE ID.

[0127] In another option, SMF 305 requests SF information 329 from UDM 308 by providing the UE ID. The UE ID can be SUPI (or GPSI, 5G-GUTI, 5G-S-TMSI). UDM 308 responds to SF 331 with the UE ID and SF information (e.g., SF ID, IP address, or FQDN of the SF).

[0128] Upon receiving the SF information, SMF 305 triggers the sensing policy association establishment process. For example, SMF 305 sends a sensing policy association establishment request message to SF 304, including the UE ID. This message may also include a sensing task ID. The UE ID can be SUPI (or GPSI, 5G-GUTI, 5G-S-TMSI), or a UE ID assigned by AMF (e.g., AMF UE XAPID). If UE 304 provides a sensing task ID, that ID is present in the sensing policy association establishment request message.

[0129] SF 304 sends a Sensing Policy Association Establishment Response Message 335, containing UE ID and sensing policy information, to SMF 305. Furthermore, the Sensing Policy Association Establishment Response Message may include a Sensing Task ID. The Sensing Policy Information may include any combination of the following: flow description (e.g., including protocol 3-tuples, SF-side IP address, and port number), sensing QoS requirements (e.g., QoS references for determining QoS parameters, such as 5G QoS identifiers, 5QI), individual QoS parameters (e.g., requested priority, maximum burst size, requested 5GS latency, requested 5G latency, requested maximum bit rate, requested guaranteed bit rate, and requested packet error rate, etc.), sensing measurement requirements (e.g., sensing service type, refresh rate, target detection rate, target false alarm rate, sensing area, sensing speed range, last sensing time, reporting period, latency, resolution and accuracy of the sensed object location, speed, and angle, etc.), UE user plane information (e.g., SF user plane address and security-related information), and TNL information on the SF 304 side. TNL information includes the IP address and the General Packet Radio System Tunneling Protocol User Plane (GTP-U) Tunnel Endpoint Identifier (TEID). Alternatively, SF 304 may provide SF-side TNL information in a separate message. If SF 304 provides UE 301 with UE's user plane information via AMF 303, then UE 301's user plane information is not present here.

[0130] Assuming a user plane tunnel exists between RAN node 302 and UPF 307, SMF 305 triggers the 337 N4 session establishment or N4 session modification process upon receiving sensing policy information from SF 304. During the N4 session establishment or modification process, SMF 305 provides UPF 307 with PDR, QoS-related information (e.g., maximum bit rate of the service data stream, guaranteed stream bit rate, and guaranteed stream bit rate QoS stream maximum stream bit rate), corresponding packet label information, and SF-side TNL information. In response, UPF 307 can provide SMF 305 with UPF-side TNL information. SMF 305 should then forward the UPF-side TNL information to SF 304, which is not shown in the figure. Alternatively, SMF 305 can instruct UPF 307 to provide both UPF-side TNL information by providing a bidirectional tunnel indication. Then, UPF 307 provides SMF 305 with TNL information on the UPF side for RAN node 302 (for UL) and TNL information on the UPF side for SF 304 (for DL). Accordingly, the TNL information on the UPF side for RAN node 302 (for UL) should be forwarded to RAN node 302, and the TNL information on the UPF side for SF 304 (for DL) should be forwarded to SF 304. If a direct user plane tunnel exists between RAN node 302 and SF 304 or SF-U, the N4 session establishment procedure or N4 session modification procedure will not be triggered.

[0131] SMF 305 provides RAN node 302 with UE NAS messages, PDU session IDs, (multiple) QFIs, QoS profiles, sensing control information, and TNL information from the SF side or UPF side. Sensing control information may include sensing task IDs and sensing modes, etc. Alternatively, sensing control information may also include at least one sensing requirement. UE 301's NAS messages (e.g., N1 SM container) may include UE user plane information (e.g., user plane address and security-related information from SF 304) (if available). If the user plane connection is between RAN node 302 and SF 304 without UPF involvement, SMF 305 further provides RAN node 302 with SF-side TNL information. If the user plane connection is between RAN node 302 and UPF 307, SMF 305 forwards UPF-side TNL information to RAN node 302.

[0132] Upon receiving sensing control information from SMF 305, RAN node 302 determines sensing resources based on the sensing mode and sensing requirements. RAN node 302 provides UE 301 with a 341 NAS message (UE user plane information), the associated sensing resources, and any one of the following: QFI, DRB ID, logical channel ID, or logical channel group ID. For example, if the sensing mode is RAN node 302 transmitting and UE 301 receiving, the sensing resources are the time and frequency resources (e.g., time slots, physical resource blocks) that UE 301 should use to perform sensing and process sensing data. If the sensing mode is UE 301 transmitting and RAN / another UE receiving, the sensing resources are the time and frequency resources that UE 301 should use to transmit sensing signals. Furthermore, RAN node 302 establishes a GTP-U tunnel with UPF 307 or SF 304 based on TNL information from UPF 307 or SF 304. In response, RAN node 302 should provide SMF 305 with the RAN node's TNL information. SMF 305 will then forward TNL information to UPF 307 or SF 304, which are not shown in the diagram.

[0133] When UE 301 receives the UE's user plane information contained in the NAS message from SMF 305, it generates sensing measurement data by setting the target address to the user plane address of SF 304 (e.g., setting the target IP address to the IP address of SF 304). Furthermore, UE 301 encapsulates the sensing measurement data together with the security-related information contained in the user plane information of the NAS message.

[0134] Figure 4 The illustration shows a signaling diagram of an example process 400 according to some embodiments of the present disclosure. Process 400 may involve UE 401, RAN node 402, AMF 403, SF 404, SMF 405, and UPF 406. It should be understood that process 400 can be considered as Figure 2 A more specific example of process 200.

[0135] In procedure 400, UE 401 sends a 417 sensing instruction to AMF 403. This can be triggered by three reasons. For one reason, SF 404 assigns a 411 sensing task to UE 401. SF 404 provides UE 401 with a sensing task ID, and may also provide UE 401 with sensing requests, user plane connection instructions, or user plane information, etc. For another reason, RAN node 402 assigns a 413 sensing task to UE 401. For example, RAN node 402 provides UE 401 with a sensing task ID. RAN node 402 may also provide UE 401 with sensing requests and instructions on sensing results directly to SF 404. It is assumed that UE 401 may have already negotiated with SF 404 to use a user plane connection to exchange sensing data. For yet another reason, the application on UE 401 assigns a 415 sensing task to UE 401. For example, the UE's application layer provides the sensing task ID to the UE's NAS layer, and the UE's application layer can also provide sensing requirements and user plane connection indications.

[0136] UE 401 can decide to use user plane connectivity for self-sensing, or be indicated by user plane connectivity indication, or be indicated by user plane information. There are two main options for establishing a user plane between UE 401 and SF 404.

[0137] In one option, the default PDU session is used for sensing. UE 401 sends a 417 sensing indication to AMF 403. The sensing indication can be a user plane sensing indication. Upon receiving the sensing indication, AMF 403 determines 419 the SF information associated with the UE (e.g., SF ID, IP address, or SF FQDN) based on the sensing indication. AMF 403 then provides 421 the UE ID (e.g., SUPI) and SF information to SMF 405. Alternatively, AMF 403 can also provide the sensing indication. In this case, the sensing indication is not transparent to the AMF.

[0138] In another option, it is assumed that a new PDU session should be established for sensing. If no existing PDU session exists for sensing, UE 401 triggers the PDU session establishment procedure. UE 401 checks 423 whether a PDU session has been established for sensing. The UE sends a 425 PDU session establishment request message and a sensing indication (or user plane sensing indication) to AMF 403. AMF 403 determines 427 SF information (e.g., SF ID, IP address, or FQDN of the SF) based on the sensing indication. AMF 403 sends a 429 PDU session establishment request message and SF information to the selected SMF 405. AMF may also provide a UE ID assigned by AMF or SF, such as AMF UE XAP ID or SF UE XAP ID. Alternatively, AMF 403 sends a SUPI along with the PDU session establishment request message. In this case, the sensing indication is not transparent to the AMF.

[0139] SMF 405 sends a Sensing Policy Association Establishment Request message 431 to SF 404, including the UE ID (e.g., SUPI, or AMF UE XAP ID, or SF UEXAP ID), which may also include a Sensing Task ID. If UE 404 provides a Sensing Task ID, the Sensing Task ID is present in the Sensing Policy Association Establishment Request message. SF identifies the UE by the UE ID. SF 404 sends a Sensing Policy Association Establishment Response message 433 to SMF 405, containing the UE ID and sensing policy information. Furthermore, the Sensing Policy Association Establishment Response message may include the Sensing Task ID. In another embodiment, SMF 405 may have sensing policy information pre-configured with a specific DNN or (DNN, S-NSSAI) by the Operation, Management and Maintenance (OAM) or Public Land Mobile Network (PLMN). SMF 405 can then determine the sensing policy information based on the DNN or (DNN, S-NSSAI) of the PDU session.

[0140] Upon receiving sensing policy information from SF 404, SMF 405 triggers the 435 N4 session establishment or N4 session modification procedure. During the N4 session establishment or modification procedure, SMF 405 provides PDR, QoS-related information (e.g., maximum bit rate of the service data stream, guaranteed stream bit rate, and guaranteed stream bit rate of the QoS stream), corresponding packet label information, and TNL information on the SF side. In response, UPF 406 can provide UPF-side TNL information to SMF 405. SMF 405 should then forward the UPF-side TNL information to SF 404, which is not shown in the figure. Alternatively, SMF 405 can instruct UPF 406 to provide both UPF-side TNL information by providing a bidirectional tunnel indication. UPF 406 then provides SMF 405 with UPF-side TNL information for RAN node 402 (for UL) and UPF-side TNL information for SF 404 (for DL). Then, accordingly, the TNL information for the UPF side of RAN node 402 (for UL) should be forwarded to RAN node 402, and the TNL information for the UPF side of SF 404 (for DL) should be forwarded to SF 404. If a direct user plane tunnel exists between RAN node 402 and SF 404 or SF-U, the N4 session establishment procedure or N4 session modification procedure will not be triggered.

[0141] SMF 405 provides RAN node 402 with 437 UE's NAS message, PDU session ID, (multiple) QFIs, QoS profile, sensing control information, etc. Upon receiving sensing control information from SMF 405, RAN node 402 determines sensing resources based on sensing mode and sensing requirements. RAN node 402 provides UE 401 with 439 associated sensing resources, and any one of the following: QFI, DRB ID, logical channel ID, or logical channel group ID.

[0142] Figure 5 The illustration shows a signaling diagram of an example process 500 according to some embodiments of the present disclosure. Process 500 may involve UE 501, RAN node 502, AMF 503, SF 504, SMF 505, PCF 506, UPF 507, and UDM 508. It should be understood that process 500 can be considered as... Figure 2 A more specific example of process 200.

[0143] In procedure 500, UE 501 checks whether a PDU session has been established for sensing, i.e., whether an existing sensing PDU session exists. This can be triggered by three reasons. For one reason, SF 504 assigns a sensing task (511) to UE 501. SF 504 provides a sensing task ID to UE 501, and SF 504 can also provide a sensing request to UE 501. For another reason, RAN node 502 assigns a sensing task (513) to UE 501. For example, RAN node 502 provides a sensing task ID to UE 501. RAN node 502 can also provide a sensing request to UE 501. It is assumed that UE 501 may have already negotiated with SF 504 to exchange sensing data using a user plane connection. For yet another reason, the application on UE 501 assigns a sensing task (515) to UE 501. For example, the UE's application layer provides a sensing task ID to the UE's NAS layer, and the UE's application layer can also provide a sensing request.

[0144] There are two main options for establishing a user plane between UE 501 and SF 504. In one option, the default PDU session is used for sensing. In this way, it is assumed that the default PDU session is established as usual. Whenever UE 501 is triggered by a sensing task, UE 501 provides 517, the sensing task ID or sensing indication, to SMF 505. In the other option, a PDU session is established specifically for sensing. UE 501 checks 519 whether a PDU session has been established for sensing. If no existing PDU session exists for sensing, UE 501 triggers the PDU session establishment procedure. UE 501 sends 521, the PDU session establishment request message, to AMF 503. The PDU session establishment request message includes the sensing task ID or sensing indication. AMF 503 forwards 523, the PDU session establishment request message, to the selected SMF 505. In this case, the sensing triggering information is transparent to the AMF.

[0145] After receiving the Sensing Task ID or Sensing Indicator contained in the PDU Session Establishment Request message from AMF 503 or UE 501, SMF 505 requests SF information. When requesting SF information, SMF 505 also sends the UE ID.

[0146] There are two options for requesting SF information. In one option, SMF 505 requests SF information 525 from AMF 503 by providing the UE ID. AMF 503 responds to SMF 505 with the SF information 527. AMF 503 also responds to SMF 505 with the UE ID. In the other option, SMF 505 requests SF information 529 from UDM 508 by providing the UE ID. UDM 508 responds to SF 504 with the UE ID and SF information 531.

[0147] SMF 505 triggers the SM policy association establishment process toward PCF 506 by providing the UE ID (e.g., SUPI), PDU session ID, and SF information. SMF 505 can also provide the sensing task ID to PCF 506. For example, SMF 505 sends a 533 SM policy association request message to PCF 506. The SM policy association request message includes the UE ID, PDU session ID, and SF information. The SM policy association request message may also include the sensing task ID. If UE 501 provides a sensing task identifier, the sensing task identifier is present in the SMF's message.

[0148] After receiving SF information from SMF 505, PCF 506 triggers a sensing policy association establishment process upon receiving the SF message. For example, PCF 506 sends a 535 sensing policy association establishment request message to SF 504, which includes the UE ID. The sensing policy association establishment request message may also include a sensing task ID. In another embodiment, PCF 506 may be pre-configured with sensing policy information for a specific DNN or (DNN, S-NSSAI) by OAM or PLMN. Then, PCF 506 can determine the sensing policy information based on the DNN or (DNN, S-NSSAI) of the PDU session provided by SMF 505.

[0149] SF 504 sends a Sensing Policy Association Establishment Response Message 537, containing UE ID and sensing policy information, to PCF 506. Alternatively, the Sensing Policy Association Establishment Response Message may include a Sensing Task ID. The Sensing Policy Information may include Sensing QoS Requirements, such as a QoS Reference for determining QoS parameters, individual QoS parameters, at least one Sensing Requirement, UE 501's User Plane Information (e.g., SF 504's User Plane Address and Security-Related Information), and TNL Information on the SF side. UE 501's User Plane Information may be provided to the UE in advance. Furthermore, the TNL Information on the SF side may be sent in separate signaling.

[0150] PCF 506 generates PCC rules based on the sensing policy information provided by SF 504. PCF 506 provides SMF 505 with QoS parameters 539, sensing control #1 (which may include sensing modes), UE user plane information, SF-side TNL information, etc. Furthermore, PCF 506 can also provide SMF 505 with at least one sensing requirement. Alternatively, UE 501's user plane information can be directly provided to UE 501 by PCF 506, for example, by being included in the UE policy container.

[0151] Upon receiving the PCC rule from PCF 506, SMF 505 triggers the 541 N4 session establishment or N4 session modification procedure. During the N4 session establishment or modification procedure, SMF 505 provides UPF 507 with PDR, QoS-related information (e.g., maximum bit rate of the service data stream, guaranteed stream bit rate, and maximum stream bit rate of the guaranteed stream bit rate QoS stream), corresponding packet label information, and TNL information from the SF side. In response, UPF 507 may provide SMF 505 with its own TNL information. SMF 505 should then forward the UPF-side TNL information to SF 504, which is not shown in the figure. Alternatively, SMF 505 can instruct UPF 507 to provide both UPF-side TNL information by providing a bidirectional tunnel indication. Then, UPF 507 provides SMF 505 with TNL information on the UPF side for RAN node 502 (for UL) and TNL information on the UPF side for SF 504 (for DL). Accordingly, the TNL information on the UPF side for RAN node 502 (for UL) should be forwarded to RAN node 502, and the TNL information on the UPF side for SF 504 (for DL) should be forwarded to SF 504. If a direct user plane tunnel exists between RAN node 502 and SF 504 or SF-U, the N4 session establishment procedure or N4 session modification procedure will not be triggered.

[0152] SMF 505 provides RAN node 502 with NAS messages, PDU session IDs, (multiple) QFIs, QoS profiles, Sensing Control #2, and TNL information from the SF side or UPF side for UE 543. Sensing Control #2 may include sensing task IDs and sensing modes, etc. Alternatively, Sensing Control #2 may also include at least one sensing requirement.

[0153] After receiving sensing control information from SMF 505, RAN node 502 determines sensing resources based on the sensing mode and sensing requirements. RAN node 502 provides UE 501 with the sensing resources associated with 545, and any one of the following: QFI, DRB ID, logical channel ID, or logical channel group ID. UE 501 then generates sensing measurement data by setting the target address to the user plane address of SF 504 (e.g., setting the target IP address to the IP address of SF 504). Furthermore, UE 501 encapsulates the sensing measurement data along with security-related information contained in the NAS message.

[0154] Figure 6 The illustration shows a signaling diagram of an example process 600 according to some embodiments of the present disclosure. Process 600 may involve UE 601, RAN node 602, AMF 603, SF 604, SMF 605, PCF 606, and UPF 607. It should be understood that process 600 can be considered as... Figure 2 A more specific example of process 200.

[0155] In procedure 600, UE 601 sends a 617 sensing instruction to AMF 603. This can be triggered by three reasons. For one reason, SF 604 assigns a 611 sensing task to UE 601. SF 604 provides a sensing task ID to UE 601, and may also provide sensing requirements, etc. For another reason, RAN node 602 assigns a 613 sensing task to UE 601. For yet another reason, an application on UE 601 assigns a 615 sensing task to UE 601. For example, the UE's application layer provides a sensing task ID to the UE's NAS layer, and may also provide sensing requirements and user plane connectivity indications.

[0156] UE 601 can decide to use a user plane connection for sensing on its own, or be instructed by a user plane connection indication. There are two main options for establishing a user plane connection between UE 601 and SF 604. In one option, the default PDU session is used for sensing. UE 601 sends a 617 sensing indication to AMF 603. The sensing indication can be a user plane sensing indication. Upon receiving the sensing indication, AMF 603 determines 619 the SF information associated with the UE (e.g., SF ID, IP address, or SF FQDN) based on the sensing indication. AMF 603 then provides 621 the UE ID (e.g., SUPI) and SF information to SMF 605. Alternatively, AMF 603 can also provide the sensing indication. In this case, the sensing indication is opaque to the AMF.

[0157] In another option, it is assumed that a new PDU session should be established for sensing. If no existing PDU session exists for sensing, UE 601 triggers the PDU session establishment procedure. UE 601 checks 623 whether a PDU session has been established for sensing. UE 601 sends a 625 PDU session establishment request message and a sensing indication (or user plane sensing indication) to AMF 603. AMF 603 determines 627 SF information (e.g., SF ID, IP address, or FQDN of the SF) based on the sensing indication. AMF 603 sends a 629 PDU session establishment request message and SF information to the selected SMF 605. AMF may also provide a UEID assigned by AMF or SF, such as the AMF UE XAP ID or the SF UE XAP ID. Alternatively, AMF 603 sends a SUPI along with the PDU session establishment request message. In this case, the sensing indication is not transparent to the AMF.

[0158] SMF 605 triggers the SM policy association establishment process toward PCF 606 by providing the UE ID, PDU session ID, and SF information. SMF 605 may also provide the PCF 606 with a sensing task ID. For example, SMF 605 sends a 631 SM policy association request message to PCF 606. After receiving the SF information from SMF 605, PCF 606 triggers the sensing policy association establishment process. For example, PCF 606 sends a 633 sensing policy association establishment request message to SF 604, which includes the UE ID. The sensing policy association establishment request message may also include the sensing task ID. In another embodiment, PCF 606 may be pre-configured by OAM or PLMN with sensing policy information for a specific DNN or (DNN, S-NSSAI). PCF 606 can then determine the sensing policy information based on the DNN or (DNN, S-NSSAI) of the PDU session provided by SMF 605.

[0159] SF 604 sends a Sensing Policy Association Establishment Response Message 635, containing the UE ID and sensing policy information, to PCF 606. Alternatively, the Sensing Policy Association Establishment Response Message may include a Sensing Task ID.

[0160] PCF 606 generates PCC rules based on the sensing policy information provided by SF 604. PCF 606 provides SMF 605 with QoS parameters 637, sensing control #1 (which may include sensing modes), UE user plane information, SF-side TNL information, etc. Furthermore, PCF 606 can also provide SMF 605 with at least one sensing requirement. Alternatively, UE 601's user plane information can be directly provided to UE 601 by PCF 606, for example, by being included in the UE policy container.

[0161] Upon receiving the PCC rule from PCF 606, SMF 605 triggers the 639 N4 session establishment or N4 session modification procedure. During the N4 session establishment or modification procedure, SMF 605 provides UPF 607 with PDR, QoS-related information (e.g., maximum bit rate of the service data stream, guaranteed stream bit rate, and guaranteed stream bit rate QoS stream maximum stream bit rate), corresponding packet labeling information on the SF side, and TNL information. In response, UPF 607 can provide SMF 605 with UPF-side TNL information. SMF 605 should later forward the UPF-side TNL information to SF 604, which is not shown in the figure. Alternatively, SMF 605 can instruct UPF 607 to provide both UPF-side TNL information by providing a bidirectional tunnel indication. UPF 607 then provides SMF 605 with UPF-side TNL information for RAN node 602 (for UL) and UPF-side TNL information for SF 604 (for DL). Then, correspondingly, the TNL information for the UPF side of RAN node 602 (for UL) should be forwarded to RAN node 602, and the TNL information for the UPF side of SF 604 (for DL) should be forwarded to SF 604. If a direct user plane tunnel exists between RAN node 602 and SF 604 or SF-U, the N4 session establishment procedure or N4 session modification procedure will not be triggered.

[0162] SMF 605 provides RAN node 602 with 641 UE NAS messages, PDU session ID, (multiple) QFIs, QoS profiles, Sensing Control #2, and TNL information from the SF side or UPF side. Upon receiving sensing control information from SMF 605, RAN node 602 determines sensing resources based on the sensing mode and sensing requirements. RAN node 602 provides UE 601 with 643 associated sensing resources, and any one of the following: QFI, DRB ID, logical channel ID, or logical channel group ID. UE 601 then generates sensing measurement data by setting the target address to the user plane address of SF 604 (e.g., setting the target IP address to the IP address of SF 604). Furthermore, UE 601 encapsulates the sensing measurement data together with security-related information contained in the NAS message.

[0163] Figure 7 The illustration shows a signaling diagram of an example process 700 according to some embodiments of the present disclosure. Process 700 may involve UE 701, RAN node 702, AMF 703, SF 704, and UDM 705. It should be understood that process 700 can be considered as Figure 2 A more specific example of process 200.

[0164] Assume that after UE 701 performs registration with AMF 703, UE 701 performs sensing registration with SF 704 via AMF 703.

[0165] In procedure 700, UE 701 sends a 711 UL NAS message to AMF 703. This UL NAS message contains the UE ID and a sensing registration request message. The UE ID can be SUPI, GPSI, 5G-GUTI, 5G-S-TMSI, etc. Taking SUPI as the UE ID as an example, assume a new payload container type is defined for the UL NAS message, such as a sensing message container. Assume the UE includes sensing capability information in the sensing registration request, including supported sensing modes, supported sensing accuracy, confidence level, sensing resolution, false alarm probability, missed detection probability, refresh rate, maximum sensing service latency, user plane connectivity support indicator (or CP / UP support indicator), Tx / Rx support indicator, non-3GPP sensing support indicator, etc. The Tx / Rx support indicator indicates whether the UE can operate as a sensing Tx, sensing Rx, or both. The CP / UP support indicator indicates whether the UE supports CP-based sensing measurement reporting, UP-based sensing measurement reporting, or both. Specifically, the sensing modes include, for example, sensing mode 1: the RAN node performs both transmitting and receiving; sensing mode 2: RAN node A performs transmitting and RAN node B performs receiving; sensing mode 3: the UE performs transmitting and the RAN node performs receiving; sensing mode 4: UE A performs transmitting and UE B performs receiving; and sensing mode 5: the RAN node performs transmitting and the UE performs receiving. Furthermore, the UE may include its UEID in the sensing registration message.

[0166] Upon receiving the UL NAS message, AMF 703 determines that the container contains sensing messages based on the payload container type. Then, AMF selects a 713 SF based on factors such as UE location and SF payload. It is assumed that AMF is already configured with SF information (e.g., via OAM or PLMN), such as SF ID, SF IP address or FQDN, and SF service area. Alternatively, it is assumed that SF 704 registers with NEF by certifying its SF information. AMF 703 can request SF information from NEF. NEF will check the service area of ​​AMF 703 and find at least one corresponding SF. NEF will then provide the SF information to AMF 703.

[0167] AMF 703 sends a 715 Sensing Registration Request message to the selected SF 704. In this way, SF 704 can identify the sensing UE located in its service area. It is assumed that an X interface exists between AMF 703 and SF 704. AMF 703 assigns an AMF UE XAP ID to the UE to identify the UE via the X interface. In this way, AMF can send the UE ID (e.g., AMF UE XAP ID) and the Sensing Registration Request message to SF. Furthermore, SF obtains the UE ID (e.g., SUPI) from the Sensing Registration Request message. When SF 704 receives a sensing task, SF 704 can select the appropriate sensing UE based on the sensing capability information provided by the UE during the sensing registration process.

[0168] Then, SF 704 sends a 717 Sensing Registration Response message to AMF 703. Upon receiving the AMF UE XAP ID, SF 704 can also assign an SF UE XAP ID to the UE. That is, SF 704 provides the AMF with the AMF UE XAP ID and SF UEXAP ID (optional), along with the Sensing Registration Response message. Alternatively, SF 704 provides the UE ID (e.g., SUPI) and the Sensing Registration Response message to AMF 703. AMF 703 forwards a 719 Sensing Registration Response message to UE 701 based on the UE ID (e.g., SUPI, AMF UE XAP ID, SF UE XAP ID). SF 704 can also provide UDM 705 with a 721 UE ID (e.g., SUPI) and SF information (e.g., SF ID, IP address, or SF FQDN). UDM 705 then reserves a UE context containing the UE ID and SF information. In some embodiments, SF 704 may provide UEID and SF information to UDM 705 before providing UE ID and SF information to AMF 703.

[0169] The SMF selects the PCF used to generate the SM policy for the PDU session. For sensing PDU sessions, the AMF has already selected the SF during the sensing registration process. However, the selected PCF is unaware of the SF. Alternatively, the SF can be considered to provide the sensing policy directly to the SMF. Therefore, this solution primarily offers two options: one is that the sensing policy comes directly from the SF (e.g., processes 300 and 400), and the other is that the sensing policy comes from the PCF (e.g., processes 500 and 600). It should be understood that... Figures 3 to 7 Each part of the content in a process can be used individually or in combination. Figures 3 to 7 The contents of other processes can be used in any combination.

[0170] Figure 8An example of a device 800 supporting sense data exchange according to various aspects of this disclosure is illustrated. Device 800 may be an example of an SMF 120 as described herein. Device 800 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 800 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 802, memory 804, transceiver 806, and optional I / O controller 808). These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0171] Processor 802, memory 804, transceiver 806, or various combinations thereof, or various components thereof, may be examples of components used to perform the various aspects of this disclosure described herein. For example, processor 802, memory 804, transceiver 806, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0172] In some implementations, processor 802, memory 804, transceiver 806, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 802 and memory 804 coupled to processor 802 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 804 by processor 802).

[0173] For example, according to the examples disclosed herein, processor 802 may support wireless communication at device 800. Processor 802 may be configured to operate to support components for: receiving, via a transceiver, sensing trigger information for a sensing protocol data unit (PDU) session for a terminal device; and sending, via a transceiver, a request for sensing policy information associated with a sensing PDU session for the terminal device to a network function. Processor 802 may also be configured to operate to support components for: Figure 2 Other components that perform the actions described in the text.

[0174] Processor 802 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 802 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 802. Processor 802 may be configured to execute computer-readable instructions stored in memory (e.g., memory 804) to cause device 800 to perform various functions of this disclosure.

[0175] Memory 804 may include random access memory (RAM) and read-only memory (ROM). Memory 804 may store computer-readable, computer-executable code, including instructions that, when executed by processor 802, cause device 800 to perform the 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. In some implementations, the code may not be directly executed by processor 802, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 804 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0176] I / O controller 808 can manage the input and output signals of device 800. I / O controller 808 can also manage peripheral devices not integrated into device 800. In some implementations, I / O controller 808 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 808 can utilize an operating system such as iOS®, Android®, MS Windows®, OS / 2®, UNIX®, Linux®, or other known operating systems. In some implementations, I / O controller 808 can be implemented as part of a processor, such as processor 802. In some implementations, a user can interact with device 800 via I / O controller 808 or via hardware components controlled by I / O controller 808.

[0177] In some implementations, device 800 may include a single antenna 810. However, in other implementations, device 800 may have more than one antenna 810 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 806 may communicate bidirectionally via one or more antennas 810, wired or wireless links, as described herein. For example, transceiver 806 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 806 may also include a modem for modulating packets, providing modulated packets to one or more antennas 810 for transmission, and demodulating packets received from one or more antennas 810. Transceiver 806 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0178] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 810 for transmitting the amplified signal into the air or wireless medium.

[0179] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 810 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0180] Figure 9An example of a device 900 supporting sense data exchange according to various aspects of this disclosure is illustrated. Device 900 may be an example of an AMF 130 as described herein. Device 900 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 900 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 902, memory 904, transceiver 906, and optional I / O controller 908). These components may communicate electronically or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0181] Processor 902, memory 904, transceiver 906, or various combinations thereof, or various components thereof, may be examples of components used to perform the various aspects of this disclosure described herein. For example, processor 902, memory 904, transceiver 906, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0182] In some implementations, processor 902, memory 904, transceiver 906, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 902 and memory 904 coupled to processor 902 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 904 by processor 902).

[0183] For example, according to the examples disclosed herein, processor 902 can support wireless communication at device 900. Processor 902 can be configured to operate to support components for: determining sensing function (SF) information associated with a sensing protocol data unit (PDU) session for a terminal device; and transmitting SF information to a session management function (SMF) via a transceiver. Processor 902 can also be configured to operate to support components for... Figure 2 Other components that perform the actions described in the text.

[0184] Processor 902 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 902 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 902. Processor 902 may be configured to execute computer-readable instructions stored in memory (e.g., memory 904) to cause device 900 to perform various functions of this disclosure.

[0185] Memory 904 may include random access memory (RAM) and read-only memory (ROM). Memory 904 may store computer-readable, computer-executable code, including instructions that, when executed by processor 902, cause device 900 to perform the 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. In some implementations, the code may not be directly executed by processor 902, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 904 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0186] I / O controller 908 can manage the input and output signals of device 900. I / O controller 908 can also manage peripheral devices not integrated into device 900. In some implementations, I / O controller 908 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 908 can utilize an operating system such as iOS®, Android®, MS Windows®, OS / 2®, UNIX®, Linux®, or other known operating systems. In some implementations, I / O controller 908 can be implemented as part of a processor, such as processor 902. In some implementations, a user can interact with device 900 via I / O controller 908 or via hardware components controlled by I / O controller 908.

[0187] In some implementations, device 900 may include a single antenna 910. However, in other implementations, device 900 may have more than one antenna 910 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 906 may communicate bidirectionally via one or more antennas 910, wired or wireless links, as described herein. For example, transceiver 906 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 906 may also include a modem for modulating packets, providing modulated packets to one or more antennas 910 for transmission, and demodulating packets received from one or more antennas 910. Transceiver 906 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0188] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 910 for transmitting the amplified signal into the air or wireless medium.

[0189] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 910 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0190] Figure 10An example of a device 1000 supporting sensing data exchange according to various aspects of this disclosure is illustrated. Device 1000 may be an example of an SF as described herein. Device 1000 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 1000 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 1002, memory 1004, transceiver 1006, and optional I / O controller 1008). These components may communicate electronically or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0191] Processor 1002, memory 1004, transceiver 1006, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the present disclosure described herein. For example, processor 1002, memory 1004, transceiver 1006, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0192] In some implementations, processor 1002, memory 1004, transceiver 1006, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 1002 and memory 1004 coupled to processor 1002 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 1004 by processor 1002).

[0193] For example, according to the examples disclosed herein, processor 1002 may support wireless communication at device 1000. Processor 1002 may be configured to operate to support components for: receiving, via a transceiver, a request for sensing policy information associated with a sensing protocol data unit (PDU) session from a second network device, wherein the sensing policy information includes an identifier (ID) of a terminal device associated with the sensing PDU session; and transmitting the sensing policy information to the second network device via a transceiver. Processor 1002 may also be configured to support components for: Figure 2 Other components that perform the actions described in the text.

[0194] Processor 1002 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 1002 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 1002. Processor 1002 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1004) to cause device 1000 to perform various functions of this disclosure.

[0195] Memory 1004 may include random access memory (RAM) and read-only memory (ROM). Memory 1004 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1002, cause device 1000 to perform the 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. In some implementations, the code may not be directly executed by processor 1002, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 1004 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0196] I / O controller 1008 can manage the input and output signals of device 1000. I / O controller 1008 can also manage peripheral devices not integrated into device 1000. In some implementations, I / O controller 1008 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 1008 can utilize an operating system such as iOS®, Android®, MS Windows®, OS / 2®, UNIX®, Linux®, or other known operating systems. In some implementations, I / O controller 1008 can be implemented as part of a processor, such as processor 1002. In some implementations, a user can interact with device 1000 via I / O controller 1008 or via hardware components controlled by I / O controller 1008.

[0197] In some implementations, device 1000 may include a single antenna 1010. However, in other implementations, device 1000 may have more than one antenna 1010 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1006 may communicate bidirectionally via one or more antennas 1010, wired or wireless links, as described herein. For example, transceiver 1006 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1006 may also include a modem for modulating packets, providing modulated packets to one or more antennas 1010 for transmission, and demodulating packets received from one or more antennas 1010. Transceiver 1006 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0198] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 1010 for transmitting the amplified signal into the air or wireless medium.

[0199] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 1010 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0200] Figure 11An example of a device 1100 supporting sense data exchange according to various aspects of this disclosure is illustrated. Device 1100 may be an example of a UE 104 as described herein. Device 1100 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 1100 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 1102, memory 1104, transceiver 1106, and optional I / O controller 1108). These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0201] Processor 1102, memory 1104, transceiver 1106, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the present disclosure described herein. For example, processor 1102, memory 1104, transceiver 1106, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0202] In some implementations, processor 1102, memory 1104, transceiver 1106, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 1102 and memory 1104 coupled to processor 1102 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 1104 by processor 1102).

[0203] For example, according to the examples disclosed herein, processor 1102 may support wireless communication at device 1100. Processor 1102 may be configured to operate to support components for: determining to establish a user plane connection with a sensing function (SF); and transmitting sensing trigger information associated with a sensing protocol data unit (PDU) session to a network function via a transceiver. Processor 1102 may also be configured to operate to support components for... Figure 2 Other components that perform the actions described in the text.

[0204] Processor 1102 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 1102 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 1102. Processor 1102 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1104) to cause device 1100 to perform various functions of this disclosure.

[0205] Memory 1104 may include random access memory (RAM) and read-only memory (ROM). Memory 1104 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1102, cause device 1100 to perform the 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. In some implementations, the code may not be directly executed by processor 1102, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 1104 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0206] I / O controller 1108 can manage the input and output signals of device 1100. I / O controller 1108 can also manage peripheral devices not integrated into device 1100. In some implementations, I / O controller 1108 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 1108 can utilize an operating system such as iOS®, Android®, MS Windows®, OS / 2®, UNIX®, LINUX®, or other known operating systems. In some implementations, I / O controller 1108 can be implemented as part of a processor, such as processor 1102. In some implementations, a user can interact with device 1100 via I / O controller 1108 or via hardware components controlled by I / O controller 1108.

[0207] In some implementations, device 1100 may include a single antenna 1110. However, in other implementations, device 1100 may have more than one antenna 1110 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1106 may communicate bidirectionally via one or more antennas 1110, wired or wireless links, as described herein. For example, transceiver 1106 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1106 may also include a modem for modulating packets, providing modulated packets to one or more antennas 1110 for transmission, and demodulating packets received from one or more antennas 1110. Transceiver 1106 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0208] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. At least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 1110 for transmitting the amplified signal into the air or wireless medium.

[0209] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 1110 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0210] Figure 12An example of a processor 1200 supporting sense data exchange according to various aspects of this disclosure is illustrated. Processor 1200 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 1200 may include a controller 1202 configured to perform various operations according to the examples described herein. Processor 1200 may optionally include at least one memory 1204, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 1200 may optionally include one or more arithmetic logic units (ALUs) 1206. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0211] Processor 1200 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset or included in the processor chipset (e.g., processor 1200)) 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), etc.).

[0212] Controller 1202 can be configured to manage and coordinate various operations of processor 1200 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 1200 to support various operations according to the examples described herein. For example, controller 1202 can operate as a control unit of processor 1200 to generate control signals for managing the operation of various components of processor 1200. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0213] Controller 1202 can be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 1204 and determine subsequent instructions(s) to be executed, enabling processor 1200 to support various operations according to the examples described herein. Controller 1202 can be configured to track the memory addresses of instructions associated with memory 1204. Controller 1202 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 1202 can be configured to interpret instructions and determine control signals to be output to other components of processor 1200, enabling processor 1200 to support various operations according to the examples described herein. Additionally or alternatively, controller 1202 can be configured to manage data flow within processor 1200. Controller 1202 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 1200.

[0214] Memory 1204 may include one or more caches (e.g., memory or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc., local to or included in processor 1200). In some implementations, memory 1204 may reside within or on the processor chipset (e.g., local to processor 1200). In some other implementations, memory 1204 may reside outside the processor chipset (e.g., remote from processor 1200).

[0215] Memory 1204 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1200, cause processor 1200 to perform the 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. Controller 1202 and / or processor 1200 may be configured to execute computer-readable instructions stored in memory 1204 to cause processor 1200 to perform various functions. For example, processor 1200 and / or controller 1202 may be coupled to or coupled to memory 1204, and processor 1200, controller 1202, and memory 1204 may be configured to perform the various functions described herein. In some examples, processor 1200 may include multiple processors, and memory 1204 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0216] One or more ALU 1206s can be configured to support a variety of operations as described in the examples herein. In some implementations, one or more ALU 1206s may reside within or on a processor chipset (e.g., processor 1200). In some other implementations, one or more ALU 1206s may reside outside the processor chipset (e.g., processor 1206). One or more ALU 1206s can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 1206s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 1206s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU 1206 may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 1206 to handle conditional operations, comparisons, and bitwise operations.

[0217] Based on the examples disclosed herein, processor 1200 can support wireless communication. Processor 1200 can be configured or operable to support components for: receiving, via a transceiver, sensing trigger information for a sensing protocol data unit (PDU) session of a terminal device for use with the terminal device; and sending, via a transceiver, a request for sensing policy information associated with a sensing PDU session of the terminal device to a network function. Processor 1202 can also be configured to support components for: Figure 2 Other components that perform the actions described in the text.

[0218] Figure 13 An example of a processor 1300 supporting sense data exchange according to various aspects of this disclosure is illustrated. Processor 1300 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 1300 may include a controller 1302 configured to perform various operations according to the examples described herein. Processor 1300 may optionally include at least one memory 1304, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 1300 may optionally include one or more arithmetic logic units (ALUs) 1306. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0219] Processor 1300 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset or included in the processor chipset (e.g., processor 1300)) 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), etc.).

[0220] Controller 1302 can be configured to manage and coordinate various operations of processor 1300 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 1300 to support various operations according to the examples described herein. For example, controller 1302 can operate as a control unit of processor 1300 to generate control signals for managing the operation of various components of processor 1300. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0221] Controller 1302 can be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 1304 and determine subsequent instructions(s) to be executed, enabling processor 1300 to support various operations according to the examples described herein. Controller 1302 can be configured to track the memory addresses of instructions associated with memory 1304. Controller 1302 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 1302 can be configured to interpret instructions and determine control signals to be output to other components of processor 1300, enabling processor 1300 to support various operations according to the examples described herein. Additionally or alternatively, controller 1302 can be configured to manage data flow within processor 1300. Controller 1302 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 1300.

[0222] Memory 1304 may include one or more caches (e.g., memory local to or included in processor 1300, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, memory 1304 may reside within or on the processor chipset (e.g., locally to processor 1300). In some other implementations, memory 1304 may reside outside the processor chipset (e.g., remotely from processor 1300).

[0223] Memory 1304 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1300, cause processor 1300 to perform the 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. Controller 1302 and / or processor 1300 may be configured to execute computer-readable instructions stored in memory 1304 to cause processor 1300 to perform various functions. For example, processor 1300 and / or controller 1302 may be coupled to or coupled to memory 1304, and processor 1300, controller 1302, and memory 1304 may be configured to perform the various functions described herein. In some examples, processor 1300 may include multiple processors, and memory 1304 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0224] One or more ALU 1306s can be configured to support a variety of operations as described in the examples herein. In some implementations, one or more ALU 1306s may reside within or on a processor chipset (e.g., processor 1300). In some other implementations, one or more ALU 1306s may reside outside the processor chipset (e.g., processor 1306). One or more ALU 1306s can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 1306s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 1306s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU 1306 may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 1306 to handle conditional operations, comparisons, and bitwise operations.

[0225] Based on the examples disclosed herein, processor 1300 can support wireless communication. Processor 1300 can be configured or operable to support components for: determining sensing function (SF) information associated with a sensing protocol data unit (PDU) session of a terminal device; and transmitting SF information to a session management function (SMF) via a transceiver. Processor 1302 can also be configured to support components for... Figure 2 Other components that perform the actions described in the text.

[0226] Figure 14 An example of a processor 1400 supporting sense data exchange according to various aspects of this disclosure is illustrated. Processor 1400 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 1400 may include a controller 1402 configured to perform various operations according to the examples described herein. Processor 1400 may optionally include at least one memory 1404, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 1400 may optionally include one or more arithmetic logic units (ALUs) 1406. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0227] Processor 1400 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset or included in the processor chipset (e.g., processor 1400)) 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), etc.).

[0228] Controller 1402 can be configured to manage and coordinate various operations of processor 1400 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 1400 to support various operations according to the examples described herein. For example, controller 1402 can operate as a control unit of processor 1400 to generate control signals for managing the operation of various components of processor 1400. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0229] Controller 1402 can be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 1404 and determine subsequent instructions(s) to be executed, enabling processor 1400 to support various operations according to the examples described herein. Controller 1402 can be configured to track the memory addresses of instructions associated with memory 1404. Controller 1402 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 1402 can be configured to interpret instructions and determine control signals to be output to other components of processor 1400, enabling processor 1400 to support various operations according to the examples described herein. Additionally or alternatively, controller 1402 can be configured to manage data flow within processor 1400. Controller 1402 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 1400.

[0230] Memory 1404 may include one or more caches (e.g., memory or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc., native to or included in processor 1400). In some implementations, memory 1404 may reside within or on the processor chipset (e.g., native to processor 1400). In some other implementations, memory 1404 may reside external to the processor chipset (e.g., remote from processor 1400).

[0231] Memory 1404 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1400, cause processor 1400 to perform the 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. Controller 1402 and / or processor 1400 may be configured to execute computer-readable instructions stored in memory 1404 to cause processor 1400 to perform various functions. For example, processor 1400 and / or controller 1402 may be coupled to or coupled to memory 1404, and processor 1400, controller 1402, and memory 1404 may be configured to perform the various functions described herein. In some examples, processor 1400 may include multiple processors, and memory 1404 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0232] One or more ALU 1406s can be configured to support a variety of operations as described in the examples herein. In some implementations, one or more ALU 1406s may reside within or on a processor chipset (e.g., processor 1400). In some other implementations, one or more ALU 1406s may reside outside the processor chipset (e.g., processor 1406). One or more ALU 1406s can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 1406s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 1406s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU 1406 may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 1406 to handle conditional operations, comparisons, and bitwise operations.

[0233] Based on the examples disclosed herein, processor 1400 can support wireless communication. Processor 1400 can be configured or operable to support components for: receiving, via a transceiver, a request for sensing policy information associated with a sensing protocol data unit (PDU) session from a second network device, wherein the sensing policy information includes an identifier (ID) of a terminal device associated with the sensing PDU session; and transmitting the sensing policy information to the second network device via a transceiver. Processor 1402 can also be configured to support components for: Figure 2 Other components that perform the actions described in the text.

[0234] Figure 15 An example of a processor 1500 supporting sense data exchange according to various aspects of this disclosure is illustrated. Processor 1500 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 1500 may include a controller 1502 configured to perform various operations according to the examples described herein. Processor 1500 may optionally include at least one memory 1504, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 1500 may optionally include one or more arithmetic logic units (ALUs) 1506. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0235] Processor 1500 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset or included in the processor chipset (e.g., processor 1500)) 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), etc.).

[0236] Controller 1502 can be configured to manage and coordinate various operations of processor 1500 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 1500 to support various operations according to the examples described herein. For example, controller 1502 can operate as a control unit of processor 1500 to generate control signals for managing the operation of various components of processor 1500. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0237] Controller 1502 can be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 1504 and determine subsequent instructions(s) to be executed, enabling processor 1500 to support various operations according to the examples described herein. Controller 1502 can be configured to track the memory addresses of instructions associated with memory 1504. Controller 1502 can be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 1502 can be configured to interpret instructions and determine control signals to be output to other components of processor 1500, enabling processor 1500 to support various operations according to the examples described herein. Additionally or alternatively, controller 1502 can be configured to manage data flow within processor 1500. Controller 1502 can be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 1500.

[0238] Memory 1504 may include one or more caches (e.g., memory or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc., local to or included in processor 1500). In some implementations, memory 1504 may reside within or on the processor chipset (e.g., local to processor 1500). In some other implementations, memory 1504 may reside outside the processor chipset (e.g., remote from processor 1500).

[0239] Memory 1504 may store computer-readable, computer-executable code, including instructions that, when executed by processor 1500, cause processor 1500 to perform the 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. Controller 1502 and / or processor 1500 may be configured to execute computer-readable instructions stored in memory 1504 to cause processor 1500 to perform various functions. For example, processor 1500 and / or controller 1502 may be coupled to or connected to memory 1504, and processor 1500, controller 1502, and memory 1504 may be configured to perform the various functions described herein. In some examples, processor 1500 may include multiple processors, and memory 1504 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0240] One or more ALU 1506s can be configured to support a variety of operations as described in the examples herein. In some implementations, one or more ALU 1506s may reside within or on a processor chipset (e.g., processor 1500). In some other implementations, one or more ALU 1506s may reside outside the processor chipset (e.g., processor 1500). One or more ALU 1506s can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 1506s can receive input operands and an opcode that determines the operation to be performed. One or more ALU 1506s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU 1506s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 1506s to handle conditional operations, comparisons, and bitwise operations.

[0241] Based on the examples disclosed herein, processor 1500 can support wireless communication. Processor 1500 can be configured or operable to support components for: determining sensing function (SF) information associated with a sensing protocol data unit (PDU) session of a terminal device; and transmitting SF information to a session management function (SMF) via a transceiver. Processor 1502 can also be configured to support components for... Figure 2 Other components that perform the actions described in the text.

[0242] Figure 16 A flowchart illustrating a method 1600 supporting sense data exchange according to various aspects of this disclosure is shown. Operation of method 1600 can be implemented by the device or components thereof described herein. For example, operation of method 1600 can be performed by the SMF 120 described herein. In some implementations, the device can execute an instruction set to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the described functions.

[0243] At 1605, the method includes receiving sensing trigger information for a sensing PDU session for a terminal device via a transceiver. The operation of 1605 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1605 can be performed by the device described with reference to FIG1.

[0244] At 1610, the method includes sending a request for sensing policy information to a network function via a transceiver, the sensing policy information being associated with a sensing PDU session for a terminal device. The operation of 1610 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1610 can be derived from references... Figure 1A The aforementioned device is used to perform this action.

[0245] In some embodiments, the sensing trigger information may include one of the following: a sensing indication; or a sensing task identifier (ID). In some embodiments, the network function may be a sensing function (SF), and the request may include one of the following: the ID of the terminal device; or the ID of the terminal device and the sensing task ID.

[0246] In some embodiments, the network function may be a policy control function (PCF), and the request may include one of the following: the ID of the terminal device and SF information associated with the terminal device; or the ID of the terminal device, SF information, and sensing task ID.

[0247] In some embodiments, SF information can be received from the Access and Mobility Management Function (AMF) via a transceiver through a request for SF information, wherein the request includes the ID of the terminal device.

[0248] In some embodiments, the method may further include sending a request for SF information associated with a terminal device to a unified data management (UDM) via a transceiver, wherein the request includes the ID of the terminal device; and receiving the SF information associated with the terminal device from the UDM via the transceiver.

[0249] In some embodiments, SF information may include one of the following: the SF's ID, the SF's Internet Protocol (IP) address, or the SF's Fully Qualified Domain Name (FQDN).

[0250] In some embodiments, the method may further include being configured to receive sensing trigger information via: receiving sensing trigger information from a terminal device via an uplink (UL) message via a transceiver; receiving sensing trigger information from a terminal device via a transceiver via an establishment request for a sensing PDU session; or receiving sensing trigger information and SF information associated with the terminal device from an AMF via a transceiver.

[0251] In some embodiments, the method may further include receiving a response to sensing policy information from the SF via a transceiver, wherein the response includes sensing policy information associated with a sensing PDU session of the terminal device.

[0252] In some embodiments, the response may further include a sensing task ID. In some implementations, the method may also include receiving a response from the PCF via a transceiver, including sensing control information associated with sensing policy information.

[0253] In some embodiments, the sensing policy information may include one of the following: at least one QoS parameter, at least one sensing requirement, user plane information of the terminal device, or transport network layer (TNL) information at the SF.

[0254] In some embodiments, the method may further include sending a trigger message for an N4 session establishment procedure or an N4 session modification procedure to the User Plane Function (UPF) via a transceiver, wherein the trigger message includes a bidirectional tunnel indication; and receiving TNL information for the Radio Access Network (RAN) node and TNL information for the SF at the UPF from the UPF via the transceiver.

[0255] In some embodiments, the method may further include sending the ID of the sensing PDU session, TNL information at the SF or TNL information at the UPF, and second sensing control information to the RAN node via a transceiver.

[0256] In some embodiments, the first sensing control information and the second sensing control information may include one of the following: a sensing task ID and a sensing mode of the terminal device; or a sensing task ID, a sensing mode of the terminal device, and at least one sensing requirement.

[0257] Figure 17 A flowchart illustrating a method 1700 supporting sensing data exchange according to various aspects of this disclosure is shown. Operation of method 1700 can be implemented by the device or components thereof described herein. For example, operation of method 1700 can be performed by an AMF 130 as described herein. In some implementations, the device can execute an instruction set to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the described functions.

[0258] At 1705, the method includes determining SF information associated with a sensing PDU session for a terminal device. The operation of 1705 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1705 can be derived from references... Figure 1A The aforementioned device is used to perform this action.

[0259] At 1710, the method includes sending SF information to the SMF via a transceiver. The operation of 1710 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1710 can be found in the references. Figure 1A The aforementioned device is used to perform this action.

[0260] In some embodiments, the method may further include: receiving a sensing indication from a terminal device via a transceiver for determining SF information for the terminal device before determining SF information.

[0261] In some embodiments, the method may further include: receiving a sensing indication for determining the SF information and a request to establish a Sensing Protocol Data Unit (PDU) session from a terminal device via a transceiver before determining the SF information, wherein the SF information is sent to the SMF together with the establishment request.

[0262] In some embodiments, the method may further include determining SF information by: determining SF information based on sensing indications.

[0263] In some embodiments, the method may further include: receiving a request for SF information from a Session Management Function (SMF) via a transceiver before determining SF information, wherein the request includes the ID of the terminal device.

[0264] In some embodiments, the method may further include receiving a sensing registration request from a terminal device via a transceiver; selecting a sensing function (SF) for the terminal device; and sending a sensing registration request to the selected SF via the transceiver.

[0265] In some embodiments, a sensing registration request may include information about sensing capabilities and the ID of the terminal device.

[0266] Figure 18 A flowchart illustrating a method 1800 supporting sensing data exchange according to various aspects of this disclosure is shown. Operation of method 1800 can be implemented by the device or components thereof described herein. For example, operation of method 1800 can be performed by an SF 140 as described herein. In some implementations, the device can execute an instruction set to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the described functions.

[0267] At 1805, the method includes receiving a request for sensing policy information associated with a sensing PDU session from a second network device via a transceiver, wherein the request includes the ID of the terminal device associated with the sensing PDU session. The operation of 1805 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1805 can be derived from references... Figure 1A The aforementioned device is used to perform this action.

[0268] At 1810, the method includes sending sensing policy information to a second network device via a transceiver. The operation of 1810 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1810 can be found in the references... Figure 1A The aforementioned device is used to perform this action.

[0269] In some embodiments, the request may also include a sensing task ID. In some implementations, the second network device may include a session management function (SMF) and a policy control function (PCF).

[0270] In some embodiments, the method may further include receiving a sensing registration request from a terminal device via a transceiver from an Access and Mobility Management Function (AMF).

[0271] In some embodiments, the method may further include sending sensing function (SF) information associated with the terminal device to the Unified Data Management (UDM) via a transceiver.

[0272] In some embodiments, the method may further include assigning a sensing task to a terminal device by sending one of the following to the terminal device via a transceiver: a sensing task ID, at least one sensing request, and a user plane connection indication; or a sensing task ID, at least one sensing request, a user plane connection indication, and user plane information.

[0273] Figure 19 A flowchart illustrating a method 1900 supporting sense data exchange according to various aspects of this disclosure is shown. Operation of method 1900 can be implemented by the device or components thereof described herein. For example, operation of method 1900 can be performed by UE 104, as described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions.

[0274] At point 1905, the method includes determining to establish a user plane connection with SF. The operation at point 1905 can be performed according to the examples described herein. In some implementations, aspects of the operation at point 1905 can be found in the references... Figure 1A The aforementioned device is used to perform this action.

[0275] At 1910, the method includes sending sensing trigger information associated with the sensing PDU session to the network function via a transceiver. The operation of 1910 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1910 can be found in the references. Figure 1A The aforementioned device is used to perform this action.

[0276] In some embodiments, the network function may be a session management function (SMF), and the sensing trigger information may include one of the following: a sensing indication; or a sensing task identifier (ID).

[0277] In some embodiments, the network function may be an access and mobility management function (AMF), and the sensing trigger information may include one of the following: a sensing indication; or a sensing task identifier (ID).

[0278] In some embodiments, the sensing trigger information may be sent together with a request to establish a sensing PDU session.

[0279] In some embodiments, the method may further include being configured to determine to establish a user plane connection with the SF by: determining to establish a user plane connection with the SF based on sensing task information received from the SF; determining to establish a user plane connection with the SF based on sensing task information received from a radio access network (RAN) node; or determining to establish a user plane connection with the SF based on sensing task information received from an application on a terminal device.

[0280] In some embodiments, the sensing task information may include one of the following: a sensing task ID, at least one sensing requirement, a user plane connection indication, user plane information, or an indication to provide sensing results directly to the SF.

[0281] In some embodiments, the method may further include receiving UE routing policy (URSP) rules for sensing from the PCF via a transceiver; and determining at least one attribute of the sensing PDU session based on the rules, wherein the at least one attribute includes the PDU session and service continuity (SSC) mode, the type of PDU session, network slice, data network name (DNN), and access type.

[0282] In some embodiments, the method may further include sending a sensing registration request to the AMF via a transceiver, so that the AMF sends a sensing registration request to the SF; and receiving a sensing registration response from the AMF via a transceiver, wherein the AMF receives the sensing registration response from the SF.

[0283] In some embodiments, the method may further include receiving, via a transceiver, one of the following from a radio access network (RAN) node: user plane information of the terminal device; Quality of Service (QoS) Flow Identifier (QFI); Data Radio Bearer (DRB) ID; Logical Channel ID; Logical Channel Group ID; or at least one sensing resource corresponding to the sensing mode and at least one sensing requirement of the terminal device.

[0284] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0285] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0286] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0287] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0288] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the use of “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two 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). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” without departing from the scope of this disclosure could be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0289] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0290] The embodiments disclosed herein may be further described using the following terms.

[0291] Clause 1. A network device comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive sensing trigger information for a sensing protocol data unit (PDU) session for an end device via the transceiver; and send a request for sensing policy information associated with a sensing PDU session for the end device to a network function via the transceiver.

[0292] Clause 2. The network device according to Clause 1, wherein the sensing trigger information includes one of the following: a sensing indication; or a sensing task identifier (ID).

[0293] Clause 3. A network device as described in Clause 1, wherein the network function is a sensing function (SF), and the request includes one of the following: the ID of the terminal device; or the ID of the terminal device and the ID of the sensing task.

[0294] Clause 4. A network device as described in Clause 1, wherein the network function is a policy control function (PCF), and the request includes one of the following: the ID of the terminal device and SF information associated with the terminal device; or the ID of the terminal device, SF information, and sensing task ID.

[0295] Clause 5. The network device as described in Clause 4, wherein SF information is received from the Access and Mobility Management Function (AMF) via a transceiver through a request for the SF information, wherein the request includes the ID of the terminal device.

[0296] Clause 6. The network device according to Clause 4, wherein the processor is further configured to: send a request for SF information associated with a terminal device to the Unified Data Management (UDM) via a transceiver, wherein the request includes the ID of the terminal device; and receive the SF information associated with the terminal device from the UDM via the transceiver.

[0297] Clause 7. A network device as described in Clause 4, wherein the SF information includes one of the following: the SF's ID, the SF's Internet Protocol (IP) address, or the SF's Fully Qualified Domain Name (FQDN).

[0298] Clause 8. The network device according to Clause 1, wherein the processor is configured to receive sensing trigger information via: receiving sensing trigger information from the terminal device via an uplink (UL) message via a transceiver; receiving sensing trigger information from the terminal device via a sensor PDU session establishment request via a transceiver; or receiving sensing trigger information and SF information associated with the terminal device from the AMF via a transceiver.

[0299] Clause 9. The network device according to Clause 3, wherein the processor is further configured to: receive a response to sensing policy information from the SF via a transceiver, wherein the response includes sensing policy information associated with a sensing PDU session for a terminal device.

[0300] Clause 10. The network device as described in Clause 9, wherein the response further includes a sensing task ID.

[0301] Clause 11. The network device according to Clause 4, wherein the processor is further configured to: receive a response from the PCF via a transceiver including first sensing control information associated with sensing policy information.

[0302] Clause 12. The network device according to Clause 1, wherein the sensing policy information includes one of the following: at least one QoS parameter, at least one sensing requirement, user plane information for the terminal device, or transport network layer (TNL) information at the SF.

[0303] Clause 13. The network device according to Clause 11, wherein the processor is further configured to: send a trigger message for an N4 session establishment procedure or an N4 session modification procedure to the User Plane Function (UPF) via a transceiver, wherein the trigger message includes a bidirectional tunnel indication; and receive, via the transceiver, TNL information at the UPF for Radio Access Network (RAN) nodes and TNL information at the UPF for SF nodes from the UPF.

[0304] Clause 14. The network device according to any one of Clauses 1 to 13, wherein the processor is further configured to: transmit via a transceiver to the RAN node the ID of the sensing PDU session, TNL information at the SF or TNL information at the UPF, and second sensing control information.

[0305] Clause 15. The network device according to Clause 14, wherein the first sensing control information and the second sensing control information include one of the following: a sensing task ID and a sensing mode of the terminal device; or a sensing task ID, a sensing mode of the terminal device, and at least one sensing requirement.

[0306] Clause 16. A network device comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: determine sensing function (SF) information associated with a sensing protocol data unit (PDU) session for an end device; and transmit the SF information to a session management function (SMF) via the transceiver.

[0307] Clause 17. The network device according to Clause 16, wherein the processor is further configured to: receive, via a transceiver, a sensing indication for determining SF information for the terminal device before determining SF information.

[0308] Clause 18. The network device according to Clause 16, wherein the processor is further configured to: receive, via a transceiver, a sensing indication for determining the SF information and a request to establish a Sensing Protocol Data Unit (PDU) session from the terminal device before determining the SF information, and wherein the SF information is sent to the SMF together with the establishment request.

[0309] Clause 19. A network device according to any one of Clauses 16 to 18, wherein the processor is configured to determine SF information by: determining SF information based on sensing indication.

[0310] Clause 20. The network device according to Clause 16, wherein the processor is further configured to: receive a request for SF information from the Session Management Function (SMF) via a transceiver before determining SF information, wherein the request includes the ID of the terminal device.

[0311] Clause 21. The network device according to Clause 16, wherein the processor is further configured to: receive a sensing registration request from an end device via a transceiver; select a sensing function (SF) for the end device; and send a sensing registration request to the selected SF via a transceiver.

[0312] Clause 22. The network device as described in Clause 21, wherein the sensing registration request includes information on sensing capabilities and the ID of the terminal device.

[0313] Clause 23. A network device comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver, a request for sensing policy information associated with a sensing protocol data unit (PDU) session from a second network device, wherein the sensing policy information is associated with a sensing protocol data unit (PDU) session, wherein the request includes an identifier (ID) of an end device associated with the sensing PDU session; and transmit the sensing policy information to the second network device via the transceiver.

[0314] Clause 24. The network device as described in Clause 23, wherein the request also includes a sensing task ID.

[0315] Clause 25. The network device as described in Clause 23, wherein the second network device includes a Session Management Function (SMF) and a Policy Control Function (PCF).

[0316] Clause 26. The network device according to Clause 23, wherein the processor is further configured to receive a sensing registration request from the terminal device via a transceiver from the Access and Mobility Management Function (AMF).

[0317] Clause 27. The network device according to Clause 23, wherein the processor is further configured to: transmit sensing function (SF) information associated with the terminal device to the Unified Data Management (UDM) via a transceiver.

[0318] Clause 28. A network device according to any one of Clauses 23 to 27, wherein the processor is further configured to assign a sensing task to the terminal device by sending, via a transceiver, one of the following: a sensing task ID, at least one sensing request, and a user plane connection indication; or a sensing task ID, at least one sensing request, a user plane connection indication, and user plane information.

[0319] Clause 29. A terminal device comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: determine to establish a user plane connection with a sensing function (SF); and transmit sensing trigger information associated with a sensing protocol data unit (PDU) session to the network function via the transceiver.

[0320] Clause 30. The terminal device as described in Clause 29, wherein the network function is a session management function (SMF), and the sensing trigger information includes one of the following: a sensing indication; or a sensing task identifier (ID).

[0321] Clause 31. The terminal device as described in Clause 29, wherein the network function is an access and mobility management function (AMF), and the sensing trigger information includes one of the following: a sensing indication; or a sensing task identifier (ID).

[0322] Clause 32. The terminal device according to Clause 31, wherein the sensing trigger information is sent together with the request to establish a sensing PDU session.

[0323] Clause 33. The terminal device according to Clause 29, wherein the processor is configured to determine to establish a user plane connection with the SF by: receiving sensing task information from the SF; receiving sensing task information from a radio access network (RAN) node; or receiving sensing task information from an application on the terminal device.

[0324] Clause 34. The terminal device according to Clause 33, wherein the sensing task information includes one of the following: sensing task ID, at least one sensing request, user plane connection indication, user plane information, or indication to provide sensing results directly to the SF.

[0325] Clause 35. The terminal device according to Clause 29, wherein the processor is further configured to: receive UE routing policy (URSP) rules for sensing from the PCF via a transceiver; and determine at least one attribute of the sensing PDU session based on the rules, wherein the at least one attribute includes the mode of the PDU session and service continuity (SSC), the type of the PDU session, network slice, data network name (DNN), and access type.

[0326] Clause 36. The terminal device according to Clause 29, wherein the processor is further configured to: send a sensing registration request to the AMF via a transceiver, so that the AMF sends a sensing registration request to the SF; and receive a sensing registration response from the AMF via a transceiver, wherein the AMF receives the sensing registration response from the SF.

[0327] Clause 37. The terminal device according to any one of Clauses 28 to 34, wherein the processor is further configured to receive, via a transceiver, one of the following from a radio access network (RAN) node: user plane information for the terminal device; Quality of Service (QoS) Flow Identifier (QFI); Data Radio Bearer (DRB) ID; Logical Channel ID, Logical Channel Group ID; or at least one sensing resource corresponding to the sensing mode and at least one sensing requirement of the terminal device.

[0328] Clause 38. A method performed by a network device, comprising: receiving sensing trigger information of a sensing protocol data unit (PDU) session of a terminal device via a transceiver; and in response to receiving the sensing trigger information, sending a request for sensing policy information associated with the sensing PDU session of the terminal device to a network function via the transceiver.

[0329] Clause 39. A method performed by a network device, comprising: determining sensing function (SF) information associated with a sensing protocol data unit (PDU) session of an end device; and sending the SF information to a session management function (SMF) via a transceiver.

[0330] Clause 40. A method performed by a network device, comprising: receiving, via a transceiver, a request for sensing policy information associated with a sensing protocol data unit (PDU) session, wherein the request includes an identifier (ID) of an end device associated with the sensing PDU session; and, in response to the request, sending the sensing policy information via the transceiver to a second network device.

[0331] Clause 41. A method performed by a terminal device, comprising: determining to establish a user plane connection with a sensing function (SF); and transmitting sensing trigger information associated with a sensing protocol data unit (PDU) session to a network function via a transceiver.

[0332] Clause 42. A computer-readable medium having instructions stored thereon, which, when executed by a processor of a device, cause the device to perform at least the method according to any one of Clauses 38 to 41.

Claims

1. A network device, comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver, sensing trigger information for a terminal device for a sensing protocol data unit (PDU) session; and send, via the transceiver, a request to a network function for sensing policy information associated with the sensing PDU session for the terminal device.

2. The network device of claim 1, wherein the sensing trigger information comprises one of: a sensing indication; or a sensing task identifier (ID).

3. The network device of claim 1, wherein the network function is a sensing function (SF), and the request comprises one of: an ID of the terminal device; or the ID of the terminal device and a sensing task ID.

4. The network device of claim 1, wherein the network function is a policy control function (PCF), and the request comprises one of: an ID of the terminal device and SF information associated with the terminal device; or an ID of the terminal device, the SF information, and a sensing task ID.

5. The network device of claim 4, wherein the SF information comprises one of: an ID of the SF, an Internet protocol (IP) address of the SF, or a fully qualified domain name (FQDN) of the SF.

6. The network device of claim 1, wherein the processor is configured to receive the sensing trigger information by: receiving, via the transceiver, the sensing trigger information from the terminal device via an uplink (UL) message; receiving, via the transceiver, the sensing trigger information from the terminal device via a setup request for a sensing PDU session; or receiving, via the transceiver, the sensing trigger information from an AMF and the SF information associated with the terminal device.

7. The network device of claim 3, wherein the processor is further configured to: receive, via the transceiver, a response to the sensing policy information from the SF, wherein the response comprises the sensing policy information associated with the sensing PDU session for the terminal device.

8. The network device of claim 4, wherein the processor is further configured to: receive, via the transceiver, a response from the PCF comprising first sensing control information associated with the sensing policy information.

9. The network device of claim 1, wherein the sensing policy information comprises one of: at least one QoS parameter, at least one sensing requirement, user plane information for the terminal device, or transport network layer (TNL) information at a SF.

10. The network device of any one of claims 1-9, wherein the processor is further configured to: send, via the transceiver, an ID of the sensing PDU session, TNL information at a SF or TNL information at a UPF, and second sensing control information to the RAN node. ​ 11. The network device of claim 10, wherein the first sensing control information and the second sensing control information comprise one of: the sensing task ID and a sensing mode of the terminal device; or the sensing task ID, the sensing mode of the terminal device, and the at least one sensing requirement.

12. A network device comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: determine sensing function (SF) information associated with a sensing protocol data unit (PDU) session for a terminal device; and send, via the transceiver, the SF information to a session management function (SMF).

13. The network device of claim 12, wherein the processor is further configured to: receive, via the transceiver, from the terminal device, a sensing indication for determining the SF information for the terminal device, prior to determining the SF information.

14. The network device of claim 12, wherein the processor is further configured to: receive, via the transceiver, from the terminal device, a sensing indication for determining the SF information and a setup request for a sensing protocol data unit (PDU) session, prior to determining the SF information, and wherein the SF information is sent to the SMF together with the setup request.

15. The network device of claim 12, wherein the processor is further configured to: receive, via the transceiver, a sensing registration request from the terminal device; select a sensing function (SF) for the terminal device; and send, via the transceiver, the sensing registration request to the selected SF.

16. The network device of claim 15, wherein the sensing registration request comprises information of sensing capabilities and an ID of the terminal device.

17. A terminal device comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: determine to establish a user plane connection with a sensing function (SF); and send, via the transceiver, sensing trigger information associated with a sensing protocol data unit (PDU) session to a network function.

18. The terminal device of claim 17, wherein the network function is a session management function (SMF), and the sensing trigger information comprises one of: a sensing indication; or a sensing task identifier (ID).

19. The terminal device of claim 17, wherein the network function is an access and mobility management function (AMF), and the sensing trigger information comprises one of: a sensing indication; or a sensing task identifier (ID).

20. The terminal device of claim 17, wherein the processor is further configured to: receive, via the transceiver, a UE route selection policy (URSP) rule for sensing from the PCF; and determine at least one attribute of the sensing PDU session based on the rule, wherein the at least one attribute comprises a mode of PDU session and service continuity (SSC), a type of PDU session, a network slice, a data network name (DNN), and an access type.

Images