Sidelink-based sensing

Abstract

The invention discloses UE, an apparatus, a base station and a method for sidelink-based sensing. In one aspect, a first UE receives a first sensing service request from a first apparatus or base station. The first sensing service request includes at least first information about a sensing task. In turn, the first UE sends second information about the sensing task via a sidelink.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically, to apparatus and methods for sidelink-based sensing. Background Technology

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

[0003] Wireless sensing technology aims to acquire information about objects, their environment, and their characteristics without physical contact. Sensing data about objects and their surroundings can be used for analysis, allowing meaningful information about the objects and their properties to be obtained. This can be achieved using cameras, radar, lidar, and other similar technologies.

[0004] There are also studies and solutions regarding how communication technologies (e.g., Long Term Evolution (LTE), New Radio (NR), Wireless Local Area Networks (WLANs), etc.) can be utilized for sensing. Alternatives exist for enhancing cellular wireless communication systems, such as the fifth-generation system (5GS) as defined by the 3rd Generation Partnership Project (3GPP), to incorporate wireless sensing. In other words, in addition to traditional communication services, wireless systems can perform sensing tasks and report the results to applications, customers, or industries interested in the sensing results. Sensing can also be used within wireless communication systems to improve network performance. Integrated Sensing and Communication (ISAC) refers to technologies that combine sensing and communication systems to utilize wireless resources more effectively. ISAC, provided by 3GPP 5GS, means that sensing capabilities are provided by the same 5G NR wireless communication systems and infrastructure used for communication, and sensing information can be derived from radio frequency (RF) based and / or non-RF based sensors.

[0005] In research on ISAC, the Sensing Function (SF) has been introduced to enable sensing in 5GS networks. The SF can be a standalone Network Function (NF) or co-located with an existing NF, such as a Location Management Function (LMF). Radio Access Network (RAN) nodes can communicate with the SF via a Mobility Management Function (AMF) or directly. The sensing process can be triggered by an application server, a 5GC NF, or a UE. The SF can assign sensing tasks to access nodes (e.g., RAN nodes in 3GPP, or WLAN access nodes outside of 3GPP) or UEs. Summary of the Invention

[0006] This disclosure relates to a UE, apparatus, base station, and method for sidelink-based sensing. Using the UE, apparatus, base station, and method, sidelink-based sensing can be implemented.

[0007] Some implementations of the first UE described herein may include a processor and a transceiver coupled to the processor. The processor is configured to: receive a first sensing service request from a first device or base station via the transceiver, the first sensing service request including at least first information about a sensing task; and transmit second information about the sensing task via the transceiver and a side link.

[0008] In some implementations, the processor is configured to send second information about the sensing task via a transceiver in either broadcast or multicast mode via a transceiver and a side link.

[0009] In some implementations, the first information about the sensing task includes the first ID of the sensing task, and the second information about the sensing task includes the second ID of the sensing task.

[0010] In some implementations, the processor is configured to send second information about the sensing task via a transceiver by sending a direct communication request message via the transceiver and a side link, the direct communication request message including a second ID of the sensing task and information about the sensing service type.

[0011] In some implementations, the processor is further configured to: determine a destination layer 2 ID associated with the sensing service type; and the processor is configured to send second information about the sensing task via the transceiver by sending a broadcast or multicast communication request message via the transceiver and a side link, the broadcast or multicast communication request message including the second ID of the sensing task and the destination layer 2 ID.

[0012] In some implementations, the processor is also configured to obtain information about the association between the destination layer 2 ID and the sensing service type from one of the following: a first device, a second device, or an application server.

[0013] In some implementations, the first sensing service request further includes at least one of the following: a sensing requirement associated with a sensing task, a sensing mode associated with a sensing task, a first instruction instructing a first UE to send a sensing signal, a second instruction instructing the first UE to collect sensing measurement data associated with the sensing task from at least one second UE and send the sensing measurement data to a first device, the at least one second UE receiving a reflected signal associated with the sensing signal, information regarding the transmission of the sensing measurement data via a user plane connection between the first device and the first UE, or a first sidelink signal threshold, the first UE determining whether a candidate UE is identified as one of the at least one second UE based on the first sidelink signal threshold.

[0014] Some implementations of the second UE described herein may include a processor and a transceiver coupled to the processor. The processor is configured to: receive a second sensing service request from a first device or base station via the transceiver, the second sensing service request including at least first information about a sensing task; receive second information about the sensing task from the first UE via the transceiver and a side link; and receive a reflected signal associated with a sensing signal based on determining that the first information and the second information are the same.

[0015] In some implementations, the first information about the sensing task includes a first ID of the sensing task, and the second information about the sensing task includes a second ID of the sensing task.

[0016] In some implementations, the processor is configured to receive second information about the sensing task by receiving a direct communication request message from a first UE via a transceiver and a side link. The direct communication request message includes a second ID of the sensing task and information about the sensing service type.

[0017] In some implementations, the processor is also configured to: determine whether the first information is the same as the second information based on the determination that the direct communication request message includes information about the type of sensing service.

[0018] In some implementations, the processor is configured to receive second information about the sensing task by receiving a broadcast or multicast communication request message from a first UE via a transceiver and a side link. The broadcast or multicast communication request message includes a second ID of the sensing task and a destination layer 2 ID associated with the sensing service type.

[0019] In some implementations, the processor is also configured to: determine whether the first information is the same as the second information based on the determination that the broadcast or multicast communication request message includes a destination layer 2 ID associated with the sensing service type.

[0020] In some implementations, the processor is also configured to obtain information about the association between the destination layer 2 ID and the sensing service type from one of the following: a first device, a second device, or an application server.

[0021] In some implementations, the processor is also configured to: determine whether the first information is the same as the second information based on the determination that the received signal strength from the first UE is higher than the second side link signal threshold.

[0022] In some embodiments, the second sensing service request further includes at least one of the following: a sensing requirement associated with a sensing task, a sensing mode associated with a sensing task, a third instruction instructing the second UE to receive a reflected signal associated with a sensing signal, a fourth instruction instructing the second UE to send sensing measurement data to the first UE via a side link, a fifth instruction instructing the second UE to send sensing measurement data to a base station, information regarding the transmission of sensing measurement data via a user plane connection between the first device and the second UE, or a second side link signal threshold, based on which the second UE determines whether to receive the reflected signal associated with the sensing signal.

[0023] Some implementations of the first device described herein may include at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to cause the first device to: receive a sensing service request from a sensing service consumer; determine, based on the sensing service request, a first UE for transmitting a sensing signal and at least one second UE for receiving a reflected signal associated with the sensing signal; and provide the sensing service request to the first UE and the at least one second UE, the sensing service request including at least first information about the sensing task.

[0024] In some implementations, the first device is configured to provide a sensing service request by sending a first sensing service request to a first UE, the first sensing service request including at least first information about the sensing task.

[0025] In some implementations, the first sensing service request further includes at least one of the following: a sensing requirement associated with a sensing task; a sensing mode associated with a sensing task; a first instruction instructing the first UE to send a sensing signal; a second instruction instructing the first UE to collect sensing measurement data associated with a sensing task from at least one second UE and send the sensing measurement data to the first device; information regarding the transmission of the sensing measurement data via the user plane connection between the first device and the first UE; or a first sidelink signal threshold, based on which the first sidelink signal threshold determines whether a candidate UE is identified as one of the at least one second UE.

[0026] In some implementations, the first device is configured to provide a sensing service request by sending a second sensing service request to at least one second UE, the second sensing service request including at least first information about the sensing task.

[0027] In some embodiments, the second sensing service request further includes at least one of the following: a sensing request associated with a sensing task; a sensing mode associated with a sensing task; a third indication instructing at least one second UE to receive a reflected signal associated with a sensing signal; a fourth indication instructing at least one second UE to send sensing measurement data to a first UE via a side link; a fifth indication instructing at least one second UE to send sensing measurement data to a base station; information regarding the transmission of sensing measurement data via a user plane connection between a first device and one of the at least one second UE; or a second side link signal threshold, based on which one of the at least one second UE determines whether to receive the reflected signal.

[0028] In some implementations, the first device is configured to provide a sensing service request by sending a sensing service request to a base station serving a first UE and at least one second UE.

[0029] In some embodiments, the sensing service request may further include at least one of the following: a sensing request associated with a sensing task, the IDs of the first UE and at least one second UE, a fourth instruction instructing at least one second UE to send sensing measurement data to the first UE via a side link, a fifth instruction instructing at least one second UE to send sensing measurement data to a base station, or information regarding the transmission of sensing measurement data via a user plane connection between the first device and at least one second UE.

[0030] In some implementations, the first device is further configured to: send a request to the second device for converting a first type ID of the first UE and at least one second UE into a second type ID of the first UE and at least one second UE, the second type ID being recognizable by the base station; and receive the second type ID from the second device.

