Sensing discovery procedure

The sensing discovery procedure optimizes beam-based partner selection for ISAC systems, addressing the challenge of discovering and selecting sensing partners in mobile networks, enhancing ISAC capabilities in various coverage scenarios.

WO2026234147A2PCT designated stage Publication Date: 2026-11-12FRAUNHOFER GESELLSCHAFT ZUR FORDERUNG DER ANGEWANDTEN FORSCHUNG EV
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/063196
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

The challenge of discovering and selecting appropriate sensing partners for integrated sensing and communication (ISAC) systems in mobile communication networks, particularly in out-of-coverage scenarios, is not adequately addressed in existing literature, as current methods assume known sensing partners and lack standardization in 6G networks.

Method used

A sensing discovery procedure is implemented in wireless communication systems, where a sensing initiator entity identifies and selects suitable sensing partners by transmitting discovery requests using a subset of beams based on position, orientation, velocity, and sensing area, and receives responses to establish a sensing session.

Benefits of technology

Enables effective discovery and selection of sensing partners, ensuring efficient bi-static or multi-static sensing operations by optimizing beam usage and partner selection criteria, enhancing ISAC capabilities in both in-coverage and out-of-coverage scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026063196_12112026_PF_FP_ABST
    Figure EP2026063196_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Embodiment provide a sensing initiator entity of a wireless communication network, wherein the sensing initiator entity is configured to discover one or more sensing candidate partner entities for sensing a sensing area, wherein the sensing initiator entity is configured to select at least one sensing partner entity out of the one or more discovered candidate sensing partner entities as sensing partner for sensing the sensing area.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Sensing Discovery Procedure

[0002] Description

[0003] Embodiments of the present application relate to the field of wireless communication, and more specifically, to a sensing discovery procedure. Some embodiments relate to discovery and selection of one or more sensing partners, for example, for sensing a defined sensing area.

[0004] Fig. 1 is a schematic representation of an example of a terrestrial wireless network 100 including, as is shown in Fig. 1(a), a core network 102 and one or more radio access networks (RANs) RAN1, RAN2, ...RANN. Fig. 1(b) is a schematic representation of an example of a radio access network RANn that may include one or more base stations (BSs) gNBi to gNBs, each serving a specific area surrounding the base station schematically represented by respective cells 1061 to 106s. The base stations are provided to serve users within a cell. The term base station, BS, refers to a next generation node B (gNB) in 5G / 6G networks, an evolved node B (eNB) in UMTS / LTE / LTE-A / LTE-A Pro, or just a BS in other mobile communication standards. A user may be a stationary device or a mobile device. The wireless communication system may also be accessed by mobile or stationary Internet of Things (loT) devices which connect to a base station or to a user. The mobile devices or the loT devices may include physical devices, ground based vehicles, such as robots or cars, aerial vehicles, such as manned or unmanned aerial vehicles (UAVs), the latter also referred to as drones, buildings and other items or devices having embedded therein electronics, software, sensors, actuators, or the like as well as network connectivity that enables these devices to collect and exchange data across an existing network infrastructure. Fig. 1(b) shows an exemplary view of five cells, however, the RANn may include more or less such cells, and RANn may also include only one base station. Fig. 1(b) shows two users UE1 and UE2, also referred to as user equipment, UE, that are in cell IO62 and that are served by base station gNB2. Another user UE3 is shown in cell IO64 which is served by base station gNB4. The arrows IO81, IO82 and IO83 schematically represent uplink / downlink connections for transmitting data from a user UE1, UE2 and UE3 to the base stations gNB2, gNB4 or for transmitting data from the base stations gNB2, gNB4 to the users UE1, UE2, UE3. Further, Fig. 1(b) shows two loT devices 110i and HO2 in cell IO64, which may be stationary or mobile devices. The loT device 110i accesses the wireless communication system via the base station gNB4 to receive and transmit data as schematically represented by arrow 112i . The loT device 11O2 accesses the wireless communication system via the user UE3 as is schematically represented by arrow 1122. The respective base station

[0005] FH250503PEP-2026154931. DOCXgNBi to gNBs may be connected to the core network 102, e.g., via the S1 interface, via respective backhaul links 114i to 114s, which are schematically represented in Fig. 1(b) by the arrows pointing to “core”. The core network 102 may be connected to one or more external networks. Further, some or all of the respective base station gNBi to gNBs may connected, e.g., via the S1 or X2 interface or the XN interface in NR, with each other via respective backhaul links 116i to 116s, which are schematically represented in Fig. 1(b) by the arrows pointing to “gNBs”.

[0006] For data transmission a physical resource grid may be used. The physical resource grid may comprise a set of resource elements (REs) to which various physical channels and physical signals are mapped. For example, the physical channels may include the physical downlink, uplink and sidelink shared channels (PDSCH, PLISCH, PSSCH) carrying user specific data, also referred to as downlink, uplink and sidelink payload data, the physical broadcast channel (PBCH) carrying for example a master information block (MIB), the physical downlink shared channel (PDSCH) carrying for example a system information block (SIB), the physical downlink, uplink and sidelink control channels (PDCCH, PLICCH, PSSCH) carrying for example the downlink control information (DCI), the uplink control information (UCI) and the sidelink control information (SCI). For the uplink, the physical channels, or more precisely the transport channels according to 3GPP, may further include the physical random access channel (PRACH or RACH) used by UEs for accessing the network once a UE is synchronized and has obtained the MIB and SIB. The physical signals may comprise reference signals or symbols (RS), synchronization signals and the like. The resource grid may comprise a frame or radio frame having a certain duration in the time domain and having a given bandwidth in the frequency domain. The frame may have a certain number of subframes of a predefined length, e.g., 1ms. Each subframe may include one or more slots of 12 or 14 orthogonal frequency-division multiplexing (OFDM) symbols depending on the cyclic prefix (CP) length. All OFDM symbols may be used for downlink (DL) or uplink (UL) or only a subset, e.g., when utilizing shortened transmission time intervals (sTTI) or a mini-slot / non-slot-based frame structure comprising just a few OFDM symbols.

[0007] The wireless communication system may be any single-tone or multicarrier system using frequency-division multiplexing, like the OFDM system, the orthogonal frequency-division multiple access (OFDMA) system, or any other IFFT-based signal with or without CP, e.g., DFT-s-OFDM. Other waveforms, like non-orthogonal waveforms for multiple access, e.g., filter-bank multicarrier (FBMC), generalized frequency division multiplexing (GFDM) or universal filtered multi carrier (LIFMC), may be used. The wireless communication system may

[0008] FH250503PEP-2026154931. DOCXoperate, e.g., in accordance with the LTE-Advanced pro standard or the NR (5G), New Radio, standard.

[0009] The wireless network or communication system depicted in Fig. 1 may by a heterogeneous network having distinct overlaid networks, e.g., a network of macro cells with each macro cell including a macro base station, like base station gNBi to gNBs, and a network of small cell base stations (not shown in Fig. 1), like femto or pico base stations.

[0010] In addition to the above described terrestrial wireless network also non-terrestrial wireless communication networks exist including spaceborne transceivers, like satellites, and / or airborne transceivers, like unmanned aircraft systems. The non-terrestrial wireless communication network or system may operate in a similar way as the terrestrial system described above with reference to Fig. 1, for example in accordance with the LTE-Advanced Pro standard or the NR (5G), new radio, standard.

[0011] In mobile communication networks, for example in a network like that described above with reference to Fig. 1, like an LTE or 5G / NR or 6G network, there may be UEs that communicate directly with each other over one or more sidelink (SL) channels, e.g., using the PC5 interface. UEs that communicate directly with each other over the sidelink may include vehicles communicating directly with other vehicles (V2V communication), vehicles communicating with other entities of the wireless communication network (V2X communication), for example roadside entities, like traffic lights, traffic signs, or pedestrians. Other UEs may not be vehicular related UEs and may comprise any of the above-mentioned devices. Such devices may also communicate directly with each other (D2D communication) using the SL channels.

[0012] When considering two UEs directly communicating with each other over the sidelink, both UEs may be served by the same base station so that the base station may provide sidelink resource allocation configuration or assistance for the UEs. For example, both UEs may be within the coverage area of a base station, like one of the base stations depicted in Fig. 1. This is referred to as an “in-coverage” scenario. Another scenario is referred to as an “out-of-coverage” scenario. It is noted that “out-of-coverage” does not mean that the two UEs are not within one of the cells depicted in Fig. 1, rather, it means that these UEs

[0013] may not be connected to a base station, for example, they are not in a radio resource control (RRC) connected state, so that the UEs do not receive from the base station any sidelink resource allocation configuration or assistance, and / or

[0014] FH250503PEP-2026154931. DOCXmay be connected to the base station, but, for one or more reasons, the base station may not provide sidelink resource allocation configuration or assistance for the UEs, and / or

[0015] may be connected to the base station that may not support NR V2X services, e.g., GSM, UMTS, LTE base stations.

