Local sensing integration for integrated sensing and communication

Abstract

A sensing function control plane (SF-C) is configured to: receive a sensing session setup request from an access and mobility management function (AMF) of a core network, wherein the SF-C is located in the core network; selecting a sensing function user plane (SF-U) for sensing a session in response to the request, wherein the SF-U is located outside the core network; and receiving a sensing data processing result from the SF-U.

Description

Technical Field

[0001] The present application relates generally to wireless communication systems, and particularly to local sensing integration for integrated sensing and communication. Background Art

[0002] Wireless sensing can be used to gather information about remote objects and their characteristics without physically contacting them. Sensing information can be derived from radio frequency (RF)-based and / or non-RF-based sensors. Wireless communication systems can be configured with integrated sensing and communication, where sensing services are provided by the same systems and infrastructure used for communication. Summary of the Invention

[0003] Some exemplary embodiments relate to a method performed by a sensing function control plane (SF-C), the method comprising: receiving a sensing session establishment request from an access and mobility management function (AMF) of a core network, wherein the SF-C is located in the core network; selecting a sensing function user plane (SF-U) for the sensing session in response to the request, wherein the SF-U is located outside the core network; and receiving a sensing data processing result from the SF-U.

[0004] Other exemplary embodiments relate to a method performed by a sensing function user plane (SF-U). The method includes: receiving a sensing session establishment request from a sensing function control plane (SF-C), wherein the SF-C is located in a core network and the SF-U is located outside the core network; processing sensing data for the sensing session; and sending a sensing data processing result to the SF-C or a radio access network (RAN) node. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 Exemplary arrangements according to various exemplary embodiments are shown.

[0006] Figure 2 Exemplary network architectures according to various exemplary embodiments are shown.

[0007] Figure 3 Shown is a signaling diagram for sensing session establishment according to various exemplary embodiments.

[0008] Figure 4 An exemplary user equipment (UE) is shown in accordance with various exemplary embodiments.

[0009] Figure 5 An exemplary base station is shown in accordance with various exemplary embodiments. DETAILED DESCRIPTION

[0010] The exemplary embodiments may be further understood with reference to the following description and associated drawings, wherein like elements are provided with like reference numerals.Exemplary embodiments relate to integrated sensing and communication.

[0011] The exemplary embodiments are described with respect to fifth generation (5G) New Radio (NR) networks. However, reference to 5G NR networks is provided for illustrative purposes only. The exemplary embodiments may be applied to any type of wireless communication system with integrated sensing and communication.

[0012] Wireless sensing can be used to collect information about remote objects and their characteristics without physically contacting the objects. The sensed data of the objects and their surroundings can be analyzed so that meaningful information about the objects and their characteristics can be obtained. Radar is an example of a wireless sensing technology and uses radio waves to determine certain characteristics about remote objects (e.g., distance, angle, velocity, etc.). Other types of wireless sensing technologies include, but are not limited to, time-of-flight cameras, accelerometers, gyroscopes, and lidar. Throughout this specification, any reference to a specific type of wireless sensing technology is provided for illustrative purposes only. The exemplary embodiments may be utilized with any appropriate type of radio frequency (RF)-based and / or non-RF-based sensors.

[0013] The exemplary embodiments are further described with respect to integrated sensing and communication in 5G systems. Those skilled in the art will understand that integrated sensing and communication refers to a concept in which sensing services are provided by the same 5G New Radio (NR) wireless communication system and infrastructure used for communication. This concept can encompass communication-assisted sensing, in which a communication system provides sensing services, or sensing-assisted communication, in which sensed information about the communication channel or environment is used to improve the system's communication performance. Sensing services can be used for a variety of different use cases. To provide some examples, use cases such as, but not limited to, smart transportation, aviation, weather monitoring, health monitoring, and intruder detection in smart factories and smart homes can benefit from 5G systems with integrated sensing and communication.

[0014] The exemplary embodiments introduce a method for integrated sensing and communication using local processing of sensory data. Throughout this specification, this method may generally be referred to as "local sensing integration." Local sensing integration generally refers to a concept in which sensory data is processed locally rather than sent to a core network for processing. For example, sensory data processing may occur at a UE, a base station, a RAN node, and / or an edge network node. In one aspect, local sensing integration minimizes the network signaling overhead associated with the transmission and processing of sensory data. In another aspect, local sensing integration introduces less latency compared to central processing approaches.

