LCP restriction enhancement

Abstract

Aspects of enhanced logical channel prioritization mapping processes and restrictions are disclosed. In one aspect, a wireless communication method includes: receiving, by a user equipment (UE), a logical channel prioritization (LCP) restriction configuration for a logical channel, the LCP restriction configuration indicating an SRS configuration set associated with the logical channel; receiving, by the UE, an uplink grant, the uplink grant indicating an uplink grant instance and an SRS configuration for the uplink grant instance; and selecting, by the UE, a logical channel of resources to use the uplink grant instance based in part on the SRS configuration set and the SRS configuration for the uplink grant instance. Other aspects are also described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Patent Application No. 16 / 945,329, filed on July 31, 2020, entitled “LCP RESTRICTION ENHANCEMENT,” and U.S. Provisional Patent Application No. 62 / 884067, filed on August 7, 2019, entitled “LCP RESTRICTION ENHANCEMENT,” both of which are expressly incorporated herein by reference in their entirety. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly to logical channel prioritization (LCP) enhancements such as for multiple transmit receive point (TRP) modes. Background Art

[0004] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcasting, etc. These wireless networks can be multiple access networks that can support multiple users by sharing available network resources. Such a network is typically a multiple access network that supports communication for multiple users by sharing available network resources. An example of such a network is the Universal Terrestrial Radio Access Network (UTRAN). UTRAN is a radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), which is a third generation (3G) mobile phone technology supported by the Third Generation Partnership Project (3GPP). Examples of multiple access network formats include code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, and single carrier FDMA (SC-FDMA) networks.

[0005] A wireless communication network may include multiple base stations or Node Bs that can support communication for multiple user equipments (UEs). A UE may communicate with a base station via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a base station to a UE, while an uplink (or reverse link) refers to a communication link from a UE to a base station.

[0006] The base station may send data and control information to the UE on the downlink, and / or may receive data and control information from the UE on the uplink. On the downlink, the transmission from the base station may encounter interference due to transmissions from neighboring base stations or from other radio frequency (RF) transmitters. On the uplink, the transmission from the UE may encounter interference from uplink transmissions of other UEs communicating with neighboring base stations, or interference from other wireless RF transmitters. This interference may reduce performance on both the downlink and uplink.

[0007] As the demand for mobile broadband access continues to increase, more and more UEs are accessing long-range wireless communication networks, and more and more short-range wireless systems are being deployed in communities, increasing the possibility of interference and congested networks. The research and development of wireless technology continues to advance, not only meeting the growing demand for mobile broadband access, but also improving the user experience of mobile communications. Summary of the invention

[0008] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not a broad overview of all expected features of the present disclosure, and its purpose is neither to determine the key or important elements of all aspects of the present disclosure, nor to describe the scope of any or all aspects of the present disclosure. Its only purpose is to present some concepts of one or more aspects of the present disclosure in the form of an overview, as a preface to the more detailed description proposed later.

[0009] The described technology relates to improved methods, systems, devices and apparatuses that support enhanced logical channel prioritization mapping processes and restrictions, such as indications of logical channel prioritization (LCP) restrictions based on SRS / SRI (sounding reference signal (SRS) / SRS resource indicator (SRI)). This enhanced LCP mapping process can enable operation in multi-TRP mode and / or mapping of duplicate data for transmission via the same carrier. Therefore, such technology can increase reliability and reduce latency, and enable operation in URLLC mode.

[0010] In one aspect of the present disclosure, a wireless communication method includes: receiving, by a user equipment (UE), a logical channel prioritization (LCP) restriction configuration for a logical channel, the LCP restriction configuration indicating an SRS configuration set associated with the logical channel; receiving, by the UE, an uplink grant, the uplink grant indicating an uplink grant instance and an SRS configuration for the uplink grant instance; and selecting, by the UE, a logical channel of resources to use the uplink grant instance based in part on the SRS configuration set and the SRS configuration for the uplink grant instance.

[0011] In an additional aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes at least one processor and a memory coupled to the processor. The processor is configured to: receive, by a user equipment (UE), a logical channel prioritization (LCP) restriction configuration for a logical channel, the LCP restriction configuration indicating an SRS configuration set associated with the logical channel; receive, by the UE, an uplink grant, the uplink grant indicating an uplink grant instance and an SRS configuration for the uplink grant instance; and select, by the UE, a logical channel of resources to use the uplink grant instance based in part on the SRS configuration set and the SRS configuration for the uplink grant instance.

[0012] In another aspect of the present invention, a wireless communication method includes: a network entity sending a logical channel prioritization (LCP) restriction configuration for a logical channel, the LCP restriction configuration indicating an SRS configuration set associated with the logical channel; the network entity determining data of the logical channel to be scheduled for a specific UE; the network entity sending an uplink grant, the uplink grant indicating an uplink grant instance for a specific user equipment and an SRS configuration of the SRS configuration set; and the network entity receiving a transmission corresponding to the uplink grant instance and including data of the logical channel.

[0013] In an additional aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes at least one processor, and a memory coupled to the processor. The processor is configured to: send a logical channel prioritization (LCP) restriction configuration for a logical channel by a network entity, the LCP restriction configuration indicating an SRS configuration set associated with the logical channel; determine data of a logical channel to be scheduled for a specific UE by the network entity; send an uplink grant by the network entity, the uplink grant indicating an uplink grant instance for a specific user equipment and an SRS configuration of the SRS configuration set; and receive a transmission of data corresponding to the uplink grant instance and including the logical channel by the network entity.

[0014] The foregoing fairly broadly summarizes the features and technical advantages of examples according to the present disclosure so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures to achieve the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein, their organization and methods of operation, together with the associated advantages, will be better understood from the following description. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] A further understanding of the features and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar components or features may have the same reference numerals. In addition, various components of the same type may be distinguished by following the reference numeral with a dash and a second reference numeral that distinguishes between similar components. If only the first reference numeral is used in the specification, the specification applies to any of the similar components having the same first reference numeral, without regard to the second reference numeral.

[0016] Figure 1 is a block diagram showing details of a wireless communication system.

[0017] Figure 2 is a block diagram showing a design of a base station and a UE configured according to one aspect of the present disclosure.

[0018] Figure 3 is a schematic diagram illustrating an example of a wireless communication system of a multiple transmission / reception point (TRP) scheme according to aspects of the present disclosure.

[0019] Figure 4 is a block diagram illustrating an example of a processing flow for supporting dynamic switching between different multi-TRP schemes according to aspects of the present disclosure.

[0020] Figure 5A-5D is a schematic diagram illustrating different multi-TRP schemes and corresponding PDCP PDU duplication for different multi-TRP schemes according to aspects of the present disclosure.

[0021] Fig. 6A and Figure 6B is a schematic diagram showing uplink and downlink diagrams of replication and LCP for a multi-TRP scheme according to aspects of the present disclosure.

[0022] Figure 7 is a block diagram illustrating an example of a wireless communication system that enables enhanced LCP mapping restrictions according to aspects of the present disclosure.

[0023] Figure 8A-8F Each of is a diagram showing an example of a downlink control message including fields thereof.

[0024] Fig. 9 is a block diagram illustrating example blocks executed by a UE configured according to one aspect of the present disclosure.

[0025] Fig.10 is a block diagram illustrating example blocks executed by a base station configured according to one aspect of the present disclosure.

[0026] Fig.11 is a block diagram conceptually illustrating a design of a UE according to some embodiments of the present disclosure.

[0027] Fig.12 is a block diagram conceptually illustrating a design of a base station configured in accordance with some embodiments of the present disclosure. DETAILED DESCRIPTION

[0028] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. Instead, the detailed description includes specific details in order to provide a thorough understanding of the subject matter of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every case, and in some cases, well-known structures and components are shown in block diagram form for clarity of presentation.

[0029] The detailed description is related to logical channel prioritization (LCP) enhancement. Typically, the UE uses LCP to select a logical channel for uplink data. When operating in some multiple transmit receive point (TRP) modes, the UE can send data to different TRPs with spatial diversity (e.g., different positions due to different antenna devices). The UE can send duplicate data to increase throughput and reliability, such as enabling operation in URLLC mode. Because the data is duplicated, the LCP mapping restrictions make it impossible to schedule and send copies / copies of data via the same carrier. To illustrate, in conventional operation, when the UE attempts to map duplicate data (e.g., two copies of the same data) to a separate logical channel via an uplink grant for subsequent scheduling, no mapping criteria are available to allow appropriate selection of logical channels for appropriate transmission. For example, the UE cannot send duplicate data via a logical channel because there may be no indication of a transmission parameter (e.g., different transmission parameters) so that two transmissions can be successfully sent to two different TRPs via the same carrier. Therefore, in this case, the UE uses different carriers to send duplicate data. For certain operating modes such as URLLC (e.g., eURLLC), such a process may not be able to achieve low latency requirements or constraints.

[0030] The described technology relates to improved methods, systems, devices and apparatuses that support enhanced logical channel prioritization mapping processes and restrictions, such as indications of logical channel prioritization (LCP) restrictions based on SRS / SRI (sounding reference signal (SRS) / SRS resource indicator (SRI)). This enhanced LCP mapping process can enable operation in multi-TRP mode and / or mapping of duplicate data for transmission via the same carrier. Therefore, such technology can increase reliability and reduce latency, and enable operation in URLLC mode.

[0031] The present disclosure generally relates to providing or participating in authorized shared access between two or more wireless communication systems (also referred to as wireless communication networks). In various embodiments, the techniques and apparatus may be used for wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth generation (5G) or new radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" may be used interchangeably.

[0032] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE802.20, flash-OFDM, etc. UTRA, E-UTRA, and Global System for Mobile Communications (GSM) are part of Universal Mobile Telecommunications System (UMTS). In particular, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These different radio technologies and standards are either well known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between a group of telecommunications associations whose purpose is to define globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project that aims to improve the mobile phone standards of Universal Mobile Telecommunications System (UMTS). 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution of wireless technologies from LTE, 4G, 5G, NR and beyond, which use a new and different set of radio access technologies or radio air interfaces to share access to the wireless spectrum between networks.

[0033] In particular, 5G networks consider different deployments, different spectrums, and different services and devices using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to (1) provide coverage for the massive Internet of Things (IoT) with ultra-high density (e.g., ~1M nodes / km2), ultra-low complexity (e.g., ~tens of bits / second), ultra-low energy (e.g., ~10+ years of battery life), and deep coverage capable of reaching challenging locations; (2) include mission-critical control with strong security to protect sensitive personal, financial, or confidential information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1 millisecond), and users with wide mobility range or lack of mobility range; and (3) have enhanced mobile broadband, including extremely high capacity (e.g., ~10Tbps / km2), extremely high data rates (e.g., rates of several Gbps, 100+Mbps user experience rates), and deep awareness with advanced discovery and optimization.

[0034] 5G NR can be implemented using an optimized OFDM-based waveform with scalable numerology and transmission time interval (TTI); with a common, flexible framework to efficiently multiplex services and features with dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and with advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding and decoding, and device-centric mobility. The scalability of the numerology in 5G NR, along with the expansion of subcarrier spacing, can efficiently solve the problem of operating different services on different spectrums and different deployments. For example, in various outdoor and macro coverage deployments less than 3GHz FDD / TDD implementations, the subcarrier spacing can occur at 15kHz, such as on bandwidths of 1MHz, 5MHz, 10MHz, 20MHz, etc. For various other outdoor and small cell coverage deployments with TDD greater than 3GHz, the subcarrier spacing can occur at 30kHz on 80 / 100MHz bandwidth. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing can occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting with a millimeter wave component using TDD at 28 GHz, subcarrier spacing can occur at 120 kHz over a 500 MHz bandwidth.

[0035] 5G NR's scalable parameter set provides scalable TTI for different latency and quality of service (QoS) requirements. For example, shorter TTI can be used for low latency and high reliability, while longer TTI can be used for higher spectral efficiency. Efficient multiplexing of long TTI and short TTI allows transmission to start on symbol boundaries. 5G NR also considers a self-contained integrated subframe design with uplink / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink / downlink, which can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current business needs.

[0036] Various other aspects and features of the present disclosure are further described below. It is obvious that the teachings of this article can be embodied in various forms, and any specific structure, function or both disclosed herein are only representative and not restrictive. Based on the teachings of this article, it should be understood by those of ordinary skill in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects proposed herein can be used to implement a device or practice method. In addition, other structures, functions or structures and functions other than one or more aspects proposed herein can be used to implement such a device or practice such a method. For example, a method can be implemented as a part of a system, device, device, and / or implemented as instructions stored on a computer-readable medium for execution on a processor or computer. In addition, an aspect may include at least one element of a claim.

