Method and apparatus of uplink transmission reconfiguration
The method dynamically adjusts uplink transmission configurations based on TCI state indications to align with the gNB's receive beam, reducing latency and signaling overhead in 5G/NR systems by updating time domain locations without RRC reconfiguration, thus improving scheduling efficiency.
Patent Information
- Application Number
- PCT/CN2026/082380
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-15
- Filing Date
- 2026-03-10
- Publication Date
- 2026-11-19
AI Technical Summary
The current 5G/NR system faces significant scheduling difficulties due to mismatches between the receive beam expected by the gNB and the semi-statically fixed time domain transmission locations of uplink transmissions, leading to substantial latency and signaling overhead when TCI states are dynamically switched.
A method for dynamically updating the time domain transmission configuration of uplink transmissions, such as scheduling requests and CSI reports, based on TCI state indications without requiring RRC reconfiguration, using a list of TCI states and time domain configurations to align UE transmission timing with the gNB's receive beam.
This approach reduces latency and signaling overhead by dynamically adjusting transmission locations, ensuring alignment with the gNB's receive beam and optimizing scheduling without the need for RRC reconfiguration, thereby enhancing beam management efficiency.
Smart Images

Figure CN2026082380_19112026_PF_FP_ABST
Abstract
Description
METHOD AND APPARATUS OF UPLINK TRANSMISSION RECONFIGURATIONCROSS REFERENCE TO RELATED APPLICATIONSThe application claims priority to US provisional patent application No. 63 / 806,356, filed on May 15, 2025, which is incorporated by reference in the present application in its entirety.BACKGROUND OF DISCLOSURE1. Field of Disclosure
[0001] The present disclosure relates to the field of communication systems, and more particularly, to a method and apparatus for dynamically updating the time domain transmission configuration of configured uplink transmissions based on Transmission Configuration Indicator (TCI) state indication. 2. Description of Related Art
[0002] In 5th Generation (5G) New Radio (NR) wireless communication systems, multi-beam operation is essential to achieve high beamforming gain, particularly in millimeter-wave (mmWave) and higher frequency bands. A communication system includes a downlink (DL) that conveys signals from a transmission point such as a gNB (Next generation NodeB) to a User equipment (UE) , and an uplink (UL) that conveys signals from the UE to the gNB. The 5G / NR system supports up to 128 CSI-RS antenna ports, enabling the gNB to be equipped with a very large number of antenna elements and to apply hybrid beamforming for multi-beam operation.
[0003] The 3rd Generation Partnership Project (3GPP) specification supports beam indication function and beam measurement reporting function. For DL beam indication and measurement, the reference signal (RS) can be a non-zero power Channel State Information RS (NZP CSI-RS) and / or a Synchronization Signal Block (SSB) . Beam indication is performed via a TCI state, wherein a set of TCI states is configured via Radio Resource Control (RRC) signaling, a subset of TCI states is activated through Medium Access Control Control Element (MAC CE) , and the gNB subsequently indicates beam assignment to the UE through Downlink Control Information (DCI) signaling. For UL beam indication and measurement, the reference RS can be NZP CSI-RS, SSB, and / or Sounding Reference Signal (SRS) .Technical Problem
[0004] In the current 5G / NR design, the time domain transmission configurations of semi-statically configured uplink transmissions-such as scheduling request (SR) transmissions and periodic or semi-persistent Channel State Information (CSI) reports on physical uplink control channel (PUCCH) , as well as configured physical uplink shared channel (PUSCH) transmissions under a configured grant-are configured via RRC signaling in a semi-static manner. As a result, the time domain transmission locations (i.e., periodicity and slot offset) of these configured transmissions are fixed at the time of RRC configuration.
[0005] On the other hand, the gNB implements a mapping between time domain transmission resources and receive beams used to receive uplink transmissions from the UE. Therefore, when the TCI state applied on a configured uplink transmission (e.g., PUCCH for SR or CSI reporting, or configured grant PUSCH) is dynamically switched by the gNB, a mismatch may arise between the receive beam expected by the gNB and the semi-statically fixed time domain transmission location from the UE's perspective. This mismatch causes significant scheduling difficulty for the gNB. Resolving this mismatch through RRC reconfiguration introduces substantial latency and signaling overhead, which is undesirable for time-sensitive beam management operations.
[0006] Hence, an enhanced method for addressing the problem is desirable.SUMMARY
[0007] An object of the present disclosure is to propose a method of TCI state update and uplink transmission reconfiguration, a user equipment (UE) , and a network node.
[0008] In a first aspect, a method of uplink transmission reconfiguration performed by a User equipment (UE) , comprising: receiving a radio resource control (RRC) configuration comprising: a list of Transmission Configuration Indicator (TCI) states; an uplink transmission configuration comprising at least one default time domain parameter specifying a default periodicity and a default time domain offset; and a list of time domain configurations; receiving an indication of one TCI state of the list of TCI states to be applied on a configured uplink transmission associated with the uplink transmission configuration; and performing the configured uplink transmission on physical layer resources for the configured uplink transmission based on the TCI state indicated in the indication, wherein depending on whether the indicated TCI state is associated with a first indicator, the physical layer resources for the configured uplink transmission are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter.
[0009] In a second aspect, an embodiment of the invention provides a method of uplink transmission reconfiguration performed by a network node, comprising: transmitting a radio resource control (RRC) configuration comprising: a list of Transmission Configuration Indicator (TCI) states; an uplink transmission configuration comprising at least one default time domain parameter specifying a default periodicity and a default time domain offset; and a list of time domain configurations; transmitting an indication of one TCI state of the list of TCI states to be applied on a configured uplink transmission associated with the uplink transmission configuration, wherein the indication of the TCI state indicated, depending on whether the indicated TCI state is associated with a first indicator, indicates that the physical layer resources for the configured uplink transmission are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter; and receiving the configured uplink transmission on the physical layer resources.
[0010] In a third aspect, an embodiment of the invention provides a user equipment (UE) comprising a processor configured to call and run a computer program stored in a memory, to cause a device in which the processor is installed to execute the disclosed method.
[0011] In a fourth aspect, an embodiment of the invention provides a network node comprising a processor configured to call and run a computer program stored in a memory, to cause a device in which the processor is installed to execute the disclosed method.
[0012] The disclosed method may be programmed as computer executable instructions stored in non-transitory computer readable medium. The non-transitory computer readable medium, when loaded to a computer, directs a processor of the computer to execute the disclosed method.
[0013] The non-transitory computer readable medium may comprise at least one from a group consisting of: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory, a Programmable Read Only Memory, an Erasable Programmable Read Only Memory, EPROM, an Electrically Erasable Programmable Read Only Memory and a Flash memory.
[0014] The disclosed method may be programmed as a computer program product, that causes a computer to execute the disclosed method.
[0015] The disclosed method may be programmed as a computer program, that causes a computer to execute the disclosed method.Advantageous Effects
[0016] The proposed method enables dynamic adjustment of the time domain transmission location (periodicity and / or slot offset) of configured uplink transmissions-including scheduling request (SR) , periodic CSI report, semi-persistent CSI report on PUCCH, and configured grant PUSCH-based on the TCI state indicated by the gNB, without requiring RRC reconfiguration. This eliminates the large latency associated with RRC-level reconfiguration procedures.
[0017] Additionally, by associating each TCI state with a first indicator that indexes a pre-configured list of time domain configurations, the UE can promptly align its configured uplink transmission timing with the receive beam indicated by the gNB. This resolves the mismatch between the gNB's receive beam mapping and the UE's transmission timing that may otherwise occur upon TCI state switching, thereby significantly reducing scheduling difficulty for the network.
[0018] Further, the disclosed mechanism provides a flexible and scalable framework supporting multiple time domain configuration variants-including lists of {periodicity, slot offset} pairs or lists of slot offsets alone-applicable uniformly across different types of configured uplink transmissions (SR, periodic CSI, semi-persistent CSI on PUCCH, and configured grant PUSCH) . This flexibility allows network deployments to optimize uplink beam-aligned transmission scheduling with minimal signaling overhead.BRIEF DESCRIPTION OF DRAWINGS
[0019] To clearly illustrate the embodiments of the present disclosure or related technical solutions, the accompanying drawings are briefly described below. These drawings represent embodiments of the present disclosure. A person of ordinary skill in the art may derive additional figures or variations based on these drawings without departing from the scope of the present disclosure.
[0020] FIG. 1 illustrates a schematic diagram showing a telecommunication system.
[0021] FIG. 2 illustrates a schematic diagram showing a beam measurement method of an embodiment of the disclosure, including steps for UE reception of RRC configuration and TCI state indication for dynamic uplink transmission reconfiguration.
[0022] FIG. 3 illustrates a schematic diagram showing a beam measurement method of an embodiment of the disclosure, including steps for UE reception of RRC configuration and TCI state indication for reconfiguration of configured scheduling request (SR) transmission.
[0023] FIG. 4 illustrates a schematic diagram showing a beam measurement method of an embodiment of the disclosure, including steps for UE reception of RRC configuration and TCI state indication for reconfiguration of periodic CSI reporting.
[0024] FIG. 5 illustrates a schematic diagram showing a beam measurement method of an embodiment of the disclosure, including steps for UE reception of RRC configuration and TCI state indication for reconfiguration of semi-persistent CSI reporting.
[0025] FIG. 6 illustrates a schematic diagram showing a beam measurement method of an embodiment of the disclosure, including steps for UE reception of RRC configuration and TCI state indication for reconfiguration of configured PUSCH transmission.
[0026] FIG. 7 illustrates a schematic view showing a user equipment (UE) .
[0027] FIG. 8 illustrates a schematic view showing a base station.
[0028] FIG. 9 illustrates a schematic view showing a network node.
[0029] FIG. 10 illustrates a schematic view showing a chip or executing the disclosed method in a UE.
[0030] FIG. 11 illustrates a schematic view showing a chip or executing the disclosed method in a base station.
[0031] FIG. 12 illustrates a schematic view showing a chip or executing the disclosed method in a network node.
[0032] FIG. 13 illustrates a schematic view showing a system for wireless communication according to an embodiment of the present disclosure.DETAILED DESCRIPTION OF EMBODIMENTS
[0033] Embodiments of the disclosure are described in detail with the technical matters, structural features, achieved objects, and effects with reference to the accompanying drawings as follows. Specifically, the terminologies in the embodiments of the present disclosure are merely for describing the purpose of the certain embodiment, but not to limit the disclosure.
[0034] A communication system, such as a 5G New Radio (NR) system, includes a downlink (DL) that conveys signals from a transmission point, such as a next-generation NodeB (gNB) , to a user equipment (UE) . A UE, which may also be referred to as a terminal or mobile station, can be fixed or mobile and encompasses devices such as cellular phones, personal computers, or automated systems like autonomous vehicles and industrial machinery. Correspondingly, a gNB is generally a fixed station and may be referred to as an access point or by other equivalent terminology.
[0035] In 5G NR systems, DL signals include data signals conveying information via the Physical downlink shared channel (PDSCH) , control signals conveying Downlink Control Information (DCI) , and Reference Signals (RS) . Specifically, a gNB transmits data through the PDSCH and DCI through the Physical downlink control channel (PDCCH) . The gNB also transmits various types of RS, including Channel State Information Reference Signals (CSI-RS) and Demodulation Reference Signals (DMRS) . CSI-RS can be transmitted over a DL system bandwidth (BW) and utilized by UEs to track channel Quasi Co-Location (QCL) information, estimate CSI, or perform beam measurements. In contrast, DMRS is typically transmitted only within the bandwidth of its respective PDSCH or PDCCH, enabling the UE to demodulate the associated data or control information.
[0036] The transmission time interval for DL channels is defined as a subframe or a slot. Downlink resource allocation is performed across a specified number of symbols and a group of Physical Resource Blocks (PRBs) . Furthermore, the transmission bandwidth is composed of frequency resource units referred to as Resource Blocks (RBs) .
[0037] Each RB consists of sub-carriers, or Resource Elements (REs) , such as 12 REs. A unit of one RB over one subframe is referred to as a PRB. A UE can be allocated MPDSCH RBs for a total of REs for the PDSCH transmission BW.
[0038] In a 5G New Radio (NR) system, PDSCH transmissions are scheduled either through a dynamic scheduling method based on Downlink Control Information (DCI) or through a semi-static method based on Radio Resource Control (RRC) configuration and DCI activation. Under dynamic scheduling, a UE decodes a PDSCH according to parameters indicated in a detected DCI within a PDCCH. This DCI provides essential information for the corresponding PDSCH, including frequency and time-domain resource assignments, the modulation and coding scheme (MCS) and redundancy version (RV) for each transport block, Hybrid Automatic Repeat Request (HARQ) process numbers, Transmission Power Control (TPC) commands for the PUCCH, and PUCCH resource indicators for HARQ feedback. Additionally, the DCI may convey transmission configuration indications (TCI) , SCell dormancy indications, and other control parameters.
[0039] The 5G NR system supports up to 128 CSI-RS antenna ports, enabling the next-generation NodeB (gNB) to be equipped with a very large number of antenna elements. In this configuration, multiple antenna elements are mapped onto a single reference signal port. In millimeter-wave (mmWave) bands, although the number of antenna elements can be vast, the number of digital transmission paths is often limited by hardware implementation restrictions. In this configuration, a single reference signal port is mapped to a plurality of antenna elements, which are controlled by an array of analog phase shifters, time delay shifters, or both. Consequently, a hybrid beamforming mechanism is applied where an antenna sub-array connected to one reference signal port produces an analog beam through analog beamforming, while digital beamforming performs linear combinations across ports to increase precoding gain. Unlike analog beams, which are wideband and non-frequency selective, digital precoding can be varied across frequency sub-bands or RBs to support multi-beam operation.
[0040] Beam management in 3GPP specifications encompasses both beam indication and beam measurement reporting functions. The beam indication function supports the selection of one or two transmission (Tx) beams from separate transmission / reception points (TRPs) , with each Tx beam associated with a reference signal (RS) . For DL beam management, the reference RS may include Non-Zero Power (NZP) CSI-RS or Synchronization Signal Blocks (SSB) , with indications provided via TCI states. A comprehensive set of TCI states is configured through RRC signaling, a subset is then selected or activated via Media Access Control (MAC) Control Elements (CE) , and the final selection of one or more TCI states is indicated through DCI by gNB / NW. Uplink (UL) beam management utilizes NZP CSI-RS, SSB, or Sounding Reference Signals (SRS) , with beam indication achieved either through the SRS Resource Indicator (SRI) field in UL-related DCI or through the indicated TCI state.
[0041] For efficient multi-beam operation, beam measurement and reporting are essential to facilitate beam selection. 5G NR systems support two primary measurement metrics: Layer 1 Reference Signal Received Power (L1-RSRP) and Layer 1 Signal-to-Interference-plus-Noise Ratio (L1-SINR) . These metrics, derived from measuring CSI-RS or SSB resources, for beam reporting are reported alongside an associated CSI-RS Resource Indicator (CRI) or SS / PBCH block (SSB) resource Indicator (SSBRI) . L1-RSRP is derived from measurements of either CSI-RS or SSB, resulting in CSI-RSRP or SS-RSRP, respectively. Similarly, L1-SINR is derived from CSI-RS or SSB measurements and is designated as CSI-SINR or SS-SINR depending on the reference signal utilized. To align the Tx beam at the gNB and the Rx beam at the UE, the 5G / NR system utilizes a multi-stage beam sweeping procedure. The network (e.g., gNB) initially executes a coarse beam sweep, during which the UE measures the available beams to identify and report the preferred candidate (e.g., a selected optimal coarse beam) . Subsequently, the network sweeps a set of narrow beams within the spatial range of the selected coarse beam to refine the Tx beam measurement. Finally, the network may provide repeated transmissions of a specific narrow Tx beam, enabling the UE to perform its own reception (Rx) beam sweep to finalize the communication link alignment.
[0042] A primary limitation of the current 3GPP system design is that time-domain transmission configurations for semi-statically configured uplink transmissions-such as scheduling requests (SRs) or periodic and semi-persistent CSI reporting on the PUCCH-are established via RRC signaling. Because these parameters are semi-static, the specific time-domain locations for these transmissions remain fixed over long durations.
[0043] Simultaneously, the gNB typically implements a specific mapping between its available time-domain transmission resources and its corresponding receive beams. This spatial-to-temporal mapping is designed to optimize the gNB’s ability to capture signals from specific directions at specific times.
[0044] A technical conflict arises when the TCI state applied to the PUCCH is switched. When the beam is updated, a mismatch often occurs between the gNB's updated receive beam and the fixed time-domain locations assigned during the RRC configuration phase. From the perspective of the network or gNB, this misalignment between the spatial direction and the pre-allocated time slot creates substantial scheduling complexity and operational overhead, as the fixed resources no longer align with the optimal spatial reception window.
[0045] The present disclosure provides methods and apparatuses for dynamically updating the transmission configuration (e.g., time domain location, such as periodicity and / or slot offset) of configured uplink transmissions, such as scheduling request (SR) transmissions, periodic or semi-persistent CSI reports on PUCCH, or configured grant PUSCH transmissions. These updates are triggered based on a switch in the TCI state applied to the configured transmission, enabling alignment with the network's receive beam without requiring RRC reconfiguration, thereby reducing latency and signaling overhead.
[0046] Aspects, features, and advantages of the present disclosure are readily apparent from the following detailed description, which illustrates a number of exemplary embodiments and implementations. The present disclosure is also capable of other and different embodiments, and its several details can be modified in various obvious respects, all without departing from the spirit and scope of the present disclosure. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive. The present disclosure is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings. In the following, for brevity, both Frequency Division Duplex (FDD) and Time Division Duplex (TDD) are considered as duplex methods for both DL and UL signaling. Although the exemplary descriptions and embodiments that follow assume Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) , the techniques of the present disclosure can be extended to other OFDM-based transmission waveforms or multiple access schemes, such as filtered OFDM (F-OFDM) . The present disclosure covers several embodiments that can be used in conjunction or in combination with one another, or can operate as standalone schemes.
[0047] In the present disclosure, the term "configured uplink transmission" refers to semi-statically configured UL transmissions, such as SR transmissions on PUCCH, periodic or semi-persistent CSI reports on PUCCH, or configured grant PUSCH transmissions. These transmissions are initially configured via RRC signaling with parameters including time-domain resources (e.g., periodicity and slot offset) , and their beam indications are managed through TCI states.
[0048] Within the present disclosure, the term ‘PDSCH’ (Physical downlink shared channel) refers to a downlink transmission from a network, such as a gNB, to a User equipment (UE) . A PDSCH represents a transmission of data information within a specific frequency-time resource allocation. These transmissions can be managed through various scheduling mechanisms, including dynamic scheduling, semi-static configuration, or a hybrid approach. In dynamic scheduling, the network schedules the channel via DCI on a per-transmission basis. Conversely, semi-static configurations are preconfigured with fixed parameters-such as frequency-time resource locations, Modulation and Coding Schemes (MCS) , and transmission schemes like Semi-Persistent Scheduling-through RRC signaling. A hybrid configuration utilizes a combination of these methods, typically involving a semi-static pre-configuration followed by a dynamic activation or triggering event.
[0049] An exemplary PDSCH transmission flow triggered by DCI involves a sequence of operations where the UE first receives a DCI from the network that indicates specific scheduling or configuration parameters, followed by the UE receiving the PDSCH according to those parameters. For example, the gNB or network signaling a DCI to the UE to trigger or schedule the PDSCH transmission. Upon receiving the DCI, the UE decodes the message to extract essential configuration and indication information. This information includes, but is not limited to, frequency domain and time-domain resource assignments, the Hybrid Automatic Repeat Request (HARQ) process ID, the MCS level, the Redundancy Version (RV) , and the selection of the transmission scheme and TCI. After successfully decoding the DCI, the UE is directed to detect and receive the PDSCH at the allocated resources based on the obtained indication information.
[0050] The techniques of the present disclosure encompass several embodiments that may be utilized independently, in conjunction, or in various combinations with one another. Throughout this description, terms such as TCI, TCI state, RS, beam, and beam measurement RS (BM RS) are used for illustrative purposes and are not intended to be normative, as other terminology referring to functionally equivalent features may be employed. A reference RS, beam RS, or BM RS corresponds to a specific set of DL or UL transmission beam characteristics, including spatial direction, angular parameters, precoding, beamforming, and port configurations.
[0051] For instance, a UE may receive a reference RS identifier within a DL assignment represented by a TCI state, allowing the UE to apply the known spatial characteristics of that reference RS to the assigned DL transmission. These reference signals can be measured by the UE to generate beam reports, providing the network (e.g., gNB) with the necessary information to assign optimal DL or UL transmission beams. Alternatively, the UE may transmit these reference signals to the network, enabling the gNB to measure and calculate the information required for spatial link adaptation and beam assignment.
[0052] The reference signals and associated ports can be managed through various time-domain behaviors and signaling mechanisms. They may be dynamically triggered by the network via DCI signaling or preconfigured with specific periodic behaviors through RRC signaling. Furthermore, the system supports hybrid configurations that combine semi-static pre-configuration with dynamic activation and deactivation, such as those utilized in semi-persistent transmission schemes.
[0053] With reference to FIG. 1, a telecommunication system including a UE 10a, a UE 10b, a base station (BS) 20a, and a network entity device 30 executes the disclosed method according to an embodiment of the present disclosure. FIG. 1 is shown for illustrative not limiting, and the system may comprise more UEs, BSs, and CN entities. Connections between devices and device components are shown as lines and arrows in the FIGs. The UE 10a may include a processor 11a, a memory 12a, and a transceiver 13a. The UE 10b may include a processor 11b, a memory 12b, and a transceiver 13b. The base station 20a may include a processor 21a, a memory 22a, and a transceiver 23a. The network entity device 30 may include a processor 31, a memory 32, and a transceiver 33. Each of the processors 11a, 11b, 21a, and 31 may be configured to implement proposed functions, procedures and / or methods described in the description. Layers of radio interface protocol may be implemented in the processors 11a, 11b, 21a, and 31. Each of the memory 12a, 12b, 22a, and 32 operatively stores a variety of programs and information to operate a connected processor. Each of the transceivers 13a, 13b, 23a, and 33 is operatively coupled with a connected processor, transmits and / or receives radio signals or wireline signals. The UE 10a may be in communication with the UE 10b or other UEs. The base station 20a may be an eNB, a gNB, or one of other types of radio nodes, and may configure radio resources for the UE 10a and UE 10b.
[0054] Each of the processors 11a, 11b, 21a, and 31 may include an application-specific integrated circuit (ASICs) , other chipsets, logic circuits and / or data processing devices. Each of the memory 12a, 12b, 22a, and 32 may include read-only memory (ROM) , a random access memory (RAM) , a flash memory, a memory card, a storage medium and / or other storage devices. Each of the transceivers 13a, 13b, 23a, and 33 may include baseband circuitry and radio frequency (RF) circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented with modules, procedures, functions, entities, and so on, that perform the functions described herein. The modules may be stored in a memory and executed by the processors. The memory may be implemented within a processor or external to the processor, in which those may be communicatively coupled to the processor via various means are known in the art.
[0055] The network entity device 30 may be a node in a CN. CN may include LTE CN, 5G core (5GC) , or 6G core which includes user plane function (UPF) , session management function (SMF) , Access and mobility management function (AMF) , unified data management (UDM) , policy control function (PCF) , control plane (CP) / user plane (UP) separation (CUPS) , authentication server (AUSF) , network slice selection function (NSSF) , and the network exposure function (NEF) . An example of the UE in the description may include one of the UE 10a or UE 10b. An example of the base station in the description may include the base station 20a.
[0056] With reference to FIG. 2, for example, an embodiment of a UE 10 includes one of the UE 10a or UE 10b, an embodiment of a base station 20 (e.g., gNB) includes the base station 20a. Although the UE 10 and the base station 20 are detailed as examples in the description, the disclosed method may be applied to other UEs and / or other base stations. Uplink (UL) transmission of a control signal or data may be a transmission operation from a UE to a base station. Downlink (DL) transmission of a control signal or data may be a transmission operation from a base station to a UE. Unless otherwise specified, configurations in the description (e.g., time domain transmission configuration, scheduling request configuration, periodic transmission configuration, semi-persistent transmission configuration, configured grant configuration, a first parameter, a second list, and a third list, ) for a UE (e.g., UE 10) are provided by a base station (e.g., base station 20) .
[0057] Step S001: The base station 20 transmits, to the UE 10, a RRC configuration comprising: a list of TCI states; an uplink transmission configuration comprising at least one default time domain parameter specifying a default periodicity and a default time domain offset; and a list of time domain configurations. The UE 10 receives the RRC configuration.
[0058] Step S002: The base station 20 transmits an indication of one TCI state of the list of TCI states to be applied on a configured uplink transmission associated with the uplink transmission configuration. The indication of the TCI state indicated, depending on whether the indicated TCI state is associated with a first indicator, indicates that the physical layer resources for the configured uplink transmission are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter. The UE 10 receives the indication of the TCI state to be applied on a configured uplink transmission associated with the uplink transmission configuration.
[0059] Step S003: The UE 10 performs the configured uplink transmission on physical layer resources for the configured uplink transmission based on the TCI state indicated in the indication. The base station 20 receives the configured uplink transmission on the physical layer resources. Depending on whether the indicated TCI state is associated with a first indicator, the physical layer resources for the configured uplink transmission are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter.
[0060] With reference to FIG. 3, an embodiment of the disclosure is illustrated in the following.
[0061] Step S101: The base station 20 transmits, to the UE 10, a RRC configuration comprising: a list of TCI states; an uplink transmission configuration comprising at least one default time domain parameter specifying a default periodicity and a default time domain offset; and a list of time domain configurations. The UE 10 receives the RRC configuration.
[0062] Step S102: The base station 20 transmits an indication of one TCI state of the list of TCI states to be applied on a configured SR transmission associated with the uplink transmission configuration. The indication of the TCI state indicated, depending on whether the indicated TCI state is associated with a first indicator, indicates that the physical layer resources for the configured SR transmission are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter. The UE 10 receives the indication of the TCI state to be applied on a configured SR transmission.
[0063] Step S103: The UE 10 performs the configured SR transmission on physical layer resources for the configured SR transmission based on the TCI state indicated in the indication. The base station 20 receives the configured SR transmission on the physical layer resources. Depending on whether the indicated TCI state is associated with a first indicator, the physical layer resources for the configured SR transmission are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter.
[0064] With reference to FIG. 4, an embodiment of the disclosure is illustrated in the following.
[0065] Step S201: The base station 20 transmits, to the UE 10, a RRC configuration comprising: a list of TCI states; an uplink transmission configuration comprising at least one default time domain parameter specifying a default periodicity and a default time domain offset; and a list of time domain configurations. The UE 10 receives the RRC configuration.
[0066] Step S202: The base station 20 transmits an indication of one TCI state of the list of TCI states to be applied on a periodic CSI reporting associated with the uplink transmission configuration. The indication of the TCI state indicated, depending on whether the indicated TCI state is associated with a first indicator, indicates that the physical layer resources for the periodic CSI reporting are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter. The UE 10 receives the indication of the TCI state to be applied on a periodic CSI reporting.
[0067] Step S203: The UE 10 performs the periodic CSI reporting on physical layer resources for the periodic CSI reporting based on the TCI state indicated in the indication. The base station 20 receives the periodic CSI reporting on the physical layer resources. Depending on whether the indicated TCI state is associated with a first indicator, the physical layer resources for the periodic CSI reporting are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter.
[0068] With reference to FIG. 5, an embodiment of the disclosure is illustrated in the following.
[0069] Step S301: The base station 20 transmits, to the UE 10, a RRC configuration comprising: a list of TCI states; an uplink transmission configuration comprising at least one default time domain parameter specifying a default periodicity and a default time domain offset; and a list of time domain configurations. The UE 10 receives the RRC configuration.
[0070] Step S302: The base station 20 transmits an indication of one TCI state of the list of TCI states to be applied on a semi-persistent CSI reporting associated with the uplink transmission configuration. The indication of the TCI state indicated, depending on whether the indicated TCI state is associated with a first indicator, indicates that the physical layer resources for the semi-persistent CSI reporting are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter. The UE 10 receives the indication of the TCI state to be applied on a semi-persistent CSI reporting.
[0071] Step S303: The UE 10 performs the semi-persistent CSI reporting on physical layer resources for the semi-persistent CSI reporting based on the TCI state indicated in the indication. The base station 20 receives the semi-persistent CSI reporting on the physical layer resources. Depending on whether the indicated TCI state is associated with a first indicator, the physical layer resources for the semi-persistent CSI reporting are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter.
[0072] With reference to FIG. 6, an embodiment of the disclosure is illustrated in the following.
[0073] Step S401: The base station 20 transmits, to the UE 10, a RRC configuration comprising: a list of TCI states; an uplink transmission configuration comprising at least one default time domain parameter specifying a default periodicity and a default time domain offset; and a list of time domain configurations. The UE 10 receives the RRC configuration.
[0074] Step S402: The base station 20 transmits an indication of one TCI state of the list of TCI states to be applied on a configured PUSCH transmission associated with the uplink transmission configuration. The indication of the TCI state indicated, depending on whether the indicated TCI state is associated with a first indicator, indicates that the physical layer resources for the configured PUSCH transmission are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter. The UE 10 receives the indication of the TCI state to be applied on a configured PUSCH transmission.
[0075] Step S403: The UE 10 performs the configured PUSCH transmission on physical layer resources for the configured PUSCH transmission based on the TCI state indicated in the indication. The base station 20 receives the configured PUSCH transmission on the physical layer resources. Depending on whether the indicated TCI state is associated with a first indicator, the physical layer resources for the configured PUSCH transmission are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter.
[0076] In one or more embodiments of the disclosure, the configured uplink transmission is carried on a PUCCH, and the uplink transmission configuration further comprises a PUCCH resource identifier, wherein the at least one default time domain parameter is a single parameter specifying both the default periodicity and the default slot offset.
[0077] In one or more embodiments of the disclosure, the configured uplink transmission is a scheduling request (SR) , and the uplink transmission configuration further comprises a scheduling request resource identifier and a scheduling request identifier.
[0078] In one or more embodiments of the disclosure, the configured uplink transmission is a periodic CSI report, and the uplink transmission configuration further comprises a report configuration identifier and a report configuration type set to periodic.
[0079] In one or more embodiments of the disclosure, the configured uplink transmission is a semi-persistent CSI report, and the uplink transmission configuration further comprises a report configuration identifier and a report configuration type set to semi-persistent.
[0080] In one or more embodiments of the disclosure, the configured uplink transmission is a semi-statically configured PUSCH transmission under a configured grant, and the at least one default time domain parameter comprises a first parameter specifying the default periodicity and a second parameter specifying the default time domain offset.
[0081] In one or more embodiments of the disclosure, when the indicated TCI state is not associated with a first indicator, the physical layer resources are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter; and when the indicated TCI state is associated with the first indicator having a value, the physical layer resources are allocated based on the time domain configuration in the list of time domain configurations corresponding to a value of the first indicator.
[0082] In one or more embodiments of the disclosure, the value of the first indicator is an integer n, and the time domain configuration is the (n+1) -th entry in the list of time domain configurations.
[0083] In one or more embodiments of the disclosure, when the indicated TCI state is associated with the first indicator having a value of 0, the physical layer resources are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter; and when the indicated TCI state is associated with the first indicator having a value n greater than 0, the physical layer resources are allocated based on the time domain configuration in the list of time domain configurations corresponding to a value of the first indicator.
[0084] In one or more embodiments of the disclosure, the value of the first indicator is an integer n, and the time domain configuration is the n-th entry in the list of time domain configurations.
[0085] In one or more embodiments of the disclosure, each time domain configuration in the list of time domain configurations comprises a set of periodicity and time domain offset; and when the indicated TCI state is associated with the first indicator, both a periodicity and a time domain offset of the physical layer resources for the configured uplink transmission are determined based on a periodicity and a time domain offset of the time domain configuration in the list of time domain configurations corresponding to the first indicator.
[0086] In one or more embodiments of the disclosure, each time domain configuration in the list of time domain configurations comprises a time domain offset; and when the indicated TCI state is associated with the first indicator, a time domain offset of the physical layer resources for the configured uplink transmission is determined based on a time domain offset of the time domain configuration in the list of time domain configurations corresponding to the first indicator.
[0087] In one or more embodiments of the disclosure, the TCI state is a joint TCI state or an UL TCI state.
[0088] In one or more embodiments of the disclosure, the indication of the TCI state comprises a Medium Access Control Control Element (MAC CE) or a DCI indicating the TCI state.
[0089] The present disclosure encompasses several embodiments for dynamically updating the time domain transmission configuration of configured uplink transmissions based on TCI state indications, each tailored to specific transmission types and adjustment mechanisms. Embodiment 1 focuses on SR transmissions on PUCCH, utilizing a list of TCI states associated with a first indicator to index pre-configured sets of {periodicity, slot offset} pairs for absolute time domain replacement. Embodiment 2 extends this to periodic or semi-persistent CSI reports on PUCCH, incorporating similar indexing but with options for lists of slot offsets alone. Embodiment 3 addresses configured grant PUSCH transmissions, adapting the mechanism to {periodicity, time domain offset} configurations. Embodiment 4 introduces a relative adjustment approach using a slot offset increment associated with TCI states, applicable across SR, CSI reports, and PUSCH. These embodiments differ primarily in the type of uplink transmission targeted (control vs. data channels) , the structure of the time domain configuration lists (absolute pairs vs. offsets) , and the adjustment logic (index-based selection vs. incremental offset) , providing flexible solutions to mitigate beam mismatch without RRC reconfiguration.
[0090] Embodiment 1: TCI state-based parameter adjustment
[0091] In one embodiment, a NW (e.g., base station 20) can provide a UE (e.g., UE 10 or 10a) with a list of N TCI states. Additionally, the UE can be configured with an uplink transmission configuration, such as a periodic transmission or semi-persistent transmission. An example of a periodic transmission configuration can be a configuration of schedule request, where the UE is configured with a periodicity, a slot offset, and a PUCCH resource. An example of a periodic transmission configuration can be a configuration of PUCCH-based periodic CSI reporting, where the UE is configured with a periodicity, a slot offset, and a PUCCH resource. An example of semi-persistent transmission configuration can be a configuration of PUCCH-based semi-persistent CSI reporting, where the UE is configured with a periodicity, a slot offset, and a PUCCH resource. An example of semi-persistent transmission configuration can be a configuration of PUSCH-based periodic CSI reporting, where the UE is configured with a periodicity and a slot offset, and the PUSCH resource allocation for the UE in one slot may be scheduled by a DCI.
[0092] In a first configuration of periodic transmission or semi-persistent transmission, the UE can be provided with a list of M configurations of {periodicity, slot offset} . One TCI state can be associated with or include a first indicator. The NW (e.g., BS 20) can indicate one TCI state to the UE, and the UE can apply the indicated TCI state to PUCCH transmissions and / or PUSCH transmission. When the UE applies the indicated TCI state to PUCCH or PUSCH associated with the first configuration of periodic transmission or semi-persistent transmission, the UE shall assume the periodicity and slot offset of the transmission to be the one of the M configurations of {periodicity, slot offset} corresponding to the value of the first indicator in the indicated TCI state. For example, the first indicator in the indicated TCI state can take values such as integer values 0, 1, 2, and so on. If the value of the first indicator in the indicated TCI state is n (where M > n ≥ 0) , the UE shall assume the periodicity and slot offset of the transmission of the first configuration are equal to the values contained in the (n+1) -th entry of those M configurations.
[0093] Embodiment 2: Methods for schedule request.
[0094] In one embodiment 2-1, a NW (e.g., base station 20) can provide a UE (e.g., UE 10 or 10a) with a list of N TCI states in an RRC configuration. The TCI state can be a joint TCI state or UL TCI state. Each TCI state can be configured with a first indicator which can take values such as integer values 0, 1, 2, and so on. The UE can be provided with a configured scheduling request configuration, which can include configuration of the physical layer resources on PUCCH where the UE may send the SR. In the configuration of physical layer resources on PUCCH for SR, the UE can be provided with one or more of the following information elements (IEs) : 1. A scheduling request resource ID; 2. A scheduling request ID; 3. A first parameter indicating a periodicity and a slot offset; 4. A second list of M sets of {periodicity, slot offset} ; and 5. A PUCCH resource ID.
[0095] The UE can determine the physical layer resources for the configured uplink transmission (e.g., configured scheduling request) based on: i) . the default periodicity and the default time domain offset specified by the at least one default time domain parameter (e.g., the first parameter) ; or ii) . a time domain configuration in the list of time domain configurations (e.g., the second list) .
[0096] The determination depends on whether the indicated TCI state is associated with a first indicator. This can be implemented in an embodiment of an implicit fallback mechanism or an explicit fallback mechanism.
[0097] In one embodiment, the determination of physical layer resources for a SR on the PUCCH relies on an implicit fallback mechanism wherein, if the indicated TCI state lacks or is not associated with a first indicator, the UE defaults to utilizing the periodicity and slot offset specified by a first parameter in the configuration for SR; whereas, when the first indicator is present with a value n (where M > n ≥ 0) , the UE selects the (n+1) -th configuration from a second list of M sets, thereby treating all provided indicator values as mappings to distinct list entries without a dedicated fallback value.
[0098] In contrast, a sub-embodiment introduces an explicit fallback indication, maintaining the implicit fallback for absent indicators, but specifying that a first indicator value of 0 explicitly directs the UE to the first parameter, while values n (where M > n > 0) map to the n-th configuration in the list, thus providing enhanced flexibility and signaling redundancy for network control in dynamic beam management scenarios.
[0099] The NW (e.g., BS 20) can indicate one TCI state to the UE, and the UE can apply the indicated TCI state on the PUCCH transmission. The UE can determine the physical layer resource for scheduling request based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the configuration of physical layer resources on PUCCH for SR. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n ≥ 0) , the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the (n+1) -th configuration in the second list of M sets in the configuration of physical layer resources on PUCCH for SR.
[0100] In one sub-embodiment, the UE can determine the physical layer resource for scheduling request based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the configuration of physical layer resources on PUCCH for SR. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is 0, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the configuration of physical layer resources on PUCCH for SR. 3. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n > 0) , the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the (n) -th configuration in the second list of M sets in the configuration of physical layer resources on PUCCH for SR.
[0101] In one embodiment 2-2, a NW (e.g., base station 20) can provide a UE (e.g., UE 10 or 10a) with a list of N TCI states in an RRC configuration. The TCI state can be a joint TCI state or UL TCI state. Each TCI state can be configured with a first indicator which can take values such as integer values 0, 1, 2, and so on. The UE can be provided with a configured scheduling request configuration, which can include configuration of the physical layer resources on PUCCH where the UE may send the SR. In the configuration of physical layer resources on PUCCH for SR, the UE can be provided with one or more of the following information elements: 1. A scheduling request resource ID; 2. A scheduling request ID; 3. A first parameter indicating a periodicity and a slot offset; 4. A second list of M slot offset; and 5. A PUCCH resource ID.
[0102] The UE can determine the physical layer resources for the configured uplink transmission (e.g., configured scheduling request) based on: i) . the default periodicity and the default time domain offset specified by the at least one default time domain parameter (e.g., the first parameter) ; or ii) . the default periodicity specified by the at least one default time domain parameter and a slot offset specified by a time domain configuration in the list of time domain configurations (e.g., the second list) .
[0103] The determination depends on whether the indicated TCI state is associated with a first indicator. This can be implemented in an embodiment of an implicit fallback mechanism or an explicit fallback mechanism.
[0104] In one embodiment, the determination of physical layer resources for a SR on the PUCCH relies on an implicit fallback mechanism wherein, if the indicated TCI state lacks or is not associated with a first indicator, the UE defaults to utilizing the periodicity and slot offset specified by a first parameter in the configuration for SR; whereas, when the first indicator is present with a value n (where M > n ≥ 0) , the UE selects the (n+1) -th configuration from a second list of M sets, thereby treating all provided indicator values as mappings to distinct list entries without a dedicated fallback value.
[0105] In contrast, a sub-embodiment introduces an explicit fallback indication, maintaining the implicit fallback for absent indicators, but specifying that a first indicator value of 0 explicitly directs the UE to the first parameter, while values n (where M > n > 0) map to the n-th configuration in the list, thus providing enhanced flexibility and signaling redundancy for network control in dynamic beam management scenarios.
[0106] The NW (e.g., BS 20) can indicate one TCI state to the UE, and the UE can apply the indicated TCI state to the PUCCH transmission. The UE can determine the physical layer resource for scheduling request based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the configuration of physical layer resources on PUCCH for SR. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n ≥ 0) , the UE can determine the physical layer resources on PUCCH based on the periodicity provided by the first parameter and the slot offset indicated by the (n+1) -th configuration in the second list of M slot offsets in the configuration of physical layer resources on PUCCH for SR.
[0107] In one sub-embodiment, the UE can determine the physical layer resource for scheduling request based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the configuration of physical layer resources on PUCCH for SR. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is 0, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the configuration of physical layer resources on PUCCH for SR. 3. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n > 0) , the UE can determine the physical layer resources on PUCCH based on the periodicity provided by the first parameter and the slot offset indicated by the (n) -th configuration in the second list of M slot offsets in the configuration of physical layer resources on PUCCH for SR.
[0108] Embodiment 3-1: Method for periodic CSI report on PUCCH
[0109] In one embodiment 3-1-1, a NW (e.g., base station 20) can provide a UE (e.g., UE 10 or 10a) with a list of N TCI states in an RRC configuration. The TCI state can be a joint TCI state or UL TCI state. Each TCI state can be configured with a first indicator which can take values such as integer values 0, 1, 2, and so on. The UE can be provided with a configuration of periodic CSI reporting on PUCCH and the UE can be provided with one or more of the following configuration parameters: 1. A report configuration ID; 2. A report configuration type set to periodic reporting; 3. A first parameter indicating a periodicity and a slot offset for CSI reporting; 4. A second list of M sets of {periodicity, slot offset} for CSI reporting; and 5. A PUCCH resource ID.
[0110] The UE can determine the physical layer resources for the configured uplink transmission (e.g., periodic CSI reporting) based on: i) . the default periodicity and the default time domain offset specified by the at least one default time domain parameter (e.g., the first parameter) ; or ii) . a time domain configuration in the list of time domain configurations (e.g., the second list) .
[0111] The determination depends on whether the indicated TCI state is associated with a first indicator. This can be implemented in an embodiment of an implicit fallback mechanism or an explicit fallback mechanism.
[0112] In one embodiment, the determination of physical layer resources for a periodic CSI report on the PUCCH relies on an implicit fallback mechanism wherein, if the indicated TCI state lacks or is not associated with a first indicator, the UE defaults to utilizing the periodicity and slot offset specified by a first parameter in the configuration for periodic CSI reporting; whereas, when the first indicator is present with a value n (where M > n ≥ 0) , the UE selects the (n+1) -th configuration from a second list of M sets, thereby treating all provided indicator values as mappings to distinct list entries without a dedicated fallback value.
[0113] In contrast, a sub-embodiment introduces an explicit fallback indication, maintaining the implicit fallback for absent indicators, but specifying that a first indicator value of 0 explicitly directs the UE to the first parameter, while values n (where M > n > 0) map to the n-th configuration in the list, thus providing enhanced flexibility and signaling redundancy for network control in dynamic beam management scenarios.
[0114] The NW (e.g., BS 20) can indicate one TCI state to the UE, and the UE can apply the indicated TCI state to the PUCCH transmission carrying the CSI report. The UE can determine the physical layer resource for CSI reporting based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the CSI report configuration. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n ≥ 0) , the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the (n+1) -th configuration in the second list of M sets in the CSI report configuration.
[0115] In one sub-embodiment, the UE can determine the physical layer resource for CSI reporting on PUCCH based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the CSI report configuration. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is 0, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the CSI report configuration. 3. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n > 0) , the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the (n) -th configuration in the second list of M sets in the CSI report configuration.
[0116] In one embodiment 3-1-2, a NW (e.g., base station 20) can provide a UE (e.g., UE 10 or 10a) with a list of N TCI states in an RRC configuration. The TCI state can be a joint TCI state or UL TCI state. Each TCI state can be configured with a first indicator which can take values such as integer values 0, 1, 2, and so on. The UE can be provided with a configuration of periodic CSI reporting on PUCCH and the UE can be provided with one or more of the following configuration parameters: 1. A report configuration ID; 2. A report configuration type set to periodic reporting; 3. A first parameter indicating a periodicity and a slot offset for CSI reporting; 4. A second list of M slot offsets for CSI reporting; and 5. A PUCCH resource ID.
[0117] The UE can determine the physical layer resources for the configured uplink transmission (e.g., periodic CSI reporting) based on: i) . the default periodicity and the default time domain offset specified by the at least one default time domain parameter (e.g., the first parameter) ; or ii) . the default periodicity specified by the at least one default time domain parameter and a slot offset specified by a time domain configuration in the list of time domain configurations (e.g., the second list) .
[0118] The determination depends on whether the indicated TCI state is associated with a first indicator. This can be implemented in an embodiment of an implicit fallback mechanism or an explicit fallback mechanism.
[0119] In one embodiment, the determination of physical layer resources for a periodic CSI report on the PUCCH relies on an implicit fallback mechanism wherein, if the indicated TCI state lacks or is not associated with a first indicator, the UE defaults to utilizing the periodicity and slot offset specified by a first parameter in the configuration for periodic CSI reporting; whereas, when the first indicator is present with a value n (where M > n ≥ 0) , the UE selects the (n+1) -th configuration from a second list of M sets, thereby treating all provided indicator values as mappings to distinct list entries without a dedicated fallback value.
[0120] In contrast, a sub-embodiment introduces an explicit fallback indication, maintaining the implicit fallback for absent indicators, but specifying that a first indicator value of 0 explicitly directs the UE to the first parameter, while values n (where M > n > 0) map to the n-th configuration in the list, thus providing enhanced flexibility and signaling redundancy for network control in dynamic beam management scenarios.
[0121] The NW (e.g., BS 20) can indicate one TCI state to the UE, and the UE can apply the indicated TCI state to the PUCCH transmission carrying the CSI report. The UE can determine the physical layer resource for CSI reporting based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the CSI report configuration. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n ≥ 0) , the UE can determine the physical layer resources on PUCCH based on the periodicity provided by the first parameter and the slot offset indicated by the (n+1) -th configuration in the second list of M sets in the CSI report configuration.
[0122] In one sub-embodiment, the UE can determine the physical layer resource for CSI reporting on PUCCH based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the CSI report configuration. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is 0, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the CSI report configuration. 3. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n > 0) , the UE can determine the physical layer resources on PUCCH based on the periodicity provided by the first parameter and the slot offset indicated by the (n) -th configuration in the second list of M slot offsets in the CSI report configuration.
[0123] Embodiment 3-2: Method for semi-persistent CSI report on PUCCH
[0124] In one embodiment 3-2-1, a NW (e.g., base station 20) can provide a UE (e.g., UE 10 or 10a) with a list of N TCI states in an RRC configuration. The TCI state can be a joint TCI state or UL TCI state. Each TCI state can be configured with a first indicator which can take values such as integer values 0, 1, 2, and so on. The UE can be provided with a configuration of semi-persistent CSI reporting on PUCCH and the UE can be provided with one or more of the following configuration parameters: 1. A report configuration ID; 2. A report configuration type set to semi-persistent reporting 3. A first parameter indicating a periodicity and a slot offset for CSI reporting; 4. A second list of M sets of {periodicity, slot offset} for CSI reporting; and 5. A PUCCH resource ID.
[0125] The UE can determine the physical layer resources for the configured uplink transmission (e.g., semi-persistent CSI reporting) based on: i) . the default periodicity and the default time domain offset specified by the at least one default time domain parameter (e.g., the first parameter) ; or ii) . a time domain configuration in the list of time domain configurations (e.g., the second list) .
[0126] The determination depends on whether the indicated TCI state is associated with a first indicator. This can be implemented in an embodiment of an implicit fallback mechanism or an explicit fallback mechanism.
[0127] In one embodiment, the determination of physical layer resources for a semi-persistent CSI report on the PUCCH relies on an implicit fallback mechanism wherein, if the indicated TCI state lacks or is not associated with a first indicator, the UE defaults to utilizing the periodicity and slot offset specified by a first parameter in the configuration for semi-persistent CSI reporting; whereas, when the first indicator is present with a value n (where M > n ≥ 0) , the UE selects the (n+1) -th configuration from a second list of M sets, thereby treating all provided indicator values as mappings to distinct list entries without a dedicated fallback value.
[0128] In contrast, a sub-embodiment introduces an explicit fallback indication, maintaining the implicit fallback for absent indicators, but specifying that a first indicator value of 0 explicitly directs the UE to the first parameter, while values n (where M > n > 0) map to the n-th configuration in the list, thus providing enhanced flexibility and signaling redundancy for network control in dynamic beam management scenarios.
[0129] The NW (e.g., BS 20) can indicate one TCI state to the UE, and the UE can apply the indicated TCI state to the PUCCH transmission carrying the CSI report. The UE can determine the physical layer resource for CSI reporting based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the CSI report configuration. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n ≥ 0) , the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the (n+1) -th configuration in the second list of M sets in the CSI report configuration.
[0130] In one sub-embodiment, the UE can determine the physical layer resource for CSI reporting on PUCCH based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the CSI report configuration. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is 0, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the CSI report configuration. 3. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n > 0) , the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the (n) -th configuration in the second list of M sets in the CSI report configuration.
[0131] In one embodiment 3-2-2, a NW (e.g., base station 20) can provide a UE (e.g., UE 10 or 10a) with a list of N TCI states in an RRC configuration. The TCI state can be a joint TCI state or UL TCI state. Each TCI state can be configured with a first indicator which can take values such as integer values 0, 1, 2, and so on. The UE can be provided with a configuration of semi-persistent CSI reporting on PUCCH and the UE can be provided with one or more of the following configuration parameters: 1. A report configuration ID; 2. A report configuration type set to semi-persistent reporting 3. A first parameter indicating a periodicity and a slot offset for CSI reporting; 4. A second list of M slot offsets for CSI reporting; and 5. A PUCCH resource ID.
[0132] The UE can determine the physical layer resources for the configured uplink transmission (e.g., semi-persistent CSI reporting) based on: i) . the default periodicity and the default time domain offset specified by the at least one default time domain parameter (e.g., the first parameter) ; or ii) . the default periodicity specified by the at least one default time domain parameter and a slot offset specified by a time domain configuration in the list of time domain configurations (e.g., the second list) .
[0133] The determination depends on whether the indicated TCI state is associated with a first indicator. This can be implemented in an embodiment of an implicit fallback mechanism or an explicit fallback mechanism.
[0134] In one embodiment, the determination of physical layer resources for a semi-persistent CSI report on the PUCCH relies on an implicit fallback mechanism wherein, if the indicated TCI state lacks or is not associated with a first indicator, the UE defaults to utilizing the periodicity and slot offset specified by a first parameter in the configuration for semi-persistent CSI reporting; whereas, when the first indicator is present with a value n (where M > n ≥ 0) , the UE selects the (n+1) -th configuration from a second list of M sets, thereby treating all provided indicator values as mappings to distinct list entries without a dedicated fallback value.
[0135] In contrast, a sub-embodiment introduces an explicit fallback indication, maintaining the implicit fallback for absent indicators, but specifying that a first indicator value of 0 explicitly directs the UE to the first parameter, while values n (where M > n > 0) map to the n-th configuration in the list, thus providing enhanced flexibility and signaling redundancy for network control in dynamic beam management scenarios.
[0136] The NW (e.g., BS 20) can indicate one TCI state to the UE, and the UE can apply the indicated TCI state to the PUCCH transmission carrying the CSI report. The UE can determine the physical layer resource for CSI reporting based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the CSI report configuration. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n ≥ 0) , the UE can determine the physical layer resources on PUCCH based on the periodicity provided by the first parameter and the slot offset indicated by the (n+1) -th configuration in the second list of M sets in the CSI report configuration.
[0137] In one sub-embodiment, the UE can determine the physical layer resource for CSI reporting on PUCCH based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the CSI report configuration. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is 0, the UE can determine the physical layer resources on PUCCH based on the periodicity and slot offset indicated by the first parameter included in the CSI report configuration. 3. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n > 0) , the UE can determine the physical layer resources on PUCCH based on the periodicity provided by the first parameter and the slot offset indicated by the (n) -th configuration in the second list of M slot offsets in the CSI report configuration.
[0138] Embodiment 4: Method for configurated PUSCH transmission
[0139] In one embodiment 4-1, a NW (e.g., base station 20) can provide a UE (e.g., UE 10 or 10a) with a list of N TCI states in an RRC configuration. The TCI state can be a joint TCI state or UL TCI state. Each TCI state can be configured with a first indicator which can take values such as integer values 0, 1, 2, and so on. The UE can be provided with semi-statically configured PUSCH resource allocation. In other word, the PUSCH resource allocation can be semi-statically configured through higher layer parameter. The UE can be provided with the following higher layer parameters in configured grant configuration to be applied on the configured PUSCH transmission: 1. A first parameter to indicate time domain periodicity; 2. A second parameter to indicate time domain offset; and 3. A third list of M sets of {periodicity, time domain offset} for PUSCH resource allocation;
[0140] The UE can determine the physical layer resources for the configured uplink transmission (e.g., configured PUSCH transmission) based on: i) . the default periodicity and the default time domain offset specified by the at least one default time domain parameter (e.g., the first parameter and the second parameter) ; or ii) . a time domain configuration in the list of time domain configurations (e.g., the third list) .
[0141] The determination depends on whether the indicated TCI state is associated with a first indicator. This can be implemented in an embodiment of an implicit fallback mechanism or an explicit fallback mechanism.
[0142] In one embodiment, the determination of physical layer resources for a configured PUSCH transmission on the PUSCH relies on an implicit fallback mechanism wherein, if the indicated TCI state lacks or is not associated with a first indicator, the UE defaults to utilizing the periodicity and slot offset specified by a first parameter and the second parameter in the configuration for configured PUSCH transmission; whereas, when the first indicator is present with a value n (where M > n ≥ 0) , the UE selects the (n+1) -th configuration from the third list of M sets of {periodicity, time domain offset} , thereby treating all provided indicator values as mappings to distinct list entries without a dedicated fallback value.
[0143] In contrast, a sub-embodiment introduces an explicit fallback indication, maintaining the implicit fallback for absent indicators, but specifying that a first indicator value of 0 explicitly directs the UE to the first parameter and the second parameter, while values n (where M > n > 0) map to the n-th configuration in the third list, thus providing enhanced flexibility and signaling redundancy for network control in dynamic beam management scenarios.
[0144] The NW (e.g., BS 20) can indicate one TCI state to the UE, and the UE can apply the indicated TCI state to the PUSCH transmission. The UE can determine the physical layer resource for PUSCH transmission based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources for the PUSCH based on the periodicity indicated by the first parameter and the slot offset indicated by the second parameter included in the configured grant configuration. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n ≥ 0) , the UE can determine the physical layer resources for the PUSCH based on the periodicity and slot offset indicated by the (n+1) -th configuration in the third list of M sets in the configured grant configuration.
[0145] In one sub-embodiment, the UE can determine the physical layer resource for PUSCH based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources for PUSCH based on the periodicity indicated by the first parameter and the slot offset indicated by the second parameter included in the configured grant configuration. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is 0, the UE can determine the physical layer resources for the PUSCH based on the periodicity indicated by the first parameter and the slot offset indicated by the second parameter included in the configured grant configuration. 3. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n > 0) , the UE can determine the physical layer resources for the PUSCH based on the periodicity and slot offset indicated by the (n) -th configuration in the second list of M sets in the configured grant configuration.
[0146] In one embodiment 4-2, a NW (e.g., base station 20) can provide a UE (e.g., UE 10 or 10a) with a list of N TCI states in an RRC configuration. The TCI state can be a joint TCI state or UL TCI state. Each TCI state can be configured with a first indicator which can take values such as integer values 0, 1, 2, and so on. The UE can be provided with semi-statically configured PUSCH resource allocation. In other word, the PUSCH resource allocation can be semi-statically configured through higher layer parameter. The UE can be provided with the following higher layer parameters in configured grant configuration to be applied on the configured PUSCH transmission: 1. A first parameter to indicate time domain periodicity; 2. A second parameter to indicate time domain offset; and 3. A third list of M time domain offset for PUSCH resource allocation;
[0147] The UE can determine the physical layer resources for the configured uplink transmission (e.g., configured PUSCH transmission) based on: i) . the default periodicity and the default time domain offset specified by the at least one default time domain parameter (e.g., the first parameter and the second parameter) ; or ii) . the default periodicity specified by the at least one default time domain parameter and a time domain offset specified by a time domain configuration in the list of time domain configurations (e.g., the third list) .
[0148] The determination depends on whether the indicated TCI state is associated with a first indicator. This can be implemented in an embodiment of an implicit fallback mechanism or an explicit fallback mechanism.
[0149] In one embodiment, the determination of physical layer resources for a configured PUSCH transmission on the PUSCH relies on an implicit fallback mechanism wherein, if the indicated TCI state lacks or is not associated with a first indicator, the UE defaults to utilizing the periodicity and slot offset specified by a first parameter and the second parameter in the configuration for configured PUSCH transmission; whereas, when the first indicator is present with a value n (where M > n ≥ 0) , the UE selects the (n+1) -th configuration from the third list of M sets of {time domain offset} , thereby treating all provided indicator values as mappings to distinct list entries without a dedicated fallback value.
[0150] In contrast, a sub-embodiment introduces an explicit fallback indication, maintaining the implicit fallback for absent indicators, but specifying that a first indicator value of 0 explicitly directs the UE to the first parameter and the second parameter, while values n (where M > n > 0) map to the n-th configuration in the third list, thus providing enhanced flexibility and signaling redundancy for network control in dynamic beam management scenarios.
[0151] The NW (e.g., BS 20) can indicate one TCI state to the UE, and the UE can apply the indicated TCI state to the PUSCH transmission. The UE can determine the physical layer resource for the PUSCH based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources for the PUSCH based on the periodicity indicated by the first parameter and the slot offset indicated by the second parameter included in the configured grant configuration. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n ≥ 0) , the UE can determine the physical layer resources for the PUSCH based on the periodicity provided by the first parameter and the slot offset indicated by the (n+1) -th configuration in the third list of M time domain offsets in the configured grant configuration.
[0152] In one sub-embodiment, the UE can determine the physical layer resource for the PUSCH based on the indicated TCI state as follows: 1. If the indicated TCI state does not contain or is not associated with the first indicator, the UE can determine the physical layer resources for the PUSCH based on the periodicity indicated by the first parameter and the slot offset indicated by the second parameter included in the configured grant configuration. 2. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is 0, the UE can determine the physical layer resources for the PUSCH based on the periodicity indicated by the first parameter and the slot offset indicated by the second parameter included in the configured grant configuration. 3. If the indicated TCI state contains or is associated with the first indicator and the value of the first indicator is n (where M > n > 0) , the UE can determine the physical layer resources for the PUSCH based on the periodicity provided by the first parameter and the slot offset indicated by the (n) -th entry in the third list of M time domain offsets in the configured grant configuration.
[0153] The proposed method enables dynamic adjustment of the time domain transmission location (periodicity and / or slot offset) of configured uplink transmissions-including SR, periodic CSI report, semi-persistent CSI report on PUCCH, and configured grant PUSCH-based on the TCI state indicated by the gNB, without requiring RRC reconfiguration. This eliminates the large latency associated with RRC-level reconfiguration procedures.
[0154] Additionally, by associating each TCI state with a first indicator that indexes a pre-configured list of time domain configurations, the UE can promptly align its configured uplink transmission timing with the receive beam indicated by the gNB. This resolves the mismatch between the gNB's receive beam mapping and the UE's transmission timing that may otherwise occur upon TCI state switching, thereby significantly reducing scheduling difficulty for the network.
[0155] Further, the disclosed mechanism provides a flexible and scalable framework supporting multiple time domain configuration variants-including lists of {periodicity, slot offset} pairs or lists of slot offsets alone-applicable uniformly across different types of configured uplink transmissions (SR, periodic CSI, semi-persistent CSI on PUCCH, and configured grant PUSCH) . This flexibility allows network deployments to optimize uplink beam-aligned transmission scheduling with minimal signaling overhead.
[0156] With reference to FIG. 7, the UE 10 may include a processor 11a, a memory 12a, and a transceiver 13a. The processor 11a is configured to call and run a computer program stored in the memory 12a, to cause UE 10 in which the processor 11a is installed to execute the disclosed method, steps, and / or functions of a UE. The UE 10 is an example of the UE in the description. The transceiver 13a may include baseband circuitry and radio frequency (RF) circuitry.
[0157] With reference to FIG. 8, the base station 20 is a network device and may include a processor 21a, a memory 22a, and a transceiver 23a. The processor 21a is configured to call and run a computer program stored in the memory 22a, to cause base station 20 in which the processor 21a is installed to execute the method, steps, and / or functions of a RAN, such as a base station 20a. The eNB, ng-eNB, and gNB are examples of the base station in the description. The base station can have a functional split configuration such that a first portion of the base station (referred to as onboard eNB, ng-eNB, and gNB) is installed in an NTN device, such as a satellite, and a second portion of the base station (referred to as on-ground eNB, ng-eNB, and gNB) is installed in a terrestrial network (TN) device. The transceiver 23a, may include baseband circuitry and radio frequency (RF) circuitry.
[0158] With reference to FIG. 9, the network device 30 may be a core network device and may include a processor 31a, a memory 32a, and a transceiver 33a. The processor 31a is configured to call and run a computer program stored in the memory 32a, to cause network node 30 in which the processor 31a is installed to execute the method, steps, and / or functions of a network device, such as network entity device 30a, EPC, 5G Core, 6G Core, IMS server, and other network devices in the description. The network device can have a functional split configuration such that a first portion of the network device (referred to as onboard core network device, such as MME-onboard) is installed in an NTN device, such as a satellite, and a second portion of the network device (referred to as on-ground core network device, such as MME-ground) is installed in a terrestrial network (TN) device. The transceiver 33a, may include baseband circuitry and radio frequency (RF) circuitry.
[0159] With reference to FIG. 10, the embodiment of the disclosure also provides a chip 70 that may correspond to a UE in the embodiments of the disclosure. The chip 70 may implement a corresponding process realized by the UE in various methods of the embodiments of the disclosure. The chip 70 includes a processor 71, and the processor 71 may call and run a computer program from memory to implement the methods in the embodiments of the present application.
[0160] Optionally, the chip 70 may also include a memory 72. In particular, the processor 71 may call and run the computer program from the memory 72 to implement the methods in the embodiments of the present application.
[0161] Moreover, the memory 72 may be a separate device from the processor 71 or may be integrated into the processor 71.
[0162] Optionally, the chip 70 may include an input interface 73. Note that the processor 71 may control the input interface 73 to communicate with other devices or chips, specifically, to obtain messages or data sent by other devices or chips.
[0163] Optionally, the chip 70 may further include an output interface 74. Note that the processor 71 may control the output interface 74 to communicate with other devices or chips, specifically, to output messages or data to other devices or chips.
[0164] With reference to FIG. 11, the embodiment of the disclosure also provides another chip 80 that may correspond to a RAN in the description, and the chip 80 may implement the corresponding processes implemented by the base station in the various methods of the embodiments of the disclosure. The chip 80 includes a processor 81, and the processor 81 may call and run a computer program from the memory 82 to implement the methods in the embodiments of the present application.
[0165] Optionally, the chip 80 may further include a memory 82. In particular, the processor 81 may call and run the computer program from the memory 82 to implement the methods in the embodiments of the present application.
[0166] Wherein the memory 82 may be a separate device from the processor 81 or may be integrated into the processor 81.
[0167] Optionally, the chip 80 may also include an input interface 83. In particular, the processor 81 may control the input interface 83 to communicate with other devices or chips, specifically, to obtain messages or data sent by other devices or chips.
[0168] Optionally, the chip may further include an output interface 84. In particular, the processor 81 may control the output interface 84 to communicate with other devices or chips, specifically, to output messages or data to other devices or chips.
[0169] With reference to FIG. 12, the embodiment of the disclosure also provides another chip 90 that may correspond to a network device (e.g., EPC, 5G Core, 6G Core, IMS server, RAN) in the description, and the chip 90 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of the disclosure. The chip 90 includes a processor 91, and the processor 91 may call and run a computer program from the memory 92 to implement the methods in the embodiments of the present application.
[0170] Optionally, the chip 90 may further include a memory 92. In particular, the processor 91 may call and run the computer program from the memory 92 to implement the methods in the embodiments of the present application.
[0171] Wherein the memory 92 may be a separate device from the processor 91 or may be integrated into the processor 91.
[0172] Optionally, the chip 90 may also include an input interface 93. In particular, the processor 91 may control the input interface 93 to communicate with other devices or chips, specifically, to obtain messages or data sent by other devices or chips.
[0173] Optionally, the chip may further include an output interface 94. In particular, the processor 91 may control the output interface 94 to communicate with other devices or chips, specifically, to output messages or data to other devices or chips.
[0174] The embodiment of the present disclosure is a combination of techniques / processes that may be adopted in 3GPP specification to create an end product.
[0175] FIG. 13 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the system using any suitably configured hardware and / or software. FIG. 13 illustrates the system 700 including a radio frequency (RF) circuitry 710, a baseband circuitry 720, a processing unit 730, a memory / storage 740, a display 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780, coupled with each other as illustrated.
[0176] The processing unit 730 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combinations of general-purpose processors and dedicated processors, such as graphics processors and application processors. The processors may be coupled with the memory / storage and configured to execute instructions stored in the memory / storage to enable various applications and / or operating systems running on the system.
[0177] The baseband circuitry 720 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processors may include a baseband processor. The baseband circuitry may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with 5G NR, LTE, an evolved universal terrestrial radio access network (EUTRAN) and / or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) . Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry. In various embodiments, the baseband circuitry 720 may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency. For example, in some embodiments, baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.
[0178] The RF circuitry 710 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. In various embodiments, the RF circuitry 710 may include circuitry to operate with signals that are not strictly considered as being in a radio frequency. For example, in some embodiments, RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.
[0179] In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the UE, eNB, or gNB may be embodied in whole or in part in one or more of the RF circuitries, the baseband circuitry, and / or the processing unit. As used herein, “circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC) , an electronic circuit, a processor (shared, dedicated, or group) , and / or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and / or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuitry, the processing unit, and / or the memory / storage may be implemented together on a system on a chip (SOC) .
[0180] The memory / storage 740 may be used to load and store data and / or instructions, for example, for the system. The memory / storage for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM) ) , and / or non-volatile memory, such as flash memory. In various embodiments, the I / O interface 780 may include one or more user interfaces designed to enable user interaction with the system and / or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface.
[0181] In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and / or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuitry and / or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite. In various embodiments, the display 750 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, the system 700 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an Ultrabook, a smartphone, etc. In various embodiments, the system may have more or less components, and / or different architectures. Where appropriate, the methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.
[0182] The embodiment of the present disclosure is a combination of techniques / processes that may be adopted in 3GPP specification to create an end product.
[0183] A person having ordinary skill in the art understands that each of the units, algorithm, and steps described and disclosed in the embodiments of the present disclosure are realized using electronic hardware or combinations of software for computers and electronic hardware. Whether the functions run in hardware or software depends on the condition of the application and design requirement for a technical plan. A person who has ordinary skill in the art may use different ways to realize the function for each specific application while such realizations should not go beyond the scope of the present disclosure. It is understood by a person having ordinary skill in the art that he / she may refer to the working processes of the system, device, and unit in the above-mentioned embodiment since the working processes of the above-mentioned system, device, and unit are basically the same. For easy description and simplicity, these working processes will not be detailed.
[0184] It is to be understood that the systems, devices, and methods disclosed in the embodiments of the present disclosure may be implemented in alternative configurations. The embodiments described are illustrative and not restrictive. The division of functional units is based on logical functions, and alternative divisions may be employed in practice. Multiple units or components may be combined or integrated into another system, or certain features may be omitted or not implemented. Additionally, the described couplings, whether direct, indirect, or communicative, may be achieved through various interfaces, devices, or units using electrical, mechanical, or other forms of connection.
[0185] The functional units described herein may or may not be physically separate. Displayed units may or may not constitute physical entities and may be located in a single location or distributed across multiple network entities. Some or all of the units may be selected based on the objectives of specific embodiments. Furthermore, each functional unit in the embodiments may be integrated into a single processing unit, exist as physically distinct units, or be integrated with other units into a single processing unit.
[0186] If the software function unit is realized and used and sold as a product, it may be stored in a readable storage medium in a computer. Based on this understanding, the technical plan proposed by the present disclosure may be essentially or partially realized in the form of a software product. Or, one part of the technical plan beneficial to conventional technology may be realized as the form of a software product. The software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the steps disclosed by the embodiments of the present disclosure. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM) , a random-access memory (RAM) , a floppy disk, or other kinds of media capable of storing program codes.
[0187] While the present disclosure has been described in connection with what is considered the most practical and preferred embodiments, it is understood that the present disclosure is not limited to the disclosed embodiments but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.
Claims
1.A method of uplink transmission reconfiguration performed by a user equipment (UE) , comprising:receiving a radio resource control (RRC) configuration comprising:a list of Transmission Configuration Indicator (TCI) states;an uplink transmission configuration comprising at least one default time domain parameter specifying a default periodicity and a default time domain offset; anda list of time domain configurations;receiving an indication of one TCI state of the list of TCI states to be applied on a configured uplink transmission associated with the uplink transmission configuration; andperforming the configured uplink transmission on physical layer resources for the configured uplink transmission based on the TCI state indicated in the indication, wherein depending on whether the indicated TCI state is associated with a first indicator, the physical layer resources for the configured uplink transmission are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter.2.The method of claim 1, wherein the configured uplink transmission is carried on a physical uplink control channel (PUCCH) , and the uplink transmission configuration further comprises a PUCCH resource identifier, wherein the at least one default time domain parameter is a single parameter specifying both the default periodicity and the default slot offset.3.The method of claim 2, wherein the configured uplink transmission is a scheduling request (SR) , and the uplink transmission configuration further comprises a scheduling request resource identifier and a scheduling request identifier.4.The method of claim 2, wherein the configured uplink transmission is a periodic channel state information (CSI) report, and the uplink transmission configuration further comprises a report configuration identifier and a report configuration type set to periodic.5.The method of claim 2, wherein the configured uplink transmission is a semi-persistent CSI report, and the uplink transmission configuration further comprises a report configuration identifier and a report configuration type set to semi-persistent.6.The method of claim 1, wherein the configured uplink transmission is a semi-statically configured physical uplink shared channel (PUSCH) transmission under a configured grant, and the at least one default time domain parameter comprises a first parameter specifying the default periodicity and a second parameter specifying the default time domain offset.7.The method of claim 1, wherein when the indicated TCI state is not associated with a first indicator, the physical layer resources are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter; andwhen the indicated TCI state is associated with the first indicator having a value, the physical layer resources are allocated based on the time domain configuration in the list of time domain configurations corresponding to a value of the first indicator.8.The method of claim 7, wherein the value of the first indicator is an integer n, and the time domain configuration is the (n+1) -th entry in the list of time domain configurations.9.The method of claim 1, wherein when the indicated TCI state is associated with the first indicator having a value of 0, the physical layer resources are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter; andwhen the indicated TCI state is associated with the first indicator having a value n greater than 0, the physical layer resources are allocated based on the time domain configuration in the list of time domain configurations corresponding to a value of the first indicator.10.The method of claim 9, wherein the value of the first indicator is an integer n, and the time domain configuration is the n-th entry in the list of time domain configurations.11.The method of claim 7 or 9, wherein each time domain configuration in the list of time domain configurations comprises a set of periodicity and time domain offset; andwhen the indicated TCI state is associated with the first indicator, both a periodicity and a time domain offset of the physical layer resources for the configured uplink transmission are determined based on a periodicity and a time domain offset of the time domain configuration in the list of time domain configurations corresponding to the first indicator.12.The method of claim 7 or 9, wherein each time domain configuration in the list of time domain configurations comprises a time domain offset; andwhen the indicated TCI state is associated with the first indicator, a time domain offset of the physical layer resources for the configured uplink transmission is determined based on a time domain offset of the time domain configuration in the list of time domain configurations corresponding to the first indicator.13.The method of claim 1, wherein the TCI state is a joint TCI state or an uplink (UL) TCI state.14.The method of claim 1, wherein receiving the indication of the TCI state comprises receiving a Medium Access Control Control Element (MAC CE) or a Downlink Control Information (DCI) indicating the TCI state.15.A method of uplink transmission reconfiguration performed by a network node, comprising:transmitting a radio resource control (RRC) configuration comprising:a list of Transmission Configuration Indicator (TCI) states;an uplink transmission configuration comprising at least one default time domain parameter specifying a default periodicity and a default time domain offset; anda list of time domain configurations;transmitting an indication of one TCI state of the list of TCI states to be applied on a configured uplink transmission associated with the uplink transmission configuration, wherein the indication of the TCI state indicated, depending on whether the indicated TCI state is associated with a first indicator, indicates that the physical layer resources for the configured uplink transmission are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter or based on a periodicity and an offset of one time domain configuration in the list of time domain configurations or based on an offset of one time domain configuration in the list of time domain configurations and the default periodicity specified by the at least one default time domain parameter; andreceiving the configured uplink transmission on the physical layer resources.16.The method of claim 15, wherein the configured uplink transmission is carried on a physical uplink control channel (PUCCH) , and the uplink transmission configuration further comprises a PUCCH resource identifier, wherein the at least one default time domain parameter is a single parameter specifying both the default periodicity and the default slot offset.17.The method of claim 16, wherein the configured uplink transmission is a scheduling request (SR) , and the uplink transmission configuration further comprises a scheduling request resource identifier and a scheduling request identifier.18.The method of claim 16, wherein the configured uplink transmission is a periodic CSI report, and the uplink transmission configuration further comprises a report configuration identifier and a report configuration type set to periodic.19.The method of claim 16, wherein the configured uplink transmission is a semi-persistent CSI report, and the uplink transmission configuration further comprises a report configuration identifier and a report configuration type set to semi-persistent.20.The method of claim 15, wherein the configured uplink transmission is a semi-statically configured physical uplink shared channel (PUSCH) transmission under a configured grant, and the at least one default time domain parameter comprises a first parameter specifying the default periodicity and a second parameter specifying the default time domain offset.21.The method of claim 15, wherein when the indicated TCI state is not associated with a first indicator, the physical layer resources are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter; andwhen the indicated TCI state is associated with the first indicator having a value, the physical layer resources are allocated based on the time domain configuration in the list of time domain configurations corresponding to a value of the first indicator.22.The method of claim 21, wherein the value of the first indicator is an integer n, and the time domain configuration is the (n+1) -th entry in the list of time domain configurations.23.The method of claim 15, wherein when the indicated TCI state is associated with the first indicator having a value of 0, the physical layer resources are allocated based on the default periodicity and the default time domain offset specified by the at least one default time domain parameter; andwhen the indicated TCI state is associated with the first indicator having a value n greater than 0, the physical layer resources are allocated based on the time domain configuration in the list of time domain configurations corresponding to a value of the first indicator.24.The method of claim 23, wherein the value of the first indicator is an integer n, and the time domain configuration is the n-th entry in the list of time domain configurations.25.The method of claim 21 or 23, wherein each time domain configuration in the list of time domain configurations comprises a set of periodicity and time domain offset; andwhen the indicated TCI state is associated with the first indicator, both a periodicity and a time domain offset of the physical layer resources for the configured uplink transmission are allocated based on a periodicity and a time domain offset of the time domain configuration in the list of time domain configurations corresponding to the first indicator.26.The method of claim 21 or 23, wherein each time domain configuration in the list of time domain configurations comprises a time domain offset; andwhen the indicated TCI state is associated with the first indicator, a time domain offset of the physical layer resources for the configured uplink transmission is allocated based on a time domain offset of the time domain configuration in the list of time domain configurations corresponding to the first indicator.27.The method of claim 15, wherein the TCI state is a joint TCI state or an uplink (UL) TCI state.28.The method of claim 15, wherein the indication of the TCI state comprises a Medium Access Control Control Element (MAC CE) or a Downlink Control Information (DCI) indicating the TCI state.29.A user equipment (UE) comprising: a processor configured to call and run a computer program stored in a memory, to cause a device in which the processor is installed to execute the method of any of claims 1 to 14.30.A network node comprising:a processor configured to call and run a computer program stored in a memory, to cause a device in which the processor is installed to execute the method of any of claims 15 to 28.31.A chip, comprising:a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the method of any of claims 1 to 28.32.A non-transitory computer-readable storage medium, in which a computer program is stored, wherein the computer program causes a computer to execute the method of any of claims 1 to 28.33.A computer program product, comprising a computer program, wherein the computer program causes a computer to execute the method of any of claims 1 to 28.34.A computer program, wherein the computer program causes a computer to execute the method of any of claims 1 to 28.