[0015] Local sensing integration can use a split control plane and user plane. For the control plane, the Sensing Function - Control Plane (SF-C) is introduced to process control plane signals for sensing services. In some embodiments, the SF-C can be implemented in the core network for simple interaction with other network functions. For the user plane, the Sensing Function - User Plane (SF-U) is introduced to receive and process sensing data. The SF-U can be implemented locally at different components to achieve shorter sensing data transmission distances and local sensing data processing in applicable scenarios. For example, sensing data processing can occur at the UE, base station, RAN node, and / or edge network node. However, references to the terms SF-C and SF-U are provided for illustrative purposes only. Different entities may refer to similar concepts by different names.

[0016] As described above, the exemplary embodiments introduce enhancements to network architectures for local sensing integration (e.g., SF-C, SF-U). Furthermore, the exemplary embodiments introduce mechanisms related to the transmission and processing of sensory data in networks with local sensing integration. The exemplary embodiments can be used independently of one another, in conjunction with other currently implemented integrated sensing and communication mechanisms, in future implementations of integrated sensing and communication mechanisms, or independently of other integrated sensing and communication mechanisms.

[0017] The exemplary network arrangement 100 is provided as a general overview of an exemplary wireless communication system. The exemplary SF-C and SF-U described herein are not shown in the network arrangement 100. These components are described in detail below with respect to the network architecture 200. However, it should be understood that the exemplary SF-C and SF-U may reside in various locations shown in the network arrangement 100. These locations may include: within the radio access network (e.g., RAN 120), within the core network 130, as described with respect to the RAN 120, within the core network 13 ... Figure 1 Separate components outside of the described locations, etc.

[0018] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. Exemplary network arrangement 100 includes user equipment (UE) 110. Those skilled in the art will appreciate that UE 110 may be any type of electronic component configured to communicate via a network, such as a mobile phone, tablet computer, desktop computer, smartphone, phablet, embedded device, wearable device, Internet of Things (IoT) device, etc. It should also be understood that an actual network arrangement may include any number of UEs used by any number of users. Therefore, the example of a single UE 110 is provided for illustrative purposes only.

[0019] In some of the examples provided below, UE 110 may be characterized as a sensor. Throughout this specification, sensor may be used to generally refer to a device that collects sensory data. In some embodiments, UE 110 may be equipped with the hardware, software, and / or firmware required to generate the sensory data. In other embodiments, UE 110 may be connected to another electronic component that generates the sensory data. Figure 4 A detailed description of UE 110 is provided.

[0020] UE 110 can be configured to communicate with one or more networks. In the example of network configuration 100, the network with which UE 110 can wirelessly communicate is a 5G NR radio access network (RAN) 120. However, UE 110 can also communicate with other types of networks (e.g., sixth generation (6G) RAN, 5G cloud RAN, next generation RAN (NG-RAN), long term evolution (LTE) RAN, traditional cellular networks, wireless local area networks (WLAN), etc.), and UE 110 can also communicate with the network via a wired connection. In an exemplary embodiment, UE 110 can establish a connection with 5G NR RAN 120. Therefore, UE 110 can have a 5G NR chipset to communicate with 5G NR RAN 120.

[0021] The 5G NR RAN 120 may be part of a cellular network that may be deployed by a network operator, such as Verizon, AT&T, T-Mobile, etc. The 5G NR RAN 120 may include, for example, nodes or base stations (Node B, eNodeB, HeNB, eNBS, gNB, gNodeB, macro cell, micro cell, small cell, femto cell, etc.) configured to transmit and receive traffic from UEs equipped with appropriate cellular chipsets.

[0022] Those skilled in the art will appreciate that any relevant procedures may be performed for UE 110 to connect to 5G NR RAN 120. For example, as discussed above, 5G NR RAN 120 may be associated with a particular cellular provider for which UE 110 and / or its user has protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR RAN 120, UE 110 may transmit corresponding credential information in order to associate with 5G NR RAN 120. More specifically, UE 110 may associate with a particular base station, such as next-generation Node B (gNB) 120A.

[0023] In some of the examples provided below, gNB 120A, a node operated by gNB 120A, and / or any other type of RAN node may be characterized as a sensor. As mentioned above, throughout this specification, the term sensor may be used to generally refer to a device that collects sensory data. In some embodiments, a network node may be equipped with hardware, software, and / or firmware to generate sensory data. In other embodiments, a network node may be connected to another electronic component that generates sensory data. Thus, throughout this specification, a sensor may refer to a UE or a network node that collects sensory data.

[0024] The network arrangement 100 also includes a cellular core network 130. The cellular core network 130 may refer to an interconnected set of components that manage the operation and traffic of the cellular network. It may include network functions such as, but not limited to, an access management and mobility function (AMF) 131, a unified data management function (UDM) 132, a policy control function (PCF) 133, a network data analysis function (NWDAF) 134, a network exposure function (NEF) 135, and an authentication server function (AUSF) 136.

