[go: up one dir, main page]

WO2024119942A1 - Détection basée sur la liaison latérale - Google Patents

Détection basée sur la liaison latérale Download PDF

Info

Publication number
WO2024119942A1
WO2024119942A1 PCT/CN2023/118477 CN2023118477W WO2024119942A1 WO 2024119942 A1 WO2024119942 A1 WO 2024119942A1 CN 2023118477 W CN2023118477 W CN 2023118477W WO 2024119942 A1 WO2024119942 A1 WO 2024119942A1
Authority
WO
WIPO (PCT)
Prior art keywords
sensing
information
task
processor
implementations
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/118477
Other languages
English (en)
Inventor
Haiyan Luo
Mingzeng Dai
Lianhai WU
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2023/118477 priority Critical patent/WO2024119942A1/fr
Publication of WO2024119942A1 publication Critical patent/WO2024119942A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/38—Services specially adapted for particular environments, situations or purposes for collecting sensor information

Definitions

  • the present disclosure relates to wireless communications, and more specifically to apparatuses and methods for sidelink based sensing.
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • Each network communication devices such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) .
  • the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • Wireless sensing technologies aim at acquiring information about an object or its environment and its characteristics without physically contacting it.
  • the perception data of the object and its surrounding can be utilized for analysis so that meaningful information about the object and its characteristics can be obtained. This can be achieved by using a camera, radar, lidar and so on.
  • Integrated Sensing and Communication refers to the technologies that combine sensing and communication systems to utilize wireless resources more efficiently.
  • ISAC provided by 3GPP 5GS means the sensing capabilities are provided by the same 5G NR wireless communication system and infrastructure as used for communication, and the sensing information could be derived from radio frequency (RF) -based and/or non-RF based sensors.
  • RF radio frequency
  • SF sensing function
  • SF can be a standalone network function (NF) or collocated with the existing NF, e.g., location management function (LMF) .
  • a radio access network (RAN) node may communicate with the SF via mobility management function (AMF) or directly.
  • An application server or 5GC NF or UE may trigger a sensing procedure.
  • the SF may assign a sensing task to access node (e.g., RAN node in 3GPP, WLAN access node in non-3GPP etc. ) or UE.
  • the present disclosure relates to UEs, apparatus, base station and methods for sidelink based sensing.
  • sidelink based sensing may be achieved.
  • a first UE described herein may comprise a processor and a transceiver coupled to the processor.
  • the processor is configured to: receive a first sensing service request via the transceiver from a first apparatus or a base station, the first sensing service request comprising at least first information about a sensing task; and transmit second information about the sensing task via the transceiver and sidelink.
  • the processor is configured to transmit the second information about the sensing task via the transceiver by: transmitting the second information about the sensing task via the transceiver and sidelink in a broadcast mode or in a groupcast mode.
  • the first information about the sensing task comprises a first ID of the sensing task
  • the second information about the sensing task comprises a second ID of the sensing task
  • the processor is configured to transmit the second information about the sensing task via the transceiver by: transmitting, via the transceiver and sidelink, a Direct Communication Request message comprising the second ID of the sensing task and information about a sensing service type.
  • the processor is further configured to: determine a Destination Layer-2 ID associated with a sensing service type; and the processor is configured to transmit the second information about the sensing task via the transceiver by:transmitting, via the transceiver and sidelink, a Broadcast or Groupcast Communication Request message comprising the second ID of the sensing task and the Destination Layer-2 ID.
  • the processor is further configured to obtain information about association between the Destination Layer-2 ID and the sensing service type from one of the following: the first apparatus, a second apparatus, or an application server.
  • the first sensing service request further comprises at least one of the following: sensing requirement associated with the sensing task, a sensing mode associated with the sensing task, a first indication indicating the first UE to transmit a sensing signal, a second indication indicating the first UE to collect sensing measurement data associated with the sensing task from at least one second UE and transmit the sensing measurement data to the first apparatus, the at least one second UE receiving a reflected signal associated with the sensing signal, information about transmission of the sensing measurement data via a user plane connection between the first apparatus and the first UE, or a first sidelink signal threshold based on which the first UE determines whether a candidate UE is determined as one of the at least one second UE.
  • a second UE described herein may comprise a processor and a transceiver coupled to the processor.
  • the processor is configured to: receive a second sensing service request via the transceiver from a first apparatus or a base station, the second sensing service request comprising at least first information about a sensing task; receive second information about the sensing task via the transceiver and sidelink from a first UE; and based on determining that the first information is identical to the second information, receive a reflected signal associated with a sensing signal.
  • the first information about the sensing task comprises a first ID of the sensing task
  • the second information about the sensing task comprises a second ID of the sensing task
  • the processor is configured to receive the second information about the sensing task by: receiving, via the transceiver and sidelink from the first UE, a Direct Communication Request message comprising the second ID of the sensing task and information about a sensing service type.
  • the processor is further configured to: based on determining that the Direct Communication Request message comprises the information about the sensing service type, determine whether the first information is identical to the second information.
  • the processor is configured to receive the second information about the sensing task by: receiving, via the transceiver and sidelink from the first UE, a Broadcast or Groupcast Communication Request message comprising the second ID of the sensing task and a Destination Layer-2 ID, the Destination Layer-2 ID being associated with a sensing service type;
  • the processor is further configured to: based on determining that the Broadcast or Groupcast Communication Request message comprises the Destination Layer-2 ID associated with the sensing service type, determine whether the first information is identical to the second information.
  • the processor is further configured to obtain information about association between the Destination Layer-2 ID and the sensing service type from one of the following: the first apparatus, a second apparatus, or an application server.
  • the processor is further configured to: based on determining that a receiving signal strength from the first UE is above a second sidelink signal threshold, determine whether the first information is identical to the second information.
  • the second sensing service request further comprises at least one of the following: sensing requirement associated with the sensing task, a sensing mode associated with the sensing task, a third indication indicating the second UE to receive the reflected signal associated with the sensing signal, a fourth indication indicating the second UE to transmit sensing measurement data to the first UE via sidelink, a fifth indication indicating the second UE to transmit the sensing measurement data to the base station, information about transmission of the sensing measurement data via a user plane connection between the first apparatus and the second UE, or a second sidelink signal threshold based on which the second UE determines whether to receive a reflected signal associated with the sensing signal.
  • Some implementations of a first apparatus described herein may comprise at least one memory and at least one processor coupled with the at least one memory.
  • the at least one processor is configured to: cause the first apparatus 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 comprising at least first information about a sensing task.
  • the first apparatus is caused to provide the sensing service request by: transmitting a first sensing service request to the first UE, the first sensing service request comprising at least the first information about the sensing task.
  • the first sensing service request further comprises at least one of the following: sensing requirement associated with the sensing task, a sensing mode associated with the sensing task, a first indication indicating the first UE to transmit a sensing signal, a second indication indicating the first UE to collect sensing measurement data associated with the sensing task from the at least one second UE and transmit the sensing measurement data to the first apparatus, information about transmission of the sensing measurement data via a user plane connection between the first apparatus and the first UE, or a first sidelink signal threshold based on which the first UE determines whether a candidate UE is determined as one of the at least one second UE.
  • the first apparatus is caused to provide the sensing service request by: transmitting a second sensing service request to the at least one second UE, the second sensing service request comprising at least the first information about the sensing task.
  • the second sensing service request further comprises at least one of the following: sensing requirement associated with the sensing task, a sensing mode associated with the sensing task, a third indication indicating the at least one second UE to receive the reflected signal associated with the sensing signal, a fourth indication indicating the at least one second UE to transmit sensing measurement data to the first UE via sidelink, a fifth indication indicating the at least one second UE to transmit the sensing measurement data to a base station, information about transmission of the sensing measurement data via a user plane connection between the first apparatus and one of the at least one second UE, or a second sidelink signal threshold based on which one of the at least one second UE determines whether to receive the reflected signal.
  • the first apparatus is caused to provide the sensing service request by: transmitting the sensing service request to a base station serving the first UE and the at least one second UE.
  • the sensing service request further comprises at least one of the following: sensing requirement associated with the sensing task, IDs of the first UE and the at least one second UE, a fourth indication indicating the at least one second UE to transmit sensing measurement data to the first UE via sidelink, a fifth indication indicating the at least one second UE to transmit the sensing measurement data to the base station, or information about transmission of the sensing measurement data via a user plane connection between the first apparatus and one of the at least one second UE.
  • the first apparatus is further caused to: transmit, to a second apparatus, a request for translating a first type of IDs of the first UE and the at least one second UE into a second type of IDs of the first UE and the at least one second UE, the second type of IDs being recognizable by the base station; and receive the second type of IDs from the second apparatus.
  • the first information about the sensing task comprises a first ID of the sensing task
  • the second information about the sensing task comprises a second ID of the sensing task
  • a base station described herein may comprise a processor and a transceiver coupled to the processor.
  • the processor is configured to: transmit, via the transceiver to a second apparatus, a request for translating a first type of identities (IDs) of a first UE and at least one second UE into a second type of IDs of the first UE and the at least one second UE, the second type of IDs being recognizable by the base station; and receive the second type of IDs via the transceiver from the second apparatus.
  • IDs first type of identities
  • the processor is further configured to: receive a sensing service request via the transceiver from a first apparatus, the sensing service request comprising the first type of IDs of the first UE and the at least one second UE.
  • the sensing service request further comprises sensing requirement associated with a sensing task; and the processor is further configured to: determine, based on the sensing requirement, resources for transmission of a sensing signal via sidelink, the sensing signal being associated with a sensing task; transmit a first sensing service request via the transceiver to the first UE, the first sensing service request comprising the sensing requirement and information about the resources; and transmit a second sensing service request via the transceiver to the at least one second UE, the second sensing service request comprising the sensing requirement and the information about the resources.
  • Some implementations of a method described herein may comprise: receiving a first sensing service request at a first UE from a first apparatus or a base station, the first sensing service request comprising at least first information about a sensing task; and transmitting second information about the sensing task via sidelink.
  • Some implementations of a method described herein may comprise: receiving a second sensing service request at a second UE from a first apparatus or a base station, the second sensing service request comprising at least first information about a sensing task; receiving second information about the sensing task via sidelink from a first UE; and based on determining that the first information is identical to the second information, receiving a reflected signal associated with a sensing signal.
  • Some implementations of a method described herein may comprise: receiving a sensing service request at a first apparatus from a sensing service consumer; 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 the at least one second UE, the sensing service request comprising at least first information about a sensing task.
  • Some implementations of a method described herein may comprise: transmitting, from a base station to a second apparatus, a request for translating a first type of IDs of a first UE and at least one second UE into a second type of IDs of the first UE and the at least one second UE, the second type of IDs being recognizable by the base station; and receiving the second type of IDs from the second apparatus.
  • Figs. 1A, 1B and 1C illustrate an example of a wireless communications system that supports sidelink based sensing in accordance with aspects of the present disclosure, respectively;
  • Figs. 2 to 4 illustrate a signaling diagram illustrating an example process that supports sidelink based sensing in accordance with aspects of the present disclosure, respectively;
  • Fig. 5 illustrates a signaling diagram illustrating an example sensing registration procedure in accordance with aspects of the present disclosure
  • Fig. 6 illustrates an example of a device that supports sidelink based sensing in accordance with some aspects of the present disclosure
  • Fig. 7 illustrates an example of a processer that supports sidelink based sensing in accordance with other aspects of the present disclosure.
  • Figs. 8 to 11 illustrate a flowchart of a method that supports sidelink based sensing in accordance with other aspects of the present disclosure, respectively.
  • references in the present disclosure to “one implementation, ” “an example implementation, ” “an implementation, ” “some implementations, ” and the like indicate that the implementation (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every implementation includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same implementation (s) . Further, when a particular feature, structure, or characteristic is described in connection with an implementation, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other implementations whether or not explicitly described.
  • first and second or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of implementations. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.
  • Fig. 1A illustrates an example of a wireless communications system 100A that supports sidelink based sensing in accordance with aspects of the present disclosure.
  • the wireless communications system 100A may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more terminal devices or UEs 104, a core network 106, and a packet data network 108.
  • the UEs 104 may comprise a UE 104-1 and a UE 104-2.
  • the UE 104-1 and the UE 104-2 are also referred to as a first UE 104-1 and a second UE 104-2, respectively.
  • the wireless communications system 100A may support various radio access technologies.
  • the wireless communications system 100A may be a 4G network, such as an LTE network or an LTE-advanced (LTE-A) network.
  • the wireless communications system 100A may be a 5G network, such as an NR network.
  • the wireless communications system 100A may be a combination of a 4G network and a 5G network, or other suitable radio access technology including institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20.
  • IEEE institute of electrical and electronics engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • the wireless communications system 100A may support radio access technologies beyond 5G. Additionally, the wireless communications system 100A may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100A.
  • One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • RAN radio access network
  • eNB eNodeB
  • gNB next-generation NodeB
  • a network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection.
  • a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • a network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112.
  • a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies.
  • a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network.
  • different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • the one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100A.
  • a UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples.
  • IoT Internet-of-Things
  • IoE Internet-of-Everything
  • MTC machine-type communication
  • a UE 104 may be stationary in the wireless communications system 100A.
  • a UE 104 may be mobile in the wireless communications system 100A.
  • the one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in Fig. 1.
  • a UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in Fig. 1.
  • a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100A.
  • a UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • a network entity 102 may support communications with the core network 106, or with another network entity 102, or both.
  • a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) .
  • the network entities 102 may communicate with each other directly (e.g., between the network entities 102) .
  • the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) .
  • one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) .
  • An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
  • TRPs transmission-reception points
  • a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack 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) ) .
  • IAB integrated access backhaul
  • O-RAN open RAN
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.
  • CU central unit
  • DU distributed unit
  • RU radio unit
  • RIC RAN Intelligent Controller
  • RIC e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC)
  • SMO Service Management and Orchestration
  • An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof
  • a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack.
  • the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • RRC Radio Resource Control
  • SDAP service data adaption protocol
  • PDCP Packet Data Convergence Protocol
  • the CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access
  • a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack.
  • the DU may support one or multiple different cells (e.g., via one or more RUs) .
  • a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .
  • a CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • a CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u)
  • a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface)
  • FH open fronthaul
  • a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.
  • the core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.
  • NAS non-access stratum
  • the core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the packet data network 108 may include an application server 118.
  • one or more UEs 104 may communicate with the application server 118.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102.
  • the core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) .
  • the PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .
  • the network entities 102 and the UEs 104 may use resources of the wireless communications system 100A (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) .
  • the network entities 102 and the UEs 104 may support different resource structures.
  • the network entities 102 and the UEs 104 may support different frame structures.
  • the network entities 102 and the UEs 104 may support a single frame structure.
  • the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) .
  • the network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.
  • One or more numerologies may be supported in the wireless communications system 100A, and a numerology may include a subcarrier spacing and a cyclic prefix.
  • a first subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first subcarrier spacing e.g., 15 kHz
  • a time interval of a resource may be organized according to frames (also referred to as radio frames) .
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • a subframe may include a number (e.g., quantity) of slots.
  • the number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100A.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • the wireless communications system 100A may support one or multiple operating frequency bands, such as frequency range designations 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) .
  • the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • Fig. 1B illustrates an example of a wireless communications system 100B that supports sidelink based sensing in accordance with aspects of the present disclosure. Specifically, Fig. 1B illustrates network entities or Network Functions (NFs) in the core network 106 as shown in Fig. 1A.
  • NFs Network Functions
  • the core network 106 may comprise at least a mobility management function (AMF) 120 and an SF 122.
  • AMF mobility management function
  • the AMF 120 may communicate with the UE 104 and the base station 102 via N1 interface and N2 interface, respectively.
  • the SF 122 enables sensing in a 5G network.
  • the SF 122 may be a standalone 5GC NF or co-located with the existing 5GC NF, e.g., LMF.
  • the SF 122 may communicate with the AMF 120 via NS1 interface.
  • the SF 122 may comprise an SF control plane (SF-C) part and an SF user plane (SF-U) part.
  • SF-C SF control plane
  • SF-U SF user plane
  • the SF 122 may communicate with the base station 102 via the AMF 120. Alternatively, the SF 122 may communicate with the base station 102 directly via an interface therebetween.
  • ISAC may be performed in the wireless communications systems 100A and 100B.
  • an application server or 5GC NF or the UE 104 may trigger a sensing procedure.
  • the SF 122 may assign a sensing task to the base station 102 or UE 104.
  • a sensing mode may comprise at least one of the following:
  • ⁇ Sensing mode#1 a base station works as both Sensing Transmitter (Tx) and Sensing Receiver (Rx) ;
  • ⁇ Sensing mode#2 a first base station and a second base station work as the Sensing Tx and Sensing Rx, respectively;
  • ⁇ Sensing mode#3 a UE and a base station work as the Sensing Tx and Sensing Rx, respectively;
  • ⁇ Sensing mode#4 a base station and a UE work as the Sensing Tx and Sensing Rx, respectively;
  • ⁇ Sensing mode#5 a first UE and a second UE work as the Sensing Tx and Sensing Rx, respectively; or
  • ⁇ Sensing mode#6 a UE works as both Sensing Tx and Sensing Rx.
  • Fig. 1C illustrates an example of a wireless communications system 100C that supports sidelink based sensing in accordance with aspects of the present disclosure.
  • the sensing mode#5 may be performed.
  • the first UE 104-1 works as a Sensing Tx and transmits a sensing signal via sidelink.
  • the sensing signal is reflected by a sensing object 130.
  • the second UE 104-2 works as a Sensing Rx and receives a reflected signal associated with the sensing signal. It needs to discuss how to coordinate with the Sensing Tx and the Sensing Rx to perform a sensing task.
  • a first UE receives a first sensing service request from a first apparatus or a base station.
  • the first sensing service request comprises at least first information about a sensing task.
  • the first UE transmit second information about the sensing task via sidelink.
  • sidelink based sensing may be achieved.
  • Fig. 2 illustrates a signaling diagram illustrating an example process 200 that supports sidelink based sensing in accordance with aspects of the present disclosure.
  • the process 200 may involve the first UE 104-1, the second UE 104-2, the base station 102, a first apparatus and a second apparatus.
  • the first apparatus may perform the SF 122 in Fig. 1B.
  • the first apparatus may perform other network function than the SF 122 in Fig. 1B.
  • the second apparatus may perform the AMF 120 in Fig. 1B.
  • the second apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the process 200 will be described with reference to Fig. 1B and 1C.
  • the process 200 may involve the base station 102, the AMF 120 and the SF 122 in Fig. 1B, the first UE 104-1 and the second UE 104-2 in Fig. 1B or 1C as well as a sensing service consumer 140 (which is not shown in Fig. 1B or 1C)
  • the SF 122 may assign a sensing task to the first UE 104-1 and the second UE 104-2 directly.
  • the SF 122 receives 205 a sensing service request from the sensing service consumer 140.
  • the sensing service request comprises at least information about a sensing task.
  • the information about the sensing task may comprise an identity (ID) of the sensing task.
  • ID identity of the sensing task.
  • the ID of the sensing task is also referred to as a sensing task ID.
  • the first information about the sensing task may comprise a sensing transaction ID or a correlation ID.
  • the sensing service request may further comprise at least one of the following: sensing requirement associated with the sensing task, a target sensing area or a target sensing object (such as the sensing object 130 in Fig. 1C) .
  • the sensing requirement may comprise at least one of the following: a sensing service type, a sensing service type resolution and accuracy of sensing object’s location/velocity/angle, a refresh rate, a target detection ratio, a target false alarm ratio, a sensing area, a sensing velocity range, a sensing duration (e.g., sensing start time, sensing end time) , a reporting period, or delay.
  • a sensing service type e.g., a sensing service type resolution and accuracy of sensing object’s location/velocity/angle, a refresh rate, a target detection ratio, a target false alarm ratio, a sensing area, a sensing velocity range, a sensing duration (e.g., sensing start time, sensing end time) , a reporting period, or delay.
  • the target sensing object may be a UE or a non-UE object.
  • the target sensing area or the target sensing object may be comprised in the sensing requirement.
  • the sensing service consumer may be a UE, an application function (AF) , the application server 118 or a 5GC NF (e.g., a network data analytics function (NWDAF) ) .
  • AF application function
  • NWDAF network data analytics function
  • the sensing service type may be one of the following smart transportation (e.g., high definition map construction or intrusion detection) , smart low attitude (e.g., flight intrusion detection or flight path management) , smart network (e.g., channel estimation enhancement or beam management) and smart life (e.g., respiratory monitoring, gesture or posture recognition) .
  • smart transportation e.g., high definition map construction or intrusion detection
  • smart low attitude e.g., flight intrusion detection or flight path management
  • smart network e.g., channel estimation enhancement or beam management
  • smart life e.g., respiratory monitoring, gesture or posture recognition
  • the SF 122 determines 210 a sensing mode based on the sensing service request.
  • the SF 122 may be pre-configured by operations administration and maintenance (OAM) , a public land mobile network (PLMN) or Operator with mapping between a sensing service type and at least one sensing mode.
  • OAM operations administration and maintenance
  • PLMN public land mobile network
  • the mapping between a sensing service type and at least one sensing mode may be pre-defined.
  • the SF 122 may select a sensing mode based on the sensing service type and the mapping between a sensing service type and at least one sensing mode.
  • the selected sensing mode may be one of the sensing modes #1 to #6 as described above.
  • the sensing mode #5 as an example of the selected sensing mode.
  • the SF 122 determines 215, based on the sensing service request, the first UE 104-1 for transmitting a sensing signal and at least one second UE 104-2 for receiving a reflected signal associated with the sensing signal. In other words, the SF 122 selects the first UE 104-1 as a Sensing Tx and at least one second UE 104-2 as at least one Sensing Rx.
  • the SF 122 may select the Sensing Tx and the at least one Sensing Rx for the sensing mode#5 based on a UE location and the target sensing area or a location of the target sensing object.
  • the SF 122 may subscribe UE Affiliation information to the AMF 120.
  • the UE Affiliation information may comprise information about a base station serving a UE, a cell or a Tracking Area (TA) where the UE is located.
  • the UE Affiliation information may comprise one of the following, gNB ID, Cell ID, Tracking Area Identity (TAI) , Tracking Area Code (TAC) .
  • the AMF 120 may provide the UE Affiliation information to the SF 122 upon handover or Tracking Area Update (TAU) .
  • a sensing UE such as the first UE 104-1 or the second UE 104-2 may provide UE Affiliation information to the SF 122 instead.
  • the SF 122 is able to determine the serving base station, TAI or TAC of the UE.
  • the SF 122 may subscribe location service to the AMF 120 or LMF (which is not shown) in order to obtain a UE location.
  • the UE location may be the geographical coordinates, e.g., X/Y/Z coordinates.
  • the SF 122 may select a first sensing UE (such as the first UE 104-1) as the Sensing Tx based on sensing capability of the first sensing UE (e.g., Tx capability, Rx capability etc. ) , the UE location and the target sensing area or target sensing object etc.
  • the SF 122 may further select at least one second sensing UE as at least one candidate Sensing Rx based on a distance between the Sensing Tx and a respective second sensing UE.
  • the SF 122 may obtain sensing capability of a sensing UE via a sensing registration procedure. This will be described later with reference to Fig. 5.
  • the SF 122 transmits 220 a first sensing service request to the first UE 104-1.
  • the first sensing service request may comprise at least the first information about the sensing task.
  • the first sensing service request may comprise a first ID of the sensing task.
  • the first ID of the sensing task is also referred to as a first sensing task ID.
  • the first sensing service request may further comprise at least one of the following: sensing requirement associated with the sensing task, a sensing mode associated with the sensing task, or a first indication indicating the first UE 104-1 to transmit a sensing signal.
  • the first indication is also referred to as a Sensing Tx indication.
  • the first sensing service request may further comprise a second indication indicating the first UE 104-1 to collect sensing measurement data associated with the sensing task from the at least one second UE 104-2 and transmit the sensing measurement data to the SF 122.
  • the second indication is also referred to as a report indication.
  • the first sensing service request may further comprise information about transmission of the sensing measurement data via a user plane (UP) connection between the SF 122 and the first UE 104-1.
  • UP user plane
  • the information about transmission of the sensing measurement data via a UP connection between the SF 122 and the first UE 104-1 is also referred to as first UP reporting information.
  • the first UP reporting information may comprise a UP report indicator and a reporting address (e.g., the IP address of the SF 122 or the SF-U part for UP reporting) .
  • the first UP reporting information may be provided without the UP report indicator.
  • the SF 122 may further provide an ID list of at least one candidate Sensing Rx comprising at least one ID of the at least one candidate Sensing Rx.
  • An ID of a Sensing Rx may be an Application Layer ID or other types of UE ID.
  • the first sensing service request may further comprise a first sidelink signal threshold.
  • the first UE 104-1 i.e., the Sensing Tx UE
  • the first UE 104-1 may determine a candidate UE as one of the at least one second UE 104-2 (i.e., the Sensing Rx UE) .
  • the first UE 104-1 may determine the candidate UE as the second UE 104-2.
  • the first UE 104-1 may autonomously select resources for transmission of a sensing signal via sidelink from at least one resource pool provided by broadcast system information or dedicated signalling while inside NG-RAN coverage.
  • the resources for transmission of a sensing signal via sidelink is also referred to as sidelink sensing resources.
  • the first UE 104-1 may request the sidelink sensing resources from the base station 102 serving the first UE 104-1.
  • the first UE 104-1 may transmit 225 a sidelink sensing resource request message to the base station 102.
  • the sidelink sensing resource request message may be a new type of dedicated radio resource control (RRC) message.
  • RRC radio resource control
  • the sidelink sensing resource request message may be an existing RRC message with new parameters.
  • the sidelink sensing resource request message may comprise the first sensing task ID and the sensing requirement.
  • the base station 102 may determine the sidelink sensing resources based on the sensing requirement.
  • the sidelink sensing resource request message may comprise required sidelink sensing resources without the sensing requirement.
  • the required sidelink sensing resource may be the required physical resource block (PRB) number, frame number or slot number.
  • the base station 102 transmits 230 a sidelink sensing resource response message to the first UE 104-1.
  • the sidelink sensing resource response message may comprise the first sensing task ID and information about the sidelink sensing resources.
  • the information about the sidelink sensing resources is also referred to as sidelink sensing resource information.
  • the sidelink sensing resource information may comprise the time/frequency/spatial information and other information related to the sensing signal.
  • the sidelink sensing resource information may comprise at least one of the following: frame index, sub-frame index, slot index, sub-slot index, PRB index, synchronization signal block (SSB) index, beam index, bandwidth part (BWP) ID, the transmit power of the sensing signal, or the transmit signal sequence.
  • the actions 225 and 230 will not be performed.
  • the first UE 104-1 may transmit 235 a sensing service response message to the SF 122 in order to inform the SF 122 whether it accepts the sensing task.
  • the sensing service response message may comprise the sidelink sensing resource information.
  • the SF 122 transmits 240 a second sensing service request to the at least one second UE 104-2.
  • the second sensing service request may comprise at least the first information about the sensing task.
  • the second sensing service request may comprise the first ID of the sensing task.
  • the second sensing service request may further comprise at least one of the following: sensing requirement associated with the sensing task, a sensing mode associated with the sensing task, or a third indication indicating the at least one second UE 104-2 to receive the reflected signal associated with the sensing signal.
  • the third indication is also referred to as a Sensing Rx indication.
  • the second sensing service request may further comprise a fourth indication indicating the at least one second UE 104-2 to transmit sensing measurement data to the first UE 104-1 via sidelink.
  • the fourth indication is also referred to as a report to Tx indication.
  • the second sensing service request may further comprise a fifth indication indicating the at least one second UE 104-2 to transmit the sensing measurement data to the base station 102.
  • the fifth indication is also referred to as a report to RAN node indication.
  • the second sensing service request may further comprise information about transmission of the sensing measurement data via a UP connection between the SF 122 and one of the at least one second UE 104-2.
  • the information about transmission of the sensing measurement data via a UP connection between the SF 122 and one of the at least one second UE 104-2 is also referred to as second UP reporting information.
  • the second UP reporting information may comprise a UP report indicator and a reporting address (e.g., the IP address of the SF 122 or the SF-U part for UP reporting) . If the second UP reporting information is provided, it means the second UE 104-2 shall report to the SF 122 by itself via the UP connection therebetween.
  • a reporting address e.g., the IP address of the SF 122 or the SF-U part for UP reporting
  • the second sensing service request may further comprise a second sidelink signal threshold.
  • the second UE 104-2 may determine whether to receive the reflected signal associated with the sensing signal.
  • the second UE 104-2 acting as a candidate Sensing Rx may determine whether it can be a Sensing Rx. For example, if a receiving signal strength from the first UE 104-1 (i.e., the Sensing Tx) is above the second sidelink signal threshold, the second UE 104-2 may determine it can be a Sensing Rx.
  • the SF 122 may further provide the sidelink sensing resource information to the second UE 104-2 in the second sensing service request.
  • the second UE 104-2 may transmit a sensing service response message to the SF 122 in order to inform the SF 122 whether it accepts the sensing task, which is not shown in Fig. 2.
  • the first UE 104-1 transmits 252 second information about the sensing task to the second UE 104-2 via sidelink.
  • the second information about the sensing task may comprise a second ID of the sensing task.
  • the second ID of the sensing task is also referred to as a second sensing task ID.
  • the second information about the sensing task may comprise a sensing transaction ID or a correlation ID.
  • the first UE 104-1 may transmit the second information about the sensing task via sidelink in a unicast mode.
  • the first UE 104-1 may transmit a Direct Communication Request message for unicast link establishment procedure.
  • the Direct Communication Request message may comprise the second ID of the sensing task and information about a sensing service type.
  • the sensing service may be defined as a dedicated or new vehicle-to-everything (V2X) service type.
  • V2X vehicle-to-everything
  • different sensing service type e.g., smart transportation, smart low attitude, smart network and smart life
  • the Direct Communication Request message may comprise a field of V2X Service Info.
  • the field of V2X Service Info may comprise the information about the sensing service (or sensing service type) requesting Layer-2 link establishment.
  • the Direct Communication Request message may further comprise the sensing requirement.
  • the first UE 104-1 may transmit the second information about the sensing task via sidelink in a broadcast or groupcast mode.
  • the first UE 104-1 may transmit, via sidelink, a Broadcast or Groupcast Communication Request message.
  • the Broadcast or Groupcast Communication Request message may comprise the second ID of the sensing task and a Destination Layer-2 ID associated with a sensing service (or a sensing service type) .
  • a sensing service may be associated with a Destination Layer-2 ID.
  • a specific sensing service type may be associated with a Destination Layer-2 ID.
  • the Broadcast or Groupcast Communication Request message may further comprise the sensing requirement.
  • the sensing service may be defined as a dedicated or new V2X service type.
  • the first UE 104-1 may obtain information about association or mapping between the Destination Layer-2 ID and the sensing service (or the sensing service type) from one of the following: the SF 122, a policy control function (PCF) , a V2X Application server or a Sensing Application server (which are not shown in Fig. 1A, 1B or 1C) .
  • the first UE 104-1 may determine the Destination Layer-2 ID based on the sensing service (or the sensing service type) and the association between the Destination Layer-2 ID and the sensing service (or the sensing service type) .
  • the second UE 104-2 Upon receiving the second information about the sensing task, the second UE 104-2 determines 254 whether the first information about the sensing task received from the SF 122 is identical to the second information about the sensing task. For example, the second UE 104-2 may determine whether the first sensing task ID is identical to the second sensing task ID.
  • the second UE 104-2 receives 265 a reflected signal associated with a sensing signal.
  • the second UE 104-2 may receive the reflected signal based on the sidelink sensing resource information received from the SF 122 or the first UE 104-1. For example, the second UE 104-2 may receive the reflected signal by monitoring the sidelink sensing resource.
  • the second UE 104-2 may receive the second information about the sensing task via sidelink from the first UE 104-1 in a unicast mode. In such implementations, the second UE 104-2 may receive a Direct Communication Request message for unicast link establishment procedure.
  • the Direct Communication Request message may comprise the second ID of the sensing task and information about the sensing service (or a sensing service type) .
  • the second UE 104-2 may first determine whether the Direct Communication Request message comprises the information about the sensing service (or the sensing service type) . If the Direct Communication Request message comprises the information about the sensing service (or the sensing service type) , the second UE 104-2 may further determine whether the first information is identical to the second information.
  • the second UE 104-2 may receive the second information about the sensing task which is transmitted by the first UE 104-1 via sidelink in a broadcast or groupcast mode.
  • the second UE 104-2 may receive a Broadcast or Groupcast Communication Request message from the first UE 104-1.
  • the Broadcast or Groupcast Communication Request message may comprise the second ID of the sensing task and a Destination Layer-2 ID associated with sensing service (or a sensing service type) .
  • the second UE 104-2 may first determine whether the Broadcast or Groupcast Communication Request message comprises the Destination Layer-2 ID associated with the sensing service (or the sensing service type) . If the Broadcast or Groupcast Communication Request message comprises the Destination Layer-2 ID associated with the sensing service (or the sensing service type) , the second UE 104-2 may further determine whether the first information is identical to the second information.
  • the sensing service (or the sensing service type) may be defined as a dedicated or new V2X service type.
  • the second UE 104-2 may obtain information about association or mapping between the Destination Layer-2 ID and the sensing service (or the sensing service type) from one of the following: the SF 122, a PCF, a V2X Application server or a Sensing Application server (which are not shown in Fig. 1A, 1B or 1C) .
  • the second UE 104-2 may first determine whether a receiving signal strength from the first UE 104-1 is above a second sidelink signal threshold. If the receiving signal strength from the first UE 104-1 is above the second sidelink signal threshold, the second UE 104-2 may further determine whether the first information is identical to the second information.
  • the second sidelink signal threshold may be pre-configured or received from the SF 122.
  • the second UE 104-2 may first determine whether the sensing requirement provided by the first UE 104-1 via sidelink is identical to the one provided by the SF 122 (for example, via the action 240) . If the sensing requirement provided by the first UE 104-1 via sidelink is identical to the one provided by the SF 122, the second UE 104-2 may further determine whether the first information is identical to the second information.
  • the second UE 104-2 may transmit 256 a response message to the first UE 104-1 by using a source Layer-2 ID assigned by the second UE 104-2. By doing so, Sensing Tx/Rx Association is finished.
  • the second UE 104-2 may receive the reflected signal associated with the sensing signal transmitted by the first UE 104-1. If the first sidelink signal threshold is provided by the SF 122, the first UE 104-1 may further determine whether the receiving signal strength from the second UE 104-2 is above the first sidelink signal threshold or not. If the receiving signal strength from the second UE 104-2 is above the first sidelink signal threshold, the first UE 104-1 may mark the second UE 104-2 as a Sensing Rx UE.
  • the first UE 104-1 may further inform the candidate sensing Rx (such as the second UE 104-2 ) to stop monitoring and release the sidelink connection therebetween. If an ID of the candidate Sensing Rx is provided by the SF 122, the first UE 104-1 may further determine whether an Application Layer ID of the candidate Sensing Rx matches the one provided by the SF 122.
  • the first UE 104-1 may provide 260 the sidelink sensing resource information and the second sensing task ID to the second UE 104-2 via sidelink. For example, if unicast link between the first UE 104-1 and the second UE 104-2 is established via the Sensing Tx/Rx association procedure 250, the first UE 104-1 provides the sidelink sensing resource information and the second sensing task ID via the unicast link. Otherwise, the first UE 104-1 broadcasts or groupcasts the sidelink sensing resource information and the second sensing task ID instead. In some implementations, if the first UE 104-1 does not provide the sidelink sensing resource information to the SF 122 in the action 235, the action 260 may be performed.
  • the second UE 104-2 may generate 270 sensing measurement data based on the reflected signal.
  • the second UE 104-2 will trigger 275 a sensing user plane establishment procedure.
  • the second UE 104-2 may provide 280 the sensing measurement data report to the SF 122.
  • the SF 122 may calculate 285 the sensing result based on the sensing measurement report.
  • the SF 122 may expose 290 the sensing results towards the sensing service consumer 140.
  • a Sensing Tx may coordinate with at least one Sensing Rx to perform a sensing task.
  • Fig. 3 illustrates a signaling diagram illustrating an example process 300 that supports sidelink based sensing in accordance with aspects of the present disclosure.
  • the process 300 may involve the first UE 104-1, the second UE 104-2, the base station 102, a first apparatus and a second apparatus.
  • the first apparatus may perform the SF 122 in Fig. 1B.
  • the first apparatus may perform other network function than the SF 122 in Fig. 1B.
  • the second apparatus may perform the AMF 120 in Fig. 1B.
  • the second apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the process 300 will be described with reference to Fig. 1B and 1C.
  • the process 300 may involve the base station 102, the AMF 120 and the SF 122 in Fig. 1B, the first UE 104-1 and the second UE 104-2 in Fig. 1B or 1C as well as a sensing service consumer 140 (which is not shown in Fig. 1B or 1C)
  • the SF 122 may assign a sensing task to the first UE 104-1 and the second UE 104-2 via the base station 102.
  • the SF 122 may provide IDs of a Sensing Tx and at least one candidate Sensing Rx together with information about the sensing task to the base station 102. It is assumed that the SF 122 is able to know that the Sensing Tx and the at least one candidate Sensing Rx are in a serving area of the base station 102.
  • the base station 102 may determine resources for transmission of a sensing signal via sidelink and provide information about the resources to the Sensing Tx and the at least one Sensing Rx, respectively.
  • the base station 102 can identify a UE based on the AMF/RAN UE NGAP ID provided by the AMF 120 as described later with reference to Fig. 5. However, the base station 102 is not able to identify the UE by a UE ID provided by the SF 122 directly.
  • the UE ID provided by the SF 122 may be one of the following: subscription permanent identifier (SUPI) , generic public subscription identifier (GPSI) , or 5G globally unique temporary UE identity (5G-GUTI) .
  • the UE will report an ID of the UE (such as 5G system architecture evolution temporary mobile station identifier (5G-S- TMSI) ) to the base station 102 in an uplink (UL) RRC message.
  • 5G-S- TMSI 5G system architecture evolution temporary mobile station identifier
  • the base station 102 has the mapping between 5G-S-TMSI and cell-radio network temporary identifier (C-RNTI) of the UE, where C-RNTI is the UE ID used via air interface by the base station 102.
  • C-RNTI cell-radio network temporary identifier
  • the base station 102 is able to identify the UE if the SF 122 provides 5G-S-TMSI. If a UE ID provided by the SF 122 is not known by the base station 102, e.g., SUPI, GPSI, 5G-GUTI and so on, UE ID translation for the base station 102 is needed.
  • a UE ID translation procedure 320 between the SF 122 and the AMF 120 may be performed.
  • the SF 122 transmits 322, to the AMF 120, a request for translating a first type of IDs of the first UE 104-1 and the at least one second UE 104-2 into a second type of IDs of the first UE 104-1 and the at least one second UE 104-2.
  • the second type of IDs are recognizable by the base station 102.
  • the first type of IDs of the first UE 104-1 and the at least one second UE 104-2 may be IDs of the first UE 104-1 and the at least one second UE 104-2 which are used via a service interface between NFs in the core network 106.
  • the first type of IDs may be SUPIs, GPSIs or 5G-GUTIs of the first UE 104-1 and the at least one second UE 104-2.
  • the AMF 120 Upon receiving the request, the AMF 120 translates the first type of IDs of the first UE 104-1 and the at least one second UE 104-2 into the second type of IDs of the first UE 104-1 and the at least one second UE 104-2.
  • the second type of IDs of the first UE 104-1 and the at least one second UE 104-2 may be IDs of the first UE 104-1 and the at least one second UE 104-2 which are used via a point-to-point interface between the based station 102 and an NF in the core network 106.
  • the second type of IDs are recognizable by the base station 102.
  • the second type of IDs may be AMF/RAN UE NGAP IDs of the first UE 104-1 and the at least one second UE 104-2.
  • the AMF 120 transmits 324 the second type of IDs of the first UE 104-1 and the at least one second UE 104-2 to the SF 122.
  • the SF 122 transmits 330 a sensing service request to the base station 102.
  • the sensing service request comprises at least information about a sensing task.
  • the information about the sensing task may comprise a sensing task ID.
  • the information about the sensing task may comprise a sensing transaction ID or a correlation ID.
  • the sensing service request may further comprise the second type of IDs of the first UE 104-1 and the at least one second UE 104-2.
  • the base station 102 may translate the second type of IDs into IDs of the first UE 104-1 and the at least one second UE 104-2 used via air interface.
  • the base station 102 may translate the second type of IDs into C-RNTIs of the first UE 104-1 and the at least one second UE 104-2.
  • the sensing service request may further comprise the sensing requirement associated with the sensing task.
  • the base station 102 may determine 335, based on the sensing requirement, resources for transmission of a sensing signal via sidelink.
  • the sensing signal is associated with the sensing task.
  • the base station 102 may determine, based on the sensing task ID, the resources for transmission of the sensing signal via sidelink.
  • the resources for transmission of a sensing signal via sidelink is also referred to as sidelink sensing resources.
  • the base station 102 transmits 340 a first sensing service request to a Sensing Tx (such as the first UE 104-1) identified by the second type of ID of the Sensing Tx.
  • the first sensing service request may comprise the first sensing task ID.
  • the first sensing service request may further comprise information about the sidelink sensing resources.
  • the information about the sidelink sensing resources is also referred to as sidelink sensing resource information.
  • the first sensing service request may further comprise at least one of the following: the sensing requirement associated with the sensing task, the Sensing Tx indication or the first sidelink signal threshold.
  • the base station 102 transmits 345 a second sensing service request to at least one Sensing Rx (such as the second UE 104-2) identified by the second type of ID of the Sensing Rx.
  • the second sensing service request may further comprise the sidelink sensing resource information.
  • the second sensing service request may further comprise at least one of the following: the sensing requirement associated with the sensing task, the Sensing Rx indication, the second sidelink signal threshold, the report to Tx indication, the report to RAN node indication, or the second UP reporting information.
  • Actions 205, 210, 215, 252, 254, 256, 260, 265, 270, 275, 280, 285 and 290 in the process 300 are similar to those in the process 200. Details of these actions are omitted for brevity.
  • Fig. 4 illustrates a signaling diagram illustrating an example process 400 that supports sidelink based sensing in accordance with aspects of the present disclosure.
  • the process 400 may involve the first UE 104-1, the second UE 104-2, the base station 102, a first apparatus and a second apparatus.
  • the first apparatus may perform the SF 122 in Fig. 1B.
  • the first apparatus may perform other network function than the SF 122 in Fig. 1B.
  • the second apparatus may perform the AMF 120 in Fig. 1B.
  • the second apparatus may perform other network function than the AMF 120 in Fig. 1B.
  • the process 400 will be described with reference to Fig. 1B and 1C.
  • the process 400 may involve the base station 102, the AMF 120 and the SF 122 in Fig. 1B, the first UE 104-1 and the second UE 104-2 in Fig. 1B or 1C as well as a sensing service consumer 140 (which is not shown in Fig. 1B or 1C)
  • the SF 122 may assign a sensing task to the first UE 104-1 and the second UE 104-2 via the base station 102.
  • the process 400 is different from the process 300 mainly in that a UE ID translation procedure 430 between the base station 102 and the AMF 120 is performed.
  • the SF 122 transmits 420 a sensing service request to the base station 102.
  • the sensing service request comprises at least information about a sensing task.
  • the information about the sensing task may comprise a sensing task ID.
  • the information about the sensing task may comprise a sensing transaction ID or a correlation ID.
  • the sensing service request may further comprise the first type of IDs of the first UE 104-1 and the at least one second UE 104-2.
  • the sensing service request may further comprise the sensing requirement associated with the sensing task.
  • the sensing service request may further comprise at least one of the following: the fourth indication indicating the at least one second UE 104-2 to transmit sensing measurement data to the first UE 104-1 via sidelink, the fifth indication indicating the at least one second UE 104-2 to transmit the sensing measurement data to the base station 102, or the information about transmission of the sensing measurement data via a user plane connection between the SF 122 and one of the at least one second UE 104-2.
  • the base station 102 may determine 425, based on the sensing requirement, resources for transmission of a sensing signal via sidelink.
  • the sensing signal is associated with the sensing task.
  • the base station 102 may determine, based on the sensing task ID, the resources for transmission of the sensing signal via sidelink.
  • the resources for transmission of a sensing signal via sidelink is also referred to as sidelink sensing resources.
  • the base station 102 transmits 432, to the AMF 120, a request for translating the first type of IDs of the first UE 104-1 and the at least one second UE 104-2 into the second type of IDs of the first UE 104-1 and the at least one second UE 104-2.
  • the second type of IDs are recognizable by the base station 102.
  • the first type of IDs of the first UE 104-1 and the at least one second UE 104-2 may be IDs of the first UE 104-1 and the at least one second UE 104-2 which are used via a service interface between NFs in the core network 106.
  • the first type of IDs may be SUPIs, GPSIs or 5G-GUTIs of the first UE 104-1 and the at least one second UE 104-2.
  • the AMF 120 Upon receiving the request, the AMF 120 translates the first type of IDs of the first UE 104-1 and the at least one second UE 104-2 into the second type of IDs of the first UE 104-1 and the at least one second UE 104-2.
  • the second type of IDs of the first UE 104-1 and the at least one second UE 104-2 may be IDs of the first UE 104-1 and the at least one second UE 104-2 which are used via a point-to-point interface between the based station 102 and an NF in the core network 106.
  • the second type of IDs are recognizable by the base station 102.
  • the second type of IDs may be AMF/RAN UE NGAP IDs of the first UE 104-1 and the at least one second UE 104-2.
  • the AMF 120 transmits 434 the second type of IDs of the first UE 104-1 and the at least one second UE 104-2 to the base station 102.
  • Actions 205, 210, 215, 252, 254, 256, 260, 265, 270, 275, 280, 285 and 290 in the process 300 are similar to those in the process 200.
  • Actions 340 and 345 in the process 400 are similar to those in the process 300. Details of these actions are omitted for brevity.
  • the Sensing Tx and a candidate sensing Rx may be not served by the same base station.
  • the Sensing Tx is served by the base station 102
  • the candidate sensing Rx is served by a second base station which is different from the base station 102.
  • the SF 122 may transmit the sensing task ID, the sensing requirement, the candidate Sensing Rx ID, the report to Tx indicator, the report to RAN node indicator and the UP reporting information to the base station 102.
  • the SF 122 may need to provide an ID of a serving RAN node (e.g., NG-RAN#2) of the Sensing Rx to a serving RAN node of the Sensing Tx (e.g., NG-RAN#1) , e.g., in the action 330 or 420.
  • NG-RAN#1 may transmit a sensing Task ID#1 and sidelink resource information to NG-RAN#2 via Xn interface.
  • NG-RAN#2 will forward the sidelink resource information to the Sensing Rx associated with the same sensing task ID as in the action 345.
  • the sidelink sensing resource information is provided via sidelink, no additional steps are needed.
  • the SF 122 may obtain sensing capability of a sensing UE via a sensing registration procedure. This will be described with reference to Fig. 5.
  • Fig. 5 illustrates a signaling diagram illustrating an example sensing registration procedure 500 in accordance with aspects of the present disclosure.
  • the procedure 500 may involve the UE 104 (such as the first UE 104-1 or the second UE 104-2) , the base station 102, the AMF 120 and the SF 122 in Fig. 1B.
  • the UE 104 performs a sensing registration towards the SF 122 via the AMF 120.
  • the SF 122 may be a standalone NF or co-located with LMF (which is not shown) .
  • the UE 104 transmits 510 an UL NAS message towards the AMF 120.
  • the UL NAS message comprises an ID of the UE 104 (also referred to as UE ID for brevity) and a sensing registration request message.
  • the UE ID may be SUPI, GPSI, 5G-GUTI, or 5G-S-TMSI. We take SUPI as the UE ID as an example.
  • the UE 104 may comprise sensing capability information in the sensing registration request message.
  • the sensing registration request message may comprise at least one of the following: the supported sensing mode, supported accuracy of sensing, confidence level, sensing resolution, false alarm probability, missed detection probability, refreshing rate, max sensing service latency, user plane connection supported indicator, supported sensing mode, user plane connection supported indicator (or CP/UP support indicator) , Tx/Rx support indicator (or supported sensing mode) , or non-3GPP sensing support indicator.
  • the Tx/Rx support indicator indicates whether the UE 104 can work as a sensing Tx, or a sensing Rx, or both of a sensing Tx and sensing Rx.
  • the CP/UP support indicator indicates whether the UE 104 supports CP based sensing measurement report or UP based sensing measurement report or both.
  • the UE ID may also be contained in the sensing registration request message.
  • the UE 104 transmits an UL RRC message which comprises the UL NAS message as the payload container to the base station 102.
  • the base station 102 identifies the UL NAS message based on the payload container type and forwards the UL NAS message towards the AMF 120 by using RAN UE NGAP ID and/or the AMF UE NGAP ID (which are used to identify the UE 104 by the base station 102 or the AMF 120 over NG interface) .
  • the base station 102 has the mapping between RAN/AMF UE NGAP ID and C-RNTI (which is used by the base station 102 to identify the UE 104 over air interface) .
  • the AMF 120 has the mapping between RAN/AMF UE NGAP ID and UE ID (e.g., SUPI) . It is assumed that a new payload container type, e.g., sensing message container is defined for the UL NAS message.
  • the AMF 120 determines the container comprises sensing message based on payload container type. Then, the AMF 120 selects 520 an SF based on e.g., the UE location, the SF load and so on. It is assumed that the AMF 120 has been configured (e.g., by OAM or PLMN) with the SF information, e.g., the SF ID, IP address or FQDN of the SF, the serving area of the SF and so on. Alternatively, it is assumed that the SF registered at NEF by proving the SF information. The AMF 120 may request for the SF information from NEF. And NEF will determine the serving area of the AMF 120 and find at least one corresponding SF. Then NEF will provide the AMF 120 the SF information.
  • the SF information e.g., the UE location, the SF load and so on. It is assumed that the AMF 120 has been configured (e.g., by OAM or PLMN) with the SF information, e.
  • the AMF 120 transmits 530 UE ID and the sensing registration request message towards the selected SF (such as the SF 122) .
  • the SF 122 is able to know the sensing UE located in its serving area.
  • the SF 122 obtains UE ID (e.g., SUPI) from the sensing registration request message or from the AMF 120.
  • UE ID e.g., SUPI
  • the SF 122 is able to select the appropriate sensing UE based on the sensing capability information provided by UE during the sensing registration procedure.
  • the SF 122 transmits 540 UE ID and sensing registration response message to the AMF 120.
  • the AMF 120 forwards 550 the sensing registration response message towards the UE 104 based on UE ID. That is, the AMF 120 translates UE ID into the AMF/RAN UE NGAP ID. The AMF 120 transmits the sensing registration response message and the AMF/RAN UE NGAP ID to the base station 102 serving the UE 104. And the base station 102 translates the AMF/RAN UE NGAP ID into C-RNTI. The base station 102 then forwards the sensing registration response message towards the UE 104 based on C-RNTI.
  • Fig. 6 illustrates an example of a device 600 that supports sidelink based sensing in accordance with aspects of the present disclosure.
  • the device 600 may be an example of a network entity 102, a UE 104 or a first apparatus as described herein.
  • the device 600 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 600 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 602, a memory 604, a transceiver 606, and, optionally, an I/O controller 608. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • the processor 602, the memory 604, the transceiver 606, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 602, the memory 604, the transceiver 606, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 602, the memory 604, the transceiver 606, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 602 and the memory 604 coupled with the processor 602 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604) .
  • the processor 602 may support wireless communication at the device 600 in accordance with examples as disclosed herein.
  • the processor 602 may be configured to operable to support a means for performing the following: receiving a first sensing service request at a first UE from a first apparatus or a base station, the first sensing service request comprising at least first information about a sensing task; and transmitting second information about the sensing task via sidelink.
  • the processor 602 may be configured to operable to support a means for performing the following: receiving a second sensing service request at a second UE from a first apparatus or a base station, the second sensing service request comprising at least first information about a sensing task; receiving second information about the sensing task via sidelink from a first UE; and based on determining that the first information is identical to the second information, receiving a reflected signal associated with a sensing signal.
  • the processor 602 may be configured to operable to support a means for performing the following: receiving a sensing service request at a first apparatus from a sensing service consumer; 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 the at least one second UE, the sensing service request comprising at least first information about a sensing task.
  • the processor 602 may be configured to operable to support a means for performing the following: transmitting, from a base station to a second apparatus, a request for translating a first type of IDs of a first UE and at least one second UE into a second type of IDs of the first UE and the at least one second UE, the second type of IDs being recognizable by the base station; and receiving the second type of IDs from the second apparatus.
  • the processor 602 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 602 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 602.
  • the processor 602 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 604) to cause the device 600 to perform various functions of the present disclosure.
  • the memory 604 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 602 cause the device 600 to perform 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.
  • the code may not be directly executable by the processor 602 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 604 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 608 may manage input and output signals for the device 600.
  • the I/O controller 608 may also manage peripherals not integrated into the device M02.
  • the I/O controller 608 may represent a physical connection or port to an external peripheral.
  • the I/O controller 608 may utilize an operating system such as or another known operating system.
  • the I/O controller 608 may be implemented as part of a processor, such as the processor 606.
  • a user may interact with the device 600 via the I/O controller 608 or via hardware components controlled by the I/O controller 608.
  • the device 600 may include a single antenna 610. However, in some other implementations, the device 600 may have more than one antenna 610 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 606 may communicate bi-directionally, via the one or more antennas 610, wired, or wireless links as described herein.
  • the transceiver 606 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 606 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 610 for transmission, and to demodulate packets received from the one or more antennas 610.
  • the transceiver 606 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit 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 like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) .
  • the transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmit chain may also include one or more antennas 610 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 610 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • Fig. 7 illustrates an example of a processor 700 that supports sidelink based sensing in accordance with aspects of the present disclosure.
  • the processor 700 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 700 may include a controller 702 configured to perform various operations in accordance with examples as described herein.
  • the processor 700 may optionally include at least one memory 704, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 700 may optionally include one or more arithmetic-logic units (ALUs) 700.
  • ALUs arithmetic-logic units
  • the processor 700 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • the processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the 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) , and others) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • the controller 702 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein.
  • the controller 702 may operate as a control unit of the processor 700, generating control signals that manage the operation of various components of the processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 702 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 704 and determine subsequent instruction (s) to be executed to cause the processor 700 to support various operations in accordance with examples as described herein.
  • the controller 702 may be configured to track memory address of instructions associated with the memory 704.
  • the controller 702 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 702 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein.
  • the controller 702 may be configured to manage flow of data within the processor 700.
  • the controller 702 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 700.
  • ALUs arithmetic logic units
  • the memory 704 may include one or more caches (e.g., memory local to or included in the processor 700 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 704 may reside within or on a processor chipset (e.g., local to the processor 700) . In some other implementations, the memory 704 may reside external to the processor chipset (e.g., remote to the processor 700) .
  • caches e.g., memory local to or included in the processor 700 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 704 may reside within or on a processor chipset (e.g., local to the processor 700) . In some other implementations, the memory 704 may reside external to the processor chipset (e.g., remote to the processor 700) .
  • the memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 700, cause the processor 700 to perform 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.
  • the controller 702 and/or the processor 700 may be configured to execute computer-readable instructions stored in the memory 704 to cause the processor 700 to perform various functions.
  • the processor 700 and/or the controller 702 may be coupled with or to the memory 704, the processor 700, the controller 702, and the memory 704 may be configured to perform various functions described herein.
  • the processor 700 may include multiple processors and the memory 704 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
  • the one or more ALUs 700 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 700 may reside within or on a processor chipset (e.g., the processor 700) .
  • the one or more ALUs 700 may reside external to the processor chipset (e.g., the processor 700) .
  • One or more ALUs 700 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 700 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 700 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 700 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 700 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 700 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 700 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 700 may be configured to or operable to support a means for performing the following: receiving a first sensing service request at a first UE from a first apparatus or a base station, the first sensing service request comprising at least first information about a sensing task; and transmitting second information about the sensing task via sidelink.
  • the processor 700 may be configured to operable to support a means for performing the following: receiving a second sensing service request at a second UE from a first apparatus or a base station, the second sensing service request comprising at least first information about a sensing task; receiving second information about the sensing task via sidelink from a first UE; and based on determining that the first information is identical to the second information, receiving a reflected signal associated with a sensing signal.
  • the processor 700 may be configured to operable to support a means for performing the following: receiving a sensing service request at a first apparatus from a sensing service consumer; 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 the at least one second UE, the sensing service request comprising at least first information about a sensing task.
  • the processor 700 may be configured to operable to support a means for performing the following: transmitting, from a base station to a second apparatus, a request for translating a first type of IDs of a first UE and at least one second UE into a second type of IDs of the first UE and the at least one second UE, the second type of IDs being recognizable by the base station; and receiving the second type of IDs from the second apparatus.
  • Fig. 8 illustrates a flowchart of a method 800 that supports sidelink based sensing in accordance with aspects of the present disclosure.
  • the operations of the method 800 may be implemented by a device or its components as described herein.
  • the operations of the method 8 may be performed by a first UE 104-1 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a first sensing service request at a first UE from a first apparatus or a base station, the first sensing service request comprising at least first information about a sensing task.
  • the operations of 810 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 810 may be performed by a device as described with reference to Fig. 1A, 1B or 1C.
  • the method may include transmitting second information about the sensing task via sidelink.
  • the operations of 820 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 820 may be performed by a device as described with reference to Fig. 1A, 1B or 1C.
  • Fig. 9 illustrates a flowchart of a method 900 that supports sidelink based sensing in accordance with aspects of the present disclosure.
  • the operations of the method 900 may be implemented by a device or its components as described herein.
  • the operations of the method 9 may be performed by a second UE 104-1 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a second sensing service request at a second UE from a first apparatus or a base station, the second sensing service request comprising at least first information about a sensing task.
  • the operations of 910 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 910 may be performed by a device as described with reference to Fig. 1A, 1B or 1C.
  • the method may include receiving second information about the sensing task via sidelink from a first UE.
  • the operations of 920 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 920 may be performed by a device as described with reference to Fig. 1A, 1B or 1C.
  • the method may include receiving a reflected signal associated with a sensing signal based on determining that the first information is identical to the second information.
  • the operations of 930 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 930 may be performed by a device as described with reference to Fig. 1A, 1B or 1C.
  • Fig. 10 illustrates a flowchart of a method 1000 that supports sidelink based sensing in accordance with aspects of the present disclosure.
  • the operations of the method 1000 may be implemented by a device or its components as described herein.
  • the operations of the method 10 may be performed by a first apparatus as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a sensing service request at a first apparatus from a sensing service consumer.
  • the operations of 1010 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1010 may be performed by a device as described with reference to Fig. 1A, 1B or 1C.
  • the method may include 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.
  • the operations of 1020 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1020 may be performed by a device as described with reference to Fig. 1A, 1B or 1C.
  • the method may include providing the sensing service request to the first UE and the at least one second UE, the sensing service request comprising at least first information about a sensing task.
  • the operations of 1030 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1030 may be performed by a device as described with reference to Fig. 1A, 1B or 1C.
  • Fig. 11 illustrates a flowchart of a method 1100 that supports sidelink based sensing in accordance with aspects of the present disclosure.
  • the operations of the method 1100 may be implemented by a device or its components as described herein.
  • the operations of the method 11 may be performed by a second UE 104-1 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting, from a base station to a second apparatus, a request for translating a first type of IDs of a first UE and at least one second UE into a second type of IDs of the first UE and the at least one second UE, the second type of IDs being recognizable by the base station.
  • the operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1110 may be performed by a device as described with reference to Fig. 1A, 1B or 1C.
  • the method may include receiving the second type of IDs from the second apparatus.
  • the operations of 1120 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1120 may be performed by a device as described with reference to Fig. 1A, 1B or 1C.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a list of items indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) .
  • the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure.
  • the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.
  • a “set” may include one or more elements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention divulgue des UE, un appareil, une station de base et des procédés pour la détection basée sur la liaison latérale. Selon un aspect, un premier UE reçoit une première demande de service de détection depuis un premier appareil ou une station de base. La première demande de service de détection comprend au moins des premières informations concernant une tâche de détection. À son tour, le premier UE transmet des secondes informations concernant la tâche de détection par l'intermédiaire d'une liaison latérale.