[0016] When considering two UEs directly communicating with each other over the sidelink, e.g., using the PC5 interface, one of the UEs may also be connected with a BS, and may relay information from the BS to the other UE via the sidelink interface. The relaying may be performed in the same frequency band (in-band-relay) or another frequency band (out-of-band relay) may be used. In the first case, communication on the Uu and on the sidelink may be decoupled using different time slots as in time division duplex (TDD) systems.

[0017] Fig. 2 is a schematic representation of an in-coverage scenario in which two UEs directly communicating with each other are both connected to a base station. The base station gNB has a coverage area that is schematically represented by the circle 200 which, basically, corresponds to the cell schematically represented in Fig. 1. The UEs directly communicating with each other include a first vehicle 202 and a second vehicle 204 both in the coverage area 200 of the base station gNB. Both vehicles 202, 204 are connected to the base station gNB and, in addition, they are connected directly with each other over the PC5 interface. The scheduling and / or interference management of the V2V traffic is assisted by the gNB via control signaling over the Uu interface, which is the radio interface between the base station and the UEs. In other words, the gNB provides SL resource allocation configuration or assistance for the UEs, and the gNB assigns the resources to be used for the V2V communication over the sidelink. This configuration is also referred to as a mode 1 configuration in NR V2X or as a mode 3 configuration in LTE V2X.

[0018] Fig. 3 is a schematic representation of an out-of-coverage scenario in which the UEs directly communicating with each other are either not connected to a base station, although they may be physically within a cell of a wireless communication network, or some or all of the UEs directly communicating with each other are to a base station but the base station does not provide for the SL resource allocation configuration or assistance. Three vehicles 206, 208 and 210 are shown directly communicating with each other over a sidelink, e.g., using the PC5 interface. The scheduling and / or interference management of the V2V traffic is based on algorithms implemented between the vehicles. This configuration is also referred to as a mode 2 configuration in NR V2X or as a mode 4 configuration in LTE V2X. As mentioned above, the scenario in Fig. 3 which is the out-of-coverage scenario does not necessarily mean that the

[0019] FH250503PEP-2026154931. DOCXrespective mode 2 UEs (in NR) or mode 4 UEs (in LTE) are outside of the coverage 200 of a base station, rather, it means that the respective mode 2 UEs (in NR) or mode 4 UEs (in LTE) are not served by a base station, are not connected to the base station of the coverage area, or are connected to the base station but receive no SL resource allocation configuration or assistance from the base station. Thus, there may be situations in which, within the coverage area 200 shown in Fig. 2, in addition to the NR mode 1 or LTE mode 3 UEs 202, 204 also NR mode 2 or LTE mode 4 UEs 206, 208, 210 are present.

[0020] Naturally, it is also possible that the first vehicle 202 is covered by the gNB, i.e. connected with Uu to the gNB, wherein the second vehicle 204 is not covered by the gNB and only connected via the PC5 interface to the first vehicle 202, or that the second vehicle is connected via the PC5 interface to the first vehicle 202 but via Uu to another gNB, as will become clear from the discussion of Figs. 4 and 5.

[0021] Fig. 4 is a schematic representation of a scenario in which two UEs directly communicating with each, wherein only one of the two UEs is connected to a base station. The base station gNB has a coverage area that is schematically represented by the circle 200 which, basically, corresponds to the cell schematically represented in Fig. 1. The UEs directly communicating with each other include a first vehicle 202 and a second vehicle 204, wherein only the first vehicle 202 is in the coverage area 200 of the base station gNB. Both vehicles 202, 204 are connected directly with each other over the PC5 interface.

[0022] Fig. 5 is a schematic representation of a scenario in which two UEs directly communicating with each, wherein the two UEs are connected to different base stations. The first base station gNB1 has a coverage area that is schematically represented by the first circle 2001, wherein the second station gNB2 has a coverage area that is schematically represented by the second circle 2002. The UEs directly communicating with each other include a first vehicle 202 and a second vehicle 204, wherein the first vehicle 202 is in the coverage area 2001 of the first base station gNB1 and connected to the first base station gNB1 via the Uu interface, wherein the second vehicle 204 is in the coverage area 2002 of the second base station gNB2 and connected to the second base station gNB2 via the Uu interface.

[0023] In a communication system as described above, integrated sensing and communication (ISAC) is becoming an increasingly important development area. In the context of integrated sensing and communication (ISAC), a bi-static (or multi-static) sensing system involves at least two sensing entities, whereas a monostatic sensing system only involves one sensing entity.

[0024] FH250503PEP-2026154931. DOCXHowever, the problem of how to discover and select an appropriate sensing partner is not yet addressed in known publications. Indeed, current literature usually assumes that all sensing partners are known. On the other hand, ISAC is not standardized yet in the context of mobile communication systems and will begin only for 6G in Rel-20.

[0025] Therefore, there is the need for improvements or enhancements with respect to the discovery selection of sensing entities.

[0026] It is noted that the information in the above section is only for enhancing the understanding of the background of the invention and therefore it may contain information that does not form prior art and is already known to a person of ordinary skill in the art.

[0027] Embodiments of the present invention are described herein making reference to the appended drawings.

[0028] Figs. 1a, b show a schematic representation of an example of a wireless communication system;

[0029] Fig. 2 is a schematic representation of an in-coverage scenario in which UEs directly communicating with each other are connected to a base station;

[0030] Fig. 3 is a schematic representation of an out-of-coverage scenario in which UEs directly communicating with each other receive no SL resource allocation configuration or assistance from a base station;

[0031] Fig. 4 is a schematic representation of a partial out-of-coverage scenario in which some of the UEs directly communicating with each other receive no SL resource allocation configuration or assistance from a base station;

[0032] Fig. 5 is a schematic representation of an in-coverage scenario in which UEs directly communicating with each other are connected to different base stations;

[0033] Fig. 6 is a schematic representation of a wireless communication system comprising a transceiver, like a base station or a relay, and a plurality of communication devices, like UEs, according to an embodiment,

[0034] FH250503PEP-2026154931. DOCXFig. 7 shows a schematic representation of a target sensing service area of a sensing entity,

[0035] Fig. 8 shows a schematic representation of a selection of a sensing partner for sensing a target sensing area of a sensing initiator,

[0036] Fig. 9 shows a schematic representation of the sensing discovery procedure performed between the sensing initiator entity and the candidate sensing partner entities acting as monitoring sensing entities,

[0037] Fig. 10 shows a schematic representation of a sensing discovery procedure performed between the sensing initiator and candidate sensing partners acting as announcing sensing entities,

[0038] Fig. 11 shows a flow chart of the discovery and selection procedure to support the sensing of a target sensing service area, and

[0039] Fig. 12 illustrates an example of a computer system on which units or modules as well as the steps of the methods described in accordance with the inventive approach may execute.

[0040] Equal or equivalent elements or elements with equal or equivalent functionality are denoted in the following description by equal or equivalent reference numerals.

[0041] In the following description, a plurality of details is set forth to provide a more thorough explanation of embodiments of the present invention. However, it will be apparent to one skilled in the art that embodiments of the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form rather than in detail in order to avoid obscuring embodiments of the present invention. In addition, features of the different embodiments described hereinafter may be combined with each other, unless specifically noted otherwise.

[0042] As indicated above, in the context of integrated sensing and communication (ISAC), a bi-static (or multi-static) sensing system involves at least two sensing entities which are not co-located. Embodiments described herein consider the case when a sensing entity wants to sense a specific target sensing service area. Some of the embodiments described herein aim to solve the following technical problem: for a sensing entity with a given target sensing service area to

[0043] FH250503PEP-2026154931. DOCXbe covered, it needs to discover and select one or more suitable other sensing entities as its sensing partners.

[0044] Specifically, embodiments describe how to perform the procedure to first discover and then select appropriate “sensing partner(s)” prior to starting the bi-static (or multi-static) sensing of a target sensing service area of interest for the sensing initiator. These steps are the prerequisite to the establishment of a sensing session between a sensing initiator and at least one sensing partner.

[0045] Embodiments of the present invention may be implemented in a wireless communication system or network as depicted in Figs. 1 to 5 including a transceiver, like a base station, gNB, or relay, and a plurality of communication devices, like user equipments, UEs. Fig. 6 is a schematic representation of a wireless communication system comprising a transceiver 200, like a base station, and a plurality of communication devices 2021 to 202n, like UEs. The UEs might communicate directly with each other via a wireless communication link or channel 203, like a radio link (e.g., using the PC5 interface (sidelink)). Further, the transceiver and the UEs 202 might communicate via a wireless communication link or channel 204, like a radio link (e.g., using the Uu interface). The transceiver 200 might include one or more antennas ANT or an antenna array having a plurality of antenna elements, a signal processor 200a and a transceiver unit 200b. The UEs 202 might include one or more antennas ANT or an antenna array having a plurality of antennas, a processor 202a1 to 202an, and a transceiver (e.g., receiver and / or transmitter) unit 202b1 to 202bn. The base station 200 and / or the one or more UEs 202 may operate in accordance with the inventive teachings described herein.