[0025] The exemplary SF-C and SF-U described herein may reside in various physical and / or virtual locations. Figure 1 It is not shown, but it should be understood that SF-C and SF-U can be located Figure 1 For example, in some embodiments, the SF-C may be located in the core network 130 for simpler communication with the core network 130 functions. Figure 1 To provide another example within the context of , the SF-U may reside at the UE 110 and / or the gNB 120A. However, these examples are not intended to limit the exemplary embodiments in any way. Figure 2 The network architecture 200 describes an exemplary SF-C and SF-U in detail.

[0026] The AMF 131 is generally responsible for connection and mobility management in the 5G NR RAN 120. Those skilled in the art will understand that the AMF 131 is a control plane function and can perform operations related to registration management and connection management. For example, the AMF 131 can perform operations related to registration management between the UE 110 and the core network 130. The exemplary embodiments are not limited to an AMF performing the above-referenced operations. Those skilled in the art will understand the various different types of operations that the AMF can perform. In addition, reference to a single AMF is for illustrative purposes only, and an actual network arrangement may include any appropriate number of AMFs.

[0027] UDM 132 may perform operations related to processing subscription-related information to support network processing of communication sessions. UDM 132 may be equipped with one or more communication interfaces to communicate with other network components (e.g., network functions, RAN, UE, etc.). The exemplary embodiments are not limited to a UDM performing the operations referenced above. Those skilled in the art will appreciate the various different types of operations that a UDM may perform. Furthermore, reference to a single UDM is for illustrative purposes only; an actual network deployment may include any appropriate number of UDMs.

[0028] PCF 133 can perform control plane-related operations, such as, but not limited to, managing policy rules for control plane functions, including network slicing, roaming, and mobility management. PCF 133 can be equipped with one or more communication interfaces to communicate directly or indirectly with other network components (e.g., network functions, RAN, UE, etc.). The exemplary embodiments are not limited to a PCF performing the operations mentioned above. Those skilled in the art will appreciate the various different types of operations that a PCF can perform. Furthermore, reference to a single PCF is for illustrative purposes only; an actual network deployment may include any appropriate number of PCFs.

[0029] NWDAF 134 is a network function that performs operations for network automation, such as receiving input from other network components (e.g., network functions, UEs, cells, etc.), performing analysis on the input, and generating output based on the analysis. However, reference to the NWDAF is provided for illustrative purposes only, and different entities may refer to similar concepts by different names. Thus, the NWDAF described herein may represent any mechanism for performing analysis for network automation. Furthermore, reference to a single NWDAF is for illustrative purposes only; actual network deployments may include any appropriate number of NWDAFs.

[0030] NEF 135 is generally responsible for securely exposing the services and capabilities provided by 5G NR RAN network functions. NEF 135 may be equipped with one or more communication interfaces to communicate with other network components (e.g., network functions, RAN, UE, etc.). The exemplary embodiments are not limited to NEFs performing the operations referenced above. Those skilled in the art will appreciate the various different types of operations that an NEF can perform. Furthermore, reference to a single NEF is for illustrative purposes only; an actual network deployment may include any appropriate number of NEFs.

[0031] The AUSF 136 may store data for authenticating the UE and handle authentication-related functions. The AUSF 136 may be equipped with one or more communication interfaces to communicate with other network components (e.g., network functions, RAN, UE, etc.). The exemplary embodiments are not limited to AUSFs performing the operations mentioned above. Those skilled in the art will appreciate the various different types of operations that an AUSF may perform. Furthermore, reference to a single AUSF is for illustrative purposes only, and an actual network arrangement may include any appropriate number of AUSFs.

[0032] Network arrangement 100 also includes the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. Cellular core network 130 manages traffic flowing between the cellular network and the Internet 140. IMS 150 can generally be described as an architecture for delivering multimedia services to UE 110 using IP protocols. IMS 150 can communicate with cellular core network 130 and the Internet 140 to provide multimedia services to UE 110. Network services backbone 160 communicates directly or indirectly with the Internet 140 and cellular core network 130. Network services backbone 160 can generally be described as a collection of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of UE 110 in communicating with various networks.

[0033] Figure 2 An exemplary network architecture 200 is shown in accordance with various exemplary embodiments. The exemplary architecture 200 is provided as one example of a non-roaming architecture configured for local sensing integration.