PCT/CN2023/118477 2023-09-13 2023-09-13 Détection basée sur la liaison latérale Pending WO2024119942A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/118477 WO2024119942A1 (fr) 2023-09-13 2023-09-13 Détection basée sur la liaison latérale

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/118477 WO2024119942A1 (fr) 2023-09-13 2023-09-13 Détection basée sur la liaison latérale

Publications (1)

Publication Number Publication Date
WO2024119942A1 true WO2024119942A1 (fr) 2024-06-13

Family

ID=91378507

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/118477 Pending WO2024119942A1 (fr) 2023-09-13 2023-09-13 Détection basée sur la liaison latérale

Country Status (1)

Country Link
WO (1) WO2024119942A1 (fr)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220014901A1 (en) * 2019-04-30 2022-01-13 Fujitsu Limited Method and apparatus for identifying user equipment capability in sidelink transmission
US20220141897A1 (en) * 2019-08-15 2022-05-05 Lg Electronics Inc. Allocation of lower and upper identifiers for sidelink transmission
WO2022133867A1 (fr) * 2020-12-24 2022-06-30 Huawei Technologies Co., Ltd. Systèmes, procédés et appareil de détection dans des réseaux de communication sans fil
CN115104375A (zh) * 2020-02-14 2022-09-23 高通股份有限公司 用于新无线电第二层中继的技术
US20220346180A1 (en) * 2021-04-22 2022-10-27 FG Innovation Company Limited Methods and apparatus for partial sensing under sidelink discontinuous reception mechanisms
US20220377725A1 (en) * 2019-10-17 2022-11-24 Lg Electronics Inc. Method and apparatus for performing sensing for sidelink communication in nr v2x
US20230007727A1 (en) * 2020-03-10 2023-01-05 Huawei Technologies Co., Ltd. Wireless communication method and communication apparatus
US20230066448A1 (en) * 2020-01-21 2023-03-02 FG Innovation Company Limited Method and user equipment for sidelink packet exchange operation
US20230092224A1 (en) * 2020-05-22 2023-03-23 Fraunhofer-Gesellschaft Zur Foerderung Der Angewandten Forschung E.V. Cooperative Sensing for Sidelink Communication
US20230171020A1 (en) * 2021-11-30 2023-06-01 Lenovo (Singapore) Pte. Ltd. Sensing reference signal adjustments for user equipment participation

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220014901A1 (en) * 2019-04-30 2022-01-13 Fujitsu Limited Method and apparatus for identifying user equipment capability in sidelink transmission
US20220141897A1 (en) * 2019-08-15 2022-05-05 Lg Electronics Inc. Allocation of lower and upper identifiers for sidelink transmission
US20220377725A1 (en) * 2019-10-17 2022-11-24 Lg Electronics Inc. Method and apparatus for performing sensing for sidelink communication in nr v2x
US20230066448A1 (en) * 2020-01-21 2023-03-02 FG Innovation Company Limited Method and user equipment for sidelink packet exchange operation
CN115104375A (zh) * 2020-02-14 2022-09-23 高通股份有限公司 用于新无线电第二层中继的技术
US20230007727A1 (en) * 2020-03-10 2023-01-05 Huawei Technologies Co., Ltd. Wireless communication method and communication apparatus
US20230092224A1 (en) * 2020-05-22 2023-03-23 Fraunhofer-Gesellschaft Zur Foerderung Der Angewandten Forschung E.V. Cooperative Sensing for Sidelink Communication
WO2022133867A1 (fr) * 2020-12-24 2022-06-30 Huawei Technologies Co., Ltd. Systèmes, procédés et appareil de détection dans des réseaux de communication sans fil
US20220346180A1 (en) * 2021-04-22 2022-10-27 FG Innovation Company Limited Methods and apparatus for partial sensing under sidelink discontinuous reception mechanisms
US20230171020A1 (en) * 2021-11-30 2023-06-01 Lenovo (Singapore) Pte. Ltd. Sensing reference signal adjustments for user equipment participation

