Sensing in wireless communication system

Abstract

A method, an apparatus and a computer program for communication are described, comprising: receiving a sensing service request from a sensing client of a wireless communication system, the sensing service request comprising information related to a sensing service requested by the sensing client, the sensing service to be provided by the sensing management function; one of single-station sensing for the sensing service, where a first selected radio access network node is used for transmission and reception of radio signals for sensing, and multi-station sensing, where a second selected radio access network node is used for transmission and reception of radio signals for sensing, is selected based at least in part on the information related to the sensing service. Wherein one selected radio access network node is used for transmission of sensed radio signals, and one or more other selected radio access nodes are used for reception of sensed radio signals.

Description

Technical Field

[0001] The present description relates to sensing in wireless communication systems. Background Art

[0002] This specification relates to sensing in wireless communication systems, such as obtaining an awareness of a scene surrounding a sensing device. Example applications include detecting or tracking objects and extracting features for identification or classification purposes. Further developments are still needed in this area. Summary of the invention

[0003] In a first aspect, the specification describes an apparatus (e.g., a sensing management function (SeMF)), comprising: at least one processor; and at least one memory storing instructions of the sensing management function, wherein execution of the instructions causes the apparatus to at least perform: receiving a sensing service request from a sensing client (e.g., a UE, an application function (AF), or a network function (NEF) of a wireless communication system), the sensing service request comprising information related to a sensing service requested by the sensing client, the sensing service to be provided by the sensing management function (the sensing service request may include information such as sensing QoS, sensing type, sensing requirements (e.g., sensing area), etc.); selecting one of the following items based at least in part on the information related to the sensing service: a single station (monostati c) sensing, wherein a first selected radio access network node is used for transmission and reception of radio signals for sensing, and multi-static sensing, wherein one selected radio access network node is used for transmission of radio signals for sensing, and one or more other selected radio access nodes are used for reception of radio signals for sensing; selected based on single-station sensing: sending a sensing configuration of the first selected radio access network node to the first selected radio access network node used for transmission and reception of radio signals for sensing; and selected based on multi-station sensing: sending a sensing configuration of a selected radio access network node to a selected radio access network node used for transmission of radio signals for sensing. Multi-station sensing encompasses dual-station sensing (e.g. comprising one transmitter and one receiver).

[0004] In some example embodiments, the sensing configuration of the first selected radio access network node used for transmission and reception of radio signals for sensing includes at least one of: a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration. Thus, the apparatus may configure mono-static sensing.

[0005] In some example embodiments, the sensing configuration of a selected radio access network node for transmission of a radio signal for sensing comprises at least one of: a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration. Thus, the apparatus may configure multi-station (eg, dual-station) sensing.

[0006] Based on multi-station sensing being selected, execution of the instructions may also cause the apparatus to at least perform: sending a sensing configuration of a corresponding other radio access network node to each corresponding other radio access network node (e.g., a second node in a dual-station case) used for reception of a radio signal. In some example embodiments, the sensing configuration of each corresponding other radio access network node includes at least one of the following items: a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration.

[0007] The information related to the sensing service may include at least one of the following items: a sensing service type of the sensing service; a sensing requirement of the sensing service; and a sensing service quality of the sensing service. For example, the sensing requirement of the sensing service may include a sensing area of ​​the sensing service.

[0008] In some example embodiments, sending the sensing configuration of the first selected radio access network node (e.g. in a single station case) comprises sending a request to the first selected radio access network node for establishing a sensing session for a sensing service, the request comprising the sensing configuration of the first selected radio access network node.

[0009] Execution of the instructions may further cause the apparatus to perform at least sending a request for a radio access network node to initiate sensing to a first selected radio access network node (eg, in a single station case) used for transmission and reception of radio signals for sensing.

[0010] The execution of the instructions may also cause the device to perform at least one of the following: receiving sensing data from a first selected radio access network node used for transmission and reception of radio signals for sensing; and receiving sensing data from one or more other selected radio access network nodes (e.g., in a multi-station case) used for reception of radio signals for sensing. Moreover, the execution of the instructions may also cause the device to perform: processing the sensing data (e.g., at the SeMF) to generate sensing output data; and providing the sensing output data (e.g., to a sensing client).

[0011] In some example embodiments, sending a sensing configuration of a selected radio access network node (e.g., in a multi-station case) includes: sending a request to a selected radio access network node for establishing a sensing session for a sensing service, the request including the sensing configuration of the selected radio access network node. The request may also include an indication that the selected radio access network node initiates sensing.

[0012] In some example embodiments, execution of the instructions further causes the apparatus to at least perform: controlling session admission, in which a determination is made as to whether the corresponding selected network node is capable of meeting defined requirements. The requirements may relate to, for example, available resources and / or the ability to meet quality of service (QoS) requirements.

[0013] In a second aspect, the present specification describes an apparatus (e.g., a RAN node) comprising: at least one processor; and at least one memory storing instructions, wherein execution of the instructions causes the apparatus to at least perform: receiving a sensing configuration of a sensing service at a radio access network node of a wireless communication system from a sensing management function of the wireless communication system (e.g., including at least one of a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration), wherein the sensing configuration configures at least one of the following items: single-station sensing for the sensing service, wherein the radio access network node is a first selected radio access network node used for transmission and reception of radio signals for sensing, and multi-station sensing, wherein the radio access network node is a selected radio access network node for transmission of radio signals for sensing, or a radio access node among one or more other selected radio access nodes used for reception of radio signals for sensing; configuring the radio access node according to the sensing configuration; and causing the radio access network node to initiate sensing.

[0014] In some example embodiments, execution of the instructions further causes the apparatus to perform at least one of: transmission of a radio signal for sensing; and reception of a radio signal for sensing.

[0015] Execution of the instructions may further cause the apparatus to perform at least one of: providing the received radio signal to the sensing management function; and processing the received radio signal and providing the received radio signal to the sensing management function.

[0016] Execution of the instructions may also cause the apparatus to perform at least receiving a request for a radio access network node to initiate sensing.

[0017] Execution of the instructions may further cause the apparatus to perform control session admission in which a determination is made as to whether sufficient resources are available to satisfy the sensing requirements included in the session establishment message.

[0018] Execution of the instructions may also cause the device to perform: in response to a request to establish a sensing session, provide a sensing session establishment response, which may include: an indication of accepting the request to establish a sensing session, an indication of rejecting the request to establish a sensing session, a new and / or updated sensing configuration for the sensing session, and / or an indication of resources allowed for the sensing session.

[0019] Execution of the instructions may further cause the apparatus to send information regarding the updated sensing configuration.

[0020] In an alternative embodiment, the transmitting RAN entity may identify and / or discover the receiving RAN entity and then perform the inter-RAN entity interactions discussed above.

[0021] In a third aspect, the present specification describes a method, comprising: receiving a sensing service request from a sensing client of a wireless communication system, the sensing service request comprising information related to a sensing service requested by the sensing client (such as a UE, an application function (AF) or a network function (NEF) of the wireless communication system), the sensing service to be provided by a sensing management function; selecting one of the following items based at least in part on the information related to the sensing service: single-station sensing for the sensing service, wherein a first selected radio access network node is used for transmission and reception of radio signals for sensing, and multi-station sensing, wherein one selected radio access network node is used for transmission of radio signals for sensing and one or more other selected radio access nodes are used for reception of radio signals for sensing; being selected based on single-station sensing: sending a sensing configuration of a first selected radio access network node to a first selected radio access network node used for transmission and reception of radio signals for sensing; and being selected based on multi-station sensing: sending a sensing configuration of a selected radio access network node to a selected radio access network node used for transmission of radio signals for sensing. For example, the method can be implemented at a sensing management function (SeMF).

[0022] The sensing configuration of the first selected radio access network node used for transmission and reception of radio signals for sensing may include at least one of: sensing resource configuration, sensing session configuration and sensing data reporting configuration. Thus, the apparatus may configure single-station sensing.

[0023] The sensing configuration of a selected radio access network node used for transmission of radio signals for sensing may include at least one of: sensing resource configuration, sensing session configuration and sensing data reporting configuration. Thus, the apparatus may configure multi-station (eg dual-station) sensing.

[0024] Based on multi-station sensing being selected, the method may comprise sending the sensing configuration of the respective other radio access network node to each respective other radio access network node used for reception of radio signals (eg the second node in a dual-station case).

[0025] In some example embodiments, sending the sensing configuration of the first selected radio access network node (e.g. in a single station case) comprises sending a request to the first selected radio access network node for establishing a sensing session for a sensing service, the request comprising the sensing configuration of the first selected radio access network node.

[0026] The method may comprise sending a request of the radio access network node to initiate sensing to a first selected radio access network node (eg in a single station case) used for transmission and reception of radio signals for sensing.

[0027] The method may also include receiving sensing data from a first selected radio access network node used for transmission and reception of radio signals for transmission, and receiving sensing data from one or more other selected radio access network nodes used for reception of radio signals for sensing (e.g. in a multi-station case). Moreover, the method may include processing (e.g. at the SeMF) the sensing data to generate sensing output data; and providing the sensing output data (e.g. to a sensing client).

[0028] In some example embodiments, sending a sensing configuration of a selected radio access network node (e.g., in the case of determining a multi-station sensing method) includes sending a request to a selected radio access network node to establish a sensing session for a sensing service, the request including the sensing configuration of the selected radio access network node. The request may also include an indication that the selected radio access network node initiates sensing.

[0029] The method may include controlling session admission in which a determination is made as to whether a respective selected network node is able to meet defined requirements.

[0030] In a fourth aspect, the specification describes a method, comprising: receiving a sensing configuration of a sensing service at a radio access network node of a wireless communication system from a sensing management function of the wireless communication system, wherein the sensing configuration (e.g., including at least one of a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration) configures one of: single-station sensing for the sensing service, wherein the radio access network node is a first selected radio access network node used for transmission and reception of a radio signal for sensing, and multi-station sensing, wherein the radio access network node is a selected radio access network node used for transmission of the radio signal for sensing or a radio access node in one or more other selected radio access nodes for reception of the radio signal for sensing; configuring the radio access node according to the sensing configuration; and causing the radio access network node to initiate sensing. The method may be implemented, for example, at a RAN node.

[0031] The method may also include transmission of a radio signal for sensing and reception of a radio signal for sensing.

[0032] The method may further include providing the received radio signal to the sensing management function, and processing the received radio signal and providing the processed received radio signal to the sensing management function.

[0033] The method may further include receiving a request for the radio access network node to initiate sensing.

[0034] The method may also include controlling session admission in which a determination is made as to whether sufficient resources are available to satisfy the sensing requirements included in the session establishment message.

[0035] The method may also include providing a sensing session establishment response in response to the request to establish the sensing session. The sensing session establishment response may include an indication of accepting the request to establish the sensing session, an indication of rejecting the request to establish the sensing session, an indication that a new and / or updated sensing configuration is required, or information indicating resources allowed for the sensing session.

[0036] The method may further include sending information regarding the updated sensing configuration.

[0037] The method may further comprise exchanging configuration and data between different radio access network nodes configured by the sensing management function for use during multi-site sensing.

[0038] In an alternative embodiment, the transmitting base station may identify / discover the receiver base station and then perform the inter-base station interaction discussed above.

[0039] In a fifth aspect, the present specification describes computer readable instructions which, when executed by a computing device, cause the computing device to perform (at least) any method described herein (including the method of the third aspect or the fourth aspect above).

[0040] In a sixth aspect, the present specification describes a computer-readable medium (such as a non-transitory computer-readable medium) comprising program instructions stored thereon to perform (at least) any method described herein (including the method of the third aspect or the fourth aspect described above).

[0041] In a seventh aspect, the present specification describes a device comprising: at least one processor; and at least one memory comprising computer program code, which, when executed by at least one processor, causes the device to perform (at least) any method described herein (including the method of the third aspect or the fourth aspect above).

[0042] In an eighth aspect, the present specification describes a device comprising: at least one processor; and at least one memory storing instructions, which, when executed by at least one processor, causes the device to perform (at least) any method described herein (including the method of the third aspect or the fourth aspect above).

