Dynamic selection of LCP parameters

Abstract

A method, computer-readable medium, and apparatus for wireless communication at a base station are provided. The apparatus configures a user equipment (UE) with a first logical channel prioritization (LCP) configuration and a second LCP configuration for a logical channel. The apparatus instructs the UE to use the first LCP configuration for uplink transmission on the logical channel based on a first condition. The apparatus instructs the UE to use the second LCP configuration for uplink transmission on the logical channel based on a second condition. The UE sends an uplink transmission block based on the indicated LCP configuration of the logical channel.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application Serial No. 63 / 012,855, filed on April 20, 2020, and entitled “Dynamic Selection of LCP Parameters,” and U.S. Patent Application No. 17 / 203,649, filed on March 16, 2021, and entitled “Dynamic Selection of LCP Parameters,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to communication systems and, more particularly, to wireless communications including logical channel prioritization. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution released by the Third Generation Partnership Project (3GPP) to meet new requirements and other requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)). 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A brief summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a base station. The apparatus configures a user equipment (UE) with a first logical channel prioritization (LCP) configuration and a second LCP configuration for a logical channel. The apparatus instructs the UE to use the first LCP configuration for uplink transmission on the logical channel based on a first condition. The apparatus instructs the UE to use the second LCP configuration for uplink transmission on the logical channel based on a second condition.

[0008] In another aspect of the present disclosure, a method, computer-readable medium, and apparatus are provided for wireless communication at a UE. The apparatus receives a configuration of a first LCP configuration and a second LCP configuration for a logical channel. The apparatus receives a first indication of using the first LCP configuration for uplink transmission on the logical channel based on a first condition, and receives a second indication of using the second LCP configuration for uplink transmission on the logical channel based on a second condition. The apparatus sends an uplink transmission based on the first LCP configuration or the second LCP configuration. For example, the apparatus may send an uplink transmission block based on the LCP configuration of the logical channel that satisfies a specific condition.

[0009] To accomplish the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A , 2B , 2C and 2D are diagrams illustrating examples of a first 5G / NR frame, a DL channel within a 5G / NR subframe, a second 5G / NR frame, and a UL channel within a 5G / NR subframe, respectively.

[0012] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0013] Figure 4 is an example communication flow between a UE and a base station including a configuration of the UE with multiple LCP scheduling configurations including aspects presented herein.

[0014] Figure 5 is an example communication flow between a UE and a base station including a configuration of the UE with multiple LCP scheduling configurations including aspects presented herein.

[0015] Figure 6 is a flow chart of a method of wireless communication including application of multiple LCP scheduling configurations.

[0016] Figure 7 is a flow chart of a method of wireless communication including configuration of a plurality of LCP scheduling configurations.

[0017] Figure 8 is a diagram illustrating an example of a hardware implementation for an example apparatus configured to perform aspects of a method of wireless communications including application of multiple LCP scheduling configurations.

[0018] Fig. 9 is a diagram illustrating an example of a hardware implementation for an example apparatus configured to perform aspects of a method of wireless communications including configuration of multiple LCP scheduling configurations. DETAILED DESCRIPTION

[0019] 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 represent the only configuration in which the concepts described herein can be practiced. For the purpose of providing a thorough understanding of the various concepts, the detailed description includes specific details. However, it will be clear to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0020] Several aspects of telecommunication systems will now be presented with reference to various devices and methods. These devices and methods will be described in the following detailed description by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements") and illustrated in the accompanying drawings. These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0021] As an example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc.

[0022] Therefore, in one or more example embodiments, the described functions can be implemented with hardware, software or any combination thereof. If implemented with software, the functions can be stored on a computer-readable medium or encoded as one or more instructions or codes on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0023] During the transmission control protocol (TCP) slow start phase, for a given number of TCP packets sent by a base station, there will be an increased number of TCP ACKs from the UE. The TCP congestion window can start with a small value and can be scaled quickly with the number of TCP confirmations (ACKs) until the TCP stream reaches a steady state. Therefore, the TCP implementation will have frequent ACKs in the early TCP phase after the connection (such as during the slow start phase). Parameters can be configured to be more optimal for the steady state phase, and can result in a transmission block including more ACKs than the ACKs that the network can decode. The network can discard at least a portion of the ACKs in the transmission block, resulting in retransmissions and delayed congestion window scaling. The various aspects presented herein implement improved TCP process management of uplink traffic by configuring multiple logical channel prioritization (LCP) scheduling configurations for each logical channel by the base station. Multiple LCP scheduling configurations enable dynamic selection between different configurations based on different TCP phases (e.g., slow start phase or steady state phase) and / or network conditions. The various aspects presented herein provide improved efficiency of resource allocation while also providing an improved user experience.

[0024] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100 including base stations 102 and 180 and multiple UEs 104. As described herein, the base station 102 or 180 may include an LCP configuration component 199, which configures the first LCP configuration and the second LCP configuration for the logical channel for the UE 104, and (dynamically) indicates that the UE uses the first LCP configuration or the second LCP configuration. The base station 102 or 180 may also be configured to receive an uplink transmission from the UE based on the first LCP configuration or the second LCP configuration. The UE 104 may include an LCP configuration component 198, which is configured to receive the first LCP configuration and the second LCP configuration of the logical channel, and (dynamically) receive one or more indications for the UE to use the first LCP configuration or the second LCP configuration. The LCP configuration component 198 may also be configured to send an uplink transmission based on the first LCP configuration or the second LCP configuration. For example, the UE 104 may send an uplink transmission block based on the LCP configuration of the logical channel that meets a specific condition.

[0025] The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0026] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can be connected to the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can be connected to the core network 190 via a second backhaul link 184. The various aspects described herein are not limited to terrestrial networks and can be similarly applicable to non-terrestrial networks (NTNs). In addition to other functions, the base station 102 can also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (eg, through the EPC 160 or the core network 190) via a third backhaul link 134 (eg, an X2 interface). The third backhaul link 134 may be wired or wireless.

[0027] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB) that may provide services to a restricted group referred to as a closed subscriber group (CSG). A communication link 120 between base station 102 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple input and multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. Base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The carriers may be adjacent or non-adjacent to each other. The allocation of carriers may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​than for UL). A component carrier may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell), and a secondary component carrier may be referred to as a secondary cell (SCell).

[0028] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0029] The wireless communication system may further include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) before communicating to determine whether the channel is available.

[0030] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve coverage of the access network and / or increase capacity of the access network.

[0031] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes arises with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in literature and articles, but is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0032] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands of these mid-bands as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling into FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designation FR4a or FR4-1 (52.6GHz-71 GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0033] In view of the above, unless otherwise specifically stated, it should be understood that the term "below 6 GHz" and the like (if used herein) can broadly refer to frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that the term "millimeter wave" and the like (if used herein) can broadly refer to frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0034] The base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in the traditional sub-6 GHz spectrum, in millimeter wave (mmW) frequencies, and / or in near-mmW frequencies for communicating with the UE 104. When the gNB 180 operates in mmW or near-mmW frequencies, the gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near mmW can extend down to frequencies of 3 GHz with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter waves. Communications using the mmW / near-mmW radio frequency (RF) band (e.g., 3 GHz-300 GHz) have extremely high path losses and short distances. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range. The base station 180 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0035] The base station 180 may transmit beamformed signals in one or more transmit directions 182' to the UE 104. The UE 104 may receive beamformed signals from the base station 180 in one or more receive directions 182". The UE 104 may also transmit beamformed signals to the base station 180 in one or more transmit directions. The base station 180 may receive beamformed signals from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base stations 180 / UE 104. The transmit and receive directions of the base station 180 may be the same or different. The transmit and receive directions of the UE 104 may be the same or different.

[0036] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to the IP service 176. The IP service 176 may include the Internet, the intranet, the IP multimedia subsystem (IMS), the PS streaming service, and / or other IP services. The BM-SC 170 may provide functions for MBMS user service provision and delivery. The BM-SC 170 may be used as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0037] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switching (PS) stream (PSS) service, and / or other IP services.

[0038] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of the UEs 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, an oven, a vehicle, a heart monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other appropriate terminology.

[0039] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM and other wireless technologies.