[0031] In some implementations, the first information about the sensing task includes a first ID of the sensing task, and the second information about the sensing task includes a second ID of the sensing task.

[0032] Some implementations of the base station described herein may include a processor and a transceiver coupled to the processor. The processor is configured to: send a request to a second device via the transceiver, the request being used to convert a first type ID of a first UE and at least one second UE into a second type ID of the first UE and at least one second UE, the second type ID being recognizable by the base station; and receive the second type ID from the second device via the transceiver.

[0033] In some implementations, the processor is further configured to receive a sensing service request from the first device via the transceiver, the sensing service request including the ID of the first UE and at least one second UE of a first type.

[0034] In some implementations, the sensing service request also includes sensing requirements associated with the sensing task; and the processor is further configured to: determine, based on the sensing requirements, resources for the transmission of sensing signals via a side link, the sensing signals being associated with the sensing task; send a first sensing service request to a first UE via a transceiver, the first sensing service request including the sensing requirements and information about the resources; and send a second sensing service request to at least one second UE via a transceiver, the second sensing service request including the sensing requirements and information about the resources.

[0035] Some implementations of the method described herein may include: receiving a first sensing service request from a first device or base station at a first UE, the first sensing service request including at least first information about the sensing task; and sending second information about the sensing task via a side link.

[0036] Some implementations of the method described herein may include: receiving a second sensing service request from a first device or base station at a second UE, the second sensing service request including at least first information about a sensing task; receiving second information about the sensing task from the first UE via a side link; and receiving a reflected signal associated with a sensing signal based on determining that the first information and the second information are the same.

[0037] Some implementations of the method described herein may include: receiving a sensing service request from a sensing service consumer at a first device; determining, based on the sensing service request, a first UE for transmitting a sensing signal and at least one second UE for receiving a reflected signal associated with the sensing signal; and providing the sensing service request to the first UE and at least one second UE, the sensing service request including at least first information about the sensing task.

[0038] Some implementations of the method described herein may include: sending a request from a base station to a second device to convert a first type ID of a first UE and at least one second UE into a second type ID of the first UE and at least one second UE, the second type ID being recognizable by the base station; and receiving the second type ID from the second device.

[0039] It should be understood that the summary section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to be used to limit the scope of this disclosure. Other features of this disclosure will become apparent from the following description. Attached Figure Description

[0040] Figure 1A , Figure 1B as well as Figure 1C Examples of wireless communication systems supporting side-link-based sensing according to aspects of this disclosure are illustrated respectively;

[0041] Figures 2 to 4 Signaling diagrams of example processes supporting side-link-based sensing according to aspects of this disclosure are illustrated respectively;

[0042] Figure 5 The diagram illustrates a signaling diagram of an example sensing registration process according to aspects of this disclosure;

[0043] Figure 6 Examples of devices supporting side-link-based sensing according to some aspects of this disclosure are illustrated;

[0044] Figure 7 Examples of processors supporting side-link-based sensing according to other aspects of this disclosure are illustrated; and

[0045] Figures 8 to 11 Flowcharts illustrating methods for supporting side-link-based sensing according to other aspects of this disclosure are also shown. Detailed Implementation

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

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

[0048] References to "one implementation," "an example implementation," "an implementation," "some implementations," etc., in this disclosure indicate that the described implementation(s) may include a particular feature, structure, or characteristic, but not every implementation includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to (multiple) identical implementations. Moreover, when a particular feature, structure, or characteristic is described in conjunction with an implementation, it should be assumed that, whether explicitly described or not, the influence of such feature, structure, or characteristic on other implementations is within the knowledge of those skilled in the art.

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

[0050] The terminology used herein is for the purpose of describing a particular implementation only and is not intended to limit the example implementation. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that, when used herein, the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” specify the presence of the stated feature, element, and / or component, but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0051] The aspects of this disclosure are described in the context of wireless communication systems.

[0052] Figure 1A An example of a wireless communication system 100A supporting sidelink-based sensing according to aspects of this disclosure is illustrated. The wireless communication system 100A may include one or more network entities 102 (also referred to as network devices (NEs)), one or more terminal devices or UEs 104, a core network 106, and a packet data network 108. For example, UE 104 may include UE 104-1 and UE 104-2. Hereinafter, UE 104-1 and UE 104-2 may also be referred to as first UE 104-1 and second UE 104-2, respectively. The wireless communication system 100A may support various radio access technologies. In some implementations, the wireless communication system 100A may be a 4G network, such as an LTE network or an LTE-A Advanced network. In some other implementations, the wireless communication system 100A may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100A can be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100A can support radio access technologies beyond 5G. Additionally, the wireless communication system 100A can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0053] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100A. One or more of the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. In the following description, some implementations of this disclosure will be described by using a base station as an example of a network entity 102. Therefore, network entity 102 can be used interchangeably with base station 102.

[0054] Network entity 102 and UE 104 can communicate via communication link 110, which can be a wireless connection or a wired connection. For example, network entity 102 and UE 104 can perform wireless communication (e.g., receive signaling, send signaling) through the Uu interface.

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

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

[0057] One or more UEs 104 can be devices of different forms or with different capabilities. Examples of some UEs 104 are illustrated in Figure 1. As shown in Figure 1, a UE 104 can have the ability to communicate with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay device, integrated access and backhaul (IAB) node, or another network device). Alternatively or additionally, a UE 104 can support communication with other network entities 102 or UEs 104, which can act as relays in a wireless communication system 100A.

[0058] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a side link. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

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

[0060] In some implementations, network entity 102 can be configured as a de-aggregation architecture, which can be configured to utilize protocol stacks physically or logically distributed among two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-Real-Time RIC, a Non-Real-Time RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

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

[0062] The functional division among CU, DU, and RU can be flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU, or RU. For example, the functional division of the protocol stack can be adopted between the CU and DU, such that the CU can support one or more layers of the protocol stack, while the DU can support one or more different layers of the protocol stack. In some implementations, the CU can carry higher-level protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and these DUs or RUs can carry lower-level protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical Layer (PHY)) or L2 (e.g., Radio Link Control (RLC), Media Access Control (MAC)) functions, and each can be at least partially controlled by the CU 160.

[0063] Alternatively, or alternatively, the functional division of the protocol stack can be adopted between DU and RU, such that DU can support one or more layers of the protocol stack, while RU can support one or more different layers of the protocol stack. DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between CU and DU or between DU and RU may be within the protocol layer (e.g., some functions for the protocol layer may be performed by one of CU, DU, or RU, while other functions of the protocol layer may be performed by a different one of CU, DU, or RU).

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

[0065] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route packets or interconnections to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

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

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

