TW202324961A - Radio link control for mixed numerology standalone carrier aggregation - Google Patents

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a wireless communication device may establish a first carrier of a carrier aggregation (CA) configuration, wherein the first carrier is associated with a first configuration. The wireless communication device may establish a second carrier of the CA configuration, wherein the second carrier is associated with a second configuration different than the first configuration. The wireless communication device may receive information indicating a first set of radio link control (RLC) parameters for the first configuration and a second set of RLC parameters for the second configuration. The wireless communication device may perform an RLC function for a first communication on the first carrier using the first set of RLC parameters and for a second communication on the second carrier using the second set of RLC parameters. Numerous other aspects are described.

Description

Radio Link Control for Hybrid Digital Scheme Independent Carrier Aggregation

The various aspects of the subject matter of this case relate generally to wireless communications and to technical devices for radio link control for hybrid digital scheme independent carrier aggregation.

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging and broadcasting. A typical wireless communication system may adopt a multiple access technology capable of supporting communication with multiple users by sharing available system resources (eg, bandwidth, transmit power, etc.). Examples of such multiple access techniques 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, Access (OFDMA) system, single carrier frequency division multiple access (SC-FDMA) system, time division synchronous code division multiple access (TD-SCDMA) system and long-term evolution (LTE). LTE/LTE-Advanced (LTE-Advanced) is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile service standard promulgated by the 3rd Generation Partnership Project (3GPP).

A wireless network may include one or more base stations that support communication for a user equipment (UE) or multiple UEs. The UE can communicate with the base station via downlink communication and uplink communication. "Downlink" (or "DL") refers to the communication link from the base station to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the base station.

Such multiple access techniques have been adopted in various telecommunication standards to provide common protocols enabling different UEs to communicate on a municipal, national, regional or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile service standard published by 3GPP. NR is designed to better support mobile broadband Internet access by: increasing spectral efficiency; reducing cost, improving service, utilizing new spectrum, and using orthogonal cyclic prefix (CP) on the downlink Frequency Division Multiplexing (OFDM) (CP-OFDM), using CP-OFDM or Single Carrier Frequency Division Multiplexing (SC-FDM) on the uplink (also known as Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM) ), to better integrate with other open standards; also supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements to LTE, NR and other radio access technologies remain useful.

Some aspects described herein relate to methods of wireless communication performed by wireless communication devices. The method may include establishing a first carrier of a carrier aggregation (CA) configuration, wherein the first carrier is associated with the first configuration. The method may include establishing a second carrier of the CA configuration, wherein the second carrier is associated with a second configuration different from the first configuration. The method may include receiving information indicative of a first set of radio link control (RLC) parameters for the first configuration and a second set of RLC parameters for the second configuration. The method may include performing RLC functions for a first communication on the first carrier using the first set of RLC parameters. The method may include using the second set of RLC parameters to perform the RLC function for a second communication on the second carrier.

Some aspects described herein relate to wireless communication devices for wireless communication. A wireless communication device may include memory and one or more processors coupled to the memory. The one or more processors may be configured to establish a first carrier of a CA configuration, where the first carrier is associated with the first configuration. The one or more processors may be configured to establish a second carrier of the CA configuration, wherein the second carrier is associated with a second configuration different from the first configuration. The one or more processors may be configured to receive information indicative of a first set of RLC parameters for the first configuration and a second set of RLC parameters for the second configuration. The one or more processors may be configured to use the first set of RLC parameters to perform the RLC function for a first communication on the first carrier. The one or more processors may be configured to use the second set of RLC parameters to perform the RLC function for a second communication on the second carrier.

Some aspects described herein relate to a non-transitory computer readable medium storing a set of instructions for wireless communication by a wireless communication device. When executed by one or more processors of the wireless communication device, the set of instructions may cause the wireless communication device to establish a first carrier of a CA configuration, wherein the first carrier is associated with the first configuration. When executed by one or more processors of a wireless communication device, the set of instructions may cause the wireless communication device to establish a second carrier of the CA configuration, wherein the second carrier is associated with a second configuration different from the first configuration of. When executed by one or more processors of a wireless communication device, the set of instructions may cause the wireless communication device to receive information indicative of a first set of RLC parameters for the first configuration and a second set of RLC parameters for the second configuration . When executed by one or more processors of a wireless communication device, the set of instructions may cause the wireless communication device to use the first set of RLC parameters to perform RLC functions for a first communication on the first carrier. When executed by one or more processors of a wireless communication device, the set of instructions may cause the wireless communication device to use the second set of RLC parameters to perform the RLC function for a second communication on the second carrier.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for establishing a first carrier of a CA configuration, where the first carrier is associated with the first configuration. The apparatus can include means for establishing a second carrier of the CA configuration, wherein the second carrier is associated with a second configuration different from the first configuration. The apparatus may include means for receiving information indicative of a first set of RLC parameters for the first configuration and a second set of RLC parameters for the second configuration. The apparatus can include means for performing an RLC function for a first communication on the first carrier using the first set of RLC parameters. The apparatus can include means for performing the RLC function for a second communication on the second carrier using the second set of RLC parameters.

Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, wireless communication equipment and/or processing systems.

The foregoing has outlined rather broadly the features and technical advantages of examples according to the present disclosure so that the detailed description that follows may be better understood. Other features and advantages are described below. The conception and specific example disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the teachings herein. Such equivalent structures do not depart from the scope of the appended patent scope. The features of the concepts disclosed herein, both their organization and method of operation, and associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for purposes of illustration and description, not as a definition of the limits of the claims.

Although aspects have been described in this context by illustrating a few examples, those skilled in the art will understand that the aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes and/or packaging arrangements. For example, some aspects may be implemented via monolithic chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail/purchasing devices, medical devices, and/or artificial intelligence devices) to achieve. Aspects can be implemented in wafer-level components, modular components, non-modular components, non-wafer-level components, device-level components, or system-level components. Devices incorporating the described aspects and features may comprise additional elements and features for realizing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more elements for both analog and digital purposes (e.g., hardware elements including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processing adder, interleaver, adder and/or summer). It is contemplated that the aspects described herein can be practiced in a wide variety of devices, components, systems, distributed arrangements and/or end-user devices of different sizes, shapes and configurations.

Aspects of the subject matter of the present case are more fully described hereinafter with reference to the accompanying drawings. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or functionality presented throughout the present disclosure. Rather, such aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. One skilled in the art will understand that the scope of the subject matter is intended to cover any aspect of the subject matter disclosed herein, whether implemented alone or combined with any other aspect of the subject matter. For example, an apparatus may be implemented or a method practiced using any number of aspects set forth herein. Additionally, the scope of the subject matter is intended to cover such devices practiced with other structures, functions, or both, in addition to or not the aspects of the subject matter set forth herein or method. It should be understood that any aspect of the subject matter disclosed herein may be embodied through one or more elements of a claim.

Several aspects of a telecommunications system will now be presented with reference to various devices and technologies. These devices and methods will be described in the following detailed description and illustrated in the accompanying drawings via various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software or a combination thereof. Whether these elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

Although terms commonly associated with 5G or New Radio (NR) Radio Access Technologies (RATs) may be used herein to describe aspects, aspects of this disclosure may apply to other RATs such as 3G RATs, 4G RATs, and/or post-5G RATs (e.g., 6G)).

FIG. 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (NR) network and/or a 4G (eg, Long Term Evolution (LTE)) network, among others. Wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), user equipment (UE) 120, or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e) and/or other network entities. Base station 110 is an entity that communicates with UE 120 . Base stations 110 (sometimes referred to as BSs) may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, non-aggregated base stations One or more network nodes and/or transmit-receive points (TRPs) of the network. Each base station 110 can provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell service area" can refer to the coverage area of a base station 110 and/or the base station subsystems serving the coverage area, depending on the context in which the term is used.

The base station 110 may provide communication coverage for a macrocell service area, a picocell service area, a femtocell service area, and/or another type of cell service area. A macrocell service area may cover a relatively large geographic area (eg, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscription. A picocell service area may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell service area may cover a relatively small geographic area (e.g., a home) and may allow UEs 120 (e.g., UEs 120 in a Closed Subscriber Group (CSG)) to have an association with the femtocell service area. restricted access. The base station 110 used in the macro cell service area may be called a macro base station. A base station 110 for a picocell service area may be referred to as a pico base station. A base station 110 for a femto cell service area may be called a femto base station or a home base station. In the example shown in FIG. 1, BS 110a may be a macro base station for macrocell service area 102a, BS 110b may be a pico base station for picocell service area 102b, and BS 110c may be a A femto base station in the femtocell service area 102c. A base station can support one or more (eg, three) cell service areas.

In some instances, the cellular service area may not necessarily be stationary, and the geographic area of the cellular service area may move depending on the location of the mobile base station (eg, mobile base station). In some examples, the base stations 110 may use any suitable transmission network to interconnect with each other and/or communicate with each other in the wireless network 100 via various types of backhaul interfaces (for example, direct physical connections, or virtual networks). One or more other base stations 110 or network nodes (not shown) are interconnected.

Wireless network 100 may include one or more relay stations. A relay station is an entity that may receive data transmissions from upstream stations (eg, base station 110 or UE 120) and send data transmissions to downstream stations (eg, UE 120 or base station 110). A relay station may be a UE 120 capable of relaying transmissions for other UEs 120 . In the example shown in FIG. 1, BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. A base station 110 that can relay communications may be referred to as a relay station, relay base station, relay, or the like.

The wireless network 100 may be a heterogeneous network including different types of base stations 110 (such as macro base stations, pico base stations, femto base stations, relay base stations, etc.). The different types of base stations 110 may have different transmit power levels, different coverage areas, and/or different effects on interference in the wireless network 100 . For example, macro base stations may have high transmit power levels (e.g., 5 to 40 watts), while pico, femto, and relay base stations may have lower transmit power levels (e.g., 0.1 to 40 watts). 2 watts).

A network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110 . The network controller 130 can communicate with the base station 110 via the backhaul communication link. The base stations 110 may also communicate directly or indirectly with each other via wireless or wired backhaul communication links.

UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, terminal, mobile station, and/or subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop, a wireless phone, a wireless local loop (WLL) station, a tablet devices, cameras, gaming devices, small laptops, smart computers, ultrabooks, medical devices, biometric devices, wearable devices (e.g., smart watches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings or smart bracelets, etc.), entertainment equipment (such as music equipment, video equipment, and/or satellite radio units), vehicle components or sensors, smart instruments/sensors, industrial manufacturing equipment, global positioning systems device and/or any other suitable device configured to communicate via a wireless medium.

Some UEs 120 may be considered machine type communication (MTC) UEs or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and/or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and/or location tags, which may communicate with a base station, another device (e.g., a remote device) or communicate with some other entity. Some UEs may be considered Internet of Things (IoT) devices, and/or may be implemented as NB-IoT (Narrow Band IoT) devices. Some UEs may be considered customer premise equipment. The UE 120 may be included inside a housing housing elements of the UE 120 such as processor elements and/or memory elements. In some instances, processor elements and memory elements may be coupled together. For example, a processor element (eg, one or more processors) and a memory element (eg, a memory) may be operatively, communicatively, electrically and/or electrically coupled.

In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, an air interface, or the like. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

In some examples, two or more UEs 120 (eg, shown as UE 120a and UE 120e ) may communicate directly using one or more sidelink channels (eg, without using base station 110 as a communication channel for each other). intermediary for communication). For example, UE 120 may use peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocol (for example, which may include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, Vehicle to Pedestrian (V2P) protocol), and/or mesh network etc. for communication. In such instances, UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by base station 110 .

The devices of the wireless network 100 can communicate using the electromagnetic spectrum, and the electromagnetic spectrum can be subdivided into various categories, frequency bands, channels, etc. by frequency or wavelength. For example, the devices of the wireless network 100 may use one or more operating frequency bands for communication. In 5G NR, two initial operating frequency bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that FR1 is often (interchangeably) referred to in various documents and articles as the "Sub-6 GHz" frequency band, although a portion of FR1 is greater than 6 GHz. There is sometimes a similar nomenclature issue with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in various documents and articles, but is distinct from the super High frequency (EHF) frequency band (30 GHz–300 GHz).

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have determined the operating band for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz–24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, the three upper operating frequency bands are identified as frequency range designations FR4a or FR4-1 (52.6 GHz–71 GHz), FR4 (52.6 GHz–114.25 GHz) and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands belongs to the EHF frequency band.