[0040] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G / NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G / NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G / NR subframe. The 5G / NR frame structure can be frequency division duplex (FDD), where, for a particular set of subcarriers (carrier system bandwidth), subframes within a subcarrier set are dedicated to either DL or UL; or the 5G / NR frame structure can be time division duplex (TDD), where, for a particular set of subcarriers (carrier system bandwidth), subframes within a subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2CIn the example provided, it is assumed that the 5G / NR frame structure is TDD, where subframe 4 is configured with slot format 28 (primarily with DL), where D is DL, U is UL, and X is flexible in use between DL / UL, and subframe 3 is configured with slot format 34 (primarily with UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format (dynamically through DL control information (DCI), or semi-statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the following description also applies to the 5G / NR frame structure as TDD.

[0041] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Depending on the time slot configuration, each time slot may include 7 or 14 symbols. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbol on the DL may be a cyclic prefix (CP) OFDM (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ0 to μ5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframes. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figures 2A-2DAn example is provided for slot configuration 0, with 14 symbols per slot, and parameter set μ = 2, with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0042] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0043] like Figure 2A As shown in FIG. 1 , some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration). x , where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0044] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of the frame. The UE 104 uses the PSS to determine the subframe / symbol timing and the physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of the frame. The UE uses the SSS to determine the physical layer cell identification group number and the radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE is able to determine the physical cell identifier (PCI). Based on the PCI, the UE is able to determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (eg, System Information Block (SIB)) that is not transmitted through the PBCH, and paging messages.

[0045] like Figure 2CAs shown in , some of the REs carry DM-RS for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE can send DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent, and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE can send a sounding reference signal (SRS). The SRS can be sent in the last symbol of the subframe. The SRS can have a comb tooth structure, and the UE can send the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to achieve frequency-dependent scheduling on the UL.

[0046] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH may be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0047] Figure 33 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with: broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0048] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes and for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0049] At the UE 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. Subsequently, the RX processor 356 converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

[0050] The controller / processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0051] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0052] The TX processor 368 may select an appropriate coding and modulation scheme and facilitate spatial processing using channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0053] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0054] The controller / processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0055] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Various aspects related to the LCP configuration component 198.

[0056] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 Various aspects related to the LCP configuration component 199.

[0057] When a wireless device performs a new transmission, a Logical Channel Prioritization (LCP) procedure is applied. Uplink data scheduling is controlled by the RRC layer through signaling for each logical channel of each MAC entity. The RRC layer additionally controls the LCP procedure by configuring mapping restrictions for each logical channel. The UE may receive control signaling from the base station and apply the control to the uplink transmission.

[0058] When performing a new transmission, the MAC entity may select a logical channel for each uplink grant that satisfies one or more specific conditions. The specific conditions may be referred to as mapping restrictions for each logical channel. An example condition is a set of one or more subcarrier spacings for transmission, which may be configured as allowed subcarrier spacing index values ​​(e.g., in "allowedSCS-List"). If an allowed SCS list is configured for a logical channel, the MAC entity may select a logical channel in the set of configured allowed SCSs to send an uplink transmission based on the subcarrier spacing index associated with the uplink grant.

[0059] Another example condition is a maximum PUSCH duration for transmission (e.g., which may be referred to as "maxPUSCH-Duration"). If a maximum PUSCH duration is configured for a logical channel, the MAC entity may select a logical channel for uplink transmission based on the configured maximum PUSCH duration being greater than or equal to the PUSCH transmission duration associated with the UL grant.

[0060] Another example condition is a configuration that enables a particular grant type to be used for transmissions on a logical channel. As an example, the configuration may allow a configured grant type 1 (e.g., which may be referred to as "configuredGrantType1Allowed") to be used for transmissions on a logical channel. As an example, if the logical channel is configured to allow configured grant type 1 (e.g., by setting "configuredGrantType1Allowed" to true), then if the uplink grant is a configured grant type 1, the MAC entity may select a logical channel for uplink transmissions.

[0061] Another example condition is a set of one or more allowed cells that are allowed to transmit on the logical channel (e.g., which may be referred to as "allowedServingCells"). If a set of one or more allowed cells is configured for a logical channel, the MAC entity may select a logical channel for uplink transmission based on the allowed cells (including cells with cell information associated with the UL grant). The subcarrier spacing index, PUSCH transmission duration, and cell information may be included in the uplink transmission information received from the lower layer for the corresponding scheduled uplink transmission.

[0062] When a new transmission is performed, the MAC entity can allocate resources to the logical channel. For example, for the logical channel selected for the UL authorization (e.g., in the case of Bj>0), the MAC entity can allocate resources in descending priority order. Bj corresponds to the amount of data and indicates the maximum amount of data to be encoded on the selected logical channel, for example, for the priority bit rate (PBR) and bucket size duration (BSD). If the PBR of the logical channel is set to a high level, such as infinity, the MAC entity can allocate resources for all data available for transmission on the logical channel before meeting the PBR of the lower priority logical channel. The MAC entity can decrement Bj by the total size of the MAC SDU serving logical channel j above. If any resources remain, all selected logical channels can be served in descending priority order (regardless of the value of Bj) until the data or UL authorization of the logical channel is exhausted, whichever comes first. Logical channels configured with the same priority can be served equally. The value of Bj can be negative.

[0063] If the MAC entity is requested to send multiple MAC PDUs simultaneously, or if the MAC entity receives multiple UL grants within one or more overlapping PDCCH opportunities (ie, on different serving cells), the UE may determine the order in which the grants are processed.

[0064] The UE may also follow rules during the scheduling process. For example, if the entire SDU (or partially transmitted SDU or retransmitted RLC PDU) fits into the remaining resources of the associated MAC entity, the UE may not segment the RLC SDU (or partially transmitted SDU or retransmitted RLC PDU). As another example, if the UE segments the RLC SDU from a logical channel, the UE may maximize the size of the segment to fill as much of the grant of the associated MAC entity as possible. As another example, the UE may maximize the transmission of data. As another example, if the MAC entity is given an uplink grant size equal to or greater than 8 bytes while having data available and allowed to be transmitted, the MAC entity may send more than just padding BSR and / or padding.

[0065] In some aspects, the MAC entity may not generate a MAC PDU for the HARQ entity if one or more conditions are met. The conditions may include that the MAC entity is configured with an indication to skip uplink transmission, such as "skipUplinkTxDynamic" is configured with a true value, the grant indicated to the HARQ entity is addressed to a cell radio network temporary identifier (C-RNTI), or the grant indicated to the HARQ entity is a configured uplink grant; there is no non-periodic CSI for the PUSCH transmission request; the MAC PDU includes zero MAC SDUs; and the MAC PDU includes only a periodic buffer status report (BSR) and no data is available for any logical channel group (LCG), or the MAC PDU includes only padding BSR.

[0066] Logical channels may be prioritized based on: priority order (e.g., order starting with the highest priority including C-RNTI MAC-CE or data from an uplink common control channel (UL-CCCH)); configured authorization confirmation MAC-CE; MAC-CE for BSR, except for BSR included for padding; single-entry power headroom report (PHR) MAC-CE or multi-entry PHR MAC-CE; data from any logical channel except data from UL-CCCH; MAC-CE for recommended bit rate query; and MAC-CE for padding of included BSR.

[0067] The Transmission Control Protocol (TCP) uses aspects of network congestion avoidance, including a slow start phase and a congestion window, to help prevent congestion. For example, TCP can implement controls so that a sender does not send more packets than the receiver can receive. The sender can use the acknowledgment of sent data, or the lack of such acknowledgment, to infer network conditions between the TCP sender and the receiver and change the behavior of the data flow. Packets may be lost, duplicated, or delivered out of order at lower levels of the protocol stack based on network congestion, traffic load balancing, or unpredictable network behavior. TCP can help detect these problems, request retransmission of lost data, and reorder out-of-order data. TCP can help reduce network congestion to reduce the occurrence of other problems.

[0068] The congestion window may be maintained by the sender for each connection. The sender may use the congestion window to avoid sending too much traffic to the receiver by limiting the total number of unacknowledged packets that may be in transit. Slow start is also used to avoid sending more data than can be processed. When a connection is established between a sender and a receiver, the congestion window starts with a small value, for example, a small multiple of the maximum segment size (MSS) in size. During the slow start phase, the congestion window scales rapidly from a small starting value in response to the number of TCP ACKs. Although the initial transmission rate may be low due to the small size of the congestion window, the rate of increase may be rapid. For each confirmed packet, the congestion window increases by 1MSS, so that the congestion window effectively doubles for each received TCP acknowledgment. The congestion window may be scaled continuously in this manner until the TCP flow reaches a steady state, for example, until a threshold is reached, packet loss occurs, etc. The increased size of the congestion window increases the transmission rate to the receiver. In a steady state, the congestion window may be adjusted differently, for example, without the same level of scaling applied during the slow start phase. As an example, the congestion window may scale linearly with each TCP acknowledgment received during the steady state phase.

