Control signaling for integrated awareness and communication

Abstract

A method of perception and communication includes receiving, by a perception node, a perception configuration request from a perception function, determining, by the perception node, to support a perception configuration in response to the perception configuration request, and configuring a perception signal of the perception node according to the perception configuration. The method provides an integrated framework to implement advanced perceptual applications while minimizing the impact on communication performance and allowing independent evolution of perceptual and communication technologies.

Description

[0001] Cross-references

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 584,511, filed September 22, 2023, the contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to wireless communication, and more specifically, to a signaling method for controlling the activity of sensing nodes in an integrated communication and sensing scheme. Background Technology

[0004] In wireless communication systems, such as 5G or 6G cellular systems, "sensing" capabilities can be integrated to detect objects that are not actively participating in the system. This means that network nodes, such as user equipment (UE) or base stations (BS), can transmit signals and analyze reflected or returned signals from objects in the environment. By processing these returned signals, the system can infer the location of the sensed object and other contextual information. This approach of integrating sensing capabilities into wireless communication systems is called integrated sensing and communication (ISAC) or similar terms.

[0005] Current sensing systems face several key challenges for effective implementation. These challenges include effectively allocating resources between sensing and communication functions, managing mutual interference, ensuring proper coordination and synchronization among multiple nodes, addressing privacy and security issues, designing versatile waveforms, balancing performance trade-offs, developing flexible network architectures, handling increased processing complexity, establishing standardized protocols, and addressing regulatory challenges. Therefore, a control signaling mechanism is needed to address many of these issues by providing a flexible framework for managing sensing operations within communication networks. This framework would allow for dynamic resource allocation, improved coordination among nodes, and adaptive network architectures, thereby helping to address key ISAC challenges such as resource management, interference mitigation, and system integration. Summary of the Invention

[0006] One embodiment discloses a method for sensing and communication. The method includes a sensing node receiving a sensing configuration request from a sensing function, the sensing node responding to the sensing configuration request to determine support for a sensing configuration, and configuring a sensing signal of the sensing node according to the sensing configuration.

[0007] Another embodiment discloses a method for sensing and communication. The method includes a first node receiving a sensing configuration request from a sensing function, the first node responding to the sensing configuration request to determine a sensing configuration supporting a second node, and configuring a sensing signal of the second node according to the sensing configuration.

[0008] One embodiment discloses a user equipment (UE) including a sensor and a processor coupled to the sensor. The sensor is used to generate a sensing signal. The processor is used to receive a sensing configuration request from a sensing function, determine to respond to the sensing configuration request to support a sensing configuration, and configure the sensing signal according to the sensing configuration.

[0009] These, and other objectives of the invention, will undoubtedly become apparent to those skilled in the art upon reading the following detailed description of the preferred embodiments, illustrated in various figures and diagrams. Attached Figure Description

[0010] Figure 1 Basic sensing operations between sensing nodes and sensing targets are described according to an embodiment.

[0011] Figure 2 A communication system comprising sensing functionality and multiple sensing nodes according to an embodiment is described.

[0012] Figure 3 A protocol stack for communication between a first sensing node and sensing functions located in the core network, according to an embodiment, is described.

[0013] Figure 4 A control plane protocol stack for communication between a second sensing node and sensing functions located in the core network, according to an embodiment, is described.

[0014] Figure 5 The user plane protocol stack for communication between the second sensing node and the sensing function located in the data network is described.

[0015] Figure 6 A flowchart is described, illustrating the sequence of protocol interactions between the sensing function and the sensing node according to an embodiment.

[0016] Figure 7 A communication system comprising sensing functionality and multiple sensing nodes according to an embodiment is described.

[0017] Figure 8 A communication system comprising sensing functionality and multiple sensing nodes according to an embodiment is described.

[0018] Figure 9A communication system comprising sensing functionality and multiple sensing nodes according to an embodiment is described.

[0019] Figure 10 A flowchart describing the protocol interaction sequence according to an embodiment is provided.

[0020] Figure 11 Alternative arrangements of nodes according to an embodiment are described.

[0021] Figure 12 An exemplary protocol stack according to an embodiment is described.

[0022] Figure 13 A simplified block diagram of a user equipment (UE) and network entities according to an embodiment is described. Detailed Implementation

[0023] This disclosure explores specific details in detail to provide a comprehensive understanding, but those skilled in the art can practice it without these details. Well-known methods, procedures, components, and circuits are not described in detail to maintain clarity. This disclosure focuses primarily on 3GPP wireless networks, but can also be applied to other cellular and non-cellular wireless networks.

[0024] Specifically, the following technologies, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, Carrier Frequency Division Multiple Access (C-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using wireless technologies such as Global System for Mobile Communications (GSM), Universal Packet Radio Service (GPRS), or Enhanced Data Rate GSM Evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3GPP Long Term Evolution (LTE) is part of the Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). The evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G New Radio (NR).

[0025] For ease of description, the embodiments described herein are primarily relating to 3GPP-based wireless communication systems. However, the technical features of this specification are not limited thereto. For example, the following detailed description is based on a mobile communication system corresponding to, but is not limited to, 3GPP-based wireless communication systems; aspects of this specification can be applied to other wireless communication systems.

[0026] As described in 3GPP, different wireless communication system standards and protocols can use various Radio Access Networks (RANs) to communicate between RAN base stations (sometimes generally referred to as RAN nodes, network nodes, or simply nodes) and wireless communication devices called User Equipment (UEs). 3GPP RANs can include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN). A RAN can include base stations (cell sites), Radio Equipment Controllers (RECs), and fronthaul and backhaul networks to transmit data between base stations, RECs, and the core network.