[0043] In a ninth aspect, the present specification describes a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to: receive a sensing service request from a sensing client of a wireless communication system, the sensing service request comprising information related to a sensing service requested by the sensing client, the sensing service to be provided by a sensing management function; select one of the following items based at least in part on the information related to the sensing service: single-station sensing for the sensing service, wherein a first selected radio access network node is used for transmission and reception of a radio signal for sensing, and multi-station sensing, wherein one selected radio access network node is used for transmission of a radio signal for sensing, and one or more other selected radio access nodes are used for reception of a radio signal for sensing; selected based on single-station sensing: sending a sensing configuration of a first selected radio access network node to a first selected radio access network node used for transmission and reception of a radio signal for sensing; and selected based on multi-station sensing: sending a sensing configuration of a selected radio access network node to a selected radio access network node used for transmission of a radio signal for sensing.

[0044] In a tenth aspect, the present specification describes a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to: receive a sensing configuration of a sensing service at a radio access network node of a wireless communication system from a sensing management function of the wireless communication system, wherein the sensing configuration configures one of the following items: single-station sensing for the sensing service, wherein the radio access network node is a first selected radio access network node used for transmission and reception of a radio signal for sensing, and multi-station sensing, wherein the radio access network node is a selected radio access network node used for transmission of a radio signal for sensing or one of one or more other selected radio access nodes used for reception of a radio signal for sensing; configure the radio access node according to the sensing configuration; and cause the radio access network node to initiate sensing.

[0045] In an eleventh aspect, the present specification describes an input of a SEMF module (or some other component) for receiving a sensing service request from a sensing client of a wireless communication system, the sensing service request including information related to the sensing service requested by the sensing client, the sensing service to be provided by a sensing management function; a control module (or some other component) for selecting one of the following items based at least in part on the information related to the sensing service: single-station sensing for the sensing service, wherein a first selected radio access network node is used for transmission and reception of a radio signal for sensing, and multi-station sensing, wherein one selected radio access network node is used for transmission of a radio signal for sensing, and one or more other selected radio access nodes are used for reception of a radio signal for sensing; an output of the SEMF module (or some other component) for sending a sensing configuration of a first selected radio access network node to a first selected radio access network node used for transmission and reception of a radio signal for sensing, selected based on single-station sensing; and an output of the SEMF module (or some other component) for sending a sensing configuration of a selected radio access network node to a selected radio access network node used for transmission of a radio signal for sensing, selected based on multi-station sensing.

[0046] In a twelfth aspect, the present specification describes an input of a RAN module (or some other component) for receiving a sensing configuration of a sensing service at a radio access network node of a wireless communication system from a sensing management function of the wireless communication system, wherein the sensing configuration configures one of the following items: single-station sensing for the sensing service, wherein the radio access network node is a first selected radio access network node used for transmission and reception of radio signals for sensing, and multi-station sensing, wherein the radio access network node is a selected radio access network node used for transmission of radio signals for sensing or a radio access node among one or more other selected radio access nodes for reception of radio signals for sensing; a control module (or some other component) for configuring the radio access node according to the sensing configuration; and a control module (or some other component) for causing the radio access network node to initiate sensing. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Example embodiments will now be described by way of non-limiting example with reference to the following schematic diagrams, in which:

[0048] Figure 1 is a block diagram illustrating a single-station sensing system according to an example embodiment;

[0049] Figure 2 is a block diagram illustrating a bistatic sensing system according to an example embodiment;

[0050] Figure 3 is a block diagram illustrating a system according to an example embodiment;

[0051] Figures 4 to 7 is a flowchart illustrating a method or process according to an example embodiment;

[0052] Figures 8 to 12 shows a message flow sequence and process operation according to an example embodiment;

[0053] Fig.13 is a schematic diagram of components of one or more of the previously described example embodiments; and

[0054] Fig.14 A tangible medium for storing computer readable code is shown, which when executed by a computer can perform a method according to the example embodiments described herein. DETAILED DESCRIPTION

[0055] The scope of protection sought by various embodiments of the present invention is set out by the independent claims. Embodiments and features described in this specification that do not belong to the scope of the independent claims, if any, are to be construed as examples useful for understanding various embodiments of the present invention.

[0056] Like reference numerals refer to like elements throughout the specification and drawings.

[0057] The present specification relates to sensing in a wireless communication system, for example to obtain awareness of a scene surrounding a radio access network entity configured as a sensing device. For example, this may include the ability to perform one or more of the following:

[0058] ●Detection, localization and / or tracking of objects;

[0059] ● forming an image of a specific scene or environment; and / or

[0060] ●Identify features of discovered objects for identification and / or classification, etc.

[0061] Wireless communication systems in which sensing and communication are integrated are generally referred to as integrated sensing and communication systems. The integrated sensing and communication (ISAC) system described herein can potentially achieve relatively high data rate communications and relatively high resolution object detection using at least some of the same hardware and spectrum resources. For example, this may be beneficial for improving sensing accuracy in scenarios or situations where existing sensing technologies may not perform well (e.g., non-line of sight (NLOS) conditions, requirements for high-speed resolution, etc.), improving spectral efficiency by sharing communication and sensing spectrum, and / or reducing hardware costs by combining sensing and communication equipment / hardware.

[0062] Example scenarios where the Integrated Sensing and Communication (ISAC) system may be used include (but are not limited to) the following:

[0063] ● Intrusion detection (e.g. intruder detection in smart homes, pedestrian or animal intrusion detection on highways, etc.)

[0064] ● Support for autonomous driving (e.g., sensing to assist vehicle maneuvering and navigation by providing additional information for objects detected on the road (such as pedestrians, bicycles, other vehicles, etc.), sensing for parking space determination, etc.)

[0065] ● Support for unmanned aerial vehicle (UAV) flights (e.g., UAV flight trajectory tracking, network-assisted sensing to avoid UAV collisions by providing information about objects detected in the air, especially those that may not have a communications component to indicate their presence)

[0066] ●Support for automated guided vehicles (AGVs) or autonomous mobile robots (AMRs) in factories (e.g. AGV detection and tracking in factories), AMR collision avoidance in smart factories, etc.

[0067] ●Environmental and / or weather monitoring (e.g., rainfall, pollution, flooding)

[0068] ●Health monitoring (e.g. fall detection, contactless sleep monitoring services)

[0069] ●Extended reality (XR) applications.

[0070] Figure 1 is a block diagram illustrating a single-station sensing system of a wireless communication system, generally indicated by reference numeral 10, according to an example embodiment. The single-station sensing system 10 comprises a first radio access network entity 14 (a gNB in ​​the example shown). When the first radio access network entity 14 is configured for a sensing operation (e.g., a single-station sensing operation), the first radio access network entity 14 emits (e.g., transmits) a sensing signal (e.g., an RF signal). Thus, when configured for single-station sensing, the first radio access network entity 14 is considered to be (or acts as) a sensing transmitter. When the first radio access network entity 14 is configured for a sensing operation (e.g., a single-station sensing operation), the first radio access network entity 14 also receives sensing signals (e.g., radio signals), which are, for example, deflected, reflected or refracted by an object (e.g., object 12) in the vicinity of the first radio access network entity 14. Thus, when configured for a single-station sensing operation, the first radio access network entity 14 is also considered to be or acts as a sensing receiver.

[0071] Figure 2 is a block diagram illustrating a bi-station sensing system of a wireless communication system, generally indicated by reference numeral 20, according to an example embodiment. The sensing system 20 includes a first radio access network entity 24 (a gNB in ​​the example shown) and a second radio access network node 26 (also a gNB in ​​the example shown). When configured for a sensing operation (e.g., a bi-station sensing operation), the first radio access entity 24 emits a sensing signal (e.g., a radio signal). Thus, when configured for a bi-station sensing operation, the first radio access network entity 26 is thereby configured to or considered to act as a sensing transmitter). When the second radio access network entity is configured for a sensing operation (e.g., a bi-station sensing operation), the second radio access network entity 26 receives a sensing signal deflected, reflected, or refracted by an object (e.g., object 22) located in the vicinity of the second radio access network entity 26. Thus, when the second radio access network entity 26 is configured for a bi-station sensing operation, the second radio access network entity 26 is configured to or considered to act as a sensing receiver).

[0072] In the sensing system 10, the first radio access network entity 14 receives a sensing signal (e.g., a radio signal) that is, for example, deflected, reflected, or refracted by an object (e.g., object 12). Similarly, in the sensing system 20, the second radio access network entity 26 receives the sensing signal. In the sensing systems 10 and 20, the sensing measurement data (or sensing data / sensing measurement information) includes data derived from the sensing signals (e.g., radio signals) that are affected (e.g., reflected, refracted, diffracted) by an object (e.g., object 12 or 22) in the environment of interest when performing a sensing operation, and are optionally processed (e.g., by a network function within a wireless communication system such as a 5G and / or 6G system, a server outside the wireless communication system, an application server connected to the wireless communication system via, for example, a network open function of the wireless communication system, an edge server (e.g., a server located near the wireless communication server), etc.). And the sensing output(s) include processed sensing data, such as sensing data requested by a sensing service consumer (or sensing service client) of a sensing service provided by a 5G and / or 6G system including the sensing system 10 and / or the sensing system 20.

[0073] Examples of sensing data or sensing measurement information include information about one or more electromagnetic signals in information about received or arriving electromagnetic signals. Information about received or arriving electromagnetic signals may include received power, delay, departure angle, arrival angle, Doppler shift, etc. of the received or arriving electromagnetic signals.

[0074] Thus, the systems 10 and 20 differ in that in the single-station sensing system 10, the first radio access node 14 is configured as or acts as a sensing transmitter and a sensing receiver, whereas in the dual-station sensing system 20, different radio access network nodes are configured as or act as sensing transmitters and receivers. Note also that the dual-station sensing system 20 is a special case of a multi-station sensing system, where one radio access network entity is configured as or acts as a sensing transmitter, and multiple radio access network entities are configured as or act as sensing receivers.

[0075] In the single-station sensing system 10 and the dual-station sensing system 20, both the sensing transmitter and the receiver are radio access network entities (eg, BS, gNB); this is not necessary for all example embodiments.

[0076] As described herein, sensing operations of a sensing session performed by a radio access network entity can be used in the context of a public land mobile network (PLMN) (including a communication system including a radio access network node) and in the context of a standalone non-public network (SNPM) (including a communication system including a radio access network node).

[0077] Figure 3is a block diagram illustrating a wireless communication system supporting or providing sensing services according to an example embodiment, generally indicated by reference numeral 30. The wireless communication system 30 includes a sensing management module 32 that implements or includes a sensing management function (SeMF) for providing sensing services to a sensing service client 34, and one or more entities 36 of a radio access network (generally referred to as RAN entities 36 and collectively referred to as RAN entities 36). As discussed further below, the sensing client 34 may be a user equipment (e.g., UE), an application function (AF), or a network exposure function (NEF) of a wireless communication system (e.g., 5G or similar system).

[0078] A sensing management module 32 is provided to configure, coordinate and enable sensing operations for one or more RAN entities 36. The sensing management module 32 may be, may implement or may include a sensing management function (SeMF) discussed in detail below.

[0079] As used herein, the term "sensing management module" refers to a combination of hardware processing circuitry and software and / or firmware (including machine-readable instructions executable by the hardware processing circuitry) or software including machine-readable instructions executable by the hardware processing circuitry of the device. The hardware processing circuitry includes at least one processor and at least one memory storing machine-readable instructions, the processor including machine-readable instructions executable by the hardware processing circuitry. The processor may include any one or some combination of an accelerator, a microprocessor, a core of a multi-core microprocessor, a microcontroller, a programmable integrated circuit, a programmable gate array, a digital signal processor, a central processing unit, a graphics processing unit, a tensor processing unit. The memory may include any one or some combination of volatile or non-volatile memory (e.g., flash memory, cache, random access memory (RAM) and / or read-only memory (ROM)). The memory 112 may store machine-executable instructions of the software and / or firmware for execution by at least one processor of the hardware processing circuitry. The software and / or firmware may implement or include SeMF, and the machine-executable instructions may be executed by the hardware processing circuitry to perform the actions or operations of the method of SeMF described herein.

