[go: up one dir, main page]

WO2024169218A1 - Accès aléatoire pour détection - Google Patents

Accès aléatoire pour détection Download PDF

Info

Publication number
WO2024169218A1
WO2024169218A1 PCT/CN2023/125788 CN2023125788W WO2024169218A1 WO 2024169218 A1 WO2024169218 A1 WO 2024169218A1 CN 2023125788 W CN2023125788 W CN 2023125788W WO 2024169218 A1 WO2024169218 A1 WO 2024169218A1
Authority
WO
WIPO (PCT)
Prior art keywords
sensing
random access
network entity
sensing signal
processor
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/125788
Other languages
English (en)
Inventor
Jianfeng Wang
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/125788 priority Critical patent/WO2024169218A1/fr
Publication of WO2024169218A1 publication Critical patent/WO2024169218A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Definitions

  • the present disclosure relates to wireless communications, and more specifically to a user equipment (UE) , a network entity, a processor for wireless communication, methods, and a computer readable medium for random access for sensing.
  • UE user equipment
  • 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
  • Radio information obtained during signal processing can be used to detect environmental changes caused by motion of objects and people, which is termed as radio sensing or wireless sensing, similar with radar.
  • Some examples of ubiquitous radio sensing services are safe autonomous vehicles, environment mapping to improve positioning accuracy and enable environment related applications and real-time monitoring for intrusion detection, etc.
  • Introducing sensing capability into cellular wireless communication system has the benefit of sharing the same spectrum and infrastructure especially on the industry with both communication and sensing, which is one of the promising techniques in next generation radio access network (RAN) , e.g., beyond 5G (B5G) /6G.
  • RAN next generation radio access network
  • the present disclosure relates to a user equipment (UE) , a network entity, a processor for wireless communication, methods, and a computer readable medium for reporting of beam measurements.
  • UE user equipment
  • Embodiments of the disclosure can support UE in an idle/inactive state to request sensing signals from network using a random access procedure without transition to a connected state.
  • a UE comprising a processor; and a transceiver coupled to the processor, wherein the processor is configured to: transmit, via the transceiver, a random access preamble associated with sensing trigger to a network entity; receive, via the transceiver, a sensing signal configuration from the network entity; and receive, via the transceiver, sensing signals from the network entity based on the sensing signal configuration.
  • a network entity comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver, a random access preamble associated with sensing trigger from a user equipment (UE) ; transmit, via the transceiver, a sensing signal configuration to the UE; and transmit, via the transceiver, sensing signals to the UE based on the sensing signal configuration.
  • UE user equipment
  • a processor for wireless communication comprise at least one memory; and a controller coupled with the at least one memory and configured to cause the controller to: transmit a random access preamble associated with sensing trigger to a network entity; receive a sensing signal configuration from the network entity; and receive sensing signals from the network entity based on the sensing signal configuration.
  • a user equipment UE
  • the method comprising: transmitting a random access preamble associated with sensing trigger to a network entity; receiving a sensing signal configuration from the network entity; and receiving sensing signals from the network entity based on the sensing signal configuration.
  • a network entity comprising: receiving a random access preamble associated with sensing trigger from a user equipment (UE) ; transmitting a sensing signal configuration to the UE; and transmitting sensing signals to the UE based on the sensing signal configuration.
  • UE user equipment
  • a computer readable medium having instructions stored thereon, the instructions, when executed by a processor of an apparatus, causing the apparatus to perform the method according to the fourth or the fifth aspect of the disclosure.
  • the UE may receive, before transmission of the random access preamble, a system information (SI) message from the network entity, wherein the SI message indicates at least one random access preamble and corresponding occasion associated with a system information block (SIB) for sensing trigger.
  • SI system information
  • the UE and the network entity described herein may transmit the random access preamble for sensing trigger by:selecting one of the at least one random access preamble; and transmitting the selected random access preamble on the corresponding occasion.
  • the UE and the network entity described herein may receive the sensing signal configuration by: receiving, from the network entity, a SIB associated with the random access preamble and the corresponding occasion, wherein the SIB comprises the sensing signal configuration.
  • the UE may receive a SIB comprising a sensing functionality from the network entity, wherein the sensing functionality indicates at least one of the following: sensing applicable scenarios, or supportive sensing signal configurations.
  • the SIB is received in response to the random access preamble being successfully detected by the network entity.
  • the sensing applicable scenarios include at least one of: information about whether sensing is supported currently; or information about supportive UE capability.
  • the UE may receive the sensing signal configuration by: transmitting, based on the sensing functionality, a request including sensing requirements to the network entity; and receiving, from the network entity, the sensing signal configuration determined based on the sensing requirements.
  • the UE and the network entity described herein may be transmitted via Msg3 of a Type-1 random access procedure, and the sensing signal configuration may be received via Msg4 of the Type-1 random access procedure.
  • the request may be transmitted together with the random access preamble via MsgA of a Type-2 random access procedure, and the sensing signal configuration may be received together with the sensing signal configuration via MsgB of the Type-2 random access procedure.
  • the sensing signal configuration may comprise at least one of the following: transmission window duration; transmission periodicity; or a transmission offset.
  • the sensing signal configuration may further comprises at least one of the following: time and frequency resources; antenna ports settings; transmit power; or sensing signal format.
  • the network entity may transmit, before reception of the random access preamble, a system information (SI) message to the UE, wherein the SI message indicates at least one random access preamble and corresponding occasion associated with a system information block (SIB) for sensing trigger.
  • SI system information
  • the network entity may transmit the sensing signal configuration by: transmitting, to the UE, a SIB associated with the random access preamble and the corresponding occasion, wherein the SIB comprises the sensing signal configuration.
  • the network entity may transmit a SIB comprising a sensing functionality to the UE, wherein the sensing functionality indicates at least one of the following: sensing applicable scenarios, or supportive sensing signal configurations.
  • the network entity may transmit the SIB based on successful detection of the random access preamble.
  • the network entity may receive the sensing signal configuration by: receiving a request including sensing requirements from the UE; determine the sensing signal configuration based on the sensing requirements; and transmitting the sensing signal configuration to the UE.
  • FIG. 1 illustrates an example of a wireless communications system in which some embodiments of the present disclosure can be implemented.
  • FIG. 2A illustrates alternatives to enable wireless sensing.
  • FIG. 2B illustrates UE-based sensing with assistance from network.
  • FIG. 3 illustrates an example of a process flow of random access for sensing in accordance with some example embodiments of the present disclosure.
  • FIG. 4 illustrates a schematic diagram of a process for delivering sensing signal configurations in system information (SI) in accordance with some example embodiments of the present disclosure.
  • FIG. 5 illustrates a schematic diagram of a process for delivering sensing signal configurations with dedicated signaling in accordance with some example embodiments of the present disclosure.
  • FIG. 6 illustrates a schematic diagram of sensing signal transmission configurations in time domain in accordance with some example embodiments of the present disclosure.
  • FIG. 7 illustrates another example of a process flow of random access for sensing in accordance with some example embodiments of the present disclosure.
  • FIG. 8 illustrates an example of a device that is suitable for implementing some embodiments of the present disclosure.
  • FIG. 9 illustrates an example of a processor that is suitable for implementing some embodiments of the present disclosure.
  • FIG. 10 illustrates a flowchart of a method that performed by a user equipment in accordance with aspects of the present disclosure.
  • FIG. 11 illustrates a flowchart of a method that performed by a network entity in accordance with aspects of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, 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 embodiments whether or not explicitly described.
  • first and second 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 embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms. In some examples, values, procedures, or apparatuses are referred to as “best, ” “lowest, ” “highest, ” “minimum, ” “maximum, ” or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • the term “includes” and its variants are to be read as open terms that mean “includes, but is not limited to. ”
  • the term “based on” is to be read as “based at least in part on. ”
  • the term “one embodiment” and “an embodiment” are to be read as “at least one embodiment. ”
  • the term “another embodiment” is to be read as “at least one other embodiment. ”
  • the use of an expression such as “A and/or B” can mean either “only A” or “only B” or “both A and B. ”
  • Other definitions, explicit and implicit, may be included below.
  • UE can be in different radio resource control (RRC) states, including RRC_idle, RRC_inactive or RRC_connected.
  • RRC radio resource control
  • the random access procedure defined in NR is not only used for a device to initially access the network from the idle/inactive state, but also to assist handover, to reestablish uplink synchronization and for system information (SI) request.
  • SI system information
  • the UE accesses the new cell by first carrying out a random access to establish synchronization and a radio resource control (RRC) connection to the cell.
  • RRC radio resource control
  • the synchronization to the network may be lost. If the network detects such a loss of uplink synchronization it may trigger a random access from the device by means of a so-called PDCCH order.
  • the system information can be provided to a device in form of SI messages, which could be broadcast and thus always be available also for devices in idle/inactive state.
  • SI messages could be broadcast and thus always be available also for devices in idle/inactive state.
  • a device in idle/inactive state has to explicitly request its transmission by means of an SI request.
  • some basic information can be delivered without switching into the connected state.
  • UE-based sensing where UE receives sensing signals from network (e.g. gNB) for measurements, if only sensing signals are needed, it would be not necessary for the UE to switch into connected state to avoid large latency and overhead.
  • network e.g. gNB
  • both downlink and uplink synchronization should be obtained via receiving downlink synchronization signals, system information and random access procedure.
  • UE may transmit a random access preamble associated with sensing trigger to a network entity.
  • the network entity may transmit a sensing signal configuration to the UE, thereby aligning sensing signals between the UE and the network entity. Afterwards, the network entity transmits and the UE receives the sensing signals based on the sensing signal configuration.
  • FIG. 1 illustrates an example of a wireless communications system 100 in which some embodiments of the present disclosure can be implemented.
  • the wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network 106, and a packet data network 108.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network.
  • LTE-A LTE-Advanced
  • the wireless communications system 100 may be a 5G network, such as an NR network.
  • the wireless communications system 100 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
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 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 100.
  • 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.
  • 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 in form of a satellite can directly communicate to UE 104 using NR/LTE Uu interface.
  • the satellite may be a transparent satellite or a regenerative satellite.
  • a base station on earth may communicate with a UE via the satellite.
  • the base station may be on board and directly communicate with the UE.
  • 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 100.
  • 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 100.
  • a UE 104 may be mobile in the wireless communications system 100.
  • 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 100.
  • 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 100 (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 100, and a numerology may include a subcarrier spacing and a cyclic prefix.
  • 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 100.
  • 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 100 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) .
  • 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
  • FR5 114.25 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) .
  • Alt. 1-A and Alt. 3-A are more or less about implementation issues.
  • Alt. 1-B, Alt. 3-B and Alt. 2 there should be some enhancements on the air interface, i.e., Uu or PC5 interface.
  • the present disclosure focuses on Alt. 2-B, where UEs do sensing with the assistance from network, which means that the serving network entity needs to send downlink signals, i.e., sensing signals, to UE to assist sensing as illustrated in FIG. 2B.
  • FIG. 3 illustrates an example of a process flow of random access for sensing in accordance with some example embodiments of the present disclosure.
  • the process flow 300 may involve a UE 301 and a network entity (e.g. a base station, such as gNB) 302.
  • the process flow 300 may be applied to the wireless communications system 100 with reference to FIG. 1, for example, the UE 301 may be any of UEs 104, and the network entity 302 may be any of the network entities 102. It would be appreciated that the process flow 300 may be applied to other communication scenarios.
  • the UE 310 may transmit, to the network entity 302, a random access preamble 315 associated with sensing trigger to a network entity. Accordingly, at 320, the network entity 302 may receive the random access preamble 315 associated with sensing trigger from the UE 301.
  • the network entity 302 may indicate the UE 301 with random access preamble (s) and corresponding occasion (s) which is associated with sensing trigger.
  • the network entity 302 may broadcast a system information (SI) message, for example, System Information Block 1 (SIB1) , periodically to indicate the preamble and occasion to assist random access from UE 301.
  • SIB1 System Information Block 1
  • the UE 301 obtain the knowledge about which preamble (s) is associated with sensing, and may transmit the indicated preamble on the corresponding occasion to request transmission of sensing signals. Accordingly, upon successful detection of the random access preamble 315, the network entity 320 would know that the UE is requesting transmission of sensing signals.
  • the network entity 302 may transmit a sensing signal configuration 335 to the UE 301. Accordingly, at 340, the UE 301 may receive the sensing signal configuration 335 from the network entity 302.
  • the sensing signal configuration 335 may indicate resources in time domain and/or frequency domain used for transmission of sensing signals. Details of the sensing signal configuration 335 will be further described with reference to FIG. 6.
  • the network entity 302 may transmit sensing signals 355 based on the sensing signal configuration 335 to the UE 301.
  • the UE 301 may receive the sensing signals 355 from the network entity 302.
  • the UE 301 may perform sensing operations, e.g., channel estimation to obtain the channel state information (CSI) , analyze the CSI to obtain the Doppler or delay to estimate the velocity, position information, or other sensing services.
  • sensing operations e.g., channel estimation to obtain the channel state information (CSI)
  • CSI channel state information
  • the sensing signal configuration 335 may be delivered to the UE 301 in system information (SI) , or alternatively, in dedicated signaling.
  • SI system information
  • FIG. 4 illustrates a schematic diagram of a process for delivering sensing signal configurations in system information (SI) in accordance with some example embodiments of the present disclosure.
  • SI system information
  • FIG. 4 the association between broadcast system information, random access (RA) resource (i.e., preamble, RA occasion (time and frequency resources) ) and sensing signal transmission is illustrated, which denotes the transmission (uplink transmission) and receiving (downlink receiving) instances of UE.
  • RA random access
  • the system information broadcasted by network e.g. gNB periodically to indicate the basic information to assist random access from UE.
  • the system information may be carried in an SI message, for example, System Information Block 1 (SIB1) .
  • SIB1 System Information Block 1
  • the system information may indicate associated RA preambles/occasions for the system information (SI) request on the sensing signal configurations, which may be transmitted in predefined system information blocks (SIBs) .
  • SIBs system information blocks
  • the SI message may indicate the association between RA preambles/occasions between the predefined SIBs.
  • the UE may select one or more of the associated RA preambles and corresponding occasions indicated in SIB1 to initiate the random access procedure to request a corresponding SI.
  • the UE may select the preamble and occasion for transmission based on network condition, UE capability, sensing requirements like quality of service (QoS) , etc. from the indicated preambles and occasions. Then, the UE may transmit the selected random access preamble on the corresponding occasion.
  • QoS quality of service
  • a random access response (RAR) as acknowledgement would be responded to the UE with some additional information, e.g., time advance information to adjust the uplink timing if needed. If the UE does not receive RAR, the UE may re-transmit the preamble, trying to access again and trigger sensing signal transmission.
  • RAR random access response
  • the gNB may send the sensing signal configuration, accordingly, which can be broadcast to UEs in the cell or unicast to the requested UE.
  • a new SIB may be defined, e.g., SIBx, or senSIB, which can be indicated to UE as being associated with a set of random access preamble/occasions within SIB1 for UE to request.
  • the gNB may transmit the sensing signal configuration via a SIB corresponding to the received preamble/occasion from the UE.
  • the gNB may transmit the sensing signals according to the configuration, either broadcast or unicast.
  • the requesting UE may receive the sensing signals for sensing operations, e.g., do channel estimation to obtain the channel state information (CSI) , analyze the CSI to obtain the Doppler or delay to estimate the velocity or position, and the like.
  • CSI channel state information
  • the UE can obtain the expected sensing results based on the received sensing signals pre-configured by gNB, whose values are determined by the sensing service via dedicated function, e.g., Sensing Function, via core network.
  • the pre-configured broadcast sensing signals in this alternative are beneficial for the environment monitoring and reconstruction sensing services.
  • FIG. 5 illustrates a schematic diagram of a process for delivering sensing signal configurations with dedicated signaling in accordance with some example embodiments of the present disclosure.
  • the association between broadcast system information, random access resource (i.e., time and frequency resources) , dedicate signaling to request and configurations on sensing signals and sensing signal transmission is illustrated.
  • the system information may be carried in an SI message, for example, System Information Block 1 (SIB1) .
  • SIB1 System Information Block 1
  • the system information may indicate associated RA preambles/occasions for the system information (SI) request on the sensing signal configurations, which will be transmitted in dedicated signaling described below.
  • SI System Information Block 1
  • the associated RA preamble (s) /occasion (s) indicated in SIB1 may be selected to initiate the random access procedure to request the corresponding SI, which is also similar as that described with reference to FIG. 4. If the preambles is successfully detected by the gNB, an RAR as the acknowledgement would be responded to the UE with some additional information, e.g., time advance information to adjust the uplink timing if needed. If not receiving RAR, the UE may re-transmit the preamble, trying to access again.
  • the gNB transmits system information associated with the RA preamble and occasion to the UE.
  • new SIB may be defined, e.g., SIBx, or senSIB, which can be indicated as being associated with a set of random access preamble/occasions within SIB1 for UE to request.
  • the supportive sensing functionality of the RAN may be indicated to the requesting UE.
  • the UE can obtain the potential sensing signal configurations via dedicated signaling.
  • the concept of sensing functionality may be defined as the sensing capability within RAN, which may include the applicable scenarios and supportive sensing signal configurations.
  • the sensing applicable scenarios may include information about whether the sensing is supported or not currently, considering the load of communication resources. Additionally or alternatively, the sensing applicable scenarios may include information about supportive UE capability, considering the type of sensing signals. In some embodiments, the supportive sensing signal configurations may be used to indicate the potential sensing signal configurations, which can be regarded as a set of parameters which will be explained with reference to FIG. 6.
  • the UE may be need to request the sensing signals with expected requirements.
  • Dedicated signaling may be used for the request and response for the sensing configuration.
  • UE may decide whether to trigger the request for the sensing signals transmission. If the condition, for example, the applicable scenarios as indicated in SI, is satisfied, the UE may provide the sensing requirements to gNB, such as the expected resolutions and accuracies of positioning or velocity estimation, successful detection rate, receiving signal power levels and duration.
  • this signaling may be designed as a new RRC signaling, carried in Msg3 of a Type-1 random access procedure (i.e. 4-step RA procedure) .
  • the gNB may determine the sensing signal configuration based on the sensing requirements and transmit the sensing signal configuration to the UE.
  • the gNB may send the requirements to the dedicated function in core network, e.g., the sensing function, where the requirements can be mapped the sensing signal configurations. For example, if higher resolution in time domain is required, the more resources in frequency domain need to be provided; and to obtain better velocity estimation, the resources in time domain need to be provided. Note that the resources allocation for sensing needs to consider the balance between communication resources in practice.
  • the generated configurations can be sent to the UE via gNB. Note that this signaling can be designed as a new RRC signaling, carried in Msg. 4 of the Type-1 random access procedure.
  • the request with sensing requirements and the response of the configurations may be transmitted via different signaling other than signaling of the RA procedure.
  • a UE in RRC_connected state may data transmission resources to request and obtain sensing signal configurations.
  • embodiments of the present disclosure are also applicable to UE in a connected state.
  • the gNB may transmit the sensing signals according to the configuration.
  • the UE accordingly receives the sensing signals for sensing operations, e.g., do channel estimation to obtain the channel state information (CSI) , analyze the CSI to obtain the Doppler or delay to estimate the velocity or position.
  • CSI channel state information
  • the UE can obtain the expected sensing results based on the received sensing signals.
  • the configurations are determined in dedicated function, e.g., Sensing Function, in core network according to the receiving sensing signal request, which is generated by the sensing service.
  • the sensing signals can be more flexible to be beneficial for more kinds of sensing services, e.g., object detection and tracking.
  • the sensing signal configuration may indicate resources of the sensing signals transmitted by the network entity, including time domain resources and frequency domain resources.
  • the sensing signal configuration may be carried in system information as described with reference to FIG. 4, or carried in dedicated signaling, as described with reference to FIG. 4.
  • FIG. 6 illustrates a schematic diagram of sensing signal transmission configurations in time domain in accordance with some example embodiments of the present disclosure.
  • a transmission window duration (T w ) is used to indicate the window duration where the sensing signals will be transmitted.
  • the window may be identified with the starting time, T w, start and end time T w, end .
  • the sensing signal configuration may comprise information about transmission periodicity. This information is used to indicate the periodicity, T p , of the sensing signal transmission in the window.
  • the sensing signal configuration may comprise information about transmission offset, which indicates time difference, Toffset, between the first sensing signal transmission and the window starting time.
  • the resources in the frequency domain may be reserved and indicated in the sensing signal configuration as time and frequency domain resources. This information may be used to indicate the allocated resources in both time and frequency domains, including number of orthogonal frequency division multiplexing (OFDM) symbols, L OS , and number of resource blocks, K RB .
  • OFDM orthogonal frequency division multiplexing
  • L OS number of orthogonal frequency division multiplexing
  • K RB number of resource blocks
  • the sensing signal configuration may further comprise antenna ports settings. If there are multiple ports at gNB, the antenna ports, ⁇ p 0 , p 1 , ..., p n ⁇ , where the sensing signals are transmitted, the corresponding antenna ports settings need to be indicated to UE. Additionally or alternatively, the sensing signal configuration may further comprise transmit power. This information may be used to indicate the transmit power of the sensing signal, P s , to facilitate measurement for UE, such as the path loss calculation. Additionally or alternatively, the sensing signal configuration may further comprise sensing signal format. The information about the sensing signal format may need to be indicated, such as the root index to generate a sequence, length of sequence, and even the type of sequence.
  • the random access procedure to trigger sensing needs to be adjusted to support Type-2 random access procedure (i.e. 2-step RA procedure) , since the embodiments as described above are proposed for the 4-step random access.
  • Type-2 random access procedure i.e. 2-step RA procedure
  • FIG. 7 illustrates another example of a process flow of random access for sensing in accordance with some example embodiments of the present disclosure.
  • the process flow 700 adapted for Type-2 RA procedure is illustrated.
  • the UE 301 receives the system information with sensing functionality indication from the network entity 302.
  • the system information may be SIB 1 transmitted in broadcast by the network entity 302 and indicate dedicated random access preamble (s) /occasion (s) for sensing trigger.
  • the sensing functionality may be similar as that described with reference to FIG. 5.
  • the UE 301 may transmit a dedicated random access preamble/occasion together with the sensing signal request in MsgA, where the sensing signal request may include sensing requirements.
  • the network entity 302 may transmit a random access response (RAR) together with the sensing signal configuration in MsgB.
  • the network entity 302 transmits the sensing signals, and the UE 301 would receive them for sensing operations., e.g., to do channel estimation to obtain the channel state information (CSI) , analyze the CSI to obtain the Doppler or delay to estimate the velocity or position.
  • CSI channel state information
  • the random-access procedures and signalling to support UE-based sensing with assistance from network are proposed, where the UE could be in idle/inactive state without transit to connected state. In this way, large latency and overhead can be reduced, and UE power can be saved.
  • FIG. 8 illustrates an example of a device that is suitable for implementing some embodiments of the present disclosure.
  • the device 800 may be an example of a UE 104 or network entity 102 as described herein.
  • the device 800 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 800 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 802, a memory 804, a transceiver 806, and, optionally, an I/O controller 908. 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) .
  • interfaces e.g., buses
  • the processor 802, the memory 804, the transceiver 806, 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 802, the memory 804, the transceiver 806, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 802, the memory 804, the transceiver 806, 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 802 and the memory 804 coupled with the processor 802 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 802, instructions stored in the memory 804) .
  • the processor 802 may support wireless communication at the device 800 in accordance with examples as disclosed herein.
  • the device 800 may be an example of a UE 104.
  • the processor 802 may be configured to operable to support means for transmitting a random access preamble associated with sensing trigger to a network entity; means for receiving a sensing signal configuration from the network entity; and means for receiving sensing signals from the network entity based on the sensing signal configuration.
  • the device 800 may be an example of a network entity 102, e.g. a network entity.
  • the processor 802 may be configured to operable to support means for receiving a random access preamble associated with sensing trigger from a user equipment (UE) ; means for transmitting a sensing signal configuration to the UE; and means for transmitting sensing signals to the UE based on the sensing signal configuration.
  • UE user equipment
  • the processor 802 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 802 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 802.
  • the processor 802 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 804) to cause the device 800 to perform various functions of the present disclosure.
  • the memory 804 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 802 cause the device 800 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 802 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 804 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 808 may manage input and output signals for the device 800.
  • the I/O controller 808 may also manage peripherals not integrated into the device 800.
  • the I/O controller 808 may represent a physical connection or port to an external peripheral.
  • the I/O controller 808 may utilize an operating system such as or another known operating system.
  • the I/O controller 808 may be implemented as part of a processor, such as the processor 802.
  • a user may interact with the device 800 via the I/O controller 808 or via hardware components controlled by the I/O controller 808.
  • the device 800 may include a single antenna 810. However, in some other implementations, the device 800 may have more than one antenna 810 (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 806 may communicate bi-directionally, via the one or more antennas 810, wired, or wireless links as described herein.
  • the transceiver 806 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 806 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 810 for transmission, and to demodulate packets received from the one or more antennas 810.
  • the transceiver 906 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 810 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 810 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. 9 illustrates an example of a processor 900 is suitable for implementing some embodiments of the present disclosure.
  • the processor 900 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 900 may include a controller 902 configured to perform various operations in accordance with examples as described herein.
  • the processor 900 may optionally include at least one memory 904. Additionally, or alternatively, the processor 900 may optionally include one or more arithmetic-logic units (ALUs) 906.
  • ALUs arithmetic-logic units
  • One or more of 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 900 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 900) 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 902 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 900 to cause the processor 900 to support various operations in accordance with examples as described herein.
  • the controller 902 may operate as a control unit of the processor 900, generating control signals that manage the operation of various components of the processor 900. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 902 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 904 and determine subsequent instruction (s) to be executed to cause the processor 900 to support various operations in accordance with examples as described herein.
  • the controller 902 may be configured to track memory address of instructions associated with the memory 904.
  • the controller 902 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 902 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 900 to cause the processor 900 to support various operations in accordance with examples as described herein.
  • the controller 902 may be configured to manage flow of data within the processor 900.
  • the controller 902 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 900.
  • ALUs arithmetic logic units
  • the memory 904 may include one or more caches (e.g., memory local to or included in the processor 900 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 904 may reside within or on a processor chipset (e.g., local to the processor 900) . In some other implementations, the memory 904 may reside external to the processor chipset (e.g., remote to the processor 900) .
  • caches e.g., memory local to or included in the processor 900 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 904 may reside within or on a processor chipset (e.g., local to the processor 900) . In some other implementations, the memory 904 may reside external to the processor chipset (e.g., remote to the processor 900) .
  • the memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 900, cause the processor 900 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 902 and/or the processor 900 may be configured to execute computer-readable instructions stored in the memory 904 to cause the processor 900 to perform various functions (e.g., functions or tasks supporting transmit power prioritization) .
  • the processor 900 and/or the controller 902 may be coupled with or to the memory 904, the processor 900, the controller 902, and the memory 904 may be configured to perform various functions described herein.
  • the processor 900 may include multiple processors and the memory 904 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 906 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 906 may reside within or on a processor chipset (e.g., the processor 900) .
  • the one or more ALUs 906 may reside external to the processor chipset (e.g., the processor 900) .
  • One or more ALUs 906 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 906 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 906 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 906 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 906 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 906 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 900 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 900 may implemented at a UE 104.
  • the processor 900 may be configured to operable to support means transmitting a random access preamble associated with sensing trigger to a network entity; means for receiving a sensing signal configuration from the network entity; and means for receiving sensing signals from the network entity based on the sensing signal configuration.
  • the processor 900 may implemented at a network entity 102, e.g. a base station.
  • the processor 900 may be configured to operable to support means for receiving a random access preamble associated with sensing trigger from a user equipment (UE) ; means for transmitting a sensing signal configuration to the UE; and means for transmitting sensing signals to the UE based on the sensing signal configuration.
  • UE user equipment
  • FIG. 10 illustrates a flowchart of a method 1000 performed by a UE 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 1100 may be performed by a UE 104 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 a random access preamble associated with sensing trigger to a network entity.
  • 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 UE 104 as described with reference to FIG. 1.
  • the method may include receiving a sensing signal configuration from the network entity.
  • 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 UE 104 as described with reference to FIG. 1.
  • the method may include receiving sensing signals from the network entity based on the sensing signal configuration.
  • 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 UE 104 as described with reference to FIG. 1.
  • FIG. 11 illustrates a flowchart of a method 1100 performed by a network entity 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 1100 may be performed by a network entity 102 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 random access preamble associated with sensing trigger from a user equipment (UE) .
  • UE user equipment
  • 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 network entity 102 as described with reference to FIG. 1.
  • the method may include transmitting a sensing signal configuration to the UE.
  • 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 network entity 102 as described with reference to FIG. 1.
  • the method may include transmitting sensing signals to the UE based on the sensing signal configuration.
  • the operations of 1130 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1130 may be performed by a network entity 102 as described with reference to FIG. 1.
  • 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation concernent un UE, un processeur pour une communication sans fil, une entité de réseau, des procédés et un support lisible par ordinateur pour une association et un mappage entre des ensembles de faisceaux. L'UE transmet un préambule d'accès aléatoire associé à un déclencheur de détection à une entité de réseau. L'UE reçoit en outre une configuration de signal de détection depuis l'entité de réseau. L'UE reçoit en outre des signaux de détection depuis l'entité de réseau sur la base de la configuration du signal de détection. De cette manière, l'UE dans un état au repos/inactif peut demander des signaux de détection depuis un réseau pendant une procédure d'accès aléatoire sans passer dans un état connecté.
PCT/CN2023/125788 2023-10-20 2023-10-20 Accès aléatoire pour détection Pending WO2024169218A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/125788 WO2024169218A1 (fr) 2023-10-20 2023-10-20 Accès aléatoire pour détection

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/125788 WO2024169218A1 (fr) 2023-10-20 2023-10-20 Accès aléatoire pour détection

Publications (1)

Publication Number Publication Date
WO2024169218A1 true WO2024169218A1 (fr) 2024-08-22

Family

ID=92422175

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/125788 Pending WO2024169218A1 (fr) 2023-10-20 2023-10-20 Accès aléatoire pour détection

Country Status (1)

Country Link
WO (1) WO2024169218A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111567133A (zh) * 2018-01-11 2020-08-21 瑞典爱立信有限公司 用户设备、无线电网络节点以及在其中执行的用于处理无线通信网络中的通信的方法
CN112544120A (zh) * 2018-08-08 2021-03-23 高通股份有限公司 随机接入中的退避规程
CN113383605A (zh) * 2019-02-01 2021-09-10 高通股份有限公司 随机接入规程回退
WO2023130428A1 (fr) * 2022-01-10 2023-07-13 Qualcomm Incorporated Techniques de configuration de répétitions de préambule d'accès aléatoire
WO2023155118A1 (fr) * 2022-02-18 2023-08-24 Qualcomm Incorporated Techniques d'allocation dynamique de ressources

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111567133A (zh) * 2018-01-11 2020-08-21 瑞典爱立信有限公司 用户设备、无线电网络节点以及在其中执行的用于处理无线通信网络中的通信的方法
CN112544120A (zh) * 2018-08-08 2021-03-23 高通股份有限公司 随机接入中的退避规程
CN113383605A (zh) * 2019-02-01 2021-09-10 高通股份有限公司 随机接入规程回退
WO2023130428A1 (fr) * 2022-01-10 2023-07-13 Qualcomm Incorporated Techniques de configuration de répétitions de préambule d'accès aléatoire
WO2023155118A1 (fr) * 2022-02-18 2023-08-24 Qualcomm Incorporated Techniques d'allocation dynamique de ressources

Similar Documents

Publication Publication Date Title
WO2024146185A1 (fr) Ltm basé sur une condition
WO2024183312A1 (fr) Procédés et appareils pour des procédures ltm intra-bs et inter-bs
WO2024087745A1 (fr) Procédé et appareil de prise en charge de rapport de temps d'arrivée de rafale (bat)
WO2024169218A1 (fr) Accès aléatoire pour détection
WO2024148819A1 (fr) Radiomessagerie pour détection d'ue
WO2025148422A1 (fr) Procédés et appareils pour prendre en charge une mobilité déclenchée par l1/l2 (ltm) conditionnelle
WO2024230254A1 (fr) Procédé de demande de signal de liaison descendante
WO2024164606A1 (fr) Dispositifs et procédés de communication
WO2024217078A1 (fr) Procédé et appareil pour une indication de réinitialisation de l2 et une indication de ta mesurée par ue dans un scénario ltm
WO2025050684A1 (fr) Procédés et appareils pour une procédure de mobilité déclenchée par l1/l2 (ltm) et procédure de transfert conditionnel (cho)
WO2024098839A1 (fr) Ajout de trajet indirect pour communication u2n
WO2024093414A1 (fr) Mesure de positionnement de phase de porteuse
WO2024093337A1 (fr) Dispositifs et procédés de communication
WO2024179019A1 (fr) Procédé et appareil pour une indication de réinitialisation de l2 et une indication de ta mesurée par ue dans un scénario ltm
WO2025035790A1 (fr) Transmission de données précoce
WO2025145658A1 (fr) Contrôle d'accès d'une cellule ntn
WO2024212567A1 (fr) Transmission de préambule prach déclenchée par une instruction de commutation de cellules
WO2024207740A1 (fr) Mobilité déclenchée de couche 1 ou de couche 2
WO2025152400A1 (fr) Gestion d'informations système
WO2025236750A1 (fr) Transmission en liaison montante
WO2025097900A1 (fr) Gestion d'accès
WO2025145619A1 (fr) Procédé et appareil de prise en charge d'applications d'intelligence artificielle (ia) dans des communications sans fil
WO2025107718A1 (fr) Prédiction de défaillance de liaison radio
WO2025112051A1 (fr) Transmission de signal fonctionnel double
WO2025241554A1 (fr) Détection de mobilité d'objet

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: 23922335

Country of ref document: EP

Kind code of ref document: A1