[0037] Figure 1 1 is a block diagram illustrating a 5G network 100 including various base stations and UEs configured according to aspects of the present disclosure. The 5G network 100 includes multiple base stations 105 and other network entities. A base station may be a station that communicates with a UE and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each base station 105 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to this particular geographic coverage area of ​​a base station and / or a base station subsystem serving that coverage area, depending on the context in which the term is used.

[0038] A base station may provide communication coverage for a macro cell or a small cell (such as a pico cell or a femto cell), and / or other types of cells. A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs with a service subscription with a network provider. A small cell, such as a pico cell, may generally cover a relatively small geographic area and may allow unrestricted access to UEs with a service subscription with a network provider. A small cell, such as a femto cell, may also generally cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown, base station 105d and base station 105e are conventional macro base stations, while base stations 105a-105c are macro base stations capable of one of three-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 105a-105c take advantage of their higher-dimensional MIMO capabilities and utilize 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station that can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0039] The 5G network 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time.

[0040] UE 115 is scattered throughout the wireless network 100, and each UE can be fixed or mobile. UE can also be referred to as a terminal, a mobile station, a user unit, a station, etc. UE can be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc. In one aspect, the UE can be a device including a universal integrated circuit card (UICC). On the other hand, the UE can be a device that does not include a UICC. In some aspects, a UE that does not include a UICC can also be referred to as an Internet of Everything (IoE) or Internet of Things (IoT) device. UE 115a-115d is an example of a mobile smart phone type device that accesses the 5G network 100. UE can also be a machine specially configured for connecting communications (including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc.). UE 115e-115k is an example of various machines configured for accessing communications of the 5G network 100. The UE may be able to communicate with any type of base station, whether macro, small cell, or similar. Figure 1 In the present invention, lightning (e.g., communication link) indicates wireless transmission between the UE and a serving base station, which is a base station designated to serve the UE on a downlink and / or uplink, or desired transmission between base stations, and backhaul transmission between base stations.

[0041] In operation at the 5G network 100, base stations 105a-105c use 3D beamforming and coordinated spatial techniques (such as coordinated multipoint (CoMP) or multi-connectivity) to serve UE 115a and UE 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cell base station 105f. Macro base station 105d also transmits multicast services that are subscribed to and received by UE 115c and UE 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts (such as Amber alerts or gray alerts).

[0042] The 5G network 100 also supports mission-critical communications for mission-critical devices such as drone UE 115e with ultra-reliable and redundant links. The redundant communication links with UE 115e include from macro base stations 105d and 105e and small cell base stations 105f. Other machine-type devices such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device) can communicate directly with base stations such as small cell base stations 105f and macro base stations 105e through the 5G network 100, or communicate with another user device that relays its information to the network (such as UE 115f that communicates temperature measurement information to smart meter UE 115g, which is then reported to the network by UE 115g through small cell base station 105f) in a multi-hop configuration. The 5G network 100 may also provide additional network efficiencies through dynamic, low latency TDD / FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between UEs 115i-115k communicating with a macro base station 105e.

[0043] Figure 2 A block diagram of a design of a base station 105 and a UE 115 is shown, and the base station 105 and the UE 115 can be one of the base stations and one of the UEs in the figure. At the base station 105, a transmit processor 220 can receive data from a data source 212 and control information from a controller / processor 240. The control information can be used for PBCH, PCFICH, PHICH, PDCCH, EPDCCH, MPDCCH, etc. The data is maliciously used for PDSCH, etc. The transmit processor 220 can process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The transmit processor 220 can also generate reference symbols for PSS, SSS, and cell-specific reference signals, for example. The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols (if applicable), and can provide output symbol streams to modulators (MODs) 232a to 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a to 232t may be transmitted via antennas 234a to 234t, respectively.

[0044] At the UE 115, antennas 252a to 252r may receive downlink signals from the base station 105 and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 115 to a data sink 260, and provide decoded control information to a controller / processor 280.

[0045] On the uplink, at the UE 115, a transmit processor 264 may receive and process data from a data source 262 (e.g., for PUSCH), and control information from the controller / processor 280 (e.g., for PUCCH). The transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. The processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240.

[0046] The controllers / processors 240 and 280 may direct the operation at the base station 105 and the UE 115, respectively. The controller / processor 240 and / or other processors and modules at the base station 105 may perform or direct the execution of various processes for the techniques described herein. The controller / processor 280 and / or other processors and modules at the UE 115 may also perform or direct the execution of various processes for the techniques described herein. Fig. 9 and Fig.10 The functional blocks shown and / or other processes for the techniques described herein may be executed. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs to transmit data on the downlink and / or uplink.

[0047] Wireless communication systems operated by different network operating entities (e.g., network operators) may share spectrum. In some instances, a network operating entity may be configured to use the entire designated shared spectrum for at least one time period before another network operating entity uses the entire designated shared spectrum for a different time period. Therefore, in order to allow network operating entities to use the fully designated shared spectrum and to mitigate interfering communications between different network operating entities, certain resources (e.g., time) may be divided and allocated to different network operating entities for certain types of communications.

[0048] For example, a network operation entity may be allocated specific time resources reserved for dedicated communications by the network operation entity using the entire shared spectrum. Other time resources may also be allocated to a network operation entity where the entity is given priority over other network operation entities to communicate using the shared spectrum. The time resources prioritized for use by the network operation entity may be utilized on an opportunistic basis by other network operation entities if the prioritized network operation entity does not utilize those resources. Additional time resources may be allocated to any network operator for use on an opportunistic basis.

[0049] Arbitration of access to shared spectrum and time resources between different network operating entities may be centrally controlled by a separate entity, autonomously determined by a predefined arbitration scheme, or dynamically determined based on interactions between wireless nodes of the network operator.