Similar Documents

Publication Publication Date Title
WO2024159793A1 (fr) Dispositifs et procédés pour des opérations de stockage et de transfert
WO2025145681A1 (fr) Évitement de collision d'id temporaires d'as pour dispositifs aiot
WO2024239690A1 (fr) Procédés de gestion d'une tâche informatique infructueuse
WO2024093326A1 (fr) Détection d'échange de données
WO2024146185A1 (fr) Ltm basé sur une condition
WO2024119942A1 (fr) Détection basée sur la liaison latérale
WO2024148819A1 (fr) Radiomessagerie pour détection d'ue
WO2024169218A1 (fr) Accès aléatoire pour détection
WO2025241554A1 (fr) Détection de mobilité d'objet
WO2025161467A1 (fr) Relais de détection
WO2024093325A1 (fr) Transfert de contexte d'ue lors de la commutation d'une fonction de détection
WO2024234701A1 (fr) Collecte de données assistée par amf pour une lmf
WO2024093414A1 (fr) Mesure de positionnement de phase de porteuse
WO2024207740A1 (fr) Mobilité déclenchée de couche 1 ou de couche 2
WO2025107612A1 (fr) Localisation de dispositifs de l'internet des objets ambiants
WO2025156295A1 (fr) Continuité de service de multidiffusion ou de diffusion
WO2024187813A1 (fr) Mécanisme de gestion de collision de détection
WO2025002480A1 (fr) Transmission de signal de détection
WO2025218260A1 (fr) Gestion de mobilité d'ue de détection
WO2025107718A1 (fr) Prédiction de défaillance de liaison radio
WO2025097794A1 (fr) Acquisition de sib dans une communication relais
WO2024093275A1 (fr) Groupe d'états indicateurs de configuration de transmission
WO2025060464A1 (fr) Procédé et appareil de prise en charge d'applications d'intelligence artificielle (ia) dans des communications sans fil
WO2025107659A1 (fr) Détection coopérative
WO2024179093A1 (fr) Apprentissage fédéré assisté

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23899525

Country of ref document: EP

Kind code of ref document: A1