With the above examples in mind, and unless specifically stated otherwise, it should be understood that the term "sub-6 GHz", etc., if used herein, may refer broadly to frequencies less than 6 GHz, may be within FR1, or may include mid-band frequencies . In addition, unless specifically stated otherwise, it should be understood that the term "millimeter wave", etc. (if used herein) can broadly refer to frequencies that can include mid-band frequencies, which can be found in FR2, FR4, FR4-a or FR4-1 and/or Or within FR5, or could be within the EHF band. It is contemplated that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and/or FR5) may be modified and that the techniques described herein are applicable to such modifications frequency range.

In some aspects, a wireless communication device (such as UE 120 or BS 110 or a network node that is not a converged base station) may include a communication manager 140 . As described in detail elsewhere herein, the communications manager 130 may: establish a first carrier of a carrier aggregation (CA) configuration, wherein the first carrier is associated with a first digital scheme; establish a second carrier of a CA configuration, wherein the first The two carriers are associated with a second bit scheme different from the first bit scheme; reception indicates a first set of radio link control (RLC) parameters for the first bit scheme and a second set of RLC parameters for the second bit scheme information; use the first set of RLC parameters to perform the RLC function for the first communication on the first carrier; and use the second set of RLC parameters to perform the RLC function for the second communication on the second carrier. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

As noted above, Figure 1 is provided as an example. Other examples may differ from the example described with respect to FIG. 1 .

FIG. 2 is a diagram illustrating an example 200 of communication between a base station 110 and a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas ( T ≧1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas ( R ≧1).

At base station 110 , transmit processor 220 may receive data intended for UE 120 (or group of UEs 120 ) from data source 212 . Transmit processor 220 may select one or more modulation and coding schemes (MCSs) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120 . Base station 110 may process (eg, encode and modulate) data for each UE 120 based at least in part on the MCS selected for that UE and may provide data symbols to UE 120 . The transmit processor 220 may process system information (eg, for semi-static resource partitioning information (SRPI)) and control information (eg, CQI requests, grants, and/or upper layer signaling), and provide management overhead symbols and control symbols. Transmit processor 220 may generate signals for reference (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS) ) reference symbol. A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on data symbols, control symbols, administrative burden symbols, and/or reference symbols, as applicable, and may provide a A corresponding set of data machines 232 (eg, T data machines) of the modems 232a through 232t provides a set of output symbol streams (eg, T output symbol streams). For example, each output symbol stream may be provided to a modulator element (shown as MOD) of data engine 232 . Each data engine 232 may use a corresponding modulator element to process a corresponding output symbol stream (eg, for OFDM) to obtain an output sample stream. Each modem 232 may further use a corresponding modulator element to process (eg, analog convert, amplify, filter, and/or upconvert) the output sample stream to obtain a downlink signal. The data sets 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas), shown as antennas 234a through 234t, respectively.

At UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from base station 110 and/or other base stations 110 and may transmit downlink signals to a set of antennas shown as data sets 254a through 254r, respectively. Modems 254 (eg, R modems) provide a set of received signals (eg, R received signals). For example, each received signal may be provided to a demodulator element (shown as DEMOD) of modem 254 . Each modem 254 may use a corresponding demodulator element to condition (eg, filter, amplify, down convert, and/or digitize) the received signal to obtain input samples. Each modem 254 may employ demodulator elements to further process the input samples (eg, for OFDM) to obtain received symbols. MIMO detector 256 may obtain received symbols from modem 254, may perform MIMO detection on the received symbols (if applicable), and may provide detected symbols. Receive processor 258 may process (e.g., demodulate and decode) detected symbols, may provide decoded data for UE 120 to data slot 260, and may provide decoded control information to controller/processor 280 and system information. The term "controller/processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, and/or a CQI parameter. In some examples, one or more elements of UE 120 may be included in housing 284 .

The network controller 130 may include a communication unit 294 , a controller/processor 290 and a memory 292 . The network controller 130 may include one or more devices in the core network, for example. The network controller 130 can communicate with the base station 110 via the communication unit 294 .

One or more antennas (e.g., antennas 234a-234t and/or antennas 252a-252r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more The antenna array, etc., may be included in one or more antenna panels, one or more antenna groups, one or more antenna element sets, and/or one or more antenna arrays. Antenna panels, antenna groups, sets of antenna elements, and/or antenna arrays may include one or more antenna elements (within a single enclosure or multiple enclosures), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and/or coupled to One or more antenna elements of one or more transmit and/or receive elements, such as the one or more elements of FIG. 2 .

On the uplink, at UE 120, transmit processor 264 may receive and process data from data source 262 and control information from controller/processor 280 (e.g., for information including RSRP, RSSI, RSRQ, and/or CQI report). Transmit processor 264 may generate reference symbols for one or more reference signals. Symbols from transmit processor 264 may be precoded by TX MIMO processor 266 (if applicable), further processed by data engine 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110 . In some examples, modem 254 of UE 120 may include a modulator and a demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252 , modem 254 , MIMO detector 256 , receive processor 258 , transmit processor 264 and/or TX MIMO processor 266 . The transceiver may be used by a processor (eg, controller/processor 280 ) and memory 282 to perform aspects of any of the methods described herein (eg, see FIGS. 3-11 ).

At base station 110, uplink signals from UE 120 and/or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator element of modem 232 shown as DEMOD), transmitted by MIMO The detector 236 detects (if applicable), and is further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120 . Receive processor 238 may provide decoded data to data slot 239 and may provide decoded control information to controller/processor 240 . The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244 . The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communication. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, base station 110 includes a transceiver. The transceiver may include any combination of antenna 234 , modem 232 , MIMO detector 236 , receive processor 238 , transmit processor 220 and/or TX MIMO processor 230 . The transceiver may be used by a processor (eg, controller/processor 240 ) and memory 242 to perform aspects of any of the methods described herein (eg, see FIGS. 3-11 ).

controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other element of FIG. 2 may perform one or more techniques associated with split RLC functionality for carrier aggregation, As described in more detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other element of FIG. 2 may perform or direct, for example, process 800 of FIG. 8 and/or other components described herein. operation of the process. The memory 242 and the memory 282 can respectively store data and program codes of the base station 110 and the UE 120 . In some examples, memory 242 and/or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (eg, code and/or program code) for wireless communication. For example, when executed by one or more processors of base station 110 and/or UE 120 (e.g., directly, or after compiling, converting, and/or interpreting), one or more instructions may cause one or more Multiple processors, UE 120 and/or base station 110 perform or direct operations such as process 800 of FIG. 8 and/or other processes described herein. In some examples, executing instructions may include executing instructions, converting instructions, compiling instructions and/or interpreting instructions, and the like.

In some aspects, a wireless communication device (e.g., UE 120, BS 110, network node of a non-aggregated base station) includes means for establishing a CA-configured first carrier, wherein the first carrier is associated with the first digital Scheme-associated; means for establishing a second carrier of a CA configuration, wherein the second carrier is associated with a second digit scheme different from the first digit scheme; for receiving a first digit scheme indicating the first digit scheme means for a set of RLC parameters and information on a second set of RLC parameters for a second digit scheme; means for performing an RLC function using the first set of RLC parameters for a first communication on a first carrier; and/or with means for performing an RLC function for a second communication on a second carrier using a second set of RLC parameters. In some aspects, components for a wireless communication device to perform the operations described herein may include, for example, communication manager 140, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receiver One or more of processor 238 , controller/processor 240 , memory 242 or scheduler 246 . In some aspects, components for a wireless communication device to perform the operations described herein may include, for example, communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO One or more of processor 266 , controller/processor 280 or memory 282 .

Although the blocks in FIG. 2 are shown as different components, the above-mentioned functions related to the blocks may be implemented in a single hardware, software, or combination of components, and may also be implemented in various combinations of components. For example, functionality described with respect to transmit processor 264 , receive processor 258 and/or TX MIMO processor 266 may be performed by or under the control of controller/processor 280 .

As noted above, Figure 2 is provided as an example. Other examples may differ from the example described with respect to FIG. 2 .

Deployments of communication systems such as 5G NR systems can be arranged in a variety of ways with various elements or components. In a 5G NR system or network, a network node, network entity, mobile element of the network, radio access network (RAN) node, core network node, network element, base station or network equipment may Implemented in aggregated or non-aggregated architecture. For example, a base station (such as NB, eNB, NR BS, 5G NB, gNB, AP, TRP, or cell service area) or one or more units (or one or more elements) performing base station functions can be implemented as an aggregated Base stations (also known as stand-alone base stations or monolithic base stations) or non-aggregated base stations. A "network entity" or "network node" may refer to a non-aggregated base station, or to one or more units of a non-aggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or its combination). An aggregated base station may be configured to utilize a stack of radio protocols that are physically or logically integrated within a single RAN node (eg, within a single device or unit). A non-aggregated base station may be configured to utilize a stack of agreements that are physically or logically distributed between two or more units, such as one or more CUs, one or more DUs, or one or more RUs. In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed among one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit (eg, a virtual central unit (VCU), virtual distributed unit (VDU), or virtual radio unit (VRU)).

Base station type operations or network design may take into account the aggregation nature of base station functions. For example, in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations sponsored by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN , also known as Cloud Radio Access Network (C-RAN)) utilizes non-aggregated base stations to facilitate scaling of communication systems by separating base station functions into one or more units that can be deployed independently . A non-aggregated base station may include functions implemented on two or more units at different physical locations, and functions implemented virtually on at least one unit, so that flexibility in network design can be achieved. For example, a first set of protocol functions may be implemented at the CU, a second set of protocol functions may be implemented at the DU, and a third set of protocol functions may be implemented at the RU. Functional separation may indicate which agreed upon functions are implemented at a CU, DU or RU. In one example, Packet Data Convergence Protocol (PDCP) functionality may be implemented at the CU, but other functional separations may be used (e.g., a functional separation in which both PDCP functionality and RLC functionality are implemented at the CU, Functional separation of both PDCP functions and RLC functions is achieved, functional separation in which CU and DU are co-located). Each unit of a non-aggregated base station may be configured to be in wired or wireless communication with at least one other unit of a non-aggregated base station.

3 is a diagram illustrating an example 300 of a user plane protocol stack and a control plane protocol stack for base station 110 and core network to communicate with UE 120 according to the present disclosure.

On the user plane, UE 120 and BS 110 may include respective physical (PHY) layer, medium access control (MAC) layer, RLC layer, PDCP layer and service data adaptation protocol (SDAP) layer. The user plane function can handle the transmission of user data between UE 120 and BS 110 . On the control plane, UE 120 and BS 110 may include respective Radio Resource Control (RRC) layers. Additionally, UE 120 may include a non-NAS layer in communication with the Access Stratum (NAS) layer of the Access and Management Mobility Function (AMF). The AMF may be associated with a core network such as a 5G Core Network (5GC) or a Next Generation Radio Access Network (NG-RAN) associated with the BS 110 . The control plane function can handle the transmission of control information between the UE and the core network. In general, a first layer is said to be higher than a second layer if the first layer is farther from the PHY layer than the second layer. For example, the PHY layer may be called the lowest layer, and the SDAP/PDCP/RLC/MAC layer may be called higher than the PHY layer and lower than the RRC layer. The application (APP) layer not shown in Figure 3 may be higher than the SDAP/PDCP/RLC/MAC layer. In some cases, entities may handle services and functions of a given layer (eg, a PDCP entity may handle services or functions of a PDCP layer), but the description herein refers to the layers themselves as handling services and functions.

The RRC layer can handle communications related to configuration and operation of UE 120, such as: broadcasting system information related to Access Stratum (AS) and NAS; paging initiated by 5GC or NG-RAN; RRC connection between UE and NG-RAN establishment, maintenance and release, including addition, modification and release of carrier aggregation, and addition, modification and release of dual connectivity; security functions, including key management; signaling radio bearers (SRBs) and data radio bearers (DRBs) Establishment, configuration, maintenance and release; mobility functions (e.g. handover and context transfer, UE cell service area selection and reselection and control of cell service area selection and reselection, inter-RAT mobility); quality of service (QoS) Management functions; UE measurement reporting and control of reporting; detection of and recovery from radio link failures; NAS message transfer between the NAS layer and lower layers of the UE 120 . The RRC layer is generally referred to as Layer 3 (L3).