[0046] Embodiments provide a sensing initiator entity of a wireless communication network [e.g., 5G I NR, or 6G], wherein the sensing initiator entity is configured to discover one or more sensing candidate partner entities for sensing a sensing area, wherein the sensing initiator entity is configured to select at least one sensing partner entity out of the one or more discovered candidate sensing partner entities as sensing partner for sensing the sensing area.

[0047] In embodiments, the sensing initiator entity is configured to select a subset [e.g., proper subset] of beams [e.g., sensing beams or antenna beams] covering the sensing area out of a plurality of different beams.

[0048] In embodiments, the sensing initiator entity is configured to select the subset of beams out of the plurality of different beams in dependence on at least one out of

[0049] a position of the sensing initiator entity,

[0050] FH250503PEP-2026154931. DOCXan orientation of the sensing initiator entity,

[0051] a velocity of the sensing initiator entity,

[0052] a beam pattern of the sensing initiator entity, and

[0053] the sensing area.

[0054] In embodiments, the plurality of different beams is usable by the sensing initiator entity for transmitting and / or receiving radio signals of the wireless communication network.

[0055] In embodiments, the sensing initiator entity is configured to receive a configuration message [e.g., from a network entity], wherein the sensing initiator entity is configured, in case that the configuration message indicates a first activation type, to discover the one or more sensing candidate partner entities by transmitting a discovery request [e.g., discovery request message], and receiving one or more discovery responses [e.g., discovery response messages] from the one or more sensing candidate partner entities.

[0056] In embodiments, the sensing initiator entity is configured to transmit the discovery request using a selected subset of beams selected out of the plurality of different beams.

[0057] In embodiments, the sensing initiator entity is configured to transmit the discovery request on each beam of the selected subset of beams.

[0058] In embodiments, the discovery request indicates at least one out of

[0059] an identity of the sensing initiator entity,

[0060] a position of the sensing initiator entity,

[0061] a velocity of the sensing initiator entity,

[0062] the sensing area [e.g., a geographical location describing the sensing area], sensing requirements,

[0063] sensing capabilities of the sensing initiator entity.

[0064] In embodiments, the sensing initiator entity is configured to transmit a at least one sensing activation request [or second discovery request] indicating an identity of the at least one sensing partner entity selected as sensing partner.

[0065] In embodiments, the sensing initiator entity is configured to receive a configuration message [e.g., from a network entity], wherein the sensing initiator entity is configured, in case that the configuration message indicates a second activation type, to discover the one or more sensing

[0066] FH250503PEP-2026154931. DOCXcandidate partner entities by receiving one or more discovery requests [e.g., discovery request messages] from the one or more sensing candidate partner entities.

[0067] In embodiments, each of the one or more discovery requests indicates at least one out of: an identity of the respective sensing partner entity,

[0068] a position of the respective sensing partner entity,

[0069] an orientation of the respective sensing partner entity,

[0070] a velocity of the respective sensing partner entity,

[0071] sensing capabilities of the respective sensing partner entity.

[0072] In embodiments, the sensing initiator entity is configured to transmit at least one discovery response indicating an identity of the at least one sensing partner entity selected as sensing partner.

[0073] In embodiments, the discovery response indicates the sensing area.

[0074] In embodiments, the sensing initiator entity is configured to receive a configuration message [e.g., from a network entity], wherein the sensing initiator entity is configured, in case that the configuration message indicates a third activation type, to discover and select the at least one sensing partner entity for sensing the sensing area based on a look-up table.

[0075] In embodiments, the look-up table describes different sensing areas and associated sensing partner entities.

[0076] In embodiments, the sensing initiator entity is configured to transmit a sensing activation request [or second discovery request] indicating an identity of the at least one sensing partner entity selected as sensing partner.

[0077] In embodiments, the sensing initiator is configured to transmit the sensing activation request via the Xn interface.

[0078] In embodiments, the sensing initiator entity is configured to receive a configuration message from a network entity of the wireless communication network, the configuration message indicating that sensing initiator entity is allowed to switch into a sensing mode of operation [e.g., in which the sensing discovery procedure is performed. For example, discovering the one or more candidate sensing partners and / or selection of the sensing partner].

[0079] FH250503PEP-2026154931. DOCXIn embodiments, the sensing initiator entity is configured to switch into the sensing mode of operation in response to the reception of the configuration message.

[0080] In embodiments, the configuration message indicates at least one out of

[0081] an identity allocated to the sensing initiator entity,

[0082] an identity of a sensing group to which the sensing initiator entity belongs,

[0083] an activation type.

[0084] In embodiments, the sensing initiator entity is configured to transmit an information message to the network entity, the information message indicating sensing capabilities of the sensing initiator entity.

[0085] In embodiments, the sensing initiator entity is configured to select the at least one sensing partner entity out of the one or more candidate sensing partner entities based on a quality of a link [e.g. sensing link] between the sensing initiator entity and a respective candidate sensing partner entity.

[0086] In embodiments, the sensing initiator is configured to determine the quality of the link by performing quality measurements [e.g., received signal strength indicator (RSSI), the reference signal received power (RSRP) or the signal-to-noise ratio (SNR)] based on a signal [e.g., comprising the discovery response or discover request] received from the respective candidate sensing partner entity.

[0087] In embodiments, the sensing initiator is configured to determine the quality of the link using each beam of the subset of beams.

[0088] In embodiments, the sensing initiator is configured to select the at least one sensing partner entity out of the one or more candidate sensing partner in case that the quality of the link [e.g. sensing or communication link] between the sensing initiator entity and a respective candidate sensing partner entity fulfills a quality selection criterion [e.g., RSSI, RSRP or SNR [e.g., on each sensing beam] equal to or higher than a (pre-)configured threshold, or average RSSI, RSRP or SNR across all sensing beams equal to or higher than a (pre-)configured threshold].

[0089] In embodiments, the sensing initiator entity is configured to select the at least one sensing partner entity out of the one or more candidate sensing partner entities based on a position of the respective candidate sensing partner entity [e.g., with respect to the sensing area and / or indicated in the discovery response or request].

[0090] FH250503PEP-2026154931. DOCXIn embodiments, the sensing initiator entity is configured to prefer a candidate sensing partner entity in the selection of the at least one sensing partner entity out of the one or more candidate sensing partner entities that fulfills a preference selection criterion.

[0091] In embodiments, the preference selection criterion includes at least one out of

[0092] static candidate sensing partner entities are preferred over moving candidate sensing partner entities,

[0093] a first type [e.g., TRPs] of candidate sensing partner entities are preferred over a second type [e.g., UEs] candidate sensing partner entities,

[0094] a candidate sensing partner located at a smaller distance to a reference point [e.g., center] of the sensing area is preferred over another candidate sensing partner located at a greater distance to the reference point,

[0095] a candidate sensing partner fulfilling sensing requirements to a higher degree is preferred over a candidate sensing partner that fulfills the sensing requirements to a lower degree.

[0096] In embodiments, the preference selection criterion is defined by the sensing initiator entity itself, network signaling, higher layers, or (pre-)configuration.

[0097] In embodiments, the sensing initiator entity is a user equipment, UE, or a transmit receive point, TRP, [e.g., base station or roadside unit].

[0098] Further embodiments provide a sensing partner entity of a wireless communication network [e.g., 5G I NR, or 6G], wherein the sensing partner entity is discoverable by a sensing initiator entity, wherein the sensing partner entity is configured, in response to being selected as sensing partner by the sensing initiator entity, to assist the sensing initiator entity in sensing a sensing area.

[0099] In embodiments, the sensing partner entity is configured to select a subset of beams out of a plurality of different beams covering a sensing area of the sensing initiator entity.

[0100] In embodiments, the sensing partner entity is configured to select the subset of beams out of the plurality of different beams in dependence on at least one out of

[0101] a position of the sensing partner entity,

[0102] an orientation of the sensing partner entity,

[0103] a velocity of the sensing partner entity,

[0104] FH250503PEP-2026154931. DOCXa beam pattern of the sensing partner entity, and

[0105] the sensing area of the sensing initiator entity.

[0106] In embodiments, the plurality of different beams is usable by the sensing partner entity for transmitting and / or receiving radio signals of the wireless communication network.

[0107] In embodiments, the sensing partner entity is configured to receive a configuration message [e.g., from a network entity], wherein the sensing partner entity is discoverable by the sensing initiator entity, in case that the configuration message indicates a first activation type, by receiving a discovery request [e.g., discovery request message] from the sensing initiator entity and transmitting a discovery response [e.g., discovery response message] to the sensing initiator entity.

[0108] In embodiments, the sensing partner entity is configured to transmit the discovery response on

[0109] each beam of a plurality of different beams,

[0110] or on each beam the sensing partner entity received the discovery request, or on each beam of a selected subset of beams in case that the discovery request indicates the sensing area.

[0111] In embodiments, the discovery response indicates at least one out of

[0112] an identity of the sensing partner entity,

[0113] a position of the sensing partner entity,

[0114] an orientation of the sensing partner entity,

[0115] a velocity of the sensing partner entity.

[0116] In embodiments, the sensing partner entity is configured to transmit the discovery response only in case that sensing partner entity fulfills sensing quality requirements indicated in the discovery request.