[0050] In some cases, 5G network 100 (in Figure 1 The UE 115 and the base station 105 (in) can operate in a shared radio frequency spectrum band, which can include licensed or unlicensed (e.g., based on competition) spectrum. In the unlicensed frequency portion of the shared radio frequency spectrum band, the UE 115 or the base station 105 can traditionally perform a medium sensing process to compete for access to the spectrum. For example, the UE 115 or the base station 105 can perform a listen-before-talk (LBT) process such as a clear channel assessment (CCA) before communication to determine whether the shared channel is available. CCA may include an energy detection process to determine whether there are any other active transmissions. For example, the device may infer that a change in a received signal strength indicator (RSSI) of a power meter indicates that the channel is occupied. Specifically, a signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor limit may indicate another wireless transmitter. CCA may also include detection of a specific sequence indicating channel usage. For example, another device may send a specific preamble before sending a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel and / or acknowledgement / negative acknowledgement (ACK / NACK) feedback for its own transmitted packets as a conflicting proxy.

[0051] Generally speaking, four categories of LBT procedures have been proposed for sensing a shared channel for signals that may indicate that the channel is occupied. In the first category (CAT 1 LBT), no LBT or CCA is applied to detect occupancy of a shared channel. The second category (CAT 2 LBT), which may also be referred to as simplified LBT, single-shot LBT, or 25-μs LBT, provides that a node performs CCA to detect energy above a predetermined threshold or to detect a message or preamble occupying a shared channel. CAT 2 LBT performs CCA without using a random backoff operation, which results in its reduced length relative to the next category.

[0052] The third category (CAT 3LBT) performs CCA to detect energy or messages on a shared channel, but also uses random backoffs and fixed contention windows. Therefore, when a node initiates CAT 3LBT, it performs a first CCA to detect occupancy of the shared channel. If the shared channel is idle for the duration of the first CCA, the node can continue to transmit. However, if the first CCA detects a signal occupying the shared channel, the node selects a random backoff based on the fixed contention window size and performs an extended CCA. If the shared channel is detected to be idle during the extended CCA and the random number has been decremented to 0, the node can start transmitting on the shared channel. Otherwise, the node decrements the random number and performs another extended CCA. The node will continue to perform extended CCAs until the random number reaches 0. If the random number reaches 0 without any extended CCA detecting channel occupancy, the node can transmit on the shared channel. If at any extended CCA, the node detects channel occupancy, the node can reselect a new random backoff based on the fixed contention window size to start the countdown again.

[0053] The fourth category (CAT 4 LBT), also known as the full LBT process, performs CCA with energy or message detection using random backoff and variable contention window size. The sequence of CCA detection is similar to the process of CAT3 LBT, except that for the CAT 4 LBT process, the size of the contention window is variable.

[0054] Using a media sensing process to compete for access to an unlicensed shared spectrum may result in communication inefficiencies. This may be particularly evident when multiple network operating entities (e.g., network operators) attempt to access shared resources. In a 5G network 100, base stations 105 and UEs 115 may be operated by the same or different network operating entities. In some examples, individual base stations 105 or UEs 115 may be operated by more than one network operating entity. In other examples, each base station 105 and UE 115 may be operated by a single network operating entity. Requiring each base station 105 and UE 115 of different network operating entities to compete for shared resources may result in an increase in signaling overhead and communication latency.

[0055] Figure 3 An example of a wireless communication system 300 that supports dynamic switching between different multi-TRP schemes according to aspects of the present disclosure is shown. In some examples, the wireless communication system 300 can implement aspects of the wireless communication system 100. For example, the wireless communication system 300 can include multiple UEs 115 and base stations 105. The base stations 105 can communicate with the UEs 115 using TRPs 305. Each base station 105 can have one or more TRPs 305. For example, the base station 105-a can include TRP 305-a and TRP 305-b, and the base station 105-b can include TRP 305-c. UE 115-a may communicate with the network using a single TRP 305, using multiple TRPs 305 corresponding to a single base station 105 (e.g., TRP 305-a and TRP 305-b at base station 105-a), or using multiple TRPs 305 corresponding to multiple different base stations 105 (e.g., TRP 305-a at base station 105-a and TRP 305-c at base station 105-b, where base station 105-a and base station 105-b may be connected via a backhaul connection).

[0056] In a communication scheme including multiple TRPs 305, a single DCI message can configure the communication of multiple TRPs 305. In one example, a base station 105-a can use a first TRP 305-a and a second TRP 305-b for communication. The base station 105-a can use TRP 305-a to send DCI to UE 115-a on PDCCH 310-a. DCI may include communication configuration information for TCI states. The TCI state may determine whether the communication corresponds to a single TRP communication or to multiple TRP communications. The TCI state may also indicate the type of communication scheme configured for the communication (e.g., TDM, FDM, SDM, etc.). If the TCI configuration is a TCI state, the one TCI state may correspond to a single TRP communication. If the TCI configuration is a plurality of TCI states, the plurality of TCI states may correspond to communications with a plurality of TRPs. In some cases, the wireless communication system 300 may support up to M candidate TCI states for quasi-colocation (QCL) indication. Among these M candidates (e.g., 128 candidate TCI states), a subset of TCI states may be determined based on a medium access control (MAC) control element (CE). The MAC-CE may correspond to a specific number (e.g., 2 N , such as 8 TCI states). N One of the TCI states may be dynamically indicated in a message (eg, DCI) using N bits.

[0057] The DCI on PDCCH 310-a may schedule a PDSCH 315-a transmission from TRP 305-a for a single TRP communication configuration. Alternatively, the DCI on PDCCH 310-a may schedule multiple PDSCH 315 transmissions from multiple TRPs 305. For example, the DCI may schedule a PDSCH 315-a transmission from TRP 305-a and a PDSCH 315-b transmission from TRP 305-b, or a PDSCH 315-a transmission from TRP 305-a and a PDSCH 315-c transmission from TRP 305-c for multiple TRP communication configurations. UE 115 may be configured with a list of different candidate TCI states for the purpose of QCL indication. The QCL indication may also indicate the DMRS in the DCI corresponding to PDSCH 315. Each TCI code point in the DCI may correspond to one or more QCL relations (eg, to one or more reference signal (RS) sets), and accordingly to one or more TCI states.

[0058] In the case where the network utilizes TRP 305 to communicate with UE 115, whether in a single TRP configuration or in a multi-TRP configuration, multiple different schemes can be used to communicate with TRP 305. The TRP communication scheme can be determined by the TCI state. The TCI state used for communication on PDSCH 315 can be indicated by one or more bits in the DCI, wherein the one or more bits indicate a TCI code point. The TCI code point in the DCI can correspond to one or more TCI states (e.g., one or two TCI states). If the TCI code point in the DCI indicates a TCI state, UE 115 is configured for single TRP operation. If the TCI code point in the DCI indicates two TCI states (and correspondingly, indicates two QCL relationships), UE 115 is configured for multiple TRP operations. For example, if two TCI states are valid within the TCI code point, each TCI state can correspond to a code division multiple access (CDM) group.

[0059] In a first example multi-TRP scheme, TRP 305 can communicate by utilizing SDM. In this case, different spatial layers can be sent from different TRP 305 on the same RB and symbol. Each TCI state can also correspond to a different DMRS port group. The DMRS ports in a DMRS CDM port group can be QCL (quasi collocated). This allows UE 115 to estimate each channel separately. In SDM, each antenna port used on the downlink may belong to a different CDM group. Base station 105-a can indicate the antenna port group using the antenna port field in the DCI.

[0060] The SDM scheme may include different TCI states within a single time slot, where the TCI states overlap in time, frequency, or both. Different groups of spatial layers (which may correspond to different TCI states) may use the same modulation order. The use of the same modulation order by multiple groups may be signaled by a modulation and coding scheme (MCS). In some cases, the base station 105-a may indicate the MCS in the DCI. In the case where different groups of spatial layers use different modulation orders, each of the different modulation orders may be signaled to the UE 115-a. Different DMRS port groups may correspond to different TRPs, QCL relationships, TCI states, or a combination thereof.

[0061] In other examples of multi-TRP schemes, the TRP 305 may communicate with the UE 115-a by utilizing an FDM and / or TDM communication scheme. In the FDM scheme, a group of RBs or a group of PRGs may correspond to a first TRP 305-a and a first TCI state, and a second group of RBs or a second group of PRGs may correspond to a second TRP 305-b and a second TCI state. The RBs allocated to each TRP may be different from each other, so that each TRP communicates on a set of designated RBs that are different from another set of RBs (but may overlap in the same OFDM symbol). The frequency domain resource allocation field in the DCI may indicate both the first and second groups of RBs or PRGs. In some cases, the base station 105-a may use additional signaling in the DCI to indicate which RBs belong to the first group and which belong to the second group. In some cases, the system may support a limited number of possibilities for allocating frequency resources to different TRPs (e.g., to reduce overhead).

[0062] In a TDM scheme, a similar probability table can be used to signal resource allocations for different TRPs. In this case, each TRP is assigned to a different set of OFDM symbols rather than to a different set of RBs. Such a TDM scheme can support TDMized transmissions within a single time slot (e.g., a transmit time interval (TTI)). In some cases, a TDM scheme can implement time slot aggregation, where transmissions using different TCI states can be spread over different time slots (e.g., TTIs). In time slot aggregation, transmissions on different TRPs can use separate rate matching, but can have the same or different modulation orders.

[0063] The network may communicate with UE 115-a using multiple TRPs and any of the communication schemes described herein. In addition, some communication schemes may include a combination of TDM and FDM, or situations where TDM may or may not be in a time slot aggregation configuration. The schemes may also include some situations where rate matching is joint and some situations where rate matching is separate for different TRPs, and the schemes may also include situations where different TRPs have the same or different modulation orders. Each scheme may also utilize different parameters included in the signaling, such as which DMRS ports to use (e.g., for an SDM scheme) or how to split the RBs (e.g., for an FDM scheme).

[0064] In order to efficiently configure UE 115-a with TCI state information and a corresponding TRP scheme, base station 105-a may generate bits for a DCI message and may send the DCI on PDCCH 310-a. The DCI message may be sent to UE 115-a using TRP 305-a. UE 115-a may determine which scheme is configured for communication with TRP 305 based on one or more fields of the received DCI. The DCI may have the same size in all communication schemes, and the format (e.g., number of bits) of the DCI field may remain the same across communication schemes.

[0065] In a first implementation, UE 115-a may detect a communication scheme based on the antenna port field and the TCI field of a received DCI message. The TCI field of the DCI may indicate whether communication with one TRP using one TCI state (e.g., TRP 305-a) is configured or communication with multiple TRPs using multiple TCI states (e.g., TRP 305-a and TRP 305-b) is configured. For example, a value in the TCI field (e.g., tci-PresentInDCI) may not be configured for a CORESET that schedules a PDSCH, or the value may correspond to one TCI state. The MAC-CE may configure the TCI state possibility, and the TCI state field of the DCI may indicate the possibility based on the configuration of the MAC-CE. Different values ​​in the TCI status field can correspond to single TRP communication (e.g., communication with TRP 305-a if a single TCI state is indicated) or multi-TRP communication (e.g., communication with TRP 305-a and 305-b, 305-a and 305-c, etc. if two TCI states are indicated).

[0066] UE 115-a can determine whether the DCI indicates a single TRP communication scheme or a multi-TRP communication scheme based on the value in the TCI field, and can interpret the value in the antenna port field of the DCI based on the TCI field value. In the case where the TCI field corresponds to a communication scheme with a single TRP 305 (such as TRP 305-a), UE 115-a can identify the value of the antenna port field for a single TCI state. Based on the table in the memory, UE 115-a can determine one or more antenna ports for scheduled PDSCH 315-a transmission based on the antenna port field value. In the case where the TCI field corresponds to a communication scheme with multiple TRPs 305 (such as TRP 305-a and TRP 305-b), UE 115-a can identify the value of the antenna port field and determine the multi-TRP scheme based on the value. In one example, the antenna port field value can correspond to one or more DMRS ports, communication schemes, rate matching configurations, scheme-specific parameters, or some combination of these.

[0067] In a second implementation, UE 115-a may determine the communication scheme based on a field in the DCI message that explicitly indicates the scheme (e.g., a multi-TCI scheme field). The value in the multi-TCI scheme field may correspond to a specific multi-TCI scheme (e.g., SDM, FDM, or TDM). If the value in the multi-TCI scheme field corresponds to a TDM scheme, the value may additionally indicate whether the TDM scheme is configured for one time slot or for multiple time slots based on a time slot aggregation process.

[0068] In one example, UE 115-a may identify a value of a TCI field in a DCI message and may determine whether a communication scheme includes multiple TCI states based on the TCI field value. If the value does not correspond to multiple TCI states, UE 115-a may ignore (e.g., not process) the Multiple TCI States field. In some cases, the value of the Multiple TCI Scheme field may only be relevant if the TCI field in the DCI corresponds to more than one TCI state.

[0069] In a second example, UE 115-a may determine whether a communication scheme includes multiple TCI states based on the multi-TCI state field. For example, a specific value of the multi-TCI state field may correspond to a single TCI state, while other values ​​may correspond to different multi-TCI scheme possibilities. In this example, UE 115-a may interpret the TCI field based on whether the multi-TCI state field indicates a single TRP operation or a multi-TRP operation. For example, based on whether the multi-TCI state field indicates a single TRP operation or a multi-TRP operation, the same TCI code point in the TCI field may correspond to one TCI state or a pair of TCI states. In this way, a three-bit TCI field may support eight different single TCI state options and eight different pairs of multi-TCI state options.

[0070] UE 115-a can interpret the value received in the multi-TCI status field based on the table. For example, the value can indicate a TRP communication scheme, a rate matching configuration, one or more scheme-specific parameters, a modulation order, or any combination of these.

[0071] In some cases, different modulation orders are used in different TCI states. The table referenced above may include an additional column or an alternative column indicating the modulation order of the second TCI state in the multi-TCI scheme. The modulation order value may be an absolute modulation order, or may be a relative modulation order with respect to the modulation order of the first TCI state in the multi-TCI scheme.

[0072] In some cases, UE 115-a may interpret the antenna port field in the DCI message based on the multiple TCI scheme field. In some examples, UE 115-a may determine whether to use a single TRP configuration or a multiple TRP configuration with TDM or FDM based on these two fields. In these examples, UE 115-a may determine the antenna port scheme based on a table that supports a single TCI state (or based on no SDM). In other examples, UE 115-a may determine that multiple TRP configurations with SDM are used. In these other examples, UE 115-a may determine the antenna port scheme based on a table that supports multiple antenna ports for multiple TCI states.

[0073] In other cases, UE 115-a may use both the antenna port field and the multi-TCI scheme field to determine the communication scheme. For example, UE 115-a may determine whether the multi-TCI scheme is an SDM scheme based on the antenna port field. If not, UE 115-a may determine whether the multi-TCI scheme is an FDM scheme or a TDM scheme based on the multi-TCI scheme field.

[0074] In a third implementation, UE 115-a may determine the RV sent by PDSCH 315 based on the DCI. For example, base station 105-a may identify a transport block for transmission to UE 115-a. Base station 105-a may use TRP 305-a and TRP 305-b to encode the transport block and send the coded bits. If base station 105-a performs joint rate matching, the coded bits of the two TCI states may be the same, corresponding to one RV. If base station 105-a performs separate rate matching, the coded bits of each TCI state may be different, corresponding to two different RVs. Base station 105-a may indicate the one or more RVs in a single DCI message on PDCCH 310-a. If one RV is indicated (e.g., for a single TCI operation or when performing joint rate matching), base station 105-a may indicate the one RV in the RV field in the DCI. If multiple (e.g., two) RVs are indicated, base station 105-a may indicate a pair of RVs in one or more DCI fields.

[0075] In a first example, the first RV may be indicated in the RV field of the DCI, and the second RV may be indicated in another field of the DCI. For example, the second RV may be indicated in the antenna port field of the DCI, the multi-TCI scheme field of the DCI, or some combination of these fields.

[0076] In a second example, the antenna port field or the multi-TCI scheme field of the DCI as described herein may indicate a rate matching configuration. If the UE 115-a determines that the base station 105-a performs separate rate matching, the UE 115-a may interpret the value in the RV field to indicate separate RV values ​​for different TCI states. For example, the value of the RV field may correspond to an RV pair, wherein the first RV value in the RV pair may correspond to a first TCI state, and the second RV value in the RV pair may correspond to a second TCI state. The correspondence of values ​​to RV pairs may be specified in a table (e.g., a lookup table). The table may be pre-configured in a memory at the UE 115-a and the base station 105-a, or the network may configure the UE 115-a with the table.

[0077] In a third example, the rate matching configuration may also be indicated in the RV field. For example, the value of the RV field may correspond to a single RV or multiple RVs, as shown in the example RV table below. In some cases, when it is determined that a multi-TRP scheme is configured, UE115-a may use the table to interpret the RV field. The table may be specified as a lookup table and may be pre-configured or dynamically configured by the network. If the value of the RV field corresponds to a single RV value for multi-TRP operation, UE 115-a may determine that base station 105-a is performing joint rate matching. If the value of the RV field corresponds to a pair of RV values ​​for multi-TRP operation, UE115-a may determine that base station 105-a is performing separate rate matching.

[0078] In a fourth implementation, UE 115-a may determine how to interpret the indication of the PRG size in the DCI based on the configured multi-TCI scheme. If UE 115-a determines that the multi-TCI scheme is an FDM scheme (e.g., based on the antenna port field or the multi-TCI field), UE 115-a may interpret the PRB bundling size indicator field in the DCI per TCI state, rather than per bandwidth portion. For example, if the PRB bundling size indicator field indicates wideband precoding, the wideband precoding configuration may include only wideband communications within RBs associated with the same TCI state.

[0079] It should be understood that the wireless communication system 300 may implement any combination of the implementations described herein to dynamically signal the TCI status of a selected multi-TRP scheme in a single DCI message.

[0080] Figure 4 An example of a process flow 400 that supports dynamic switching between different multi-TRP schemes according to aspects of the present disclosure is shown. In some examples, the process flow 400 can implement aspects of the wireless communication system 100 or 300. For example, a base station 105 and a UE 115 (such as a base station 105-c and a UE 115-b) can perform one or more processes described with reference to the process flow 400. The base station 105-c can communicate with the UE 115-b by sending and receiving signals through TRP 405-a and TRP 405-b. In other cases, TRP 405-a and TRP 405-b can correspond to different base stations 105. The following alternative examples can be implemented, in which some of the steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or further steps may be added.

[0081] At 410, the base station 105-c may generate a DCI. The generating may include generating a first bit set (e.g., a TCI field) that may indicate a set of TCI states for communicating with the UE 115-b. The generating may also include generating a second bit set (e.g., an antenna port field) that may indicate an antenna port set and, in some cases, may indicate a multi-TRP communication scheme for multiple TRP communication operations. In some cases, the second bit set may additionally indicate a modulation order of at least one TCI state (e.g., a second TCI state of TRP 405-b), an RV of a TB of at least one TCI state (e.g., a second TCI state of TRP405-b), or a combination thereof.

[0082] At 415, base station 105-c may send the generated DCI to UE 115-b. UE 115-b may receive the DCI from base station 105-c. The DCI may be sent from TRP 405-a on the PDCCH. The DCI may schedule an upcoming PDSCH transmission and may include other control information. The DCI may include an indication of the first bit set and the second bit set. For example, the DCI may include coded bits based on the first bit set and the second bit set.

[0083] At 420, the UE 115-b may read the TCI field (e.g., a first set of bits) received in the DCI message. The UE 115-b may use the first set of bits to identify one or more TCI states for communicating with the base station 105-c using one or more TRPs 405.

[0084] At 425, UE 115-b may determine the TCI state configuration based on reading the TCI field of the DCI. For example, the value in the TCI field (e.g., tci-PresentInDCI) may not be configured for the CORESET that schedules the PDSCH, or the value may correspond to one TCI state. In these cases, the communication scheme may be configured for one TRP. In other cases, the TCI field value may correspond to more than one TCI state. In these other cases, the communication may be configured to communicate with multiple TRPs.

[0085] UE 115-b may read the antenna port field of the DCI and may interpret the value of the field based on the determined TCI state configuration. For example, if UE 115-b determines that the TCI field indicates a single TCI state, UE 115-b may use the second bit set to identify the set of antenna ports used for PDSCH transmission. At 430, UE 115-b may access a table (e.g., pre-configured in memory or configured by the network) to determine one or more antenna ports corresponding to the antenna port field value.

[0086] Alternatively, if UE 115-b determines that the TCI field indicates multiple TCI states, UE 115-b may use a second bit set to identify the TCI state set to identify the antenna port set and the multi-TRP communication scheme. The second bit set may include the same number of bits whether the field indicates only the antenna port and for single TRP operation or the antenna port set and the multi-TRP scheme for multi-TRP operation. At 430, UE 115-b may access a lookup table to determine the antenna port set and the multi-TRP scheme based on the antenna port field value. In some cases, UE 115-b may select a lookup table from a set of lookup tables, wherein the set of lookup tables may include one lookup table for single TRP operation and one lookup table for multi-TRP operation.

[0087] The lookup table may include information that maps both the antenna port set and the multi-TRP scheme to a second bit set. In some cases, the lookup table that maps both the antenna port set and the multi-TRP communication scheme to the second bit set may be pre-configured in a memory, and in some cases, it may be dynamically configured by the base station 105-c. The UE 115-b may identify the second set of antenna ports and the multi-TRP scheme based on the selected lookup table. In the lookup table for multi-TRP operation, together with an indication of a DMRS port, the table may include an indication of a multi-TRP scheme (e.g., SDM, FDM, TDM, or some combination thereof). The antenna port field lookup table may indicate that the value in the antenna port field of the DCI corresponds to a DMRS port set, wherein the DMRS port set further corresponds to a communication scheme such as SDM or FDM. The antenna port field value may also indicate whether the rate matching is joint or separate. If the antenna port field value indicates the use of the FDM communication scheme, the lookup table may additionally indicate the RB configuration of the TCI state of the FDM, as shown in the "Possibility" column of the following table. If the lookup table is configurable by the network, the network can define the possible DMRS port sets and the type of scheme using Radio Resource Control (RRC) signaling.

[0088] In some cases, UE 115-b may use a second bit set to identify the modulation order of at least one TCI state in the set of possible TCI states. Different modulation orders may also be used across different TCI states. A first modulation order may be indicated in the modulation order field. The first modulation order may correspond to a first TCI state in a multi-TRP operation. A second modulation order may be indicated in one of the above tables based on the value of the received antenna port field. For example, a column in the antenna port field lookup table may indicate whether the modulation order corresponding to the second TCI state is the same as the modulation order indicated in the MCS (i.e., the modulation order of the first TCI state). If the modulation order is not the same as the modulation order indicated in the MCS, the value of the modulation order of the second TCI state may be indicated in the antenna port field. The value of the modulation order may be an absolute value, or may be a relative value relative to the first modulation order.

[0089] If it is determined that the TCI state configuration indicates communication with a single TRP, the UE 115-b may transmit or receive transmissions from one TRP 405-a at 435. The UE 115-b may communicate with the single TRP 405-a based on the determined communication scheme. In some aspects, transmitting to the TRP may involve using transmit configuration parameters (e.g., beam, spatial filter configuration) suitable for receiving using the TRP.

[0090] If it is determined that the TCI state configuration indicates communication with multiple TRPs 405, the UE 115-b may send or receive transmissions from one TRP 405-a at 435, and may also send or receive transmissions from another TRP 405-b at 440 (where, in some cases, 435 and 440 may correspond to the same time or OFDM symbol). The UE 115-b may communicate with the network via the multiple configured TRPs 405 based on the determined communication scheme. In some aspects, transmitting to a set of TRPs may involve using transmit configuration parameters (e.g., beams, spatial filter configurations) suitable for receiving using the set of TRPs.

[0091] The system and method described herein are directed to enhanced LCP mapping restrictions so that UE has enhanced functionality. The enhanced functionality can allow duplication of operations and / or data (e.g., PDCP PDU) in multiple TRP modes. In a specific implementation, the system and method described herein enable the use of the same carrier to send PDCP PDU duplication to different TRPs. Therefore, such a system and method can be used for URLLC and / or multiple TRP modes.

[0092] refer to Figures 5A-5D , showing examples of replication of different multi-TRP patterns. Figure 5Aand Figure 5C corresponds to a schematic diagram of a carrier aggregation multi-TRP mode, and Figure 5B and 5D Schematic diagram corresponding to dual connection multi-TRP mode. Figure 5A , a schematic diagram illustrating carrier aggregation is shown. Figure 5A One base station 105a is depicted in communication with a UE 115a. The base station 105a may send data and control information; the base station 105 may use different equipment and / or settings (e.g., different frequencies) to send (and receive) information. Figure 5B , a schematic diagram illustrating dual connectivity is shown. Figure 5B Two base stations 105a and 105b are depicted in communication with a UE 115a. The UE 115a communicates data with both base stations and control information with one base station (primary base station 105a).

[0093] Figure 5C and Figure 5D A block diagram of a UE stack is depicted. The UE stack (e.g., a user plane protocol stack) includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical (PHY) layer. The SDAP layer is configured to provide mapping between QoS flows and data radio bearers, marking QoS flow IDs (QFIs) in uplinks and downlinks. In some scenarios, a single SDAP (e.g., a single SDAP entity) can be configured for each protocol data unit (PDU) session. In dual connectivity (DC), two SDAP entities, such as two stacks, can be configured.

[0094] The PDCP layer is configured to perform services and functions including sequence numbering, delivery, reordering and duplication detection of user data, PDCP PDU routing (e.g., for split bearers), retransmission of PDCP SDUs, and duplication of PDCP PDUs. The RLC layer is configured to perform services and functions including delivery, sequence numbering, segmentation, and resegmentation of upper layer PDUs.

[0095] The MAC layer is configured to perform services and functions including mapping between logical channels (LCH) and transport channels, multiplexing and demultiplexing of MAC SDUs, and logical channel prioritization. A single logical channel can be mapped to one or more parameter sets and / or TTI durations. For example, in LCP, the MAC layer (e.g., a MAC entity of the layer) determines the TTI duration or parameter set from the physical layer.

[0096] The MAC layer provides services to the RLC layer in the form of logical channels. Logical channels are defined by the type of data / information they carry and are generally referred to as control channels and are used for transmission of control and / or configuration, or as traffic channels for user data. The PHY layer is configured to perform services and functions including mapping between transport channels and physical channels.

[0097] refer to Figure 5C and Figure 5D , two example user plane stacks are shown. Figure 5C depicts a user plane stack for a UE 115 operating in a multi-TRP carrier aggregation mode, and Figure 5D Depicted is a user plane stack for a UE 115 operating in multi-TRP carrier dual connectivity mode.

[0098] refer to Figure 5C , the user plane stack includes an SDAP entity 512, a PDCP entity 522, a first RLC entity 532, a second RLC entity 534, and a MAC entity 542. The MAC entity includes a scheduler 552 and two HARQ entities 562, 564.

[0099] During operation, the SDAP entity 512 generates a PDCP SDU 580 and sends the PDCP SDU 580 to the PDCP entity 522. The PDCP entity 522 generates a PDCP header 590 and combines the PDCP header 590 and the PDCP SDU 580 to generate a first PDCP PDU 592. The PDCP entity 522 copies the first PDCP PDU 592 to generate a second PDCP PDU 594. The PDCP entity 522 sends the two PDCP PDUs 592, 594 to the corresponding RLC entities 532, 534. The RLC entities 532, 534 may perform RLC operations on the PDCP PDUs 592, 594, such as adding corresponding RLC headers. The RLC 532, 534 entities transmit the PDCP PDUs 592, 594 (e.g., RLC modified PDCP PDUs) to the MAC entity 542.

[0100] The scheduler 552 determines in which uplink each PDCP PDU 592, 594 is allowed to be transmitted. For example, the scheduler 552 receives two uplink grants and determines to transmit a first PDCP PDU 592 in a first uplink grant and to transmit a second PDCP PDU 594 in a second uplink grant. The scheduler 552 may use LCP mapping restrictions to perform the LCP mapping process. In some such implementations, the scheduler 552 may perform enhanced LCP mapping or use "enhanced" LCP mapping restrictions, e.g., additional and / or alternative LCP mapping restrictions compared to the LCP mapping restrictions of sections 38.321 and / or 38.331 of Release 15. As shown in FIG. Figure 5C As shown, a first PDCP PDU 592 is sent to the first HARQ entity 562 for a first component carrier (CC1), and a second PDCP PDU 594 is sent to the second HARQ entity 564 for a second component carrier (CC2).

[0101] refer to Figure 5D , the user plane stack includes a main stack 502 and a secondary stack 504. The main stack 502 corresponds to a first network entity, such as a primary base station (such as 105a), and the secondary stack 504 corresponds to a secondary base station (such as 105b). The main stack 502 includes an SDAP entity 512, a PDCP entity 522, a first RLC entity 532, and a first MAC entity 542. The secondary stack includes a second RLC entity 534 and a second MAC entity 544. The MAC entities 542, 544 may include a scheduler and / or a HARQ entity, similar to Figure 5C MAC entity 542 (such as 552 and / or 562).

[0102] During operation, the SDAP entity 512 of the primary stack 502 generates a PDCP SDU 580 and sends the PDCP SDU 580 to the PDCP entity 522 of the primary stack 502. The PDCP entity 522 generates a PDCP header 590 and combines the PDCP header 590 and the PDCP SDU 580 to generate a first PDCP PDU 592. The PDCP entity 522 copies the first PDCP PDU 592 to generate a second PDCP PDU 594. The PDCP entity 522 sends the two PDCP PDUs 592, 594 to the corresponding RLC entities 532, 534 of the primary stack 502 and the secondary stack 504, respectively. The RLC entities 532, 534 may perform RLC operations on the PDCP PDUs 592, 594, such as adding corresponding RLC headers. The RLC 532, 534 entities transmit the PDCP PDUs 592, 594 (e.g., RLC modified PDCP PDUs) to the corresponding MAC entities 542, 544 of the main stack 502 and the secondary stack 504, respectively. Each of the MAC entities 542 and 544 (e.g., their corresponding schedulers 552) may perform MAC layer functions such as the LCP operations and LCP mapping described with reference to FIG. Fig. 6A and Figure 6B An illustration of receiving an uplink grant and sending data such as PDCP PDU copy data is shown in FIG.

[0103] refer to Fig. 6A and Figure 6B , showing an example of PDCP PDU duplication. Fig. 6A An example downlink operation is shown, while Figure 6B An example uplink operation is shown. Fig. 6A , the system 600 includes a first transmit receive point (TRP) 605a and a second TRP 605b. As described above, the first TRP 605a and the second TRP 605b have spatial diversity (i.e., do not correspond to the same antenna device) and can be combined in the same base station (the same or different planes thereof) or in different base stations. In other words, the UE 115a can operate in a carrier aggregation multi-TRP mode or a dual connectivity multi-TRP mode.

[0104] exist Fig. 6A In the embodiment of the present invention, UE 115a receives a downlink message or a message indicating an uplink grant (e.g., one or more DCIs, RRCs, MAC CEs, etc.). The one or more uplink grants may include or correspond to a dynamic grant, a configured grant, or multiple configured grants. When multiple downlink messages are used, the message may be sent by the first TRP 605a, the second TRP 605b, or both the TRP 605a and the TRP 605b.

[0105] UE 115a may perform the steps of FIG. 5 and Figure 5D The PDCP PDU described above is replicated to generate first and second copies 692, 694. Additionally, the UE 115a performs the reference Figure 5C and Figure 5D The enhanced LCP mapping described above allocates or maps the first copy 692 to the first logical channel 615a and allocates or maps the second copy 694 to the second logical channel 615b. Fig. 6A , UE 115a can determine that the first logical channel 615a is restricted to sending data to the first TRP 605a (e.g., the first TRP605a uplink grant), and the second logical channel 615b is restricted to sending data to the second TRP 605b (e.g., TRP605b uplink grant).

[0106] refer to Figure 6B , describes the uplink transmission of the first copy 692 and the second copy 694. Figure 6B , UE 115a sends a first copy 692 to a first TRP 605a using an uplink grant for the first TRP 605a, and sends a second copy 694 to a second TRP 605b using an uplink grant for the second TRP 605b. UE 115a may send each copy 692, 694 with different transmission parameters, and the transmission parameters may be suitable for reception by each corresponding TRP. For illustration, a transmission parameter (e.g., corresponding to a transmission parameter received by a TRP) may allow reception or enhanced reception by the corresponding TRP. Such transmission parameters include beam parameters, spatial filtering parameters, etc., or a combination thereof. Thus, UE 115a may send data (e.g., replicated data) to two TRPs using the same carrier (e.g., physical medium).

[0107] Figure 7 An example of a wireless communication system 700 supporting enhanced LCP mapping restrictions according to aspects of the present disclosure is shown. In some examples, the wireless communication system 700 can implement aspects of the wireless communication system 100. For example, the wireless communication system 700 may include a network entity 705 (e.g., a base station 105), a UE 115, and an optional second network entity 706 (e.g., a second base station 105). The enhanced LCP mapping restrictions may be able to reduce overhead and latency when processing repetitions, and thus may increase throughput and reduce latency. This increased throughput and reduced latency may enable URLLC to take effect, and may be used to increase reliability, as well as potentially increase throughput when there is interference or blocking between the UE and a particular TRP.

[0108] The network entity 705 and the UE 115 may be configured to communicate via a frequency band, such as FR1 with a frequency of 450 MHz to 6000 MHz for sub-6 GHz or FR2 with a frequency of 24250 MHz to 26000 MHz for millimeter wave (mm-Wave). It should be noted that for some data channels, the subcarrier spacing (SCS) may be equal to 15 kHz, 30 kHz, 60 kHz, or 120 kHz. The network entity 705 and the UE 115 may be configured to communicate via one or more component carriers (CCs), such as a representative first CC 781, a second CC 782, a third CC 783, and a fourth CC 784. Although four CCs are shown, this is for illustration only, and more or less than four CCs may be used. One or more CCs may be used to communicate a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), a physical uplink control channel (PUCCH), or a physical uplink shared channel (PUSCH). In some implementations, such transmissions may be scheduled by one or more periodic grants and may correspond to configuration grants of the one or more periodic grants.