The SDAP layer, PDCP layer, RLC layer, and MAC layer may be collectively referred to as Layer 2 (L2). Therefore, SDAP, PDCP, RLC, and MAC layers are referred to as sublayers of layer 2 in some cases. On the sending side (eg, if UE 120 is sending uplink traffic or BS 110 is sending downlink traffic), the SDAP layer may receive data streams in the form of QoS streams. A QoS flow is associated with a QoS identifier and a QoS flow identifier (QFI). The QoS identifier identifies the QoS parameters associated with the QoS flow. The QoS flow identifier (QFI) identifies the QoS flow. Policy and charging parameters are enforced at the granularity of QoS flows. A QoS Flow may consist of one or more Service Data Flows (SDFs), as long as each SDF of the QoS Flow is associated with the same policy and charging parameters. In some aspects, the RRC/NAS layer can generate control information to be sent, and can map the control information to one or more radio bearers for provision to the PDCP layer.

SDAP layer or RRC/NAS layer can map QoS flows or control information to radio bearers. Therefore, it can be said that the SDAP layer handles the QoS flow on the sending side. The SDAP layer can provide QoS flows to the PDCP layer via corresponding radio bearers. The PDCP layer can map radio bearers to RLC channels. The PDCP layer handles various services and functions on the user plane, including sequence numbering, header compression and decompression (if robust header compression is enabled), transmission of user data, reordering, and duplicate detection (if required In-sequence delivery to layers above the PDCP layer), PDCP Protocol Data Unit (PDU) routing (in case of split bearers), retransmission of PDCP Service Data Units (SDUs), encryption and decryption, PDCP SDU discarding (eg, based on timers, as described elsewhere herein), PDCP re-establishment and data recovery for RLC Acknowledged Mode (AM), and replication of PDCP PDUs. The PDCP layer can handle similar services and functions on the control plane, including sequence numbering, encryption, decryption, integrity protection, transmission of control plane data, duplicate detection, and replication of PDCP PDUs.

The PDCP layer may provide data in the form of PDCP PDUs to the RLC layer via the RLC channel. The RLC layer can handle transmission of upper layer PDUs to the MAC and/or PHY layer, sequence numbering independent of PDCP sequence numbering, error correction via Automatic Repeat Request (ARQ), segmentation and re-segmentation, SDU reassembly, RLC SDU discarding and RLC reconstruction.

The RLC layer may provide the MAC layer with data mapped to logical channels. Services and functions of the MAC layer include mapping between logical lanes and transport lanes (used by the PHY layer as described below), multiplexing/demultiplexing to/from MAC SDUs belonging to one or different logical lanes on transport lanes Transport Block (TB) delivered to/from physical layer, scheduling information reporting, error correction via Hybrid ARQ (HARQ), prioritization between UEs via dynamic scheduling, prioritization in a Priority management and stuffing are performed between the logical channels of the UE.

The MAC layer can encapsulate data from logical lanes into transport blocks (TBs), and can provide TBs on one or more transport lanes to the PHY layer. The PHY layer may handle various operations related to the transmission of data signals, as described in more detail in connection with FIG. 2 . The PHY layer is often referred to as Layer 1 (L1).

On the receiving side (eg, if UE 120 is receiving downlink communications or BS 110 is receiving uplink communications), operations may be similar to those described for the transmitting side, but reversed. For example, the PHY layer may receive the TB and may provide the TB to the MAC layer on one or more transport lanes. The MAC layer can map transport channels to logical channels, and can provide data to the RLC layer via the logical channels. The RLC layer may map logical channels to RLC channels, and may provide data to the PDCP layer via the RLC channels. The PDCP layer can map RLC channels to radio bearers and can provide data to the SDAP layer or the RRC/NAS layer via the radio bearers.

Data can be passed between layers in the form of PDUs and SDUs. SDUs are data units passed from a layer or sublayer to lower layers. For example, the PDCP layer may receive PDCP SDUs. A given layer can then encapsulate the data units into PDUs, and the PDUs can be passed to lower layers. For example, the PDCP layer may encapsulate PDCP SDUs into PDCP PDUs and may deliver the PDCP PDUs to the RLC layer. The RLC layer may receive PDCP PDUs as RLC SDUs, may encapsulate RLC SDUs as RLC PDUs, and so on. In fact, PDUs carry SDUs as payload. According to the techniques described herein, a PDCP PDU may be delivered to one of multiple RLC entities of the RLC layer, where each RLC entity is associated with a respective carrier or set of carriers. For example, a PDCP Control PDU (ie, a PDCP PDU carrying control information) may be delivered to or received from a selected RLC entity (eg, a preferred RLC entity) among a plurality of RLC entities. The selected RLC entity may be an RLC entity that performs RLC functions for PDCP control PDUs. In some aspects, traffic may be split among multiple RLC entities. For example, a PDCP entity at the PDCP layer may deliver traffic to (or receive traffic from) multiple RLC entities in conjunction with radio bearers such as signaling radio bearers or data radio bearers. Hence, communications associated with different RLC entities may be associated with the same radio bearer.

The RLC layer can work in Acknowledged Mode (AM), Unacknowledged Mode (UM) or Transparent Mode (TM). In AM, buffering is performed at the transmitter and receiver. Segmentation is performed at the transmitter and reassembly is performed at the receiver. Feedback mechanisms including acknowledgment (ACK) or negative ACK (NACK) are used for communication (such as RLC PDU or RLC SDU). AM can be used for certain signaling radio bearers (such as SRB1, SRB2 and SRB3) and data radio bearers. The sequence numbers that can be used for reassembly and recovery in AM can be selected from 12-bit size or 18-bit size. In UM, buffering is performed at the transmitter and receiver, segmentation is performed at the transmitter, and reassembly is performed at the receiver, and no feedback mechanism is used. In TM, no RLC header is used, only caching is performed at the transmitter, no segmentation or reassembly is performed, and no feedback mechanism is used.

The RLC transmitter in the AM can perform packet segmentation and concatenation. The RLC transmitter can add an RLC header to the packet. The RLC transmitter can provide RLC PDUs with RLC headers to the MAC layer. The RLC transmitter can also buffer RLC PDUs in case of NACK from the RLC receiver. If the RLC transmitter receives a NACK for a period of time, the RLC transmitter may trigger retransmission of the buffered RLC PDUs.

The RLC transmitter can use a transmit window to limit the number of RLC SDUs transmitted while waiting for an acknowledgment from the RLC receiver. The transmit window may start with the earliest transmitted RLC SDU that has not yet been fully acknowledged. The earliest transmitted RLC SDU may have been partially acknowledged if fragmented before transmission. When an acknowledgment is received, the launch window advances. The size of the transmit window is limited by the sequence number (SN) range. The transmit window is used to prevent SN ambiguity at the RLC receiver. The length of the SN is configured using RRC parameters.

The RLC transmitter may request a status report from the RLC receiver, such as based at least in part on a number of PDUs sent since a previous request, or an amount of data since a previous request. The RLC parameter pollPDU may indicate the number of PDUs sent since the previous request, and the RLC parameter pollByte may indicate the amount of data since the previous request. If the RLC transmitter requests but does not receive a status report after waiting the time period defined by the RLC parameter t-PollRetransmit, the RLC transmitter may retransmit the request. The status report may identify the SNs to which all RLC SDUs have been successfully received, in addition to the RLC SDUs specified in the remainder of the status report. The status report may indicate retransmission of a complete RLC SDU, or may indicate retransmission of one or more segments of an RLC SDU.

If the RLC PDU is within the receive window, the RLC receiver in the AM can buffer the received RLC PDU (called AM Data (AMD) PDU), remove the RLC header, and perform reassembly. In AM, the RLC receiver can provide feedback on the reception of RLC PDUs. In AM, each RLC PDU can be sent with SN in ascending order. AM supports Automatic Repeat Request (ARQ). The RLC receiver may send a status PDU (sometimes called a status message or status report) to indicate the status of the RLC PDU at the RLC receiver. The Status PDU may indicate which RLC PDU SNs were not received by the RLC receiver. For example, an RLC receiver may use a reassembly timer t-reassembly (defined by RLC parameters). When a segment of an SDU is received and multiple segments of the SDU are pending (eg, if one or more SNs in the SDU are lost), the RLC receiver may start a reassembly timer. Once the SDU is fully received, the RLC receiver can stop the reassembly timer. If the reassembly timer expires without receiving the missing one or more SNs, the RLC receiver may send a status report indicating one or more segments of the SDU that were not received. For example, the RLC receiver may wait the length of the reassembly timer (hoping that a Hybrid ARQ (HARQ) mechanism will enable retransmission of the lost SN(s) via retransmission to provide recovery).

As before, FIG. 3 is provided as an example. Other examples may differ from the example described with respect to FIG. 3 .

FIG. 4 is a diagram illustrating an example 400 of carrier aggregation in accordance with the teachings of the present disclosure.

Carrier aggregation is a technique that enables two or more component carriers (CCs, sometimes referred to as carriers) to be combined (eg, into a single channel) for a single UE 120 to enhance data capacity. As shown, carriers may be combined in the same or different frequency bands. Additionally or alternatively, contiguous or non-contiguous carriers may be combined. The base station 110 may configure carrier aggregation for the UE 120, such as in an RRC message, downlink control information (DCI), and/or another signaling message.

As indicated by reference numeral 405, in some aspects, carrier aggregation may be configured in an in-band contiguous mode, where the aggregated carriers are adjacent to each other and in the same frequency band. As indicated by reference numeral 410, in some aspects, carrier aggregation may be configured in an in-band non-contiguous mode, wherein the aggregated carriers are not contiguous with each other and in the same frequency band. As indicated by reference numeral 415, in some aspects, carrier aggregation may be configured in an inter-band non-contiguous mode, where the aggregated carriers are not contiguous with each other and are in different frequency bands.

In carrier aggregation, UE 120 may be configured with a primary carrier or primary cell service area (PCell) and one or more secondary carriers or secondary cell service areas (SCells). In some aspects, the primary carrier may carry control information (eg, downlink control information and/or scheduling information) for scheduling data communications on one or more secondary carriers, which may be referred to as cross-carrier schedule. In some aspects, a carrier (eg, a primary carrier or a secondary carrier) may carry control information for scheduling data communications on the carrier itself, which may be referred to as self-carrier scheduling or carrier self-scheduling.

In some aspects, carrier aggregation may be used across multiple bit schemes. The carrier may be configured in a bit scheme, which may be denoted by the index µ. The bit scheme may indicate the sub-carrier spacing (SCS) of the carrier in the frequency domain as well as other parameters such as cyclic prefix length. SCS can be used to export the frequency-domain bandwidth and time-domain duration of resource elements. In some aspects, a first carrier configured with carrier aggregation may have a first bit scheme (corresponding to a first SCS), and a second carrier configured with carrier aggregation may have a second bit scheme (corresponding to a second SCS). In some aspects, different bit schemes (defined elsewhere herein) may be used in different frequency ranges. For example, FR1 can generally be associated with digit schemes µ=0, 1, and 2 (corresponding to SCS at 15 kHz, 30 kHz, and 60 kHz, respectively), while FR2 can generally be associated with digit schemes µ=2, 3, and 4 (corresponding to 60 kHz, 120 kHz, and 240 kHz SC) are associated. Carrier aggregation can be used for carriers in different frequency ranges, such as the first set of carriers in FR1 (associated with a number scheme in the range µ=0, 1 and 2) and the second set of carriers in FR2 (with µ = associated with number schemes in the range 2, 3 and 4).

As before, FIG. 4 is provided as an example. Other examples may differ from the example described with respect to FIG. 4 .

As mentioned above, the BS and UE can perform various RLC functions for communication between the BS and UE. The RLC function is described in conjunction with Figure 3. In some implementations, the BS and UE can communicate using multiple carriers associated with different bit schemes. As an example, a BS and a UE may communicate in carrier aggregation using a first set of carriers in a first frequency range and a second set of carriers in a second frequency range, where the first set of carriers uses a first bit scheme and the second set of carriers uses a second bit scheme. The group carrier uses a second bit scheme different from the first bit scheme.

