[go: up one dir, main page]

WO2025111847A1 - Techniques de signalisation pour réduction de latence de procédures de gestion de faisceau - Google Patents

Techniques de signalisation pour réduction de latence de procédures de gestion de faisceau Download PDF

Info

Publication number
WO2025111847A1
WO2025111847A1 PCT/CN2023/135006 CN2023135006W WO2025111847A1 WO 2025111847 A1 WO2025111847 A1 WO 2025111847A1 CN 2023135006 W CN2023135006 W CN 2023135006W WO 2025111847 A1 WO2025111847 A1 WO 2025111847A1
Authority
WO
WIPO (PCT)
Prior art keywords
dci
csi
slot
pucch
field
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/135006
Other languages
English (en)
Inventor
Hong He
Ankit Bhamri
Chunhai Yao
Chunxuan Ye
Dawei Zhang
Haitong Sun
Wei Zeng
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Inc filed Critical Apple Inc
Priority to PCT/CN2023/135006 priority Critical patent/WO2025111847A1/fr
Publication of WO2025111847A1 publication Critical patent/WO2025111847A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0027—Scheduling of signalling, e.g. occurrence thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0028—Formatting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling

Definitions

  • the present disclosure generally relates to wireless communication, and in particular, to signaling techniques for latency reduction of beam management procedures.
  • a user equipment (UE) and a network may utilize beam management procedures to acquire and maintain beams for wireless communication. It has been identified that the beam management procedures introduce latency that may cause throughput performance degradation in various types of deployment scenarios.
  • Some example embodiments are related to an apparatus of a user equipment (UE) , the apparatus including processing circuitry configured to decode, based on signaling received from a base station, downlink control information (DCI) for uplink resource allocation, the DCI comprising a first field configured to provide a transmission configuration indicator (TCI) update and a second field configured to trigger aperiodic channel state information (CSI) reporting and configure transceiver circuitry to transmit one or more CSI reports using physical uplink shared channel (PUSCH) resources indicated by the DCI.
  • DCI downlink control information
  • TCI transmission configuration indicator
  • CSI periodic channel state information
  • DCI downlink control information
  • CSI channel state information
  • Fig. 1 shows an example network arrangement according to various example embodiments.
  • Fig. 2 shows an example user equipment (UE) according to various example embodiments.
  • Fig. 3 shows an example base station according to various example embodiments.
  • Fig. 4 shows a method for beam management according to various example embodiments.
  • Fig. 5 shows a first example downlink control information (DCI) according to various example embodiments.
  • DCI downlink control information
  • Fig. 6 shows examples of a slot offset for the triggered channel state information (CSI) -reference signal (RS) resource set according to various example embodiments.
  • CSI channel state information
  • RS reference signal
  • Fig. 7 shows a method for beam management according to various example embodiments.
  • Fig. 8 shows a second example DCI according to various example embodiments.
  • Fig. 9 shows a third example DCI according to various example embodiments.
  • the example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals.
  • the example embodiments introduce signaling techniques that reduce the latency associated with beam management.
  • the example embodiments are described with regard to a user equipment (UE) .
  • UE user equipment
  • reference to a UE is merely provided for illustrative purposes.
  • the example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and/or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.
  • the example embodiments are also described with regard to beam management in a Fifth Generation (5G) New Radio (NR) network.
  • 5G NR is merely provided for illustrative purposes.
  • the example embodiments may be utilized with any appropriate type of network, e.g., 5G-advanced network, 6G network, etc.
  • beam management procedures such as beam update, beam measurement and beam reporting may be performed sequentially.
  • the sequential performance of beam management procedures may increase the latency and/or signaling overhead associated with beam management.
  • a first procedure may be performed to update the beam direction.
  • the network may transmit a beam indication to the UE, the UE may transmit an acknowledgement in response to the beam indication and then after beam application time the updated beam is applied at the UE.
  • a second procedure may be performed for beam measurement and beam reporting.
  • the network may trigger aperiodic channel state information (CSI) reporting at the UE and after an offset duration, CSI measurement resources corresponding to one or more neighbor cells may be provided.
  • CSI channel state information
  • the UE may compile CSI reports corresponding to one or neighbor cells and then transmit the CSI reports to the network. For any of a variety of reasons, a scenario may occur where the updated beam is no longer the best beam to serve the UE. However, the UE will not be able to update the beam for a second time until after the beam reporting procedure is complete, another beam indication is received and the corresponding beam is applied at the UE.
  • the example embodiments introduce signaling techniques for latency reduction of beam management.
  • the example embodiments may be used independently from one another, in conjunction with currently implemented beam management techniques, in conjunction with future implementations of beam management techniques or independently from other beam management techniques.
  • Fig. 1 shows an example network arrangement 100 according to various example embodiments.
  • the example network arrangement 100 includes a UE 110.
  • the UE 110 may be any type of electronic component that is configured to communicate via a network, e.g., mobile phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things (IoT) devices, etc.
  • IoT Internet of Things
  • an actual network arrangement may include any number of UEs being used by any number of users.
  • the example of a single UE 110 is merely provided for illustrative purposes.
  • the UE 110 may be configured to communicate with one or more networks.
  • the network with which the UE 110 may wirelessly communicate is a 5G NR radio access network (RAN) 120.
  • RAN radio access network
  • the UE 110 may also communicate with other types of networks (e.g., sixth generation (6G) RAN, 5G cloud RAN, a next generate RAN (NG-RAN) , a legacy cellular network, a wireless local area network (WLAN) , etc. ) and the UE 110 may also communicate with networks over a wired connection. Therefore, the UE 110 may have a 5G NR chipset to communicate with the NR RAN 120 and, optionally, any other appropriate type of chipset to communicate with other types of networks.
  • 6G sixth generation
  • NG-RAN next generate RAN
  • WLAN wireless local area network
  • the 5G NR RAN 120 may be a portion of a cellular network that may be deployed by a network carrier (e.g., Verizon, AT&T, Sprint, T-Mobile, etc. ) .
  • the 5G NR RAN 120 may include base stations that are configured to send and receive traffic from UEs that are equipped with the appropriate cellular chip set.
  • the 5G NR RAN 120 includes the gNB 120A.
  • a gNB is merely provided for illustrative purposes, the example embodiments may be utilized with any appropriate type of access node (e.g., Node Bs, eNodeBs, HeNBs, eNBs, gNBs, gNodeBs, macrocells, microcells, small cells, femtocells, etc. ) .
  • access node e.g., Node Bs, eNodeBs, HeNBs, eNBs, gNBs, gNodeBs, macrocells, microcells, small cells, femtocells, etc.
  • any association procedure may be performed for the UE 110 to connect to the 5G NR RAN 120.
  • the 5G NR RAN 120 may be associated with a particular network carrier where the UE 110 and/or the user thereof has a contract and credential information (e.g., stored on a SIM card) .
  • the UE 110 may transmit the corresponding credential information to associate with the 5G NR RAN 120. More specifically, the UE 110 may associate with a specific cell (e.g., the gNB 120A) .
  • the network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160.
  • the cellular core network 130 may refer an interconnected set of components that manages the operation and traffic of the cellular network.
  • the cellular core network 130 also manages the traffic that flows between the cellular network and the Internet 140.
  • the IMS 150 may be generally described as an architecture for delivering multimedia services to the UE 110 using the IP protocol.
  • the IMS 150 may communicate with the cellular core network 130 and the Internet 140 to provide the multimedia services to the UE 110.
  • the network services backbone 160 is in communication either directly or indirectly with the Internet 140 and the cellular core network 130.
  • the network services backbone 160 may be generally described as a set of components (e.g., servers, network storage arrangements, etc. ) that implement a suite of services that may be used to extend the functionalities of the UE 110 in communication with the various networks.
  • Fig. 2 shows an example UE 110 according to various example embodiments.
  • the UE 110 will be described with regard to the network arrangement 100 of Fig. 1.
  • the UE 110 may include a processor 205, a memory arrangement 210, a display device 215, an input/output (I/O) device 220, a transceiver 225 and other components 230.
  • the other components 230 may, for example, an audio input device, an audio output device, a power supply, a data acquisition device, ports to electrically connect the UE 110 to other electronic devices, etc.
  • the processor 205 may be configured to execute a plurality of engines of the UE 110.
  • the engines may include a beam management engine 235.
  • the management engine 235 may perform various operations related to beam management such as, but not limited to, receiving DCI, receiving measurement resources, collecting measurement data, compiling CSI reports and transmitting the CSI reports to the network.
  • the above referenced engine 235 being an application (e.g., a program) executed by the processor 205 is merely provided for illustrative purposes.
  • the functionality associated with the engine 235 may also be represented as a separate incorporated component of the UE 110 or may be a modular component coupled to the UE 110, e.g., an integrated circuit with or without firmware.
  • the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information.
  • the engines may also be embodied as one application or separate applications.
  • the functionality described for the processor 205 is split among two or more processors such as a baseband processor and an applications processor. The example embodiments may be implemented in any of these or other configurations of a UE.
  • the memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110.
  • the display device 215 may be a hardware component configured to show data to a user while the I/O device 220 may be a hardware component that enables the user to enter inputs.
  • the display device 215 and the I/O device 220 may be separate components or integrated together such as a touchscreen.
  • the transceiver 225 may be a hardware component configured to establish a connection with the 5G NR-RAN 120, an LTE-RAN (not pictured) , a legacy RAN (not pictured) , a WLAN (not pictured) , etc. Accordingly, the transceiver 225 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies) .
  • the transceiver 225 includes circuitry configured to transmit and/or receive signals (e.g., control signals, data signals) . Such signals may be encoded with information implementing any one of the methods described herein.
  • the processor 205 may be operably coupled to the transceiver 225 and configured to receive from and/or transmit signals to the transceiver 225.
  • the processor 205 may be configured to encode and/or decode signals (e.g., signaling from a base station of a network) for implementing any one of the methods described herein.
  • Fig. 3 shows an example base station 300 according to various example embodiments.
  • the base station 300 may represent the gNB 120A or any other access node through which the UE 110 may establish a connection and manage network operations.
  • the base station 300 may include a processor 305, a memory arrangement 310, an input/output (I/O) device 315, a transceiver 320 and other components 325.
  • the other components 325 may include, for example, a power supply, a data acquisition device, ports to electrically connect the base station 300 to other electronic devices and/or power sources, etc.
  • the processor 305 may be configured to execute a plurality of engines of the base station 300.
  • the engines may include a beam management engine 330.
  • the beam management engine 330 may perform various operations related to beam management such as, but not limited to, transmitting DCI and receiving CSI reports.
  • the above noted engine 330 being an application (e.g., a program) executed by the processor 305 is only example.
  • the functionality associated with the engine 330 may also be represented as a separate incorporated component of the base station 300 or may be a modular component coupled to the base station 300, e.g., an integrated circuit with or without firmware.
  • the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information.
  • the functionality described for the processor 305 is split among a plurality of processors (e.g., a baseband processor, an applications processor, etc. ) .
  • the example embodiments may be implemented in any of these or other configurations of a base station.
  • the memory 310 may be a hardware component configured to store data related to operations performed by the base station 300.
  • the I/O device 315 may be a hardware component or ports that enable a user to interact with the base station 300.
  • the transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UE in the network arrangement 100.
  • the transceiver 320 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies) .
  • the transceiver 320 includes circuitry configured to transmit and/or receive signals (e.g., control signals, data signals) . Such signals may be encoded with information implementing any one of the methods described herein.
  • the processor 305 may be operably coupled to the transceiver 320 and configured to receive from and/or transmit signals to the transceiver 320.
  • the processor 305 may be configured to encode and/or decode signals (e.g., signaling from a UE) for implementing any one of the methods described herein.
  • the example embodiments introduce enhancements for downlink control information (DCI) that is used for uplink resource allocation.
  • DCI downlink control information
  • This enhanced DCI may reduce latency and improve performance of beam management procedures.
  • the DCI may be DCI format 0_1 or DCI format 0_2.
  • any reference to a particular type of DCI is merely provided for illustrative purposes.
  • the example embodiments may utilize any other appropriate type of DCI that is used for uplink resource allocation.
  • Fig. 4 shows a method 400 for beam management according to various example embodiments.
  • the method 400 includes explicit signaling techniques introduced herein that may be used to reduce latency and improve performance with regard to beam management.
  • the method 400 is described from the perspective of the UE 110 of the network arrangement 100 in Fig. 1.
  • the UE 110 receives DCI from the network that is configured for physical uplink shared channel (PUSCH) resource allocation.
  • the DCI may be DCI format 0_1, DCI format 0_2 or any other appropriate type of DCI that is used for uplink resource allocation.
  • the example embodiments introduce a transmission configuration indicator (TCI) field that may be added to the DCI.
  • TCI field may include information to be used by the UE 110 to select an activated TCI state for a beam update. The updated beam may then be applied at the UE 110.
  • the DCI may also include a channel state information (CSI) -request field that is configured to trigger aperiodic CSI reporting.
  • the UE 110 may transmit CSI reports corresponding to one or more cells on the PUSCH resources allocated to the UE 110 in the DCI 405.
  • CSI channel state information
  • Fig. 5 shows an example DCI 500 according to various example embodiments.
  • the DCI 500 includes a TCI field 510.
  • a 3-bit TCI field may be used.
  • the TCI field may be any appropriate size.
  • the DCI 500 further includes a CSI request field 515, legacy DCI fields 520 (e.g., existing fields in DCI format 0_1, DCI format 0_2, etc. ) and cyclic redundancy check (CRC) 525.
  • the DCI 500 is provided to illustrate one example of a structure that may be used to implement the example DCI introduced herein and is not intended to limit the example embodiments in any way.
  • the example DCI may be configured in any appropriate manner.
  • the UE 110 transmits physical uplink control channel (PUCCH) to the network in response to the DCI.
  • PUCCH physical uplink control channel
  • the UE 110 transmits PUCCH with a hybrid automatic repeat request (HARQ) feedback in slot (n) corresponding to the DCI.
  • HARQ feedback may include an acknowledgement (ACK) that is configured to indicate to the network that the UE 110 has received the TCI update and/or applied the updated beam.
  • ACK acknowledgement
  • NACK negative ACK
  • a scheduling request may be transmitted by the UE 110 on the PUCCH instead of an ACK.
  • the SR may serve as an ACK while also requesting additional uplink and/or downlink resources.
  • he SR transmission may use PUCCH format 0, PUCCH format 1 or any other appropriate type of PUCCH format.
  • the UE 110 may determine the uplink resources on which to transmit the PUCCH based on DCI, configuration information previously received via RRC signaling and/or configuration information provided in any other appropriate manner.
  • parameters such as, but not limited to, uplink bandwidth part (BWP) ID, PUCCH resource ID, PUCCH slot offset and/or PUCCH slot offset list may be provided to the UE 110 by the network.
  • the PUCCH slot offset list may include a plurality of slot offsets to ensure sufficient flexibility.
  • the example embodiments introduce an offset indicator field that may be added to DCI.
  • the offset indicator field may include information configured to indicate a slot offset relative to the DCI on which the PUCCH is to be transmitted.
  • any appropriate type of information may be used to determine the PUCCH resources for the ACK and/or SR.
  • the UE 110 receives beam measurement resources.
  • the UE 110 may be configured with one or more CSI-reference signal (RS) resource sets that are to be used for beam measurement of one or more neighbor cells.
  • the CSI-RS resource set may include synchronization signal block (SSB) , CSI-RS and/or any other appropriate type of measurement resource. Additional details regarding the CSI-RS resource set are provided below after the description of the method 400.
  • the gNB 120A may decode the PUCCH ACK or SR from the UE 110 and then trigger the CSI-RS resource set. However, if the gNB 120A does not receive the PUCCH, the gNB 120A may assume that the UE 110 did not receive the DCI in 405. As a result, the gNB 120A may not transmit the CSI-RS resource set to the UE 110. Accordingly, the lack of PUCCH ACK or SR in response to the TCI update in the DCI may allow the network to avoid the unnecessary transmission of the CSI-RS resource set and thus, limit signaling overhead.
  • the UE 110 transmits one or more CSI reports to the network on the PUSCH resources allocated to the UE 110 by the DCI received in 405 using the updated beam.
  • the one or more CSI reports may be based on the CSI-RS resource set and include beam measurements for one or more beams, e.g., beam reporting.
  • the UE 110 may not transmit the PUCCH in response to the DCI 405. Instead, the PUSCH transmission in 420 may serve as the ACK for the TCI state update provided by the TCI field of the DCI. Compared to the example described in the method 400, this approach has less uplink signaling overhead. In this scenario, the UE 110 may always assume that the triggered CSI-RS resource sets are transmitted by the network after the DCI is detected.
  • the UE 110 may know where the CSI-RS resource set is located based on a slot offset parameter (T offset ) .
  • the slot offset (T offset ) for the triggered CSI-RS resource set may be configured by higher layer signaling and may be defined in a variety of different ways.
  • the slot offset (T offset ) may be defined relative to the slot containing the DCI that triggers the CSI-RS resource set (e.g., the DCI received in 405) .
  • the slot offset (T offset ) may be defined relative to the slot where PUCCH comprising the ACK and/or SR is transmitted (e.g., the PUCCH transmitted in 410) . Examples of both of these approaches are shown below in Fig. 6.
  • Fig. 6 shows examples of a slot offset for the triggered CSI-RS resource set according to various example embodiments.
  • Fig. 6 includes a timeline 600 comprising DCI 605, PUCCH 610, a CSI-RS resource set 615 and PUSCH 620.
  • the slot offset (T offset ) for the CSI-RS resource set may be defined relative to the slot containing the DCI that triggers the CSI-RS resource set.
  • the UE 110 may receive the DCI 605 and in response, transmit the PUCCH 610 comprising an ACK or SR. After the PUCCH, the UE 110 may apply the updated beam in 611.
  • the slot of the DCI 605 may also define the slot offset 625 for the CSI-RS resource set that is to be used for beam measurement.
  • the UE 110 may then use the PUSCH 620 indicated by the DCI 605 for beam reporting.
  • Fig. 6 also includes a timeline 650 comprising DCI 655, PUCCH 660, a CSI-RS resource set 665 and PUSCH 670.
  • the slot offset (T offset ) for the CSI-RS resource set may be defined relative to the PUCCH transmitted in response to the DCI.
  • the UE 110 may receive the DCI 655 and in response, transmit the PUCCH 660 comprising an ACK or SR. After the PUCCH, the UE 110 may apply the updated beam in 661
  • the slot of the PUCCH 660 may also define the slot offset 675 for the CSI-RS resource set that is to be used for beam measurement.
  • the UE 110 may then use the PUSCH 670 indicated by the DCI 655 for beam reporting.
  • the smaller offset means less candidate values for the offset may be signaled to the UE 110 and thus, signaling overhead may be limited.
  • the example embodiments introduce enhancements for DCI that is used for downlink resource allocation.
  • This enhanced DCI may be used to reduce the latency and improve performance of beam management procedures.
  • the DCI may be DCI format 1_1 or DCI format 1_2.
  • any reference to a particular type of DCI is merely provided for illustrative purposes.
  • the example embodiments may utilize any other appropriate type of DCI that is used for downlink resource allocation.
  • Fig. 7 shows a method 700 for beam management according to various example embodiments.
  • the method 700 includes explicit signaling techniques introduced herein that may be used to reduce latency and improve performance with regard to beam management.
  • the method 700 is described from the perspective of the UE 110 of the network arrangement 100 in Fig. 1.
  • the UE 110 receives DCI from the network that is configured for downlink resource allocation.
  • the DCI may be DCI format 1_1, DCI format 1_2 or any other appropriate type of DCI that is used for downlink resource allocation.
  • the UE 110 may, optionally, be configured with PUCCH resources to transmit HARQ feedback in response to the DCI.
  • the DCI may include a TCI field comprising a TCI update for the downlink resource assignment.
  • the example embodiments introduce a CSI request field for the DCI that is configured to trigger aperiodic CSI reporting.
  • DCI format 1_1 and DCI format 1_2 may be without a downlink resource assigned for the TCI update.
  • the CSI request configured to trigger aperiodic CSI reporting may be introduced by repurposing one or more of the legacy DCI fields including, but not limited to, modulation coding scheme (MCS) field, redundancy version (RV) field or the frequency domain resource assignment (FDRA) field.
  • MCS modulation coding scheme
  • RV redundancy version
  • FDRA frequency domain resource assignment
  • the UE 110 received beam measurement resources corresponding to one or more cells. For example, the UE 110 may measure one or more beam based on CSI-RS, SSB or any other appropriate type of measurement resource. In 715, the UE 110 transmits an aperiodic CSI report to the network. As will be described in more detail below, a variety of different mechanisms may be used to configure uplink resources for beam reporting in response to the DCI.
  • aperiodic beam reports may be transmitted on the PUCCH.
  • RRC signaling may be used to configure the PUCCH format for the aperiodic reporting.
  • PUCCH format 2, 3 or 4 may be configured.
  • the UE 110 may perform CSI reporting on the PUCCH on slot n+k where n represents the slot where the UE 110 detects the DCI and k is a CSI report slot offset value.
  • the value of k may be provided in a report offset indicator field introduced herein for DCI.
  • the CSI report slot offset value may be defined relative to the slot of the DCI or the slot where PUCCH with HARQ feedback corresponding to the DCI is transmitted.
  • a bit value of 0 (e.g., , the report offset indicator filed is not present in the DCI) may correspond to the case where a single offset value is configured by RRC signaling for CSI reporting.
  • Fig. 8 shows an example DCI 800 according to various example embodiments.
  • the DCI 800 includes a CSI request field 810.
  • a 6-bit CSI request field may be used.
  • the CSI request field may be any appropriate size.
  • the DCI 800 further includes the report offset indicator field 815 comprising 0-N bits, legacy DCI fields 820 (e.g., existing fields in DCI format 1_1, DCI format 1_2, etc. ) and CRC 825.
  • the DCI 800 is provided to illustrate one example of a structure that may be used to implement the example DCI introduced herein and is not intended to limit the example embodiments in any way.
  • the example DCI may be configured in any appropriate manner.
  • configured grant (CG) -PUSCH may be used for aperiodic CSI reporting.
  • the triggering DCI may include a report offset indicator field comprising a slot offset value relative to the DCI on which the CSI report is to be transmitted over PUSCH.
  • a slot offset value relative to the to the triggering DCI may be provided by RRC signaling.
  • the following parameters may be provided via RRC signaling for each CG-PUSCH configuration, uplink BWP ID, time domain resource allocation (TDRA) , FDRA, antenna ports and MCS.
  • the MCS of CG-PUSCH may be dynamically indicated by the DCI for fast link adaptation.
  • the differential MCS may be used for CG-PUSCH MCS.
  • the differential MCS may be quantized to a 3-bit value with reference to the MCS value indicated for PDCH in the same DCI.
  • a CG-PUSCH indicator is introduced for the DCI to enable the UE 110 to select one of multiple previously provided CG-PUSCH configurations. The selection may be based on the number of triggered CSI reporting that is conveyed by the CG-PUSCH or any other appropriate factor.
  • a bit value of 0 (e.g., the CG-PUSCH indicator filed is not present in the DCI) may correspond to the case where a single CG-PUSCH configuration is configured by RRC signaling for CSI reporting.
  • PUCCH with HARQ-ACK defined in 3GPP release 17 may not be transmitted. Instead, the transmission of PUCCH carrying CSI reporting may be used as an acknowledgment for the beam update provided in the DCI. Alternatively, the PUCCH with HARQ-ACK defined in Rel-17 may be enabled or disabled by the network for this procedure.
  • the DCI 900 includes a 6-bit CSI request field 910. However, in an actual deployment scenario, the CSI request field may be any appropriate size.
  • the DCI 800 further includes the report offset indicator field 915 comprising 0-N bits, the CG-PUSCH indicator field 920 comprising 0-M bits, MCS 925, legacy DCI fields 930 (e.g., existing fields in DCI format 1_1, DCI format 1_2, etc. ) and CRC 935.
  • the DCI 900 is provided to illustrate one example of a structure that may be used to implement the example DCI introduced herein and is not intended to limit the example embodiments in any way.
  • the example DCI may be configured in any appropriate manner.
  • a method performed by a user equipment comprising decoding, based on signaling received from a base station, downlink control information (DCI) for uplink resource allocation, the DCI comprising a first field configured to provide a transmission configuration indicator (TCI) update and a second field configured to trigger aperiodic channel state information (CSI) reporting and configuring transceiver circuitry to transmit one or more CSI reports using physical uplink shared channel (PUSCH) resources indicated by the DCI.
  • DCI downlink control information
  • TCI transmission configuration indicator
  • CSI periodic channel state information
  • the method of the first example further comprising configuring the transmit circuitry to transmit a physical uplink control channel (PUCCH) signal in response to the decoded DCI.
  • PUCCH physical uplink control channel
  • the method of the third example where the PUCCH comprises a hybrid automatic repeat request (HARQ) acknowledgement (ACK) .
  • HARQ hybrid automatic repeat request
  • ACK acknowledgement
  • the method of the third example further comprising determining a PUCCH resource for the PUCCH signal transmission based on configuration information received by radio resource control (RRC) signaling.
  • RRC radio resource control
  • the configuration information includes at least one of an uplink bandwidth part (BWP) ID, a PUCCH resource ID, a slot offset defined relative to a slot in which the DCI is detected and a slot offset list comprising a plurality of slot offsets.
  • BWP uplink bandwidth part
  • the method of the third example further comprising decoding, based on signaling received from the base station, a parameter indicating a slot offset between a slot of the PUCCH and a first slot of the CSI-RS resource set.
  • the method of the seventh example further comprising decoding, based on the slot offset, a channel state information (CSI) -reference signal (RS) resource set, wherein the one or more CSI reports are transmitted on the PUSCH scheduled by the detected DCI and include at least measurement data based on the CSI-RS resource set.
  • CSI channel state information
  • RS reference signal
  • the method of the first example further comprising decoding, based on signaling received from the base station, a slot offset parameter corresponding to a channel state information (CSI) -reference signal (RS) resource set indicating a slot offset between a slot in which the DCI is detected and a first slot of the CSI-RS resource set and decoding, based on the slot offset, the CSI-RS resource set, wherein the one or more CSI reports are to be transmitted on a physical uplink shared channel (PUSCH) and include at least measurement data based on the CSI-RS resource set.
  • CSI channel state information
  • RS reference signal
  • the method of the first example wherein the PUSCH transmission is configured to indicate to the base station a successful reception of the TCI update field in the DCI.
  • a processor configured to perform any of the methods of the first through tenth examples.
  • a user equipment comprising a transceiver configured to communicate with a base station and a processor communicatively coupled to the transceiver and configured to perform any of the methods of the first through tenth examples.
  • a method performed by a user equipment comprising decoding, based on signaling received from a base station, downlink control information (DCI) for downlink resource allocation, the DCI comprising a field configured to trigger aperiodic channel state information (CSI) reporting and configuring transceiver circuitry to transmit an aperiodic CSI report corresponding to one or more beams to the base station.
  • DCI downlink control information
  • CSI channel state information
  • the method of the thirteenth example, wherein the field configured to trigger aperiodic CSI reporting comprises one or more of a modulation a coding scheme (MCS) field, a redundancy version (RV) field and the frequency domain resource assignment (FDRA) field.
  • MCS modulation a coding scheme
  • RV redundancy version
  • FDRA frequency domain resource assignment
  • the method of the thirteenth example wherein the aperiodic CSI report is transmitted on physical uplink control channel (PUCCH) .
  • PUCCH physical uplink control channel
  • the method of the fifteenth example wherein the aperiodic CSI report is transmitted using one of PUCCH format 2, 3 or 4, wherein the one of PUCCH format 2, 3 or 4 is configured by radio resource control (RRC) signaling.
  • RRC radio resource control
  • the DCI is configured to include a report offset indicator field configured to indicate a slot offset from one or more slot offset values configured by radio resource control (RRC) signaling, wherein each slot offset value is defined as an offset between a slot in which the DCI is detected and a first slot of a PUCCH resource.
  • RRC radio resource control
  • the method of the seventeenth example wherein when a single slot offset value is configured by radio resource control (RRC) signaling, the slot offset indicator field is not present in the DCI.
  • RRC radio resource control
  • the report offset indicator field is configured to indicate which of a plurality of slot offset values are to be used for the PUCCH transmission, wherein the plurality of slot offset values are configured by radio resource control (RRC) signaling.
  • RRC radio resource control
  • the method of the thirteenth example wherein the aperiodic CSI report is transmitted using a configured grant (CG) -physical uplink shared channel (PUSCH) .
  • CG configured grant
  • PUSCH physical uplink shared channel
  • the DCI further comprises a report offset indicator field configured to indicate a slot offset relative to the DCI for a semi-persistent scheduling (SPS) configured grant (CG) -PUSCH.
  • SPS semi-persistent scheduling
  • CG configured grant
  • the method of the twentieth example wherein for each semi-persistent scheduling (SPS) configured grant (CG) -PUSCH configuration an offset relative to a slot in which the DCI is detected is configured by radio resource control (RRC) signaling.
  • SPS semi-persistent scheduling
  • CG configured grant
  • RRC radio resource control
  • the DCI further comprises a CG-PUSCH indicator field configured to indicate one CG-PUSCH configuration from a plurality of CG-PUSCH configuration for the aperiodic CSI report transmission.
  • the method of the twentieth example further comprising decoding, based on radio resource control (RRC) signaling received from the base station, one or more parameters for each CG-PUCH configuration, the one or more parameters comprising at least one of an uplink bandwidth part (BWP) ID, a time domain resource allocation (TDRA) , a frequency domain resource allocation (FDRA) , antenna ports and modulation and coding s cheme (MCS) configuration information.
  • RRC radio resource control
  • the method of the twentieth example wherein the DCI is configured to indicate a modulation and coding scheme (MCS) for the CG-PUSCH.
  • MCS modulation and coding scheme
  • the DCI is configured to indicate a differential modulation and coding scheme (MCS) for the CG-PUSCH with reference to the MCS of a physical downlink shared channel (PDSCH) scheduled by the DCI, the differential MCS quantized to a 3-bit value.
  • MCS modulation and coding scheme
  • the method of the twentieth example wherein the DCI is configured to include a CG-PUSCH indicator field.
  • the method of the twenty seventh example wherein when a single CG-PUSCH is configured by radio resource control (RRC) signaling for the aperiodic CSI report, the CG-PUSCH indicator field is not present in the DCI.
  • RRC radio resource control
  • the method of the twenty seventh example wherein the CG-PUSCH indicator field is configured to indicate which of a plurality of CG-PUSCH configurations are to be used for the CG-PUSCH transmission, wherein the plurality of CG-PUSCH configurations are provided by radio resource control (RRC) signaling.
  • RRC radio resource control
  • the method of the thirteenth example wherein the DCI is DCI format 1_1 or DCI format 1_2 and further comprises a transmission configuration indicator (TCI) update, wherein the aperiodic CSI report is transmitted on PUSCH and is configured to indicate successful reception of the TCI update field in the DCI.
  • TCI transmission configuration indicator
  • a beam application time for the TCI update is based on a UE capability for beam application time and an offset value provided in the DCI.
  • a processor configured to perform any of the methods of the thirteenth through thirty first examples.
  • a user equipment comprising a transceiver configured to communicate with a base station and a processor communicatively coupled to the transceiver and configured to perform any of the methods of the thirteenth through thirty first examples.
  • An example hardware platform for implementing the example embodiments may include, for example, an Intel x86 based platform with compatible operating system, a Windows OS, a Mac platform and MAC OS, a mobile device having an operating system such as iOS, Android, etc.
  • the example embodiments described above may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that, when compiled, may be executed on a processor or microprocessor.
  • personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
  • personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un équipement utilisateur (UE) est configuré pour décoder, sur la base d'une signalisation reçue en provenance d'une station de base, des informations de commande de liaison descendante (DCI) pour une attribution de ressources de liaison montante, les DCI comprenant un premier champ configuré pour fournir une mise à jour d'indicateur de configuration de transmission (TCI) et un second champ configuré pour déclencher un rapport d'informations d'état de canal (CSI) apériodique et configurer un ensemble de circuits d'émetteur-récepteur pour transmettre un ou plusieurs rapports de CSI à l'aide de ressources de canal physique partagé de liaison montante (PUSCH) indiquées par les DCI.