[0109] Each periodic grant may have a corresponding configuration, such as configuration parameters / settings. The periodic grant configuration may include configuration grant (CG) configuration and settings. Additionally or alternatively, one or more periodic grants (e.g., their CGs) may have a CC ID, or be assigned to a CC ID (such as an expected CC ID).

[0110] Each CC may have a corresponding configuration, such as a configuration parameter / setting. The configuration may include bandwidth, bandwidth portion, HARQ process, TCI state, RS, control channel resources, data channel resources, or a combination thereof. Additionally or alternatively, one or more CCs may have or be assigned to a cell ID, a bandwidth portion (BWP) ID, or both. The cell ID may include a unique cell ID of the CC, a virtual cell ID, or a specific cell ID of a specific CC in multiple CCs. Additionally or alternatively, one or more CCs may have or be assigned to a HARQ ID. Each CC may also have corresponding management functions, such as beam management, BWP switching functions, or both.

[0111] In some implementations, two or more CCs are quasi-collocated such that the CCs have the same beam and / or the same symbol. Additionally or alternatively, CCs may be grouped into a set of one or more CCs, such as a cross-carrier CORESET. Each CC in a CORESET may have the same cell ID, the same HARQ ID, or both.

[0112] In some implementations, the control information may be communicated via the network entity 705 and the UE 115. For example, the control information may be communicated using a MAC-CE transmission, an RRC transmission, a DCI transmission, another transmission, or a combination thereof.