[0080] The SeMF implemented or included in the sensing management module 32 may receive sensing requests for different types of sensing services provided by the SeMF from the sensing client 34, determine the sensing method to be performed (e.g., whether to use single-station or multi-station (e.g., dual-station) sensing), and determine one or more RAN entities 36 to participate in the sensing operation based on the determined sensing method and the sensing role of the corresponding RAN entity. For example, for each of the one or more RAN entities, the SeMF implemented or included in the sensing management module 32 may determine a sensing configuration, including: a sensing resource configuration; a sensing session configuration (e.g., a RAN entity that sends a sensing signal (sensing transmitter (Tx role)) and / or a RAN entity (or multiple RAN entities) that receives the corresponding sensing signal (sensing receiver (Rx) role)); and a sensing data report configuration.

[0081] The SeMF implemented or included in the sensing management module 32 interacts with one or more RAN entities 36 and sends the determined sensing configuration to the one or more RAN entities 36 (for example, during a sensing session establishment process for establishing a session for sensing services, generally referred to as a sensing session in this document).

[0082] SeMF can be configured to determine or calculate sensing output according to the request. The sensing output may include, for example, processed sensing data requested by a sensing service client (e.g., sensing client 34). For example, the processed sensing data may be sensing data that has been processed by SeMF. The processed sensing data may include data about objects in the area and / or data about features or data about these objects. For example, one or more of the position, speed, velocity, shape, material and / or size of the object may be data about the objects in the area. SeMF may alternatively or additionally be configured to provide sensing data received or collected from one or more sensing devices as sensing output. If the sensing service client has requested the sensing data, SeMF may provide the sensing data to the sensing service client.

[0083] The sensing service client 34 may be, for example:

[0084] • Application functionality (eg trusted by the Public Land Mobile Network (PLMN)), and the request may be received directly from the Sensing Service Client.

[0085] • Application functions and requests received from sensing service clients via network open functions.

[0086] ●User equipment.

[0087] • Another network entity, such as a RAN node and / or a network function of the wireless communication system, such as a network function of a core network of the wireless communication system.

[0088] The RAN entity 36 may be, for example, a base station (e.g., an evolved Node B (eNB) or a gNB) or another entity having at least some sensing functionality (i.e., the sensing functionality may include at least one of the following: providing sensing and / or positioning measurements, sending signals for sensing and / or positioning), and may be a new network node (e.g., dedicated for sensing purposes, a sensing unit) or a part of an existing network node (e.g., a positioning reference unit, a reconfigurable smart surface). The RAN entity may validate and implement the sensing configuration received from the sensing management module 32. The RAN entity 36 may also perform sensing admission control on sensing resources for sending (Tx) and / or receiving (Rx) sensing signals(s), and update and / or select the sensing configuration of the RAN entity 36, which is then provided to the sensing management module 32 and / or other RAN entities (e.g., via an Xn interface). Then, any RAN entity 36 operating as a sensing receiver may obtain the sensing data and provide the sensing data to the sensing management module 32 (with or without processing the sensing data), according to the sensing data reporting configuration for processing the sensing data to derive the sensing output.

[0089] As discussed above, the sensing management module 32 may be, may implement or may include a sensing management function (SeMF). The sensing management module may be provided or included in a communication system such as 5GS. The SeMF may be a dedicated network function for a core network of a communication system (e.g., a network function for 5GC (5G core network of 5GS) or a dedicated network function for one or more RAN entities 36). In some embodiments, the SeMF (e.g., the functionality of the SeMF) may be integrated into existing network functions of a wireless communication system (e.g., existing network functions of 5GS or 5GC of 5GS), such as a location management function (LMF) that provides location services for locating user equipment in 5GS. In some embodiments, the functionality of the SeMF may be distributed across multiple different network functions of the core network (e.g., NEF, LMF, GMLC, AMF), or may be integrated into one or more RAN entities 36).

[0090] In an example implementation, SeMF may:

[0091] ● Determine a sensing method (e.g. single-site sensing, dual-site sensing or multi-site sensing), and determine a sensing configuration of a RAN entity (e.g. BS, such as a gNB) identified or selected to participate in a sensing session of the determined sensing method, taking into account a) requirements included in a sensing service request received from a sensing service client 34 (e.g. sensing area of ​​the sensing service, QoS requirements of the sensing service) and b) static and / or dynamic sensing capabilities of the RAN entity. In the case where the determined sensing method is single-site sensing, the SeMF may identify or select one or more RAN entities to participate, and determine or generate a sensing configuration for the one or more RAN entities to configure the one or more RAN entities as a sensing transmitter (Tx) and a sensing receiver (Rx) based on the determined sensing method, and provide the sensing configuration to the one or more RAN entities. Alternatively, in case of determining dual-station sensing and / or multi-station sensing, one RAN entity is identified or selected as a sensing transmitter and one or more other RAN entities (e.g., BS) are identified or selected as sensing receivers, and a sensing configuration for configuring one RAN entity as a sensing transmitter and a sensing configuration for configuring one or more other RAN entities (e.g., BS) as sensing receivers are determined or identified.

[0092] ● Perform sensing admission control, which identifies whether the identified or selected RAN entity has available sensing resources (e.g., sensing requirements) for the requested sensing service, and determines the sensing resource configuration of the identified or selected RAN entity. Depending on the method or scheme selected for single-station, dual-station, or multi-station approach implementation, the sensing resource configuration may include reference signals and / or pilots and / or user data and control plane resources.

[0093] ● According to the selected sensing method (single-station, dual-station or multi-station sensing), a sensing session establishment request is sent to one or more RAN entities to establish a sensing session, including one or more of the following: sensing configuration for each corresponding selected RAN entity for configuring the corresponding RAN entity as a sensing transmitter and / or sensing receiver; sensing resource configuration; sensing session configuration; sensing data reporting configuration, i.e., whether control plane-based reporting or user plane (e.g. to a dedicated server or via a dedicated server) will be used to transmit sensing measurements (sensing data) from the RAN entity (e.g. BS) to the SeMF, resources and configuration for reporting; one or more identifiers for the sensing session. Each identifier of a sensing session identifies a sensing session and is generally referred to as a sensing session identifier and collectively referred to as sensing session identifiers).

[0094] ● Generate a sensing session identifier (ID) for the determined sensing method and assign it to one or more RAN entities participating in the selected sensing session, the sensing session identifier (ID) being used to uniquely identify and coordinate sensing operations between different RAN entities and for sending sensing measurements and / or sensing data belonging to the same sensing session from the RAN entity (or RAN entities) to the SeMF.

[0095] In the context of the same sensing session, one or more single-station sensing operations or one or more multi-station sensing operations may be initiated. Moreover, the same RAN entity may participate in one or more single-station sensing operations and one or more multi-station sensing operations. In addition, a RAN entity may be identified or selected as a sensing transmitter and may be configured to send sensing signals based on a sensing configuration, and / or may be identified or selected as a sensing receiver and may be configured to receive sensing signals based on a sensing configuration. Each of the one or more RAN entities 36 of the system 30 may be a base station (BS) or some other entity with sensing capabilities (e.g., a dedicated unit or element for receiving sensing signals, a reconfigurable smart surface with integrated sensing capabilities or for assisting ISAC). Each RAN entity 36 may:

[0096] ● Send a response to the sensing session establishment request to the SeMF. The response to the sensing session establishment request includes an indication of acceptance (success) or failure to provide and / or support and / or establish the sensing session. The response to the sensing session establishment request may also include a reason code indicating the reason for the failure to provide and / or support and / or establish the sensing session.

[0097] ● After establishing the sensing session, perform self-configuration according to the received sensing resource configuration and sensing session configuration, and enable the corresponding RAN entity to perform sensing operations.

[0098] ● When involved in a sensing session (eg identified by a sensing session ID) and configured as a sensing receiver, sending corresponding sensing data (eg measurement values ​​obtained when the RAN entity performs sensing operations) to the SeMF.

[0099] • Optionally perform sensing admission control and determine sensing resources for sending or receiving sensing signals based on the sensing resource configuration received from the SeMF.

[0100] The interaction between the SeMF and (multiple) RAN entities may occur through a direct interface (e.g. in the case where the core network has a service-based architecture) or through the AMF. The AMF may transparently route messages between RAN entities (e.g. access nodes) and the SeMF through an interface (e.g. NG-C interface) using a non-UE associated mode. The Next Generation Application Protocol (NGAP) protocol terminated between the AMF and the RAN entity (e.g. NG-RAN node) may be used as a transport protocol for transporting sensing protocol messages through the NG-C interface.

[0101] In some embodiments, admission control may be performed by a RAN entity (e.g., a BS). The SeMF may provide information to the RAN entity (e.g., a BS), such as a requested QoS for the sensing session, an indication of the requested sensing service type, sensing requirements for the sensing session (e.g., sensing area, sensing duration, sensing update rate, etc.), which may allow one or more RAN entities (e.g., a BS) to determine the resources required for the sensing session. A RAN entity (e.g., a BS) configured as or acting as a sensing sender (e.g., having a sensing sending role (e.g., when the SeMF selects the RAN entity to participate in a dual-station sensing method)) may provide its sensing resource configuration (e.g., sensing signal frequency, bandwidth, timing of the RAN entity (e.g., a BS) sending sensing signals) and / or sensing session configuration, for example, via an Xn interface (inter-RAN entity) to: one or more RAN entities (e.g., a BS) configured as or acting as a sensing receiver (e.g., having a sensing receiving role) for the corresponding sensing session; or a SeMF, for example, via an NG interface; or an AMF, for example, using a mechanism similar to remote interference management (RIM) information transmission.

[0102] Figure 4 4 is a flow chart illustrating a method or process according to an example embodiment, generally indicated by reference numeral 40. The method or process 40 may be performed by a SeMF implemented or included in the sensing management module 32 described above.

[0103] The method or process 40 begins at operation 42, where a sensing service request is received (e.g., at the sensing management module 32) from a sensing service client (such as the sensing client 34). The sensing service request is a request for a sensing service supported or provided by the sensing management module 32. The sensing service request includes information related to the sensing service requested by the sensing client. Example information related to the sensing service that may be included in the sensing service request includes at least one of the following: an indication of a sensing service type of the sensing service; information indicating a sensing requirement for the sensing service; an indication of a quality of service of the sensing service; and information indicating a sensing area of ​​the sensing service.

[0104] In operation 44, a sensing method (e.g., a sensing mode) is selected based at least in part on the information related to the sensing service (e.g., included in operation 42). Operation 44 may involve selecting between one of: single-station sensing for the sensing service, in which a first RAN entity (e.g., a radio access network node) is used for transmission and reception of radio signals for sensing, and multi-station sensing (e.g., dual-station sensing), in which one selected radio access network node is used for transmission of radio signals for sensing, and one or more other selected radio access nodes are used for reception of radio signals for sensing.

[0105] In operation 46, sensing configuration information is sent (e.g., from the sensing management module 32 to the RAN entity 36). For example, if single-site sensing is selected in operation 44, operation 46 may involve sending a sensing configuration of the first RAN entity (e.g., a radio access network node) used for transmission and reception of radio signals for sensing (e.g., the sensing configuration may include at least one of a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration). If multi-site (e.g., dual-site) sensing is selected in operation 44, operation 46 may involve sending a sensing configuration of a selected radio access network node (e.g., the sensing configuration may include at least one of a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration) to a selected radio access network node used for transmission of radio signals for sensing.

[0106] Moreover, in the case where multi-station sensing is selected, operation 46 may also include sending a sensing configuration of the corresponding other radio access network node to each corresponding other radio access network node for reception of radio signals. It should be noted that the sensing configuration of the (multiple) corresponding other radio access nodes may be sent by one of the RAN nodes 36 (e.g., another node in the case of dual stations) instead of by the sensing management module 32. As with the sensing configuration example discussed above, the sensing configuration of each corresponding other radio access network node may include at least one of a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration.