[0069] TCP can be optimized for accurate delivery rather than timely delivery, and can incur relatively long delays while waiting for retransmission of out-of-order messages or lost messages. If the delay is reduced, the receiver can confirm the packet faster, which then enables the congestion window size to be increased in a faster manner. Therefore, the reduction of uplink delay can affect TCP downlink performance. Since the initial window size of the TCP connection is very small, the increase in window size increases with each size increment. During the slow start phase, the effect of delay reduction will be more significant. For small file sizes, the impact during the slow start phase will be greater, wherein the slow start phase can last for the duration of the file. If the TCP rate can be accelerated, the user experience is improved by increasing the throughput, and the capacity of the system can be used more effectively by delivering more packets. Shorter delay techniques will increase overhead, which will be less effective during the steady state phase. For example, larger overhead will reduce the throughput in the steady state phase.

[0070] Latency can be reduced through configured grant (CG) resources and / or larger parameter sets. Allocation of CG resources provides periodic resources available for transmission. The mapping of logical channels on CG resources and / or parameter sets can be controlled by the network. LCP mapping limits can be dynamically reconfigured so that TCP traffic can benefit from CG resources and large parameter sets in different phases without over-scaling the system.

[0071] The base station may configure multiple sets of LCP mapping restrictions for the UE, for example in RRC signaling. The base station may then dynamically activate / deactivate different sets of LCP mapping restrictions. For example, the base station may send an indication of activating a set of LCP mapping restrictions in a MAC-CE. The MAC-CE may indicate a logical channel and one or more bits indicating activation / deactivation of an RRC-configured set of LCP mapping restrictions.

[0072] During the TCP slow start phase, for a given number of TCP packets sent by the sender, there will be an increasing number of TCP ACKs from the receiver. As described above, the TCP sender side congestion window starts with a smaller value and increases proportionally with the number of TCP ACKs until the TCP flow reaches a steady state. Therefore, many TCP implementations will have frequent ACKs in the early stages after the connection, for example, as part of a TCP slow start operation. Various aspects presented herein implement improved TCP slow start management of uplink traffic (e.g., ACKs from receiving UEs).

[0073] With TCP packet folding features in the downlink, such as TCP Generic Receive Offload (GRO) / Large Receive Offload (LRO) or Receive Side Coalescing (RSC), the UE can send 1 TCP ACK for 2 downlink TCP data packets in the uplink. With GRO / LRO / RSC, the UE can consume about 15K worth of bytes in each TCP packet. This results in 60B uplink TCP ACK traffic for 30K downlink TCP data traffic.

[0074] Since the server can count the number of ACKs in the ramp-up phase (e.g., slow start phase) to adjust the TCP congestion window size, the UE can send a TCP ACK for every 1.5KB or 3KB of TCP downlink traffic in the first few seconds of a new transmission, for example, until the TCP downlink transmission reaches a stable state (e.g., steady state phase).

[0075] The network infrastructure will have difficulty processing more than 200 RLC PDUs in one MAC TB. When the CG is 27K or larger, each MAC TB can carry nearly 400 to 500 RLC PDUs (TCP ACK). The network may not be able to decode / process more than 200 RLC PDUs. The remaining 300 RLC PDUs in the MAC TB can be discarded by the network. As an example, if the UE encodes and sends 500 packets, the base station can decode the first 200 packets and can simply discard the remaining 300 packets. Discarding part of the packets from the UE's MAC TB will cause the base station to have continuous holes at the RLC acknowledgement mode (AM) level. The packets for the holes can be recovered by RLC automatic retransmission request (ARQ). The RLC ARQ process can be a slow recovery process because T reorganization will be more than HARQ level recovery or CG opportunity. In some aspects, T reorganization may involve an RLC level reorganization timer to detect missing holes at the PHY HARQ level. RLC ARQ also increases the number of incomplete TCP ACKs in the uplink (e.g., due to the transmission of new packets and dropped packets). Therefore, dropping a portion of the packets of the MAC TB can make it difficult for the network to quickly get TCP ACKs in sequence and can cause holes in the PDCP reordering window and Treordering when it expires. In some aspects, Treordering may involve a timer for detecting missing holes at the PDCP level. Treordering may refer to a process after the timer expires, such as when PDCP stops waiting for PDU recovery and allows processing of PDUs in the reordering window.

[0076] Various aspects presented herein improve the TCP process in a manner different from adjusting the CG configuration (e.g., grant value or periodicity) and / or the periodic grant configuration (which may have been tuned for the steady state phase). Changes to the CG configuration or the periodic grant configuration may be based on an RRC-level reconfiguration of the UE, which may involve an amount of time that is not beneficial to the slow start phase of the TCP process.

[0077] In the medium access control (MAC), each logical channel can be configured with mapping restrictions. The RRC can additionally control the LCP process by configuring mapping restrictions for each logical channel. The LCP mapping restrictions may include, for example, a list of subcarrier spacings allowed for transmission (e.g., which may be referenced by a parameter name such as "allowedSCS-List"), a maximum PUSCH duration allowed for transmission (e.g., which may be referenced by a parameter name such as "maxPUSCH-Duration"), whether the configured grant type 1 can be used for transmission (e.g., which may be referenced by a parameter name such as "configuredGrantType1Allowed"), and cells allowed for transmission (e.g., which may be referenced by a parameter name such as "allowedServingCells").

[0078] The network may configure CG opportunities and grant sizes based on steady state traffic, which may not accommodate temporary increases in uplink traffic that occur during the slow start phase. A radio network entity (e.g., base station 102 or 180) may not have flow level state information, which may be a core network function (e.g., of core network 190 or EPC 160).

[0079] For example, the network may have a configuration with a smaller CG value (e.g., uplink grant size or longer duration). During the slow start phase, the UE may have a larger number of packets waiting to be sent to the base station even after the CG opportunity. TCP window expansion may be slow during the slow start phase, for example, due to the small starting size of the window. In the steady state phase, a CG with a smaller CG value may be sufficient for uplink traffic.

[0080] The network may have a larger CG (e.g., larger uplink grant size or smaller duration). During the slow start phase, the UE may group a large number of packets into one MAC TB, which may cause the network to drop a portion of the packets as described above. In the steady state phase, a larger CG may result in a waste of grant resources (e.g., MAC padding) because the UE may have fewer TCP ACKs to send during the steady state phase.

[0081] Similarly, other restrictions such as CG period, allowed SCS, and allowed serving cells can be configured based on the steady state traffic model, which may not work well during the slow start phase. Therefore, the base station can configure multiple LCP restriction sets and can dynamically activate them to provide better resource allocation for different TCP phases (e.g., slow start phase and steady state phase). The network can select different restrictions at the RAN level, for example, based on uplink traffic patterns (a large number of ACKs or RLC PDUs in one MAC TB) and / or downlink traffic patterns (TCP extensions or steady state information from the core network). When the uplink is on a thinner pipe (e.g., a smaller bandwidth, such as using LTE or NR with a smaller bandwidth) and the downlink has a thicker pipe (e.g., a larger bandwidth, such as using NR with a higher bandwidth), different amounts of uplink traffic during different phases of the TCP process become more problematic.

[0082] LCP mapping restrictions can focus on the PHY parameters to be selected for a given logical channel traffic. As presented herein, different LCP scheduling configurations (e.g., MAC level parameters) can be configured for UEs that can be dynamically activated / deactivated. The RRC layer can control the scheduling of uplink data through control signaling for each logical channel of each MAC entity. The scheduling of uplink data for each logical channel of each MAC entity can be controlled based on priority, for example, where an increasing priority value indicates a lower priority. The scheduling of uplink data for each logical channel of each MAC entity can be controlled based on PBR (e.g., "prioritisedBitRate"). The scheduling of uplink data for each logical channel of each MAC entity can be controlled based on a bucket size duration (e.g., "bucketSizeDuration"). In some examples, the scheduling of uplink data for each logical channel of each MAC entity can be controlled based on any combination of priority, priority bit rate, or bucket size duration.

[0083] The base station can configure multiple LCP scheduling configurations (including one or more of priority values, priority bit rates, or bucket size durations) for the logical channels of each MAC entity. Different LCP scheduling configurations can enable the base station to dynamically select MAC parameters for logical channels, which MAC parameters help which logical channel (e.g., based on priority) is included in the uplink MAC TB and how much data (e.g., Bj) from the logical channel is included in the uplink MAC TB. Parameter Bj indicates how many packets (e.g., maximum) can be encoded from the selected logical channel based on the priority bit rate and bucket size duration configured for the LCP scheduling configuration. Different LCP scheduling configurations (e.g., with MAC-level parameters) can be used in combination with multiple configured LCP restrictions (e.g., with PHY-level parameters). For example, the base station can activate one or more configured LCP scheduling configurations, and can activate one or more configured LCP mapping restrictions. In some examples, the base station can activate different LCP scheduling configurations for the slow start phase and the steady state phase of the TCP process.