[0113] The UE 115 includes a processor 702, a memory 704, a transmitter 710, a receiver 712, an encoder 713, a decoder 714, a combiner 715, and antennas 252a-r. The processor 702 may be configured to execute instructions stored at the memory 704 to perform the operations described herein. In some implementations, the processor 702 includes or corresponds to the controller / processor 280, and the memory 704 includes or corresponds to the memory 282. As further described herein, the memory 704 may also be configured to store LCP restriction data 706, SRS configuration 708, a first transmit configuration 742, a second transmit configuration 744, or a combination thereof.

[0114] The LCP restriction data 706 may include or correspond to one or more LCP restrictions, such as LCP restrictions for multi-TRP mode. In a specific implementation, the LCP restriction data 706 includes an SRS configuration 708. The LCP restriction data 706 may be sent via a MAC-CE, a DCI, or an RRC message. The SRS configuration may include a set of all enabled or allowed SRS configurations for a specific logical channel, for multiple logical channels, or for all logical channels. In a specific implementation, the SRS configuration includes a set of enabled or allowed SRS configurations for one or more logical channels. The SRS configuration for a specific transmission or multiple transmissions may be indicated in an uplink grant.

[0115] Each uplink grant configuration may have a corresponding transmission configuration and / or transmission parameters. Figure 7 As shown, UE115 stores a first transmit configuration 742 and a second transmit configuration 744. The first transmit configuration 742 may include or correspond to a first transmit parameter for a first TRP (e.g., suitable for reception by the first TRP), and the second transmit configuration 744 may include or correspond to a second transmit parameter for the first TRP (e.g., suitable for reception by the first TRP). For illustration, the transmit parameters may include scheduling information such as when and where to transmit. As another illustration, the transmit parameters may include transmit and / or receive characteristics for transmission / reception, such as BWP ID, beam scanning effectiveness, beam scanning mode, etc., i.e., how to transmit.

[0116] The transmitter 710 is configured to send data to one or more other devices, and the receiver 712 is configured to receive data from one or more other devices. For example, the transmitter 710 can send data via a network such as a wired network, a wireless network, or a combination thereof, and the receiver 712 can receive data. For example, the UE 115 can be configured to send and / or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other now known or later developed communication network that allows two or more electronic devices to communicate therein. In some implementations, the transmitter 710 and the receiver 712 can be replaced with a transceiver. Additionally or alternatively, the transmitter 710, the receiver 712, or both may include or correspond to reference Figure 2 One or more components of UE 115 are described.

[0117] The encoder 713 and the decoder 714 may be configured to perform encoding and decoding, such as joint encoding and joint decoding, respectively. The duplicator 715 may be configured to duplicate data (such as PDCP PDU) for encoding by the encoder 713. The LCH prioritizer 716 may be configured to select a logical channel based on LCP mapping restrictions and / or rules (e.g., LCP logic).

[0118] The network entity 705 includes a processor 730, a memory 732, a transmitter 734, a receiver 736, an encoder 737, a decoder 738, a combiner 739, and antennas 234a-t. The processor 730 may be configured to execute instructions stored at the memory 732 to perform the operations described herein. In some implementations, the processor 730 includes or corresponds to the controller / processor 240, and the memory 732 includes or corresponds to the memory 242. Similar to the UE 115 and as further described herein, the memory 732 may be configured to store the LCP restriction data 706, the SRS configuration 708, the first transmit configuration 742, the second transmit configuration 744, or a combination thereof.

[0119] The transmitter 734 is configured to send data to one or more other devices, and the receiver 736 is configured to receive data from one or more other devices. For example, the transmitter 734 can send data via a network such as a wired network, a wireless network, or a combination thereof, and the receiver 736 can receive data. For example, the network entity 705 can be configured to send and / or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other now known or later developed communication network that allows two or more electronic devices to communicate therein. In some implementations, the transmitter 734 and the receiver 736 can be replaced with a transceiver. Additionally or alternatively, the transmitter 734, the receiver 736, or both may include or correspond to reference Figure 2 One or more components of the depicted network entity 705. The encoder 737, decoder 738 and combiner 739 may include the same functionality as described with reference to the encoder 713 and decoder 714, respectively.

[0120] During operation of the wireless communication system 700, the network entity 705 may determine that the UE 115 has enhanced LCP mapping restriction capabilities, such as SRS-based LCP mapping. For example, the UE 115 may send a message 748 including an enhanced LCP mapping restriction capability indicator 792. The indicator 792 may indicate an enhanced LCP mapping capability or a specific type of enhanced LCP mapping capability, such as an enhanced LCP mapping for replication, an enhanced LCP mapping for a multi-TRP mode, or an enhanced LCP mapping with a specific type of LCP restriction (e.g., SRS). In some implementations, the network entity 705 sends control information to indicate to the UE 115 that the enhanced LCP mapping restriction will be used. For example, in some implementations, the message 748 (or another message, such as a response or trigger message) is sent by the network entity 705.

[0121] The network entity 705 sends an LCP configuration transmission 750 (e.g., an RRC or MAC CE) to the UE 115. The LCP configuration transmission 750 includes LCP restriction data 706, such as enhanced LCP mapping restrictions. In a specific implementation, the LCP restriction data includes or corresponds to a set of enabled or allowed SRS configurations for a logical channel or channels. The UE 115 receives the LCP configuration transmission 750 and updates its stored LCP restriction data 706 based on the LCP restriction data 706 of the LCP configuration transmission 750.

[0122] After the transmission of the message 748 (e.g., a configuration message, such as an RRC message or a MAC CE) and / or the LCP configuration transmission 750, the transmission may be scheduled by the network entity 705, the UE 115, or both. Such scheduled transmissions may include shared channel transmissions (such as PUSCH transmissions). These scheduled transmissions may include or correspond to dynamically or periodically scheduled uplink transmissions. A dynamic grant may schedule a single uplink grant or an uplink grant instance, while a periodic grant may schedule a single configuration grant and multiple uplink grant instances. An uplink grant may include or correspond to a DCI, an RRC, or a MAC CE.

[0123] exist Figure 7 In the example of , the network entity 705 sends a first downlink transmission 752 to the UE 115. The first downlink transmission 752 includes a logical channel indicator and / or a transmission indicator, such as a first specific SRS configuration 708a for a corresponding uplink grant or an uplink grant instance. The uplink grant may include or correspond to a specific TRP. The UE 115 determines a logical channel based on at least the first specific SRS configuration 708a and the updated LCP restriction data 706. For example, the LCP prioritizer 716 performs an LCP mapping operation and determines a logical channel for the first uplink transmission 754 based on at least the first specific SRS configuration 708a and the updated LCP restriction data 706. In some implementations, the UE 115 determines a second logical channel based on at least a second specific SRS configuration 708b (included in 752) and the updated LCP restriction data 706. For example, in such an implementation, the first downlink transmission 752 includes two uplink grants, and the LCP prioritizer 716 performs an LCP mapping operation and determines a second logical channel for a second uplink transmission 764 corresponding to a second TRP based at least on the second specific SRS configuration 708b and the updated LCP restriction data 706.

[0124] In other implementations, the network entity 705 may send a second downlink transmission 762 to the UE 115; the second downlink transmission 762 includes a second specific SRS configuration 708b for a second uplink grant associated with a second TRP. In such implementations, the UE 115 determines a second logical channel based at least on the second specific SRS configuration 708b (included in 762) and the updated LCP restriction data 706. For example, the LCP prioritizer 716 performs an LCP mapping operation and determines a logical channel for the second uplink transmission 764 based at least on the second specific SRS configuration 708b and the updated LCP restriction data 706.

[0125] After the UE 115 performs a logical channel prioritization operation to determine the logical channel for the uplink grant, the UE 115 schedules the transmission. Figure 7 In the example of , UE 115 schedules a first uplink transmission 754 and a second uplink transmission 764 using first and second logical channels, respectively. UE 115 may send transmissions 754, 764 via the same carrier. For example, UE 115 may send transmissions 754, 764 on the same carrier using different transmission configurations 742, 744 suitable for reception by corresponding TRPs. Thus, UE 115 may send transmissions 754, 764 to two different TRPs via the same carrier (e.g., simultaneously or concurrently (such as partially concurrently)), even when duplicate data is being sent. In some implementations, UE 115 duplicates at least a portion of transmissions 754, 764. For example, UE 115 may perform the following. Figure 5C and Figure 5D PDCP PDU duplication as described.