RLC functions may be performed according to a set of RLC parameters, which are described in more detail elsewhere herein. The set of RLC parameters may identify timers and thresholds for various RLC functions, such as recovery from one or more lost SNs (sometimes called reassembly) at the RLC receiver. A set of RLC parameters suitable for a first digital scheme may not be suitable for a second digital scheme. For example, a recombination timer for a 15 kHz SCS might be suitable for a longer length (due to the longer slot length of a 15 kHz SCS), while a recombination timer for a 120 kHz SCS might be suitable for a shorter length (because of the 120 kHz SCS shorter slot length). In this example, the RLC receiver can conservatively use the set of parameters for the smaller SCS (eg, 15 kHz) so that the communication of the smaller SCS can be properly handled. However, due to the increased bandwidth at larger SCSs (eg, 120 kHz), using this set of parameters for smaller SCSs may result in significant resource usage associated with buffering and processing traffic for larger SCSs. Furthermore, no matter how many sets of RLC parameters are configured, a single RLC entity (i.e., a single entity implementing the RLC functions of FIG. reconfiguration timer). Similar issues can arise for carriers associated with different configurations, such as different numbering schemes, different duplex configurations (e.g. time-division duplex vs. frequency-division duplex), different scheduling delays, different frequency ranges (eg FR1 vs. FR2) or different uplink/downlink slot assignments for time-division duplex carriers. This may result in significant resource usage, delays in RLC functions, reduced throughput, and reduced communication reliability.

Some of the techniques and devices described herein use multiple RLC entities to provide communication in multiple bit schemes. For example, an RLC transmitter and/or RLC receiver may use two or more RLC entities. In some aspects, an RLC entity may correspond to a bit scheme. For example, each RLC entity may be associated with a respective bit scheme, and each RLC entity may have its own set of RLC parameters, which may be adapted to the respective bit scheme. Thus, if there are two bit schemes, the RLC transmitter may have a first RLC entity associated with the first bit scheme and a second RLC entity associated with the second bit scheme. If there are three bit schemes, the RLC transmitter may have three RLC entities: one RLC entity for each of the three bit schemes. Furthermore, the techniques can be applied to combinations of bit schemes and duplex configurations (ie, whether the carrier is configured as a time division duplex (TDD) carrier or a frequency division duplex (FDD) carrier). As used herein, "configuration" may refer to a combination of a digital scheme and a duplex configuration, or may refer to a digital scheme alone. For example, a UE associated with a first configuration [TDD, 15 kHz] and a second configuration [FDD, 15 KHz] may use two RLC entities: one for each configuration. Furthermore, these techniques can be applied to any number of configurations. Furthermore, in the context of an RLC entity, "configuration" may include a combination of any one or more of duplex configuration, scheduling delay, bit scheme, frequency range, or uplink/downlink slot allocation (e.g. , TDD downlink/uplink slot configuration provided via shared RRC configuration, dedicated RRC configuration, or slot format indication). In some aspects, multiple RLC entities may perform RLC functions in parallel such that RLC functions may be performed simultaneously by a first RLC entity and RLC functions (eg, same RLC function or different RLC functions) of a second RLC entity. Thus, resource consumption is reduced, delays in the RLC function are reduced, throughput is increased, and communication reliability is improved. These improvements may be particularly relevant for carrier aggregation of carriers using different digital schemes.

5 is a diagram illustrating an example 500 of a protocol architecture for carrier aggregation using two RLC entities in accordance with the present disclosure. The protocol framework can be used at the RLC transmitter or the RLC receiver. For example, the protocol framework may be used at UE 120, base station 110, or another receiver or transmitter in a network such as wireless network 100.

As indicated by reference numeral 510, the protocol framework includes PDCP entities. The PDCP entity may perform functions of the PDCP layer, such as those described in connection with FIG. 3 . In some aspects, the agreement framework may include a single PDCP entity, as shown. For example, a single PDCP entity may perform the functions of the PDCP layer.

As indicated by reference numeral 520, the protocol framework includes a first RLC entity. As indicated by reference numeral 530, the protocol framework includes a second RLC entity. A first RLC entity is associated with a first set of carriers (shown as component carriers (CCs) 0 to 2) and a second RLC entity is associated with a second set of carriers (shown as CCs 3 to 5) . In some aspects, the first set of carriers and the second set of carriers are associated with (eg, the same radio bearer) a radio bearer such as a data radio bearer or a signaling radio bearer of a PDCP entity. In some aspects, a first set of carriers may be associated with a first configuration and a second set of carriers may be associated with a second configuration. The first configuration may indicate a first numbering scheme for a first set of carriers. In some aspects, the first configuration may also indicate whether the first set of carriers are TDD carriers or FDD carriers. The second configuration may indicate a second bit scheme for the second set of carriers. In some aspects, the second configuration may also indicate whether the second set of carriers are TDD carriers or FDD carriers. In some aspects, the first configuration or the second configuration may indicate duplex configuration (eg, TDD versus FDD), scheduling delay, bit scheme, frequency range, and/or uplink/downlink time slot allocation. At least one (eg, a TDD downlink/uplink slot configuration that may be provided via a shared RRC configuration, a dedicated RRC configuration, or a slot format indication). Communications associated with the first configuration may be handled by a first RLC entity and communications associated with the second configuration may be handled by a second RLC entity. For example, RLC functions for a first set of carriers (such as any functions performed by the RLC layer, such as the functions described in connection with FIG. 3 ) may be handled by a first RLC entity, and RLC functions for a second set of carriers may be handled by a second RLC entity to deal with. In some aspects, the first set of carriers may be in a first frequency range (eg, FR1, sub-6 frequency range) and the second set of carriers may be in a second frequency range (eg, FR2, mmW frequency range). As indicated by element numeral 540, the protocol framework may include a single MAC entity that may perform MAC layer functions, such as those described in connection with FIG. 3 .

The first RLC entity may be associated with a first set of RLC parameters. The second RLC entity may be associated with a second set of RLC parameters. A set of RLC parameters may include a t-reassembly value, a t-statusProhibit value (which indicates the length of time within which only a single status report may be sent), etc. at the RLC receiver. A set of RLC parameters may include at the RLC transmitter a pollPDU value, a pollByte value, a t-PollRetransmit value (which may indicate the length of time within which only a single poll request may be sent), a maxRetxThreshold value (which may indicate a poll request can be retransmitted), etc.

In some aspects, the first set of RLC parameters may be different than the second set of RLC parameters. For example, the first set of RLC parameters may be different from the second set of RLC parameters if the first set of carriers is associated with a first configuration different from the second configuration of the second set of carriers. In some aspects, a set of RLC parameters may be based at least in part on a configuration. For example, one or more timers indicated by a set of RLC parameters may be shorter for configurations involving shorter symbol lengths (e.g., with a larger SCS) than for configurations involving longer symbol lengths (e.g., with a smaller SCS) . As used herein, a first SCS is considered greater than a second SCS if the first SCS has a larger bandwidth (eg, a 60 kHz SCS is greater than a 30 kHz SCS).

The first RLC entity and the second RLC entity may perform RLC functions independently of each other. For example, a first RLC entity may perform RLC functions for a first set of carriers, while a second RLC entity may perform the RLC functions for a second set of carriers. For example, consider recovering from a lost SN of an SDU. If an SDU is lost on a carrier of the first set of carriers, the first RLC entity may use the first set of RLC parameters to perform recovery of the SDU. If an SDU is lost on a carrier of the second set of carriers, the second RLC entity may perform recovery of the SDU using the second set of RLC parameters.

Using different sets of parameters (which may be associated with different configurations) can improve the performance of the RLC function for different configured carriers. For example, if a single RLC entity is to be configured by a single set of parameters for two different configurations, that single set of parameters may be suboptimal for one or both of the two different configurations. For example, for a configuration with 120 kHz SCS, the reassembly timer for a configuration with 15 kHz SCS may be too long because the RLC receiver may need to buffer due to the higher throughput at 120 kHz SCS compared to 15 The traffic of the kHz SCS is relatively more traffic of the 120 kHz SCS. By providing different sets of RLC parameters for different configurations, the RLC function performance is improved, UE resource usage is reduced, and transmission throughput is increased.

Furthermore, using two different RLC entities for different configurations allows the UE to perform RLC functions for different configurations in parallel. For example, a UE using a single RLC entity may be forced to perform a single reassembly or recovery function at a time (such as using a reassembly timer). If a lost SN is detected on two different configurations, the UE may have to perform a first recovery RLC function for the first configuration, followed by a second recovery RLC function for the second configuration in sequence functionality, which further increases UE resource usage, delays associated with RLC functionality, and the occurrence of lost communications. By using the first RLC entity and the second RLC entity to perform RLC functions in parallel, UE resource usage is reduced (so because information associated with the second RLC function does not need to be cached throughout the first RLC function), reducing The delay associated with the RLC function is eliminated, and the occurrence of lost communication is reduced.

As before, Figure 5 is provided as an example. Other examples may differ from the example with respect to FIG. 5 . For example, although FIG. 5 includes examples associated with two configurations, the techniques described herein may be used with any number of configurations greater than or equal to two.

6 is a diagram illustrating an example 600 of signaling associated with using multiple RLC entities for various configurations in accordance with the present disclosure. Example 600 includes UE 120 and BS 110 .

As shown in FIG. 6 and via reference numerals 605 and 610, BS 110 and UE 120 may establish a first carrier and a second carrier of a carrier aggregation configuration. A first carrier may be associated with (eg, configured in the first configuration) a first carrier and a second carrier may be associated with a second configuration different from the first configuration. The first configuration may be associated with (eg, indicate the first digit scheme and/or the first duplex configuration) the first digit scheme and/or the first duplex configuration. The second configuration may be associated with (eg, indicate the second digit scheme and/or the second duplex configuration) the second digit scheme and/or the second duplex configuration. In some aspects, UE 120 and BS 110 may establish a first set of carriers including the first carrier and/or a second set of carriers including the second carrier. In some aspects, a first carrier may be associated with (eg, within the first frequency range) a first frequency range, and a second carrier may be associated with a second frequency range different from the first frequency range (eg, within the first frequency range). in the second frequency range). In some other aspects, the first carrier and the second carrier may be in the same frequency range (eg, have different configurations in the same frequency range). In some aspects, BS 110 and UE 120 may establish carriers associated with more than two configurations. In such cases, the techniques described herein may be applied to carriers associated with more than two configurations (eg, using one RLC entity per configuration).

As indicated by reference numerals 615 and 620, UE 120 may receive information indicative of a first set of RLC parameters and a second set of RLC parameters. This information can be provided via a single transmission or two separate transmissions. In some aspects, UE 120 may receive this information in conjunction with establishing the first carrier and/or the second carrier (eg, UE 120 may receive information indicative of a set of RLC parameters via signaling associated with the establishing carrier). In some other aspects, UE 120 may receive this information separately from carrier establishment. A set of RLC parameters (eg, a first set of RLC parameters, a second set of RLC parameters) may include one or more of the RLC parameters described in connection with FIG. 3 and/or FIG. 5 above.

The first set of RLC parameters may be associated with the first configuration and the second set of RLC parameters may be associated with the second configuration. Additionally or alternatively, the first set of RLC parameters may be for a first RLC entity (which may handle communications associated with the first configuration) and the second set of RLC parameters may be for a second RLC entity (which may handle communications associated with the second configure the associated communications). Additionally or alternatively, the first set of RLC parameters may be for the first carrier, and the second set of RLC parameters may be for the second carrier.

As indicated by reference numeral 625, UE 120 may establish a first RLC entity and a second RLC entity. The first RLC entity can be associated with the first configuration and can use the first set of RLC parameters. The second RLC entity can be associated with the second configuration and can use the second set of RLC parameters. Additionally or alternatively, a first RLC entity may be associated with a first carrier and a second RLC entity may be associated with a second carrier. Additionally or alternatively, a first RLC entity may be associated with a first frequency range (eg, may handle RLC functions for all carriers in the first frequency range), and a second RLC entity may be associated with a second frequency range ( For example, RLC functionality for all carriers in the second frequency range may be processed). In some aspects, UE 120 may establish a first RLC transmitter entity (e.g., an RLC entity for transmission by UE 120), a first RLC receiver entity (e.g., an RLC entity for reception by UE 120 RLC entity), a second RLC transmitter entity (eg, an RLC entity for transmission by UE 120), and a second RLC receiver entity (eg, an RRC entity for reception by UE 120). In some other aspects, UE 120 may establish a single first RLC entity and a single second RLC entity.