[0084] Figure 4 An example communication flow 400 between a UE 404 and a base station 402 is illustrated, which includes configuration of multiple LCP scheduling configurations. Figure 4 The various aspects described are not limited to base stations of a terrestrial network and may be similarly applicable to an NTN. As shown in 403, a base station 402 configures a plurality of LCP scheduling configuration sets for a logical channel. The LCP scheduling configuration 403 may be configured in RRC signaling for a UE. As an example, the plurality of sets may include a first set of [priority, PBR, BSD] 1 and a second set of [priority, PBR, BSD] 2 for a logical channel.

[0085] The base station 402 may dynamically select a first configuration set of LCP scheduling configurations, for example, [priority, PBR, BSD] for a given logical channel. i. As an example, the base station may select a first set of LCP scheduling configurations for a slow start phase or a steady state, for example, based on a dynamic state of traffic between the UE and the base station. At 405, the base station 402 indicates to the UE the selection of a first LCP scheduling configuration. For example, the base station may activate a first LCP scheduling configuration in the MAC-CE. At 405, the dynamic indication is shown as a dotted line. In some examples, one of the LCP scheduling configurations may be a default LCP scheduling configuration, which is applied until the default LCP scheduling configuration is deactivated and / or until a different LCP scheduling configuration is activated. The base station 402 may activate / deactivate the LCP scheduling configuration configured in the MAC-CE that identifies the logical channel (e.g., including the LCID) and includes a bit indicating that the LCP scheduling configuration is activated / deactivated at 403. The base station may activate / deactivate the LCP configuration (e.g., switch between LCP configurations) based on an upper layer protocol state (such as different states of TCP). For example, the base station may activate one LCP configuration during the slow start phase and may switch to a second LCP configuration during the steady state phase. In another example, the base station may activate / deactivate the LCP configuration based on Quick UDP Internet Connection (QUIC) conditions, Ethernet conditions, etc. In another example, activation / deactivation may be based on MAC level conditions, such as queue size, etc.

[0086] The base station 402 sends downlink data 411 to the UE 404 based on the logical channel. At 413, the UE applies the first LCP scheduling configuration, whether as a default LCP scheduling configuration or based on the activation at 405, to generate a MAC-TB with one or more ACKs for the downlink data 411. At 415, the UE 404 sends a MAC TB to the base station 402.

[0087] A UE variable (eg, Bj maintained for each logical channel j) may be used in the logical channel prioritization process. When a logical channel is established, the MAC entity may initialize Bj of the logical channel to zero.

[0088] For each logical channel j, the MAC entity may increment Bj by the product PBR×T before each instance of the LCP procedure, where T is the time that has passed since Bj was last incremented. If the value of Bj is greater than the bucket size (i.e., PBR×BSD), the MAC entity may set Bj to the bucket size. For example, the time at which the UE updates Bj between LCP procedures may be determined by the UE as long as Bj is up to date when the LCP process is granted.

[0089] As conditions change and / or when the TCP process reaches a steady state, the base station can dynamically select a different LCP scheduling configuration. At 417, the base station 402 indicates activation of the second LCP scheduling configuration. This indication can be sent in a MAC-CE, similar to the indication at 405.

[0090] As shown at 423, the UE applies the second LCP scheduling configuration for sending an ACK for the downlink data 421 (eg, in a MAC TB 425).

[0091] The base station may also configure multiple LCP mapping restrictions for the UE at 407, and may dynamically select between different LCP mapping restrictions at 409 and 419. The configuration at 407 may be in RRC signaling to the UE 404. At 409, a dynamic indication may be indicated to the UE 404 in the MAC-CE. Although shown with separate lines, the configurations at 403 and 407 may be sent together or in an order different from the order shown. For example, the RRC may additionally control the LCP process by configuring mapping restrictions for each logical channel. The mapping restrictions for each logical channel may be based on the allowed subcarrier spacing for transmission, which may be indicated in a list (e.g., "allowedSCS-List"). The mapping restrictions for each logical channel may be based on the maximum PUSCH duration allowed for transmission (e.g., "maxPUSCH-Duration"). The mapping restrictions for each logical channel may be based on the configured grant type (e.g., "configuredGrantType1Allowed"), such as whether the configured grant type 1 can be used for transmission. The mapping restrictions for each logical channel can be based on the cells allowed for transmission (e.g., "allowedServingCells, which sets the cells allowed for transmission"). In some examples, the mapping restrictions for each logical channel can be based on the allowed subcarrier spacing, the maximum PUSCH duration, the configured grant type, or any combination of the cells allowed for transmission.

[0092] In an example for illustrating the concept, each bearer has 100K of data to be sent. The base station 402 may configure radio bearer 1 with a first LCP scheduling configuration (e.g., a default configuration) as [priority 1, PBR=10K, BSD=30K] and a second LCP scheduling configuration (e.g., an enhanced configuration) as [priority 1, PBR=20K, BSD=80K]. For radio bearer 2, the base station 402 may configure the first configuration as [priority 2, PBR=5K, BSD=50K] and the second configuration as [priority 1, PBR=10K, BSD=100K]. For radio bearer 3, the base station 402 may configure the first configuration as [priority 3, PBR=2K, BSD=80K] and the second configuration as [priority 2, PBR=5K, BSD=150K].

[0093] The base station may dynamically select a priority change. For example, during slow start traffic on radio bearer 2, the base station may select an enhanced configuration (e.g., a second LCP scheduling configuration) so that uplink traffic from the UE has priority 1 instead of the default priority 2. The base station 402 may select a priority change during slow start traffic on radio bearer 2. Figure 4 Activation of the enhanced LCP scheduling configuration is indicated at 405 .

[0094] The base station may dynamically select a BSD change. For example, during slow start traffic on radio bearer 1, the base station may select an elevated configuration (e.g., a second LCP scheduling configuration) so that uplink traffic from the UE has a larger BSD configuration. In this example, radio bearer 1 is able to send up to 80K even though the transmission opportunities are spaced with large gaps instead of being capped at 30K.

[0095] The base station may dynamically select a PBR change. For example, during slow start traffic on radio bearer 1, the base station may select an enhanced configuration (e.g., a second LCP scheduling configuration) so that uplink traffic from the UE has a larger PBR from 10K to 20K. During the enhanced period with a PBR change, even if the transmission opportunities are spaced apart with large gaps, the rate of outstanding allowed data in a given time increases as the PBR changes from 10K to 20K (based on Bj=PBR*T).

[0096] PHY level LCP restrictions provide a boost to all bearers, while only a subset of bearers may be in a slow start phase that will benefit from the change in LCP mapping restrictions. MAC level LCP scheduling configuration enables the base station to boost specific bearers in order to address specific bearers with slow start phase traffic. MAC level LCP scheduling configuration provides finer granularity, which enables the base station to address different phases and traffic for specific bearers. MAC level LCP scheduling configuration can better address multi-bearer, multi-packet data network (PDN) communications, and select between configurations in a manner that is localized to the UE rather than affecting the entire system with PHY parameter changes.

[0097] The ability of the network to dynamically select between different configured LCP restrictions at the PHY level and / or between different LCP scheduling configurations at the MAC level from the network (e.g., using MAC CE, RRC, RLC, PHY) provides flexibility in dynamically configuring the UE based on traffic type / state, network radio conditions (such as load, subcarrier spacing, bandwidth (ROT)), etc.

[0098] In some examples, the UE may autonomously select between different configuration sets of LCP restriction and / or LCP scheduling configurations. For example, the UE may autonomously select a set of LCP restriction / LCP scheduling configurations based on any UE-only intelligence (e.g., information) or based on conditions configured by the network for the UE (similar to conditional switching). Figure 5 An example communication flow 500 is illustrated in which a UE 504 may autonomously select between a plurality of configured LCP restrictions and / or LCP scheduling configurations.