[0126] therefore, Figure 7 Enhanced LCP mapping restrictions for a UE are described. Use of the enhanced LCP mapping may enable improvements in multi-TRP mode and / or when duplicating data for transmission. Performing LCP operations using the enhanced LCP mapping restrictions enables the network to reduce latency and improve reliability. The improved performance may increase throughput of communications on the network and enable use of millimeter wave frequency ranges and URLLC mode.

[0127] refer to Figure 8A-8F , showing examples of messages and fields that may include an LCP configuration. Fig. 8A is an example of a block diagram of an exemplary field layout of a downlink control message. Figure 8B-Figure 8F are examples of different configurations of specific fields of the downlink control message of FIG. A.

[0128] Reference Fig. 8A , showing an example of the field layout of the downlink control message 800. The downlink control message 800 may include or correspond to Figure 7 Downlink control message 800 includes one or more fields. Fig. 8A As shown, the downlink control message 800 is a DCI. DCI (or DCI message) can have a variety of different types or formats, such as format 0_0, 0_1, 1_0, 1_1, etc. Fig. 8A In the example shown, the downlink control message 800 includes one or more first fields 812, a value field 814, and one or more second fields 816. Fig. 8AThree fields are illustrated in FIG. 8 , but DCI 800 may include more than three fields or less than three fields.

[0129] The value field 814 may indicate a corresponding transmitted SRI value, SSB (synchronization signal block) value, RS (e.g., NZP-CSI-RS) value, TCI state value, or a combination thereof. For example, the value field 814 indicates the corresponding transmitted SRI and RV values. The value indicated by the value field 814 may be used for LCP, such as for enhanced LCP restriction. In a specific implementation, the value field 814 is a multi-bit field. In the implementation described herein, as Figure 8B-Figure 8F As shown, the value (or sequence thereof) of the value field 814 sent can be reused to identify the value of a different parameter. Additionally or alternatively, the value field 814 can be the first field or the last field.

[0130] refer to Figure 8B-Figure 8F , shows an example of a value field 814. Figure 8B-Figure 8F In the example, the value field 814 includes or corresponds to the SRI field 820 and may indicate a value of an SRI value, an SRS value, an SSB value, an RS value, a TCI state, or a combination thereof for corresponding transmission. Figure 8B In the example, SRI field 820 indicates the corresponding transmitted SRI value, SRI value 832. In a specific implementation, SRI field 820 is a multi-bit field. In the implementation described herein, Figure 8C-8F As shown, the value of the SRI field 820 (or its sequence) may be reused to identify the values ​​of other parameters.

[0131] exist Figure 8C In , the SRI field 822 includes or indicates the SSB value 834. Fig.8D In , the SRI field 824 includes or indicates the NZP-CSI-RS value 836. Fig. 8E In , the SRI field 826 includes or indicates an SSB value 834, which indicates a TCI value 842 such as a TCI status value. Fig.8F , the SRI field 826 includes or indicates an NZP-CSI-RS value 836, which indicates a TCI value 842 such as a TCI state value.

[0132] The SRI field (e.g., 822-828) may directly indicate a value such as an SRS value. For example, the value of the SRI field, i.e., the value identified by its bits, is or indicates the value of one or more SRI values ​​corresponding to the transmission. For illustration, one bit of the SRI field corresponds to a particular transmitted SRI value.

[0133] Alternatively, the SRI field may indicate a value indirectly, i.e., identify the value by indicating a member of a set. For example, the value of the SRI field, i.e., the value identified by its bits, indicates a particular member of a set of values, and the value of the particular member (e.g., the second value) indicates the parameter value. For illustration, the bit sequence 111 indicates the 8th member of the set. Although, in Figure 8A-8F 8, but the downlink control message 800 may be a MAC CE or an RRC message. In such an implementation, the downlink control message 800 may include an SRI field instead of an SRI field.

[0134] Fig. 9 is a block diagram illustrating example blocks executed by a UE configured according to one aspect of the present disclosure. Fig.11 The example blocks are described with reference to UE 115 as shown. Fig.11 1 is a block diagram illustrating a UE 115 configured according to one aspect of the present disclosure. The UE 115 includes Figure 2 115. For example, the UE 115 includes a controller / processor 280 that operates to execute logic or computer instructions stored in a memory 282 and controls the components of the UE 115 that provide the features and functions of the UE 115. The UE 115 sends and receives signals via wireless radios 1100a-r and antennas 252a-r under the control of the controller / processor 280. Figure 2 As shown for UE 115, wireless radios 1100a-r include various components and hardware, including modulators / demodulators 254a-r, MIMO detectors 256, receive processors 258, transmit processors 264, and TX MIMO processors 266. Fig.11 As shown in the example, the memory 282 stores multi-TRP logic 1102, LCP logic 1103, replication logic 1104, LCP restriction data 1105, SRS configuration data 1106 (e.g., allowed SRS configurations), SRS configuration data 1107, logical channel data 1108, transmission channel data 1109, and transmission parameter data 1110.

[0135] At block 900, a mobile communication device such as a UE receives a logical channel prioritization (LCP) restriction configuration for a logical channel indicating a set of SRS configurations. A UE such as UE 115 receives a downlink transmission (e.g., a first downlink transmission, such as a DCI, RRC, MAC CE) via a wireless radio 1100a-r and antennas 252a-r. The downlink transmission (e.g., 750) includes an LCP restriction (e.g., 706) for at least one logical channel. The LCP restriction may be based on SRS / SRI, such as may indicate an allowed SRS / SRI configuration set (e.g., 708).

[0136] The UE 115 may execute the multi-TRP logic 1102 stored in the memory 282 under the control of the controller / processor 280. The execution environment of the multi-TRP logic 1102 provides the UE 115 with functionality to define and execute multi-TRP procedures. Additionally, the UE 115 may execute one or more of the LCP logic 1103 and / or the replication logic 1104. The execution environment of the multi-TRP logic 1102 (and optionally the LCP logic 1103 and / or the replication logic 1104) defines different multi-TRP procedures, such as determining a multi-TRP mode, determining an LCP mode, determining enhanced LCP restrictions, updating LCP restrictions, selecting logical channels, replicating data, etc. For illustration, the UE 115 may store / update LCP restriction data 1105 based on a received LCP restriction, and / or may store / update an allowed SRS configuration 1106 based on a received allowed SRS / SRI configuration set. Additionally, UE 115 may send an acknowledgement message in response to the downlink transmission to indicate successful receipt and decoding of the downlink transmission.

[0137] At block 901, the UE 115 receives an uplink grant indicating an uplink grant instance and an SRS configuration for the uplink grant instance. The UE 115 receives an uplink grant (e.g., a second downlink transmission) via the wireless radio 1100a-r and the antenna 252a-r. The uplink grant may indicate or include one or more uplink grant instances for a particular TRP and may indicate corresponding SRS configurations 1107 (e.g., 708a, 708b) for the uplink grant instance and the particular TRP.

[0138] In some implementations, the uplink grant is a periodic grant. In other implementations, another uplink grant is received that includes or is a periodic grant. In such a periodic grant implementation, the UE 115 may execute periodic grant logic stored in the memory 282 under the control of the controller / processor 280. The execution environment of the periodic grant logic defines different periodic grant processes, such as determining a periodic grant configuration, configured grant configurations, and / or scheduling uplink grants. The UE 115 may schedule or determine the scheduling of upcoming uplink transmissions based on the periodic grants, and may use the antennas 252a-r and wireless radios 1100a-r to send such downlink transmissions.

[0139] At box 902, the UE 115 selects a logical channel of resources to use for the uplink grant instance based in part on the SRS configuration set and the SRS configuration for the uplink grant instance. The UE 115 selects a logical channel from a plurality of logical channels based on an enhanced LCP mapping restriction and an indication in the uplink grant (e.g., based on an indication of SRS / SRI). For example, an execution environment of the multi-TRP logic 1102 (and optional LCP logic 1103 and / or replication logic 1104) provides the UE 115 with functionality described in various aspects of the present disclosure, such as performing LCP operations. For illustration, in an execution environment of the multi-TRP logic 1102 (and optional LCP logic 1103), the UE 115, under the control of the controller / processor 280, can determine a specific logical channel among the logical channels indicated by the logical channel data 1108 based on the LCP restriction 1105, the SRS configuration 1106, and the SRS configuration 1107.