As indicated by reference numeral 630, UE 120 may communicate using a first configuration, such as on a first carrier. Additionally, as indicated by reference numeral 635, UE 120 may perform communications using a second configuration, such as on a second carrier. As indicated by reference numeral 640, UE 120 (eg, a first RLC entity) may perform RLC functions for the first communication. As indicated by reference numeral 645, UE 120 (eg, a second RLC entity) may perform an RLC function (eg, the same RLC function or a different RLC function) for the second communication. For example, a first RLC entity may use a first set of RLC parameters. The second RLC entity may use the second set of RLC parameters. In some aspects, UE 120 may perform RLC functions in parallel for the first communication and for the second communication. Additionally or alternatively, UE 120 may perform RLC functions for the first communication and perform RLC functions for the second communication sequentially (eg, using the first set of parameters and the second set of parameters, respectively). As used herein, "communication" may refer to RLC PDUs, RLC SDUs, transmissions carrying one or more RLC PDUs and/or RLC SDUs, and the like.

In some aspects, the RLC function may be a reassembly function, such as may be associated with a reassembly timer. For example, UE 120 may detect a lost SN of communication. Depending on whether the communication is on the first carrier or the second carrier, UE 120 may enable a reassembly timer identified by the first set of RLC parameters or the second set of RLC parameters. For example, if the communication is on a first carrier, UE 120 may enable a reassembly timer identified by a first set of RLC parameters, and if the communication is on a second carrier, UE 120 may enable a reassembly timer identified by a second set of RLC parameters. The reassembly timer identified by the parameter. If no missing SN is received by the end of the reassembly timer, UE 120 may send a status report indicating the missing SN. For example, the status report may be sent according to the same set of RLC parameters used to determine the reassembly timer. Accordingly, UE 120 can reduce buffer size, reduce latency associated with recovery of lost SNs, and increase transmission throughput.

In some aspects, communications, such as those shown by reference numerals 630 and 635 , may carry RLC PDUs, such as AMD PDUs. In some aspects, the RLC PDU may include a field indicating whether the RLC PDU is associated with the first configuration or the second configuration. For example, the field may be a bit scheme information field including a value indicating the configuration associated with the RLC PDU. An RLC transmitter generating an RLC PDU may set this field to a value associated with the configuration to be used for the RLC PDU. The RLC receiver can identify whether the RLC PDU should be processed by the first RLC entity or the second RLC entity based at least in part on the field. For example, the RLC receiver can identify whether the RLC functions for the RLC PDU should be performed by a first RLC entity or by a second RLC entity. In some aspects, the RLC PDU may be a status report, such as based at least in part on the RLC entity's reassembly timer (associated with the configuration indicated by the field) expiring or based at least in part on the RLC entity receiving a Linked polling messages. Polling messages or status reports associated with a particular configuration (eg, related to communications using a particular configuration) may be considered specific to a particular configuration.

In some aspects, communications associated with the first configuration and communications associated with the second configuration can be distinguished based at least in part on the SN. For example, a set of potential SNs that can be assigned to communications can be divided into subsets corresponding to various configurations. If there are M configurations for a set of carrier configurations, the set of potential SNs can be divided into M subsets, and each configuration can be associated with a subset (for example, the mth configuration can be associated with the mth subset couplet). In some aspects, the M subsets may have interleaved SNs. As an example, all communications associated with a first configuration may have an odd SN, while all communications associated with a second configuration may have an even SN. An RLC entity associated with a particular configuration may perform RLC functions, such as reassembly according to SNs belonging to the subset associated with the particular configuration. By using a subset of a set of SNs, the signaling management burden associated with sending the field indicating the configuration and the impact on the RLC PDU format is reduced.

In some aspects, UE 120 may send a status report (eg, the communication indicated by element numeral 630 or 635 may be a status report). In this case, the status report may indicate whether the status report is associated with the first configuration or the second configuration, as previously described. In some aspects, UE 120 may send a status report based at least in part on expiration of a reassembly timer associated with a particular configuration. For example, consider that UE 120 performs two reassembly functions: one for carriers in FR1 with a first configuration, and another reassembly function for carriers in FR2 with a second configuration. In such a case, the reassembly timer associated with the carrier in FR2 may expire before the reassembly timer associated with the carrier in FR1. Accordingly, UE 120 may send a status report indicating a NACK for the carrier in FR2. However, the reassembly function for the carriers in FR1 may still be in progress due to the longer reassembly timer associated with the carriers in FR1. For example, according to the longer reassembly timer, UE 120 still has time to recover the lost SN on the carrier in FR1. In some cases, UE 120 may receive a poll message requesting a status report for the carrier for which the reassembly timer is running.

In some aspects, a status report sent by UE 120 may indicate an unavailable status for the SN. Continuing with the above example, the status report may indicate a NACK for the carrier in FR2 and may indicate that the status of the missing SN for the carrier in FR1 is unavailable. The unavailable state may indicate that the reassembly timer for the carrier in FR1 has not elapsed (eg, the reassembly timer is in progress). Therefore, the unavailable state may not trigger RLC retransmission of communications associated with the lost SN. For example, BS 110 may not perform RLC retransmissions of communications associated with a lost SN if the status report indicates an unavailable status. In some aspects, a status report may indicate an unavailable status related to a single carrier (eg, the report may also not indicate ACK/NACK for a different carrier). For example, a status report may indicate an unavailable status for only one carrier.

By providing a NACK for a first carrier associated with past reassembly timers and an unavailable status (e.g., across two RLC entities) for a second carrier associated with ongoing reassembly timers, UE 120 may be at RLC recovery for the first carrier begins when the reassembly timer executes for the second carrier. Once the reassembly timer for the second carrier has elapsed, UE 120 may send a NACK for the second carrier (if the missing SN has not been received). This can be especially useful when the RLC transmitter sends a poll message requesting a status message, because the RLC transmitter can reduce the size of the buffer based on a NACK for the first carrier and at the same time reduce the size of the buffer based on an unavailable status message for the second carrier. Continue caching with state. Furthermore, UE RLC transmitter resources can be saved since the UE does not need to perform replication (eg, PDCP replication) for the acknowledged SN, thereby reducing buffer size, transmit power and network resource consumption.

FIG. 7 is a diagram illustrating examples 700 and 705 of RLC PDU structures including an unavailable state in accordance with the teachings of the present disclosure. In some aspects, an RLC PDU carrying a status report (eg, a status PDU) may include a field indicating whether the RLC PDU indicates a NACK or unavailable status. For example, an RLC PDU may have an El field, an E2 field, and an E3 field. The E1 field may indicate whether a NACK field is included in the RLC PDU. The NACK field indicates the first SN that was lost. The E2 field may indicate whether a Segment Offset (SO) field (indicating the position within the RLC SDU of the RLC SDU segment associated with the first SN) is included in the RLC PDU. The E3 field may indicate whether the NACK range field follows the NACK field. The NACK range indicates the number of lost consecutive RLC SDUs starting from the SN specified by the NACK field. In some aspects, the RLC PDU may include an E4 field. The E4 field may indicate whether the status report indicates a NACK or unavailable status. For example, if the E1 field indicates that a NACK field is included, then a first value of E4 may indicate that the E1, E2, and E3 fields are associated with NACK, and a second value of E4 may indicate that the E2, E1, and E4 fields are associated with the unavailable state. The E1, E2, and E3 fields may (e.g., respectively) indicate whether the field indicating the first SN that is unavailable is present, whether the SO field is present, and whether the unavailable range field follows the field indicating the first SN . In some aspects, the status report may indicate, for the highest SN up to acknowledged (represented by ACK_SN) other than unavailable or negatively acknowledged SNs, associated with the carrier for which the status report was triggered, Acknowledgment by all SNs (eg, based at least in part on reassembly timers or polling PDUs). If the reassembly timer is still running for the RLC hole or if the reassembly timer has not been started for the RLC hole, the UE may report the unavailable status for the RLC hole. An RLC hole is a set of missing RLC SNs associated with one or more RLC PDUs.

Example 700 shows a Status PDU with SN and SO fields of 18 bits. In example 700, an E4 value of 1 (shown by element symbol 710) indicates that the E1, E2, and E3 values (shown by element symbol 715) associated with the second carrier are related to the unavailable state for the SN. The indication is associated with (eg, is used for the indication). Accordingly, the field indicated by element number 720 may indicate the range of SOs and unavailable SNs, while the field indicated by element number 725 may indicate the first unavailable SN.

Example 705 illustrates a status PDU with a 12-bit SN and no SO field carrying an unavailable status. In example 700, the E4 value, indicated by element numeral 730, is set to 0, which indicates that the ACK does not indicate an unavailable state. Furthermore, the E1 value indicated by element number 735 is set to 0 (which indicates no NACK/unavailable field, SO field or NACK/unavailable range), so the E4 value indicated by element number 740 is preserved.

As indicated above, Figures 6 and 7 are provided as examples. Other examples may differ from those shown with respect to FIGS. 6 and 7 .

8 is a diagram illustrating an exemplary process 800 performed, eg, by a wireless communication device, in accordance with the present disclosure. Exemplary process 800 is an instance in which a wireless communication device (eg, UE 120, BS 110, network node of a non-converged base station) performs operations associated with radio link control for a hybrid configuration. In some aspects, the wireless communication device is an RLC transmitter (eg, a device or network node that performs RLC functionality for sending communications). In some aspects, the wireless communication device is an RLC receiver (eg, a device or network node that performs RLC functions for receiving communications).

As shown in FIG. 8 , in some aspects, process 800 may include establishing a first carrier of a CA configuration, where the first carrier is associated with the first configuration (block 810 ). For example, a wireless communication device (eg, using communication manager 140 and/or sending component 904 illustrated in FIG. 9 ) may establish a first carrier of a CA configuration, where the first carrier is associated with the first configuration, as described above. In some aspects, the first configuration may indicate the bit scheme of the first carrier. In some aspects, the first configuration may indicate the bit scheme of the first carrier and whether the first carrier is a TDD carrier or an FDD carrier.

As further shown in FIG. 8 , in some aspects, process 800 may include establishing a second carrier of the CA configuration, where the second carrier is associated with a second configuration different from the first configuration (block 820 ). For example, a wireless communication device (eg, using communication manager 140 and/or sending element 904 as illustrated in FIG. 9 ) may establish a second carrier of a CA configuration, where the second carrier is different from the second configuration is associated. In some aspects, the second configuration may indicate the bit scheme of the second carrier. In some aspects, the second configuration may indicate the bit scheme of the second carrier and whether the second carrier is a TDD carrier or an FDD carrier.

As further shown in FIG. 8 , in some aspects, process 800 may include receiving information indicative of a first set of RLC parameters for a first configuration and a second set of RLC parameters for a second configuration (block 830 ). For example, as previously described, a wireless communication device (e.g., using communication manager 140 and/or receiving element 902 as illustrated in FIG. 9 ) may receive a first set of RLC parameters indicative of a first configuration and an Information about the second set of RLC parameters.

As further shown in FIG. 8 , in some aspects, process 800 may include using a first set of RLC parameters to perform RLC functions for a first communication on a first carrier (block 840 ). For example, as previously described, a wireless communication device (e.g., using the communication manager 140 and/or the first RLC component 908 as illustrated in FIG. 9 ) may use a first set of RLC parameters to perform RLC functions for The first newsletter on .

As further shown in FIG. 8, in some aspects, process 800 may include using a second set of RLC parameters to perform RLC functions for a second communication on a second carrier (block 850). For example, as previously described, the wireless communication device (e.g., using the communication manager 140 and/or the second RLC component 910 as illustrated in FIG. 9 ) may use a second set of RLC parameters to perform RLC functions for The second newsletter on .

Process 800 can include other aspects, such as any single aspect or any combination of aspects described below and/or aspects related to one or more other processes described elsewhere herein.