[0099] exist Figure 5 In, similar to Figure 4 As described in , the base station 502 configures multiple LCP scheduling configurations for the UE at 503, and configures multiple LCP mapping restrictions for the UE at 507. Figure 5 , combined with Figure 5 The various aspects described are not limited to base stations of terrestrial networks and may similarly be applied to NTNs. Figure 5 In , base station 402 does not activate / deactivate different configurations. Figure 5, at 513, the UE applies a first LCP scheduling configuration and / or a first LCP mapping restriction. At 515, the UE 504 sends a MAC TB with an ACK for the downlink data received at 511 based on the first LCP scheduling configuration and / or the first LCP mapping restriction. At 523, the UE 504 determines to switch to using a different LCP scheduling configuration and / or LCP mapping restriction. At 525, the UE 504 sends a MAC TB with an ACK for the downlink data received at 521 based on the second LCP scheduling configuration and / or the second LCP mapping restriction. In some examples, the UE may determine parameters that may trigger the UE to change to a different configuration. In other examples, at 509, the UE may base the determination on parameters configured by the base station for the UE. In some examples, the UE may apply the first LCP scheduling configuration and / or the first LCP mapping restriction during the slow start phase, and may apply the second LCP scheduling configuration and / or the second LCP mapping restriction during the steady state phase.

[0100] Compared with the TCP steady state phase, the network (such as Figure 4 as shown) or UE (as shown Figure 5 Dynamically selecting between different LCP limits and configurations to accommodate the TCP slow start phase improves the efficient use of radio resources while balancing the improved user experience through fast TCP scaling. Switching between LCP configurations (e.g., switching between LCP configurations) is based on upper layer protocol states, such as different states of TCP. In another example, switching between LCP configurations can be based on QUIC conditions, Ethernet conditions, etc. In another example, switching between LCP configurations can be based on MAC level conditions, such as queue size, etc.

[0101] Figure 6 is a flow chart of a method of wireless communication 600. The method may be performed by a base station or a component of a base station (e.g., base station 102, 180, 310, 402, 502; Fig. 9 The method may include a device 902 in the embodiment of the present invention; a processing system, which may include a memory 376 and may be the entire base station 310 or a component of the base station 310, such as a TX processor 316, an RX processor 370 and / or a controller / processor 375). Optional aspects are shown with dashed lines. The method enables the base station to more efficiently allocate resources and more efficiently configure the UE based on different conditions for different stages of TCP (such as upper layer protocol states or MAC level conditions) and / or based on different network conditions.

[0102] At 602, the base station configures a first LCP configuration and a second LCP configuration for a logical channel for the UE. The first LCP configuration and the second LCP configuration include MAC-level LCP configurations. The base station may configure the first LCP configuration and the second LCP configuration for each logical channel. The first LCP configuration and the second LCP configuration each include one or more of a priority value for the logical channel, a priority bit rate for the logical channel, or a bucket size duration for the logical channel. The priority value for the logical channel may be a lower value indicating a higher priority in the first LCP configuration than in the second LCP configuration. The priority bit rate for the logical channel may be higher in the first LCP configuration than in the second LCP configuration. The bucket size duration for the logical channel may be longer in the first LCP configuration than in the second LCP configuration. The configuration may include combining Figure 4 and / or Figure 5 The configuration may be, for example, Fig. 9 The LCP configuration component 940 of the device 902 in the embodiment is executed and can be sent to the UE via the cellular RF transceiver of the device 902 by the sending component 934.

[0103] At 604, the base station instructs the UE to use the first LCP configuration for uplink transmission on the logical channel based on the first condition. The first condition may be based on an upper layer protocol state, a MAC level condition, etc. The indication may be, for example, Fig. 9 The first condition component 944 of the device 902 is executed and can be sent to the UE via the cellular RF transceiver of the device 902 by the sending component 934.

[0104] For example, as shown in 405, the base station may dynamically indicate (e.g., in a MAC-CE) the LCP configuration to be applied by the UE. The indication may include, for example, an LCID and one or more bits indicating activation of the first LCP configuration (or deactivation of the default LCP configuration) in response to the base station detecting the first condition. In another example, the base station may instruct the UE to use a second LCP condition in response to the UE detecting the second condition. For example, the base station may indicate the parameters of the second condition to the UE, and the UE may determine whether to apply the second LCP configuration. In some examples, such as Figure 5 As shown, the base station may provide the UE with parameters for the UE to autonomously select between the first and second LCP configurations.

[0105] At 606, the base station instructs the UE to use the second LCP configuration for uplink transmission on the logical channel, for example, during the second TCP phase. The indication may be, for example, by Fig. 9The second condition component 948 of the device 902 in the device 902 is executed and can be sent to the UE by the sending component 934 via the cellular RF transceiver of the device 902. For example, as shown in 417, the base station can dynamically indicate (for example, in the MAC-CE) the LCP configuration to be applied by the UE. The indication may include an LCID and one or more bits indicating the activation of the second LCP configuration (or the deactivation of the promoted LCP configuration). The second TCP phase may include a steady state phase. The first LCP configuration and the second LCP configuration can be configured in the RRC signaling, and for example, in response to the base station detecting the second condition, the base station can instruct the UE to use the first LCP configuration or the second LCP configuration in the MAC-CE. In another example, the base station may instruct the UE to use the second LCP condition in response to the UE detecting the second condition. For example, the base station may indicate the parameters of the second condition to the UE, and the UE may determine whether to apply the second LCP configuration.

[0106] The first condition and the second condition may be based on an upper layer protocol state. For example, the first condition may include a slow start phase of TCP, and the second TCP phase includes a steady state phase of TCP. In another example, at least one of the first condition or the second condition may be based on a QUIC condition or an Ethernet condition. In another example, the first condition and the second condition may be based on a MAC level condition.

[0107] As indicated at 608, the base station may receive an uplink transmission from the UE based on the first LCP configuration or the second LCP configuration. The reception may be performed, for example, by Fig. 9 The receiving component 930 of the apparatus 902 in the embodiment is performed, for example, via the cellular RF transceiver 922. For example, the base station may receive one or more TBs having a first LCP configuration, such as Figure 4 The base station may receive one or more TBs having a second LCP configuration, such as Figure 4 or Figure 5 As shown in 425 or 525.

[0108] Figure 6 Each box in the flowchart and / or Figure 4 or Figure 5 The various aspects of the base station execution in the process / algorithm may be performed by components of the base station device, which may include one or more of these components. The components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0109] In one configuration, the base station includes a Figure 6 The methods described and / or Figure 4 or Figure 5 Components for performing various aspects of the described methods may be one or more of a device configured to perform the functions described by these components and / or a component of a processing system of such a device. The processing system may include a transmit processor, a receive processor, and a controller / processor. Thus, in one configuration, the component may be a memory 376, a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions described by these components.

[0110] Figure 7 700 is a flow chart of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., UE 104, 350, 404, 504; apparatus 802; a processing system, which may include memory 360 and may be the entire UE 350 or a component of the UE 350, such as TX processor 368, RX processor 356, and / or controller / processor 359). Optional aspects are shown with dashed lines. The method enables the UE to more efficiently use radio resources and more efficiently communicate with a base station during different phases of TCP and / or based on different network conditions.

[0111] At 702, the UE receives a configuration of a first LCP configuration and a second LCP configuration for a logical channel. The first LCP configuration and the second LCP configuration include a MAC level LCP configuration. The UE may receive the first LCP configuration and the second LCP configuration for each logical channel from a base station. The first LCP configuration and the second LCP configuration each include one or more of a priority value for the logical channel, a priority bit rate for the logical channel, or a bucket size duration for the logical channel. The priority value for the logical channel may be a lower value indicating a higher priority level in the first LCP configuration than in the second LCP configuration. The priority bit rate for the logical channel may be higher in the first LCP configuration than in the second LCP configuration. The bucket size duration for the logical channel may be higher in the first LCP configuration than in the second LCP configuration. The configuration may include combining Figure 4 and / or Figure 5 The configuration may be received by any of 403, 407, 503, and 507. Figure 8 The LCP configuration component 840 of the device 802 in is performed, for example, via the receiving component 830 and / or the cellular RF transceiver 822.

[0112] At 704, the UE receives a first indication to configure a first LCP for uplink transmission on a logical channel based on a first condition. The receipt of the indication may be performed by Figure 8802 in the apparatus 802. In some aspects, the receiving may be performed via the receiving component 830 and / or the cellular RF transceiver 822. For example, as shown at 405, the UE may receive a dynamic indication (e.g., in a MAC-CE) of an LCP configuration for the UE application, for example, in response to the base station determining the occurrence of the first condition. The indication may include an LCID and one or more bits indicating activation of the first LCP configuration (or deactivation of the default LCP configuration). In some examples, as shown at 405, the UE may receive a dynamic indication (e.g., in a MAC-CE) of an LCP configuration for the UE application, for example, in response to the base station determining the occurrence of the first condition. Figure 5 As shown, the base station may provide the UE with parameters for the UE to autonomously select between the first and second LCP configurations. For example, the UE may receive parameters for switching between the first LCP configuration and the second LCP configuration from the base station. In this example, for example, based on the parameters for switching to the first LCP configuration, the first indication may indicate that the UE uses the first LCP configuration in response to the UE detecting the first condition, and the second indication may indicate that the UE uses the second LCP configuration in response to the UE detecting the second condition. In some examples, the first indication may be an autonomous determination at the UE based on UE information.