[0034] In various examples provided below, reference is made to the components shown in network arrangement 100. Those skilled in the art will appreciate that the components of exemplary architecture 200 may be used with respect to Figure 1 The network arrangement 100 resides in various physical and / or virtual locations. These locations may include: within an access network (e.g., RAN 120), within a core network 130, as part of a Figure 1 Individual components outside of the described locations, etc. However, Figure 1 The reference is for illustrative purposes only. The exemplary network architecture 200 is not limited to Figure 1 The network arrangement 100 shown in FIG. 1 is a block diagram of a wireless communication system and may be used with any suitable type of wireless communication system.

[0035] Some components are shown as connected via connections labeled Nx (e.g., N1, N3). Those skilled in the art will appreciate that each of these connections (or interfaces) is defined in 3GPP specifications. Example architecture 200 utilizes these connections in the manner defined in the 3GPP specifications and can be modified according to the example embodiments described herein. Furthermore, while these interfaces are referred to as connections throughout this specification, it should be understood that these interfaces need not be direct wired or wireless connections; for example, they may communicate via intermediary hardware and / or software components. To provide an example, UE 110 may exchange signals with gNB 120A over the air. However, in architecture 200, UE 110 is shown as having a connection with AMF 205. This connection or interface is not a direct communication link between UE 110 and AMF 205; rather, it is a connection facilitated by intermediary hardware and software components. Therefore, throughout this specification, the terms "connection" and "interface" may be used interchangeably to refer to Nx interfaces between various components.

[0036] In the network architecture 200, the UE 110 may be connected to the AMF 131 via an N1 interface, and the 5G NR RAN 120 may be connected to the AMF 131 via an N2 interface. The AMF 131 may also be connected to other network functions shown in the network arrangement 100, such as the AUSF 136, the UDM 132, etc.

[0037] In network architecture 200, 5G NR RAN 120 may connect to User Plane Function (UPF) 260 via the N3 interface. UPF 260 may perform operations related to packet data unit (PDU) session management and other types of data flow management. For example, UPF 260 may facilitate connectivity between UE 110 and a data network (e.g., the Internet 140). UPF 260 may be equipped with one or more communication interfaces (e.g., N3, etc.) to communicate directly or indirectly with other network components (e.g., network functions, RAN, UE, etc.). The exemplary embodiments are not limited to a UPF performing the operations referenced above. Those skilled in the art will appreciate the various different types of operations that a UPF may perform. Furthermore, reference to a single UPF is for illustrative purposes only; an actual network deployment may include any appropriate number of UPFs.

[0038] As described above, for local sensing integration, the user plane and control plane can be split. SF-C 250 is introduced to process control plane signals for sensing integration. In some examples, SF-C 250 can be deployed in core network 130 to facilitate efficient interaction with other core network functions. Furthermore, reference to a single SF-C is for illustrative purposes only; actual network deployments may include any appropriate number of SF-Cs.

[0039] In some embodiments, the SF-C 250 may be configured to perform various operations related to sensing access and mobility management for different types of sensors (e.g., UEs, RAN nodes, etc.). Sensing access and mobility management operations may include, but are not limited to, sensor registration management, sensor calibration management, sensor mobility management, sensor access and authentication, sensor access and authorization, initiating access node-specific sensing management information, and configuring external parameters for sensing. In some embodiments, the SF-C 250 may be configured to perform various operations related to sensing session management. Sensing session management may include, but is not limited to, sensing session establishment, sensing session modification, sensing session release, selection and control of an SF-U, termination of the interface toward the PCF for sensing, and configuring external parameters for sensing.

[0040] SF-U 255 is introduced to receive and process sensory data. In some examples, SF-U 255 can be deployed locally (e.g., at a base station, RAN node, edge network, etc.) to facilitate shorter sensory data transmission distances and local sensory data processing. Furthermore, reference to a single SF-U is for illustrative purposes only; actual network deployments may include any appropriate number of SF-Us.

[0041] In some embodiments, the SF-U 255 may be configured to perform various operations such as, but not limited to, retrieval of sensory data from the RAN and / or from the UE via the RAN, sensory data processing, sending sensory data processing output to the core network and / or the RAN, sensing traffic usage and reporting, serving as an anchor point for intra-RAT / inter-RAT mobility sensing and user plane sensing policy rule enforcement.

[0042] The SF-C 250 and / or the SF-U 255 may be configured with one or more interfaces to enable communication with other network components shown in the network arrangement 100 (e.g., UDM 132, PCF 133, NWDAF 132, NEF 135, etc.). In addition, the SF-C 250 and / or the SF-U 255 may be configured with one or more interfaces to enable communication with other network components not shown in the network arrangement 100 or the network architecture 200 (e.g., a unified data storage function (UDSF), a network repository function (NRF), etc.).