In the first aspect, establishing the first carrier includes establishing a first RLC entity associated with the first configuration, and wherein establishing the second carrier includes establishing a second RLC entity associated with the second configuration.

In a second aspect, alone or in combination with the first aspect, RLC functions are performed by a first RLC entity for a first communication and performed by a second RLC entity for a second communication.

In a third aspect, alone or in combination with one or more of the first and second aspects, process 800 includes transmitting a PDCP control PDU on selected ones of the first RLC entity and the second RLC entity.

In a fourth aspect, individually or in combination with one or more of the first to third aspects, the RLC function is performed in parallel for the first carrier and the second carrier.

In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the first communication or the second communication is via at least one of a data radio bearer or a signaling radio bearer.

In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the RLC function is associated with at least one of an acknowledged mode or an unacknowledged mode.

In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the RLC functionality is based at least in part on an RLC PDU, and wherein the RLC PDU includes an indication of whether the RLC PDU is associated with the first configuration or Fields associated with the second configuration.

In an eighth aspect, the RLC function, alone or in combination with one or more of the first through seventh aspects, is a recombination function, and wherein the recombination function is based at least in part on the first set of A sequence number (SN) and a second set of SNs associated with the second configuration.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the process 800 includes, based at least in part on whether the RLC PDU is associated with a selected one of the first set of SNs or the second set of SNs associated with a set of SNs to send a status report for the RLC PDU, wherein the status report is specific to the configuration associated with the selected set of SNs, and wherein the status report is based at least in part on a polling message associated with the configuration or of the reassembly timer associated with the configuration.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the process 800 includes sending a status report for RLC PDUs received on the first carrier, wherein the status report indicates a status report for the second The status of the carrier is unavailable.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the status report for the RLC PDU indicates a negative for the RLC PDU when the reassembly timer for the second carrier is active acknowledging, wherein the status report indicates that the status for the second carrier is unavailable based at least in part on the reassembly timer being valid for the second carrier, wherein the status report indicates an acknowledgment for all RLC PDUs received on the first carrier, And the method further includes performing a reassembly function associated with the RLC PDU.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the process 800 includes sending another indication of a negative acknowledgment for the second carrier after the reassembly timer has elapsed. A status report, wherein if all RLC PDUs on the second carrier were successfully received, an acknowledgment for all RLC PDUs on the second carrier is sent based at least in part on the polling associated with the second carrier.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the status report includes a field that distinguishes whether the status report indicates a negative acknowledgment or the status is unavailable.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the status report indicates an acknowledgment of sequence numbers for sequence numbers associated with the second carrier up to unavailable.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the process 800 includes sending a status report for the RLC PDU, wherein the status report includes a status report for the first carrier or the second carrier At least one of, one or more negative acknowledgments, one or more acknowledgments, and an indication that the status is unavailable.

In a sixteenth aspect, either alone or in combination with one or more of the first through fifteenth aspects, the first configuration or the second configuration indicates a duplex configuration, scheduling delay, bit scheme, frequency range, or At least one of uplink/downlink time slot assignments.

Although FIG. 8 illustrates example blocks of process 800, in some aspects, process 800 may include additional blocks, fewer blocks, different blocks, or arrangements than those shown in FIG. different squares. Additionally or alternatively, two or more blocks of process 800 may be performed in parallel.

FIG. 9 is a block diagram of an exemplary apparatus 900 for wireless communication in accordance with the present disclosure. The apparatus 900 may be a wireless communication device (eg, the UE 120 , the BS 110 , a network node of a non-aggregated BS), or the wireless communication device may include the apparatus 900 . In some aspects, device 900 includes a receiving element 902 and a transmitting element 904 that can communicate with each other (eg, via one or more busses and/or one or more other elements). As shown, an apparatus 900 can communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using a receiving element 902 and a transmitting element 904 . As further shown, device 906 may include communication manager 140 . The communication manager 140 may include one or more of the first RLC element 908 or the second RLC element 910, among others.

In some aspects, apparatus 900 may be configured to perform one or more operations described herein in conjunction with FIGS. 3-7 . Additionally or alternatively, apparatus 900 may be configured to perform one or more processes described herein (eg, process 800 of FIG. 8 ) or a combination thereof. In some aspects, apparatus 900 and/or one or more elements shown in FIG. 9 may include one or more elements of the wireless communication device described in connection with FIG. 2 . Additionally or alternatively, one or more elements shown in FIG. 9 may be implemented within one or more elements described in connection with FIG. 2 . Additionally or alternatively, one or more elements of the set of elements may be implemented at least in part as software stored in memory. For example, an element (or a portion of an element) may be implemented as instructions or codes stored in a non-transitory computer readable medium and executable by a controller or processor to perform the function or operation of the element.