[0027] The RAN can include one or more access nodes, which may be referred to as base stations, NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), 6G nodes, RAN nodes, controllers, transport receiver points (TRPs), etc., and may include ground stations (e.g., terrestrial access points) or satellite stations to provide signal coverage within a geographic area (e.g., a cell). The RAN can include one or more RAN nodes for providing macrocells, microcells, nanocells, or other types of cells. Macrocells can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UEs with service subscriptions. Microcells can cover a relatively small geographic area and can allow unrestricted access by UEs with service subscriptions. Nanocells can cover a relatively small geographic area (e.g., a home) and can allow restricted access by UEs associated with nanocells (e.g., UEs in a closed subscriber group (CSG), home UEs, etc.).

[0028] The base stations used by a RAN can correspond to that RAN. An example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also known as an evolved Node B, enhanced Node B, eNodeB, or eNB). Another example of an NG-RAN base station is a Next Generation Node B (also known as a gNodeB or gNB).

[0029] The RAN provides its communication services to external entities through its connection to the core network (CN). For example, E-UTRAN can utilize the evolved packet core.

[0030] Each RAN can use one or more Radio Access Technologies (RATs) to communicate between the base station and the UE. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements UMTS RAT or other 3GPP RAT, E-UTRAN implements LTE RAT (sometimes called LTE), and NG-RAN implements NR RAT (sometimes called 5G RAT, 5G NR RAT, or NR). In some deployments, E-UTRAN may also implement NR RAT. In some deployments, NG-RAN may also implement LTE RAT.

[0031] For terms and technologies not specifically defined or described, please refer to wireless communication standards documents (e.g., 3GPP specifications) published prior to this specification.

[0032] It should be noted that although the term 5G is used throughout the discussion, this is not restrictive, and alternative names for nodes and / or interfaces can be used for similar purposes.

[0033] In an Integrated Sensing and Communication (ISAC) system, any node capable of transmitting and receiving wireless signals can act as a sensing node, such as a User Equipment (UE) or a Base Station (BS), or a combination of both (UE and BS). These nodes can be configured with sensing signals in various ways, taking into account factors such as their own communication needs, the performance requirements of sensing operations, and the characteristics of the operating radio. For example, a node focused on high-speed communication may allocate fewer resources to sensing, while high-precision sensing may require more bandwidth for the sensing signal. Furthermore, the frequency of the sensing signal may depend on the size of the sensing area; for instance, lower frequencies are used in larger areas due to their better propagation characteristics.

[0034] The ISAC system can use multiple sensing nodes to combine their sensing information for various purposes. For example, the system can use techniques such as triangulation or trilateration to determine the precise location of a sensed object, referred to as a sensing target. Furthermore, the system can combine data about different sensed objects to construct a comprehensive model of the surrounding environment.

[0035] To manage and coordinate ISAC operations, the system can utilize a dedicated function called the Sensing Function (SF). In some cases, the SF can be combined with other functions or considered equivalent, such as the Location Management Function (LMF), which handles location-related tasks. The SF can be deployed in different locations within the system architecture depending on specific requirements and design. For example, it can reside in the Core Network (CN), the central part of the system, or in the Radio Access Network (RAN), closer to the edge and interacting directly with user equipment. In some cases, the SF can even be implemented directly on mobile devices to achieve more localized and distributed sensing capabilities and / or support sensing operations outside the coverage area of ​​network nodes. However, integrating the SF into the system introduces new challenges, particularly regarding control signaling between the SF and various sensing nodes. Efficient and reliable signaling mechanisms are crucial for ensuring the proper coordination, configuration, and operation of sensing functions within the network. Therefore, developing robust solutions for control signaling between the SF and sensing nodes is a key requirement for the successful deployment and utilization of ISAC capabilities in 5G or potential 6G systems.

[0036] Figure 1 A basic sensing operation between sensing node 110 and sensing target 120 is described according to an embodiment. This operation includes three main steps. Step 1 involves sensing node 110 (e.g., a user equipment) sending sensing signals. These signals may be specifically directed to sensing target 120 or broadcast in a directional or omnidirectional manner. Signals of particular interest are those that successfully reach sensing target 120 (e.g., a vehicle) and trigger return signals, which may be reflections of the original sensing signals.

[0037] In step 2, sensing node 110 receives return signals from sensing target 120. These return signals can take various forms depending on the specific implementation. They may be simple reflections of the original signal, or modified versions that have been amplified, modulated, or have additional information embedded within the sensing target 120 itself. (Measurement of return signals)

[0038] In step 3, sensing node 110 processes and measures various properties of the received return signals. A common measurement is the time difference between the transmission of the original sensing signal and the arrival of the corresponding return signal. This time difference can be used to calculate the distance or range between sensing node 110 and sensing target 120 based on the known signal propagation speed.

[0039] ISAC's capabilities extend beyond what has been described previously. In some applications, it can analyze the environment and extract a wide range of details, including the presence, location, and motion of objects. Furthermore, it can determine the range, velocity, size, shape, and even material properties of objects.

[0040] Figure 2 A communication system 200 comprising a sensing function (SF) 240 and multiple sensing nodes is described according to an embodiment. In this particular example, the SF 240 is located in the core network (CN) 230, although it should be noted that the SF 240 may also be located in other locations within the system.

[0041] Figure 2 The communication system described includes an SF 240 located in CN 230, a base station (BS) 210 as a first sensing node, and a UE 220 as a second sensing node. The UE 220 and BS 210 are connected via a wireless communication link. The BS 210 can be further connected to one or more nodes or network functions (NFs) in CN 230 via a communication link, which can be wired, wireless, or a combination of both. Figure 2 In this context, the communication link is represented by a solid line, terminating at a specific node within the CN. This specific node may function as an "anchor node," similar to the Access and Mobility Management Function (AMF) in a 5G system, acting as a communication gateway between the RAN and the CN.