[0107] Figure 5 is a flow chart illustrating a method or process according to an example embodiment, generally indicated by reference numeral 50. The method or process 50 may be implemented at the sensing service client 34 of the system 30 described above.

[0108] The method or process 50 begins at operation 52, where a sensing session is initiated. The initiation of the sensing session may form part of the sensing configuration operation 46 described above. In some example embodiments, the initiation of the sensing session may be achieved only after a verification process that determines that the corresponding RAN entity is capable of initiating the sensing session for the requested sensing service. Operation 52 may include sending a request to the corresponding RAN entity for the RAN entity to initiate sensing.

[0109] In operation 54, sensing data is received. The sensing data may be received from a first selected radio access network node used for transmission and reception of radio signals for sensing (when the first selected radio access network node is configured for single-station sensing). Alternatively, the sensing data may be received from one or more other selected radio access network nodes used for reception of radio signals for sensing (when the first radio access network node and the one or more other radio access network nodes are configured for multi-station sensing).

[0110] As discussed in detail below, the sensing data may be processed in some manner. For example, the sensing data may be processed at the corresponding RAN or sensing management module 32, and the processed data provided to the sensing service client 34 (in response to an original request from the sensing client).

[0111] Figure 6 is a flow chart illustrating a method or process according to an example embodiment, generally indicated by reference numeral 60. The method or process 60 may be implemented at one of the one or more RAN entities 36 of the system 30 described above.

[0112] The method or process 60 begins at operation 62, where a sensing configuration for a sensing service is received at a RAN entity (e.g., a radio access network node of a wireless communication system) from a sensing management function of the communication system (e.g., a sensing management module 32). The sensing configuration may be sent in operation 46 above and may be used by the RAN entity to self-configure for one of single-site sensing (wherein the radio access network node is a first selected radio access network node for transmission and reception of radio signals for sensing) and multi-site sensing (wherein the radio access network node is a selected radio access network node for transmission of radio signals for sensing or one of one or more other selected radio access nodes for reception of radio signals for sensing) of the sensing service.

[0113] In operation 64 of method or process 60, a RAN entity (eg, a radio access network node) configures itself according to the sensed configuration.

[0114] In operation 66, a RAN entity (e.g., a radio access network node) initiates a sensing operation of a sensing service. As discussed in detail herein, sensing is performed by transmission of a sensing signal (e.g., a radio signal) for sensing (e.g., by one RAN entity) and reception of the radio signal for sensing (e.g., by the same RAN entity or one or more different RAN entities).

[0115] Figure 7 7 is a flow chart illustrating a method or process according to an example embodiment, generally indicated by reference numeral 70. The method or process 70 may be implemented at one of the one or more RAN entities 36.

[0116] In operation 72 of the method or process 70 (which may be omitted in some example embodiments), a sensing signal (eg, a radio signal) for sensing (received by a corresponding RAN entity) is processed to generate sensing data.

[0117] In operation 74 of the method or process 70, data is provided (e.g., from the corresponding RAN entity 36 to the sensing management module 32). The data may be a received sensing signal or other sensing data (in which case operation 72 may be omitted). Alternatively, the data may be sensing data processed in operation 72 (e.g., an output of operation 72).

[0118] Figure 8 80 is a diagram illustrating a message flow sequence and process operations according to an example embodiment, generally indicated by reference numeral 80. Process 80 illustrates messages sent between an application function (AF) 81, a network exposure function (NEF) 82, a sensing management function (SeMF) 83, an access and mobility management function (AMF) 84, and one or more RAN entities (e.g., a base station (BS) 85) of a 5G wireless communication system, and operations performed by SeMF 83 and one of the RAN entities (e.g., one of the base stations 85). However, it should be noted that the principles of process 80 may be applied to other communication systems.

[0119] Process 80 is a process for configuring and enabling a RAN entity (eg, a BS) of a communication system to perform single-site sensing, wherein admission control (eg, resource allocation) is performed at SeMF 83 .

[0120] The process 80 starts at step 1, where a sensing client (in this example embodiment, AF 81) sends a request for a sensing service (generally referred to as a sensing service request) to a SeMF 83 of a communication system (e.g., a core network of the communication system, such as a 5G core network 5GC of a 5G communication system). The SeMF 83 is configured to support or provide different types of sensing services. The AF 81 may send a request to the SeMF 83 (or a 5G core network 5GC) directly. Figure 8 The sensing service request may include information related to the requested sensing service. The information included in the sensing service request may include the QoS of the requested sensing service, an indication of the requested sensing service type, information indicating the sensing requirements of the requested sensing service, and information indicating the sensing area of ​​the requested sensing service.

[0121] In step 2, the SeMF 83 determines the sensing method to be used for the requested sensing service based on the information related to the sensing service included in the sensing service request (received in step 1), and selects a RAN entity. In the example process 80, the SeMF 83 selects one or more RAN entities (e.g., BSs) 85 to participate (as sensors) in the sensing session for the requested sensing service, which RAN entities are both sensing transmitters and sensing receivers, and are selected (because the sensing method selected by the SeMF 83 is single-station sensing in this example embodiment).

[0122] The SeMF 83 uses the sensing capabilities (e.g., methods, sensing features) of each RAN entity (e.g., BS) 85, which may be stored at the SeMF or another NF, or even at an Operation, Maintenance, and Management (OAM) system. In addition, the SeMF 83 may use other information related to the RAN entity (e.g., BS 85) to select the RAN entity (e.g., BS) 85 to participate in the sensing session of the sensing service, such as computational load, availability of sensing resources, and / or availability or load of the RAN entity (e.g., BS) 85.

[0123] As part of step 2, the SeMF 83 selects one or more RAN entities (e.g. BSs and optionally cells) to participate in a sensing session of the sensing service, wherein each selected RAN entity (e.g. BS) 85 has the role of a single-station sensor (e.g. is a single-station sensor, which means that the RAN entity (e.g. BS 85) sends and receives sensing signals): Each single-station sensor has a sensor identifier (sensor ID) which identifies the selected RAN entity (e.g. BS) 85. The sensor ID of the single-station sensor may include

[0124] ●The identifier of the RAN entity (e.g. BS ID)

[0125] • and optionally a cell identifier (eg cell ID).

[0126] In step 3, the SeMF 83 performs sensing admission control to check whether each selected RAN entity (e.g., BS) 85 has available resources according to the sensing requirements (e.g., duration, update rate) and the required QoS (e.g., sensing accuracy, sensing resolution, sensing latency). The SeMF 83 determines a sensing configuration for each corresponding RAN entity (e.g., BS) 85. The sensing configuration of each corresponding RAN entity (e.g., BS) 85 includes a sensing resource configuration and a sensing session configuration of the corresponding RAN entity (e.g., BS) 85. The sensing resource configuration of the corresponding RAN entity (e.g., BS) 85 includes information about resources that the RAN entity (e.g., BS) 85 should use for the sensing session, including one or both of the following items:

[0127] • Option a) A pilot or reference signal will be used for the sensing session.

[0128] ● Option b) is used for user plane and control plane resources for the sensing session, such as resource blocks, time or frequency resources, selected frequency band assigned for PDSCH to deliver control plane messages and / or user plane data. The SeMF 83 may optionally provide user plane configuration information for user plane transmission (e.g. bandwidth used, duration of user plane transmission, amount of data to be sent), e.g. according to the sensing service requirements. Alternatively, a code may be provided that may allow a RAN entity (e.g. BS) 85 to identify or retrieve the user plane configuration information.

[0129] If the result of the admission control and resource availability check is that the required resource is not available, step 2 discussed above may be repeated.

[0130] As discussed further below, in other example embodiments, sensing admission control may be performed by another entity, such as the RAN entity (eg, BS) 85 .

[0131] In step 4, SeMF 83 (based on the output of step 3) determines a sensing session configuration that can be used to appropriately configure RAN entities and / or optimize sensing transmission and reception, the sensing session configuration including sensing methods, sensing QoS parameters, sensing session duration, sensing timing and location information, type of sensing service: request or subscription, RAT type used for sensing, sensing bandwidth, etc.

[0132] The SeMF 83 may split the sensing operations to different RAN entities (e.g. BS) 85, and different sensing configurations may also be used for different BSs. For example, different parts of the sensing area described in the sensing request (received in step 1) may be assigned to different involved RAN entities (e.g. BS) 85. In this embodiment, multiple sensors (or sensing subsessions or sensing flows) with a unique identifier (ID) may be established for each sensor (or sensing subsession). The unique identifier of the sensor identifies the sensor (or sensing subsession). The SeMF 83 may manage mapping information associated with multiple (concurrent) sensors (or sensing subsessions) with a given identifier of a sensing session and / or a sensing service request from a sensing client.

[0133] The SeMF 83 generates a sensing data reporting configuration (e.g. whether to use control plane reporting or user plane (e.g. to or via a dedicated server) to transfer sensing measurements from the RAN entity (e.g. BS) 85 to the SeMF 83). Optionally, resources and configurations for reporting may be defined.

[0134] In step 5, SeMF 83 sends a request to establish a sensing session of the requested sensing service to one or more RAN entities (e.g., BS) 85 selected to participate in the sensing operation. The request to establish a sensing session is generally referred to as a sensing service establishment request, and the request includes one or more of the following information:

[0135] An identifier of a sensing session (commonly referred to as a sensing session ID) generated by the SeMF 83 to facilitate coordination and processing of sensing operations for the specific sensing service requested.

[0136] Identifier of the RAN entity, such as BS ID (e.g. Global gNB ID or 6G Node B ID) and / or cell ID (e.g. NR CGI or 6G Cell Global ID)

[0137] Sensing session configuration, as determined in step 4.

[0138] The sensing resource configuration, as determined in step 3, comprises the resources to be used for sensing by each RAN entity (eg, BS) 85 participating in the sensing operation.

[0139] Sensor data reporting configuration, as determined in step 4.

[0140] In step 6 , each RAN entity (eg BS) 85 that has received the sensing session establishment request commits to check and implement and / or apply the sensing session configuration and sensing resource configuration received by the SeMF 83 .

[0141] In step 7, the RAN entity (eg, BS) 85 sends a response to the sensing session establishment request, the response including an indication of success or failure in establishing the requested sensing session. The response may also include a failure reason code indicating the reason for failure in establishing the requested sensing session.

[0142] Optionally, the RAN entity (eg, BS) 85 may determine another configuration for sensing (eg, sensing session configuration, sensing resource configuration, sensing data reporting configuration) in a response message or in a separate message and send it to the SeMF 83 .

[0143] In step 8 (which may be optional), the SeMF 83 notifies the corresponding RAN entity (e.g., BS) 85 to initiate a sensing session identified by the sensing session ID. For example, this step may be performed in an embodiment where it is necessary to start sensing operations at multiple RAN entities (e.g., BSs) in a coordinated manner. The sensing session establishment request may include an indication (e.g., a flag) indicating that the RAN entity (e.g., BS) 85 waits or does not wait for a notification from the SeMF to start the sensing operation.

[0144] In step 9, the RAN entity (e.g., BS) 85 executes or performs a sensing operation by allocating and / or scheduling resources according to the received sensing configuration. The RAN entity (e.g., BS) 85 transmits a reference signal and / or a pilot or a physical downlink channel for user data using the frequency, time, and space (i.e., Tx antenna, beam) resources required to meet the QoS of the requested sensing service. The RAN entity (e.g., BS) 85 also attempts to receive and measure its own transmission signal, in which the sensing configuration for sensing is received.

[0145] In step 10 (which may be optional), the RAN entity (e.g. BS) 85 may send information about an updated sensing configuration to the SeMF 83, for example due to a local (RAN entity (e.g. BS) 85) decision and / or due to changes during execution of step 9 at the RAN entity (e.g. BS) 85 and / or due to changes in the sensing environment and / or conditions and / or measurements. The RAN entity (e.g. BS) 85 may provide the updated sensing configuration to the SeMF 83 by sending a message including the updated sensing configuration. Based on the updated sensing configuration, the SeMF may update the corresponding sensing session, including any elements provided in step 5. The SeMF 83 may send the updated configuration to the corresponding BS(s).