The receiving component 902 can receive communications from the device 906, such as reference signals, control information, data communications, or combinations thereof. Receiving component 902 may provide received communications to one or more other components of device 900 . In some aspects, receiving element 902 may perform signal processing (eg, filtering, amplifying, demodulating, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communication, And the processed signal may be provided to one or more other elements of apparatus 900 . In some aspects, the receiving component 902 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers/processors, memories of the wireless communication devices described in connection with FIG. 2 or a combination thereof.

The sending component 904 can send a communication, such as a reference signal, control information, data communication, or a combination thereof, to the device 906 . In some aspects, one or more other components of device 900 may generate communications and may provide the generated communications to sending component 904 for transmission to device 906 . In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the resulting communication and can transmit the processed signal to the device 906. In some aspects, the transmitting component 904 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controller/processors, memories of the wireless communication device described in conjunction with FIG. 2 , or a combination thereof. In some aspects, the transmit element 904 can be collocated with the receive element 902 in the transceiver.

The sending component 904 can establish a first carrier of the CA configuration, where the first carrier is associated with the first configuration. The sending component 904 can establish a second carrier of the CA configuration, where the second carrier is associated with a second configuration different from the first configuration. The receiving component 902 can receive information indicative of a first set of RLC parameters for the first configuration and a second set of RLC parameters for the second configuration. The first RLC component 908 can perform RLC functions for the first communication on the first carrier using the first set of RLC parameters. The second RLC component 910 may perform RLC functions for the second communication on the second carrier using the second set of RLC parameters.

The sending component 904 can transmit a PDCP PDU on a selected one of the first RLC entity and the second RLC entity.

The sending component 904 can send a status report for the RLC PDU based at least in part on whether the RLC PDU is associated with the selected SN in the first set of SNs or the second set of SNs, wherein the status report is specific for being associated with the selected SN configured.

The sending component 904 can send a status report for the RLC PDU received on the first carrier, wherein the status report indicates that the status for the second carrier is unavailable.

The sending element 904 may send a further status report indicating a negative acknowledgment for the second carrier during or after performing the reassembly function.

The number and arrangement of elements shown in Figure 9 are provided as examples. In fact, there may be additional elements, fewer elements, different elements, or differently arranged elements than those shown in FIG. 9 . Furthermore, two or more elements shown in FIG. 9 may be implemented in a single element, or a single element shown in FIG. 9 may be implemented as multiple distributed elements. Additionally or alternatively, a set of elements (one or more elements) shown in FIG. 9 may perform one or more functions described as being performed by another set of elements shown in FIG. 9 .

10 is a diagram illustrating an exemplary process 1000 performed, eg, by a wireless communication device, in accordance with the present disclosure. Exemplary process 1000 is an instance in which a wireless communication device (eg, UE 120, base station 110, network node of a non-aggregated base station) performs operations associated with radio link control for a mixed-digit scheme.

As shown in FIG. 10 , in some aspects, process 1000 may include establishing a first set of carriers of a CA configuration, where the first set of carriers is associated with the first configuration (block 1010 ). For example, a wireless communication device (e.g., using communication manager 140 and/or sending component 904 as illustrated in FIG. 9 ) may establish a first set of carriers of a CA configuration, wherein the first set of carriers is associated with the first configuration, As mentioned above.

As further shown in FIG. 10 , in some aspects, process 1000 may include establishing a second set of carriers of a CA configuration, where the second set of carriers is associated with the second configuration (block 1020 ). For example, a wireless communication device (e.g., using communication manager 140 and/or sending element 904 as illustrated in FIG. 9 ) may establish a second set of carriers of a CA configuration, wherein the second set of carriers is associated with the second configuration, As mentioned above.

As further shown in FIG. 10, in some aspects, process 1000 may include receiving RLC PDUs on a first set of carriers (block 1030). For example, a wireless communication device (eg, using communication manager 140 and/or receiving element 902 as illustrated in FIG. 9 ) may receive RLC PDUs on a first set of carriers, as previously described.

As further shown in FIG. 10 , in some aspects, process 1000 may include sending a status report for the RLC PDU indicating that the status for the second set of carriers is unavailable (block 1040 ). For example, as previously described, the wireless communication device (e.g., using the communication manager 140 and/or the sending element 904 as illustrated in FIG. 9 ) may send a status report for the RLC PDU indicating the status for the second set of carriers is not available.

Process 1000 can include other aspects, such as any single aspect or any combination of aspects described below and/or aspects related to one or more other processes described elsewhere herein.

In a first aspect, the status report for the RLC PDU indicates a negative acknowledgment for the RLC PDU when the reassembly timer for the second set of carriers is valid, wherein the status report is based at least in part on the reassembly timing for the second set of carriers is valid to indicate that the status for the second set of carriers is unavailable, wherein the status report indicates acknowledgments for all RLC PDUs received on the first set of carriers, and wherein the method further includes performing reassembly associated with the RLC PDUs Function.

In a second aspect, alone or in combination with the first aspect, process 1000 includes sending another status report after the reassembly timer has elapsed, the other status report indicating a negative acknowledgment for the second set of carriers, wherein if successful Receiving all RLC PDUs on the second set of carriers, an acknowledgment for all RLC PDUs on the second set of carriers is sent based at least in part on polling associated with the second set of carriers.

In a third aspect, alone or in combination with one or more of the first and second aspects, the status report includes a field that distinguishes whether the status report indicates a negative acknowledgment or the status is unavailable.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the status report indicates that all but unavailable or negatively acknowledged sequence numbers are associated with the second set of carriers. Confirmation of all sequence numbers up to the highest confirmed sequence number.

In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the status report includes one or more negative acknowledgments for at least one of the first set of carriers or the second set of carriers , one or more acknowledgments, and an indication that the status is unavailable.

In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the first configuration or the second configuration indicates a duplex configuration, scheduling delay, bit scheme, frequency range, or uplink/ At least one of downlink time slot assignments.

Although FIG. 10 illustrates exemplary blocks of process 1000, in some aspects, process 1000 may include additional blocks, fewer blocks, different blocks, or arrangements than those shown in FIG. different squares. Additionally or alternatively, two or more blocks of process 1000 may be performed in parallel.

The following provides an overview of some aspects of the content of the case:

Aspect 1: A wireless communication method performed by a wireless communication device, including: establishing a first carrier configured with carrier aggregation (CA), wherein the first carrier is associated with the first configuration; establishing a first carrier configured with the CA Two carriers, wherein the second carrier is associated with a second configuration different from the first configuration; receiving an indication of a first set of radio link control (RLC) parameters for the first configuration and a set of radio link control (RLC) parameters for the second configuration information of a second set of RLC parameters; using the first set of RLC parameters to perform an RLC function for the first communication on the first carrier; and using the second set of RLC parameters to perform the RLC function for the first communication on the first carrier A second communication on a second carrier.

Aspect 2: The method of Aspect 1, wherein establishing the first carrier includes establishing a first RLC entity associated with the first configuration, and wherein establishing the second carrier includes establishing a first RLC entity associated with the second configuration Two RLC entities.

Aspect 3: The method of aspect 2, wherein the RLC function is performed by the first RLC entity for the first communication and is performed by the second RLC entity for the second communication.

Aspect 4: The method according to Aspect 2, further comprising: transmitting a Packet Data Convergence Protocol (PDCP) Control Protocol Data Unit (PDU) on a selected one of the first RLC entity and the second RLC entity.

Aspect 5: The method of any one of aspects 1-4, wherein the RLC function is performed in parallel for the first carrier and for the second carrier.

Aspect 6: The method of any one of aspects 1-5, wherein the first communication or the second communication is over at least one of a data radio bearer or a signaling radio bearer.

Aspect 7: The method of any of aspects 1-6, wherein the RLC function is associated with one of an acknowledged mode or an unacknowledged mode.

Aspect 8: The method of any of aspects 1-7, wherein the RLC function is based at least in part on an RLC protocol data unit (PDU), and wherein the RLC PDU includes an indication that the RLC-PDU is Whether the field is associated with the first configuration or the second configuration.

Aspect 9: The method of any of aspects 1-8, wherein the RLC function is a reassembly function, and wherein the reassembly function is based at least in part on a first set of sequence numbers associated with the first configuration (SN) and a second set of SNs associated with the second configuration.

Aspect 10: The method of Aspect 9, further comprising: transmitting based at least in part on whether an RLC protocol data unit (PDU) is associated with the first set of SNs or a selected set of SNs in the second set of SNs A status report for the RLC PDU, wherein the status report is specific to the configuration associated with the selected set of SNs, and wherein the status report is based at least in part on a polling message associated with the configuration or with the Sets the associated reorganization timer.

Aspect 11: The method according to any one of aspects 1-10, further comprising: sending a status report for the RLC protocol data unit (PDU) received on the first carrier, wherein the status report indicates the status report for The status of the second carrier is unavailable.

Aspect 12: The method of Aspect 11, wherein the status report for the RLC PDU indicates a negative acknowledgment for the RLC-PDU while a reassembly timer for the second carrier is active, wherein the status report is at least in part indicating that the status for the second set of carriers is unavailable based on the reassembly timer being valid for the second carrier, wherein the status report indicates acknowledgments for all RLC PDUs received on the first carrier, and Wherein the method further includes: performing a reassembly function associated with the RLC PDU.

Aspect 13: The method according to Aspect 12, further comprising: sending another status report after the reassembly timer has elapsed, the another status report indicating a negative acknowledgment for the second carrier, wherein if the All RLC PDUs on the second carrier, the acknowledgment for all RLC PDUs on the second carrier is sent based at least in part on a poll associated with the second carrier.

Aspect 14: The method of Aspect 11, wherein the status report includes a field to distinguish whether the status report indicates a negative acknowledgment or the status is unavailable.

Aspect 15: The method of Aspect 11, wherein the status report indicates acknowledgments for all sequence numbers associated with the second carrier up to the highest acknowledged sequence number except unavailable or negatively acknowledged sequence numbers .

Aspect 16: The method according to any one of aspects 1-15, further comprising: sending a status report for an RLC protocol data unit (PDU), wherein at least one of the first carrier or the second carrier One, the status report includes one or more negative acknowledgments, one or more acknowledgments, and an indication that the status is unavailable.

Aspect 17: The method of any of Aspects 1-16, wherein the first configuration or the second configuration indicates a duplex configuration, scheduling delay, bit plan, frequency range, or uplink/downlink At least one of link slot assignments.

Aspect 18. A wireless communication method performed by a wireless communication device, comprising: establishing a first group of carriers of a carrier aggregation (CA) configuration, wherein the first group of carriers is associated with the first configuration; establishing a first group of carriers of the CA configuration Two sets of carriers, wherein the second set of carriers is associated with a second configuration; receiving information indicating a first set of radio link control (RLC) parameters for the first configuration and a second set of RLC parameters for the second configuration ; using the first set of RLC parameters to perform an RLC function for a first communication on the first set of carriers; and using the second set of RLC parameters to perform the RLC function for a first communication on the second set of carriers Two communications, wherein the first communication and the second communication are associated with radio bearers.

Aspect 19: The method according to Aspect 18, further comprising performing a PDCP function for the first communication and for the second communication.

Aspect 20: The method of Aspect 19, wherein the PDCP functions for the first communication and the second communication are performed by a single PDCP entity.

Aspect 21: The method of any of aspects 18-20, wherein establishing the first set of carriers comprises establishing a first RLC entity associated with the first configuration, and wherein establishing the second set of carriers Including establishing a second RLC entity associated with the second configuration.

Aspect 22: The method of aspect 21, wherein the RLC function is performed by the first RLC entity for the first communication and is performed by the second RLC entity for the second communication.

Aspect 23: The method of Aspect 21, further comprising: transmitting a Packet Data Convergence Protocol (PDCP) Control Protocol Data Unit (PDU) on a selected one of the first RLC entity and the second RLC entity.

Aspect 24: The method of any of aspects 18-23, wherein traffic for the first communication or the second communication is split between the first RLC entity and the second RLC entity .

Aspect 25: The method of any one of aspects 18-24, wherein the RLC function is performed in parallel for the first set of carriers and the second set of carriers.

Aspect 26: The method of any one of aspects 18-25, wherein the first communication or the second communication is via the radio bearer, wherein the radio bearer is a data radio bearer or a signaling radio bearer at least one of the .

Aspect 27: The method of Aspect 26, wherein the first communication and the second communication are carried over the radio.

Aspect 28: The method of any of Aspects 18-27, wherein the RLC function is associated with one of an acknowledged mode or an unacknowledged mode.

Aspect 29: The method of any of aspects 18-28, wherein the RLC function is based at least in part on an RLC protocol data unit (PDU), and wherein the RLC PDU includes an indication that the RLC-PDU is related to The first configuration is also a field associated with the second configuration.

Aspect 30: The method of any of aspects 18-29, wherein the RLC function is a reassembly function, and wherein the reassembly function is based at least in part on a first set of sequence numbers associated with the first configuration (SN) and a second set of SNs associated with this second configuration.

Aspect 31: The method according to aspect 30, further comprising: based at least in part on whether the RLC protocol data unit (PDU) is associated with the first set of SNs or with a selected set of SNs in the second set of SNs, sending the a status report of the RLC PDU, wherein the status report is specific to the configuration associated with the selected set of SNs, and wherein the status report is based at least in part on a polling message associated with the configuration or related to the setting associated reassembly timer.

Aspect 32: The method according to any one of aspects 18-31, further comprising: sending a status report for RLC protocol data units (PDUs) received on the first set of carriers, wherein the status report indicates The status for the second set of carriers is unavailable.

Aspect 33: The method of aspect 32, wherein the status report for the RLC PDU indicates a negative acknowledgment for the RLC-PDU when a reassembly timer for the second set of carriers is active, wherein the status report is at least Indicating that the status for the second group of carriers is unavailable based in part on the reassembly timer being valid for the second group of carriers, wherein the status report indicates the status for all RLC PDUs received on the first group of carriers Acknowledging, and wherein the method further comprises: performing a reassembly function associated with the RLC PDU.

Aspect 34: The method according to Aspect 33, further comprising: sending another status report after the reassembly timer has elapsed, the another status report indicating a negative acknowledgment for the second set of carriers, wherein if successfully received For all RLC PDUs on the second set of carriers, the acknowledgments for all RLC PDUs on the second set of carriers are sent based at least in part on polling associated with the second set of carriers.

Aspect 35: The method of Aspect 33, wherein the status report includes a field to distinguish whether the status report indicates a negative acknowledgment or the status is unavailable.

Aspect 36: The method according to aspect 33, wherein the status report indicates all sequence numbers up to the highest acknowledged sequence number associated with the second set of carriers except unavailable or negatively acknowledged sequence numbers. confirm.

Aspect 37: The method according to any one of aspects 18-36, further comprising: sending a status report for an RLC protocol data unit (PDU), wherein for the first group of carriers or the second group of carriers At least one of , the status report includes one or more negative acknowledgments, one or more acknowledgments, and an indication that the status is unavailable.

Aspect 38: The method of any of Aspects 18-36, wherein the first configuration or the second configuration indicates a duplex configuration, scheduling delay, bit plan, frequency range, or uplink/downlink At least one of link slot assignments.

Aspect 39: The method of any of Aspects 18-38, wherein the method further comprises: establishing a third set of carriers of the CA configuration, wherein the third set of carriers is associated with a third configuration; and RLC functions are performed using a third set of RLC parameters for a third communication on a third set of carriers, wherein the third communication is associated with a radio bearer.

Aspect 40: A method of wireless communication performed by a user equipment (UE), comprising: establishing a first set of carriers of a carrier aggregation (CA) configuration, wherein the first set of carriers is associated with the first configuration; establishing a second set of carriers of the CA configuration, wherein the second set of carriers is associated with a second configuration; receiving an RLC protocol data unit (PDU) received on the first set of carriers; and sending a status for the RLC PDU report, the status report indicating that the status for the second set of carriers is unavailable.

Aspect 41: The method of aspect 40, wherein the status report for the RLC PDU indicates a negative acknowledgment for the RLC-PDU while a reassembly timer for the second set of carriers is active, wherein the status report is at least in part indicating that the status for the second group of carriers is unavailable based on the reassembly timer being valid for the second group of carriers, wherein the status report indicates an acknowledgment for all RLC PDUs received on the first group of carriers , and wherein the method further comprises: performing a reassembly function associated with the RLC PDU.

Aspect 42: The method according to Aspect 41, further comprising: sending another status report after the reassembly timer has elapsed, the another status report indicating a negative acknowledgment for the second set of carriers, wherein if successfully received For all RLC PDUs on the second set of carriers, the acknowledgments for all RLC PDUs on the second set of carriers are sent based at least in part on polling associated with the second set of carriers.

Aspect 43: The method of any of Aspects 40-42, wherein the status report includes a field to distinguish whether the status report indicates a negative acknowledgment or a status is not available.

Aspect 44: The method of any one of aspects 40-43, wherein the status report indicates a sequence number associated with the second set of carriers, except for unavailable or negatively acknowledged sequence numbers, up to Confirmation of all serial numbers with the highest confirmed serial number.

Aspect 45: The method of any of aspects 40-44, wherein for at least one of the first set of carriers or the second set of carriers, the status report includes one or more negative acknowledgments, a or multiple acknowledgments with an indication that the status is unavailable.

Aspect 46: The method of any of Aspects 40-45, wherein the first configuration or the second configuration indicates a duplex configuration, scheduling delay, bit plan, frequency range, or uplink/downlink At least one of link slot assignments.

Aspect 47: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and stored in the memory and executable by the processor to cause the apparatus to perform according to Aspect 1-46 Instructions for the methods described in one or more of the aspects.

Aspect 48: An apparatus for wireless communication, comprising: a memory and one or more processors coupled to the memory, the memory and the one or more processors configured to perform the method of Aspect 1-46. The method described in one or more aspects.

Aspect 49: An apparatus for wireless communication, comprising: at least one means for performing the method recited in one or more of aspects 1-46.

Aspect 50: A non-transitory computer readable medium storing code for wireless communication, the code comprising executable by a processor to perform the method of one or more of aspects 1-46 instructions.

Aspect 51: A non-transitory computer-readable medium storing a set of instructions for wireless communications, the set of instructions including one or more instructions that, when executed by one or more processors of a device, one or more The instructions cause an apparatus to perform the method recited in accordance with one or more of aspects 1-46.

The foregoing disclosure has provided illustrations and descriptions, but is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure, or may be acquired from the practice of such aspects.

As used herein, the term "element" is intended to be interpreted broadly as hardware and/or a combination of hardware and software. "Software" shall be construed broadly to mean instructions, sets of instructions, code, sections of code, code, programs, subroutines, software modules, applications, software applications, packages, routines, subroutines, objects, Executable files, executing threads, programs and/or functions, etc., regardless of whether they refer to software, firmware, middleware, microcode, hardware description languages, etc. As used herein, a "processor" is implemented in hardware and/or a combination of hardware and software. It will be apparent that the systems and/or methods described herein can be implemented in different forms of hardware and/or a combination of hardware and software. The actual dedicated control hardware or software code used to implement such systems and/or methods does not limit these aspects. Accordingly, the operation and behavior of systems and/or methods are described herein without reference to specific software code - as those skilled in the art will understand that software and hardware can be designed to implement a system based at least in part on the description herein and/or methods.

As used herein, "meeting a threshold" may refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

Although certain combinations of features are stated in the claims and/or disclosed in the specification, such combinations are not intended to limit the disclosure of the individual aspects. Many of these features may be combined in ways not specifically stated in the claims and/or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other of the set of claims. As used herein, reference to "at least one" of a list of items refers to any combination of those items, including individual members. As an example, "at least one of a, b, or c" is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c and any combination with multiples of the same element (e.g. , a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c , c+c and c+c+c or any other ordering of a, b and c).

No element, act, or instruction used herein should be construed as critical or essential unless expressly stated otherwise. Furthermore, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more". Furthermore, as used herein, the article "the" is intended to include one or more of the items referenced in connection with the article "the" and may be used interchangeably with "the one or more". Also, as used herein, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more". Where only one item is desired, the term "only one" or similar language is used. Furthermore, as used herein, the terms "having", "having", "containing" and the like are intended to be open-ended terms that do not limit the element it modifies (eg, an element "having" A may also have B). Additionally, the term "based on" is intended to mean "based at least in part on," unless expressly stated otherwise. Furthermore, as used herein, the term "or" is intended to be inclusive when used in tandem and may be used interchangeably with "and/or" unless expressly stated otherwise (for example, if used in conjunction with "or" or "Only one of them" combination).

100: wireless network 102a: Macro cell service area 102b: pico cell service area 102c: Femtocell service area 110a: macro base station 110b: pico base station 110c: femto base station 110d: Relay station base station 110: base station 120: User equipment 120a:UE 120b:UE 120c:UE 120d:UE 120e:UE 130: Network controller 140:Communication Manager 200: Example 212: Sources of information 220: send processor 230: Transmit (TX) Multiple-Input Multiple-Output (MIMO) Processor 232a: modem 232t: modem 234a: Antenna 234t: Antenna 236:MIMO detector 238: Receive processor 239: data slot 240: Controller/Processor 242: memory 244: Communication unit 252a: Antenna 252r: Antenna 254a: modem 254r: modem 256:MIMO detector 258: Receive processor 260: data slot 262: Sources of information 264: send processor 266:TX MIMO processor 280: Controller/Processor 282: memory 284: shell 290: Controller/Processor 292: memory 294: Communication unit 300: Example 400: instance 405: In-band continuous mode 410: In-band discontinuous mode 415: Discontinuous mode between bands 500: instance 510: mode 520: mode 530: mode 540: mode 600: instance 605: Operation 610: Operation 615: Operation 620: Operation 625: Operation 630: communication 635: communication 640: Operation 645: Operation 700: instance 705: Instance 710: E4 value 715: E1/E2/E3 value 720: field 725: field 730: E4 value 735: E1 value 740: E4 value 800: process 810: operation 820: Operation 830: Operation 840: Operation 850: operation 900: device 902: receiving element 904: send components 906: device 908: The first RLC component 910: second RLC element 1000: process 1010: operation 1020: Operation 1030: Operation

In order that the above recited features of the subject matter can be understood in detail, a more particular description briefly summarized above may be had by reference to various aspects, some of which are illustrated in the accompanying drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of the subject matter and are therefore not to be considered limiting of its scope, for the description may admit to other equivalent aspects. The same reference numbers in different drawings may identify the same or similar elements.

FIG. 1 is a diagram showing an example of a wireless network according to the present application.

FIG. 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present application.

FIG. 3 is a diagram showing an example of a user plane protocol stack and a control plane protocol stack for communication between a base station and a core network and a UE according to the present application.

FIG. 4 is a diagram illustrating an example of carrier aggregation according to the content of the present application.

Figure 5 is a diagram illustrating an example of a protocol architecture for carrier aggregation using two radio link control (RLC) entities according to the present disclosure.

6 is a diagram illustrating an example of signaling associated with using multiple RLC entities for multiple bit schemes in accordance with the present disclosure.

FIG. 7 is a diagram showing an example of the structure of an RLC protocol data unit including an unavailable state according to the present application.

FIG. 8 is a diagram illustrating an exemplary process, eg, performed by a wireless communication device, in accordance with the teachings of the present disclosure.

9 is a diagram of an exemplary apparatus for wireless communication in accordance with the present disclosure.

FIG. 10 is a diagram illustrating an exemplary process performed, for example, by a wireless communication device in accordance with the teachings of the present disclosure. .

Domestic deposit information (please note in order of depositor, date, and number) none Overseas storage information (please note in order of storage country, institution, date, and number) none

600: instance

605: Operation

610: Operation

615: Operation

620: Operation

625: Operation

630: communication

635: communication

640: Operation

645: Operation

Claims (30)

A wireless communication device for wireless communication, comprising: a memory; and one or more processors, coupled to the memory, configured to: establishing a first set of carriers of a carrier aggregation (CA) configuration, wherein the first set of carriers is associated with a first configuration; establishing a second set of carriers of the CA configuration, wherein the second set of carriers is associated with a second configuration; receiving information indicative of a first set of radio link control (RLC) parameters for the first configuration and a second set of RLC parameters for the second configuration; using the first set of RLC parameters to perform an RLC function for a first communication on the first set of carriers; and The RLC function is performed using the second set of RLC parameters for a second communication on the second set of carriers, wherein the first communication and the second communication are associated with a radio bearer. The wireless communication device as claimed in claim 1, wherein the one or more processors are further configured to perform a PDCP function for the first communication and the second communication. The wireless communication device as claimed in claim 2, wherein the PDCP functions for the first communication and the second communication are performed by a single PDCP entity. The wireless communication device of claim 1, wherein for establishing the first set of carriers, the one or more processors are configured to establish a first RLC entity associated with the first configuration, and wherein for establishing the For a second set of carriers, the one or more processors are configured to establish a second RLC entity associated with the second configuration. The wireless communication device as claimed in claim 4, wherein the RLC function used for the first communication is associated with a first RLC entity, and the RLC function used for the second communication is associated with the second RLC entity linked. The wireless communication device as claimed in claim 4, wherein the one or more processors are further configured to: A Packet Data Convergence Protocol (PDCP) Control Protocol Data Unit (PDU) is transmitted on a selected one of the first RLC entity and the second RLC entity. The wireless communication device of claim 4, wherein traffic of the first communication or the second communication is configured to be split between the first RLC entity and the second RLC entity. The wireless communication device as claimed in claim 1, wherein the RLC function is executed in parallel for the first group of carriers and for the second group of carriers. The wireless communication device as claimed in claim 1, wherein the first communication or the second communication is via the radio bearer, wherein the radio bearer is at least one of a data radio bearer or a signaling radio bearer. The wireless communication device as claimed in claim 9, wherein the first communication and the second communication are carried by the radio. The wireless communication device as claimed in claim 1, wherein the RLC function is associated with one of an acknowledged mode or an unacknowledged mode. The wireless communication device as claimed in claim 1, wherein the RLC function is based at least in part on an RLC protocol data unit (PDU), and wherein the RLC PDU includes an indication of whether the RLC-PDU is associated with the first configuration or with the A field associated with the second configuration. The wireless communication device of claim 1, wherein the RLC function is a reassembly function, and wherein the reassembly function is based at least in part on a first sequence number (SN) associated with the first configuration and associated with the second Two configurations are associated for a second set of SNs. The wireless communication device as claimed in claim 13, wherein the one or more processors are further configured to: sending a status report for an RLC protocol data unit (PDU) based at least in part on whether the RLC protocol data unit (PDU) is associated with the first set of SNs or a selected set of SNs in the second set of SNs, wherein the status The reporting is specific to a configuration associated with the selected set of SNs, and wherein the status reporting is based at least in part on a polling message associated with the configuration or a reassembly timer associated with the configuration. The wireless communication device as claimed in claim 1, wherein the one or more processors are further configured to: A status report is sent for an RLC protocol data unit (PDU) received on the first set of carriers, wherein the status report indicates that a status for the second set of carriers is unavailable. The wireless communication device of claim 15, wherein the status report for the RLC PDU indicates a negative acknowledgment for the RLC-PDU when a reassembly timer for the second set of carriers is valid, wherein the status Reporting indicates that the status for the second group of carriers is unavailable based at least in part on the reorganization timer being valid for the second group of carriers, wherein the status report indicates that for all RLCs received on the first group of carriers an acknowledgment of the PDU, and wherein the one or more processors are further configured to: A reassembly function associated with the RLC PDU is performed. The wireless communication device as claimed in claim 16, wherein the one or more processors are further configured to: After the reassembly timer has elapsed, sending another status report indicating a negative acknowledgment for the second set of carriers, wherein if all RLC PDUs on the second set of carriers were successfully received, then for An acknowledgment of all RLC PDUs on the second set of carriers is configured to be sent based at least in part on a poll associated with the second set of carriers. The wireless communication device of claim 15, wherein the status report includes a field for distinguishing whether the status report indicates a negative acknowledgment or a status not available. The wireless communications device of claim 15, wherein the status report indicates all sequence numbers up to a highest acknowledged sequence number associated with the second set of carriers except unavailable or negatively acknowledged sequence numbers of a confirmation. The wireless communication device as claimed in claim 1, wherein the one or more processors are further configured to: sending a status report for an RLC protocol data unit (PDU), wherein for at least one of the first set of carriers or the second set of carriers, the status report includes one or more negative acknowledgments, one or more acknowledgments, and An indication that a state is unavailable. The wireless communication device according to claim 1, wherein the first configuration or the second configuration indicates at least one of the following items: a duplex configuration, a schedule delay, a digital scheme, a frequency range, or - Uplink/downlink time slot allocation. The wireless communication device as claimed in claim 1, wherein the one or more processors are further configured to: establishing a third set of carriers of the CA configuration, wherein the third set of carriers is associated with a third configuration; and A third set of RLC parameters is used to perform the RLC function for a third communication on the third set of carriers associated with the radio bearer. A user equipment (UE) for wireless communication, comprising: a memory; and one or more processors, coupled to the memory, configured to: establishing a first set of carriers of a carrier aggregation (CA) configuration, wherein the first set of carriers is associated with a first configuration; establishing a second set of carriers of the CA configuration, wherein the second set of carriers is associated with a second configuration; and A status report is sent indicating a status for the second set of carriers is unavailable based at least in part on a reassembly timer for the first set of carriers. The UE of claim 23, wherein the status report indicates for a A negative acknowledgment of an RLC protocol data unit (PDU) based at least in part on the reassembly timer not elapsed for the second set of carriers, the status report indicating that the status for the second set of carriers is unavailable, wherein the The status report indicates an acknowledgment for all RLC PDUs received on the first set of carriers, and wherein the one or more processors are further configured to: A reassembly function associated with the RLC PDU is performed. The UE of claim 24, wherein the one or more processors are further configured to: after the reassembly timer for the second set of carriers has elapsed, based on failure to receive one or more RLC PDUs on the second set of carriers within the reassembly timer for the second set of carriers, sending another a status report, the other status report indicating a negative acknowledgment for the second set of carriers, wherein if all RLC PDUs on the second set of carriers were successfully received, then for all the RLC PDUs on the second set of carriers An acknowledgment is configured to be sent based at least in part on polling associated with the second set of carriers. The UE of claim 23, wherein the status report includes a field to distinguish whether the status report indicates a negative acknowledgment or a status is unavailable. The UE of claim 23, wherein the status report indicates a for all sequence numbers up to a highest acknowledged sequence number associated with the second set of carriers except for unavailable or negatively acknowledged sequence numbers confirm. The UE of claim 23, wherein for at least one of the first set of carriers or the second set of carriers, the status report includes one or more negative acknowledgments, one or more acknowledgments, and information about a status being unavailable an instruction. A method of wireless communication performed by a wireless communication device, comprising the steps of: establishing a first set of carriers of a carrier aggregation (CA) configuration, wherein the first set of carriers is associated with a first configuration; establishing a second set of carriers of the CA configuration, wherein the second set of carriers is associated with a second configuration; receiving information indicative of a first set of radio link control (RLC) parameters for the first configuration and a second set of RLC parameters for the second configuration; using the first set of RLC parameters to perform an RLC function for a first communication on the first set of carriers; and The RLC function is performed using the second set of RLC parameters for a second communication on the second set of carriers, wherein the first communication and the second communication are associated with a radio bearer. A method of wireless communication performed by a user equipment (UE), comprising the steps of: establishing a first set of carriers of a carrier aggregation (CA) configuration, wherein the first set of carriers is associated with a first configuration; establishing a second set of carriers of the CA configuration, wherein the second set of carriers is associated with a second configuration; and A status report is sent indicating that a status for the second set of carriers is unavailable based at least in part on a reassembly timer for the first set of carriers.

Images