[0042] In some embodiments, the BS (e.g., BS 220) may be further divided into multiple components, such as Centralized Units (CUs) and one or more Distributed Units (DUs). Nodes in the CN (e.g., CN 230) are interconnected via a service bus, as shown in the figure. This allows CN nodes to expose and invoke services via the service bus, a mechanism known as a Service-Based Interface (SBI). In some cases, one or more RAN nodes may also communicate on the same service bus as the CN, or on a separate service bus, thereby utilizing the SBI within the RAN and / or between the RAN and the CN.

[0043] It is important to note that throughout this discussion, communication can be implemented in different ways: as protocol messages at a reference point, as calls to the Application Programming Interface (API) on the Service-Based Interface (SBI), or a combination of both. In other words, the communication link between the Base Station (BS) and the Core Network (CN) can be implemented as a point-to-point interface, a service-based reference point, or a combination of both. This combination of interfaces enables communication between sensing nodes and other nodes in the system, particularly allowing sensing nodes to exchange information with sensing functions (SF).

[0044] Figure 3 This diagram describes the communication protocol stack between a first sensing node (in this case, a Distributed Unit (DU) of a base station) and a sensing function (e.g., SF 240) located in the core network (e.g., CN 230), according to an embodiment. The diagram uses 5G terminology to describe certain nodes and interfaces; however, it should be understood that other terminology may be used in 6G systems to implement similar functionality. The diagram focuses on specific parts of the communication system (e.g., communication system 200), including the Distributed Unit (DU), Centralized Unit (CU), Access and Mobility Management Function (AMF), and Sensing Function (SF). Communication between the DU and SF is achieved through a newly introduced Sensing Control Protocol (SCP), which establishes communication between the two entities.

[0045] DU and CU communicate via the F1 interface using the F1 Application Protocol (F1AP). This protocol is carried over the network transport layer, and the specific implementation may vary; it is labeled "NW transport" and "NW" in the diagram. Similarly, CU and AMF communicate via the NG interface (also known as the N2 interface) using the Next Generation Application Protocol (NGAP), which is also carried over the network transport layer according to its specific implementation. On the other hand, AMF and SF communicate via the service bus using one or more Service Basic Interfaces (SBIs).

[0046] The lower layers of the protocol stack are responsible for providing transport for SCPs. This is achieved by encapsulating or containerizing SCP messages within lower-layer communications. It's important to note that the node, protocol, and interface names used in this example are illustrative and may differ in other systems. In some cases, base stations may have a "monopolistic" architecture rather than being divided into CUs and DUs. In such cases, the protocol stack may be simpler than shown in the diagram. For monopolistic base stations, SCPs can be transmitted from the base station to the AMF via NGAP. More generally, SCPs can be transmitted between the base station and anchor nodes in the core network via any base station-to-core network interface. Essentially, SCPs enable communication between sensing nodes (DUs) and sensing nodes (SFs) in the core network, with the lower layers of the protocol stack providing the necessary transport mechanisms.

[0047] Figure 4 This diagram describes the control plane protocol stack between a second sensing node (e.g., User Equipment (UE220)) and a sensing function (e.g., SF 240) located in the core network (e.g., CN 230) according to an embodiment. The diagram focuses on a specific part of the communication system (e.g., communication system 200), which includes the User Equipment (UE), Distributed Unit (DU), Centralized Unit (CU), Access and Mobility Management Function (AMF), and Sensing Function (SF). Communication between the UE (e.g., UE 220) and the SF (e.g., SF 240) is achieved through a newly introduced Sensing Control Protocol (SCP), which is established between the two entities (i.e., the UE and the SF).

[0048] The UE and DU communicate via the air interface using one or more protocol layers, such as the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and the Physical (PHY) layer. Conversely, the DU and CU communicate via the F1 interface using F1AP, a protocol carried by a specific implementation of the associated network transport layer, labeled "NW" in the diagram. Similarly, the CU and AMF communicate via the NG interface (also known as the N2 interface) using the Next Generation Application Protocol (NGAP), which is also carried by a specific implementation of the associated network transport layer. The AMF and SF communicate via the service bus using one or more Service Basic Interfaces (SBIs).

[0049] Although the UE and CU do not communicate directly on specific interfaces, they communicate with each other through one or more protocol layers, such as the Radio Resource Control (RRC) layer and the Packet Data Convergence Protocol (PDCP) layer. The lower layers of the protocol stack are responsible for providing transport for the SCP, which is achieved by encapsulating or containerizing SCP messages in lower-layer communications. Essentially, the SCP enables communication between the sensing node (i.e., the UE) and the SF in the core network, with the lower layers of the protocol stack providing the necessary transport mechanisms.

[0050] Figure 5 This diagram describes the user plane protocol stack between a second sensing node (e.g., a user equipment (UE 220)) and a sensing function (e.g., an SF 240) located in a data network (DN), according to an embodiment. The diagram focuses on specific parts of the communication system (e.g., communication system 200), including the user equipment (UE), distributed unit (DU), centralized unit (CU), user plane function (UPF), and sensing function (SF). Communication between the UE and the SF is achieved through a newly introduced sensing control protocol (SCP), which is established between these two entities (i.e., the UE and the SF).

[0051] User Equipment (UE) and Distribution Unit (DU) communicate via an air interface using one or more protocol layers, such as the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical (PHY) layer. The DU and Central Unit (CU) communicate via the F1 interface using F1AP, which is carried out through the relevant network transport layer and is labeled "NW" in the diagram. The CU and User Plane Function (UPF) communicate via the N3 interface using the General Packet Radio Service User Plane Tunneling Protocol (GTP-U), which is transmitted through the User Datagram Protocol (UDP) layer, the Internet Protocol (IP) layer, and the relevant network transport layer.