[0068] One or more parameter sets can be supported in the wireless communication system 100A, and the parameter sets may include subcarrier spacing and cyclic prefix. The first parameter set (e.g., =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and the normal cyclic prefix. In some implementations, the first parameter set associated with the first subcarrier spacing (e.g., 15 kHz) is... =0) allows each subframe to utilize one time slot. The second parameter set (e.g., =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the normal cyclic prefix. The third parameter set (e.g., =2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and the normal cyclic prefix or extended cyclic prefix. The fourth parameter set (e.g., =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth parameter set (e.g., =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

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

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

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

[0072] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with the first parameter set (e.g., =0) is associated with a 15 kHz subcarrier spacing; the second parameter set (e.g., =1), which includes a 30 kHz subcarrier spacing; and a third parameter set (e.g., =2), which includes a 60 kHz subcarrier spacing. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with a third parameter set (e.g., =2) is associated with, which includes a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., =3), which includes a 120 kHz subcarrier spacing.

[0073] Figure 1B An example of a wireless communication system 100B supporting side-link-based sensing according to various aspects of this disclosure is illustrated. Specifically, Figure 1B The diagram shows... Figure 1A Network entities or network functions (NFs) in the core network 106 shown.

[0074] like Figure 1B As shown, the core network 106 may include at least Mobility Management Function (AMF) 120 and SF 122.

[0075] In some implementations, the AMF 120 can communicate with the UE 104 and the base station 102 via the N1 interface and the N2 interface, respectively.

[0076] In some implementations, the SF 122 enables sensing in the 5G network. The SF 122 can be a standalone 5GC NF or co-located with an existing 5GC NF (e.g., LMF). The SF 122 can communicate with the AMF 120 via the NS1 interface. The SF 122 may include an SF control plane (SF-C) portion and an SF user plane (SF-U) portion.

[0077] In some implementations, SF 122 can communicate with base station 102 via AMF 120. Alternatively, SF 122 can communicate directly with base station 102 via the interface between the two.

[0078] In some implementations, ISAC can be executed in wireless communication systems 100A and 100B. In ISAC, the application server, 5GC NF, or UE 104 can trigger the sensing process. SF 122 can assign the sensing task to base station 102 or UE 104.

[0079] In some implementations, six possible sensing modes can be introduced into ISAC. In some implementations, the sensing mode may include at least one of the following: • Sensing Mode #1: The base station operates as both a sensing transmitter (Tx) and a sensing receiver (Rx); • Sensing mode #2: The first base station and the second base station operate as sensing Tx and sensing Rx, respectively; • Sensing Mode #3: The UE and the base station operate as sensing Tx and sensing Rx, respectively; • Sensing mode #4: The base station and UE operate as sensing Tx and sensing Rx respectively; • Sensing Mode #5: The first UE and the second UE operate as sensing Tx and sensing Rx respectively; or • Sensing mode #6: The UE operates as both a sensing Tx and a sensing Rx.

[0080] Figure 1C An example of a wireless communication system 100C supporting side-link-based sensing according to aspects of this disclosure is illustrated. Figure 1C In the example, sensing mode #5 can be executed. For instance, the first UE 104-1 operates as a sensing Tx and transmits a sensing signal via a side link. This sensing signal is reflected by the sensing object 130. The second UE 104-2 operates as a sensing Rx and receives the reflected signal associated with the sensing signal. How to coordinate the sensing Tx and sensing Rx to perform the sensing task needs to be discussed.

[0081] In view of the foregoing, the present disclosure provides a solution supporting sidelink-based sensing. In one aspect of this solution, a first UE receives a first sensing service request from a first device or base station. The first sensing service request includes at least first information about the sensing task. Then, the first UE transmits second information about the sensing task via a sidelink. Using this solution, sidelink-based sensing can be implemented.

[0082] In the following text, the principles of this disclosure will be referred to Figures 2 to 11 Described.

[0083] Figure 2 The illustration shows a signaling diagram illustrating an example process 200 supporting sidelink-based sensing according to aspects of this disclosure. Process 200 may involve a first UE 104-1, a second UE 104-2, a base station 102, a first device, and a second device. In some implementations, the first device may perform... Figure 1B SF 122. Alternatively, the first device can perform... Figure 1BOther network functions besides SF122. In some implementations, the second device can perform... Figure 1B The AMF 120 in the middle. Alternatively, a second device can perform... Figure 1B Other network functions besides AMF 120. For discussion purposes, procedure 200 will refer to Figure 1B and 1C Described. Process 200 may involve Figure 1B Base stations 102, AMF 120, and SF 122 are included. Figure 1B or Figure 1C The first UE 104-1 and the second UE 104-2, and the sensing service consumer 140 ( Figure 1B or Figure 1C (Not shown in the image).

[0084] Typically, in process 200, SF 122 can directly assign sensing tasks to the first UE 104-1 and the second UE 104-2.

[0085] Specifically, SF 122 receives a sensing service request 205 from sensing service consumer 140. The sensing service request includes at least information about the sensing task.

[0086] In some implementations, information about the sensing task may include an identifier (ID) for the sensing task. For simplicity, the ID of the sensing task will also be referred to as the sensing task ID in the following text.

[0087] Alternatively, in some implementations, the first information about the sensing task may include the sensing transaction ID or association ID.

[0088] In some implementations, the sensing service request may further include at least one of the following: a sensing requirement associated with the sensing task, a target sensing area, or a target sensing object (such as...). Figure 1C (Sensing object 130 in the middle).

[0089] In some implementations, sensing requirements may include at least one of the following: sensing service type, resolution of the sensing service type and accuracy of the position / velocity / angle of the sensed object, refresh rate, target detection rate, false alarm rate of the target, sensing area, sensing speed range, sensing duration (e.g., sensing start time, sensing end time), reporting cycle, or delay.

[0090] In some implementations, the target sensing object can be a UE or a non-UE object. The target sensing area or the target sensing object can be included in the sensing requirements.

[0091] In some implementations, the sensing service consumer can be a UE, an application function (AF), an application server 118, or a 5GC NF (e.g., a network data analysis function (NWDAF)).

[0092] In some implementations, the sensing service type can be one of the following: intelligent transportation (e.g., high-resolution map building or intrusion detection), intelligent low posture (e.g., flight intrusion detection or flight path management), intelligent networking (e.g., channel estimation enhancement or beam management), and intelligent living (e.g., breathing monitoring, gesture or posture recognition).

[0093] Furthermore, SF 122 determines the 210 sensing mode based on the sensing service request.

[0094] In some implementations, SF 122 may have a pre-configured mapping between sensing service types and at least one sensing mode by Operations Management and Maintenance (OAM), the Public Land Mobile Network (PLMN), or the operator. Alternatively, in some implementations, the mapping between sensing service types and at least one sensing mode may be predefined. SF 122 may select a sensing mode based on the sensing service type and the mapping between the sensing service type and at least one sensing mode.

[0095] In some implementations, the selected sensing mode can be one of the sensing modes #1 to #6 described above. In the following description, some implementations will be illustrated by using sensing mode #5 as an example of the selected sensing mode.

[0096] Continue to refer to Figure 2 Based on the sensing service request, SF 122 determines that a first UE 104-1 is used to transmit a sensing signal, and at least one second UE 104-2 is used to receive a reflected signal associated with the sensing signal. In other words, SF 122 selects the first UE 104-1 as the sensing Tx, and selects at least one second UE 104-2 as at least one sensing Rx.

[0097] In some implementations, SF 122 may select a sensing Tx and at least one sensing Rx for sensing mode #5 based on the UE location and the location of the target sensing area or the target sensing object.

[0098] In some implementations, SF 122 can subscribe to UE home information from AMF 120.

[0099] In some implementations, UE home information may include information about the base station serving the UE, the cell, or the tracking area (TA) where the UE is located. For example, UE home information may include one of the following: gNB ID, cell ID, tracking area identifier (TAI), or tracking area code (TAC).

[0100] In some implementations, the AMF 120 can provide UE home information to the SF 122 after a handover or Tracking Area Update (TAU). Alternatively, the sensed UE (such as the first UE 104-1 or the second UE 104-2) can also provide UE home information to the SF 122. Based on the UE home information, the SF 122 can determine the UE's serving base station, TAI, or TAC.

[0101] In some implementations, SF 122 may subscribe to a location service from AMF 120 or LMF (not shown) to obtain the UE's location. The UE's location may be geographic coordinates, such as X / Y / Z coordinates. In this way, SF 122 may select a first sensing UE (such as first UE 104-1) as a sensing Tx based on its sensing capabilities (e.g., Tx capability, Rx capability, etc.), UE location, and target sensing area or target sensing object. Furthermore, SF 122 may also select at least one second sensing UE as at least one candidate sensing Rx based on the distance between the sensing Tx and the corresponding second sensing UE.

[0102] In some implementations, SF 122 can acquire the sensing capabilities of the sensing UE via a sensing registration process. See below for further details. Figure 5 describe.

[0103] Then, SF 122 sends a 220 First Sensing Service Request to the first UE 104-1. The First Sensing Service Request may include at least first information about the sensing task. For example, the First Sensing Service Request may include the first ID of the sensing task. For simplicity, the first ID of the sensing task will also be referred to as the First Sensing Task ID below.

[0104] In some implementations, the first sensing service request may further include at least one of the following: a sensing requirement associated with the sensing task, a sensing mode associated with the sensing task, or a first indication instructing the first UE 104-1 to send a sensing signal. For simplicity, the first indication is also referred to below as a sensing Tx indication.

[0105] Alternatively or additionally, in some implementations, the first sensing service request may also include a second instruction indicating that the first UE 104-1 collects sensing measurement data associated with the sensing task from at least one second UE 104-2 and sends the sensing measurement data to SF 122. For simplicity, the second instruction is also referred to below as a reporting instruction.

[0106] Alternatively or additionally, in some implementations, the first sensing service request may also include information regarding the transmission of sensing measurement data via the user plane (UP) connection between SF 122 and the first UE 104-1. For simplicity, in the following text, the information regarding the transmission of sensing measurement data via the UP connection between SF 122 and the first UE 104-1 is also referred to as first UP report information.

[0107] In some implementations, the first UP report information may include an UP report indicator and a report address (e.g., the IP address of the SF122 or the SF-U portion used for UP reporting). Alternatively, the first UP report information may not include an UP report indicator. The SF 122 may also provide a list of at least one candidate sensing Rx IDs, which includes at least one ID of the at least one candidate sensing Rx. The ID of the sensing Rx may be an application layer ID or other type of UE ID.

[0108] Alternatively or additionally, in some implementations, the first sensing service request may also include a first sidelink signal threshold. Based on the first sidelink signal threshold, the first UE 104-1 (i.e., the sensing Tx UE) may determine that the candidate UE is one of at least one second UE 104-2 (i.e., the sensing Rx UE). For example, if the received signal strength from the candidate UE is higher than the first sidelink signal threshold, the first UE 104-1 may determine that the candidate UE is the second UE 104-2.

[0109] In some implementations, when within NG-RAN coverage, the first UE 104-1 can autonomously select resources from at least one resource pool provided by broadcast system information or dedicated signaling for the transmission of sense signals via sidelinks. For simplicity, the resources used for the transmission of sense signals via sidelinks will also be referred to as sidelink sensing resources in the following text.

[0110] Alternatively, in some implementations, the first UE 104-1 may request sidelink sensing resources from the base station 102 serving the first UE 104-1. For example, optionally, the first UE 104-1 may send a 225 sidelink sensing resource request message to the base station 102.

[0111] In some implementations, the sidelink sensing resource request message can be a novel type of dedicated radio resource control (RRC) message. Alternatively, the sidelink sensing resource request message can be an existing RRC message with new parameters.

[0112] In some implementations, the sidelink sensing resource request message may include a first sensing task ID and sensing requirements. In some implementations, base station 102 may determine the sidelink sensing resources based on the sensing requirements.

[0113] Alternatively or otherwise, in some implementations, the sidelink sensing resource request message may include the required sidelink sensing resources without requiring sensing. The required sidelink sensing resources may be the required number of physical resource blocks (PRBs), frames, or time slots.

[0114] Base station 102 sends a 230 sidelink sensing resource response message to the first UE 104-1. The sidelink sensing resource response message may include a first sensing task ID and information about sidelink sensing resources. For simplicity, the information about sidelink sensing resources will also be referred to as sidelink sensing resource information below.

[0115] In some implementations, sidelink sensing resource information may include time / frequency / spatial information and other information related to the sensed signal. For example, sidelink sensing resource information may include at least one of the following: frame index, subframe index, time slot index, sub-time slot index, PRB index, synchronization signal block (SSB) index, beam index, bandwidth portion (BWP) ID, transmit power of the sensed signal, or transmit signal sequence.

[0116] In some implementations, if the first UE 104-1 autonomously selects a sidelink sensing resource from the resource pool, actions 225 and 230 will not be executed.

[0117] Therefore, the first UE 104-1 can send a 235 sensing service response message to SF 122 to notify SF 122 whether it accepts the sensing task.

[0118] In some implementations, the sensing service response message may include sidelink sensing resource information.

[0119] Additionally, SF 122 sends a second sensing service request (240) to at least one second UE 104-2. This second sensing service request may include at least first information about the sensing task. For example, the second sensing service request may include a first ID of the sensing task.

[0120] In some implementations, the second sensing service request may further include at least one of the following: a sensing requirement associated with the sensing task, a sensing mode associated with the sensing task, or a third indication instructing at least one second UE 104-2 to receive a reflected signal associated with the sensing signal. For simplicity, the third indication will also be referred to below as a sensing Rx indication.

[0121] Alternatively or additionally, in some implementations, the second sensing service request may also include a fourth instruction instructing at least one second UE 104-2 to send sensing measurement data to the first UE 104-1 via a side link. For simplicity, the fourth instruction will also be referred to below as a report of the Tx instruction.

[0122] Alternatively or additionally, in some implementations, the second sensing service request may also include a fifth instruction instructing at least one second UE 104-2 to send sensing measurement data to base station 102. For simplicity, the fifth instruction is also referred to below as a report of an instruction to the RAN node.

[0123] Alternatively or additionally, in some implementations, the second sensing service request may also include information regarding the transmission of sensing measurement data via the UP connection between SF 122 and at least one of the second UEs 104-2. For simplicity, the information regarding the transmission of sensing measurement data via the UP connection between SF 122 and at least one of the second UEs 104-2 is also referred to hereinafter as second UP report information.

[0124] In some implementations, the second UP report information may include a UP report indicator and a report address (e.g., the IP address of SF122 or the SF-U portion used for UP reporting). If the second UP report information is provided, it indicates that the second UE 104-2 will report to SF 122 itself via the UP connection between them.

[0125] Alternatively or additionally, in some implementations, the second sensing service request may also include a second sidelink signal threshold. Based on the second sidelink signal threshold, the second UE 104-2 can determine whether it receives a reflected signal associated with the sensing signal. In other words, based on the second sidelink signal threshold, the second UE 104-2, acting as a candidate sensing Rx, can determine whether it is capable of serving as a sensing Rx. For example, if the received signal strength from the first UE 104-1 (i.e., sensing Tx) is higher than the second sidelink signal threshold, the second UE 104-2 can determine that it is capable of serving as a sensing Rx.

[0126] In some implementations, if the sensing service response message sent from the first UE 104-1 to the SF 122 includes sidelink sensing resource information, the SF 122 may also provide the sidelink sensing resource information to the second UE 104-2 in the second sensing service request.

[0127] In some implementations, after receiving the second sensing service request, the second UE 104-2 can send a sensing service response message to SF 122 to notify SF 122 whether it accepts the sensing task (if it has not already accepted the request). Figure 2 (As shown in the image).

[0128] Then, the sensing Tx / Rx association process 250 via the side link will be executed.

[0129] During the sensing Tx / Rx association process 250, the first UE 104-1 sends 252 second information about the sensing task to the second UE 104-2 via a side link.

[0130] In some implementations, the second information about the sensing task may include a second ID of the sensing task. For simplicity, the second ID of the sensing task will also be referred to as the second sensing task ID in the following text.

[0131] Alternatively, in some implementations, the second information about the sensing task may include the sensing transaction ID or association ID.

[0132] In some implementations, the first UE 104-1 may send second information about the sensing task via a sidelink in unicast mode. In such an implementation, the first UE 104-1 may send a direct communication request message for the unicast link establishment process. This direct communication request message may include a second ID of the sensing task and information about the sensing service type. For example, the sensing service may be defined as a dedicated or novel vehicle-to-everything (V2X) service type. Alternatively, different sensing service types (e.g., intelligent transportation, intelligent low-pose, intelligent networks, and intelligent living) may be defined as dedicated or novel V2X service types respectively. The direct communication request message may include fields of V2X service information. These fields may include information about the sensing service (or sensing service type) requested for the Layer 2 link establishment. Optionally, the direct communication request message may also include a sensing requirement.

[0133] Alternatively, in some implementations, the first UE 104-1 may transmit second information about the sensing task via a sidelink in broadcast or multicast mode. In such an implementation, the first UE 104-1 may transmit a broadcast or multicast communication request message via the sidelink. The broadcast or multicast communication request message may include a second ID of the sensing task and a destination Layer 2 ID associated with a sensing service (or sensing service type). For example, a sensing service may be associated with a destination Layer 2 ID. Alternatively, a specific sensing service type may be associated with a destination Layer 2 ID. Optionally, the broadcast or multicast communication request message may also include a sensing requirement.

[0134] In such an implementation, the sensing service (or sensing service type) can be defined as a dedicated or new V2X service type. The first UE 104-1 can obtain information about the association or mapping between the destination layer 2 ID and the sensing service (or sensing service type) from one of the following: SF 122, Policy Control Function (PCF), V2X application server, or sensing application server ( Figure 1A , 1B (or not shown in 1C). Therefore, the first user equipment 104-1 can determine the destination layer 2 ID based on the sensing service (or sensing service type) and the association between the destination layer 2 ID and the sensing service (or sensing service type).

[0135] After receiving the second information about the sensing task, the second UE 104-2 determines whether the first information about the sensing task received by 254 from SF 122 is the same as the second information about the sensing task. For example, the second UE 104-2 may determine whether the first sensing task ID is the same as the second sensing task ID.

[0136] If the first information about the sensing task is the same as the second information about the sensing task, then the second UE 104-2 receives 265 the reflected signal associated with the sensing signal.

[0137] In some implementations, the second UE 104-2 can receive the reflected signal based on sidelink sensing resource information received from SF 122 or the first UE 104-1. For example, the second UE 104-2 can receive the reflected signal by monitoring sidelink sensing resources.

[0138] In some implementations, the second UE 104-2 may receive second information about the sensing task from the first UE 104-1 via a sidelink in unicast mode. In these implementations, the second UE 104-2 may receive a direct communication request message for the unicast link establishment process. This direct communication request message may include a second ID of the sensing task and information about the sensing service (or sensing service type).

[0139] In such an implementation, the second UE 104-2 may first determine whether the direct communication request message includes information about the sensing service (or sensing service type). If the direct communication request message includes information about the sensing service (or sensing service type), the second UE 104-2 may further determine whether the first information is the same as the second information.

[0140] Alternatively, in some implementations, the second UE 104-2 may receive second information about the sensing task transmitted by the first UE 104-1 via a sidelink in broadcast or multicast mode. In such an implementation, the second UE 104-2 may receive a broadcast or multicast communication request message from the first UE 104-1. This broadcast or multicast communication request message may include a second ID of the sensing task and a destination layer 2 ID associated with the sensing service (or sensing service type).

[0141] In such an implementation, the second UE 104-2 may first determine whether the broadcast or multicast communication request message includes a destination layer 2 ID associated with the sensing service (or sensing service type). If the broadcast or multicast communication request message includes a destination layer 2 ID associated with the sensing service (or sensing service type), the second UE 104-2 may also determine whether the first information is the same as the second information.

[0142] In such an implementation, the sensing service (or sensing service type) can be defined as a dedicated or new V2X service type. The second UE 104-2 can obtain information about the association or mapping between the destination layer 2 ID and the sensing service (or sensing service type) from one of the following: SF 122, PCF, V2X application server, or sensing application server (not in...). Figure 1A , 1B (or as shown in 1C).

[0143] Alternatively, in some implementations, the second UE 104-2 may first determine whether the received signal strength from the first UE 104-1 is higher than a second sidelink signal threshold. If the received signal strength from the first UE 104-1 is higher than the second sidelink signal threshold, the second UE 104-2 may further determine whether the first information is the same as the second information. The second sidelink signal threshold may be pre-configured or received from the sidelink SF 122.

[0144] Alternatively, in some implementations, the second UE 104-2 may first determine whether the sensing requirement provided by the first UE 104-1 via the side link is the same as the sensing requirement provided by the side link SF 122 (e.g., via action 240). If the sensing requirement provided by the first UE 104-1 via the side link is the same as the sensing requirement provided by the side link SF 122, the second UE 104-2 may further determine whether the first information is the same as the second information.

[0145] In some implementations, optionally, if the first information is the same as the second information, the second UE 104-2 can send a response message 256 to the first UE 104-1 using the source layer 2 ID assigned by the second UE 104-2. By doing so, the sensing Tx / Rx association is completed.

[0146] Then, the second UE 104-2 can receive the reflected signal associated with the sensing signal sent by the first UE 104-1. If the first sidelink signal threshold is provided by SF 122, the first UE 104-1 can also determine whether the received signal strength from the second UE 104-2 is higher than the first sidelink signal threshold. If the received signal strength from the second UE 104-2 is higher than the first sidelink signal threshold, the first UE 104-1 can mark the second UE 104-2 as a sensing Rx UE. If the received signal strength from the second UE 104-2 is not higher than the first sidelink signal threshold, the first UE 104-1 can also notify the candidate sensing Rx UE (e.g., the second UE 104-2) to stop monitoring and release the sidelink connection between them. If the ID of the candidate sensing Rx is provided by SF 122, the first UE 104-1 can also determine whether the application layer ID of the candidate sensing Rx matches the application layer ID provided by SF 122.

[0147] In some implementations, optionally, the first UE 104-1 may provide sidelink sensing resource information and a second sensing task ID to the second UE 104-2 via a sidelink. For example, if a unicast link between the first UE 104-1 and the second UE 104-2 is established via sensing Tx / Rx association procedure 250, then the first UE 104-1 provides the sidelink sensing resource information and the second sensing task ID via that unicast link. Otherwise, the first UE 104-1 broadcasts or multicasts the sidelink sensing resource information and the second sensing task ID instead. In some implementations, if the first UE 104-1 does not provide sidelink sensing resource information to SF 122 in action 235, then action 260 may be executed.

[0148] The following procedure is an example of a scenario where the second UE 104-2 sends a sensing measurement report to SF 122.

[0149] For example, the second UE 104-2 can generate 270 sensing measurement data based on the reflected signal.

[0150] If the second UP report information is provided to the second UE 104-2, the second UE 104-2 will trigger the 275 sensing user plane establishment process.

[0151] After generating the sensing measurement data, the second UE 104-2 can provide the SF 122 with a 280 sensing measurement data report.

[0152] After receiving the sensing measurement data report, SF 122 can calculate the 285 sensing results based on the sensing measurement report.

[0153] Then, SF 122 can open the sensing results 290 to the sensing service consumer 140.

[0154] Using process 200, the sensing Tx can coordinate with at least one sensing Rx to perform a sensing task.

[0155] Figure 3 The illustration shows a signaling diagram of an example process 300 supporting sidelink-based sensing according to aspects of this disclosure. Process 300 may involve a first UE 104-1, a second UE 104-2, a base station 102, a first device, and a second device. In some implementations, the first device may perform... Figure 1B SF 122. Alternatively, the first device can perform... Figure 1B Other network functions besides SF122. In some implementations, the second device can perform... Figure 1B The AMF 120 in the middle. Alternatively, a second device can perform... Figure 1B Other network functions besides AMF 120. For the purposes of discussion, procedure 300 will refer to Figure 1B and 1C Described. Process 300 may involve Figure 1B Base stations 102, AMF 120, and SF 122 are included. Figure 1B Or the first UE 104-1 and the second UE 104-2 in 1C, and the sensing service consumer 140 (not in Figure 1B (or as shown in 1C).

[0156] Typically, in process 300, SF 122 can assign sensing tasks to the first UE 104-1 and the second UE 104-2 via base station 102. SF 122 can provide base station 102 with the IDs of sensing Tx and at least one candidate sensing Rx, as well as information about the sensing task. It is assumed that SF 122 knows that sensing Tx and at least one candidate sensing Rx are within the service area of ​​base station 102. Base station 102 can determine the resources used for transmitting the sensing signal via a sidelink and provide information about the resources to sensing Tx and at least one sensing Rx, respectively.

[0157] Base station 102 can identify the UE based on the AMF / RAN UE NGAP ID provided by AMF 120, as will be discussed later. Figure 5 As described. However, base station 102 cannot directly identify the UE via the UE ID provided by SF 122. The UE ID provided by SF 122 can be one of the following: Subscriber Permanent Identifier (SUPI), Universal Public Subscriber Identifier (GPSI), or 5G Globally Unique Temporary UE Identifier (5G-GUTI). The UE will report its ID (such as the 5G System Architecture Evolution Temporary Mobile Station Identifier (5G-S-TMSI)) to base station 102 in an uplink (UL) RRC message. Therefore, base station 102 has a mapping between 5G-S-TMSI and the UE's Cell Radio Network Temporary Identifier (C-RNTI), where the C-RNTI is the UE ID used by base station 102 via the air interface. Therefore, if SF 122 provides 5G-S-TMSI, base station 102 can identify the UE. If the UE ID provided by SF 122 is not known to base station 102, such as SUPI, GPSI, 5G-GUTI, etc., then a UE ID translation for base station 102 is required. In process 300, the UE ID conversion process 320 between SF 122 and AMF 120 can be executed.

[0158] Specifically, during the UE ID conversion process 320, SF 122 sends a 322 request to AMF 120, which is used to convert the ID of the first UE 104-1 and at least one second UE 104-2 of type 1 to the ID of the first UE 104-1 and at least one second UE 104-2 of type 2. The ID of type 2 can be identified by base station 102.

[0159] In some implementations, the first type of ID for the first UE 104-1 and at least one second UE 104-2 can be the ID of the first UE 104-1 and at least one second UE 104-2, which are used via the service interface between NFs in the core network 106. For example, the first type of ID can be the SUPI, GPSI, or 5G-GUTI of the first UE 104-1 and at least one second UE 104-2.

[0160] Upon receiving the request, AMF 120 converts the first type ID of the first UE 104-1 and at least one second UE 104-2 into the second type ID of the first UE 104-1 and at least one second UE 104-2.

[0161] In some implementations, the second type of ID for the first UE 104-1 and at least one second UE 104-2 can be the ID of the first UE 104-1 and at least one second UE 104-2, which is used via the point-to-point interface between the base station 102 and the NF in the core network 106. The second type of ID can be identified by the base station 102. For example, the second type of ID can be the AMF / RAN UE NGAP ID of the first UE 104-1 and at least one second UE 104-2.

[0162] Then, AMF 120 sends 324 IDs of the first UE 104-1 and at least one second UE 104-2 of the second type to SF 122.

[0163] SF 122 sends a 330 sensing service request to base station 102. The sensing service request includes at least information about the sensing task.

[0164] In some implementations, the sensing task information may include a sensing task ID. Alternatively, the information about the sensing task may include a sensing transaction ID or an association ID.

[0165] Alternatively or additionally, in some implementations, the sensing service request may further include a second type of ID for the first UE 104-1 and at least one second UE 104-2. Upon receiving the sensing service request including the second type of ID, the base station 102 can convert the second type of ID into an ID for the first UE 104-1 and at least one second UE 104-2 used via the air interface. For example, the base station 102 can convert the second type of ID into a C-RNTI for the first UE 104-1 and at least one second UE 104-2.

[0166] Alternatively or otherwise, in some implementations, the sensing service request may also include sensing requirements associated with the sensing task.

[0167] Alternatively or additionally, in some implementations, the sensing service request may also include at least one of the following: a fourth instruction instructing at least one second UE 104-2 to send sensing measurement data to the first UE 104-1 via a side link; a fifth instruction instructing at least one second UE 104-2 to send sensing measurement data to the base station 102; or information regarding the transmission of sensing measurement data via a user plane connection between the side link 122 and at least one second UE 104-2.

[0168] After receiving a sensing service request from SF 122, base station 102 can determine the resources for transmitting a sensing signal via a side link based on the sensing requirement. This sensing signal is associated with a sensing task. Alternatively, base station 102 can determine the resources for transmitting the sensing signal via a side link based on a sensing task ID. For simplicity, the resources for transmitting the sensing signal via a side link will also be referred to as side link sensing resources below.

[0169] Then, base station 102 sends a first sensing service request 340 to the sensing Tx (such as the first UE 104-1) identified by the second type of ID of the sensing Tx.

[0170] In some implementations, the first sensing service request may include the first sensing task ID.

[0171] In some implementations, the first sensing service request may also include information about sidelink sensing resources. For the sake of brevity, this information about sidelink sensing resources will also be referred to as sidelink sensing resource information below.

[0172] In some implementations, the first sensing service request may also include at least one of the following: a sensing requirement associated with the sensing task, a sensing Tx indication, or a first sidelink signal threshold.

[0173] Additionally, base station 102 sends a second sensing service request 345 to at least one sensing Rx (such as the second UE104-2) identified by a second type of ID of the sensing Rx.

[0174] In some implementations, the second sensing service request may also include sidelink sensing resource information.

[0175] In some implementations, the second sensing service request may also include at least one of the following: a sensing requirement associated with the sensing task, a sensing Rx indication, a second sidelink signal threshold, a reporting indication to Tx, a reporting indication to the RAN node, or a second UP reporting information.

[0176] Actions 205, 210, 215, 252, 254, 256, 260, 265, 270, 275, 280, 285, and 290 in process 300 are similar to those in process 200. For the sake of brevity, the details of these actions have been omitted.

[0177] Figure 4 The illustration shows a signaling diagram illustrating an example process 400 supporting sidelink-based sensing according to aspects of this disclosure. Process 400 may involve a first UE 104-1, a second UE 104-2, a base station 102, a first device, and a second device. In some implementations, the first device may perform... Figure 1B SF 122. Alternatively, the first device can perform... Figure 1B Other network functions besides SF122. In some implementations, the second device can perform... Figure 1B The AMF 120 in the middle. Alternatively, a second device can perform... Figure 1B Other network functions besides AMF 120. For discussion purposes, procedure 400 will refer to Figure 1B and Figure 1C To describe. Process 400 may involve Figure 1B Base stations 102, AMF 120, and SF 122 are included. Figure 1B or Figure 1C The first UE 104-1 and the second UE 104-2, and the sensing service consumer 140 (not in Figure 1B or Figure 1C (As shown in the image).

[0178] Typically, similar to process 300, in process 400, SF 122 can assign sensing tasks to the first UE 104-1 and the second UE 104-2 via base station 102.

[0179] The main difference between process 400 and process 300 is that UE ID conversion process 430 is performed between base station 102 and AMF 120.

[0180] Specifically, SF 122 sends a 420 sensing service request to base station 102. This sensing service request includes at least information about the sensing task.

[0181] In some implementations, information about the sensing task may include a sensing task ID. Alternatively, information about the sensing task may include a sensing transaction ID or an association ID.

[0182] Alternatively or otherwise, in some implementations, the sensing service request may also include the ID of a first type of first UE 104-1 and at least one second UE 104-2.

[0183] Alternatively or otherwise, in some implementations, the sensing service request may also include sensing requirements associated with the sensing task.

[0184] Alternatively or additionally, in some implementations, the sensing service request may also include at least one of the following: a fourth instruction instructing at least one second UE 104-2 to send sensing measurement data to the first UE 104-1 via a side link; a fifth instruction instructing at least one second UE 104-2 to send sensing measurement data to the base station 102; or information regarding the transmission of sensing measurement data via a user plane connection between the side link 122 and at least one second UE 104-2.

[0185] After receiving a sensing service request from SF 122, base station 102 can determine 425 the resources for transmitting the sensing signal via the side link based on the sensing requirement. This sensing signal is associated with a sensing task. Alternatively, base station 102 can determine the resources for transmitting the sensing signal via the side link based on the sensing task ID. For simplicity, the resources for transmitting the sensing signal via the side link will also be referred to as side link sensing resources below.

[0186] During the UE ID conversion process 430, base station 102 sends a 432 request to AMF 120, which is used to convert the ID of the first UE 104-1 and at least one second UE 104-2 of type 1 to the ID of the first UE 104-1 and at least one second UE 104-2 of type 2. The ID of type 2 can be identified by base station 102.

[0187] In some implementations, the first type of ID for the first UE 104-1 and at least one second UE 104-2 can be the ID of the first UE 104-1 and at least one second UE 104-2, which is used via the service interface between NFs in the core network 106. For example, the first type of ID can be the SUPI, GPSI, or 5G-GUTI of the first UE 104-1 and at least one second UE 104-2.

[0188] Upon receiving the request, AMF 120 converts the first type ID of the first UE 104-1 and at least one second UE 104-2 into the second type ID of the first UE 104-1 and at least one second UE 104-2.

[0189] In some implementations, the second type of ID for the first UE 104-1 and at least one second UE 104-2 can be the ID of the first UE 104-1 and at least one second UE 104-2, which is used via the point-to-point interface between the base station 102 and the NF in the core network 106. The second type of ID can be identified by the base station 102. For example, the second type of ID can be the AMF / RAN UE NGAP ID of the first UE 104-1 and at least one second UE 104-2.

[0190] Then, AMF 120 sends 434 IDs of the first UE 104-1 and at least one second UE 104-2 of the second type to base station 102.

[0191] Actions 205, 210, 215, 252, 254, 256, 260, 265, 270, 275, 280, 285, and 290 in process 300 are similar to those in process 200. Actions 340 and 345 in process 400 are similar to those in process 300. For the sake of brevity, details of these actions have been omitted.

[0192] In processes 300 and 400, the sensing Tx and the candidate sensing Rx may not be served by the same base station. For example, the sensing Tx is served by base station 102, and the candidate sensing Rx is served by a second base station different from base station 102. SF 122 can send the sensing task ID, sensing request, candidate sensing Rx ID, Tx reporting indicator, RAN node reporting indicator, and UP reporting information to base station 102.

[0193] Furthermore, in procedures 300 and 400, it is assumed that SF 122 may need to provide the ID of the serving RAN node (e.g., NG-RAN#2) for sensing Rx to the serving RAN node (e.g., NG-RAN#1), as in actions 330 or 420. NG-RAN#1 can then send sensing task ID #1 and sidelink resource information to NG-RAN#2 via the Xn interface. NG-RAN#2 will then forward the sidelink resource information to the sensing Rx, which is associated with the same sensing task ID as in action 345. Alternatively, if the sidelink sensing resource information is provided via a sidelink, no additional steps are required.

[0194] As described above, SF 122 can acquire the sensing capabilities of the sensing UE via a sensing registration process. This will refer to... Figure 5 To describe.

[0195] Figure 5 The illustration shows a signaling diagram of an example sensing registration process 500 according to aspects of this disclosure. Process 500 may involve... Figure 1BThe UE 104 (such as the first UE 104-1 or the second UE 104-2), base station 102, AMF 120 and SF 122.

[0196] In procedure 500, it is assumed that after UE 104 (such as first UE 104-1 or second UE 104-2) performs registration with AMF 120, UE 104 performs sensing registration with SF 122 via AMF 120. SF 122 may be a standalone NF or co-located with LMF (not shown in the figure).

[0197] UE 104 sends a 510 UL NAS message to AMF 120. This UL NAS message includes UE 104's ID (also referred to as UE ID for simplicity) and a sensing registration request message. The UE ID can be SUPI, GPSI, 5G-GUTI, or 5G-S-TMSI. Here, SUPI is used as the UE ID as an example.

[0198] In some implementations, UE 104 may include sensing capability information in the sensing registration request message.

[0199] In some implementations, the sensing registration request message may include at least one of the following: supported sensing modes, supported sensing accuracy, confidence level, sensing resolution, false alarm probability, missed detection probability, refresh rate, maximum sensing service latency, user plane connectivity support indicator, supported sensing modes, user plane connectivity support indicator (or CP / UP support indicator), Tx / Rx support indicator (or supported sensing modes), or non-3GPP sensing support indicator.

[0200] In some implementations, the Tx / Rx support indicator indicates whether the UE 104 can function as a sensing Tx, a sensing Rx, or both sensing Tx and sensing Rx.

[0201] In some implementations, the CP / UP support indicator indicates whether UE 104 supports CP-based sensing measurement reporting, UP-based sensing measurement reporting, or both. The UE ID can also be included in the sensing registration request message.

[0202] UE 104 sends a UL RRC message to base station 102, which includes a ULNAS message as a payload container. Base station 102 identifies the UL NAS message based on the payload container type and forwards the UL NAS message to AMF 120 using the RAN UE NGAPID and / or AMF UE NGAP ID (which is used by base station 102 or AMF 120 to identify UE 104 via the NG interface). Base station 102 has a mapping between the RAN / AMF UE NGAP ID and the C-RNTI (which is used by base station 102 to identify UE 104 via the air interface). AMF 120 has a mapping between the RAN / AMF UE NGAP ID and the UE ID (e.g., SUPI). It is assumed that a new payload container type (e.g., a sensing message container) is defined for the UL NAS message.

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

[0204] AMF 120 sends a 530 UE ID and a sensing registration request message to the selected SF (such as SF 122). In this way, SF 122 can identify the sensing UEs located within its service area. SF 122 obtains the UE ID (e.g., SUPI) from the sensing registration request message or from AMF 120. When SF 122 receives a sensing task, it can select a suitable sensing UE based on the sensing capability information provided by the UE during the sensing registration process.

[0205] SF 122 sends a 540 UE ID and sensing registration response message to AMF 120.

[0206] AMF 120 forwards the 550 Sensing Registration Response Message to UE 104 based on the UE ID. That is, AMF 120 converts the UE ID to an AMF / RAN UE NGAP ID. AMF 120 sends the Sensing Registration Response Message and the AMF / RAN UE NGAP ID to base station 102 serving UE 104. Base station 102 then converts the AMF / RAN UE NGAP ID to a C-RNTI. Finally, base station 102 forwards the Sensing Registration Response Message to UE 104 based on the C-RNTI.

[0207] Figure 6 An example of a device 600 supporting sidelink-based sensing according to aspects of this disclosure is illustrated. Device 600 may be an example of network entity 102, user equipment 104, or a first device as described herein. Device 600 may support wireless communication with one or more network entities 102, user equipment 104, or any combination thereof. Device 600 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 602, memory 604, transceiver 606, and (optionally) I / O controller 608. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0208] Processor 602, memory 604, transceiver 606, or various combinations thereof or components thereof may be examples of parts for performing aspects of the present disclosure as described herein. For example, processor 602, memory 604, transceiver 606, or various combinations thereof or components thereof may support methods for performing one or more operations described herein.

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

[0210] For example, processor 602 may support wireless communication at device 600 according to examples disclosed herein. Processor 602 may be configured to operate to support components for performing: receiving a first sensing service request from a first device or base station at a first UE, the first sensing service request including at least first information about a sensing task; and transmitting second information about the sensing task via a side link.

[0211] Alternatively, the processor 602 may be configured to support components for performing the following: receiving a second sensing service request from a first device or base station at a second UE, the second sensing service request including at least first information about a sensing task; receiving second information about the sensing task from the first UE via a side link; and receiving a reflected signal associated with a sensing signal based on determining that the first information and the second information are the same.

[0212] Alternatively, the processor 602 may be configured to support components for performing the following: receiving a sensing service request from a sensing service consumer at a first device; determining, based on the sensing service request, a first UE for transmitting a sensing signal and at least one second UE for receiving a reflected signal associated with the sensing signal; and providing the sensing service request to the first UE and at least one second UE, the sensing service request including at least first information about the sensing task.

[0213] Alternatively, the processor 602 may be configured to support components for performing the following: sending a request from the base station to the second device for converting a first type ID of the first UE and at least one second UE into a second type ID of the first UE and at least one second UE, the second type ID being recognizable by the base station; and receiving the second type ID from the second device.

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

[0215] Memory 604 may include random access memory (RAM) and read-only memory (ROM). Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 602, cause device 600 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, this code may not be directly executable by processor 602, but may cause a computer (e.g., at compile and execution time) to perform the functions described herein. In some implementations, in addition to this, memory 604 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0216] I / O controller 608 can manage input and output signals for device 600. I / O controller 608 can also manage peripherals not integrated into device M02. In some implementations, I / O controller 608 can represent a physical connection or port to an external peripheral. In some implementations, I / O controller 608 can utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 608 can be implemented as part of a processor (such as processor 606). In some implementations, a user can interact with device 600 via I / O controller 608 or via hardware components controlled by I / O controller 608.

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

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

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

[0220] Figure 7 An example of a processor 700 supporting side-link-based sensing according to aspects of this disclosure is illustrated. The processor 700 may be an example of a processor configured to perform various operations according to the examples described herein. The processor 700 may include a controller 702 configured to perform various operations according to the examples described herein. The processor 700 may optionally include at least one memory 704, such as an L1 / L2 / L3 cache. Additionally or alternatively, the processor 700 may optionally include one or more arithmetic logic units (ALUs) 700. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0221] Processor 700 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to or included in the processor chipset (e.g., processor 700)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

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

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

[0224] Memory 704 may include one or more caches (e.g., memory native to processor 700 or included in processor 700) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 704 may be located inside or on the processor chipset (e.g., native to processor 700). In some other implementations, memory 704 may be located outside the processor chipset (e.g., remote from processor 700).

[0225] Memory 704 may store computer-readable, computer-executable code, including instructions that, when executed by processor 700, cause processor 700 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 702 and / or processor 700 may be configured to execute computer-readable instructions stored in memory 704 to cause processor 700 to perform various functions. For example, processor 700 and / or controller 702 may be coupled to or coupled to memory 704, and processor 700, controller 702, and memory 704 may be configured to perform the various functions described herein. In some examples, processor 700 may include multiple processors, and memory 704 may include multiple memories. One or more processors may be coupled to one or more memories, which may be configured individually or collectively to perform the various functions described herein.

[0226] One or more ALU 700s can be configured to support various operations as described in the examples herein. In some implementations, one or more ALU 700s may be located inside or on a processor chipset (e.g., processor 700). In some other implementations, one or more ALU 700s may be located outside the processor chipset (e.g., processor 700). One or more ALU 700s can perform one or more computations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 700s can receive input operands and opcodes, which determine the operation to be performed. One or more ALU 700s can be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively, one or more ALU700s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU700s to handle conditional operations, comparisons, and bitwise operations.

[0227] Processor 700 may support wireless communication according to examples disclosed herein. Processor 700 may be configured or operable to support components for performing: receiving a first sensing service request from a first device or base station at a first UE, the first sensing service request including at least first information about a sensing task; and transmitting second information about the sensing task via a side link.

[0228] Alternatively, the processor 700 may be configured to support components for performing the following: receiving a second sensing service request from a first device or base station at a second UE, the second sensing service request including at least first information about a sensing task; receiving second information about the sensing task from the first UE via a side link; and receiving a reflected signal associated with a sensing signal based on determining that the first information and the second information are the same.

[0229] Alternatively, the processor 700 may be configured to support components for performing the following: receiving a sensing service request from a sensing service consumer at a first device; determining, based on the sensing service request, a first UE for transmitting a sensing signal and at least one second UE for receiving a reflected signal associated with the sensing signal; and providing the sensing service request to the first UE and at least one second UE, the sensing service request including at least first information about the sensing task.

[0230] Alternatively, the processor 700 may be configured to support components for performing the following: sending a request from the base station to the second device for converting a first type ID of the first UE and at least one second UE into a second type ID of the first UE and at least one second UE, the second type ID being recognizable by the base station; and receiving the second type ID from the second device.

[0231] Figure 8 A flowchart illustrating a method 800 supporting sidelink-based sensing according to aspects of this disclosure is shown. Operation of method 800 can be implemented by a device or components thereof as described herein. For example, operation of method 800 can be performed by a first UE 104-1 as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the function. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the function.

[0232] At 810, the method may include: receiving a first sensing service request from a first device or base station at a first UE, the first sensing service request including at least first information about a sensing task. Operation of 810 may be performed according to examples as described herein. In some implementations, aspects of operation of 810 may be as described in references... Figure 1A , 1BOr the device described in 1C can be used.

[0233] At point 820, the method may include transmitting second information about the sensing task via a side link. The operation of point 820 can be performed according to examples as described herein. In some implementations, aspects of the operation of point 820 may be as described in the references... Figure 1A , 1B Or the device described in 1C can be used.

[0234] Figure 9 A flowchart illustrating a method 900 supporting side-link-based sensing according to this disclosure is shown. Operation of method 900 can be implemented by a device or components thereof as described herein. For example, operation of method 900 can be performed by a second UE 104-1 as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the function. Alternatively, the device can use dedicated hardware to perform aspects of the function.

[0235] At 910, the method may include receiving a second sensing service request from a first device or base station, the second sensing service request including at least first information about the sensing task. Operation of 910 can be performed according to examples as described herein. In some implementations, aspects of operation of 910 may be as described in references... Figure 1A , 1B Or the device described in 1C can be used.

[0236] At 920, the method may include receiving second information about the sensing task from the first UE via a side link. The operation of 920 can be performed according to examples as described herein. In some implementations, aspects of the operation of 920 may be as described in the references... Figure 1A , 1B Or the device described in 1C can be used.

[0237] At 930, the method may include: receiving a reflected signal associated with a sensed signal based on determining that the first information is the same as the second information. The operation of 930 can be performed according to examples as described herein. In some implementations, aspects of the operation of 930 may be as described in the references... Figure 1A , 1B Or the device described in 1C can be used.

[0238] Figure 10A flowchart illustrating a method 1000 supporting side-link-based sensing according to aspects of this disclosure is shown. Operation of method 1000 can be implemented by a device or components thereof as described herein. For example, operation of method 10 can be performed by a first means as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the function. Alternatively, the device can use dedicated hardware to perform aspects of the function.

[0239] At 1010, the method may include receiving a sensing service request from a sensing service consumer at a first device. The operation of 1010 can be performed according to examples as described herein. In some implementations, aspects of the operation of 1010 may be as described in the references... Figure 1A , 1B Or the device described in 1C can be used.

[0240] At point 1020, the method may include, based on the sensing service request, determining a first UE for transmitting a sensing signal and at least one second UE for receiving a reflected signal associated with the sensing signal. The operation of 1020 can be performed according to examples as described herein. In some implementations, aspects of the operation of 1020 may be as described in references... Figure 1A , 1B Or the device described in 1C can be used.

[0241] At 1030, the method may include providing a sensing service request to a first UE and at least one second UE, the sensing service request including at least first information about the sensing task. The operation of 1030 can be performed according to examples as described herein. In some implementations, aspects of the operation of 1030 may be as described in the references... Figure 1A , 1B Or the device described in 1C can be used.

[0242] Figure 11 A flowchart illustrating a method 1100 supporting side-link-based sensing according to aspects of this disclosure is shown. Operation of method 1100 can be implemented by a device or components thereof as described herein. For example, operation of method 11 can be performed by a second UE 104-1 as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the function. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the function.

[0243] At 1110, the method may include sending a request from the base station to the second device to convert a first type ID of the first UE and at least one second UE into a second type ID of the first UE and at least one second UE, the second type ID being recognizable by the base station. The operation of 1110 may be performed according to examples as described herein. In some implementations, aspects of the operation of 1110 may be as described in the references... Figure 1A , 1B Or the device described in 1C can be used.

[0244] At 1120, the method may include receiving a second type of ID from the second device. The operation of 1120 can be performed according to examples as described herein. In some implementations, aspects of the operation of 1120 may be provided by reference to [reference needed]. Figure 1A , 1B Or the device described in 1C can be used.

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

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

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

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

[0249] As used herein, including in the claims, the article “a (a)” preceding an element is unrestricted and is understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a (a),” “at least one,” “one or more,” and “at least one of one or more” may be used interchangeably. As used herein, including in the claims, “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one,” “one or more,” or “one or two”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C represents A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as referring to a closed set of conditions. For example, an example step described as “based on condition A” could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as “at least partially based on.” Moreover, as used herein, including in the claims, “set” can include one or more elements.

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

Claims

1. A first user equipment (UE), comprising: processor; as well as The transceiver coupled to the processor, The processor is configured as follows: The transceiver receives a first sensing service request from a first device or base station, the first sensing service request including at least first information about the sensing task; and Second information about the sensing task is transmitted via the transceiver and side link.

2. The first UE according to claim 1, wherein the first information regarding the sensing task includes a first identifier (ID) of the sensing task, and the second information regarding the sensing task includes a second ID of the sensing task.

3. The first UE of claim 2, wherein the processor is configured to transmit the second information about the sensing task via the transceiver in the following manner: A direct communication request message is sent via the transceiver and side link. The direct communication request message includes the second ID of the sensing task and information about the sensing service type.

4. The first UE according to claim 2, wherein: The processor is also configured to: Determine the destination layer 2 identifier (ID) associated with the sensing service type; and The processor is configured to transmit the second information about the sensing task via the transceiver in the following manner: A broadcast or multicast communication request message is sent via the transceiver and side link. The broadcast or multicast communication request message includes the second ID of the sensing task and the destination layer 2 ID.

5. The first UE according to claim 4, wherein the processor is further configured to: Obtain information about the association between the destination layer 2 ID and the sensing service type from one of the following: The first device, Second device, or Application server.

6. A second user equipment (UE), comprising: processor; as well as The transceiver coupled to the processor, The processor is configured as follows: The transceiver receives a second sensing service request from a first device or base station, the second sensing service request including at least first information about the sensing task; Second information about the sensing task is received from the first UE via the transceiver and side link; as well as Based on the determination that the first information is the same as the second information, a reflected signal associated with the sensing signal is received.

7. The second UE according to claim 6, wherein the first information regarding the sensing task includes a first identifier (ID) of the sensing task, and the second information regarding the sensing task includes a second ID of the sensing task.

8. The second UE of claim 7, wherein the processor is configured to receive the second information regarding the sensing task in such a manner as: The system receives a direct communication request message from the first UE via the transceiver and side link. The direct communication request message includes the second ID of the sensing task and information about the sensing service type.

9. The second UE according to claim 8, wherein the processor is further configured to: Based on the determination that the direct communication request message includes information about the sensing service type, it is determined whether the first information is the same as the second information.

10. The second UE of claim 7, wherein the processor is configured to receive the second information regarding the sensing task in such a manner as: The transceiver and side link receive a broadcast or multicast communication request message from the first UE. The broadcast or multicast communication request message includes the second ID of the sensing task and the destination layer 2 ID, which is associated with the sensing service type.

11. The second UE according to claim 10, wherein the processor is further configured to: Based on the determination that the broadcast or multicast communication request message includes a destination layer 2 ID associated with the sensing service type, it is determined whether the first information is the same as the second information.

12. The second UE according to claim 10, wherein the processor is further configured to: Obtain information about the association between the destination layer 2 ID and the sensing service type from one of the following: The first device, Second device, or Application server.

13. A first device, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory and configured such that the first device: Receive sensing service requests from sensing service consumers; Based on the sensing service request, a first user equipment (UE) for transmitting sensing signals and at least one second UE for receiving reflected signals associated with the sensing signals are determined; as well as The sensing service request is provided to the first UE and the at least one second UE, the sensing service request including at least first information about the sensing task.

14. The first apparatus of claim 13, wherein the first apparatus is configured to provide the sensing service request in the following manner: The first sensing service request is sent to the first UE, and the first sensing service request includes at least the first information about the sensing task.

15. The first apparatus of claim 13, wherein the first apparatus is configured to provide the sensing service request in the following manner: A second sensing service request is sent to the at least one second UE, the second sensing service request including at least the first information about the sensing task.

16. The first apparatus of claim 13, wherein the first apparatus is configured to provide the sensing service request in the following manner: The sensing service request is sent to the base station serving the first UE and the at least one second UE.

17. The first device according to claim 16, wherein the first device is further configured to: Send a request to a second device, the request being used to convert a first type of identifier (ID) of the first UE and the at least one second UE into a second type of ID of the first UE and the at least one second UE, wherein the second type of ID can be recognized by the base station; and Receive the ID of the second type from the second device.

18. The first apparatus of claim 13, wherein the first information relating to the sensing task includes a first identifier (ID) of the sensing task, and the second information relating to the sensing task includes a second ID of the sensing task.

19. A base station, comprising: processor; as well as The transceiver coupled to the processor, The processor is configured as follows: The transceiver sends a request to the second device, the request being used to convert a first type of identifier (ID) of the first user equipment (UE) and at least one second UE into a second type of ID of the first UE and the at least one second UE, the second type of ID being recognizable by the base station; as well as The second type of ID is received from the second device via the transceiver.

20. The base station according to claim 19, wherein the processor is further configured to: The transceiver receives a sensing service request from the first device, the sensing service request including the ID of the first type of the first UE and the at least one second UE.

Images