[0146] In step 11 , the RAN entity (eg BS) 85 provides the SeMF 83 with sensing data (eg measured values ​​of the performed sensing operations) identified by the sensing session ID and the identifier of the RAN entity (eg BS ID) using the sensing data reporting configuration.

[0147] In step 12, the SeMF 83 processes the collected sensing data based on the sensing data received from one or more RAN entities (eg, BS) to generate sensing output.

[0148] Steps 9 to 11 may be repeated or iterated before sending a response to the sensing service request.

[0149] In step 13 , the SeMF 82 provides the sensing output to the requesting sensing client, for example to the AF 81 directly or via the NEF 82 .

[0150] It should be noted that multiple single-station RAN entities (e.g., BSs) may be selected for the same sensing session. The SeMF 83 may keep and / or maintain and / or store a list of identifiers (e.g., BS IDs) of the RAN entities participating in each sensing session (identified by the sensing session ID), the context of each RAN entity (e.g., BS) (e.g., sensing capabilities, QoS of the sensing session), and the determined sensing session configuration and sensing resource configuration. For example, the SeMF 83 may keep and / or maintain and / or store the following information:

[0151] ● An identifier of the sensing session (eg, a sensing session ID)

[0152] ● The quality of service of the requested sensing service (referred to herein as sensing QoS)

[0153] ● RAN entities (e.g. BS) participating in the sensing session, including one or more of the following information for each RAN entity participating in the sensing session

[0154] Sensor ID

[0155] RAN entity ID (e.g. BS ID)

[0156] ●Cell ID (eg, identifier of a cell)

[0157] ● Sensing method (e.g. bistatic or monostatic sensing)

[0158] ●Sensor ID sensing capability

[0159] ●Sensing session configuration for sensor ID

[0160] ●Sensing resource configuration of sensor ID

[0161] ●Configuration of sensor data reporting by sensor ID

[0162] Fig. 9 A process is shown according to an example embodiment, generally indicated by reference numeral 90. Process 90 shows an application function (AF) 91, a network exposure function (NEF) 92, a sensing management function (SeMF) 93, an access and mobility management function (AMF) 94 and one or more RAN entities (in a 5G wireless communication system) Fig. 9 9 is shown as a message (eg, a control plane message) sent between a base station (BS) 95). However, it should be noted that the principles of process 90 may be applied to other wireless communication systems.

[0163] Process 90 is an alternative to the above process 80. In process 90, the RAN entity (eg, BS 95) is responsible for checking the availability of sensing resources, selecting sensing resources for a sensing session, and setting corresponding sensing configurations.

[0164] In step 1 of the process 90, a sensing client (e.g., AF 91) sends a sensing service request to the 5G core (5GC). The sensing client (e.g., AF 91) sends the request directly to SeMF 93 or to SeMF 93 via NEF 92. The sensing service request includes information that depends on the scenario and application. The information may include sensing QoS (i.e., the QoS of the requested sensing service), an indication of the sensing type of the requested sensing service, the sensing requirements of the requested sensing service, and an indication of the sensing area of ​​the requested sensing service.

[0165] In step 2, SeMF 93 determines the appropriate sensing method and sensing configuration based on the information included in the sensing service request. In step 2, SeMF 93 may select one or more RAN entities (e.g., BS 95) that will participate (as sensors) in the sensing operation of the requested sensing service. SeMF 93 may select one or more RAN entities (e.g., BS 95) using the sensing capabilities (which may be stored at SeMF or another NF or even at OAM) of each RAN entity BS 95 (e.g., the sensing methods supported by it, its sensing features) to select one or more RAN entities (e.g., BS 95) to participate (as sensors) in the sensing operation of the requested sensing service. In addition, SeMF may use other information of the RAN entities (e.g., RAN entity load) to select one or more RAN entities (e.g., BS 95) to participate in the sensing operation of the sensing service.

[0166] In step 3, SeMF 93 sends a sensing session establishment request to one or more RAN entities (e.g., BS) 95 selected to participate in the sensing session (e.g., via AMF 94). The sensing establishment request includes one or more of the following information:

[0167] An identifier of the sensing session (e.g., a sensing session ID), generated by the SeMF 93 to facilitate coordination and processing of sensing operations for the requested sensing service

[0168] ● An identifier of the selected RAN entity (e.g. an identifier of the BS (e.g. BS ID)) ● Sensing requirements of the requested sensing service (e.g. sensing area, duration, update rate)

[0169] ● QoS of the requested sensing service (e.g. sensing accuracy, sensing resolution, sensing latency)

[0170] • An indication of the sensing method of the requested sensing service (eg, an indication of single-station sensing, dual-station sensing, sensing using user plane resources, sensing using pilot signals and / or reference signals).

[0171] The SeMF 93 may split the sensing operation between different BSs, and different sensing configurations may also be used for different BSs. Therefore, different sensing session establishment requests may involve different areas and / or focus on different sensing features.

[0172] In step 4, the BS 95 that has received the sensing session establishment request checks whether it has available resources according to the sensing requirements and the required sensing QoS. At this stage, each BS 95 determines a sensing resource configuration that defines the resources that each associated BS will use for sensing, including one or both of the following:

[0173] ● Option a) A pilot or reference signal to be used for sensing

[0174] Option b) User plane and control plane resources used for sensing, such as resource blocks, time or frequency resources, assignments for PDSCH to deliver control plane messages to the 5GC and / or

[0175] Or selected frequency band for user plane data.

[0176] In step 5, the RAN entity (e.g., BS) 95 sends a response to the sensing session establishment request, the response including an indication of success or failure in establishing the requested sensing session. The response may also include a reason code indicating the cause of the failure (in the case where the response includes an indication of failure in establishing the requested sensing session). Optionally, the RAN entity (e.g., BS) 95 may include information about the sensing resource configuration, such as the selected resources.

[0177] In step 6, based on the output of step 5, SeMF 93 determines the sensing session configuration, which includes the RAN entities or cells involved (e.g., the BS or cell selected for the sensing session), sensing resource configuration information, and other information about the sensing session identified by the sensing session ID and each RAN entity identified by the BS ID (e.g., sensing QoS parameters, sensing session duration, and / or timing and location information used for sensing).

[0178] Depending on the outcome of the admission control and resource availability check at the RAN entity (eg, BS) 95 , the SeMF 93 may return to step 2 .

[0179] In step 7, the SeMF 93 informs the corresponding RAN entity (e.g., BS(s)) 95 to initiate the sensing session identified by the sensing session ID. This step may be required, for example, if sensing operations for the sensing session need to be started at multiple RAN entities (e.g., BSs) in a coordinated manner. The sensing data reporting configuration may also be included in this message, which may be determined in step 6. Note that some or all of step 7 may be omitted in some example embodiments.

[0180] Steps 8 to 12 are identical to the corresponding steps of message sequence 80 described above and are not discussed further here.

[0181] Steps 2 to 6 may be repeated several times depending on the result of sensing admission control at the requested RAN entity (eg, BS).

[0182] Fig.10 1 is a diagram illustrating a message flow sequence and process operations according to an example embodiment, generally indicated by reference numeral 100. Process 100 includes messages (e.g., control plane messages) sent between an application function (AF) 101, a network exposure function (NEF) 102, a sensing management function (SeMF) 103, an access and mobility management function (AMF) 104, and one or more RAN entities 105 of a 5G wireless communication system. However, it should be noted that the principles of message sequence 100 may be applied to other communication systems.

[0183] Process 100 is a process for configuring and enabling a RAN entity (e.g., BS) of a communication system for dual-station sensing, and admission control (e.g., resource allocation) occurs at SeMF 103. It should be noted that although process 100 is described with respect to dual-station sensing, the same principles also apply to multi-station sensing.

[0184] Step 1 of process 100 is the same as step 1 of processes 80 and 90 discussed above.

[0185] In step 2, the SeMF 103 determines the sensing method for the sensing session according to the input of the sensing request message (step 1), and identifies and / or selects one or more RAN entities to participate in the sensing session of the requested sensing service based on the determined sensing method. The input comprising the sensing request (e.g., the requirements of the sensing service) depends on the scenario and application, and may include sensing QoS, sensing type, sensing service, sensing requirements and / or sensing area. In a specific embodiment where the SeMF 103 determines that the sensing method is a dual-station sensing method, the SeMF 103 identifies and / or selects a RAN entity (e.g., BS_105 to participate in the sensing session of the requested sensing service (as a sensing sender)), and generates a sensing configuration for one of the RAN entities to configure the one RAN entity as or as a sensing sender. The SeMF 103 also identifies and / or selects another RAN entity (e.g., BS) 106) to participate in the sensing session of the requested sensing service (as a sensor), and generates a sensing configuration for configuring the other RAN entity (e.g., BS) 106 as or as a sensing receiver.

[0186] The SeMF 103 uses the sensing capabilities (i.e., methods, sensing characteristics) of each RAN entity (e.g., BS), which may be stored at the SeMF or another NF or even at the OAM, for selecting a RAN entity for a sensing session of the requested sensing service. In addition, other information of the RAN entity, such as computational load, sensing resource availability or load, etc., may be considered for selecting a RAN entity (e.g., BS) for a sensing session.

[0187] In the multi-station sensing method, the SeMF 103 selects multiple RAN entities (e.g., BSs), wherein one of the selected RAN entities transmits a sensing signal, and another of the selected RAN entities receives the sensing signal (e.g., is configured as or acts as a sensing receiver). Each selected RAN entity is selected for a specific sensing role (e.g., selected as a sensing transmitter or a sensing receiver) and may be identified by (or associated with) a sensor ID, which may include:

[0188] ● Identifier of the RAN entity sending the sensing signal:

[0189] BS ID)

[0190] ●Cell ID

[0191] ● Identifier(s) of the RAN entity(ies) receiving the sensing signal:

[0192] ●BS ID(s)

[0193] ●(Multiple) Cell IDs

[0194] Note that selecting a cell (eg, identified by a cell ID) results in selecting a RAN entity to use for sensing (as a transmitter, receiver, or both).

[0195] In step 3, the SeMF 103 checks whether each selected RAN entity selected for the sensing transmitter or sensing receiver role has available resources according to the sensing requirements (e.g. duration, update rate) and the required sensing QoS (e.g. sensing accuracy, sensing resolution, sensing latency). At this stage, the SeMF 103 determines the resources (Tx sensing resource configuration or Rx sensing resource configuration) that each RAN entity should use for sensing, including one or both of the following:

[0196] ● Option a) A pilot or reference signal to be used for sensing

[0197] • Option b) User plane and control plane resources used for sensing, such as resource blocks, time or frequency resources, selected frequency bands assigned for PDSCH to deliver control plane signaling and / or user plane data.

[0198] Depending on the outcome of the admission control and resource availability check, SeMF may return and repeat step 2.

[0199] In step 4, based on the output of step 3, the SeMF also determines the sensing session configuration (which can be used to appropriately configure and / or optimize the transmission and / or reception of sensing signals by the RAN entity), sensing QoS parameters, sensing session duration, sensing timing and location information, type of sensing service: request or subscription, sensing method, RAT type and / or required bandwidth for each RAN entity selected as a sensing transmitter or sensing receiver for the sensing session of the dual-station sensing operation.

[0200] The SeMF 103 may split the sensing operations of the sensing session into different RAN entities for execution, and each RAN entity may also use different sensing configurations. For example, different parts of the area to be sensed identified by the information included in the sensing service request may be assigned to different RAN entities (e.g., BSs) to be configured as or as sensing transmitters (and corresponding one or more RAN entities (e.g., BSs) configured as or as sensing receivers).

[0201] As part of the sensing configuration to configure the RAN entities as sensing receivers, the RAN entities (e.g. BSs) may be configured to receive all sensing signals from all RAN entities (BSs) configured as or acting as sensing transmitters, or only to some RAN entities (e.g. BSs) configured as or acting as sensing transmitters.

[0202] In step 5, the SeMF 103 sends a sensing session establishment request to one or more RAN entities (e.g. BSs) selected to participate in the sensing session (e.g., via the AMF 104) (e.g., the RAN entity selected as the sensing transmitter (step 5.1) and the RAN entity selected as the sensing receiver for dual-station sensing (step 5.2)). Each sensing session establishment request may include one or more of the following information:

[0203] • A sensing session ID, generated by the SeMF 103 to facilitate coordination and processing of sensing operations for a sensing session of the requested sensing service.

[0204] BS ID, cell ID

[0205] ●The RAN entity will be configured as or as an indication of a sensing transmitter or sensing receiver

[0206] ● Sensing session configuration, as defined in step 4.

[0207] • Sensing resource configuration, as determined in step 3, which includes the resources to be used for sensing by each involved BS.

[0208] ● Sensing data reporting configuration, as determined in step 4.

[0209] In step 6, each RAN entity (eg, BS) that has received the sensing session establishment request commits to implement or apply the sensing session and sensing resource configuration received by the SeMF.

[0210] In step 7, the RAN entities (e.g. BS) respectively send sensing session establishment responses to the sensing session establishment requests. Each sensing session establishment response includes an indication of success or failure of providing the requested sensing session (and optionally a reason code, when the indication indicates failure to establish the sensing session, the reason code indicates the reason for the failure to establish the sensing session). Optionally, any RAN entity (e.g. BS) may determine another configuration for sensing (e.g. sensing session configuration, sensing resource configuration, sensing data reporting configuration) and send it to the SeMF. Based on the received notifications and / or responses, the SeMF 103 may review and / or check the RAN entities (e.g. BS) and update it with a confirmed list of RAN entities (e.g. BS) that have been selected as sensing transmitters and / or sensing receivers. The updated list of RAN entities (e.g. BS) and information on whether the RAN entity will be configured as or act as a sensing receiver or sensing transmitter may be included in the message(s) sent in step 8.

[0211] In step 8 (which may be omitted in some example embodiments), the SeMF 103 notifies the corresponding RAN entity (e.g. BS) to initiate sensing operations for the sensing session identified by the sensing session ID. This step may be required, particularly in a dual-station approach, to ensure that a RAN entity (e.g. BS) configured as or acting as a sensing transmitter does not initiate sensing operations for the sensing session before the RAN entity (e.g. BS) is configured as a sensing receiver. And, if sensing operations for the sensing session need to be started at multiple BSs in a coordinated manner. The sensing data reporting configuration may also be provided to the RAN entity (e.g. BS) configured as or acting as a sensing transmitter and / or sensing receiver, which may be determined by the SeMF 103.

[0212] In step 9, the RAN entities (BS) performing the sensing allocate or schedule resources according to the received sensing configuration, depending on whether they are configured or act as a sensing transmitter and / or a sensing receiver. The RAN entity (e.g., BS) 105 configured or act as a sensing transmitter role transmits reference signals, pilots, or physical downlink channels for user data using the frequency, time, and space (i.e., Tx antennas, beams) resources required to meet the QoS requirements of the sensing session. The RAN entity (e.g., BS) 106 configured or act as a sensing also attempts to receive and measure signals transmitted by the RAN entity (e.g., BS) configured or act as a sensing transmitter according to the received sensing configuration.

[0213] In step 10 (which may be omitted in some example embodiments), the RAN entity (e.g. BS) 105 configured as or in the role of a sensing sender may send information about an updated sensing configuration to the SeMF 103, for example due to a local (RAN entity (e.g. BS)) decision and / or due to a change during execution of step 9 at the RAN entity (e.g. BS) and / or due to a change in the sensing environment, conditions or measurements. With this message, the RAN entity (e.g. BS) may provide the SeMF 103 with the updated sensing configuration. Based on this message, the SeMF 103 may update the corresponding sensing session, including any elements provided in step 5 above. The SeMF 103 may also send the updated configuration to the corresponding RAN entity (e.g. BS(s)).

[0214] A RAN entity (eg, a BS) configured as or acting as a sensing transmitter may provide updated sensing configuration information to RAN entity(ies) (eg, BS(ies)) configured as or acting as a sensing receiver.

[0215] In step 11 , the RAN entity (eg BS) configured as or acting as a sensing receiver role provides the SeMF 103 with measurement values ​​(eg sensing data) of the performed sensing operation identified by the sensing session ID and the BS ID.

[0216] In step 12, the SeMF 103 processes the collected sensing measurements based on inputs received from different RAN entities (eg, BS) and determines a sensing output.

[0217] Steps 9 to 12 may be repeated or iterated before sending a sensing service response.

[0218] Step 13 is identical to the corresponding step described above with reference to message sequences 80 and 90 .

[0219] As another feature of this embodiment, the same RAN entity (eg, BS) may be configured as or serve as a sensing transmitter and a sensing receiver for the same sensing session and / or different sensing sessions.

[0220] It should be noted that the SeMF may select multiple "dual-station" and / or multi-station sensors (RAN entities) for the same sensing session. The SeMF shall maintain, hold or store a list of RAN entities involved for each sensing session (identified by sensing session ID), the role of the selected RAN entity (sensing sender, sensing receiver), its context (e.g. sensing capabilities, sensing QoS) and the determined sensing session configuration and sensing resource configuration. For example, the SeMF may maintain and / or store the following information:

[0221] ●Sensing session ID

[0222] ●Quality of service of the requested sensing service (Sensing QoS)

[0223] ● A list of RAN entities participating in the sensing session, including one or more of the following information for each RAN entity

[0224] Sensor ID

[0225] ●Sensing method

[0226] ●Sensor ID sensing capability

[0227] ●Sensor transmitter role

[0228] BS ID

[0229] ●Cell ID

[0230] ●Tx sensing session configuration for sensor BS ID / cell ID

[0231] ●Tx sensing resource configuration of sensor BS ID / cell ID

[0232] ● Sensing data reporting configuration of transmitter sensor(s) BS ID / (s) cell ID

[0233] ●Sensor role

[0234] ●BS ID(s)

[0235] ●(Multiple) Cell IDs

[0236] ● Rx sensing session configuration for sensor(s) BS ID / (s) cell ID

[0237] ● Rx sensing resource configuration of sensor(s) BS ID / (s) cell ID

[0238] ● Sensing data reporting configuration of Rx sensor(s) BS ID / (s) cell ID

[0239] Fig.11 A process according to an example embodiment, generally indicated by reference numeral 110, is shown. The process 110 shows messages between an application function (AF) 111, a network exposure function (NEF) 112, a sensing management function (SeMF) 113, an access and mobility management function (AMF) 114, and one or more first base stations (BS) 115 of a 5G wireless communication system having a transmitter role and one or more second base stations (BS) 116 of a 5G wireless communication system having a receiver role. However, it should be noted that the principles of the message sequence 110 can be applied to other communication systems.

[0240] Process 110 is an alternative to the above process 100. In process 110, the RAN entity (e.g., BS) 85 is responsible for performing an availability check of sensing resources, selecting necessary resources, and configuring corresponding sensing configurations. In this process, coordination between RAN entities (e.g., via Xn or via AMF) is required to support coordination between RAN entities configured as or acting as sensing transmitters (e.g., having a sensing transmitter role) and RAN entities configured as sensing receivers (e.g., configured as or acting as sensing receivers).

[0241] Steps 1 and 2 are the same as the corresponding steps of process 100 described above.

[0242] In step 3, SeMF 113 sends a sensing session establishment request to one or more RAN entities (e.g., BS) involved in the sensing operation (e.g., via AMF 114), where the sensing session establishment request includes one or more of the following:

[0243] ● Sensing Session ID, generated by SeMF to facilitate the coordination and processing of sensing operations with respect to specific sensing service requests

[0244] BS ID, cell ID

[0245] ● Sensing requirements (e.g. sensing area, duration, update rate)

[0246] ● Sensing QoS (e.g., sensing accuracy, sensing resolution, sensing latency)

[0247] • Tx sensing session configuration and / or Rx sensing session configuration depending on the role identified in step 2 for each BS.

[0248] The sensing session configuration includes information about the selected sensing method and the role that each RAN entity (e.g., BS) has (e.g., is configured for). For example, the information included in the sensing session configuration includes:

[0249] ● The identifier of the selected first RAN entity (e.g. sensor ID #1)

[0250] ● Information indicating selection of a sensing method in which the first RAN entity participates (e.g., single-station sensing, dual-station sensing, or multi-station sensing)

[0251] ● Sensing area of ​​the first RAN entity

[0252] ●Timing information of the first RAN entity sensor ID#1

[0253] ● Information indicating that the first RAN entity is configured for a sensing sender role or as a sensing sender

[0254] ● An identifier of the first RAN entity (e.g. BS ID)

[0255] ● An identifier of the cell served by the first RAN entity (e.g., a cell ID)

[0256] ● Information indicating that the first RAN entity has a sensing receiver role or is configured as a sensing receiver

[0257] ● Identifier of the second RAN entity (e.g. sensor ID #2)

[0258] ● Information indicating the second RAN entity sensing method

[0259] ●Sensor ID#1’s sensing area

[0260] ● Timing information of sensor ID#1

[0261] ●Sensor transmitter role

[0262] BS ID

[0263] ●Cell ID

[0264] ●Sensor role

[0265] ●BS ID(s)

[0266] ●(Multiple) Cell IDs

[0267] ●…

[0268] The SeMF 113 may split the sensing operations of the sensing session between different RAN entities and may also utilize different sensing configurations if necessary. Therefore, different sensing session establishment requests may involve different areas and / or focus on different sensing features.

[0269] In step 4, the RAN entity (e.g., BS) 115 configured as or acting as a sensing transmitter first checks whether it has the resources required to support (e.g., perform) the sensing operation of the sensing session according to the sensing requirements (e.g., duration, update rate) and the QoS required for the sensing service (e.g., sensing accuracy, sensing resolution, sensing latency). The RAN entity (e.g., BS) 115 configured as a sensing transmitter then determines the transmitter resources (transmitter sensing resource configuration) that the RAN entity should use to transmit the sensing signals.

[0270] The transmitter sensing resource configuration includes resources to be used for sensing operations of RAN entities (e.g., BS) participating in the sensing operations, including one or both of the following:

[0271] ● Option a) A pilot or reference signal to be used to send a sensing signal

[0272] • Option b) User plane and control plane resources to be used for sending sensing signals, such as resource blocks, time or frequency resources, selected frequency bands assigned for PDSCH to deliver control plane signals and / or user plane data.

[0273] Depending on the outcome of the admission control and resource availability check, SeMF can then return and repeat step 2.

[0274] In step 5, the RAN entity (e.g. BS) 115 configured as or acting as a sensing transmitter sends the determined transmitter sensing resource configuration, i.e., the sensing signal frequency, bandwidth, timing of sending the sensing signal from the RAN entity (e.g. BS) (as indicated in step 3) to one or more RAN entities (e.g. BS) 116 configured as or acting as sensing receivers of a specific sensing session (identified by a sensing session ID or a sensor ID).

[0275] For a RAN entity (e.g., BS) configured as or acting as a sensing receiver, the RAN entity (e.g., BS) needs to know when (in the time domain) and where (in the frequency domain) the sensing signal is expected to be received. If the RAN entity (e.g., BS) configured as or acting as a sensing receiver needs to receive multiple sensing signals from different RAN entities (e.g., BS) configured as or acting as a sensing transmitter, the RAN entity (e.g., BS) configured as or acting as a sensing receiver may need to know this information to distinguish the sensing signals (e.g., sensing signal attributes from each RAN entity (e.g., BS) configured as or acting as a sensing transmitter).

[0276] In step 6, the RAN entity (eg, BS) 116 is configured as or acts as a sensing receiver that has received the request to implement the sensing configuration and checks the availability of its sensing resources (ie, performs admission control).

[0277] In step 7, the RAN entity (e.g., BS) 116 configured as or acting as a sensing receiver provides a sensing admission response to the corresponding RAN entity (e.g., BS) 115 (i.e., sending the request in step 5), indicating the success or failure of establishing the requested sensing session (and may provide a reason code indicating the reason for the failure to establish the session).