[0052] The User Plane Function (UPF) and Sensing Function (SF) communicate via the N6 interface on the Data Network (DN), the transport layer used being not detailed in the diagram. Alternatively, the UPF and SF can communicate via a Service-Based Interface (SBI) within the Core Network (CN). User Equipment (UE) and Central Unit (CU) communicate with each other through one or more protocol layers, such as the Serving Data Application Protocol (SDAP) layer and the Packet Data Convergence Protocol (PDCP) layer. The UE and UPF also communicate with each other through the Protocol Data Unit (PDU) layer.

[0053] In some embodiments, the Sensing Function (SF) can be viewed as an application server within the Data Network (DN), while the User Plane Function (UPF) can act as a gateway between the cellular network node and the Data Network (DN). In this case, the Sensing Control Protocol (SCP) is transmitted between the User Equipment (UE) and the Sensing Function (SF) as user plane data.

[0054] This user plane protocol stack enables communication between the sensing node (User Equipment, UE) and the sensing function (SF) in the data network (DN), with the lower layers of the stack providing the necessary transport mechanisms. The specific arrangement of nodes and interfaces allows for seamless integration of the sensing function into existing cellular network architectures.

[0055] Figure 6 A flowchart is described, illustrating the sequence of protocol interactions between the sensing function (SF) and sensing nodes according to an embodiment. Figure 6 The communications shown can be Perception Control Protocol (SCP) messages or Service-Based Interface (SBI) calls. These communications can be transmitted using various protocol stacks, such as the one shown in the previous diagram or similar stacks with different terminology. Furthermore, note that optional steps are indicated by dashed arrows.

[0056] The sequence begins when the Sense Function (SF) (e.g., SF 240) determines that a sense operation is required. In step 601, the Sense Function (SF) sends a sense configuration request to the sense nodes (e.g., base station (BS) 210 and / or user equipment (UE) 220), which may initiate the first SCP transaction. This request may include the required sense signal configuration characteristics (hereinafter referred to as "Sense Configuration"). Although presented as a single message, this request may comprise multiple messages sent separately to different sense nodes. In some cases, the Sense Configuration (or a portion thereof) may be passed to the sense nodes as a policy of the user equipment (UE) and / or base station (BS) via existing N1 or N2 interfaces or equivalent service-based reference points.

[0057] In step 602, each sensing node determines the sensing configuration it will support, taking into account factors including its radio capabilities, requirements for other radio frequency signal transmissions, anticipated control interference on the air interface, and the characteristics of the requested sensing configuration (e.g., radio frequency, time, power, etc.). In step 603, the sensing node then responds to the sensing function (SF) with a sensing configuration response, concluding the first SCP transaction.

[0058] Next, in step 604, the Sensing Function (SF) sends a Sensing Activation Request to the Sensing Node to initiate the transmission of sensing signals, thereby launching the second SCP transaction. In step 605, the Sensing Node can optionally respond to the Sensing Activation Response; if the previously confirmed activation of the configuration is deemed fault-free, this response can be omitted. If step 605 is executed, the second SCP transaction ends.

[0059] In step 606, the sensing node performs the transmission and measurement of the sensing signal, following a process similar to... Figure 1 The program described in [the document / document].

[0060] Optionally, if the perception activation request in step 604 does not include a measurement request, the perception function (SF) may send a perception measurement request to the perception node in step 607 to initiate a third SCP transaction.

[0061] In step 608, the sensing node sends a sensing measurement report to the sensing function (SF), providing the information obtained in step 606. Depending on whether step 607 occurs, this report (in step 608) can either end the third SCP transaction, initiate a new SCP transaction, or end the second SCP transaction.

[0062] In step 609, the sensing function (SF) sends a sensing deactivation command to the sensing nodes, instructing them to stop transmitting sensing signals. The sensing nodes may optionally send a sensing deactivation response in step 610 to confirm the deactivation of the sensing signals. In some cases, if the deactivation is considered fault-free, step 610 can be omitted.

[0063] Finally, the perception function (SF) assessment report includes perception measurements, applies specific standards and heuristics to achieve them, and infers perception goals.

[0064] In some embodiments, the sensing function (SF) may use different protocols when communicating with different types of sensing nodes. For example, the sensing function (SF) may use a first sensing control protocol (SCP1) when interacting with a sensing node embodied in a user equipment (UE); and a second sensing control protocol (SCP2) when communicating with a sensing node embodied in a base station (BS). Although these protocols may have similar messages and functions, they are considered to have different termination points in form.

[0065] Figure 7 A communication system 700 is described, including a sensing function and multiple sensing nodes, according to an embodiment. In this figure, the sensing function (SF) 740 is shown as an element of the core network (CN) 730, communicating with the sensing node embodied in the user equipment (UE) 720 using SCP1, and communicating with the sensing node embodied in the base station (BS) 710 using SCP2. The transmission protocol layering of SCP1 and SCP2 may be similar to... Figure 3 , 4 The protocol stack shown in Figure 5.

[0066] This approach allows the Sensing Function (SF) 740 to customize its communication protocols according to the specific requirements and capabilities of different types of sensing nodes. By using different protocols for the User Equipment (UE) 720 and the Base Station (BS) 710, the system can adapt to the unique characteristics and limitations of each type of sensing node while maintaining consistent message and function sets across protocols. This flexibility enables the SF 740 to effectively manage and coordinate the sensing activities of various sensing nodes within the network.

[0067] In some scenarios, different endpoints may use different protocols to carry a common Sensing Control Protocol (SCP). For example, the SF can use the first Sensing Transport Protocol (STP1) to communicate with the sensing node that is represented as a UE, and use the second Sensing Transport Protocol (STP2) to communicate with the sensing node that is represented as a BS, where each STP1 and STP2 carries SCP messages.