[0043] In network architecture 200, SF-U 255 can connect to 5G NR RAN 120 via the NS2 interface and to SF-C 250 via the NS1 interface. SF-C 250 connects to AMF 131 via the NSamf interface. Throughout this specification, references to "NSx" interfaces (e.g., NS1, NS2, NSamf) are provided for illustrative purposes only; the NSx categories provided herein may be used as placeholders. In actual deployment scenarios, any appropriate number or label may be assigned to this new interface. Furthermore, while these interfaces are referred to as connections throughout this specification, it should be understood that these interfaces are not required to be direct wired or wireless connections; for example, these interfaces may communicate via intermediary hardware and / or software components.

[0044] Figure 3 A signaling diagram 300 for sensing session establishment is shown according to various exemplary embodiments. Figure 2 The network architecture 200 and Figure 1 The network arrangement 100 of FIG. 1 depicts a signaling diagram 300. The signaling diagram 300 includes a UE 110, a 5G NR RAN 120, an AMF 131, a SF-U 255, a SF-C 150, a PCF 133, and a UDM 132.

[0045] A sensing session may be initiated by a sensor (e.g., UE 110 or a node of 5G NR RAN 120). This is illustrated in signaling diagram 300 by messages 305a and 305b. To provide an example, certain applications (e.g., video games) may utilize a user's gestures or movements for gameplay. UE 110 may collect data (e.g., sensory data) indicating the user's gestures and / or movements from internal components and / or another device connected to UE 110 (e.g., a smartwatch, wearable device, head-up display, etc.). The UE 110 or the network may establish a sensing session to process the sensory data locally at the SF-U 255, rather than by network functions deployed in the core network.

[0046] In 305a, UE 110 transmits a sensing session establishment request to AMF 131. According to some example embodiments, UE 110 may initiate a UE-requested sensing session establishment procedure by sending a non-access stratum (NAS) message with the sensing session establishment request to AMF 131 in an N1 container via an N1 interface. The sensing session establishment request initiated by UE 110 may include a sensing session ID generated by UE 110, the requirement for the sensing session, and / or any other suitable type of parameters.

[0047] In 305b, the RAN node of the 5G NR RAN 120 sends a sensing session establishment request to the AMF 131. According to some example embodiments, the RAN node may initiate the RAN node requested sensing session establishment procedure by sending a NAS message with the sensing session establishment request to the AMF 131 in the N2 container via the N2 interface. The RAN node initiated sensing session establishment request may include a sensing session ID generated by the RAN node of the 5G NR RAN 120, the requirements for the sensing session, and / or any other suitable type of parameters.

[0048] Regardless of which entity initiates the sensing session establishment procedure, the AMF 131 sends a sensing session request SF-C 250 in 310. The request provided by the AMF 131 may include the sensing session ID provided by the UE 110 in 305a or the RAN node in 305b, the requirements for the sensing session, and / or any other suitable type of parameters.

[0049] At 315, SF-C 250 may retrieve subscription information from UDM 132. This may include SF-C 250 sending a request to UDM 132 and UDM 132 sending a response to SF-C 250. However, the above example is provided for illustrative purposes only. Exemplary embodiments are not required to utilize this type of signaling exchange to retrieve subscription information. SF-C 250 may collect subscription information in any suitable manner.

[0050] At 320, SF-C 250 may retrieve Policy and Charging Control (PCC) information from PCF 133. This may include SF-C 250 sending a request to PCF 133 and PCF 133 sending a response to SF-C 250. However, the above example is provided for illustrative purposes only. Example embodiments are not required to utilize this type of signaling exchange to retrieve subscription information. SF-C 250 may collect PCC information in any suitable manner.

[0051] At 325, SF-C 250 selects an SF-U to provide user plane services for the sensing session. In this example, SF-C 250 selects SF-U 255. However, in actual deployment scenarios, there may be multiple SF-Us to choose from. SF-C 250 may select an SF-U to provide user plane services for the sensing session for a sensor (e.g., a UE, a RAN node, etc.) based on any appropriate criteria.

[0052] In 330, SF-C 250 and SF-U 255 establish a sensing session for the user plane. This may include SF-C 250 sending a request to SF-U 255 via the NS1 interface, and SF-U 255 sending a response to SF-C 250 via the NS1 interface. However, the above example is provided for illustrative purposes only. Example embodiments are not required to utilize this type of signaling exchange to establish a sensing session for the user plane. SF-C 250 and SF-U 255 may establish this relationship in any suitable manner.

[0053] In 335 , the SF-C 250 transmits an access node resource request for sensing to the RAN node of the 5G NR RAN 120 .