[0140] As an illustrative example, UE 115 selects a logical channel by determining an SRS configuration for an uplink grant instance based on a value of an SRS resource indicator field associated with the uplink grant instance, and determining a logical channel to use resources of the uplink grant instance based on a value of the SRS resource indicator field associated with the uplink grant instance. As another illustrative example, UE 115 determines a possible logical channel for the uplink grant instance from among multiple logical channels by determining a possible logical channel for the uplink grant instance from among multiple logical channels based on a corresponding SRS configuration set associated with each of the multiple logical channels and a plurality of logical channels including the logical channel, determining an unavailable logical channel for the uplink grant instance from among multiple logical channels based on an LCP mapping restriction (e.g., a general or conventional LCP mapping restriction (such as a non-SRS / SRI LCP mapping restriction), or both.

[0141] In other implementations, the UE 115 may perform additional blocks (or the UE 115 may be configured to further perform additional operations). For example, the UE 115 may send data for the selected logical channel, send an acknowledgment of the uplink grant, or a combination thereof after block 902. As another example, the UE 115 may copy the data for the selected logical channel to generate second data, perform a second LCP mapping on the second data to determine a second logical channel, and send second data for the second logical channel. In a specific implementation, as shown in FIG. Figure 5C , 5D As described in 6B, the data is sent to the first TRP using the same carrier and the copied data is sent to the second TRP. As an additional example, UE 115 can perform one or more operations described above. As another example, UE 115 can perform one or more aspects described below.

[0142] In a first aspect, the UE 115 transmits data via a selected logical channel, wherein an SRS configuration set associated with the logical channel is a subset of an allowed SRS configuration set for a plurality of logical channels including the logical channel.

[0143] In a second aspect, alone or in combination with one or more of the above aspects, selecting a logical channel to use the resources of the uplink grant instance based in part on the SRS configuration set and the SRS configuration includes: UE115 determines the SRS configuration for the uplink grant instance based on the value of the SRS resource indicator field associated with the uplink grant instance, and determines the logical channel to use the resources of the uplink grant instance based on the value of the SRS resource indicator field associated with the uplink grant instance.

[0144] In a third aspect, alone or in combination with one or more of the above aspects, determining a logical channel for resources of an uplink grant instance to be used based on the value of an SRS resource indicator field includes: UE 115 determines a possible logical channel for the uplink grant instance from multiple logical channels based on an LCP mapping restriction, and determines a logical channel for resources of the uplink grant instance from the possible logical channels based on the value of the SRS resource indicator field.

[0145] In a fourth aspect, alone or in combination with one or more of the above aspects, determining possible logical channels from multiple logical channels for the uplink grant instance includes: UE 115 determines possible logical channels from multiple logical channels for the uplink grant instance based on a corresponding SRS configuration set associated with each of the multiple logical channels and multiple logical channels including the logical channels, determines unavailable logical channels from multiple logical channels for the uplink grant instance based on LCP mapping restrictions, or both.

[0146] In a fifth aspect, alone or in combination with one or more of the above aspects, UE 115 sends data via a selected logical channel, wherein an SRS configuration set associated with the logical channel is a subset of an allowed SRS configuration group for multiple logical channels including the logical channel, copies a PDCP PDU to generate a second PDCP PDU, wherein the PDCP PDU corresponds to data sent via the selected logical channel; receives a second uplink grant indicating a second uplink grant instance and a second SRS configuration for the second uplink grant instance; selects a second logical channel of resources to use the second uplink grant instance based on the allowed SRS configuration set and the second SRS configuration, and sends second data via the selected second logical channel, the second data including a second PDCP PDU.

[0147] In a sixth aspect, alone or in combination with one or more of the above aspects, the uplink grant also indicates a second uplink grant instance, and the UE 115 further sends data via the selected logical channel, wherein the SRS configuration set associated with the logical channel is a subset of the allowed SRS configuration set for multiple logical channels including the logical channel, copies the PDCP PDU to generate a second PDCP PDU, wherein the PDCP PDU corresponds to the data sent via the selected logical channel, based on the allowed SRS configuration set and the second SRS configuration for the second uplink grant instance, selects a second logical channel of resources to use the second uplink grant instance, and sends second data via the selected logical channel, the second data including the second PDCP PDU.

[0148] In a seventh aspect, alone or in combination with one or more of the above aspects, the SRS configuration for the uplink grant instance indicates an SRS indicator value.

[0149] In an eighth aspect, alone or in combination with one or more of the above aspects, the SRS configuration for the uplink grant instance indicates an SSB value.

[0150] In a ninth aspect, alone or in combination with one or more of the above aspects, the SRS configuration for the uplink grant instance indicates a NZP-CSI-RS-resource value.

[0151] In a tenth aspect, either alone or in combination with one or more of the above aspects, the SRS configuration indicates a TCI indication, and wherein the TCI indication comprises a TCI status indication of an SSB or NZP-CSI-RS-resource.

[0152] In an eleventh aspect, alone or in combination with one or more of the above aspects, the LCP restriction configuration is included in a DCI, MAC CE or RRC message.

[0153] In a thirteenth aspect, alone or in combination with one or more of the above aspects, the uplink grant comprises a dynamic grant, and wherein the uplink grant comprises a DCI.

[0154] In a fourteenth aspect, alone or in combination with one or more of the above aspects, an uplink grant comprises a configured grant, and wherein the uplink grant comprises one or more of a DCI or an RRC message.

[0155] In a fifteenth aspect, alone or in combination with one or more of the above aspects, the UE 115 transmits a message including an SRS signal, wherein an SRI field of the LCP restriction configuration is generated based on the SRS signal.

[0156] Therefore, the UE and the base station can perform enhanced LCP mapping for the multi-TRP mode. By performing enhanced LCP mapping for multiple TRPs, additional functions can be implemented, such as the ability to send replicated data to two different TRPs using the same carrier. Therefore, latency and overhead can be reduced, and throughput and reliability can be increased.

[0157] Fig.10 is a block diagram illustrating example blocks executed by a base station configured according to one aspect of the present disclosure. Fig.12 The example blocks are described using a gNB 105 (or eNB) as shown. Fig.12 is a block diagram illustrating a gNB 105 configured according to one aspect of the present disclosure. The gNB 105 includes Figure 2105. For example, the gNB 105 includes a controller / processor 240 that operates to execute logic or computer instructions stored in a memory 242 and to control components of the gNB 105 that provide the features and functions of the gNB 105. The gNB 105 transmits and receives signals via the wireless radios 1200a-t and antennas 234a-r under the control of the controller / processor 240. Figure 2 As shown for gNB 105, wireless radio 1200a-t includes various components and hardware, including modulator / demodulators 232a-t, MIMO detector 236, receive processor 238, transmit processor 220, and TX MIMO processor 230. Data 1202-1207 in memory 242 may include or correspond to corresponding data 1102-1110 in memory 282, respectively.

[0158] At block 1000, a network entity such as a gNB sends a logical channel prioritization (LCP) restriction configuration for a logical channel indicating a set of SRS configurations. A gNB such as gNB 105 may execute multi-TRP logic 1202 stored in memory 242 under the control of controller / processor 240. The execution environment of multi-TRP logic 1202 provides gNB 105 with functionality to define and execute multi-TRP procedures.

[0159] The execution environment of the multi-TRP logic 1202 defines different multi-TRP procedures, such as signaling notifications for enhancing LCP mapping operations and indicating LCP restriction configurations. To illustrate, the gNB 105 sends a downlink configuration message (e.g., 750) including 1204 and 1205 to the UE 115 via the wireless radio 1200a-t and the antennas 234a-r, such as in response to a configuration, capability, or mode message (e.g., 748).

[0160] At block 1001, the gNB 105 determines data for a logical channel to be scheduled for a particular user equipment. The execution environment of the multi-TRP logic 1202 provides the gNB 105 with functionality to define and execute the multi-TRP process. Within the execution environment of the multi-TRP logic 1202, the gNB 105, under the control of the controller / processor 240, determines that the UE has data for a logical channel to be scheduled. The gNB 105 may determine, in response to receiving an uplink message, that the UE has data to send. When the UE is sending data via a configured grant, the gNB 105 may determine that the UE has and will have data to send periodically in the future.

[0161] At block 1002, the gNB 105 sends an uplink grant indicating an uplink grant instance for a particular user equipment, the uplink grant instance indicating an SRS configuration in the SRS configuration set associated with the logical channel. The gNB 105 generates and sends a downlink transmission (e.g., a second downlink transmission) via the antennas 234a-t and the wireless radios 1200a-t. The downlink transmission may include or correspond to Fig. 6A or Figure 7 For example, the downlink transmission may include one of the SRS configurations 1206 (eg, 708a, 708b, or both).

[0162] For example, the execution environment of the multi-TRP logic 1202 (and optional LCP logic 1203) defines different multi-TRP (and LCP) procedures, such as LCP restrictions and configurations. As gNB 105, for illustration, in the execution environment, gNB 105, under the control of the controller / processor 240, selects SRS configuration 1206 from allowed SRS configurations 1205 and generates (e.g., encodes) a downlink transmission (e.g., DCI or RRC) including SRS configuration 1206.

[0163] At block 1003, gNB 105 receives a transmission corresponding to an uplink grant instance and including data for a logical channel. The gNB receives the uplink transmission via antennas 234a-t and wireless radios 1200a-t. The uplink transmission (e.g., 754, 764) may be configured for reception by gNB 105 based on SRS configuration 1206 and LCP restrictions 1204 and allowed SRS configurations 1205. For illustration, the uplink transmission may be associated with or transmitted via transmission parameters 1110 and / or 1207.

[0164] In other implementations, the gNB 105 (or another base station or network entity) may perform additional blocks (or the gNB 105 may be configured to further perform additional operations). For example, the gNB 105 may perform one or more of the operations described above. As another example, the gNB 105 may perform one or more aspects described below.

[0165] In a first aspect, gNB 105 sends a second LCP restriction configuration for a second logical channel, which indicates a second set of SRS configurations associated with the second logical channel, determines second data of the second logical channel to be scheduled for a specific UE, sends a second uplink grant indicating a second uplink grant instance for the specific UE, wherein the second uplink grant instance indicates a second SRS configuration associated with the second logical channel in the second set of SRS configurations, and receives a second transmission corresponding to the second uplink grant instance including second data for the second logical channel.

[0166] In a second aspect, alone or in combination with one or more of the above aspects, the LCP restriction configuration and the second LCP restriction configuration are sent respectively.

[0167] In a third aspect, alone or in combination with one or more of the above aspects, the LCP restriction configuration and the second LCP restriction configuration are transmitted in the same transmission.

[0168] In a fourth aspect, alone or in combination with one or more of the above aspects, a first transmission reception point receives the transmission, and a second transmission reception point receives the second transmission, and wherein the transmission and the second transmission include replicated data.

[0169] In a fifth aspect, alone or in combination with one or more of the above aspects, the first base station receives the transmission and the second base station receives the second transmission, and wherein the transmission and the second transmission include copied data.

[0170] In a sixth aspect, alone or in combination with one or more of the above aspects, the SRS configuration is indicated by an SRS indicator field indicating an SRS indicator value.

[0171] In a seventh aspect, alone or in combination with one or more of the above aspects, the SRS configuration is indicated by an SRS indicator field indicating an SSB value.

[0172] In an eighth aspect, alone or in combination with one or more of the above aspects, the SRS configuration is indicated by an SRS indicator field indicating an NZP-CSI-RS-resource value.

[0173] In a ninth aspect, either alone or in combination with one or more of the above aspects, an SRS configuration is indicated by an SRS indicator field indicating a TCI indication, wherein the TCI indication includes a TCI status indication of an SSB or NZP-CSI-RS-resource.

[0174] In a tenth aspect, alone or in combination with one or more of the above aspects, LCP restriction configuration is included in a DCI, MAC CE or RRC message.

[0175] In an eleventh aspect, alone or in combination with one or more of the above aspects, the uplink grant comprises a dynamic grant or a configured grant.

[0176] In an eleventh aspect, alone or in combination with one or more of the above aspects, before sending the LCP restriction configuration: the gNB 105 receives a message including an SRS signal from the UE, and generates an SRI field of the LCP restriction configuration based on the SRS signal.

[0177] Therefore, the UE and the base station can perform enhanced LCP mapping for the multi-TRP mode. By performing enhanced LCP mapping for multiple TRPs, additional functions can be implemented, such as the ability to send replicated data to two different TRPs using the same carrier. Therefore, latency and overhead can be reduced, and throughput and reliability can be increased.

[0178] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout the above specification may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0179] Fig. 9 and Fig.10 The functional blocks and modules in may include processors, electronic devices, hardware devices, electronic components, logical circuits, memories, software codes, firmware codes, etc., or any combination thereof.

[0180] The technician will also understand that the various illustrative logic blocks, modules, circuits and algorithm steps described in conjunction with this disclosure can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits and steps have been generally described above in terms of their functions. Whether this functionality is implemented as hardware or software depends on the specific application and design constraints imposed on the entire system. The technician can implement the described functions in a changing manner for each specific application, but this implementation decision should not be interpreted as causing a departure from the scope of the present disclosure. The skilled technician will also easily recognize that the order or combination of the components, methods or interactions described herein are merely examples, and the components, methods or interactions of various aspects of the present disclosure can be combined or performed in a manner different from the manner shown and described herein.

[0181] The hardware and data processing apparatus in conjunction with the various illustrative logical blocks, modules, and circuits disclosed and described herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

[0182] The steps of the method or algorithm described in conjunction with the disclosure herein can be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module can reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and can write information to the storage medium. Alternatively, the storage medium can be an integral part of the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. Alternatively, the processor and the storage medium can reside in a user terminal as discrete components.

[0183] In one or more exemplary designs, the functions described can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, these functions can be stored on a computer-readable medium or sent as one or more instructions or codes on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and communication media include any media that facilitates the transfer of computer programs from one place to another. Computer-readable storage media can be any available media that can be accessed by a general or special-purpose computer. As an example and not a limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or can be used to carry or store required program code components in the form of instructions or data structures and can be accessed by a general or special-purpose computer or a general or special-purpose processor. Any other medium. Moreover, the connection can be appropriately referred to as a computer-readable medium. For example, if software is sent from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair or digital subscriber line (DSL), coaxial cable, fiber optic cable, twisted pair or DSL are included in the definition of the medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0184] As used herein, including in the claims, the term "and / or," when used in a list of two or more items, means that any one of the listed items may be used alone, or any combination of two or more of the listed items may be used. For example, if a combination is described as including components A, B, and / or C, the combination may include only A; only B; only C; A and B combined; A and C combined; B and C combined; or A, B, C combined. Also, as used herein, including in the claims, "or" used in a list of items beginning with "at least one of..." indicates a disjunctive list, so that, for example, a list of "at least one of A, B, or C" means any one of A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination thereof.

[0185] The foregoing description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Therefore, the disclosure is not intended to be limited to the examples and designs described herein, but rather to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A wireless communication method, comprising: Receiving, by a user equipment UE, a logical channel prioritization (LCP) restriction configuration for a logical channel, the LCP restriction configuration indicating a sounding reference signal (SRS) configuration set associated with the logical channel; receiving, by the UE, an uplink grant indicating an uplink grant instance and an SRS configuration for the uplink grant instance; selecting, by the UE based in part on an SRS configuration set and the SRS configuration for the uplink grant instance, the logical channel to use resources of the uplink grant instance; sending, by the UE, data via the selected logical channel, wherein the SRS configuration set associated with the logical channel is a subset of an allowed SRS configuration set for a plurality of logical channels including the logical channel; as well as The UE sends second data via a second logical channel and a carrier that is the same as the carrier used to send the data based on the allowed SRS configuration set, wherein the second data includes a second Packet Data Convergence Protocol (PDCP) packet data unit (PDU), and the second PDCP PDU is generated based on copying the PDCP PDU corresponding to the data sent via the selected logical channel.

2. The method according to claim 1, wherein: Selecting, by the UE based in part on the SRS configuration set and the SRS configuration, the logical channel of the resources of the uplink grant instance to use comprises: determining the SRS configuration for the uplink grant instance based on a value of an SRS resource indicator field associated with the uplink grant instance; and The logical channel to use the resources of the uplink grant instance is determined based on the value of the SRS resource indicator field associated with the uplink grant instance.