[0068] Figure 8A communication system 800 is illustrated, comprising a sensing function and multiple sensing nodes, according to an embodiment. In this embodiment, SF 840, shown as an element of Core Network (CN) 830, communicates with sensing nodes embodied as BS 810 and UE 820 using a single SCP. However, SF communicates with the sensing node embodied as UE 820 using a first sensing transport protocol STP1, and with the sensing node embodied as BS 810 using a second sensing transport protocol STP2.

[0069] In this example, the Sensing Transport Protocols STP1 and STP2 might be limited-scope protocols containing “container” messages. These messages might contain a transparent container field capable of encapsulating the SCP message. Such a container field can be implemented using various data types, such as BIT STRING or OCTET STRING in the Abstract Syntax Notation One (ASN.1) message format.

[0070] The above arrangement offers several advantages. It allows for the definition and maintenance of a single SCP containing the essential messages needed to control sensing activities. Simultaneously, it enables the maintenance of separate transport protocols for communication across different network nodes. This approach provides flexibility in adapting to the specific requirements and constraints of different types of sensing nodes, while maintaining a consistent set of control messages throughout the system.

[0071] By decoupling the transport protocol from SCP, this design facilitates the independent evolution and optimization of sensing and control messages. This can lead to a more modular, scalable, and maintainable architecture for sensing and control systems within the network.

[0072] Figure 9 A communication system 900 is described, including a sensing function and multiple sensing nodes, according to an embodiment.

[0073] In some cases, when the sensing node is a User Equipment (UE) 910, control of the sensing function may need to be shared between the Sensing Function (SF) 940 and the Base Station (BS) 910. This may occur when the signals used for sensing are directly controlled by the BS 910, and some operations on these signals (such as activation and deactivation) require low latency, making direct control by the SF 940 unsuitable. Furthermore, the BS 910 may have a better understanding of radio constraints that could affect the scheduling and configuration of sensing signals compared to the SF 940. Therefore, a design where the sensing configuration of the UE 920 as a sensing node is negotiated between the SF and one or more BSs, with the BS 910 directly controlling the sensing signals of the UE 920, might be preferable.

[0074] In this setup, the Sensing Control Protocol (SCP) is used for communication between SF 940 and UE 920. An additional protocol, the Sensing Management Protocol (SMP), is used for communication between SF 940 and BS 910. Radio protocols (such as RRC, MAC, or PHY) are used for communication between BS 910 and UE 920.

[0075] It is important to note that, Figure 9 In this context, BS 910 itself is not considered a sensing node. However, if BS-based sensing is still required, SF 940 can establish a separate control protocol with BS (e.g., SCP), as previously described.

[0076] This architecture allows for a clear separation of responsibilities between the SF 940 and BS 910 when controlling the sensing functions of the UE 920. The SF 940 can focus on high-level coordination and management of sensing activities across multiple nodes, while the BS 910 can handle low-level, latency-sensitive control of sensing signals based on its understanding of the radio environment and limitations. By leveraging SMP between the SF 940 and BS 910, the system ensures that the UE's sensing configuration is properly negotiated and aligned with overall sensing objectives. Simultaneously, the use of radio protocols between the BS 910 and UE 920 enables efficient and responsive control of sensing signals, taking into account the real-time dynamics of the radio interface.

[0077] Figure 10A flowchart illustrating a series of protocol interactions between the SF, the base station, and the sensing node located at the UE, according to an embodiment, is provided. The sensing configuration is negotiated between the SF (e.g., SF 940) and the BS (e.g., BS 910), and then transmitted from the BS (e.g., BS 910) to the UE (e.g., UE 920). Figure 10 The flowchart is Figure 6 The flowchart shown is a variation involving the Business Layout (BS). Additionally, note that optional steps are indicated by dashed arrows.

[0078] The process begins in step 1001 when the SF sends a perception configuration request to the BS, possibly specifying the required perception signal characteristics to meet the requirements of basic perception operations. In step 1002, the BS determines the perception configuration it can support for the UE, taking into account factors such as the UE's existing signal transmission and reception configuration, coordination with other UEs within the BS's service area, and any other specific implementation standards.

[0079] Then, in step 1003, the BS sends a aware configuration response to the SF, indicating the selected configuration, which may differ from the configuration requested in step 1. In step 1004, the BS sends a configuration message (e.g., an RRCReconfiguration message) to the UE, specifying the aware configuration. Next, the UE can optionally confirm the configuration in step 1005 (e.g., using an RRCReconfigurationComplete message) to acknowledge receipt and successful application. If configuration delivery is reliable and success is always assumed, step 1005 can be omitted, although it may be beneficial for the BS to know when the UE has completed applying the configuration.

[0080] In step 1006, the SF sends a sensing activation request to the BS, instructing the BS to trigger the UE to begin transmitting the configured sensing signals. Then, in step 1007, the BS sends a sensing activation instruction (e.g., a MAC control element) to the UE, triggering the transmission of the configured sensing signals. The activation instruction can specify which of several configured sensing signals should be activated. The UE can optionally confirm the activation in step 1008 (e.g., using an uplink MAC control element), confirming the requested activation. If it is assumed that activation is always successful and occurs immediately, and the BS does not need explicit acceptance notification, step 1008 can be omitted. Then, in step 1009, the UE transmits the sensing signals to the sensing target and measures the return signal (similar to...). Figure 6 Step 606 in the middle.

[0081] The SF may optionally send a sensing measurement request (e.g., an SCP message) to the UE in step 1010. If the UE is aware of the SF involved and the activation in step 1007 implicitly instructs the UE to return the measurement results to the SF, step 1010 can be omitted. However, if the SF has multiple algorithms requiring different measurements, step 1010 may be necessary to indicate which measurements should be reported. Step 1010 can be performed asynchronously with steps 1007-1009 because the SF can request measurements at any time after the activation request in step 1006, and the UE will only return the measurement results after activating the sensing signal and performing the requested measurement. In some cases, step 1010 can be performed before step 1009, allowing the UE to consider the request from the SF when determining which signal characteristics (e.g., time, angle, and phase) to measure.