[0117] In embodiments, the sensing partner entity is configured to receive a sensing activation request [or second discovery request] indicating an identity of the at least one selected sensing partner entity, wherein the sensing partner entity is configured to switch into a sensing partner mode of operation in case that it is identified by the identity indicated in the sensing activation request.

[0118] In embodiments, the sensing partner entity is configured to receive a configuration message [e.g., from a network entity], wherein the sensing partner entity is discoverable by the sensing

[0119] FH250503PEP-2026154931. DOCXinitiator entity, in case that the configuration message indicates a second activation type, by transmitting a discovery request to the sensing initiator entity.

[0120] In embodiments, the discovery request indicates at least one out of:

[0121] an identity of the sensing partner entity,

[0122] a position of the sensing partner entity,

[0123] an orientation of the sensing partner entity,

[0124] a velocity of the sensing partner entity,

[0125] sensing capabilities of the sensing partner entity,

[0126] a potential sensing area that can be covered by the sensing partner entity.

[0127] In embodiments, the sensing partner entity is configured to receive a discovery response [or discovery response message] indicating an identity of the selected sensing partner entity selected by the sensing initiator entity as sensing partner, wherein the sensing partner entity is configured to switch into a sensing partner mode of operation in case that it is identified by the identity indicated in the discovery response.

[0128] In embodiments, the sensing partner entity is configured to receive a configuration message [e.g., from a network entity], wherein the sensing partner entity is discoverable by the sensing initiator entity, in case that the configuration message indicates a third activation type, based on a look-up table,

[0129] In embodiments, the look-up table describes different sensing areas and associated sensing partner entities.

[0130] In embodiments, the sensing partner entity is configured to receive a sensing activation request [or second discovery request] indicating an identity of the at least one sensing partner entity selected as sensing partner, wherein the sensing partner entity is configured to switch into a sensing partner mode of operation in case that it is identified by the identity indicated in the sensing activation request.

[0131] In embodiments, the sensing partner is configured to receive the sensing activation request via the Xn interface.

[0132] In embodiments, the sensing partner entity is configured to receive a configuration message from a network entity of the wireless communication network, the configuration message indicating that sensing partner entity is allowed to switch into a sensing mode of operation

[0133] FH250503PEP-2026154931. DOCX[e.g., in which the sensing discovery procedure is performed [e.g., being discoverable by a sensing initiator entity]].

[0134] In embodiments, the sensing partner entity is configured to switch into the sensing mode of operation in response to the reception the configuration message.

[0135] In embodiments, the configuration message indicates at least one out of

[0136] an identity allocated to the sensing partner entity,

[0137] an identity of a sensing group to which the sensing partner entity belongs,

[0138] an activation type.

[0139] In embodiments, the sensing partner entity is configured to transmit an information message to the network entity, the information message indicating sensing capabilities of the sensing partner entity.

[0140] In embodiments, the sensing partner entity is a user equipment, UE, or a transmit receive point, TRP, [e.g., base station or roadside unit].

[0141] Further embodiments provide a network entity of a wireless communication network [e.g., 5G / NR, or 6G], wherein the network entity is configured to transmit configuration messages to a sensing initiator entity and / or one or more sensing partner entities, the configuration messages configuring the sensing initiator entity and the one or more sensing partner entities to perform a sensing discovery procedure.

[0142] In embodiments, the configuration message indicates at least one out of

[0143] an identity allocated to the respective sensing initiator entity or sensing partner entity, an identity of a sensing group to which the respective sensing initiator entity or sensing partner entity belongs,

[0144] an activation type of the respective sensing initiator entity or sensing partner entity.

[0145] In embodiments, the network entity is a core network node or core network function or a radio access network node [e.g., base station].

[0146] Further embodiments provide a wireless communication network, comprising at least two out of a sensing initiator entity according to an embodiment described herein, a sensing partner entity according to an embodiment described herein, and a network entity according to an embodiment described herein.

[0147] FH250503PEP-2026154931. DOCXFurther embodiments provide a method for operating a sensing initiator entity of a wireless communication network. The method comprises a step of discovering one or more sensing candidate partner entities for a sensing area. Further, the method comprises a step of selecting at least one sensing partner entity out of the one or more discovered candidate sensing partner entities as sensing partner for sensing the sensing area.

[0148] Further embodiments provide a method for operating a sensing partner entity of a wireless communication network. The method comprises a step of being discoverable by a sensing initiator entity. Further, the method comprises a step of assisting the sensing initiator entity, in response to being selected as sensing partner by the sensing initiator entity, to sense a sensing area.

[0149] Further embodiments provide a method for operating a network entity of a wireless communication network. The method comprises a step of transmitting configuration messages to a sensing initiator entity and / or one or more sensing partner entities, the configuration messages configuring the sensing initiator entity and the one or more sensing partner entities to perform a sensing discovery procedure.

[0150] In embodiments, a sensing receiver can be an entity that receives the sensing signal which the sensing service will use in its operation. A sensing receiver can be part of a RAN node or a UE. A sensing receiver can be located in the same or different entity as the sensing transmitter.

[0151] In embodiments, a sensing transmitter can be an entity that sends out the sensing signal which the sensing service will use in its operation. A sensing transmitter can be part of a RAN node or a UE. A sensing transmitter can be located in the same or different entity as the sensing receiver.

[0152] In embodiments, a target sensing service area can be a (e.g., Cartesian, 3D) location area that needs to be sensed by deriving characteristics of the environment and / or objects within the environment, e.g., with certain sensing service quality from the impacted (e.g., reflected, refracted, diffracted) 3GPP radio signals. This includes both indoor and outdoor environments.

[0153] In embodiments, (wireless) sensing can be a feature providing capabilities to get information about characteristics of the environment and / or objects within the environment (e.g., shape,

[0154] FH250503PEP-2026154931. DOCXsize, orientation, speed, location, distances or relative motion between objects, etc.) using radio frequency signals.

[0155] In embodiments, a sensing entity can be an entity with sensing capabilities. A sensing entity can be either a sensing transmitter or a sensing receiver, indistinctly.

[0156] In embodiments, a sensing initiator can be an entity with sensing capabilities, which wants to do sensing. A sensing initiator can be either a sensing transmitter or a sensing receiver, indistinctly. Consequently, a sensing initiator can be either a UE or TRP.

[0157] In embodiments, a sensing partner can be an entity with sensing capabilities which assists the sensing initiator in performing bi-static sensing. A sensing partner can be either a sensing transmitter or a sensing receiver. Consequently, a sensing initiator can be either a UE or TRP.

[0158] Embodiments described herein can be applied in the context of ISAC and bi-static sensing. Embodiments describe how to discover and select the appropriate sensing partner (receiver or transmitter) for a defined sensing area.

[0159] Subsequently, embodiments of the present invention are described in further detail.

[0160] 1. T arget sensing service area

[0161] 1.1. From sensing initiator’s perspective

[0162] In some applications, a sensing entity does not necessarily require to be aware of its entire surrounding environment but only of a specific target sensing service area. Therefore, only objects located within this target sensing service area may be considered as targets which are to be detected by the sensing entity, whereas objects outside the target sensing service area are not targets and can thus be ignored.

[0163] Fig. 7 shows a schematic representation of a target sensing service area 120 of a sensing entity 122. Thereby, in Fig. 7 by way of example it is assumed that the sensing entity 122 is a vehicle, which wants to perform sensing. For this vehicle 122, the target sensing service area 120 may be located in the direction of driving 121 such that the vehicle 120 may become aware of potential hazards 124 (e.g., vulnerable road users, autonomous and / or service vehicles, etc.) which the vehicle 122 may encounter later down the road. On the other hand, sensing the

[0164] FH250503PEP-2026154931. DOCXarea opposite to the driving direction 121 of the vehicle 120 may be of less interest and less critical and the pedestrian 126 may not be considered as a target to be detected.

[0165] Therefore, in embodiments, the sensing entity 122 does not need to use all its beams 130 for sensing but instead use only a subset of beams 132 covering the target sensing service area 120 (i.e., the blue beams 132 Fig. 7). In particular, in embodiments, partial beam scanning by the sensing entity 122 can be sufficient:

[0166] • For sensing, i.e., only targets in the target sensing service area covered by the partial beam scanning may be detected. Note that targets outside that target sensing service area may nonetheless be detected if their contributions (e.g., due to reflections or scattering) are not too attenuated.

[0167] • For discovering relevant sensing partners (i.e., only the candidate sensing partners also covering the target sensing service area). See more details below in section 2.

[0168] 1.2. Mapping to sensing beams

[0169] In embodiments, all the sensing entities located in the environment surrounding the sensing initiator 122 may be considered as candidate sensing partners 140_1 and 140_2. However, the sensing initiator 122 should select carefully an appropriate sensing partner 140, depending on the specific target sensing service area 120 of interest for the sensing initiator 122, as shown in Fig. 8.