[0278] In step 8, the RAN entity (e.g., BS) 115 configured as or acting as sensing sends a sensing session establishment response to the SeMF 113, indicating the success or failure of establishing the requested sensing session, and optionally sends a reason code indicating the reason for the failure to establish the sensing session, according to its inspection and / or notification from (multiple) RAN entities (e.g., (multiple) BSs) configured as or acting as sensing receivers. Optionally, when the RAN entity (e.g., BS) 115 successfully establishes the sensing session, the RAN entity (e.g., BS) 115 also provides the sensing resource configuration and information to the RAN entity (e.g., BS) selected by the SeMF 113 as the sensing receiver.

[0279] In optional step 9, the SeMF 113 may update the sensing session configuration according to the received response.

[0280] In step 10 (which may be omitted in some example embodiments), the SeMF 113 notifies the corresponding RAN entity (e.g. BS) to initiate a sensing operation for the sensing session identified by the sensing session ID. In particular, in a dual-station approach, this step may be required to ensure that the RAN entity (e.g. BS) 115 configured as or as sensing with a transmitter does not initiate a sensing operation for the sensing session before the RAN entity (e.g. BS) is configured as a sensing receiver based on the sensing configuration provided by the SeMF 113. Optionally, if the SeMF 113 has distinguished the sensing session configuration, the latter is included in the sensing initiation message.

[0281] The sensing data reporting configuration may also be provided to the RAN entity (eg BS), which may be determined by the SeMF 113 .

[0282] Steps 11 to 15 are identical to the corresponding steps presented in process 110 (see steps 9 to 13 of this message sequence).

[0283] In another embodiment, if part of step 3 of process 110 is omitted (e.g., the session establishment request sent to the RAN entity selected to be configured as a sensing receiver), then the RAN entity (e.g., a BS) configured to or acting as sensing 115 may optionally provide sensing session information, which may be required by the RAN entity (e.g., a BS) selected to be configured to or acting as a sensing receiver.

[0284] In another embodiment, in case the SeMF does not provide this information and / or the sensing session needs to be updated, the RAN entity (e.g. BS) configured as or acting as a sensing sender may select one or more RAN entities (e.g. BS) configured as sensing receivers. This applies to any other embodiment with multi-station sensing.

[0285] Fig.12 1 is a diagram illustrating a message sequence and process operations generally indicated by reference numeral 120 according to an example embodiment. Process 120 illustrates messages (e.g., control plane messages) sent between an application function (AF) 121, a network exposure function (NEF) 122, a sensing management function (SeMF) 123, an access and mobility management function (AMF) 124, and one or more first base stations (BSs) 125 of a 5G wireless communication system having a transmitter role and one or more second base stations (BSs) 126 of a 5G wireless communication system having a receiver role. However, it should be noted that the principles of message sequence 120 may be applied to other communication systems.

[0286] The process 120 differs from the above-described process 110 in that the interaction between the BSs is performed via the AMF(s) 124 instead of via the Xn interface.

[0287] Steps 1 to 4 of process 120 are the same as steps 1 to 4 of process 110 .

[0288] In step 5, the RAN entity (e.g., BS) 125 configured as or acting as a sensing transmitter sends a response to the sensing session establishment request (generally referred to as a sensing session establishment response) to the SeMF 123, the response including an indication of accepting or rejecting the sensing session establishment request including a specific sensing session ID and / or sensor ID.

[0289] When the sensing session establishment response includes an indication of rejecting the sensing session establishment request, the response may also include a reason code indicating the reason for rejecting the sensing session establishment request. When the sensing session establishment response includes an indication of the sensing session establishment request and an acceptance indication, the sensing resource configuration may be included in the response, as determined in step 4, taking into account:

[0290] • Option a) a pilot or reference signal to be used to send a sensing signal, or

[0291] • Option b) User plane resources for sending sensing signals.

[0292] Based on the received responses, the SeMF 123 may update the selected sensing method and / or select new RAN entities (eg BSs) 85 that will participate in the sensing session for the requested sensing service, eg RAN entities that will be configured as sensing receivers.

[0293] In step 6, the SeMF 123 (via the AMF 124) sends a sensing session establishment request to the RAN entity (e.g., BS) 126 identified or selected as a sensing receiver. The sensing session establishment request may include one or more of the following information:

[0294] ●Sensing session ID

[0295] Sensor ID

[0296] BS ID

[0297] ● Sensing requirements (e.g. sensing area, duration, update rate)

[0298] ● Sensing QoS (e.g., sensing accuracy, sensing resolution, sensing latency)

[0299] ●Tx sensing resource configuration (as determined in steps 4 and 5)

[0300] ● Sensing session configuration, including information about the selected method and the role each BS has. For example:

[0301] ●Sensor ID#1..n

[0302] ●Sensing method

[0303] ●Sensor ID#1’s sensing area

[0304] ● Timing information of sensor ID#1

[0305] ●Sensing Tx role

[0306] BS ID

[0307] ●Cell ID

[0308] ●Sensing Rx role

[0309] ●BS ID(s)

[0310] ●(Multiple) Cell IDs

[0311] In step 7, the RAN entity (eg, BS) 126 having received the sensing session establishment request commits to implement or apply the sensing configuration and sensing resource configuration included in the sensing session establishment request, and optionally checks the availability of sensing resources.

[0312] For a RAN entity (e.g., BS) configured as or acting as a sensing receiver, the RAN entity (e.g., BS) needs to know when (in the time domain) and where (in the frequency domain) the sensing signal is expected to be received. If the RAN entity (e.g., BS) configured as or acting as a sensing receiver needs to receive multiple sensing signals from different RAN entities (e.g., BS) configured as or acting as a sensing transmitter, the RAN entity (e.g., BS) configured as or acting as a sensing receiver may need to know this information to distinguish the multiple sensing signals (e.g., sensing signal attributes from each RAN entity (e.g., BS) configured as or acting as a sensing transmitter).

[0313] In step 8, the RAN entity (e.g., BS) 126 configured as or acting as a sensing receiver sends a sensing session establishment response to the SeMF 123, indicating the success or failure of establishing the requested sensing session (and optionally a reason code indicating the reason for the failure to establish the sensing session). The response may also include the determined receiver sensing resource configuration.

[0314] In step 9, the SeMF 123 determines a corresponding sensing session configuration according to the responses received in steps 5 and 8 according to the responses received from the RAN entity (eg, BS) configured as or acting as a sensing receiver and / or sensing transmitter.

[0315] In step 10, the SeMF 123 notifies the RAN entity (e.g., BS) configured as or acting as a sensing transmitter or a sensing receiver to initiate a sensing operation of a sensing session identified by a sensing session ID. The SeMF 123 includes the sensing session configuration in the sensing initiation message. The sensing data report configuration may also be provided to the RAN entity (e.g., BS) configured as or acting as a sensing transmitter and a sensing receiver, which may be determined by the SeMF.

[0316] Steps 11 to 15 are identical to the corresponding steps of processes 100 and 110 discussed above.

[0317] Those skilled in the art will recognize many variations of the embodiments described herein. Some example variations are briefly discussed below.

[0318] In an example embodiment, measurements (or sensing data) of sensing operations performed collected at a RAN entity (e.g., a BS) configured as or acting as a sensing receiver and provided by the RAN entity (e.g., the BS) to the SeMF may include information about the received sensing signal, including information about the power, delay, departure angle and arrival angle, and Doppler shift of the sensing signal.

[0319] Optionally, in another embodiment, step 2 of the embodiment discussed above may occur at another entity, such as AMF, RAN.

[0320] In an example embodiment, the procedures and signaling described above for the dual-station sensing method may also be applicable to a multi-station sensing method (eg, a sensing system with multiple sensing receivers, eg, multiple RAN entities (eg, BSs) are configured as or serve as sensing receivers).

[0321] In an example embodiment, a combination of single-station, dual-station and multi-station sensing methods may be used for the same sensing session. The SeMF or RAN entity or any other NF may decide the combination of sensing methods that may be used for each sensing service and / or sensing operation.