PCT/CN2023/135006 2023-11-29 2023-11-29 Techniques de signalisation pour réduction de latence de procédures de gestion de faisceau Pending WO2025111847A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/135006 WO2025111847A1 (fr) 2023-11-29 2023-11-29 Techniques de signalisation pour réduction de latence de procédures de gestion de faisceau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/135006 WO2025111847A1 (fr) 2023-11-29 2023-11-29 Techniques de signalisation pour réduction de latence de procédures de gestion de faisceau

Publications (1)

Publication Number Publication Date
WO2025111847A1 true WO2025111847A1 (fr) 2025-06-05

Family

ID=95896008

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/135006 Pending WO2025111847A1 (fr) 2023-11-29 2023-11-29 Techniques de signalisation pour réduction de latence de procédures de gestion de faisceau

Country Status (1)

Country Link
WO (1) WO2025111847A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190349964A1 (en) * 2018-05-10 2019-11-14 Asustek Computer Inc. Method and apparatus for beam indication for uplink transmission in a wireless communication system
CN116391324A (zh) * 2020-10-21 2023-07-04 瑞典爱立信有限公司 具有灵活信道选择的基于dci的tci状态更新
US20230362951A1 (en) * 2022-05-09 2023-11-09 Samsung Electronics Co., Ltd. Method and apparatus of tci state indication and update via dynamic signaling
CN117136516A (zh) * 2021-04-01 2023-11-28 三星电子株式会社 无线通信系统中用于上行链路发送的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190349964A1 (en) * 2018-05-10 2019-11-14 Asustek Computer Inc. Method and apparatus for beam indication for uplink transmission in a wireless communication system
CN116391324A (zh) * 2020-10-21 2023-07-04 瑞典爱立信有限公司 具有灵活信道选择的基于dci的tci状态更新
CN117136516A (zh) * 2021-04-01 2023-11-28 三星电子株式会社 无线通信系统中用于上行链路发送的方法和装置
US20230362951A1 (en) * 2022-05-09 2023-11-09 Samsung Electronics Co., Ltd. Method and apparatus of tci state indication and update via dynamic signaling