[0170] Fig. 8 shows a schematic representation of a selection of a sensing partner for sensing a target sensing area 120 of a sensing initiator 122. In the example of Fig. 8, sensing entity 140_1 may indeed be a good candidate sensing partner for the sensing initiator 122 because at least some of its beams 142_1 (i.e., the yellow beams in Fig. 8) sufficiently cover the target sensing service area 120. On the other hand, sensing entity 140_2 may not be a good candidate sensing partner for the sensing initiator 122 because its beams 142_2 (i.e., the purple beams in Fig. 8) may not sufficiently cover the target sensing service area 120.

[0171] In embodiments, the sensing beams of the sensing initiator 122 correspond to a subset of the beams 132 covering the target sensing service area 120 (i.e. the blue beams 132 in Fig. 8). These sensing beams 132 may be selected based on at least one of the following elements:

[0172] • the current position and / or orientation, and / or velocity of the sensing initiator 122, • the beam pattern of the sensing initiator 122, and

[0173] • the target sensing service area 120.

[0174] FH250503PEP-2026154931. DOCXIn one embodiment (Option 1), the description of the target sensing service area is shared by the sensing initiator with its sensing partner during the sensing discovery procedure (see section 2). In that case, the sensing beams of the sensing partner correspond to a subset of the beams of the sensing partner which are covering the target sensing area (e.g., the yellow beams 142_1 in Fig. 8). These sensing beams may be selected based on at least one of the following elements:

[0175] • the current position and / or orientation, and / or velocity of the sensing partner,

[0176] • the beam pattern of the sensing partner, and

[0177] • the target sensing service area.

[0178] Owing to mobility, in some embodiments, both the sensing initiator and the sensing partner may need to regularly update (i): their sensing beams in order to keep covering the target sensing service area, and (ii): the target sensing service area itself which is defined with respect to the sensing initiator. For that purpose, the sensing initiator may periodically share with its sensing partner updated geographical information about the target sensing service area, which may change with the mobility of the sensing initiator.

[0179] In another embodiment (Option 2), the sensing initiator may prefer not to share any geographical information about the target sensing service area with the sensing partner, e.g., out of privacy concerns. In this situation, the sensing partner remains unaware of the target sensing service area and may therefore use all its beams for sensing.

[0180] Note that, in some embodiments, this option may be (pre-)configured as default behavior for the sensing partner if no geographical information about the target sensing service area is shared by the sensing initiator during the sensing discovery procedure.

[0181] Note that, in some embodiments, the selection of the sensing beams of the sensing partner to be used for sensing the target sensing service area may be transparent for the sensing initiator.

[0182] 2. _ Sensing discovery procedure

[0183] In embodiments, the sensing discovery procedure may take place on the llu interface, i.e., between transmission reception points (TRPs) and user equipment (UEs). Hence, if the sensing initiator is a TRP, all the sensing entities which can be discovered by the sensing initiator can be only UEs. Otherwise, if the sensing initiator is a UE, all the sensing entities which can be discovered by the sensing initiator can be only TRPs.

[0184] FH250503PEP-2026154931. DOCXAlternatively, the sensing discovery procedure may take place on sidelink (direct link between UEs). In that case, all the sensing entities which can be discovered by the sensing initiator can be only UEs

[0185] 2.1 Case 1: Candidate sensing partners as monitoring sensing entity

[0186] Fig. 9 shows a schematic representation of the sensing discovery procedure performed between the sensing initiator entity 122 and the candidate sensing partner entities 140_1 to 140_n (wherein n is a natural number egual to or greater than one or two) acting as monitoring sensing entities. Thereby, note that in Fig. 9 the signaling exchange / steps are optional, i.e., only some steps may apply.

[0187] In step 301, the network 150 transmits a configuration message to each network element 122, 140_1 to 140_n (i.e., TRPs and UEs), indicating that they are authorized to operate as a bistatic sensing entity, either as a sensing initiator or as a sensing partner for another sensing entity.

[0188] In embodiments, the network 150 may obtain information about their sensing capabilities from the network elements 122, 140_1 to 140_n themselves. The configuration message may include at least one of the following:

[0189] • a sensing entity identifier (ID), which uniguely identifies the sensing entity (e.g., in the network, in the cell or in the sensing session / context),

[0190] • a group identifier (ID), which indicates that the sensing entity belongs to a specific group,

[0191] • an activation type, which identifies a candidate sensing partner either as an announcing sensing entity (i.e., which transmits sensing discovery reguests) or as a monitoring sensing entity (i.e., which listens for sensing discovery reguests).

[0192] In step 302, upon configuration, the sensing initiator 122 may trigger a sensing discovery procedure whenever (i): the sensing initiator 122 wants to start sensing a specific target sensing service area, or (ii): its sensing partner in an ongoing sensing session gets out of communication / sensing range (e.g., due to mobility), i.e. is no longer suitable to operate as a sensing partner for the target sensing area.

[0193] On the other hand, the sensing entities (i.e., candidate sensing partners 140_1 to 140_n) start to monitor periodically on each of their beams for detection of a first sensing discovery reguest, see step 303.

[0194] FH250503PEP-2026154931. DOCXIn step 303, in order to discover sensing entities 140_1 to 140_n within its sensing / communication range, the sensing initiator 122 needs to periodically broadcast on each of its sensing beams a first sensing discovery request which contains at least one of the following information:

[0195] • a sensing entity ID, which uniquely identifies the sensing initiator,

[0196] • a position and / or a velocity of the sensing initiator,

[0197] • the geographical location of the target sensing service area:

[0198] - e.g., based on the Universal Geographical Area Description (GAD) in [3], - the target sensing service area may be extended to three dimensions (3-D) by including altitude information, e.g., for sensing UAV objects,

[0199] • the sensing quality requirements, indicating the sensing class required by the sensing initiator:

[0200] - the sensing class corresponds to the quality of service (QoS) of the sensing operation and may be defined in terms of, e.g., delay / time / angular resolution, • sensing capabilities of the sensing initiator.

[0201] Note that, in some embodiments, only entities with sensing capabilities are able to decode the first sensing discovery request, i.e., TRPs with sensing capabilities or UEs with sensing capabilities if the message was sent on Uu interface, and UEs with sensing capabilities if the message was sent on sidelink.

[0202] In step 304, upon reception of a first sensing discovery request, a monitoring sensing entity 140_1 to 140_n may determine whether it has the capability to support the sensing initiator 122 in the sensing procedure, based on the received sensing quality requirements information. If so, the monitoring sensing entity 140_1 to 140_n may transmit a sensing discovery response to the sensing initiator (i): on each of its beams (e.g., if no geographical location of the target sensing service area was provided in the first sensing discovery request), (ii): on each of the beams on which the sensing entity received a first sensing discovery request, or (iii): on each of its sensing beams (e.g., if the geographical location of the target sensing service area was provided in the first sensing discovery request). The sensing discovery response may contain at least one of the following information:

[0203] • a sensing entity ID, which uniquely identifies the candidate sensing partner,

[0204] • the position and / or orientation, and / or velocity of the candidate sensing partner.

[0205] FH250503PEP-2026154931. DOCXIn step 305, the sensing initiator 122 may select one sensing entity as sensing partner among the candidates of at least one sensing entity which did send a sensing discovery response. See section 3.1 for a discussion about the selection criterion.

[0206] In step 306, the sensing initiator 122 may transmit a sensing activation request which may contain the ID of the sensing entity selected as sensing partner.

[0207] In step 307, when the selected sensing entity receives the sensing activation request, it recognizes that it contains its own sensing entity ID and may activate its sensing function.

[0208] 2.2 Case 2: Candidate sensing partners as announcing sensing entities

[0209] Fig. 10 shows a schematic representation of a sensing discovery procedure performed between the sensing initiator 122 and candidate sensing partners 140_1 to 140_n acting as announcing sensing entities. Thereby, note that in Fig. 10 the signaling exchange / steps are optional, i.e. , only some steps may apply.

[0210] In step 401 (same as step 301 of Fig. 9), the network 150 transmits a configuration message to each network element 122, 140_1 to 140_n, indicating that they are authorized to operate as a bi-static sensing entity, either as a sensing initiator 122 or as a sensing partner 140_1 to 140_n for another sensing entity. Note that the network 150 can obtain from the network elements 122, 140_1 to 140_n themselves the information about their sensing capabilities. The configuration message may include at least one of the following:

[0211] • a sensing entity identifier (ID), which uniquely identifies the sensing entity (e.g., in the network, cell or sensing session / context),

[0212] • a group identifier (ID), which indicates that the sensing entity belongs to a specific group,

[0213] • an activation type, which identifies a candidate sensing partner either as an announcing sensing entity (i.e., which transmits sensing discovery requests) or as a monitoring sensing entity (i.e., which listens for sensing discovery requests).

[0214] In step 402, upon configuration, the sensing initiator 122 starts to monitor periodically on each of its beams for detection of a sensing discovery request from other sensing entities 140_1 to 140_n, see step 403, whenever (i): the sensing initiator 122 wants to start sensing a target sensing service area, or (ii): its sensing partner in an ongoing sensing session gets out of communication / sensing range (e.g., due to mobility).