[0082] In step 1011, the UE sends a sensing measurement report (e.g., an SCP message) to the SF, containing the information measured from the returned signal in step 1009. When the SF determines that the necessary measurement results have been collected, it sends a sensing deactivation request to the BS in step 1012. Then, the BS sends a sensing deactivation instruction (e.g., a MAC control element) to the UE in step 1013, instructing the UE to stop transmitting the configured sensing signals. The UE can optionally confirm the deactivation in step 1014, which can be omitted if the deactivation cannot fail or no subsequent operation depends on the deactivation time.

[0083] Figure 11 An alternative node arrangement is described according to an embodiment. In this arrangement, SF 1104 is integrated into the first UE 1101, rather than in the network. In this example, SF 1104 is carried by the first UE 1101, while the second UE 1102 acts as a sensing node. A control protocol, such as SCP, for communication between the first UE 1101 (carrying SF 1104) and the second UE 1102 (acting as a sensing node) is responsible for controlling the operation of the second UE, instructing it to send sensing signals and measure signals returned from the sensing target.

[0084] This arrangement functions similarly to the previously described scenario where the SF is integrated into a network node. However, the transport protocol used to carry the SCP message may differ. When the SF 1104 is carried by the UE 1101, the SCP message can be transmitted using a protocol specifically designed for UE-to-UE communication, such as a protocol used for device-to-device (D2D) or sidechain communication scenarios.

[0085] In some embodiments, the SF 1104 carried on the first UE 1101 may communicate with an SF located in the core network (CN) to support sensing functions. Communication between this UE-based SF (e.g., SF 1104) and the CN-based SF may be necessary for coordination, synchronization, or exchange of information related to sensing operations. The exact nature of this communication and the protocols used may depend on the specific implementation and the division of responsibilities between the UE-based and CN-based SFs.

[0086] In some embodiments, the SF 1104 carried on the first UE 1101 can independently support sensing functions without coordination with the CN. In this case, the UE-based SF (e.g., SF 1104) may possess all the information, algorithms, and decision-making capabilities required to manage sensing operations. Autonomous operation may be suitable for scenarios where sensing is localized and does not require network-wide coordination, or for scenarios where the UE operates temporarily without a reliable network infrastructure connection.

[0087] The choice between these two approaches (coordinating with the CN-based SF or operating autonomously) may depend on a variety of factors, such as the specific use case, the scale and complexity of the awareness operation, available network resources, and the required level of control and centralization.

[0088] Figure 12 An exemplary protocol stack is described in the embodiments. The protocol stack is used to transmit SCP between two UEs 1201 and 1202 in a 5G system. In this example, the first UE 1201 and the second UE 1202 communicate using SCP, which is carried directly on top of the Packet Data Convergence Protocol (PDCP) layer.

[0089] However, in some embodiments, the SCP can be encapsulated within an intermediate control protocol layer, such as the PC5 Radio Resource Control (PC5-RRC) protocol, the PC5 Signaling (PC5-S) protocol, or a similar control protocol designed specifically for D2D communication interfaces.

[0090] In the given example, the PDCP layer sits above the RLC layer, which in turn sits above the MAC layer. The MAC layer, in turn, sits above the PHY layer. This arrangement of protocol layers follows the typical structure of a D2D protocol stack in a 5G system.

[0091] In some embodiments, the D2D protocol stack may include... Figure 12 The examples shown are of different layers or different layer organizations. Regardless of the specific structure, the core concept is that SCP can be transmitted through any layer above such a D2D protocol stack.

[0092] Using the D2D protocol stack allows SCP to efficiently transmit between UEs 1201 and 1202 without intermediate network nodes. This direct UE-to-UE communication enables fast and low-latency exchange of sensing control information, which is crucial for coordinating and synchronizing sensing operations between UEs. It should also be noted that D2D communication may support sensing operations when one or more relevant UEs are outside the coverage area of ​​a network node.

[0093] By leveraging existing 5G D2D protocol layers, such as PDCP, RLC, MAC, and PHY, SCP can benefit from the reliable and secure communication mechanisms provided by these layers. This ensures the accurate and timely delivery of sensing control messages, thereby enabling effective collaboration between UEs for sensing purposes.

[0094] Figure 13 A simplified block diagram of a user equipment (UE) 1301 and a network entity 1311 according to an embodiment is shown. The network entity 1311 can be integrated into a base station and is equipped with an antenna 1315 for transmitting and receiving radio signals. The antenna is connected to a radio frequency (RF) transceiver module 1314, which converts received RF signals into baseband signals and sends them to a processor 1313. The transceiver also converts baseband signals from the processor back into RF signals for transmission through the antenna. The processor 1313 processes the baseband signals and invokes various functional modules to perform the functions of the base station 1311. A memory 1312 stores program instructions and data 1320 to control the operation of the base station. Furthermore, the network entity 1311 includes a set of control function modules and circuitry 1390, such as a registration circuitry 1331 for handling registration and mobility procedures, a session management circuitry 1332 for managing sessions, and a configuration and control circuitry 1333 for providing configuration and control parameters to the UE.

[0095] Similarly, UE 1301 includes memory 1302, processor 1303, and RF transceiver module 1304 connected to antenna 1305. The RF transceiver converts received RF signals into baseband signals for the processor and converts baseband signals from the processor back into RF signals for transmission. Processor 1303 processes the baseband signals and invokes various functional modules and circuits to execute UE functions. Memory 1302 stores data and program instructions 1310 for the processor to execute to control UE operation. Suitable processors include dedicated processors, digital signal processors (DSPs), microprocessors, microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and other types of integrated circuits (ICs) or state machines. Software-associated processors can be used to implement and configure the functions of UE 1301.