[0113] At 706, the UE may transmit a TB on a logical channel based on the first LCP configuration. The transmission may be performed, for example, by the logical channel component 846 via the transmission component 834 and / or the cellular RF transceiver 822. For example, the UE may transmit one or more ACKs for downlink data from the base station based on the parameters of the first LCP configuration, for example, as combined with Figure 4 and / or Figure 5 In other examples, the UE may be based on a combination of Figure 4 The aspects described above determine to switch. For example, the second indication can be a determination at the UE based on parameters for switching between the first LCP configuration and the second LCP configuration. In some examples, the second indication can be an autonomous determination at the UE based on UE information.

[0114] At 708, the UE receives a second indication that the UE uses the second LCP configuration for uplink transmission on the logical channel based on the second condition. The receipt of the indication may be performed by Figure 8802 in the device 804. In some aspects, the reception may be performed via the receiving component 830 and / or the cellular RF transceiver 822. For example, as shown at 417, the UE may receive a dynamic indication of an LCP configuration for the UE application (e.g., in a MAC-CE). The indication may include an LCID and one or more bits indicating activation of a second LCP configuration (or deactivation of an elevated LCP configuration). The first LCP configuration and the second LCP configuration may be configured in RRC signaling, and in response to the base station detecting the occurrence of the first condition or the second condition, the base station may indicate in the MAC-CE that the UE uses the first LCP configuration or the second LCP configuration. In another example, the second indication may indicate that the UE uses the second LCP configuration in response to the UE detecting the second condition. In yet another example, the second indication may be based on autonomously determining at the UE that the second condition has occurred and that the second LCP configuration will be applied.

[0115] The first condition and the second condition may be based on an upper layer protocol state. For example, the first condition may include a slow start phase of TCP, and the second TCP phase includes a steady state phase of TCP. In another example, at least one of the first condition or the second condition may be based on a QUIC condition or an Ethernet condition. In another example, the first condition and the second condition may be based on a MAC level condition.

[0116] As indicated at 712, the UE may transmit an uplink transmission based on the first LCP configuration or the second LCP configuration. The transmission may be performed, for example, by the logical channel component 846 via the transmission component 834 and / or the cellular RF transceiver 822.

[0117] For example, at 710, the UE may transmit a TB on a logical channel based on the second LCP configuration. The transmission may be performed, for example, by the logical channel component 846 via the transmission component 834 and / or the cellular RF transceiver 822. For example, the UE may transmit one or more ACKs for downlink data from the base station based on the parameters of the second LCP configuration, for example, as combined with Figure 4 and / or Figure 5 As described.

[0118] Figure 7 Each box in the flowchart and / or Figure 4 The various aspects of the UE execution in and / or 5 may be performed by components of the UE device that may include one or more of these components. The components may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0119] In one configuration, the base station includes a Figure 7 The methods described and / or Figure 4 and / or Figure 5 Components for performing various aspects of the methods described herein may be components configured to perform the functions described by these components and / or one or more of the components of the processing system of such a device. The processing system may include a transmit processor, a receive processor, and a controller / processor. Thus, in one configuration, the device may be a memory 360, such as a TX processor 368, an RX processor 356, and / or a controller / processor 359, which is configured to perform the functions described by these components.

[0120] Figure 8 800 is a diagram illustrating an example of a hardware implementation of an apparatus 802. The apparatus 802 may be a UE or a component of a UE and includes a cellular baseband processor 804 (also referred to as a modem) coupled to a cellular RF transceiver 822. In some aspects, the apparatus 802 may also include one or more subscriber identity modules (SIM) cards 820, an application processor 806 coupled to a secure digital (SD) card 808 and a screen 810, a Bluetooth module 812, a wireless local area network (WLAN) module 814, a global positioning system (GPS) module 816, and / or a power supply 818. The cellular baseband processor 804 communicates with the UE 104 and / or the BS 102 / 180 via the cellular RF transceiver 822. The cellular baseband processor 804 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 804 is responsible for overall processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 804, enables the cellular baseband processor 804 to perform various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 804 when executing software. The cellular baseband processor 804 also includes a receiving component 830, a communication manager 832, and a transmitting component 834. The communication manager 832 includes one or more of the components shown. The components within the communication manager 832 may be stored in the computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 804. The cellular baseband processor 804 may be a component of the UE 350 and may include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 802 may be a modem chip and include only the baseband processor 804, while in another configuration, the device 802 may be the entire UE (e.g., see Figure 3 350) and includes additional modules of device 802.

[0121] The communication manager 832 includes an LCP configuration component 840 configured to receive a configuration of a first LCP configuration and a second LCP configuration for a logical channel, for example, as combined Figure 7 The communication manager 832 also includes a first condition component 842 configured to receive a first indication of configuring a first LCP for uplink transmission on a logical channel based on a first condition, for example, as described in conjunction with Figure 7 The communication manager 832 also includes a second condition component 844, which is configured to receive a second indication of configuring a second LCP for uplink transmission on the logical channel based on a second condition, for example, as described in conjunction with Figure 7 The communication manager 832 also includes a logical channel component 846 configured to send an uplink transmission based on the first LCP configuration or the second LCP configuration, for example, as described in conjunction with any one of 706, 710, and / or 712.

[0122] The apparatus may include executing Figure 7 Each block of the algorithm in the flowchart and / or Figure 4 and / or additional components of various aspects performed by the UE in 5. Therefore, Figure 7 Each box in the flowchart and / or Figure 4 The various aspects performed by the UE in and / or 5 may be performed by components, and the apparatus may include one or more of those components. The component may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0123] In one configuration, the apparatus 802 (particularly the cellular baseband processor 804) includes means for receiving a configuration of a first LCP configuration and a second LCP configuration for a logical channel, for example, as combined with Figure 7 The apparatus 802 may also include a first indication for receiving a first LCP configuration for uplink transmission on a logical channel based on a first condition and a second indication for receiving a second LCP configuration for uplink transmission on a logical channel based on a second condition, for example, as described in conjunction with Figure 7The apparatus 802 may also include means for sending an uplink transmission based on the first LCP configuration or the second LCP configuration, for example, as described in conjunction with any of 706, 710, and / or 712. These means may be one or more components of the apparatus 802 configured to perform the functions recited by these means. As described herein, the apparatus 802 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by these means.

[0124] Fig. 9 900 is an example of a hardware implementation of an illustrated apparatus 902. Apparatus 902 may be a base station or a component of a base station and includes a baseband unit 904. Baseband unit 904 may communicate with UE 104 via a cellular RF transceiver 922. Baseband unit 904 may include a computer-readable medium / memory. Baseband unit 904 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by baseband unit 904, enables baseband unit 904 to perform various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by baseband unit 904 when executing the software. Baseband unit 904 also includes a receiving component 930, a communication manager 932, and a sending component 934. Communication manager 932 includes one or more of the components shown. Components within communication manager 932 may be stored in a computer-readable medium / memory and / or configured as hardware within baseband unit 904. The baseband unit 904 may be a component of the BS 310 and may include the memory 376 and / or at least one of the TX processor 316 , the RX processor 370 , and the controller / processor 375 .

[0125] The communication manager 932 includes an LCP configuration component 940 configured to configure a first LCP configuration and a second LCP configuration for a logical channel for a UE, for example, as combined with Figure 6 The communication manager 932 also includes a first condition component 944, which is configured to instruct the UE to use the first LCP configuration for uplink transmission on the logical channel based on the first condition, for example, as combined with Figure 6 The communication manager 932 also includes a second condition component 948, which is configured to instruct the UE to use a second LCP configuration for uplink transmission on the logical channel based on a second condition, for example, as described in conjunction with Figure 6The apparatus 902 may also include a receiving component 930 configured to receive an uplink transmission based on the first LCP configuration or the second LCP configuration, for example, as described in conjunction with Figure 6 As described in 608.