[0215] FH250503PEP-2026154931. DOCXIn step 403, the sensing entities periodically broadcast on each of their beams a sensing discovery request which contains at least one of the following information:

[0216] • a sensing entity ID, which uniquely identifies the sensing entity,

[0217] • the position and / or orientation, and / or velocity of the sensing entity,

[0218] • the sensing quality capabilities, indicating the sensing class(es) supported by the sensing entity.

[0219] Note that, in some embodiments, only sensing entities with sensing capabilities are able to decode the sensing discovery request, i.e., TRPs with sensing capabilities or UEs with sensing capabilities if the message was sent on llu interface, and UEs with sensing capabilities if the message was sent on sidelink.

[0220] In step 404, upon reception of a sensing discovery request, the sensing initiator 122 may determine whether the associated sensing entity has the capability to support the sensing initiator in the sensing procedure, based on the received sensing quality requirements information.

[0221] In embodiments, the sensing initiator 122 may select one sensing entity as sensing partner among the pool of at least one sensing entity which did send a sensing discovery response (e.g., same as step 305 of Fig. 9). See section 3.1 for a discussion about the selection criterion.

[0222] In step 405, the sensing initiator may transmit a sensing discovery response which contains at least one of the following information

[0223] • a sensing entity ID, which uniquely identifies the selected sensing partner,

[0224] • the geographical location of the target sensing service area:

[0225] - e.g., based on the GAD in [3],

[0226] - the target sensing service area may be extended to 3-D by including altitude information, e.g., for sensing UAV objects.

[0227] In step 406 (e.g., same as step 307 of Fig. 9), when the selected sensing entity receives the sensing discovery response, it may recognize that it contains its own sensing entity ID and may activate its sensing function.

[0228] 2.3. A special case: TRP-to-TRP bi-static sensing

[0229] Typically, TRPs are installed in fixed positions and are static. As a consequence, the sensing discovery procedure may not be necessary in the case of TRP-to-TRP bi-static sensing.

[0230] FH250503PEP-2026154931. DOCXInstead, in embodiments, the TRP sensing initiator may be (pre-)configured with a lookup table associating different target sensing service areas with a preferred TRP sensing partner.

[0231] In embodiments, discovery and information on sensing capabilities / configurations between TRPs can also be exchanged directly via the Xn interface or (pre-)configured via the network to the TRPs.

[0232] 3. _ Sensing partner selection

[0233] 3.1 Selection criterion

[0234] In embodiments, one criterion for the sensing initiator to select a sensing partner may be based on the quality of the link, e.g. sensing or communication link, between the sensing initiator and the candidate sensing partner. The sensing initiator may measure on each of its sensing beams quantities such as the received signal strength indicator (RSSI), the reference signal received power (RSRP) or the signal-to-noise ratio (SNR) based on the sensing discovery response (Case 1) or on the sensing discovery requests (Case 2) sent by the sensing entities (see section 2). To be more specific, a sensing entity may be selected as a sensing partner if, e.g., one of the following options applies:

[0235] • the measured RSSI, RSRP or SNR on each sensing beam of the sensing initiator is higher than a (pre-)configured threshold, or

[0236] • the average of the measured RSSI, RSRP or SNR across all the sensing beams of the sensing initiator is higher than a (pre-)configured threshold,

[0237] i.e. , if the sensing entity provides good coverage of the target sensing service area from the sensing initiator’s point of view.

[0238] Alternatively, the sensing initiator can select a sensing entity as a sensing partner considering any other requirement, e.g.,

[0239] • the position of the sensing entity with respect to the target sensing service area, or • using the position of the sensing entity provided in the sensing discovery response (Case 1) or in the sensing discovery request (Case 2).

[0240] In embodiments, when the sensing initiator needs to down-select one or more sensing partner(s) which satisfy the selection criterion, this can be performed based on at least one of the following criteria:

[0241] • prioritization of the candidate sensing partners:

[0242] FH250503PEP-2026154931. DOCX- it may be preferrable to initiate a sensing session with static candidate sensing partners over moving candidate sensing partners,

[0243] E.g. to prefer TRPs (i.e. , a first type, higher priority) over UEs (i.e., a second type, lower priority), since TRPs are always static and the corresponding sensing link may remain stable for a longer period than with moving UEs, a candidate sensing partner located at a smaller distance to a reference point [e.g., center] of the sensing area is preferred over another candidate sensing partner located at a greater distance to the reference point,

[0244] the prioritization of a sensing entity may be defined by either (i): the sensing entity itself, (ii): network signaling, (iii): higher layers, or (iv): (pre-)configuration,

[0245] • the sensing capabilities of the candidate sensing partners:

[0246] - e.g., the sensing initiator may decide to initiate a sensing session with a sensing entity with sensing capabilities closest to the sensing quality requirements expected by the sensing initiator.

[0247] 3.2 Selecting multiple sensing partners

[0248] In embodiments, the sensing initiator may select multiple sensing entities as sensing partners. In that case, steps 306 and 405 of Figs. 9 and 10 can be updated as follows, for Case 1 and Case 2, respectively:

[0249] • Step 306: The sensing activation request is sent either to (i): each selected sensing entity individually (with only the ID of the sensing entity to which the message is addressed), or (ii): all the selected sensing entities (with a list of the IDs of all the selected sensing entities).

[0250] • Step 405: The sensing discovery response is sent either to (i): each selected sensing entity individually (with the ID of the sensing entity to which the message is addressed), or (ii): all the selected sensing entities (with a list of the IDs of all the selected sensing entities).

[0251] 4. Summary and further embodiments

[0252] Fig. 11 shows a flow chart of the discovery and selection procedure to support the sensing of a target sensing service area. Thereby, the sensing initiator may select at least one sensing partner. Note that any step of Fig. 11 may be optional.

[0253] In a first step 401 , a target sensing service area can be defined. In a second step 402 (optional), a subset of sensing beams covering the target sensing service area can be selected. In a third

[0254] FH250503PEP-2026154931. DOCXstep 403, candidate sensing entities can be discovered (e.g., in a surrounding). In step 404, at least one sensing partner among the sensing entities can be selected.

[0255] Embodiments described herein can improve safety on the roads, especially for vulnerable road users and vehicles.

[0256] Various elements and features of the present invention may be implemented in hardware using analog and / or digital circuits, in software, through the execution of instructions by one or more general purpose or special-purpose processors, or as a combination of hardware and software. For example, embodiments of the present invention may be implemented in the environment of a computer system or another processing system. Fig. 12 illustrates an example of a computer system 500. The units or modules as well as the steps of the methods performed by these units may execute on one or more computer systems 500. The computer system 500 includes one or more processors 502, like a special purpose or a general-purpose digital signal processor. The processor 502 is connected to a communication infrastructure 504, like a bus or a network. The computer system 500 includes a main memory 506, e.g., a random-access memory (RAM), and a secondary memory 508, e.g., a hard disk drive and / or a removable storage drive. The secondary memory 508 may allow computer programs or other instructions to be loaded into the computer system 500. The computer system 500 may further include a communications interface 510 to allow software and data to be transferred between computer system 500 and external devices. The communication may be in the from electronic, electromagnetic, optical, or other signals capable of being handled by a communications interface. The communication may use a wire or a cable, fiber optics, a phone line, a cellular phone link, an RF link and other communications channels 512.

[0257] The terms “computer program medium” and “computer readable medium” are used to generally refer to tangible storage media such as removable storage units or a hard disk installed in a hard disk drive. These computer program products are means for providing software to the computer system 500. The computer programs, also referred to as computer control logic, are stored in main memory 506 and / or secondary memory 508. Computer programs may also be received via the communications interface 510. The computer program, when executed, enables the computer system 500 to implement the present invention. In particular, the computer program, when executed, enables processor 502 to implement the processes of the present invention, such as any of the methods described herein. Accordingly, such a computer program may represent a controller of the computer system 500. Where the disclosure is implemented using software, the software may be stored in a computer program

[0258] FH250503PEP-2026154931. DOCXproduct and loaded into computer system 500 using a removable storage drive, an interface, like communications interface 510.

[0259] The implementation in hardware or in software may be performed using a digital storage medium, for example cloud storage, a floppy disk, a DVD, a Blue-Ray, a CD, a ROM, a PROM, an EPROM, an EEPROM or a FLASH memory, having electronically readable control signals stored thereon, which cooperate (or are capable of cooperating) with a programmable computer system such that the respective method is performed. Therefore, the digital storage medium may be computer readable.

[0260] Some embodiments according to the invention comprise a data carrier having electronically readable control signals, which are capable of cooperating with a programmable computer system, such that one of the methods described herein is performed.

[0261] Generally, embodiments of the present invention may be implemented as a computer program product with a program code, the program code being operative for performing one of the methods when the computer program product runs on a computer. The program code may for example be stored on a machine-readable carrier.

[0262] Other embodiments comprise the computer program for performing one of the methods described herein, stored on a machine-readable carrier. In other words, an embodiment of the inventive method is, therefore, a computer program having a program code for performing one of the methods described herein, when the computer program runs on a computer.