[0096] UE 1301 also includes a set of functional modules and control circuitry for performing UE tasks. Protocol stack 1360 may include an SCP layer for communicating with sensing functions in the core network, an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and a PHY layer for higher-level configuration and control. System modules and circuitry 1370, implemented and configured by software, firmware, hardware, or a combination thereof, cooperate to enable UE 1301 to perform implementation and functional tasks within the network. These modules include registration circuitry 1321 for performing registration and mobility procedures, and configuration and control circuitry 1324 for processing configuration and control parameters. UE 1311 also includes a sensor 1380 for transmitting sensing signals to a sensing target and measuring the reflected signals from the sensing target. Processor 1303 can then generate measurement reports accordingly. Examples of sensors include laser altimeters, lidar, radar, rangefinders and scatterometers, infrared sensors, multispectral sensors, radiometers, microphones, and cameras. It should be noted that sensor 1380 includes active sensors involved in the measurement of the transmission of sensing signals and their reflection or return.

[0097] The disclosed ISAC control signaling mechanism provides a flexible, scalable, and efficient framework for integrating sensing capabilities into wireless communication networks. By using a dedicated SCP, the system enables the SF (Sensing Provider) to reside in various parts of the network, such as the core network, radio access network, and even user equipment. This flexibility allows the system to adapt to different network architectures and use cases while promoting interoperability between different vendors. Control signaling enables the SF to negotiate and configure sensing parameters according to specific mission requirements, optimizing radio resource allocation and minimizing the impact on communication performance. For UE-based sensing, the separation between the SF and the base station allows for rapid response control of time-critical operations, which is crucial for real-time sensing applications. The modular approach of control signaling separates sensing-specific functions from the underlying communication protocols, promoting independent evolution and optimization of sensing and communication aspects. Furthermore, control signaling enhances coordination among multiple nodes, supports collaborative sensing technologies, and improves the accuracy, reliability, and coverage of sensing results. Overall, the disclosed ISAC control signaling mechanism provides a comprehensive framework for enabling advanced sensing applications while minimizing the impact on communication performance and allowing for the independent evolution of sensing and communication technologies.

[0098] The user equipment (UE) described in this disclosure may include devices with wireless communication capabilities. For example, a UE may include a smartphone (e.g., a handheld touchscreen mobile computing device capable of connecting to one or more cellular networks). A UE may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), pager, laptop computer, desktop computer, wireless phone, or any computing device with a wireless communication interface.

[0099] A UE can also be referred to as a client, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, wireless device, reconfigurable wireless device, or reconfigurable mobile device. A UE can include an Internet of Things (IoT) UE, which may include a network access layer designed for low-power IoT applications, utilizing ephemeral UE connections. IoT UEs can use technologies (e.g., M2M, MTC, or mMTC technologies) to exchange data with MTC servers or devices via a PLMN, other UEs using ProSe or D2D communication, sensor networks, or IoT networks. M2M or MTC data exchange can be machine-initiated. An IoT network describes the interconnection of IoT UEs, which may include uniquely identifiable embedded computing devices within the Internet infrastructure. IoT UEs can execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0100] Furthermore, User Equipment (UE) can connect or communicatively couple to the Radio Access Network (RAN) via a radio interface, which can be a physical communication interface or layer configured to operate with cellular communication protocols such as GSM, CDMA, PTT, POC, UMTS, 3GPP LTE, 5G, and NR. For example, the UE and RAN can exchange control plane data via a Uu interface (e.g., LTE-Uu interface) through a protocol stack including the PHY, MAC, RLC, PDCP, and RRC layers. Downlink (DL) transmissions can be from the RAN to the UE, and uplink (UL) transmissions can be from the UE to the RAN. The UE can also use a sidelink to directly communicate with another UE (not shown) for device-to-device (D2D), point-to-point (P2P), and / or ProSe communication. For example, the ProSe interface may include one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0101] The terminology used in this specification is for describing particular embodiments only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used in describing various embodiments and in the appended claims also include the plural forms. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items. Further understanding is that the terms “comprising,” “including,” “comprises,” and / or “including” as used herein specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0102] As used herein, the term “exemplary” means “as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as superior to the others.

[0103] Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one A, B, or C", "one or more A, B, or C", "at least one A, B, and C", "one or more A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one A, B, or C", "one or more A, B, or C", "at least one A, B, and C", "one or more A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A, B, and C, wherein any such combination may contain one or more members of A, B, or C.

[0104] The terms “coupled,” “connected,” “in connection,” and “electrically connected” are synonyms used to describe the state of an electrical or electronic link. Similarly, when an entity is said to be “communicating” with another entity or multiple entities, it means that the first entity is able to send and / or receive electrical signals to and / or from the second entity. These signals may contain voice or non-voice data / control information, regardless of whether the signals are analog or digital.

[0105] Various exemplary logic blocks, modules, functions, and circuits related to the aspects disclosed herein may be implemented or performed by 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 designed to perform the functions described herein. The processor may be a microprocessor, but alternatively, it may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0106] The aspects described herein can be implemented in hardware and software instructions. These instructions can be stored on various types of computer-readable media, such as random access memory (RAM), flash memory, read-only memory (ROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage media known in the art. In a typical setup, the storage medium is connected to the processor, allowing the processor to read from and write to the medium. Alternatively, the storage medium can be built into the processor itself. Both the processor and the storage medium can reside in an ASIC, which can be located in a remote station. In another configuration, the processor and the storage medium can exist as separate components in a remote station, base station, or server.

[0107] It should also be noted that the operational steps of any exemplary aspect described herein are for illustrative and discussion purposes only. The described operations can be performed in a variety of different orders, and are not limited to the order shown. Furthermore, the operations described in a single operational step can actually be performed through multiple different steps. Additionally, one or more operational steps discussed in the exemplary aspects can be combined. It should be understood that the operational steps shown in the figures may be modified in various ways, which will be apparent to those skilled in the art. Those skilled in the art will also understand that information and signals can be represented using a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips, etc., which may be referenced in the foregoing description, can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0108] In some embodiments, the computation instructions may be executed by an operating system, such as Microsoft Windows, Apple Mac OS X, macOS or iOS, some version of Linux, Google Android, etc.