[0126] The apparatus may include executing Figure 6 Each of the blocks of the algorithm in the flowchart and / or by Figure 4 or 5. Thus, Figure 6 Each box in the flowchart and / or Figure 4 The various aspects performed by the base station in or 5 may be performed by components, and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0127] In one configuration, the apparatus 902 (particularly the baseband unit 904) includes means for configuring a first LCP configuration and a second LCP configuration for a logical channel for a UE, for example, as combined with Figure 6 The apparatus 902 may also include a component for instructing the UE to configure the first LCP for uplink transmission on the logical channel based on the first condition and instructing the UE to configure the second LCP for uplink transmission on the logical channel based on the second condition, for example, as combined with Figure 6 The apparatus 902 may also include a component for receiving an uplink transmission based on the first LCP configuration or the second LCP configuration, for example, as described in conjunction with 604 and / or 606. Figure 6 608 in . These means may be one or more components of the apparatus 902 configured to perform the functions recited by these means. As described above, the apparatus 902 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by these means.

[0128] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of an exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims present the elements of the various blocks in a sample order and are not meant to be limited to the specific order or hierarchy presented.

[0129] To enable any person skilled in the art to practice the various aspects described herein, a previous description is provided. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the language claims, wherein, unless otherwise specified, references to elements in the singular form are not intended to represent "one and only one", but to represent "one or more". The word "exemplary" is used herein to represent "used as an example, instance or illustration". Any aspect described herein as "exemplary" is not necessarily interpreted as being preferred or advantageous over other aspects. Unless otherwise specifically stated, the term "some" refers to one or more. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C" and "A, B, C or any combination thereof" include any combination of A, B and / or C, and may include multiples of A, multiples of B or multiples of C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements throughout the various aspects described in the present disclosure that are known or later to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recited in the claims. The words "module," "mechanism," "element," "device," and the like may not be substitutes for the word "unit." Therefore, no claim element is constructed as a means + function unless the element is explicitly described using the phrase "means for..."

[0130] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without being limited thereto.

[0131] Aspect 1 is a method for performing wireless communication at a base station, comprising: configuring a first LCP configuration and a second LCP configuration for a logical channel for a UE; instructing the UE to use the first LCP configuration for uplink transmission on the logical channel based on a first condition; and instructing the UE to use the second LCP configuration for uplink transmission on the logical channel based on a second condition.

[0132] In aspect 2, the method of aspect 1 further includes: the first condition and the second condition are based on an upper layer protocol state.

[0133] In aspect 3, the method of aspect 1 or aspect 2 further includes: the first condition includes a slow start phase of TCP, and the second condition includes a steady state phase of TCP.

[0134] In aspect 4, the method of any one of aspects 1-3 further includes: at least one of the first condition or the second condition is based on a QUIC condition or an Ethernet condition.

[0135] In aspect 5, the method of any one of aspects 1-3 further includes: the first condition and the second condition are based on a MAC level condition.

[0136] In aspect 6, the method of any one of aspects 1-5 further includes: the first LCP configuration and the second LCP configuration include MAC-level LCP configuration.

[0137] In aspect 7, the method of any one of aspects 1-6 further includes: the base station configuring multiple LCP configurations for each logical channel.

[0138] In aspect 8, the method of any one of aspects 1-7 further includes that the first LCP configuration and the second LCP configuration both include one or more of the following items: a priority value of a logical channel, a priority bit rate of a logical channel, or a bucket size duration of a logical channel.

[0139] In aspect 9, the method of aspect 8 further includes: the priority value of the logical channel is a lower value indicating a higher priority in the first LCP configuration than in the second LCP configuration.

[0140] In aspect 10, the method of aspect 8 further includes: the priority bit rate of the logical channel is higher in the first LCP configuration than in the second LCP configuration.

[0141] In aspect 11, the method of aspect 8 further includes: a bucket size duration of the logical channel is longer in the first LCP configuration than in the second LCP configuration.

[0142] In aspect 12, the method of any one of aspects 1-11 also includes: configuring a first LCP configuration and a second LCP configuration in RRC signaling, and wherein the base station instructs the UE to use the first LCP configuration in response to detecting the first condition, or instructs the UE to use the second LCP configuration in MAC-CE in response to detecting the second condition.

[0143] In aspect 13, the method of any one of aspects 1-12 further includes: the base station instructing the UE to use the first LCP configuration in response to the UE detecting the first condition, and instructing the UE to use the second LCP configuration in response to the UE detecting the second condition.

[0144] In aspect 14, the method of any one of aspects 1-13 further includes receiving an uplink transmission based on the first LCP configuration or the second LCP configuration.

[0145] Aspect 15 is an apparatus for performing wireless communication at a base station, comprising an apparatus for performing the method of any one of aspects 1-14.

[0146] Aspect 16 is an apparatus for wireless communication at a base station, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to execute the method according to any one of aspects 1-14.

[0147] Aspect 17 is a non-transitory computer-readable storage medium storing computer-executable code for wireless communication at a base station, which, when executed by a processor, causes the processor to perform the method according to any one of aspects 1-14.

[0148] Aspect 18 is a method for performing wireless communication at a UE, comprising: receiving a configuration of a first LCP configuration and a second LCP configuration for a logical channel; based on a first condition, receiving a first indication to use the first LCP configuration for uplink transmission on the logical channel; and based on a second condition, receiving a second indication to use the second LCP configuration for uplink transmission on the logical channel.

[0149] In aspect 19, the method of aspect 18 further comprises sending an uplink transmission based on the first LCP configuration or the second LCP configuration.

[0150] In aspect 20, the method of aspect 18 in aspect 19 further includes: the first condition and the second condition are based on an upper layer protocol state.

[0151] In aspect 21, the method of any one of aspects 18-20 further includes: the first condition includes a slow start phase of TCP, and the second condition includes a steady state phase of TCP.

[0152] In aspect 22, the method of any one of aspects 18-21 further includes: at least one of the first condition or the second condition is based on a QUIC condition or an Ethernet condition.

[0153] In aspect 23, the method of any one of aspects 18-21 further comprises: the first condition and the second condition are based on a MAC level condition.

[0154] In aspect 24, the method of any one of aspects 18-23 further comprises: the first LCP configuration and the second LCP configuration comprise MAC level LCP configurations.

[0155] In aspect 25, the method of any one of aspects 18-24 further includes: the UE receiving a plurality of LCP configurations for each logical channel.

[0156] In aspect 26, the method of any one of aspects 18-25 further includes the first LCP configuration and the second LCP configuration both including one or more of the following items: a priority value of a logical channel, a priority bit rate of a logical channel, or a bucket size duration of a logical channel.

[0157] In aspect 27, the method of aspect 26 further includes: the priority value of the logical channel is a lower value indicating a higher priority in the first LCP configuration than in the second LCP configuration.

[0158] In aspect 28, the method of aspect 26 further comprises: the priority bit rate of the logical channel is higher in the first LCP configuration than in the second LCP configuration.

[0159] In aspect 29, the method of aspect 26 further comprises: a bucket size duration of the logical channel is longer in the first LCP configuration than in the second LCP configuration.

[0160] In aspect 30, the method of any one of aspects 18-29 further comprises: receiving the first LCP configuration and the second LCP configuration in RRC signaling, and wherein, in response to the base station detecting the first condition or the second condition, receiving the first indication and the second indication through MAC-CE.

[0161] In aspect 31, the method of any one of aspects 18-30 further includes: in response to the UE detecting a first condition, a first indication instructing the UE to use a first LCP configuration, and in response to the UE detecting a second condition, a second indication instructing the UE to use a second LCP configuration.

[0162] In aspect 32, the method of any one of aspects 18-31 further includes: the first indication and the second indication are autonomously determined at the UE based on UE information.

[0163] Aspect 33 is an apparatus for wireless communication at a UE, comprising means for performing the method of any one of aspects 18-32.

[0164] Aspect 34 is an apparatus for wireless communication at a UE, comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to perform a method according to any one of aspects 18-32.

[0165] Aspect 35 is a non-transitory computer-readable storage medium storing computer-executable code for wireless communication at a UE, which, when executed by a processor, causes the processor to perform a method according to any one of aspects 18-32.

Claims

1. A network entity for wireless communication, comprising: Memory; as well as at least one processor coupled to a memory, wherein the network entity is configured to: providing a first logical channel prioritization LCP configuration and a second LCP configuration for a logical channel to a user equipment UE, the first LCP configuration comprising a first set of one or more parameters and a first set of one or more mapping restrictions for scheduling uplink data, the second LCP configuration comprising a second set of one or more parameters and a second set of one or more mapping restrictions for scheduling the uplink data; Instructing the UE at a first time based on a first condition to use the first set of one or more parameters for scheduling the uplink data based on the first LCP configuration for uplink transmission on the logical channel; as well as Instructing the UE at a second time based on a second condition to use the second set of one or more parameters for scheduling the uplink data based on the second LCP configuration for the uplink transmission on the logical channel.