[0054] At 340, the RAN node and UE 110 establish access node-specific resources for sensing. This may include the RAN node sending a request to UE 110 and UE 110 sending a response to the RAN node. However, the above example is provided for illustrative purposes only. There is no requirement that exemplary embodiments utilize this type of signaling exchange to establish access node-specific resources or sensing. UE 110 may be made aware of the specific resources to be used for sensing in any suitable manner.

[0055] As described above, the UE 110 or the RAN node may initiate the sensing session establishment.For a RAN node initiated sensing session establishment, the RAN node and the UE 110 may not need to establish access node specific resources for sensing, as shown in 335.

[0056] In 345 , the RAN node sends an access node resource request for a sensing acknowledgement (ACK) to the SF-C 250 in response to the request in 330 .

[0057] In 350, SF-C 250 may perform an SF-U update. For example, after SF-U selection in 325, conditions may change, and SF-C 255 may select a different SF-U for sensing data processing. If a new SF-U is selected in 350, SF-C 250 and the new SF-U may perform a sensing session establishment for the user plane before the new SF-U can process sensing data. However, performing an SF-U update is not required, and as shown in this example, the SF-U selected in 325 may continue to process data for the sensing session.

[0058] Regardless of which entity initiates the sensing session establishment procedure, the UE 110 and / or the RAN node of the 5G NR RAN 120 may collect sensing data and provide it to the SF-U 255 for processing. This is illustrated in 355, where the UE 110 transmits sensing data to the 5G NR RAN 120, and 360, where the RAN node transmits sensing data to the SF-U 255.

[0059] When a sensing session is established between UE 110 and SF-U 255, sensing data may be provided by UE 110 to SF-U 255 via 5G NR RAN 120 over the NS2 interface. When a sensing session is established between a RAN node of 5G NR RAN 120 and SF-U 255, sensing data may be provided by the RAN node to SF-U 255 over the S2 interface. Multiple sensing sessions may be established simultaneously for the same or different independent sensing targets. Therefore, there may be scenarios in which both UE 110 and the RAN node provide sensing data to SF-U 255 for the same or different sensing targets.

[0060] In 365, the SF-U 255 processes the sensing data. The output of the processing performed by the SF-U 255 may be provided to the 5G NR RAN 120 and / or the SF-C 255. This is shown in 370a, where the SF-C 255 transmits the sensing data processing results to the 5G NR RAN 120, and 370b, where the SF-U 255 also sends the sensing data processing results to the SF-C 250. Although not shown in the signaling diagram 300, the SF-C 250 may then provide the sensing data processing results to other network functions.

[0061] Figure 4 An exemplary UE 110 is shown according to various exemplary embodiments. Figure 1 The network arrangement 100 and Figure 2 The network architecture 200 depicts a UE 110. The UE 110 may include a processor 405, a memory arrangement 410, a display device 415, an input / output (I / O) device 420, a transceiver 425, and other components 430. The other components 430 may include, for example, an audio input device, an audio output device, a power supply, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, a camera, an accelerometer, a gyroscope, a radar, a lidar, any other suitable type of RF-based sensor, any other suitable type of non-RF-based sensor, and the like.

[0062] The processor 405 may be configured to execute multiple engines of the UE 110. For example, the engines may include a sensing engine 435. The sensing engine 435 may perform various operations related to integrated sensing and communication. The operations may include, but are not limited to, establishing a sensing session, communicating with the SF-C 250, communicating with the SF-U 255, collecting sensing data, processing the sensing data locally at the UE 110, and sending the sensing data to the network.

[0063] The engine 435 referenced above as an application (e.g., a program) executed by the processor 405 is provided for illustrative purposes only. The functionality associated with the engine 435 may also be represented as a separate, integrated component of the UE 110, or may be a modular component coupled to the UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engine may also be embodied as a single application or multiple separate applications. Furthermore, in some UEs, the functionality described with respect to the processor 405 is split between two or more processors, such as a baseband processor and an application processor. The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0064] Memory arrangement 410 may be a hardware component configured to store data related to operations performed by UE 110. Display device 415 may be a hardware component configured to display data to a user, while I / O device 420 may be a hardware component that enables a user to enter input. Display device 415 and I / O device 420 may be separate components or may be integrated together (such as a touch screen). Transceiver 425 may be a hardware component configured to establish a connection with 5G NR-RAN 120, LTE-RAN (not shown in the figure), traditional RAN (not shown in the figure), WLAN (not shown in the figure), etc. Thus, transceiver 425 can operate on a variety of different frequencies or channels (e.g., a set of contiguous frequencies).