[0263] A further embodiment of the inventive methods is, therefore, a data carrier (or a digital storage medium, or a computer-readable medium) comprising, recorded thereon, the computer program for performing one of the methods described herein. A further embodiment of the inventive method is, therefore, a data stream or a sequence of signals representing the computer program for performing one of the methods described herein. The data stream or the sequence of signals may for example be configured to be transferred via a data communication connection, for example via the Internet. A further embodiment comprises a processing means, for example a computer, or a programmable logic device, configured to or adapted to perform one of the methods described herein. A further embodiment comprises a computer having installed thereon the computer program for performing one of the methods described herein.

[0264] FH250503PEP-2026154931. DOCXIn some embodiments, a programmable logic device (for example a field programmable gate array) may be used to perform some or all of the functionalities of the methods described herein. In some embodiments, a field programmable gate array may cooperate with a microprocessor in order to perform one of the methods described herein. Generally, the methods are preferably performed by any hardware apparatus.

[0265] The above-described embodiments are merely illustrative for the principles of the present invention. It is understood that modifications and variations of the arrangements and the details described herein are apparent to others skilled in the art. It is the intent, therefore, to be limited only by the scope of the impending patent claims and not by the specific details presented by way of description and explanation of the embodiments herein.

[0266] FH250503PEP-2026154931. DOCXList of References

[0267] [1] 3GPP TS 22 137 v19.1.0, “Service requirements for Integrated Sensing and Communication,” Apr. 2024.

[0268] [2] 3GPP TS 22261 v20.1.0, “Service requirements for the 5G system,” Dec. 2024.

[0269] [3] 3GPP TS 23.032 v18.3.0, “Universal Geographical Area Description (GAD) (Release 18), Dec 2024.

[0270] FH250503PEP-2026154931. DOCXAbbreviations

[0271] 3D three dimensions

[0272] 3GPP third generation partnership project

[0273] BS base station

[0274] CQI channel quality indicator

[0275] CRI CSI-RS resource indicator

[0276] CSI channel state information

[0277] CSI-RS channel state information - reference signal

[0278] D2D device-to-device

[0279] DCI downlink control information

[0280] DL downlink

[0281] eNB evolved node B

[0282] FR frequency range

[0283] FR1 frequency range one

[0284] FR2 frequency range two

[0285] GAD universal geographical area description

[0286] gNB next generation node B

[0287] HARQ hybrid automatic repeat request

[0288] ID identity

[0289] ISAC Integrated sensing and communication

[0290] LTE long-term evolution

[0291] MAC medium access control

[0292] MAC-CE medium access control - control element

[0293] NACK negative acknowledgement

[0294] NES network energy saving

[0295] NR new radio

[0296] OFDM orthogonal frequency-division multiplexing

[0297] OFDMA orthogonal frequency-division multiple access

[0298] PBCH physical broadcast channel

[0299] PC5 interface using the sidelink channel for D2D communication PDCCH physical downlink control channel

[0300] PDSCH physical downlink shared channel

[0301] PRACH physical random access channel

[0302] PSBCH physical sidelink broadcast channel

[0303] PSCCH physical sidelink control channel

[0304] FH250503PEP-2026154931. DOCXPSFCH physical sidelink feedback channel PSSCH physical sidelink shared channel PUCCH physical uplink control channel

[0305] PUSCH physical uplink shared channel

[0306] QoS quality of service

[0307] RACH random access channel

[0308] RAN radio access network

[0309] RB resource block

[0310] RE resource element

[0311] RRC radio resource control

[0312] RS reference signal

[0313] RSRP reference signal received power

[0314] RSRQ reference signal received quality

[0315] RSS received signal strength

[0316] RSSI received signal strength indicator

[0317] RSU road side unit

[0318] SCI sidelink control information

[0319] SI system information

[0320] SIB system information block

[0321] SNR signal-to-noise ratio

[0322] SL sidelink

[0323] SRS sounding reference signal

[0324] SSB synchronization signal block

[0325] SSS secondary synchronization signal

[0326] S-SSB sidelink synchronization signal block sTTI short transmission time interval

[0327] TTI transmission time interval

[0328] TRP transmit receive point

[0329] UAV unmanned aerial vehicle

[0330] UE user equipment

[0331] UL uplink

[0332] UMTS universal mobile telecommunication system V2V vehicle-to-vehicle

[0333] V2X vehicle-to-everything

[0334] FH250503PEP-2026154931. DOCX

Claims

Claims1. Sensing initiator entity of a wireless communication network,wherein the sensing initiator entity is configured to discover one or more sensing candidate partner entities for sensing a sensing area,wherein the sensing initiator entity is configured to select at least one sensing partner entity out of the one or more discovered candidate sensing partner entities as sensing partner for sensing the sensing area.

2. Sensing initiator entity according to claim 1,wherein the sensing initiator entity is configured to select a subset of beams covering the sensing area out of a plurality of different beams.

3. Sensing initiator entity according to claim 1 or 2,wherein the sensing initiator entity is configured to select the subset of beams out of the plurality of different beams in dependence on at least one out ofa position of the sensing initiator entity,an orientation of the sensing initiator entity,a velocity of the sensing initiator entity,a beam pattern of the sensing initiator entity, andthe sensing area.

4. Sensing initiator entity according to one of the claims 1 to 3,wherein the plurality of different beams is usable by the sensing initiator entity for transmitting and / or receiving radio signals of the wireless communication network.

5. Sensing initiator entity according to one of the claims 1 to 4,wherein the sensing initiator entity is configured to receive a configuration message,wherein the sensing initiator entity is configured, in case that the configuration message indicates a first activation type, to discover the one or more sensingFH250503PEP-2026154931. DOCXcandidate partner entities by transmitting a discovery request, and receiving one or more discovery responses from the one or more sensing candidate partner entities.

6. Sensing initiator entity according to claim 5,wherein the sensing initiator entity is configured to transmit the discovery request using a selected subset of beams selected out of the plurality of different beams.

7. Sensing initiator entity according to claim 6,wherein the sensing initiator entity is configured to transmit the discovery request on each beam of the selected subset of beams.

8. Sensing initiator entity according to one of the claims 5 to 7,wherein the discovery request indicates at least one out ofan identity of the sensing initiator entity,a position of the sensing initiator entity,a velocity of the sensing initiator entity,the sensing area,sensing requirements,sensing capabilities of the sensing initiator entity.

9. Sensing initiator entity according to one of the claims 5 to 8,wherein the sensing initiator entity is configured to transmit a at least one sensing activation request indicating an identity of the at least one sensing partner entity selected as sensing partner.

10. Sensing initiator entity according to one of the claims 1 to 4,wherein the sensing initiator entity is configured to receive a configuration message,wherein the sensing initiator entity is configured, in case that the configuration message indicates a second activation type, to discover the one or more sensing candidate partner entities by receiving one or more discovery requests from the one or more sensing candidate partner entities.FH250503PEP-2026154931. DOCX11. Sensing initiator entity according to claim 10,wherein each of the one or more discovery requests indicates at least one out of: an identity of the respective sensing partner entity,a position of the respective sensing partner entity,an orientation of the respective sensing partner entity,a velocity of the respective sensing partner entity,sensing capabilities of the respective sensing partner entity.

12. Sensing initiator entity according to claim 10 or 11,wherein the sensing initiator entity is configured to transmit at least one discovery response indicating an identity of the at least one sensing partner entity selected as sensing partner.

13. Sensing initiator entity according to claim 12,wherein the discovery response indicates the sensing area.

14. Sensing initiator entity according to one of the claims 1 to 4,wherein the sensing initiator entity is configured to receive a configuration message,wherein the sensing initiator entity is configured, in case that the configuration message indicates a third activation type, to discover and select the at least one sensing partner entity for sensing the sensing area based on a look-up table.

15. Sensing initiator entity according to claim 15,wherein the look-up table describes different sensing areas and associated sensing partner entities.

16. Sensing initiator entity according to claim 14 or 15,FH250503PEP-2026154931. DOCXwherein the sensing initiator entity is configured to transmit a sensing activation request indicating an identity of the at least one sensing partner entity selected as sensing partner.

17. Sensing initiator according to claim 16,wherein the sensing initiator is configured to transmit the sensing activation request via the Xn interface.

18. Sensing initiator entity according to one of the claims 1 to 17,wherein the sensing initiator entity is configured to receive a configuration message from a network entity of the wireless communication network, the configuration message indicating that sensing initiator entity is allowed to switch into a sensing mode of operation.

19. Sensing initiator entity according to claim 18,wherein the sensing initiator entity is configured to switch into the sensing mode of operation in response to the reception of the configuration message.

20. Sensing initiator entity according to claim 18,wherein the configuration message indicates at least one out ofan identity allocated to the sensing initiator entity,an identity of a sensing group to which the sensing initiator entity belongs, an activation type.

21. Sensing initiator entity according to one of the claims 1 to 20,wherein the sensing initiator entity is configured to transmit an information message to the network entity, the information message indicating sensing capabilities of the sensing initiator entity.