[0109] In some embodiments, the computers may reside on a distributed computing network, such as a network with any number of clients and / or servers. Each client may run software for implementing the client portion of the embodiments. Furthermore, any number of servers may be provided to handle requests received from one or more clients. Clients and servers may communicate via one or more electronic networks, which in various embodiments may be the Internet, a wide area network, a mobile phone network, a wireless network (e.g., Wi-Fi, 5G, etc.), or a local area network. The network may be implemented using any known network protocol.

[0110] In situations where the aforementioned systems collect user information, users can be provided with the opportunity to opt in or out of programs or features that may collect personal information (e.g., information about user preferences or smart device usage). Furthermore, in some embodiments, certain data may be anonymized in one or more ways before storage or use to remove personally identifiable information. For example, a user's identity may be anonymized so that the user's personally identifiable information cannot be determined or associated, and user preferences or user interactions may be generalized (e.g., based on user demographics) rather than associated with a specific user.

[0111] While some embodiments include the disclosed features and may therefore include additional features not specifically described, other embodiments may substantially exclude or completely exclude undisclosed elements. That is, undisclosed elements may be selectively omitted substantially or completely.

[0112] While some diagrams illustrate multiple logical stages arranged in a specific order, stages that are not dependent on order can be reordered, and others can be merged or decomposed. Although some reorderings or other groupings are specifically mentioned, others are obvious to those skilled in the art, and therefore the orders and groupings presented herein are not an exhaustive list of alternatives. Furthermore, it should be recognized that these stages can be implemented by hardware, firmware, software, or any combination thereof.

[0113] The figures illustrate embodiments or implementations that have been described in detail, and numerous specific details are provided to ensure a thorough understanding of these embodiments. However, it will be apparent to those skilled in the art that the described embodiments can be practiced without relying on these specific details. In some cases, well-known methods, procedures, components, circuits, and networks have been mentioned without detailed explanation to avoid unnecessarily obscuring aspects of the embodiments. Furthermore, it is important to note that the various figures presented and discussed herein, including component diagrams, are for illustrative purposes only and are not necessarily drawn to scale.

[0114] Those skilled in the art will readily observe that numerous modifications and alterations can be made to the apparatus and methods while retaining the teachings of the present invention. Therefore, the foregoing disclosure should be interpreted only by the scope of the appended claims.

Claims

1. A method for sensing and communicating, comprising: A sensing node receives a sensing configuration request from a sensing function. The sensing node responds to the sensing configuration request to determine whether a sensing configuration is supported. as well as Configure a sensing signal of the sensing node according to the sensing configuration.

2. The method of claim 1, further comprising: The sensing node sends a sensing configuration response to the sensing function. The sensing node receives a sensing activation request from the sensing function; as well as Activate the sensing configuration to trigger the sensing node to send the sensing signal according to the sensing activation request.

3. The method of claim 2, further comprising receiving a sensing measurement request from the sensing function by the sensing node to trigger the sensing node to perform a measurement.

4. The method of claim 2, further comprising sending the sensing signal from the sensing node to a sensing target, and measuring a return signal reflected from the sensing target to generate a measurement report.

5. The method of claim 4, further comprising the sensing node sending the measurement report to the sensing function.

6. The method of claim 2, further comprising: The sensing node receives a sensing deactivation command from the sensing function to deactivate the sensing configuration. as well as The sensing node terminates sending the sensing signal according to the sensing deactivation command.

7. The method of claim 1, wherein the perceived configuration request is a Radio Resource Control (RRC) message or a Media Access Control (MAC) control element (CE).

8. A method for sensing and communicating, comprising: A first node receives a sensing configuration request from a sensing function. The first node determines, in response to the perception configuration request, to support a perception configuration for a second node; and Configure a sensing signal for the second node according to the sensing configuration.

9. The method of claim 8, further comprising the first node sending a configuration message to the second node.

10. The method of claim 9, wherein the configuration message is a Radio Resource Control (RRC) message or a Media Access Control (MAC) Control Element (CE).

11. The method of claim 8, further comprising: The first node receives a perception activation request from the perception function. The first node sends a perception activation command to the second node based on the perception activation request; as well as The second node is triggered to send the sensing signal according to the sensing activation instruction.

12. The method of claim 11, wherein the perception activation instruction is an RRC message or a MAC CE.

13. The method of claim 11, further comprising the second node receiving a sensing measurement request from the sensing function.

14. The method of claim 11, further comprising sending the sensing signal from the second node to a sensing target and measuring a return signal reflected from the sensing target to generate a measurement report.

15. The method of claim 14, further comprising sending the measurement report from the second node to the sensing function to trigger the second node to perform a measurement.

16. The method of claim 11, further comprising: The first node receives a perception deactivation request from the perception function. The first node sends a sensing deactivation command to the second node based on the sensing deactivation request; as well as The second node terminates sending the sensing signal according to the sensing deactivation instruction.

17. The method of claim 16, wherein the perception deactivation instruction is an RRC message and / or a MAC CE.

18. The method of claim 8, wherein the first node and / or the second node includes a sensing function.

19. The method of claim 8, wherein the first node is a base station (BS) and the second node is a user equipment (UE).

20. A user equipment (UE) comprising: A sensor for generating a sensing signal; and A processor connected to the sensor is configured as follows: Receive a sensor configuration request from a sensor function; In response to the sensor configuration request, it is determined that a sensor configuration is supported; and Configure the sensing signal according to the sensing configuration.

Images