[0065] Figure 5 An exemplary base station 500 is shown in accordance with various exemplary embodiments. Base station 500 may represent a gNB 120A or any other access node that a UE 110 may use to establish a connection and manage network operations.

[0066] The base station 500 may include a processor 505, a memory arrangement 510, an input / output (I / O) device 515, a transceiver 520, and other components 525. The other components 525 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports for electrically connecting the base station 500 to other electronic devices and / or power sources, a camera, a radar, a lidar, any other suitable type of RF-based sensor, any other suitable type of non-RF-based sensor, and the like.

[0067] The processor 505 may be configured to execute various engines of the base station 500. For example, these engines may include a sensing engine 530. The sensing engine 530 may perform various operations related to integrated sensing and communication. The operations may include, but are not limited to, establishing a sensing session, communicating with the SF-C 250, communicating with the SF-U 255, collecting sensing data, processing the sensing data locally at the base station 500, and transmitting the sensing data to the UE 110 and / or other network nodes.

[0068] The description of engine 530 as an application (e.g., a program) executed by processor 505 is merely exemplary. The functionality associated with engine 530 may also be represented as a separate, integrated component of base station 500, or may be a modular component coupled to base station 500, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. Furthermore, in some base stations, the functionality described for processor 505 is split across multiple processors (e.g., a baseband processor, an application processor, etc.). The exemplary embodiments may be implemented in any of these or other configurations of a base station.

[0069] Memory 510 may be a hardware component configured to store data related to operations performed by base station 500. I / O device 515 may be a hardware component or port that enables a user to interact with base station 500. Transceiver 520 may be a hardware component configured to exchange data with UE 110. Transceiver 520 may operate on a variety of different frequencies or channels (e.g., a set of contiguous frequencies). Therefore, transceiver 520 may include one or more components (e.g., radios) to enable data exchange with various networks and UEs.

[0070] Example In a first embodiment, one or more processors are configured to operate as a sensing function control plane (SF-C), and the processors are configured to perform operations including: receiving a sensing session establishment request from an access and mobility management function (AMF) of a core network, wherein the SF-C is located in the core network; selecting a sensing function user plane (SF-U) for the sensing session in response to the request, wherein the SF-U is located outside the core network; and receiving sensing data processing results from the SF-U.

[0071] In a second embodiment, the one or more processors according to the first embodiment, wherein the SF-U is located in a radio access network (RAN).

[0072] In a third embodiment, the one or more processors according to the first embodiment, wherein the SF-U is located in a user equipment (UE).

[0073] In a fourth embodiment, the one or more processors according to the first embodiment, wherein the SF-U is located in an edge network node.

[0074] In a fifth embodiment, the one or more processors according to the first embodiment, wherein the sensing session establishment request includes a sensing session ID.

[0075] In a sixth embodiment, the one or more processors according to the first embodiment, wherein the sensing session ID is generated by a user equipment (UE) that initiates a sensing session establishment procedure.

[0076] In a seventh embodiment, the one or more processors according to the first embodiment, wherein the sensing session ID is generated by a radio access network (RAN) node that initiated the sensing session establishment procedure.

[0077] In an eighth embodiment, the one or more processors according to the first embodiment, wherein the operations further comprise: receiving subscription information from a unified data management function (UDM) before selecting the SF-U.

[0078] In a ninth embodiment, the one or more processors according to the first embodiment, wherein the operations further comprise receiving and retrieving policy and charging control (PCC) information from a policy and control function (PCF) before selecting the SF-U.

[0079] In a tenth embodiment, according to the one or more processors of the first embodiment, the operations further comprise: sending the sensing data processing result to another network function of the core network.

[0080] In an eleventh embodiment, the one or more processors according to the first embodiment, wherein the SF-C is configured to perform sensor registration management.

[0081] In a twelfth embodiment, the one or more processors according to the first embodiment, wherein the SF-C is configured to perform sensor connection management.

[0082] In a thirteenth embodiment, the one or more processors according to the first embodiment, wherein the SF-C is configured to perform sensor mobility management.

[0083] In a fourteenth embodiment, the one or more processors according to the first embodiment, wherein the SF-C is configured to perform at least one of sensor access authorization and sensor access authentication.

[0084] In a fifteenth embodiment, the one or more processors according to the first embodiment, wherein the SF-C is configured to perform sensing session management.

[0085] In a sixteenth embodiment, the one or more processors according to the fifteenth embodiment, wherein sensing session management includes at least one of: sensing session establishment, sensing session modification, sensing session release, or provisioning external parameters for sensing.

[0086] In a seventeenth embodiment, the one or more processors of the fifteenth example, wherein the sensing session management includes SF-U selection.