2. The network entity according to claim 1, wherein: The first condition and the second condition are based on an upper layer protocol state.

3. The network entity according to claim 2, wherein: The first condition includes a slow start phase of a transmission control protocol TCP, and the second condition includes a steady state phase of the TCP.

4. The network entity according to claim 2, wherein: At least one of the first condition or the second condition is based on a corresponding QUIC condition or a corresponding Ethernet condition.

5. The network entity according to claim 1, wherein: The first condition and the second condition are based on a medium access control MAC level condition.

6. The network entity according to claim 1, wherein: The first LCP configuration and the second LCP configuration include medium access control MAC level LCP configuration.

7. The network entity according to claim 1, wherein: The network entity is configured to provide a plurality of LCP configurations for each logical channel.

8. The network entity according to claim 1, wherein: The first set of one or more parameters for scheduling the uplink data based on the first LCP configuration and the second set of one or more parameters for scheduling the uplink data based on the second LCP configuration each include one or more of the following: the corresponding priority value of the logical channel, the corresponding priority bit rate of the logical channel, or The corresponding bucket size duration of the logical channel.

9. The network entity according to claim 8, wherein: The first priority value of the logical channel in the first set of one or more parameters in the first LCP configuration for scheduling the uplink data is a lower value indicating a higher priority level compared to the second priority value of the logical channel in the second set of one or more parameters in the second LCP configuration for scheduling the uplink data.

10. The network entity according to claim 8, wherein: A first priority bit rate for the logical channel in the first set of one or more parameters for scheduling the uplink data in the first LCP configuration is higher than a second priority bit rate for the logical channel in the second set of one or more parameters for scheduling the uplink data in the second LCP configuration.

11. The network entity according to claim 8, wherein: The first set of one or more parameters in the first LCP configuration for scheduling the uplink data includes a first bucket size duration of the logical channel, and the first bucket size duration is longer than a second bucket size duration of the logical channel in the second set of one or more parameters in the second LCP configuration for scheduling the uplink data.

12. The network entity according to claim 1, wherein: To provide the first LCP configuration and the second LCP configuration, the network entity is configured to providing the first LCP configuration and the second LCP configuration in radio resource control RRC signaling, and In which, in order to instruct the UE to use the first LCP configuration based on detecting the first condition, or to instruct the UE to use the second LCP configuration based on detecting the second condition, the network entity is configured to instruct the UE to use the first LCP configuration or the second LCP configuration in the media access control-control element MAC-CE.

13. A method of wireless communication performed by a network entity, comprising: providing a first logical channel prioritization LCP configuration and a second LCP configuration for a logical channel to a user equipment UE, the first LCP configuration comprising a first set of one or more parameters and a first set of one or more mapping restrictions for scheduling uplink data, the second LCP configuration comprising a second set of one or more parameters and a second set of one or more mapping restrictions for scheduling the uplink data; Instructing the UE at a first time based on a first condition to use the first set of one or more parameters for scheduling the uplink data based on the first LCP configuration for uplink transmission on the logical channel; as well as Instructing the UE at a second time based on a second condition to use the second set of one or more parameters for scheduling the uplink data based on the second LCP configuration for the uplink transmission on the logical channel.

14. The method of claim 13, wherein: The first condition and the second condition are based on an upper layer protocol state, and the first condition includes a slow start phase of a transmission control protocol TCP, and the second condition includes a steady state phase of the TCP.

15. The method of claim 13, wherein: The first set of one or more parameters for scheduling the uplink data based on the first LCP configuration and the second set of one or more parameters for scheduling the uplink data based on the second LCP configuration each include one or more of the following: the corresponding priority value of the logical channel, the corresponding priority bit rate of the logical channel, or The corresponding bucket size duration of the logical channel.

16. An apparatus for wireless communication, comprising: Memory; as well as at least one processor coupled to the memory, wherein the apparatus is configured to: receiving a configuration of a first logical channel prioritization LCP configuration and a second LCP configuration for a logical channel, the first LCP configuration comprising a first set of one or more parameters and a first set of one or more mapping restrictions for scheduling uplink data, the second LCP configuration comprising a second set of one or more parameters and a second set of one or more mapping restrictions for scheduling the uplink data; receiving, based on a first condition, at a first time, a first indication to use the first set of one or more parameters for scheduling the uplink data based on the first LCP configuration for uplink transmission on the logical channel; receiving, based on a second condition, at a second time, a second indication to use the second set of one or more parameters for scheduling the uplink data based on the second LCP configuration for the uplink transmission on the logical channel; and An uplink transmission is sent based on the first set of one or more parameters for scheduling the uplink data based on the first LCP configuration or the second set of one or more parameters for scheduling the uplink data based on the second LCP configuration.

17. The device of claim 16, wherein: The first condition and the second condition are based on an upper layer protocol state.

18. The device of claim 17, wherein: The first condition includes a slow start phase of a transmission control protocol TCP, and the second condition includes a steady state phase of the TCP.

19. The device of claim 17, wherein: At least one of the first condition or the second condition is based on a corresponding QUIC condition or a corresponding Ethernet condition.

20. The device of claim 16, wherein: The first condition and the second condition are based on a Medium Access Control (MAC) level condition.

21. The apparatus of claim 16, wherein: The first LCP configuration and the second LCP configuration include medium access control MAC level LCP configuration.

22. The apparatus of claim 16, wherein: The apparatus is configured to receive a plurality of LCP configurations for each logical channel.

23. The apparatus of claim 16, wherein: The first set of one or more parameters for scheduling the uplink data based on the first LCP configuration and the second set of one or more parameters for scheduling the uplink data based on the second LCP configuration each include one or more of the following: the corresponding priority value of the logical channel, the corresponding priority bit rate of the logical channel, or The corresponding bucket size duration of the logical channel.

24. The device of claim 23, wherein: The first priority value of the logical channel in the first set of one or more parameters in the first LCP configuration for scheduling the uplink data is a lower value indicating a higher priority level compared to the second priority value of the logical channel in the second set of one or more parameters in the second LCP configuration for scheduling the uplink data.

25. The apparatus of claim 23, wherein: A first priority bit rate for the logical channel in the first set of one or more parameters for scheduling the uplink data in the first LCP configuration is higher than a second priority bit rate for the logical channel in the second set of one or more parameters for scheduling the uplink data in the second LCP configuration.

26. The apparatus of claim 23, wherein: The first set of one or more parameters in the first LCP configuration for scheduling the uplink data includes a first bucket size duration of the logical channel, and the first bucket size duration is longer than a second bucket size duration of the logical channel in the second set of one or more parameters in the second LCP configuration for scheduling the uplink data.

27. The apparatus of claim 16, wherein: In order to receive the first LCP configuration and the second LCP configuration, the device is configured to receive the first LCP configuration and the second LCP configuration in radio resource control RRC signaling, and, wherein, in order to receive the first indication and the second indication, the device is configured to receive the first indication and the second indication in a media access control-control element MAC-CE.

28. The apparatus of claim 16, wherein: The first indication and the second indication are autonomously determined at the device based on device information associated with the device.

29. A method for wireless communication performed by a user equipment UE, comprising: receiving a configuration of a first logical channel prioritization LCP configuration and a second LCP configuration for a logical channel, the first LCP configuration comprising a first set of one or more parameters and a first set of one or more mapping restrictions for scheduling uplink data, the second LCP configuration comprising a second set of one or more parameters and a second set of one or more mapping restrictions for scheduling the uplink data; receiving, based on a first condition, at a first time, a first indication to use the first set of one or more parameters for scheduling the uplink data based on the first LCP configuration for uplink transmission on the logical channel; receiving, based on a second condition, at a second time, a second indication to use the second set of one or more parameters for scheduling the uplink data based on the second LCP configuration for the uplink transmission on the logical channel; as well as An uplink transmission is sent based on the first set of one or more parameters for scheduling the uplink data based on the first LCP configuration or the second set of one or more parameters for scheduling the uplink data based on the second LCP configuration.

30. The method of claim 29, wherein: The first condition and the second condition are based on an upper layer protocol state, the first condition comprising a slow start phase of a transmission control protocol TCP, and the second condition comprising a steady state phase of the TCP.

31. A non-transitory computer-readable storage medium storing computer-executable code for wireless communication, the code, when executed by a processor, causing the processor to perform the method of any one of claims 13-15.

32. A non-transitory computer-readable storage medium storing computer-executable code for wireless communication, the code, when executed by a processor, causing the processor to perform the method of any one of claims 29-30.

Images