Similar Documents

Publication Publication Date Title
US10264564B2 (en) System and method for resource allocation for massive carrier aggregation
EP3711216B1 (fr) Rétroaction de livre-code pour des retransmissions de données
US9949241B2 (en) Systems and methods for feedback reporting
EP2995106B1 (fr) Procédé, appareil et programme informatique pour communications sans fil
US20180115965A1 (en) User terminal, radio base station, radio communication system and radio communication method
US20170055249A1 (en) Base station, transmission method, mobile station and retransmission control method
US20250167857A1 (en) Channel State Information Feedback in Wireless Communications
JP2017508343A (ja) キャリアアグリゲーションためのシステムおよび方法
US20240405924A1 (en) HARQ Codebook Determination in Wireless Communications
US20230422273A1 (en) Configured Grant Operations for Multiple PUSCH
EP4000337A1 (fr) Procédés de résolution d'une collision entre sr et pusch
US20240015736A1 (en) Configured Grant based Uplink Transmissions in Wireless Communication
US12489562B2 (en) Method and apparatus for HARQ-ACK feedback transmission
US12349136B2 (en) Configured grant operations for multiple PUSCH
US20240032032A1 (en) Type-2 HARQ-ACK Codebook for Multi-Cell Scheduling DCI
US20250203612A1 (en) Enhanced uplink control information mapping to uplink channel allocations
US20230199750A1 (en) Uplink Control Information for Enabling Autonomous Uplink Transmissions
US12356396B2 (en) Signaling solution on reliability enhancement for uplink transmission
WO2024207190A1 (fr) Gestion d'avance temporelle dans des communications sans fil
WO2025111847A1 (fr) Techniques de signalisation pour réduction de latence de procédures de gestion de faisceau
EP4572258A1 (fr) Procédé de rapport d'informations d'état de canal et appareil
WO2025231719A1 (fr) Contenu de rapport de faisceau pour une gestion de faisceau initiée par un ue dans une communication sans fil
WO2023130381A1 (fr) Prise en charge d'améliorations de rétroinformations harq
EP4519996B1 (fr) Mise en correspondance d'informations de commande de liaison montante amélioré avec des attributions de canal de liaison montante
WO2022056826A1 (fr) Opérations basées sur un réseau pour une transmission de données basée sur un super-créneau

Legal Events

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

Ref document number: 23959768

Country of ref document: EP

Kind code of ref document: A1