3. The method according to claim 2, wherein: Determining the logical channel of the resources of the uplink grant instance to use based on the value of the SRS resource indicator field comprises: determining a possible logical channel from among a plurality of logical channels for the uplink grant instance based on the LCP mapping constraints; and The logical channel that is to use the resources of the uplink grant instance is determined from the possible logical channels based on the value of the SRS resource indicator field.

4. The method according to claim 3, wherein: Determining a possible logical channel from among a plurality of logical channels for the uplink grant instance comprises: determining, based on a corresponding SRS configuration set associated with each logical channel of the plurality of logical channels and the plurality of logical channels including the logical channel, an available logical channel of the plurality of logical channels for the uplink grant instance; determining an unavailable logical channel for the uplink grant instance among the plurality of logical channels based on an LCP mapping restriction; or Both.

5. The method according to claim 1, further comprising: receiving, by the UE, a second uplink grant indicating a second uplink grant instance and a second SRS configuration for the second uplink grant instance; A second logical channel to use resources of the second uplink grant instance is selected by the UE based on the allowed SRS configuration set and the second SRS configuration.

6. The method according to claim 1, wherein: The uplink grant further indicates a second uplink grant instance, and further includes: A second logical channel of resources of the second uplink grant instance is selected by the UE based on the allowed SRS configuration set and a second SRS configuration for the second uplink grant instance to use.

7. An apparatus configured for wireless communication, the apparatus comprising: at least one processor; as well as a memory coupled to the at least one processor, Wherein, the at least one processor is configured to: Receiving, by a user equipment UE, a logical channel prioritization (LCP) barring configuration for a logical channel, the LCP barring configuration indicating an SRS configuration set associated with the logical channel; receiving, by the UE, an uplink grant indicating an uplink grant instance and an SRS configuration for the uplink grant instance; selecting, by the UE based in part on an SRS configuration set and the SRS configuration for the uplink grant instance, the logical channel to use resources of the uplink grant instance; transmitting, by the UE, data via the selected logical channel, wherein the SRS configuration set associated with the logical channel is a subset of an allowed SRS configuration set for a plurality of logical channels including the logical channel; and The UE sends second data via a second logical channel and a carrier that is the same as the carrier used to send the data based on the allowed SRS configuration set, wherein the second data includes a second Packet Data Convergence Protocol (PDCP) packet data unit (PDU), and the second PDCP PDU is generated based on copying the PDCP PDU corresponding to the data sent via the selected logical channel.

8. The device according to claim 7, wherein: The SRS configuration for the uplink grant instance indicates an SRS indicator value.

9. The device according to claim 7, wherein: The SRS configuration for the uplink grant instance indicates a synchronization signal block, SSB, value.

10. The device according to claim 7, wherein: The SRS configuration for the uplink grant instance indicates a non-zero power channel state information reference signal, NZP-CSI-RS-resource value.

11. The device according to claim 7, wherein: The SRS configuration indication includes a transmission configuration indicator (TCI) indication, and wherein the TCI indication includes a TCI state indication of an SSB or NZP-CSI-RS-resource.

12. The device according to claim 7, wherein: The LCP restriction configuration is included in a downlink control information DCI, a medium access control MAC control element CE or a radio resource control RRC message.

13. The device according to claim 7, wherein: The uplink grant comprises a dynamic grant, and wherein the uplink grant comprises downlink control information DCI.

14. The device according to claim 7, wherein: The uplink grant comprises a configured grant, and wherein the uplink grant comprises one or more of a DCI or an RRC message.

15. The device according to claim 7, wherein: The processor is further configured to: A message including an SRS signal is sent by the UE, wherein an SRS resource indicator SRI field of the LCP restriction configuration is generated based on the SRS signal.

16. A wireless communication method, comprising: Sending, by a network entity, a logical channel prioritization (LCP) restriction configuration for a logical channel, the LCP restriction configuration indicating a sounding reference signal (SRS) configuration set associated with the logical channel; Determining, by the network entity, data of the logical channel of the user equipment UE to be scheduled; An uplink grant is sent by the network entity, where the uplink grant indicates an uplink grant instance for the UE, wherein the uplink grant instance indicates an SRS configuration of the SRS configuration set; receiving, by the network entity, a transmission of the data corresponding to the uplink grant instance and comprising the logical channel; sending, by the network entity, a second LCP restriction configuration for a second logical channel, the second LCP restriction configuration indicating a second set of SRS configurations associated with the second logical channel; determining, by the network entity, second data of the second logical channel of the UE to be scheduled; sending, by the network entity, a second uplink grant, the second uplink grant indicating a second uplink grant instance for the UE, wherein the second uplink grant instance indicates a second SRS configuration of the second set of SRS configurations associated with the second logical channel; and A second transmission corresponding to the second uplink grant instance and comprising the second data for the second logical channel is received by the network entity via the same carrier as used to receive the transmission corresponding to the uplink grant and comprising the data for the logical channel.

17. The method according to claim 16, wherein: The LCP restriction configuration and the second LCP restriction configuration are sent separately.

18. The method according to claim 16, wherein: The LCP restriction configuration and the second LCP restriction configuration are sent in the same transmission.

19. The method according to claim 16, wherein: The network entity corresponds to a base station, wherein a first transmission reception point receives the transmission and a second transmission reception point receives the second transmission, and wherein the transmission and the second transmission include replicated data.

20. The method according to claim 16, wherein: The network entity comprises two base stations, wherein a first base station receives the transmission and a second base station receives the second transmission, and wherein the transmission and the second transmission comprise replicated data.

21. An apparatus configured for wireless communication, the apparatus comprising: at least one processor; as well as a memory coupled to the at least one processor, Wherein, the at least one processor is configured to: Sending, by a network entity, a logical channel prioritization (LCP) restriction configuration for a logical channel, the LCP restriction configuration indicating a sounding reference signal (SRS) configuration set associated with the logical channel; Determining, by the network entity, data of the logical channel of the user equipment UE to be scheduled; sending, by the network entity, an uplink grant indicating an uplink grant instance for the UE and an SRS configuration of the SRS configuration set; receiving, by the network entity, a transmission of the data corresponding to the uplink grant instance and comprising the logical channel; sending, by the network entity, a second LCP restriction configuration for a second logical channel, the second LCP restriction configuration indicating a second set of SRS configurations associated with the second logical channel; determining, by the network entity, second data of the second logical channel of the UE to be scheduled; sending, by the network entity, a second uplink grant, the second uplink grant indicating a second uplink grant instance for the UE, wherein the second uplink grant instance indicates a second SRS configuration of the second set of SRS configurations associated with the second logical channel; and A second transmission corresponding to the second uplink grant instance and comprising the second data for the second logical channel is received by the network entity via the same carrier as used to receive the transmission corresponding to the uplink grant and comprising the data for the logical channel.

22. The device according to claim 21, wherein The SRS configuration is indicated by an SRS indicator field indicating an SRS indicator value.

23. The device according to claim 21, wherein The SRS configuration is indicated by an SRS indicator field indicating a synchronization signal block SSB value.

24. The device according to claim 21, wherein The SRS configuration is indicated by an SRS indicator field indicating a non-zero power channel state information reference signal NZP-CSI-RS-resource value.

25. The device according to claim 21, wherein The SRS configuration is indicated by an SRS indicator field indicating a transmission configuration indicator TCI indication, and wherein the TCI indication includes a TCI state indication of an SSB or NZP-CSI-RS-resource.

26. The device according to claim 21, wherein The LCP restriction configuration is included in a downlink control information DCI, a medium access control MAC control element CE or a radio resource control RRC message.

27. The device according to claim 21, wherein The uplink grant comprises a dynamic grant or a configured grant.

28. The apparatus of claim 21, further comprising, before sending the LCP restriction configuration: A message including an SRS signal is received by the network entity from the UE; and an SRS resource indicator (SRI) field of the LCP restriction configuration is generated by the network entity based on the SRS signal.

29. A non-transitory computer readable medium storing instructions that, when executed by a processor, cause the processor to perform operations comprising: Receiving, by a user equipment UE, a logical channel prioritization (LCP) restriction configuration for a logical channel, the LCP restriction configuration indicating a sounding reference signal (SRS) configuration set associated with the logical channel; receiving, by the UE, an uplink grant indicating an uplink grant instance and an SRS configuration for the uplink grant instance; selecting, by the UE based in part on an SRS configuration set and the SRS configuration for the uplink grant instance, the logical channel to use resources of the uplink grant instance; sending, by the UE, data via the selected logical channel, wherein the SRS configuration set associated with the logical channel is a subset of an allowed SRS configuration set for a plurality of logical channels including the logical channel; as well as The UE sends second data via a second logical channel and a carrier that is the same as the carrier used to send the data based on the allowed SRS configuration set, wherein the second data includes a second Packet Data Convergence Protocol (PDCP) packet data unit (PDU), and the second PDCP PDU is generated based on copying the PDCP PDU corresponding to the data sent via the selected logical channel.

30. A non-transitory computer readable medium storing instructions that, when executed by a processor, cause the processor to perform operations comprising: Sending, by a network entity, a logical channel prioritization (LCP) restriction configuration for a logical channel, the LCP restriction configuration indicating a sounding reference signal (SRS) configuration set associated with the logical channel; Determining, by the network entity, data of the logical channel of the user equipment UE to be scheduled; An uplink grant is sent by the network entity, where the uplink grant indicates an uplink grant instance for the UE, wherein the uplink grant instance indicates an SRS configuration of the SRS configuration set; receiving, by the network entity, a transmission of the data corresponding to the uplink grant instance and comprising the logical channel; sending, by the network entity, a second LCP restriction configuration for a second logical channel, the second LCP restriction configuration indicating a second set of SRS configurations associated with the second logical channel; determining, by the network entity, second data of the second logical channel of the UE to be scheduled; sending, by the network entity, a second uplink grant, the second uplink grant indicating a second uplink grant instance for the UE, wherein the second uplink grant instance indicates a second SRS configuration of the second set of SRS configurations associated with the second logical channel; and A second transmission corresponding to the second uplink grant instance and comprising the second data for the second logical channel is received by the network entity via the same carrier as used to receive the transmission corresponding to the uplink grant and comprising the data for the logical channel.

31. An apparatus configured for wireless communication, the apparatus comprising: means for receiving, by a user equipment UE, a logical channel prioritization (LCP) barring configuration for a logical channel, the LCP barring configuration indicating a sounding reference signal (SRS) configuration set associated with the logical channel; means for receiving, by the UE, an uplink grant indicating an uplink grant instance and an SRS configuration for the uplink grant instance; means for selecting, by the UE based in part on an SRS configuration set and the SRS configuration for the uplink grant instance, the logical channel of resources to use for the uplink grant instance; means for transmitting, by the UE, data via the selected logical channel, wherein the SRS configuration set associated with the logical channel is a subset of an allowed SRS configuration set for a plurality of logical channels including the logical channel; as well as A component for sending, by the UE based on the allowed SRS configuration set, second data via a second logical channel and a carrier that is the same as the carrier used to send the data, wherein the second data includes a second Packet Data Convergence Protocol PDCP Packet Data Unit (PDU), and the second PDCP PDU is generated based on copying the PDCP PDU corresponding to the data sent via the selected logical channel.

32. An apparatus configured for wireless communication, the apparatus comprising: means for sending, by a network entity, a logical channel prioritization (LCP) barring configuration for a logical channel, the LCP barring configuration indicating a set of sounding reference signal (SRS) configurations associated with the logical channel; means for determining, by the network entity, data of the logical channel of the user equipment UE to be scheduled; means for sending, by the network entity, an uplink grant indicating an uplink grant instance for the UE, wherein the uplink grant instance indicates an SRS configuration of the SRS configuration set; means for receiving, by said network entity, a transmission corresponding to said uplink grant instance and comprising said data for said logical channel; means for sending, by the network entity, a second LCP barring configuration for a second logical channel, the second LCP barring configuration indicating a second set of SRS configurations associated with the second logical channel; means for determining, by the network entity, second data of the second logical channel of the UE to be scheduled; means for sending, by the network entity, a second uplink grant indicating a second uplink grant instance for the UE, wherein the second uplink grant instance indicates a second SRS configuration of the second set of SRS configurations associated with the second logical channel; and Means for receiving, by the network entity, a second transmission corresponding to the second uplink grant instance and comprising the second data for the second logical channel via the same carrier as used for receiving the transmission corresponding to the uplink grant and comprising the data for the logical channel.

Images