[0322] In an example embodiment, when the SeMF receives a sensing request, the SeMF may send a request to the AMF (or to another NF, such as an NRF, or to a RAN entity or repository) to receive identifiers of one or more RAN entities (e.g., BSs) (e.g., in the form of a RAN entity (e.g., BS) list, the list including identifiers of one or more RAN entities (e.g., BSs) that fulfill some selection criteria (e.g., sensing requirements, sensing locations, etc.). When the AMF or another entity provides the RAN entity (e.g., BS) list, the SeMF may perform a final selection of the RAN entities (e.g., BSs) to participate in the sensing session for the requested sensing service, and select each RAN entity (e.g., BS) based on the sensing method and / or sensing configuration and identify its role (e.g., identifying that the RAN entity is to be configured as a sensing transmitter and / or a sensing receiver).

[0323] In an example embodiment, a RAN entity (e.g., a BS) configured as a sensing transmitter may select one or more RAN entities (BS) configured as sensing receivers to participate in a sensing operation, and the RAN entity (e.g., a BS) may provide its corresponding (multiple) sensing configurations to the corresponding selected one or more RAN entities (e.g., BS).

[0324] In an example embodiment, when a RAN entity (e.g., a BS) performs sensing admission control, the SeMF may send information about preferred sensing signal frequency, bandwidth, RAT, etc. to the RAN entity (e.g., as part of a sensing session configuration), which may facilitate the admission control process and / or resource allocation at the RAN entity (e.g., the BS).

[0325] In an example embodiment, the admission control procedure performed by the RAN entity (eg, BS) and / or the SeMF may include a privacy check.

[0326] In an example embodiment, the sensing data may be sensing measurements (e.g. obtained by one or more RAN entities (e.g. BS) configured as or acting as sensing receivers), and the sensing measurements may be transmitted to another RAN entity (e.g. BS configured as or acting as sensing transmitter) via an Xn interface. The sensing measurements may then be provided by the other RAN entity to the SeMF or any other entity (e.g. at the RAN or core network or application server) for processing to generate sensing output data.

[0327] In an example embodiment, some or all of the functionality of the SeMF presented in the various embodiments described herein may be undertaken by the LMF.

[0328] In an example embodiment, the sensing session may be released by the SeMF sending signaling or a message to the RAN entities involved in the sensing session to release the sensing session.

[0329] In an example embodiment, the sensing session may be updated by the SeMF sending a sensing session update message to the RAN entities selected to participate in the sensing session of the selected sensing method. The sensing session update message may include at least one of the following: a new and / or updated session configuration, a new and / or updated sensing resource configuration, a new and / or updated sensing data reporting configuration, an identifier of a RAN entity selected to be configured as or as a sensing transmitter and / or sensing receiver, or an identifier of a RAN entity selected not to be configured as a sensing transmitter and / or sensing receiver (e.g. an identifier or RAN entity to be removed as a sensor). The updated sensing reporting configuration is updated based on the measurement values ​​reported by the RAN entity (e.g. a BS) and / or the processing of the sensing data.

[0330] In an example embodiment, if more than one SeMF participates in the same sensing service request, the same sensing session ID may be used between different SeMFs for all sensing configurations and / or reports referencing the same sensing request (or sensing session).

[0331] In an example embodiment, the SeMF may invoke a service request (e.g., sensing session establishment request, sensing initiation, etc.) in the AMF, which may then send the service request via the N2 interface. The service request may be sent by the SeMF to the AMF for all selected RAN entities (e.g., gNBs), which may then send a separate N2 message to each RAN entity (e.g., gNB). Alternatively, a separate service request may be sent by the SeMF for each selected RAN entity (e.g., gNB or any other BS).

[0332] In an example embodiment, the SeMF may communicate directly with each RAN entity selected to participate in the sensing session.

[0333] In an example embodiment, the SeMF may be deployed in a RAN entity.

[0334] In an example embodiment, the RAN entity may perform (eg, conduct) a sensing operation, and provide sensing data (eg, measurement values) of the sensing operation to the SeMF using control plane resources or user plane resources.

[0335] The RAN entity (eg BS) configured as or acting as a sensing transmitter or a sensing receiver may be part of a Standalone Non-Public Network (SNPN) and / or a Public Land Mobile Network (PLMN) and / or a Public Network Integrated NPN.

[0336] For completeness, Fig.133 is a schematic diagram of components of one or more example embodiments described previously, which is generally referred to below as a processing system 300. The processing system 300 may be, for example, an apparatus as referred to below in the claims. For example, the processing system 300 may be used to implement the functionality of a sensing management function (e.g., implemented by a SeMF) or the features discussed in detail above implemented at a sensing client or RAN entity (e.g., a base station).

[0337] The processing system 300 may have a processor 302, a memory 304 tightly coupled to the processor and including a RAM 314 and a ROM 312, and optionally a user input 310 and a display 318. The processing system 300 may include one or more network or device interfaces 308 to connect to a network or device, such as a modem that may be wired or wireless. The network or device interface 308 may also operate as a connection with other devices (such as equipment or devices) that are not network-side devices. Therefore, a direct connection may be made between devices or devices without the involvement of a network.

[0338] The processor 302 is connected to each of the other components so as to control the operation thereof.

[0339] The memory 304 may include non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (SSD). The ROM 312 of the memory 304 also stores an operating system 315, and may store software applications 316. The processor 302 uses the RAM 314 of the memory 304 for temporary storage of data. The operating system 315 may contain code that, when executed by the processor, implements various aspects of the above-described methods, processes, and sequences 40, 50, 60, 70, 80, 90, 100, 110, and 120. Note that in the case of a small device or apparatus, the memory may be best suited for small size use, i.e., a hard disk drive (HDD) or a solid state drive (SSD) is not always used.

[0340] Processor 302 may take any suitable form. For example, it may be a microcontroller, multiple microcontrollers, a processor, or multiple processors.

[0341] The processing system 300 may be a standalone computer, server, console or network thereof. The processing system 300 and the required structural parts may all be within a device / apparatus such as an IoT device / apparatus, i.e., embedded in a very small size.

[0342] In some example embodiments, the processing system 300 may also be associated with external software applications. These may be applications stored on a remote server device / apparatus and may run partially or exclusively on the remote server device / apparatus. These applications may be referred to as cloud-hosted applications. The processing system 300 may communicate with the remote server device / apparatus to utilize the software applications stored therein.

[0343] Fig.14 A tangible medium in the form of a removable memory unit 365 storing computer readable code is shown, which, when run by a computer, can perform a method according to the above-described example embodiments. The removable memory unit 365 can be a memory stick, such as a USB memory stick, having an internal memory 366 storing the computer readable code. The internal memory 366 can be accessed by the computer system via a connector 367. Of course, other forms of tangible storage media can be used, as will be apparent to one of ordinary skill in the art. The tangible medium can be any device / apparatus capable of storing data / information that can be exchanged between devices / apparatus / networks.

[0344] Embodiments of the present invention may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside in a memory or on any computer medium. In an example embodiment, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media. In the context of this document, a "memory" or "computer-readable medium" may be any non-transient medium or component that may contain, store, transfer, propagate, or convey instructions used by or in conjunction with an instruction execution system, device, or apparatus (such as a computer).

[0345] Where relevant, references to "computer-readable medium", "computer program product", "tangibly embodied computer program", etc. or "processor" or "processing circuit system", etc. should be understood to cover not only computers with different architectures (such as single / multi-processor architectures and sequential / parallel architectures), but also special-purpose circuits, such as field-programmable gate arrays FPGAs, special-purpose circuits ASICs, signal processing devices / apparatuses and other devices / apparatuses. References to computer programs, instructions, codes, etc. should be understood to express software for programmable processor firmware, such as programmable content of hardware devices / apparatuses, whether instructions for a processor or configured or configuration settings for fixed-function devices / apparatuses, gate arrays, programmable logic devices / apparatuses, etc.

[0346] If desired, the different functions discussed herein may be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the above functions may be optional or may be combined. Similarly, it will also be appreciated that Figures 4 to 12 The flowcharts and sequences shown are merely examples, and the various operations depicted therein may be omitted, reordered, and / or combined.

[0347] It is to be understood that the above exemplary embodiments are illustrative only and do not limit the scope of the invention. Other variations and modifications will be apparent to those skilled in the art upon reading this specification.

[0348] Furthermore, it should be understood that the disclosure of the present application includes any novel feature or any novel combination of features disclosed herein, explicitly or implicitly, or any generalization thereof, and that new claims may be formulated during the prosecution of the present application or any application derived therefrom to cover any such feature and / or combination of such features.

[0349] Although various aspects of the invention are set out in the independent claims, further aspects of the invention comprise other combinations of features from the described example embodiments and / or the dependent claims with features of the independent claims than just the combinations explicitly set out in the claims.

[0350] It is also noted herein that although various examples are described above, these descriptions should not be viewed in a limiting sense. Rather, there are several changes and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.

Claims

1. A device comprising: at least one processor; as well as At least one memory storing instructions for sensing management functions, wherein execution of the instructions causes the apparatus to at least perform: receiving a sensing service request from a sensing client of the wireless communication system, the sensing service request comprising information related to a sensing service requested by the sensing client to be provided by the sensing management function; Based at least in part on the information related to the sensing service, selecting one of: single-site sensing for said sensing service, wherein a first selected radio access network node is used to send and receive radio signals for sensing, and multi-station sensing, in which one selected radio access network node is used to send radio signals for sensing and one or more other selected radio access nodes are used to receive radio signals for sensing; being selected based on single-station sensing: sending a sensing configuration of the first selected radio access network node to the first selected radio access network node used for sending and receiving radio signals for sensing; as well as Selected based on multi-station sensing: sending a sensing configuration of the one selected radio access network node to the one selected radio access network node used for sending a radio signal for sensing.

2. The apparatus according to claim 1, wherein the sensing configuration of the first selected radio access network node used for sending and receiving radio signals for sensing comprises at least one of the following items: a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration.

3. The apparatus according to claim 1 or 2, wherein the sensing configuration of the one selected radio access network node used to send the radio signal for sensing comprises at least one of the following items: a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration.

4. An apparatus according to any preceding claim, wherein: Based on multi-station sensing being selected, execution of the instructions further causes the apparatus to at least perform: The sensing configuration of each respective other radio access network node used to receive radio signals is sent to the respective other radio access network node. 5 . The apparatus of claim 4 , wherein the sensing configuration of each respective other radio access network node comprises at least one of: a sensing resource configuration, a sensing session configuration, and a sensing data reporting configuration.

6. The apparatus according to any one of the preceding claims, wherein the information related to the sensing service comprises at least one of: a sensing service type of the sensing service; a sensing requirement of the sensing service; and a sensing service quality of the sensing service.

7. The apparatus of claim 6, wherein the sensing requirements of the sensing service include: A sensing area of ​​the sensing service.

8. The apparatus of any preceding claim, wherein sending the sensing configuration of the first selected radio access network node comprises: A request for establishing a sensing session for the sensing service is sent to the first selected radio access network node, the request comprising the sensing configuration of the first selected radio access network node.

9. The apparatus according to any one of the preceding claims, wherein execution of the instructions further causes the apparatus to at least perform: A request for the radio access network node to initiate sensing is sent to the first selected radio access network node used for sending and receiving radio signals for sensing.

10. The apparatus of any one of the preceding claims, wherein execution of the instructions further causes the apparatus to perform at least one of the following: receiving sensing data from said first selected radio access network node used for transmitting and receiving radio signals for sensing; and Sensing data is received from the one or more other selected radio access network nodes used to receive radio signals for sensing.

11. The apparatus of claim 10, wherein execution of the instructions further causes the apparatus to execute: processing the sensed data to generate sensed output data; and The sensed output data is provided.

12. The device according to any one of the preceding claims, wherein: Sending the sensing configuration of the one selected radio access network node comprises sending a request to the one selected radio access network node for establishing a sensing session for the sensing service, the request comprising the sensing configuration of the one selected radio access network node.

13. The apparatus of claim 12, wherein the request further comprises: An indication of initiation of sensing by the one selected radio access network node.

14. The apparatus according to any one of the preceding claims, wherein execution of the instructions further causes the apparatus to at least perform: A session admission is controlled in which a decision is made as to whether the respectively selected network node is able to meet the defined requirements.

15. An apparatus comprising: at least one processor; as well as At least one memory storing instructions for sensing management functions, wherein execution of the instructions causes the apparatus to at least perform: receiving, from a sensing management function of a wireless communication system, a sensing configuration for a sensing service at a radio access network node of the wireless communication system, wherein the sensing configuration is used to configure at least one of: single-site sensing for the sensing service, wherein the radio access network node is a first selected radio access network node used for sending and receiving radio signals for sensing, and multi-station sensing, wherein the radio access network node is one of a selected radio access network node used to send a radio signal for sensing, or one of one or more other selected radio access nodes used to receive a radio signal for sensing; configuring the radio access node according to the sensing configuration; as well as The radio access network node is caused to initiate sensing.

16. The apparatus of claim 15, wherein execution of the instructions further causes the apparatus to perform at least one of the following: transmitting a radio signal for sensing; and A radio signal is received for sensing.

17. The apparatus of claim 15 or 16, wherein execution of the instructions further causes the apparatus to perform at least one of the following: providing the received radio signal to the sensing management function; and The received radio signal is processed and the processed received radio signal is provided to the sensing management function.

18. The apparatus according to any one of claims 15 to 17, wherein execution of the instructions further causes the apparatus to at least execute: A request is received for the radio access network node to initiate sensing.

19. The apparatus according to any one of claims 15 to 18, wherein execution of the instructions further causes the apparatus to execute: Controlling session admission in which a determination is made as to whether sufficient resources are available to satisfy the sensing requirements defined in the session establishment message.

20. The apparatus of any one of claims 15 to 19, further comprising means for performing the following: In response to the request to establish a sensing session, a sensing session establishment response is provided.

21. The apparatus according to any one of claims 15 to 20, wherein execution of the instructions further causes the apparatus to execute: Send information about updated sensing configuration.

22. The apparatus of any one of claims 15 to 20, further comprising means for performing the following: Configuration and data are exchanged between different radio access network nodes configured by the sensing management function for multi-site sensing scenarios.

23. A method comprising: receiving a sensing service request from a sensing client of the wireless communication system, the sensing service request comprising information related to a sensing service requested by the sensing client to be provided by the sensing management function; Based at least in part on the information related to the sensing service, selecting one of: single-site sensing for said sensing service, wherein a first selected radio access network node is used to send and receive radio signals for sensing, and multi-station sensing, in which one selected radio access network node is used to send radio signals for sensing and one or more other selected radio access nodes are used to receive radio signals for sensing; being selected based on single-station sensing: sending a sensing configuration of the first selected radio access network node to the first selected radio access network node used for sending and receiving radio signals for sensing; as well as Selected based on multi-station sensing: sending a sensing configuration of the one selected radio access network node to the one selected radio access network node used for sending a radio signal for sensing.

24. A method comprising: receiving, from a sensing management function of a wireless communication system, a sensing configuration for a sensing service at a radio access network node of the wireless communication system, wherein the sensing configuration configures at least one of: single-site sensing for the sensing service, wherein the radio access network node is a first selected radio access network node used for sending and receiving radio signals for sensing, and multi-station sensing, wherein the radio access network node is one of a selected radio access network node used to send a radio signal for sensing, or one of one or more other selected radio access nodes used to receive a radio signal for sensing; configuring the radio access node according to the sensing configuration; as well as The radio access network node is caused to initiate sensing.

25. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to: receiving a sensing service request from a sensing client of the wireless communication system, the sensing service request comprising information related to a sensing service requested by the sensing client to be provided by the sensing management function; Based at least in part on the information related to the sensing service, selecting one of: single-site sensing for said sensing service, wherein a first selected radio access network node is used to send and receive radio signals for sensing, and multi-station sensing, in which one selected radio access network node is used to send radio signals for sensing and one or more other selected radio access nodes are used to receive radio signals for sensing; being selected based on single-station sensing: sending a sensing configuration of the first selected radio access network node to the first selected radio access network node used for sending and receiving radio signals for sensing; as well as Selected based on multi-station sensing: sending a sensing configuration of the one selected radio access network node to the one selected radio access network node used for sending a radio signal for sensing.

Images