22. Sensing initiator entity according to one of the claims 1 to 21 ,FH250503PEP-2026154931. DOCXwherein the sensing initiator entity is configured to select the at least one sensing partner entity out of the one or more candidate sensing partner entities based on a quality of a link between the sensing initiator entity and a respective candidate sensing partner entity.

23. Sensing initiator entity according to claim 22,wherein the sensing initiator is configured to determine the quality of the link by performing quality measurements based on a signal received from the respective candidate sensing partner entity.

24. Sensing initiator entity according to claim 23,wherein the sensing initiator is configured to determine the quality of the link using each beam of the subset of beams.

25. Sensing initiator entity according to one of the claims 22 to 24,wherein the sensing initiator is configured to select the at least one sensing partner entity out of the one or more candidate sensing partner in case that the quality of the link between the sensing initiator entity and a respective candidate sensing partner entity fulfills a quality selection criterion.

26. Sensing initiator entity according to one of the claims 22 to 24,wherein the sensing initiator entity is configured to select the at least one sensing partner entity out of the one or more candidate sensing partner entities based on a position of the respective candidate sensing partner entity.

27. Sensing initiator entity according to one of the claims 1 to 26,wherein the sensing initiator entity is configured to prefer a candidate sensing partner entity in the selection of the at least one sensing partner entity out of the one or more candidate sensing partner entities that fulfills a preference selection criterion.

28. Sensing initiator entity according to claim 27,FH250503PEP-2026154931. DOCXwherein the preference selection criterion includes at least one out of static candidate sensing partner entities are preferred over moving candidate sensing partner entities,a first type of candidate sensing partner entities are preferred over a second type candidate sensing partner entities,a candidate sensing partner located at a smaller distance to a reference point of the sensing area is preferred over another candidate sensing partner located at a greater distance to the reference point,a candidate sensing partner fulfilling sensing requirements to a higher degree is preferred over a candidate sensing partner that fulfills the sensing requirements to a lower degree.

29. Sensing initiator entity according to claim 27 or 28,wherein the preference selection criterion is defined by the sensing initiator entity itself, network signaling, higher layers, or (pre-)configuration.

30. Sensing initiator entity according to one of the claims 1 to 29wherein the sensing initiator entity is a user equipment, UE, or a transmit receive point, TRP,.

31. Sensing partner entity of a wireless communication network,wherein the sensing partner entity is discoverable by a sensing initiator entity,wherein the sensing partner entity is configured, in response to being selected as sensing partner by the sensing initiator entity, to assist the sensing initiator entity in sensing a sensing area.

32. Sensing partner entity according to claim 31 ,wherein the sensing partner entity is configured to select a subset of beams out of a plurality of different beams covering a sensing area of the sensing initiator entity.

33. Sensing partner entity according to claim 32,FH250503PEP-2026154931. DOCXwherein the sensing partner entity is configured to select the subset of beams out of the plurality of different beams in dependence on at least one out ofa position of the sensing partner entity,an orientation of the sensing partner entity,a velocity of the sensing partner entity,a beam pattern of the sensing partner entity, andthe sensing area of the sensing initiator entity.

34. Sensing partner entity according to claim 32 or 33,wherein the plurality of different beams is usable by the sensing partner entity for transmitting and / or receiving radio signals of the wireless communication network.

35. Sensing partner entity according to one of the claims 31 to 34,wherein the sensing partner entity is configured to receive a configuration message,wherein the sensing partner entity is discoverable by the sensing initiator entity, in case that the configuration message indicates a first activation type, by receiving a discovery request from the sensing initiator entity and transmitting a discovery response to the sensing initiator entity.

36. Sensing partner entity according to claim 35,wherein the sensing partner entity is configured to transmit the discovery response on each beam of a plurality of different beams,or on each beam the sensing partner entity received the discovery request, or on each beam of a selected subset of beams in case that the discovery request indicates the sensing area.

37. Sensing partner entity according to claim 35 or 36,wherein the discovery response indicates at least one out ofan identity of the sensing partner entity,a position of the sensing partner entity,an orientation of the sensing partner entity,a velocity of the sensing partner entity.FH250503PEP-2026154931. DOCX38. Sensing partner entity according to one of the claims 35 to 37,wherein the sensing partner entity is configured to transmit the discovery response only in case that sensing partner entity fulfills sensing quality requirements indicated in the discovery request.

39. Sensing partner entity according to one of the claims 35 to 38,wherein the sensing partner entity is configured to receive a sensing activation request indicating an identity of the at least one selected sensing partner entity,wherein the sensing partner entity is configured to switch into a sensing partner mode of operation in case that it is identified by the identity indicated in the sensing activation request.

40. Sensing partner entity according to one of the claims 31 to 34,wherein the sensing partner entity is configured to receive a configuration message,wherein the sensing partner entity is discoverable by the sensing initiator entity, in case that the configuration message indicates a second activation type, by transmitting a discovery request to the sensing initiator entity.

41. Sensing partner entity according to claim 40,wherein the discovery request indicates at least one out of:an identity of the sensing partner entity,a position of the sensing partner entity,an orientation of the sensing partner entity,a velocity of the sensing partner entity,sensing capabilities of the sensing partner entity,a potential sensing area that can be covered by the sensing partner entity.

42. Sensing partner entity according to claim 40 or 41 ,FH250503PEP-2026154931. DOCXwherein the sensing partner entity is configured to receive a discovery response indicating an identity of the selected sensing partner entity selected by the sensing initiator entity as sensing partner,wherein the sensing partner entity is configured to switch into a sensing partner mode of operation in case that it is identified by the identity indicated in the discovery response.

43. Sensing partner entity according to one of the claims 31 to 34,wherein the sensing partner entity is configured to receive a configuration message,wherein the sensing partner entity is discoverable by the sensing initiator entity, in case that the configuration message indicates a third activation type, based on a lookup table.

44. Sensing partner entity according to claim 43,wherein the look-up table describes different sensing areas and associated sensing partner entities.

45. Sensing partner entity according to claim 43 or 44,wherein the sensing partner entity is configured to receive a sensing activation request indicating an identity of the at least one sensing partner entity selected as sensing partner,wherein the sensing partner entity is configured to switch into a sensing partner mode of operation in case that it is identified by the identity indicated in the sensing activation request.

46. Sensing partner according to claim 45,wherein the sensing partner is configured to receive the sensing activation request via the Xn interface.

47. Sensing partner entity according to one of the claims 31 to 46,FH250503PEP-2026154931. DOCXwherein the sensing partner entity is configured to receive a configuration message from a network entity of the wireless communication network, the configuration message indicating that sensing partner entity is allowed to switch into a sensing mode of operation.

48. Sensing partner entity according to claim 47,wherein the sensing partner entity is configured to switch into the sensing mode of operation in response to the reception the configuration message.

49. Sensing partner entity according to claim 47 or 48,wherein the configuration message indicates at least one out ofan identity allocated to the sensing partner entity,an identity of a sensing group to which the sensing partner entity belongs, an activation type.

50. Sensing partner entity according to one of the claims 31 to 49,wherein the sensing partner entity is configured to transmit an information message to the network entity, the information message indicating sensing capabilities of the sensing partner entity.

51. Sensing partner entity according to one of the claims 31 to 50,wherein the sensing partner entity is a user equipment, UE, ora transmit receive point, TRP.

52. Network entity of a wireless communication network,wherein the network entity is configured to transmit configuration messages to a sensing initiator entity and / or one or more sensing partner entities, the configuration messages configuring the sensing initiator entity and the one or more sensing partner entities to perform a sensing discovery procedure.

53. Network entity according to claim 52,FH250503PEP-2026154931. DOCXwherein the configuration message indicates at least one out ofan identity allocated to the respective sensing initiator entity or sensing partner entity,an identity of a sensing group to which the respective sensing initiator entity or sensing partner entity belongs,an activation type of the respective sensing initiator entity or sensing partner entity.

54. Network entity according to claim 52 or 53,wherein the network entity is a core network node or core network function or a radio access network node.

55. Wireless communication network, comprising at least two out of a sensing initiator entity according to one of the claims 1 to 30, a sensing partner entity according to one of the claims 31 to 51 , and a network entity according to one of the claims 52 to 54.

56. Method for operating a sensing initiator entity of a wireless communication network, the method comprising:discovering one or more sensing candidate partner entities for a sensing area, andselecting at least one sensing partner entity out of the one or more discovered candidate sensing partner entities as sensing partner for sensing the sensing area.

57. Method for operating a sensing partner entity of a wireless communication network, the method comprising:being discoverable by a sensing initiator entity, andassisting the sensing initiator entity, in response to being selected as sensing partner by the sensing initiator entity, to sense a sensing area.

58. Method for operating a network entity of a wireless communication network, the method comprising:FH250503PEP-2026154931. DOCXtransmitting configuration messages to a sensing initiator entity and / or one or more sensing partner entities, the configuration messages configuring the sensing initiator entity and the one or more sensing partner entities to perform a sensing discovery procedure.

59. Computer program for performing a method according to one of the claims 56 to 58.FH250503PEP-2026154931. DOCX