[0087] In an eighteenth embodiment, the one or more processors of the fifteenth embodiment, wherein sensing session management includes terminating an interface towards a policy control function (PCF) for sensing.

[0088] In a nineteenth embodiment, one or more processors are configured to operate as a sensing function user plane (SF-U), the processors being configured to perform operations including: receiving a sensing session establishment request from a sensing function control plane (SF-C), wherein the SF-C is located in a core network and the SF-U is located outside the core network; processing sensing data for a sensing session; and sending a sensing data processing result to the SF-C or a radio access network (RAN) node.

[0089] In a twentieth embodiment, the one or more processors according to the nineteenth embodiment, wherein the SF-U is located in a radio access network (RAN).

[0090] In a twenty-first embodiment, the one or more processors according to the nineteenth embodiment, wherein the SF-U is located in a user equipment (UE).

[0091] In a twenty-second embodiment, the one or more processors according to the nineteenth embodiment, wherein the SF-U is located in an edge network node.

[0092] In a twenty-third embodiment, the one or more processors according to the nineteenth embodiment, wherein the SF-U is configured to perform sensory traffic usage reporting.

[0093] In a twenty-fourth embodiment, the one or more processors according to the nineteenth embodiment, wherein the SF-U is configured to perform sensing policy rule enforcement for the user plane.

[0094] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. The exemplary embodiments of the above methods may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0095] Although this application describes various embodiments, each having different features in various combinations, those skilled in the art will understand that any feature of one embodiment may be combined with features of other embodiments in any manner that is not expressly disavowed or that is not functionally or logically inconsistent with the operation of the device or the stated function of the disclosed embodiment.

[0096] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0097] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, it is intended that the present disclosure covers modifications and variations of the present disclosure as long as they come within the scope of the appended claims and their equivalents.

Claims

1. A method comprising: At the sensing function control plane (SF-C): receiving a sensing session establishment request from an access and mobility management function (AMF) of a core network, wherein the SF-C is located in the core network; selecting, in response to the request, a sensing function user plane (SF-U) for a sensing session, wherein the SF-U is located outside the core network; as well as A sensing data processing result is received from the SF-U. 2 . The method of claim 1 , wherein the SF-U is located in a radio access network (RAN). The method of claim 1 , wherein the SF-U is located in a user equipment (UE). The method according to claim 1 , wherein the SF-U is located in an edge network node. The method of claim 1 , wherein the sensing session establishment request includes a sensing session ID. The method of claim 1 , wherein the sensing session ID is generated by a user equipment (UE) that initiates a sensing session establishment procedure. 7 . The method of claim 1 , wherein the sensing session ID is generated by a radio access network (RAN) node that initiates a sensing session establishment procedure.

8. The method according to claim 1, further comprising: Subscription information is received from a unified data management function (UDM) before selecting the SF-U.

9. The method according to claim 1, further comprising: Retrieving policy and charging control (PCC) information from a policy and control function (PCF) is received before selecting the SF-U.

10. The method according to claim 1, further comprising: The sensing data processing result is sent to another network function of the core network. The method according to claim 1 , wherein the SF-C is configured to perform sensor registration management. 12 . The method of claim 1 , wherein the SF-C is configured to perform sensor connection management.

13. The method of claim 1, wherein the SF-C is configured to perform sensor mobility management. 14 . The method of claim 1 , wherein the SF-C is configured to perform at least one of sensor access authorization and sensor access authentication.

15. The method of claim 1, wherein the SF-C is configured to perform sensing session management.

16. The method of claim 15, wherein sensing session management comprises at least one of: sensing session establishment, sensing session modification, sensing session release, or provisioning external parameters for sensing. The method of claim 15 , wherein the sensing session management comprises SF-U selection.

18. The method of claim 15, wherein sensing session management includes terminating an interface towards a policy control function (PCF) for sensing.

19. A method comprising: At the Sensing Function User Plane (SF-U): receiving a sensing session establishment request from a sensing function control plane (SF-C), wherein the SF-C is located in a core network and the SF-U is located outside the core network; processing the sensory data for the sensing session; and The sensing data processing result is sent to the SF-C or a radio access network (RAN) node.

20. The method of claim 19, wherein the SF-U is located in a radio access network (RAN).

21. The method of claim 19, wherein the SF-U is located in a user equipment (UE).

22. The method of claim 19, wherein the SF-U is located in an edge network node.

23. The method of claim 19, wherein the SF-U is configured to perform sensory traffic usage reporting.

24. The method of claim 19, wherein the SF-U is configured to perform sensing policy rule enforcement for the user plane.

Images