Managing an indication for sensing in a wireless communications system
Patent Information
- Application Number
- PCT/CN2023/141038
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-12-22
- Publication Date
- 2024-11-14
Smart Images

Figure CN2023141038_14112024_PF_FP_ABST
Abstract
Description
MANAGING AN INDICATION FOR SENSING IN A WIRELESS COMMUNICATIONS SYSTEMTECHNICAL FIELD
[0001] The present disclosure relates to wireless communications, and more specifically to a user equipment (UE) , a network entity (NE) , methods, apparatuses, and computer readable medium for managing (e.g., transmitting, receiving, outputting, obtaining, identifying) an indication for sensing in a wireless communications system.BACKGROUND
[0002] 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 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) . Additionally, 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) ) .
[0003] Some communication devices, for example, that support radio access technologies such as 5G advanced (5G-A) and 6G may also support Integrated Sensing and Communication (ISAC) , which may involve integrating communication and sensing functions into a wireless communications system.SUMMARY
[0004] The present disclosure relates to a UE, a network entity, methods, apparatuses, processors, and computer readable medium for managing (e.g., transmitting, receiving, outputting, obtaining, identifying) an indication for sensing in a wireless communications system. According to the various aspects of the present disclosure, a UE may be aware of information used for sensing, and thereby improving a sensing performance by the UE.
[0005] In some implementations, there is provided a UE. The UE comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive, from a network entity, an indication of whether to use downlink information or uplink information for sensing; and perform sensing based at least in part on the received indication indicating to use the downlink information for sensing or transmit the uplink information to the network entity based at least in part on the received indication indicating to use the uplink information for sensing.
[0006] In some implementations, there is provided a network entity. The network entity comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: transmit, to a UE, an indication of whether to use downlink information or uplink information for sensing; and perform sensing based at least in part on the indication indicating to use the uplink information for sensing or transmit the downlink information to the UE based at least in part on the indication indicating to use the downlink information for sensing.
[0007] In some implementations, there is provided a method performed by the UE. The method comprises: receiving, from a network entity, an indication of whether to use downlink information or uplink information for sensing; and performing sensing based at least in part on the received indication indicating to use the downlink information for sensing or transmitting the uplink information to the network entity based at least in part on the received indication indicating to use the uplink information for sensing.
[0008] In some implementations, there is provided a method performed by the network entity. The method comprises: transmitting, to a UE, an indication of whether to use downlink information or uplink information for sensing; and performing sensing based at least in part on the indication indicating to use the uplink information for sensing or transmitting the downlink information to the UE based at least in part on the indication indicating to use the downlink information for sensing.
[0009] In some implementations, there is provided a processor for wireless communication. The processor comprises at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a network entity, an indication of whether to use downlink information or uplink information for sensing; and perform sensing based at least in part on the received indication indicating to use the downlink information for sensing or transmit the uplink information to the network entity based at least in part on the received indication indicating to use the uplink information for sensing.
[0010] In some implementations, there is provided a processor for wireless communication. The processor comprises at least one controller coupled with at least one memory and configured to cause the processor to: transmit, to a UE, an indication of whether to use downlink information or uplink information for sensing; and perform sensing based at least in part on the indication indicating to use the uplink information for sensing or transmit the downlink information to the UE based at least in part on the indication indicating to use the downlink information for sensing.
[0011] In some implementations of the methods and the UE described herein, the indication indicates to use the downlink information for sensing, and the indication is carried in downlink control information (DCI) being used for scheduling M downlink channels, further comprising: generating a sensing result by performing sensing based on the downlink information; determining a resource for a transmission of the sensing result; and transmitting, to the network entity, the sensing result by using the resource.
[0012] In some implementations of the methods and the UE described herein, further comprising: in accordance with a determination that a physical uplink control channel (PUCCH) resource is overlapped with a further transmission, determining whether to transmit the sensing result based on priorities of the sensing result and the further transmission.
[0013] In some implementations of the methods and the UE described herein, further comprising: in accordance with a determination that the indication indicates that a physical downlink shared channel (PDSCH) is used for both sensing and communication, determine that a hybrid automatic repeat request acknowledgement (HARQ-ACK) of the PDSCH is: transmitted, omitted, or be jointed with the sensing result.
[0014] In some implementations of the methods and the UE described herein, further comprising: transmitting, to the network entity, information about a plurality of sensing modes supported by the UE; and receiving, from the network entity, a notification indicating a specific sensing mode among the plurality of sensing modes.
[0015] In some implementations of the methods and the UE described herein, the indication indicates to use the uplink information for sensing, further comprising: generating the uplink information based on a sensing based method; and transmitting, to the network entity, the uplink information.
[0016] In some implementations of the methods and the network entity described herein, the indication indicates to use the downlink information for sensing, and the indication is carried in a DCI being used for scheduling M downlink channels, further comprising: determining a resource for a transmission of a sensing result; and receiving, from the UE, the sensing result by using the resource.
[0017] In some implementations of the methods and the network entity described herein, further comprising: receiving, from the UE, information about a plurality of sensing modes supported by the UE; and transmitting, to the UE, a notification indicating a specific sensing mode among the plurality of sensing modes.
[0018] In some implementations of the methods and the network entity described herein, further comprising: receiving, from the UE, the uplink information being generated based on a sensing based method.
[0019] In some implementations of the methods, the UE, the network entity described herein, further comprising: determining a slot or sub-slot for the transmission of the sensing result; and determining a PUCCH resource in the slot or sub-slot.
[0020] In some implementations of the methods, the UE, the network entity described herein, further comprising: determining the PUCCH resource from a set of PUCCH resources based on a number of bits of the sensing result.
[0021] In some implementations of the methods, the UE, the network entity described herein, further comprising: determining a set of PUCCH resources from a plurality of sets of PUCCH resources based on a number of bits of the sensing result; and determining the PUCCH resource from the set of PUCCH resources based on a PUCCH resource indication (PRI) field in the DCI.
[0022] In some implementations of the methods, the UE, the network entity described herein, further comprising: determining a physical uplink shared channel (PUSCH) resource for the transmission of the sensing result, wherein the PUSCH resource comprises one of: a configured grant (CG) PUSCH indicated by the DCI, a nearest CG PUSCH with a smallest CG identifier, or a PUSCH resource scheduled by an uplink grant included in a PDSCH which is scheduled by the DCI.
[0023] In some implementations of the methods, the UE, and the network entity described herein, the indication of whether to use downlink information or uplink information for sensing comprises one of: the downlink information is used for sensing or not, the downlink information is used for communication or sensing, the downlink information is used for both sensing and communication or only used for communication, the downlink information is used for both sensing and communication or only used for communication or only used for sensing, the uplink information is used for sensing or not, the uplink information is used for communication or sensing, the uplink information is used for both sensing and communication or only used for communication, or the uplink information is used for both sensing and communication or only used for communication or only used for sensing.
[0024] In some implementations of the methods, the UE, and the network entity described herein, the indication comprises a bit field in a DCI, and wherein the bit field indicates one of:whether M downlink channels scheduled by the DCI are used for sensing, whether demodulation reference signals (DMRSs) of the M downlink channels scheduled by the DCI are used for sensing, whether M uplink channels scheduled by the DCI are used for sensing, or whether DMRSs of the M uplink channels scheduled by the DCI are used for sensing, wherein M is an integer value.
[0025] In some implementations of the methods, the UE, and the network entity described herein, the indication comprises N bit fields in a DCI, and M bit fields among the N bit fields are used for indicating one of: whether M downlink channels scheduled by the DCI are used for sensing respectively, whether DMRSs of the M downlink channels scheduled by the DCI are used for sensing respectively, whether M uplink channels scheduled by the DCI are used for sensing respectively, or whether DMRSs of the M uplink channels scheduled by the DCI are used for sensing respectively, wherein M and N are integer values, and N is larger than or equals to M.
[0026] In some implementations of the methods, the UE, and the network entity described herein, the indication comprises a time domain resource assignment (TDRA) field of a DCI.
[0027] In some implementations of the methods, the UE, and the network entity described herein, the TDRA field indicates a row of a plurality of rows of a table, and each row of the plurality of rows indicates: M time domain resources for M channels, wherein the M channels comprises M downlink channels or M uplink channels, and whether each channel among the M channels or DMRSs of each channel among the M channels is used for sensing, wherein M is an integer value.
[0028] In some implementations of the methods, the UE, and the network entity described herein, the M downlink channels comprise one of: one PDSCH, a PDSCH with M repetitions, M PDSCHs in one cell, M PDSCHs in M cells, M codewords in one cell, or M semi-persistent scheduling (SPS) PDSCHs.
[0029] In some implementations of the methods, the UE, and the network entity described herein, the M uplink channels comprises one of: one PUSCH, a PUSCH with M repetitions, M PUSCHs in one cell, M PUSCHs in M cells, M PUSCHs for one transmission block (TB) , or M type 2 CG PUSCHs.
[0030] In some implementations of the methods, the UE, and the network entity described herein, the DCI further indicates: M transmission control indicators (TCIs) for M PDSCHs, or M sounding reference signal resource indicators (SRIs) for M PUSCHs.
[0031] In some implementations of the methods, the UE, and the network entity described herein, the indication comprises M parameters in radio resource control (RRC) signalling, and wherein the M parameters are used for indicating one of: whether M CG PUSCHs configured by the RRC signalling in a period are used for sensing, whether M SPS PDSCHs configured by the RRC signalling in a period are used for sensing, whether DMRSs of the M CG PUSCHs configured by the RRC signalling in a period are used for sensing, whether DMRSs of the M SPS PDSCHs configured by the RRC signalling in a period are used for sensing, whether M downlink reference signals configured by the RRC signalling in a period are used for sensing, whether M uplink reference signals configured by the RRC signalling in a period are used for sensing, or whether M data channels or DMRSs of the M data channels in M cells configured by the RRC signaling are used for sensing, wherein M is an integer value.
[0032] In some implementations of the methods, the UE, and the network entity described herein, the slot or sub-slot is determined based on: a specific slot or sub-slot in which a last PDSCH or a last repetition which is scheduled by the DCI and is used for sensing is, and a difference value.
[0033] In some implementations of the methods, the UE, and the network entity described herein, the difference value is one of: a value indicated by a hybrid automatic repeat request acknowledgement (HARQ-ACK) timing field in the DCI, a value indicated by a specific field in the DCI, a value predefined, a value preconfigured by an RRC parameter, a value indicated in an uplink grant, or a sum of a value indicated by the HARQ-ACK timing field and a predefined or preconfigured offset.BRIEF DESCRIPTION OF THE DRAWINGS
[0034] FIG. 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.
[0035] FIG. 2A illustrates an example schematic of a PUSCH with PUSCH repetition type A in accordance with aspects of the present disclosure.
[0036] FIG. 2B illustrates an example schematic of a PUSCH with PUSCH repetition type B in accordance with aspects of the present disclosure.
[0037] FIG. 2C illustrates an example schematic of a PUSCH with enhanced PUSCH repetition type A in accordance with aspects of the present disclosure.
[0038] FIG. 2D illustrates an example schematic of a PUSCH with a transport block over multiple slots (TBOMS) in accordance with aspects of the present disclosure.
[0039] FIG. 2E illustrates examples of different modes for sensing in accordance with aspects of the present disclosure.
[0040] FIG. 3 illustrates a schematic diagram of an example wireless communication system in accordance with aspects of the present disclosure.
[0041] FIG. 4 illustrates a signalling diagram of a communication process in accordance with aspects of the present disclosure.
[0042] FIG. 5A illustrates a schematic diagram of a DCI indicating sensing in accordance with aspects of the present disclosure.
[0043] FIG. 5B illustrates a schematic diagram of a DCI indicating communication in accordance with aspects of the present disclosure.
[0044] FIG. 5C illustrates a schematic diagram of a DCI indicating ISAC in accordance with aspects of the present disclosure.
[0045] FIG. 5D illustrates a schematic diagram of a DCI indicating sensing and communication for different channels in accordance with aspects of the present disclosure.
[0046] FIG. 5E illustrates a schematic diagram of a DCI scheduling multiple PUSCH repetitions with type A in accordance with aspects of the present disclosure.
[0047] FIG. 5F illustrates a schematic diagram of a DCI scheduling multiple PUSCH repetitions with type B in accordance with aspects of the present disclosure.
[0048] FIG. 5G illustrates a schematic diagram of a DCI scheduling multiple channels for multiple cells in accordance with aspects of the present disclosure.
[0049] FIG. 6 illustrates a schematic diagram of feedback in accordance with aspects of the present disclosure.
[0050] FIG. 7 illustrates an example of a device in accordance with aspects of the present disclosure.
[0051] FIG. 8 illustrates an example of a processor in accordance with aspects of the present disclosure.
[0052] FIG. 9 illustrates a flowchart of an example method implemented at a UE in accordance with aspects of the present disclosure.
[0053] FIG. 10 illustrates a flowchart of an example method implemented at a network entity in accordance with aspects of the present disclosure.
[0054] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0055] Principles of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below. In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0056] 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.
[0057] It shall be understood that although the terms “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 embodiments. As used herein, 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.
[0058] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of embodiments. As used herein, the singular forms “a, ” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises, ” “comprising, ” “has, ” “having, ” “includes” and / or “including, ” when used herein, specify the presence of stated features, elements, components and / or the like, but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. For example, 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.
[0059] FIG. 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. 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 (CN) 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as a long term evolution (LTE) network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as a new radio (NR) network. In other implementations, 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. 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.
[0060] 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. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
[0061] 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, message, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112. For example, 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. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies 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. For example, 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.
[0062] 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. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, 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. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.
[0063] 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 CN 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. Additionally, or alternatively, 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.
[0064] A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink (SL) . For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
[0065] A network entity 102 may support communications with the CN 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the CN 106 through one or more backhaul links 116 (e.g., via an S1, N2, N3, 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) . In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102) . In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the CN 106) . In some implementations, 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) .
[0066] In some implementations, 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) ) . For example, 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.
[0067] 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) . In some implementations, 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) ) .
[0068] 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. For example, 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. In some implementations, 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) ) . 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.
[0069] Additionally, or alternatively, 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) . In some implementations, 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) .
[0070] 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) , and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface) . In some implementations, 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.
[0071] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 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) ) . In some implementations, the 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 CN 106.
[0072] The CN 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N3, or another network interface) . The packet data network 108 may include an application server 118. In some implementations, 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 CN 106 via a network entity 102. The CN 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 CN 106 (e.g., one or more network functions of the CN 106) .
[0073] In the wireless communications system 100, 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) . In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, 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.
[0074] 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 (CP) . A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.
[0075] A time interval of a resource (e.g., a communication 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. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.
[0076] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, 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. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0077] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, 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) . In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, 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) . In some implementations, 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.
[0078] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.
[0079] A network entity 102 may transmit, and a UE 104 may receive, a grant. In some implementations, the grant may be an uplink (UL) grant that dynamically schedules one or more PUSCH transmissions. For example, the network entity 102 may transmit, and the UE 104 may receive, a DCI that includes the UL grant dynamically scheduling the one or more PUSCH transmissions. In some other implementations, the one or more PUSCH transmissions may be associated with (e.g., allocated by, assigned by, scheduled by) a CG type 1 or type 2. A CG type 1 PUSCH transmission may be semi-statically configured based at least in part on one or more higher layer parameters, including configuredGrantConfig and rrc-ConfiguredUplinkGrant without receiving (e.g., detecting) a UL grant in a DCI. A CG type 2 PUSCH transmission may be semi-persistently scheduled by a UL grant that may be included in a valid activation DCI, for example, after the reception of the higher layer parameter configuredGrantConfig not including rrc-ConfiguredUplinkGrant.
[0080] In some implementations, before a UE 104 (e.g., an NR UE) transmits a PUSCH, which may be a dynamically scheduled PUSCH or a CG PUSCH, the UE 104 may receive a frequency domain resource assignment (FDRA) or a time domain resource assignment (TDRA) , or both, from a network entity 102 (e.g., an NR gNB) and determine one or more frequency and time domain resources for the PUSCH.
[0081] For a dynamically scheduled PUSCH and a CG type 2 PUSCH, a UE 104 may determine a resource assignment (e.g., a TDRA, an FDRA, or both) based on a resource allocation field in a received (e.g., detected) DCI. For CG type 1 PUSCH, the resource assignment for a PUSCH transmission may be provided by a higher layer parameter (e.g., frequencyDomainAllocation of configuredGrantConfig) . A frequency domain resource assignment indicated by the higher layer parameter (e.g., the frequencyDomainAllocation) to the UE 104 may identify (e.g., indicate) a set of resource blocks (RB) associated with an active bandwidth part (BWP) . For a dynamically scheduled PUSCH, the UE 104 may receive a DCI that includes a time domain resource assignment field 'Time domain resource assignment' with a value m in the DCI, which may indicate a row index m + 1 (an indexed row) in an allocated table, where the allocated table could be predefined or could be configured by a higher layer parameter. The row defines the slot offset K2, the start and length indicator SLIV (or directly the start symbol S and the allocation length L) , and the number of repetitions (if numberOfRepetitions is present in the table) to be applied in the PUSCH transmission. Where, the slot offset K2 is used to indicate the number of slots between the DCI received slot and the PUSCH transmitted slot.
[0082] The wireless communications system 100, including the network entities 102 and UEs 104, may support various resource allocations in a time domain for dynamically scheduled PUSCH, which include a PUSCH repetition Type A and a PUSCH repetition Type B. In some implementations, the wireless communications system 100, including the network entities 102 and UEs 104, may support enhancements for the PUSCH repetition type A for PUSCH coverage enhancements, for example, for time division duplex (TDD) . In some implementations, the network entities 102 and UEs 104 may support TB processing over multi-slot PUSCH (TBOMS) for PUSCH coverage enhancements. In some implementations, the UEs 104 may be configured by the network entities 102 to perform (e.g., support) a resource allocation of a set of resource allocations for a TB transmission based on a higher layer parameter transmitted to the UEs 104 by the network entities 102.
[0083] For a PUSCH repetition Type A, a UE 104 may determine a starting (e.g., beginning) symbol S relative to a start (e.g., beginning) of a slot, and a number (e.g., quantity) of consecutive symbols L counting from the symbol S allocated for a PUSCH, based at least in part on the start and length indicator SLIV of an indexed row:
[0084] if (L-1) ≤7 then
[0085] SLIV=14·(L-1) +S
[0086] else
[0087] SLIV=14·(14-L+1) + (14-1-S)
[0088] where 0<L≤14-S.
[0089] In some implementations, when the UE 104 transmits a PUSCH scheduled by DCI format 0_1 or DCI format 0_2 received via a PDCCH with cyclic redundancy check (CRC) scrambled with cell radio network temporary identifier (C-RNTI) , modulation coding scheme cell RNTI (MCS-C-RNTI) , or configured scheduling RNTI (CS-RNTI) with new data indicator (NDI) =1, the UE 104 may determine the number of repetitions K based on the following logic:
[0090] - if a numberOfRepetitions is present in the resource allocation table, the number of repetitions K is equal to numberOfRepetitions;
[0091] - elseif the UE 104 is configured with pusch-AggregationFactor, the number of repetitions K is equal to pusch-AggregationFactor;
[0092] - otherwise K=1.
[0093] For a PUSCH repetition Type A, in case K>1, the UE 104 may apply the same symbol allocation across the K consecutive slots. The UE 104 may repeat the TB across the K consecutive slots by applying the same symbol allocation in each slot.
[0094] For a PUSCH repetition Type A, a PUSCH transmission in a slot of a multi-slot PUSCH transmission is omitted if any symbol of the PUSCH is overlapped with the set of symbols of the slot that are indicated to a UE 104 as downlink by tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated.
[0095] FIG. 2A illustrates an example schematic of a PUSCH 210 with PUSCH repetition type A in accordance with aspects of the present disclosure. It is assumed that K2 =1, S=2, L=8, K=4, then the time domain resource for a PUSCH with PUSCH repetition Type A could be seen in FIG. 2A.
[0096] For a PUSCH repetition Type B, the number of nominal repetitions is given by numberOfRepetitions. For the n-th nominal repetition, n = 0, …, numberOfRepetitions -1,
[0097] -The slot where the nominal repetition starts is given by and the starting symbol relative to the start of the slot is given by
[0098] -The slot where the nominal repetition ends is given by and the ending symbol relative to the start of the slot is given by
[0099] Here Ks is the slot where the PUSCH transmission starts, and is the number of symbols per slot. The starting symbol S relative to the start of the slot, and the number of consecutive symbols L counting from the symbol S allocated for the PUSCH are provided by startSymbol and length of the indexed row of the resource allocation table, respectively.
[0100] For a PUSCH repetition Type B, a symbol that is indicated as downlink by tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated, is considered as an invalid symbol for a PUSCH repetition Type B transmission. After determining the invalid symbol (s) for a PUSCH repetition type B transmission for each of the K nominal repetitions, the remaining symbols are considered as potentially valid symbols for a PUSCH repetition Type B transmission. If the number of potentially valid symbols for a PUSCH repetition type B transmission is greater than zero for a nominal repetition, the nominal repetition consists of one or more actual repetitions, where each actual repetition consists of a consecutive set of all potentially valid symbols that can be used for a PUSCH repetition Type B transmission within a slot. An actual repetition with a single symbol is omitted except for the case of L=1.
[0101] An actual repetition is omitted if any symbol of the PUSCH is overlapped with the set of symbols of the slot that are indicated to a UE 104 as downlink by tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated.
[0102] FIG. 2B illustrates an example schematic of a PUSCH 220 with PUSCH repetition type B in accordance with aspects of the present disclosure. It is assumed that K2 =0, S=2, L=8, K=4, then the time domain resource for a PUSCH with PUSCH repetition Type B could be seen in FIG. 2B.
[0103] For the enhanced PUSCH repetition Type A, the resource allocation in time domain is almost the same as the PUSCH repetition type A, excluding that the number of repetitions is counted on the basis of available slots. A slot is determined as unavailable if at least one of the symbols indicated by TDRA for a PUSCH in the slot overlaps with the symbol not intended for UL transmissions, and semi-static flexible symbol configured by tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated, is considered as available.
[0104] FIG. 2C illustrates an example schematic of a PUSCH 230 with enhanced PUSCH repetition type A in accordance with aspects of the present disclosure. It is assumed that K2 =1, S=2, L=8, K=4, then the time domain resource for a PUSCH with enhanced PUSCH repetition Type A could be seen in FIG. 2C.
[0105] For TBOMS, time domain resource determination can be performed via PUSCH repetition Type A like TDRA. The number of slots K allocated for TBOMS is determined by using a row index of a TDRA list, configured via RRC and is counted based on the available slots for UL transmission. The transmission in each slot could be names as one transmission part of the TB in this invention. The determination of available slots is as defined in enhanced PUSCH repetition Type A.
[0106] FIG. 2D illustrates an example schematic of a PUSCH 240 with TBOMS in accordance with aspects of the present disclosure. It is assumed that K2 =1, S=2, L=8, K=4, then the time domain resource for a PUSCH with TBOMS could be seen in FIG. 2D.
[0107] For one DCI scheduling multiple PUSCH transmission in one cell, a DCI could also schedule multiple PUSCH transmissions in a cell by indicate a row of an allocated table, and each row in the allocated table could be configured with multiple time domain resource used for multiple PUSCH transmissions.
[0108] For one DCI scheduling multiple PUSCH transmission in multiple cells, a DCI could also schedule multiple PUSCH transmissions in multiple cells, and the DCI including a Time domain resource assignment could indicate the time domain resources for the PUSCH transmissions in multiple cells by indicate a row of table, and this field is used to indicate an entry in the higher layer parameter TDRA-FieldIndexListDCI-0-3. Each entry in the higher layer parameter TDRA-FieldIndexListDCI-0-3 contains the ‘Time domain resource assignment’ index for each cell in the scheduled cell set, where the ‘Time domain resource assignment’ indexes for all the cells are placed according to an ascending order of a serving cell index.
[0109] The DCI could include a SRS resource set indicator field, and indicates the beam / TRP for all the PUSCH repetition.
[0110] For CG Type 1 PUSCH transmissions, the higher layer parameter timeDomainAllocation value m provides a row index m+1 pointing to the determined time domain resource allocation table, where the start symbol and length are determined following the procedure defined in above for dynamically scheduled PUSCH. For CG Type 2 PUSCH transmissions, the resource allocation follows UL grant received on the DCI.
[0111] There are also four mainly schemes for resource allocation in time domain of a CG PUSCH including Type 1 or Type 2. And they have some differences with the schemes for a dynamically scheduled PUSCH, such as for a PUSCH repetition Type A, a PUSCH repetition Type B, an enhanced PUSCH repetition Type A and a TBOMS, the number of (nominal) repetitions K to be applied to the transmitted transport block is provided by the indexed row in the time domain resource allocation table if numberOfRepetitions is present in the table; otherwise K is provided by the higher layer configured parameters repK. Besides, other procedures defined in clause of dynamically scheduled could be reused.
[0112] For a PUSCH repetition Type B, for PUSCH transmissions with a Type 1 or Type 2 configured grant, the nominal repetitions and the actual repetitions are determined according to the procedures for a PUSCH repetition Type B defined in clause of dynamically scheduled PUSCH.
[0113] For the CG PUSCH, a network entity 102 (such as a gNB) could also configure multiple PUSCH resources in one period by indicate the resource for the first PUSCH, and a number N of PUSCH in a period. And each PUSCH of the multiple PUSCHs could use same resource in the continuous N slots.
[0114] For a dynamic PDSCH transmission, the transmission schemes for a PDSCH repetition type A, one DCI scheduling multiple PDSCH transmissions in one cell and multiple cells is also supported. And in the DCI scheduling the PDSCH, there could be a TCI field to indicate the beam for all the PDSCH transmissions scheduled by the DCI. For a PDSCH repetition scheduled by a DCI, the DCI could only indicate at most 2 TCIs for the PDSCH repetition. For semi-persistent scheduling (SPS) PDSCH, the transmission method is like CG type 2 transmission and the transmission schemes for the PDSCH repetition type A, one DCI scheduling multiple PUSCH transmissions in one cell and multiple cells is also supported.
[0115] ISAC is considered a promising feature in Rel-19 and 6G study, as sensing function can greatly enhance the network application scenarios, e.g., vehicle to everything (V2X) , unmanned aerial vehicles (UAVs) , smart city, smart home, factories, healthcare, and maritime sector. Some relevant sensing modes may be summarized as shown in FIG. 2E based on some use cases.
[0116] Considering the requirements of typical use cases of ISAC and setting a reasonable workload, it is proposed to study some of the sensing modes, as shown in FIG. 2E, examples of different modes 250 for sensing in accordance with aspects of the present disclosure are illustrated, among which mode 2 relates to a gNB-to-UE bi-static sensing and mode 5 relates to a UE-to-gNB bi-static sensing.
[0117] FIG. 3 illustrates a schematic diagram of an example wireless communication system 300 in accordance with aspects of the present disclosure. As shown in FIG. 3, the wireless communication system 300 may include a network entity 102 and a UE 104, which may communicate with each other, as discussed with reference to FIG. 1.
[0118] The wireless communication system 300 may be an ISAC system. For example, the network entity 102 may be a sensing transmitter and the UE 104 may be a sensing receiver. For example, the UE 104 may be a sensing transmitter and the network entity 102 may be a sensing receiver. The sensing transmitter and the sensing receiver may be used for sensing one or more objects, e.g., in a sensing area. For example, a sensing object 302 is shown in FIG. 3, and a location of the sensing object 302 may be determined by the network entity 102 or the UE 104.
[0119] It is to be understood that the numbers of network entities, UEs, sensing objects shown in FIG. 3 are only for the purpose of illustration only. The wireless communication system 300 may include any suitable numbers of devices.
[0120] FIG. 4 illustrates a signalling diagram of a communication process 400 in accordance with aspects of the present disclosure. The communication process 400 may involve a network entity 102 and a UE 104. It would be appreciated that the communication process 400 may be applied to other communication scenarios, which will not be described in detail.
[0121] In some implementations, the UE 104 may transmit information about multiple sensing modes supported by the UE 104 to the network entity 102, for example, the information may be capability information of the UE 104. In some implementations, the network entity 102 may determine (or select) a sensing mode from the multiple sensing modes supported by the UE 104. In some implementations, the network entity 102 may transmit a notification to the UE 104, where the notification may indicate a specific sensing mode, e.g., the sensing mode selected from the multiple sensing modes supported by the UE 104. In some implementations, the specific sensing mode may be used for the sensing operation between the UE 104 and the network entity 102. For example, the specific sensing mode may be sensing per cell. For example, the specific sensing mode may be sensing per resource indication. For example, the specific sensing mode may be another mode, which the present disclosure does not limit.
[0122] In the communication process 400, the network entity 102 transmits an indication to the UE 104 at step 410, where the indication may indicate whether to use downlink information for sensing or the indication may indicate whether to use uplink information for sensing. For example, the indication may be carried in a DCI or in RRC signalling.
[0123] In some implementations, the indication may at least indicate a function of the downlink information or uplink information. In some examples, the indication may indicate a same function for one or more channels (such as downlink channels or uplink channels) or one or more reference signals (such as downlink reference signals (DL RSs) or uplink reference signals (UL RSs) ) . In some examples, the indication may indicate more than one function for different channels (such as downlink channels or uplink channels) or different RSs (such as DL RSs or UL RSs) . For example, the function may be one of: sensing (sensing only) , communication (communication only) , or ISAC (i.e. both sensing and communication) .
[0124] In some implementations, the downlink information may include a downlink reference signal, such as a channel state indicator reference signal (CSI-RS) or one or more DMRSs of a PDSCH. In some implementations, the downlink information may include a downlink channel, such as a PDSCH. In some implementations, the uplink information may include an uplink reference signal, such as a sounding reference signal (SRS) or one or more DMRSs of a PUSCH. In some implementations, the uplink information may include an uplink channel, such as a PUSCH.
[0125] In some example embodiments, the indication may indicate one of the following:
[0126] - whether the downlink information is used for sensing or not;
[0127] - whether the downlink information is used for communication or for sensing;
[0128] - whether the downlink information is used for communication only or for both sensing and communication;
[0129] - whether the downlink information is used for sensing only or for both sensing and communication;
[0130] - whether the downlink information is used for sensing only or for communication only or for both sensing and communication;
[0131] - whether the uplink information is used for sensing or not;
[0132] - whether the uplink information is used for communication or for sensing;
[0133] - whether the uplink information is used for communication only or for both sensing and communication;
[0134] - whether the uplink information is used for sensing only or for both sensing and communication; or
[0135] - whether the uplink information is used for sensing only or for communication only or for both sensing and communication.
[0136] In some implementations, the indication may be carried in a DCI, for example, the DCI is used for scheduling at least one PDSCH or at least one PUSCH.
[0137] For example, the DCI may schedule: one PDSCH, a PDSCH with M repetitions, M PDSCHs in one cell, M PDSCHs in M cells, M codewords in one cell, or M SPS PDSCHs. For example, the DCI may schedule: one PUSCH, a PUSCH with M repetitions, M PUSCHs in one cell, M PUSCHs in M cells, M PUSCHs in one TB, or M types CG PUSCHs. For example, M may be an integer, M≥2.
[0138] In some example embodiments, the indication may include a bit field in the DCI, that is, the DCI may include one bit field which is used for indicating one of: whether the at least one PDSCH (such as M PDSCHs, M is an integer) scheduled by the DCI is used for sensing, whether the at least one PUSCH (such as M PUSCHs, M is an integer) scheduled by the DCI is used for sensing, whether DMRSs of the at least one PDSCH scheduled by the DCI are used for sensing, or whether DMRSs of the at least one PUSCH scheduled by the DCI are used for sensing.
[0139] In some examples, the bit field may include at least one bit, e.g. 1 bit or 2 bits. In some examples, the bit field may be a first value (such as 01 or another value) , which indicates that all those scheduled by the DCI is used for sensing. In some examples, the bit field may be a second value (such as 10 or another value) , which indicates that all those scheduled by the DCI is used for communication. In some examples, the bit field may be a third value (such as 11 or another value) , which indicates that all those scheduled by the DCI is used for both sensing and communication (i.e. ISAC) . It is to be understood that the values indicated by the bit field may depend on the functions of the indication.
[0140] In some embodiments, according to the channel (s) scheduled by the DCI, the bit field in the DCI may indicate whether one of the following is used for sensing: one PDSCH, a PDSCH with M repetitions, M PDSCHs in one cell, M PDSCHs in M cells, M codewords in one cell, or M SPS PDSCHs. In some embodiments, the bit field in the DCI may indicate whether one of the following is used for sensing: DMRSs of the one PDSCH, DMRSs of a PDSCH with M repetitions, DMRSs of M PDSCHs in one cell, DMRSs of M PDSCHs in M cells, or DMRSs of M SPS PDSCHs. For example, all PDSCHs or all DMRSs of all PDSCHs scheduled by the DCI are to be used for sensing or not used for sensing. For example, if the DCI is an activation DCI for one SPS PDSCH or M SPS PDSCHs, then the bit field in the DCI may indicate whether the one SPS PDSCH or all the M SPS PDSCHs are used for sensing or not.
[0141] In some embodiments, according to the channel (s) scheduled by the DCI, the bit field in the DCI may indicate whether one of the following is used for sensing: one PUSCH, a PUSCH with M repetitions, M PUSCHs in one cell, M PUSCHs in M cells, M PUSCHs in one TB, or M types CG PUSCHs. In some embodiments, the bit field in the DCI may indicate whether one of the following is used for sensing: DMRSs of the one PUSCH, DMRSs of a PUSCH with M repetitions, DMRSs of M PUSCHs in one cell, DMRSs of M PUSCHs in M cells, DMRSs of M PUSCHs in one TB, or DMRSs of M types CG PUSCHs. For example, all PUSCHs or all DMRSs of all PUSCHs scheduled by the DCI are to be used for sensing or not used for sensing. For example, if the DCI is an activation DCI for one type 2 CG PUSCH or M type 2 CG PUSCHs, then the bit field in the DCI may indicate whether the one type 2 CG PUSCH or all the M type 2 CG PUSCHs are used for sensing or not.
[0142] In some examples, the bit field may be the TDRA field in the DCI. For example, the bit field (i.e. the TDRA field) may indicate one row among multiple rows in an allocated table. In the table, each row may indicate a time domain resource of a corresponding channel and whether the corresponding channel (or DMRS (s) of the corresponding channel) is used for sensing. Table 1 below shows an example of the table:
[0143] Table 1
[0144] As an example, the row with an index “0” in Table 1 may indicate a time domain resource with “SLIV1” and a function with “sensing” for a corresponding channel.
[0145] In some example embodiments, the indication may include multiple bit fields in the DCI, in some examples, the multiple bit fields may correspond to multiple channels or multiple cells. A relationship or mapping relation between the multiple bit fields and the multiple channels / cells may be defined or preconfigured. For example, a first bit field may correspond to a first channel / cell, a second bit field may correspond to a second channel / cell. For example, a first bit field may correspond to a first channel / cell, a second bit field may correspond to a second channel / cell and a third channel / cell. For example, a specific bit field may correspond to one or more than one channel / cell.
[0146] In some examples, the DCI may schedule multiple (such as M) codewords in one cell, the DCI may include multiple (such as M) bit fields associated with the multiple codewords, for example, one bit field is used for indicating whether a corresponding codeword (a codeword corresponding to the one bit field) is used for sensing.
[0147] In some examples, the DCI may schedule a PDSCH with M repetitions, M PDSCH transmissions in one cell, or M PDSCH transmissions in M cells, then the DCI may include N bit fields (N≥M) , where a respective bit field of M bit fields among the N bit fields may indicate whether a corresponding PDSCH is used for sensing, or may indicate whether DMRS (s) of a corresponding PDSCH is used for sensing. In some examples, the DCI may schedule a PUSCH with M repetitions, M PUSCH transmissions in one cell, M PUSCH transmissions in M cells, or M PUSCH transmissions for TBOMS, then the DCI may include N bit fields (N≥M) , where a respective bit field of M bit fields among the N bit fields may indicate whether a corresponding PUSCH is used for sensing, or may indicate whether DMRS (s) of a corresponding PUSCH is used for sensing.
[0148] For example, M is a repetition number of PDSCH, a number of PDSCH transmissions, a repetition number of PUSCH, a number of PUSCH transmissions, or a number of slots for TBOMS. For example, M is an integer value, which is not less than 2. N is larger than or equal to M. N could be determined by the largest repetition number, or a maximum number of cells, or a configured number of PUSCHs for a TBOMS, or a maximum number of PUSCHs in a cell could schedule by a DCI.
[0149] As an example, if PUSCH repetition with type B is scheduled by the DCI, then M may represent a number of initial repetition number, for example, the actual repetition derived from the initial repetition may have a same function.
[0150] As an example, if a PUSCH with M repetitions or M PUSCH transmissions for TBOMS is scheduled by the DCI, then if two adjacent PUSCH transmissions are used for a same function, then they can be used for joint channel estimation, otherwise (i.e. two adjacent PUSCH transmissions are not used for a same function) they cannot be used for joint channel estimation. In some other examples, a change of the functions of a followed PUSCH transmission may not affect a determination of the actual time domain window.
[0151] In some examples, if multiple PDSCH transmission in one cell or multiple PUSCH transmission in one cell is scheduled by the DCI, the TDRA field in the DCI may be used as the indication. For example, the TDRA field may indicate row among multiple rows in an allocated table. In the table, each row may indicate multiple time domain resources of multiple corresponding channels and whether the multiple corresponding channels (or DMRSs of the multiple corresponding channels) are used for sensing. Table 2 below shows an example of the table:
[0152] Table 2
[0153] As an example, the row with an index “0” in Table 2 may indicate: a first time domain resource with “SLIV1” and a function with “sensing” for a first channel, and a second time domain resource with “SLIV2” and a function with “communication” for a second channel.
[0154] In some example embodiments, the DCI may further include multiple TCIs for multiple PDSCHs, where the multiple PDSCHs are used for sensing. For example, the DCI may schedule a PDSCH with M repetitions or M PDSCHs in one cell (or in M cells) , a number of the multiple TCIs may equal to or be less than M, and a mapping between the multiple TCIs and the M repetitions or M PDSCHs may be predefined or preconfigured. For example, a number of the multiple TCIs may be larger than 2.
[0155] In some example embodiments, the DCI may further include multiple SRS resource sets indicators for multiple PUSCHs, where the multiple PUSCHs are used for sensing. For example, the DCI may schedule a PUSCH with M repetitions or M PUSCHs in one cell (or in M cells) , a number of the multiple SRIs may equal to or be less than M, and a mapping between the multiple TCIs and the M repetitions or M PUSCHs may be predefined or preconfigured. For example, a number of the multiple SRIs may be larger than 2.
[0156] Accordingly, the indication may be carried in a DCI, and the function of downlink information or uplink information about whether is used for sensing may be dynamically indicated to the UE, and thus the indication may be used more flexibly.
[0157] In some other implementations, the indication may be carried in RRC signalling, for example, the RRC signalling is used for configuring a transmission of downlink information (such as PDSCH or DL RS) or uplink information (such as PUSCH or UL RS) .
[0158] In some example embodiments, the indication may be implemented as a parameter in the RRC signalling. In some examples, the RRC signalling may configure a transmission of a CG PUSCH, the parameter in the RRC signalling (i.e. the indication) may indicate whether the CG PUSCH is used for sensing, or indicate whether DMRSs of the CG PUSCH is used for sensing. In some examples, the RRC signalling may configure a transmission of an SPS PDSCH, the parameter in the RRC signalling (i.e. the indication) may indicate whether the SPS PDSCH is used for sensing, or indicate whether DMRSs of the SPS PDSCH is used for sensing. In some examples, the RRC signalling may configure a transmission of a DL RS or a UL RS, the parameter in the RRC signalling (i.e. the indication) may indicate whether the DL RS or the UL RS in a period is used for sensing.
[0159] In some example embodiments, the indication may be implemented as multiple parameters (such as M parameters) in the RRC signalling. In some examples, the RRC signalling may configure multiple CG PUSCH transmissions, the multiple parameters may respectively indicate whether the multiple CG PUSCH transmissions are used for sensing, or respectively indicate whether DMRSs of the multiple CG PUSCH transmissions are used for sensing. In some examples, the RRC signalling may configure multiple SPS PDSCH transmissions, the multiple parameters may respectively indicate whether the multiple SPS PDSCH transmissions are used for sensing, or respectively indicate whether DMRSs of the multiple SPS PDSCH transmissions are used for sensing. In some examples, the RRC signalling may configure multiple DL RSs or UL RSs, the multiple parameters may respectively indicate whether the multiple DL RSs or UL RSs in a period are used for sensing. In some examples, the RRC signalling may configure multiple data channels (such as multiple PDSCHs or multiple PUSCHs) for multiple cells, the multiple parameters may respectively indicate whether the multiple data channels are used for sensing, or respectively indicate whether DMRSs of the multiple data channels are used for sensing.
[0160] Accordingly, the indication may be carried in RRC signalling, and the function of downlink information or uplink information about whether is used for sensing may be configured to the UE, and thus signalling overhead may be reduced.
[0161] In the communication process 400, upon receiving the indication, the UE 104 performs further operation 411 or operation 451 according to the indicated information of the indication.
[0162] The UE 104 performs sensing at step 420 based on received downlink information 415, if the indication indicates to use downlink information for sensing.
[0163] In some examples, if the indication indicates that a PDSCH is used for sensing, the UE 104 may decode the PDSCH, and further sense a state of a channel from the network entity 102 to the UE 104 based on the decoded PDSCH. For example, if the indication indicates that a PDSCH is used for sensing, the UE 104 may determine that the PDSCH is transmitted with a waveform that is different from OFDM, for example, the PDSCH may be transmitted with a waveform such as linear frequency modulated (LMF) , orthogonal time frequency space (OTFS) , for example, the PDSCH is transmitted with an extended CP.
[0164] In some examples, if the indication indicates that DMRS (s) of a PDSCH is used for sensing, the UE 104 may determine the channel state based on the DMRS (s) of the PDSCH. For example, the UE 104 may use the DMRS (s) of the PDSCH to determine (calculate) one or more values to reflect the channel state. For example, the one or more values may include channel quality indicator (CQI) , rank indicator (RI) , recoding matrix indicator (PMI) , reference signal received power (RSRP) , or some other parameter.
[0165] In some examples, if the indication indicates that a downlink reference signal (DL RS) is used for sensing, the UE 104 may use the downlink reference signal to determine (calculate) one or more values to reflect the channel state. For example, the one or more values may include some parameter different with CQI, RI, PMI, RSRP.
[0166] In some examples, if the indication indicates that the downlink information (PDSCH or DL RS) is used for both sensing and communication, the UE 104 may decode the downlink information and sense the channel. In this way, the channel resource may be used more efficiently.
[0167] In some implementations, the UE 104 may determine to transmit a sensing result to the network entity 102 after sensing the downlink information. In some implementations, a configuration may have been transmitted from the network entity 102 to the UE 104, the configuration may indicate whether to transmit a sensing result. In some implementations, the UE 104 may determine to transmit the sensing result based on the configuration. It is noted that in case the configuration indicates not the transmit the sensing result, then the following steps 430-440 may be omitted.
[0168] As shown in FIG. 4, the UE 104 determine resource for a transmission of the sensing result at step 430, and transmit the sensing result at step 440 by using the determined resource.
[0169] In some example embodiments, the UE 104 may determine that the sensing result is transmitted over PUCCH. In some embodiments, the UE 104 may determine a slot (or sub-slot) , and then determine a PUCCH resource in the slot (or sub-slot) for transmitting the sensing result.
[0170] In some embodiments, the UE 104 may determine the slot (or sub-slot) for transmitting the sensing result based on a specific slot (or sub-slot) and a difference value, details of which are provided below.
[0171] In some examples, the UE 104 may determine a specific slot (or sub-slot) in which a last PDSCH used for sensing is transmitted. For example, the last PDSCH used for sensing may be the last PDSCH transmission for sensing among multiple PDSCH transmissions scheduled by the DCI. For example, the last PDSCH used for sensing may be the last PDSCH repetition for sensing among a PDSCH with repetition A or B scheduled by the DCI. For example, a PDSCH transmission or a PDSCH repetition for communication only is not counted while determining the last PDSCH used for sensing. For example, the specific slot (or sub-slot) in which a last PDSCH used for sensing is transmitted may represented as n.
[0172] In some embodiments, the UE 104 may determine a difference value which may represent a different between a slot (or sub-slot) for transmitting the sensing result and a slot (or sub-slot) for transmitting the last PDSCH used for sensing.
[0173] In some examples, the difference value may be a value indicated by a hybrid automatic repeat request acknowledgement (HARQ-ACK) timing field in the DCI. For example, the HARQ-ACK timing field may indicate a value K, that is the difference value may be represented as K. In some examples, the UE 104 may determine that the slot (or sub-slot) for transmitting the sensing result is n+K.
[0174] In some examples, the difference value may be a value indicated by a specific field in the DCI, such as a newly defined field for sensing. In some examples, the difference value may be a value predefined in the 3GPP specification. In some examples, the difference value may be a value preconfigured by the network entity 102, e.g. via an RRC parameter. In some examples, the difference value may be a value indicated by a UL grant in the PDSCH. For example, the difference value may be represented as K. In some examples, the UE 104 may determine that the slot (or sub-slot) for transmitting the sensing result is n+K.
[0175] In some examples, the difference value may be a sum of a first value and a second value, where the first value is indicated by the HARQ-ACK timing field or the specific field in the DCI, the second value is an offset configured by the network entity 102. For example, the first value may be represented as K, the second value may be represented as ΔK, that is the difference value may be represented as K+ΔK. In some examples, the UE 104 may determine that the slot (or sub-slot) for transmitting the sensing result is n+K+ΔK.
[0176] In some embodiments, the UE 104 may further determine a PUCCH resource in the slot (or sub-slot) , such as in the slot (or sub-slot) n+K (or n+K+ΔK) .
[0177] In some examples, the UE 104 may determine the PUCCH resource from a set of PUCCH resources based on a number of bits of the sensing result, for example, the set of PUCCH resources may be configured by the network entity 102 for transmitting sensing results.
[0178] In some examples, the UE 104 may determine a set of PUCCH resources from multiple sets of PUCCH resources, e.g. based on a number of bits of the sensing result, for example, the multiple sets of PUCCH resources may be configured by the network entity 102 for uplink control information (UCI) transmission. In some examples, the UE 104 may further determine the PUCCH resource from the set of PUCCH resources, e.g. based on a PRI field in the DCI.
[0179] In some embodiments, the sensing result transmitted on the PUCCH resource may be overlapped with another transmission, such as a UCI, acknowledgement or non-acknowledgement (A / N) , channel state indicator (CSI) , or scheduling request (SR) . for example, the determined PUCCH resource for the sensing result may be overlapped with the resource for another transmission.
[0180] In some examples, priorities of the transmissions may be used for determining which is transmitted. For example, if a priority of the sensing result and a priority of the UCI are the same, then the sensing result and the UCI may be multiplexed in the same PUCCH resource. For example, if a priority of the sensing result and a priority of the UCI are different, then whether the sensing result and the UCI may be multiplexed in the same PUCCH resource could be configured by the network entity 102. For example, if a priority of the sensing result and a priority of the UCI are different, then a PUCCH with a lower priority may be dropped, that is a PUCCH with a higher priority may be transmitted. For example, if a priority of the sensing result and a priority of the UCI are different, if the sensing result is with repetition and overlapped with a UCI in one or more than one slot (or sub-slot) , the PUCCH with a lower priority is dropped. For example, the priority order may be set as: A / N>SR>CSI>sensing result, or, A / N>SR> sensing result>CSI. It is to be understood that the priority order may be set in a different order, the present disclosure does not limit this aspect.
[0181] In some example embodiments, the DCI may schedule a PDSCH with multiple repetitions or multiple PDSCHs in one cell (or multiple cells) , and some or all of the PDSCH with multiple repetitions or multiple PDSCHs are used for sensing, then the sensing result may indicate a channel change between two continuous repetitions among the multiple repetitions or between two continuous PDSCHs among the multiple PDSCHs. For example, the sensing result may indicate a CQI changing, PMI changing, RI changing, or some other values.
[0182] In some other example embodiments, the UE 104 may determine that the sensing result is transmitted over PUSCH. In some embodiments, the UE 104 may determine a PUSCH resource for transmitting the sensing result.
[0183] In some examples, the PUSCH resource may be a CG PUSCH indicated by the DCI. For example, the DCI may indicate a CG ID, and the CG PUSCH with the CG ID may be used for a scheduled PUSCH, then the sensing result may be transmitted on the CG PUSCH. In some examples, a slot (or sub-slot) for transmission of the sensing result may be determined, for example, the sloe (or sub-slot) may be represented as n+K0. For example, n is determined based on a last PDSCH for sensing discussed above. For example, K0 is determined based on a specific field, such as a newly defined field or the HARQ-ACK timing field in the DCI.
[0184] In some examples, the PUSCH resource may be a nearest CG PUSCH with a smallest CG ID. In some examples, the PUSCH resource may be a nearest CG PUSCH with a configured CG ID. For example, a time duration between the nearest CG PUSCH and the PUSCH resource may be greater than a predefined time length, such as N2 symbols, N2 ms, or the like.
[0185] In some examples, the PUSCH resource may be a PUSCH resource scheduled by a UL grant. For example, the UL grant may be included in a PDSCH which is scheduled by a DCI.
[0186] In some implementations, if the PDSCH or the DMRS (s) of the PDSCH is used for sensing only, or in other words not used for communication, then the HARQ-ACK information for that PDSCH will be included in the HARQ-ACK codebook.
[0187] In some implementations, if the PDSCH or the DMRS (s) of the PDSCH is used for both sensing and communication (i.e. ISAC) , then the HARQ-ACK information for the PDSCH may be transmitted.
[0188] In some examples, the HARQ-ACK information may be feedback in a legacy way. For example, if the DCI schedules a PDSCH with multiple repetitions or multiple PDSCH transmissions, some of the multiple repetitions or multiple PDSCH transmissions are for sensing, and other some of the multiple repetitions or multiple PDSCH transmissions are for communication, then a slot (or sub-slot) for transmitting the HARQ-ACK information may be determined based on a last PDSCH repetition or a last PDSCH transmission that for communication. For example, the sensing result and the HARQ-ACK information may be transmitted separately.
[0189] In some examples, the HARQ-ACK information may be implicitly indicated, for example, the HARQ-ACK information may not be transmitted while the sensing result is transmitted. On the side of network entity 102, if the sensing result is received, it may determine that the HARQ-ACK information for the PDSCH is ACK; otherwise, if none of the sensing result or the HARQ-ACK information is received, it may determine that the HARQ-ACK information for the PDSCH is NACK.
[0190] In some examples, the HARQ-ACK information may be joint encoded with the sensing result, e.g., a joint (or combination) of the HARQ-ACK information and the sensing result is transmitted on the resource that determined at step 430. For example, a new type of UCI may be defined for the joint of the HARQ-ACK information and the sensing result. For example, a priority of the new type of UCI may be higher than a priority of A / N.
[0191] On the other side of communication, the network entity 102 receives the sensing result at step 440. In some implementations, the network entity 102 may determine a resource for the reception of the sensing result, and may receive the sensing result based on the determined resource. In some example embodiments, the determination of the resource at the network entity 102 is similar with a determination of the resource at the UE 104 at the step 430, and thus will not be repeated here for brevity.
[0192] The embodiments discussed above assume that the downlink information is indicted to be used for sensing (such as sensing only, or both sensing and communication) , in some other examples, the indication may indicate that the downlink information is used for communication only (not for sensing) , in this case, the UE 104 may receive the downlink information and perform decoding as legacy, that is, the steps 420-440 may be omitted.
[0193] Continue referring to FIG. 4, in the operation 451, the UE 104 generates uplink information by using a sensing based method at step 450 if the indication indicates to use uplink information for sensing. In addition, the UE 104 transmits the uplink information to the network entity 102 at step 455.
[0194] In some examples, if the indication indicates that a PUSCH is used for sensing, the UE 104 may transmit the PUSCH using a specific method, such as a sensing based method. For example, the UE 104 may determine that the PUSCH should be transmitted with a waveform different from OFDM, such as LMF, OTFS, or the PUSCH may be transmitted with extended CP.
[0195] In addition, the network entity 102 performs sensing at step 460 based on received uplink information.
[0196] FIG. 5A illustrates a schematic diagram of a DCI 510 indicating sensing in accordance with aspects of the present disclosure. The DCI includes one bit field, and the bit field may indicate a function as sensing, e.g. to used downlink information or uplink information for sensing.
[0197] FIG. 5B illustrates a schematic diagram of a DCI 520 indicating communication in accordance with aspects of the present disclosure. The DCI includes one bit field, and the bit field may indicate a function as communication, e.g. to used downlink information or uplink information for sensing.
[0198] FIG. 5C illustrates a schematic diagram of a DCI 530 indicating ISAC in accordance with aspects of the present disclosure. The DCI includes one bit field, and the bit field may indicate a function as ISAC, e.g. to used downlink information or uplink information for both sensing and communication.
[0199] FIG. 5D illustrates a schematic diagram of a DCI 540 indicating sensing and communication for different channels respectively in accordance with aspects of the present disclosure. For example, the DCI schedules 2 codewords in one cell, the DCI includes two bit fields, one bit field may indicate a function as communication for one codeword, and the other bit field may indicate a function as sensing for the other codeword.
[0200] FIG. 5E illustrates a schematic diagram of a DCI 550 scheduling multiple PUSCH repetitions with type A in accordance with aspects of the present disclosure. For example, the DCI schedules a PUSCH with m repetition A, the DCI includes m bit fields corresponding to the m repetitions. As shown in FIG. 5E, there are 4 PUSCH repetitions, with the functions sensing, communication, ISAC, and communication respectively.
[0201] FIG. 5F illustrates a schematic diagram of a DCI 560 scheduling multiple PUSCH repetitions with type B in accordance with aspects of the present disclosure. For example, the DCI schedules a PUSCH with m repetition B, the DCI includes m bit fields corresponding to the m repetitions. As shown in FIG. 5F, there are 4 PUSCH repetitions (actual repetitions) , with the functions sensing, communication, ISAC, and communication respectively. For example, the first actual repetition may include a first part 561 and a second part 562.
[0202] FIG. 5G illustrates a schematic diagram of a DCI 570 scheduling multiple channels for multiple cells in accordance with aspects of the present disclosure. For example, the DCI schedules multiple PUSCHs in multiple cells, the DCI may include multiple bit fields corresponding to the multiple PUSCHs in multiple cells. As shown in FIG. 5G, there are 4 PUSCHs in 4 cells, with the functions sensing, communication, ISAC, and communication respectively.
[0203] FIG. 6 illustrates a schematic diagram of feedback 600 in accordance with aspects of the present disclosure. For a PDSCH for sensing, the sensing result may be transmitted on PUCCH / PUSCH. For a PDSCH for communication, the HARQ-ACK feedback may be transmitted on PUCCH. For a PDSCH for both sensing and communication, the sensing result may be transmitted on PUCCH / PUSCH and the HARQ-ACK feedback may be transmitted on PUCCH. It is to be understood that the examples shown in figures are only for illustrative purpose without any limitation.
[0204] According to some embodiments with reference to FIGS. 3-6, an indication of whether to use the downlink information for sensing or whether to use uplink information for sensing may be provided to the UE, as such, the UE 104 may be aware of how to handle the downlink information or the uplink information. In this way, the efficiency for the sensing and the communication may be guaranteed.
[0205] FIG. 7 illustrates an example of a device 700 in accordance with aspects of the present disclosure. The device 700 may be an example of a network entity 102 or a UE 104 as described herein. The device 700 may support wireless communication with a network entity 102, a UE 104, or any combination thereof. The device 700 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 702, a memory 704, a transceiver 706, and, optionally, an I / O controller 708. 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) .
[0206] The processor 702, the memory 704, the transceiver 706, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 702, the memory 704, the transceiver 706, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
[0207] In some implementations, the processor 702, the memory 704, the transceiver 706, 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. In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704) .
[0208] For example, the processor 702 may support wireless communication at the device 700 in accordance with examples as disclosed herein. The processor 702 may be configured to operable to support a means for operations discussed above.
[0209] The processor 702 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) . In some implementations, the processor 702 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 704) to cause the device 700 to perform various functions of the present disclosure.
[0210] The memory 704 may include random access memory (RAM) and read-only memory (ROM) . The memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 702 cause the device 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. In some implementations, the code may not be directly executable by the processor 702 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 704 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.
[0211] The I / O controller 708 may manage input and output signals for the device 700. The I / O controller 708 may also manage peripherals not integrated into the device 700. In some implementations, the I / O controller 708 may represent a physical connection or port to an external peripheral. In some implementations, the I / O controller 708 may utilize an operating system such as or another known operating system. In some implementations, the I / O controller 708 may be implemented as part of a processor, such as the processor 702. In some implementations, a user may interact with the device 700 via the I / O controller 708 or via hardware components controlled by the I / O controller 708.
[0212] In some implementations, the device 700 may include a single antenna 710. However, in some other implementations, the device 700 may have more than one antenna 710 (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 706 may communicate bi-directionally, via the one or more antennas 710, wired, or wireless links as described herein. For example, the transceiver 706 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 706 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 710 for transmission, and to demodulate packets received from the one or more antennas 710. The transceiver 706 may include one or more transmit chains, one or more receive chains, or a combination thereof.
[0213] 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 710 for transmitting the amplified signal into the air or wireless medium.
[0214] A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 710 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.
[0215] FIG. 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure. The processor 800 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein. The processor 800 may optionally include at least one memory 804, such as L1 / L2 / L3 cache. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic-logic units (ALUs) 806. 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) .
[0216] The processor 800 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. 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 800) 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) .
[0217] The controller 802 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 800 to cause the processor 800 to support various operations in accordance with examples as described herein. For example, the controller 802 may operate as a control unit of the processor 800, generating control signals that manage the operation of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0218] The controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine subsequent instruction (s) to be executed to cause the processor 800 to support various operations in accordance with examples as described herein. The controller 802 may be configured to track memory address of instructions associated with the memory 804. The controller 802 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 802 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 802 may be configured to manage flow of data within the processor 800. The controller 802 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 800.
[0219] The memory 804 may include one or more caches (e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800) . In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800) .
[0220] The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 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 controller 802 and / or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions. For example, the processor 800 and / or the controller 802 may be coupled with or to the memory 804, the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein. In some examples, the processor 800 may include multiple processors and the memory 804 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.
[0221] The one or more ALUs 806 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 806 may reside within or on a processor chipset (e.g., the processor 800) . In some other implementations, the one or more ALUs 806 may reside external to the processor chipset (e.g., the processor 800) . One or more ALUs 806 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 806 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 806 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 806 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.
[0222] The processor 800 may support wireless communication in accordance with examples as disclosed herein. The processor 800 may be configured to or operable to support a means for operations described in some embodiments of the present disclosure.
[0223] FIG. 9 illustrates a flowchart of a method 900 implemented at a UE 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. For example, the operations of the method 900 may be performed by the UE 104 in FIG. 3. In some implementations, 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.
[0224] At 910, the method may include receiving, from a network entity, an indication of whether to use downlink information or uplink information for sensing. 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 the UE 104 as described with reference to FIG. 3.
[0225] At 920, the method may include performing sensing based at least in part on the received indication indicating to use the downlink information for sensing or transmitting the uplink information to the network entity based at least in part on the received indication indicating to use the uplink information for sensing. 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 the UE 104 as described with reference to FIG. 3.
[0226] FIG. 10 illustrates a flowchart of a method 1000 implemented at a network entity 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. For example, the operations of the method 1000 may be performed by the network entity 102 in FIG. 3. In some implementations, 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.
[0227] At 1010, the method may include transmitting, to a UE, an indication of whether to use downlink information or uplink information for sensing. 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 the network entity 102 as described with reference to FIG. 3.
[0228] At 1020, the method may include performing sensing based at least in part on the indication indicating to use the uplink information for sensing or transmitting the downlink information to the UE based at least in part on the indication indicating to use the downlink information for sensing. 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 the network entity 102 as described with reference to FIG. 3.
[0229] It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.
[0230] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. 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.
[0231] 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.
[0232] 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. By way of example, 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.
[0233] As used herein, including in the claims, 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. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) 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) . Also, as used herein, 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. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.
[0234] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
Claims
1.A user equipment (UE) comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the UE to:receive, from a network entity, an indication of whether to use downlink information or uplink information for sensing; andperform the sensing based at least in part on the received indication indicating to use the downlink information for sensing or transmit the uplink information to the network entity based at least in part on the received indication indicating to use the uplink information for sensing.2.The UE of claim 1, wherein whether to use the downlink information or the uplink information for sensing comprises one of:the downlink information is used for sensing or not,the downlink information is used for communication or sensing,the downlink information is used for both sensing and communication or only used for communication,the downlink information is used for both sensing and communication or only used for communication or only used for sensing,the uplink information is used for sensing or not,the uplink information is used for communication or sensing,the uplink information is used for both sensing and communication or only used for communication, orthe uplink information is used for both sensing and communication or only used for communication or only used for sensing.3.The UE of claim 1, wherein the indication comprises a bit field in a downlink control information (DCI) , and wherein the bit field indicates one of:whether M downlink channels scheduled by the DCI are used for sensing,whether demodulation reference signals (DMRSs) of the M downlink channels scheduled by the DCI are used for sensing,whether M uplink channels scheduled by the DCI are used for sensing, orwhether DMRSs of the M uplink channels scheduled by the DCI are used for sensing,wherein M is an integer value.4.The UE of claim 1, wherein the indication comprises a time domain resource assignment (TDRA) field of a DCI.5.The UE of claim 4, wherein the TDRA field indicates a row of a plurality of rows of a table, and each row of the plurality of rows indicates:M time domain resources for M channels, wherein the M channels comprises M downlink channels or M uplink channels, andwhether each channel among the M channels or DMRSs of each channel among the M channels is used for sensing,wherein M is an integer value.6.The UE of claim 3 or 5, wherein,the M downlink channels comprise one of: one physical downlink shared channel (PDSCH) , a PDSCH with M repetitions, M PDSCHs in one cell, M PDSCHs in M cells, M codewords in one cell, or M semi-persistent scheduling (SPS) PDSCHs,the M uplink channels comprises one of: one physical uplink shared channel (PUSCH) , a PUSCH with M repetitions, M PUSCHs in one cell, M PUSCHs in M cells, M PUSCHs for one transmission block (TB) , or M type 2 configured grant (CG) PUSCHs.7.The UE of claim 6, wherein the DCI further indicates:M transmission control indicators (TCIs) for M PDSCHs, orM sounding reference signal resource indicators (SRIs) for M PUSCHs.8.The UE of claim 1, wherein the indication comprises M parameters in radio resource control (RRC) signalling, and wherein the M parameters are used for indicating one of:whether M CG PUSCHs configured by the RRC signalling in a period are used for sensing,whether M SPS PDSCHs configured by the RRC signalling in a period are used for sensing,whether DMRSs of the M CG PUSCHs configured by the RRC signalling in a period are used for sensing,whether DMRSs of the M SPS PDSCHs configured by the RRC signalling in a period are used for sensing,whether M downlink reference signals configured by the RRC signalling in a period are used for sensing,whether M uplink reference signals configured by the RRC signalling in a period are used for sensing, orwhether M data channels or DMRSs of the M data channels in M cells configured by the RRC signaling are used for sensing,wherein M is an integer value.9.The UE of claim 1, wherein the indication indicates to use the downlink information for sensing, and the indication is carried in a DCI being used for scheduling M downlink channels, and wherein the at least one processor is further configured to cause the UE to:generate a sensing result by performing sensing based on the downlink information;determine a resource for a transmission of the sensing result; andtransmit, to the network entity, the sensing result by using the resource.10.The UE of claim 9, wherein the UE being caused to determine the resource comprises being caused to:determine a slot or sub-slot for the transmission of the sensing result; anddetermine a physical uplink control channel (PUCCH) resource in the slot or sub-slot.11.The UE of claim 10, wherein the slot or sub-slot is determined based on:a specific slot or sub-slot in which a last PDSCH or a last repetition which is scheduled by the DCI and is used for sensing is, anda difference value.12.The UE of claim 11, wherein the difference value is one of:a value indicated by a hybrid automatic repeat request acknowledgement (HARQ-ACK) timing field in the DCI,a value indicated by a specific field in the DCI,a value predefined,a value preconfigured by an RRC parameter,a value indicated in an uplink grant, ora sum of a value indicated by the HARQ-ACK timing field and a predefined or preconfigured offset.13.The UE of claim 10, wherein the UE being caused to determine the PUCCH resource comprises being caused to:determine the PUCCH resource from a set of PUCCH resources based on a number of bits of the sensing result.14.The UE of claim 10, wherein the UE being caused to determine the PUCCH resource comprises being caused to:determine a set of PUCCH resources from a plurality of sets of PUCCH resources based on a number of bits of the sensing result; anddetermine the PUCCH resource from the set of PUCCH resources based on a PUCCH resource indication (PRI) field in the DCI.15.The UE of claim 9, wherein the UE being caused to determine the resource comprises being caused to:determine a PUSCH resource for the transmission of the sensing result, wherein the PUSCH resource comprises one of:a CG PUSCH indicated by the DCI,a nearest CG PUSCH with a smallest CG identifier, ora PUSCH resource scheduled by an uplink grant included in a PDSCH which is scheduled by the DCI.16.The UE of claim 9, wherein the at least one processor is further configured to cause the UE to:in accordance with a determination that the indication indicates that a PDSCH is used for both sensing and communication, determine that a HARQ-ACK of the PDSCH is: transmitted, omitted, or be jointed with the sensing result.17.The UE of claim 1, wherein the at least one processor is further configured to cause the UE to:transmit, to the network entity, information about a plurality of sensing modes supported by the UE; andreceive, from the network entity, a notification indicating a specific sensing mode among the plurality of sensing modes.18.The UE of claim 1, wherein the indication indicates to use the uplink information for sensing, and wherein the at least one processor is further configured to cause the UE to:generate the uplink information based on a sensing based method; andtransmit, to the network entity, the uplink information.19.A network entity comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the network entity to:transmit, to a user equipment (UE) , an indication of whether to use downlink information or uplink information for sensing; andperform the sensing based at least in part on the indication indicating to use the uplink information for sensing or transmit the downlink information to the UE based at least in part on the indication indicating to use the downlink information for sensing.20.A method performed by a user equipment (UE) , comprising:receiving, from a network entity, an indication of whether to use downlink information or uplink information for sensing; andperforming the sensing based at least in part on the received indication indicating to use the downlink information for sensing or transmitting the uplink information to the network entity based at least in part on the received indication indicating to use the uplink information for sensing.
Citation Information
Patent Citations
Adaptive sensing mechanism for unlicensed networks
CN113261376A
Method and apparatus for channel sensing indication
CN117042165A
Conditional configured grant (CG) occasions for uplink transmission
US11570806B2
Channel sensing
US20230217488A1
