Method and apparatus for connected mode discontinuous reception (CDRX) in carrier aggregation mode with hybrid parameter sets

Abstract

Disclosed are techniques for enabling a user equipment (UE) operating in a carrier aggregation mode to use different connected mode discontinuous reception (CDRX) configurations for different sets of component carriers associated with different groups of parameter sets. For example, in frequency 1 (FR1) plus frequency 2 (FR2) carrier aggregation (i.e., one or more FR1 component carriers and one or more FR2 component carriers), CDRX can be configured for FR1 differently than for FR2. In inter-band carrier aggregation (i.e., one or more component carriers in one band and one or more component carriers in another band), CDRX can be configured per band. For mixed parameter set carrier aggregation (i.e., one or more component carriers with a first parameter set and one or more component carriers with a different parameter set), CDRX can be configured per cell group, where each cell group contains a single parameter set or a mixed parameter set.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims the benefit of U.S. Provisional Application No. 62 / 879,954, filed on July 29, 2019, entitled “CONNECTED MODE DISCONTINUOUS RECEPTION (CDRX) IN CARRIER AGGREGATION MODE WITH MIXED NUMEROLOGIES,” and U.S. Non-Provisional Application No. 16 / 940,177, filed on July 27, 2020, entitled “CONNECTED MODE DISCONTINUOUS RECEPTION (CDRX) IN CARRIER AGGREGATION MODE WITH MIXED NUMEROLOGIES,” both of which are assigned to the assignee of this application and are expressly incorporated herein by reference in their entirety.

[0003] Public background

[0004] 1. Public Domain

[0005] Aspects of the present disclosure generally relate to wireless communications and the like.

[0006] 2. Description of related technologies

[0007] Wireless communication systems have evolved over several generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G networks), third generation (3G) high-speed data wireless service with Internet capabilities, and fourth generation (4G) services (e.g., Long Term Evolution (LTE), WiMax). There are many different types of wireless communication systems in use today, including cellular and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), and the like.

[0008] The fifth generation (5G) mobile standard requires higher data transmission speeds, a greater number of connections and better coverage, among other improvements. According to the Next Generation Mobile Network Alliance, the 5G standard (also referred to as "New Radio" or "NR") is designed to provide tens of megabits per second to each of tens of thousands of users, and 1 gigabit per second to dozens of employees in an office floor. Hundreds of thousands of simultaneous connections should be supported to support large sensor deployments. Therefore, the spectrum efficiency of 5G mobile communications should be significantly enhanced compared to the current 4G / LTE standards. In addition, signaling efficiency should be improved and waiting time should be significantly reduced compared to current standards.

[0009] Overview

[0010] A simplified summary of one or more aspects disclosed herein is given below. Thus, the following summary should neither be considered an exhaustive overview of all contemplated aspects, nor should the following summary be considered to identify key or decisive elements related to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the sole purpose of the following summary is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a simplified form prior to the detailed description given below.

[0011] The present disclosure provides techniques for enabling a user equipment (UE) operating in a carrier aggregation mode to use different connected mode discontinuous reception (CDRX) configurations for different sets of component carriers associated with different groups of parameter sets. For example, in frequency 1 (FR1) plus frequency 2 (FR2) carrier aggregation (i.e., one or more FR1 component carriers and one or more FR2 component carriers), a different CDRX can be configured for FR1 than for FR2. In inter-band carrier aggregation (i.e., one or more component carriers in one band and one or more component carriers in another band), CDRX can be configured per band. For mixed parameter set carrier aggregation (i.e., one or more component carriers with a first parameter set and one or more component carriers with a different parameter set), CDRX can be configured per cell group, where each cell group contains a single parameter set or a mixed parameter set.

[0012] In one aspect, a wireless communication method performed by a UE operating in a carrier aggregation mode includes: communicating with a base station according to a first set of CDRX parameters defined in absolute time for a first set of component carriers associated with a first set of parameters; and communicating with the base station according to a second set of CDRX parameters defined in absolute time for a second set of component carriers associated with a second set of parameters.

[0013] In one aspect, an apparatus for wireless communication includes at least one receiver of a UE configured to operate in a carrier aggregation mode, the at least one receiver configured to: communicate with a base station according to a first set of CDRX parameters defined in absolute time for a first set of component carriers associated with a first set of parameter sets; and communicate with the base station according to a second set of CDRX parameters defined in absolute time for a second set of component carriers associated with a second set of parameter sets.

[0014] In one aspect, a UE configured to operate in a carrier aggregation mode includes: a device for communicating with a base station according to a first set of CDRX parameters defined in absolute time for a first set of component carriers associated with a first set of parameter sets; and a device for communicating with the base station according to a second set of CDRX parameters defined in absolute time for a second set of component carriers associated with a second set of parameter sets.

[0015] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions for wireless communications includes computer-executable instructions including: at least one instruction to instruct a UE operating in a carrier aggregation mode to communicate with a base station according to a first set of CDRX parameters defined in absolute time for a first set of component carriers associated with a first set of parameters;

[0016] At least one instruction instructing the UE to communicate with the base station according to a second set of CDRX parameters defined in absolute time for a second set of component carriers associated with a second set of parameters.

[0017] Other objects and advantages associated with the various aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings are presented to aid in describing various aspects of the disclosure and are provided solely for the purpose of illustrating these aspects and not limiting thereof.

[0020] Figure 1

[0013] An exemplary wireless communication system in accordance with aspects of the present disclosure is illustrated.

[0021] Figure 2A and 2B

[0013] Example wireless network structures are illustrated in accordance with aspects of the present disclosure.

[0022] Figures 3A to 3C is a simplified block diagram of several sample aspects of components that may be employed in a wireless communication node and configured to support communications as taught herein.

[0023] Figure 3Dis a block diagram illustrating an exemplary transceiver in accordance with aspects of the present disclosure.

[0024] Figure 4A and 4B is a diagram illustrating example frame structures and channels within these frame structures in accordance with aspects of the present disclosure.

[0025] Figures 5A to 5D Exemplary discontinuous reception (DRX) configurations in accordance with aspects of the present disclosure are illustrated.

[0026] Fig. 6A and 6B Exemplary DRX configurations in accordance with aspects of the present disclosure are illustrated.

[0027] Figure 7 and 8

[0013] Exemplary methods of wireless communications in accordance with aspects of the present disclosure are illustrated.

[0028] Fig. 9 is a conceptual data flow diagram illustrating the flow of data between different devices / components in an exemplary apparatus according to aspects of the present disclosure.

[0029] Fig.10 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system according to aspects of the present disclosure.

[0030] Fig.11 is a diagram illustrating another example of a hardware implementation for an apparatus employing a processing system according to aspects of the present disclosure.

[0031] Detailed Description

[0032] The present disclosure provides techniques for enabling a UE operating in a carrier aggregation mode to use different CDRX configurations (referred to herein as "multi-CDRX") for different sets of component carriers associated with different groups of parameter sets. For example, in FR1 plus FR2 carrier aggregation (i.e., one or more FR1 component carriers and one or more FR2 component carriers), a different CDRX may be configured for FR1 than for FR2. In inter-band carrier aggregation (i.e., one or more component carriers in one band and one or more component carriers in another band), CDRX may be configured per band. For mixed parameter set carrier aggregation (i.e., one or more component carriers with a first parameter set and one or more component carriers with a different parameter set), CDRX may be configured per cell group, where each cell group contains a single parameter set or a mixed parameter set.

[0033] These and other aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. In addition, well-known elements in the present disclosure will not be described in detail or will be omitted to avoid obscuring the relevant details of the present disclosure.

[0034] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or superior to other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.

[0035] Those skilled in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.

[0036] In addition, many aspects are described in the form of a sequence of actions performed by, for example, elements of a computing device. It will be appreciated that the various actions described herein can be performed by a dedicated circuit (e.g., an application specific integrated circuit (ASIC)), by program instructions being executed by one or more processors, or by a combination of the two. In addition, the sequence of actions described herein may be considered to be fully embodied in any form of non-transient computer-readable storage medium, which stores a corresponding set of computer instructions that, upon execution, will cause or instruct the associated processor of the device to perform the functionality described herein. Thus, various aspects of the present disclosure may be embodied in several different forms, all of which have been conceived to fall within the scope of the claimed subject matter. In addition, for each aspect described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0037] As used herein, the terms "user equipment" (UE) and "base station" are not intended to be dedicated to or otherwise limited to any particular radio access technology (RAT), unless otherwise specified. In general, a UE can be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a tracking device, a wearable device (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) head-mounted device, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate on a wireless communication network. A UE can be mobile or can be stationary (e.g., at certain times) and can communicate with a radio access network (RAN). As used herein, the term "UE" can be interchangeably referred to as an "access terminal" or "AT", "client device", "wireless device", "subscriber equipment", "subscriber terminal", "subscriber station", "user terminal" or UT, "mobile device", "mobile terminal", "mobile station", or variations thereof. In general, a UE can communicate with a core network via a RAN, and through the core network, the UE can connect to external networks (such as the Internet) and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) network (eg, based on IEEE 802.11, etc.), and the like.

[0038] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which the base station is deployed, and may be alternatively referred to as an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be primarily used to support wireless access by a UE, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may provide pure edge node signaling functions, while in other systems, a base station may provide additional control and / or network management functions. The communication link by which a UE may send a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station may send a signal to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0039] The term "base station" may refer to a single physical transmit receive point (TRP) or may refer to multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be a base station antenna corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of a base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be a serving base station that receives measurement reports from a UE and a neighbor base station whose reference RF signal (or "reference signal" for short) the UE is measuring. Since the TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmissions from or receptions at a base station should be understood as references to the specific TRP of that base station.

[0040] In some implementations supporting UE positioning, the base station may not support wireless access for the UE (e.g., may not support data, voice, and / or signaling connections with respect to the UE), but may instead transmit reference signals to be measured by the UE to the UE, and / or may receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning tower (e.g., in the case of transmitting signals to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring signals from the UE).

[0041] "RF signals" include electromagnetic waves of a given frequency that transmit information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same RF signal transmitted on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, RF signals may also be referred to as "wireless signals" or simply "signals", where it is clear from the context that the term "signal" refers to either wireless signals or RF signals.

[0042] According to various aspects, Figure 1An exemplary wireless communication system 100 is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to an NR network), or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, and the like.

[0043] Each base station 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through a backhaul link 122, and connect to one or more location servers 172 (which may be part of the core network 170 or may be external to the core network 170) through the core network 170. In addition to other functions, the base stations 102 may also perform functions related to the delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and one or more of the delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / 5GC) over a backhaul link 134 (which may be wired or wireless).

[0044] Base stations 102 may communicate wirelessly with UEs 104. Each base station 102 may provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells may be supported by base stations 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a certain frequency resource, referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and may be associated with an identifier (e.g., a physical cell identifier (PCI), a virtual cell identifier (VCI), a cell global identifier (CGI)) to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access to different types of UEs. Since a cell is supported by a specific base station, the term "cell" may refer to either or both of a logical communication entity and a base station supporting the logical communication entity, depending on the context. Additionally, because the TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to a geographic coverage area (e.g., a sector) of a base station in the sense that a carrier frequency may be detected and used for communications within a portion of the geographic coverage area 110.

[0045] Although the geographic coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (e.g., in a handoff region), some geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 110. For example, a small cell base station 102' may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB), which may provide service to a restricted group referred to as a closed subscriber group (CSG).

[0046] The communication link 120 between the base station 102 and the UE 104 may include an uplink (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than to the uplink).

[0047] The wireless communication system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with a WLAN station (STA) 152 via a communication link 154 in an unlicensed spectrum (e.g., 5 GHz). When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen-before-talk (LBT) procedure to determine whether a channel is available before communicating.

[0048] The small cell base station 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed spectrum as that used by the WLAN AP 150. The small cell base station 102' employing LTE / 5G in the unlicensed spectrum may boost coverage and / or increase capacity of the access network. NR in the unlicensed spectrum may be referred to as NR-U. LTE in the unlicensed spectrum may be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0049] The wireless communication system 100 may further include a millimeter wave (mmW) base station 180, which can operate in mmW frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended downward to a 3 GHz frequency with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmitting and / or receiving) on ​​the mmW communication link 184 to compensate for the extremely high path loss and short range. In addition, it will be appreciated that in an alternative configuration, one or more base stations 102 may also use mmW or near mmW and beamforming for transmission. Accordingly, it will be appreciated that the foregoing explanation is merely an example, and should not be construed as limiting the various aspects disclosed herein.

[0050] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Conventionally, when a network node (e.g., a base station) broadcasts an RF signal, the network node broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal. For example, a network node can use an antenna array (referred to as a "phased array" or "antenna array") that generates a beam of RF waves, and the beam of the RF wave can be "guided" to point in different directions without actually moving the antennas. Specifically, the RF current from the transmitter is fed to the individual antennas in the correct phase relationship so that the radio waves from the separate antennas are added together in the desired direction to increase the radiation, and canceled in the undesired direction to suppress the radiation.

[0051] The transmit beams can be quasi-colocated, which means that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the transmit antennas of the network nodes themselves are physically colocated. In NR, there are four types of quasi-colocation (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived from information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0052] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, a receiver may increase the gain setting of an antenna array and / or adjust the phase setting of an antenna array in a particular direction to amplify (e.g., increase its gain level) the RF signal received from that direction. Thus, when a receiver is referred to as beamforming in a certain direction, this means that the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction for all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), etc.) for the RF signal received from that direction.

[0053] The receive beams may be spatially correlated. The spatial relationship means that the parameters of the transmit beam for the second reference signal may be derived from information about the receive beam of the first reference signal. For example, the UE may receive one or more reference downlink reference signals (e.g., positioning reference signal (PRS), tracking reference signal (TRS), phase tracking reference signal (PTRS), cell-specific reference signal (CRS), channel state information reference signal (CSI-RS), primary synchronization signal (PSS), secondary synchronization signal (SSS), synchronization signal block (SSB), etc.) from a base station using a specific receive beam. The UE may then form a transmit beam based on the parameters of the receive beam for sending one or more uplink reference signals (e.g., uplink positioning reference signal (UL-PRS), sounding reference signal (SRS), demodulation reference signal (DMRS), PTRS, etc.) to the base station.

[0054] Note that depending on the entity forming the "downlink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to transmit a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam for receiving downlink reference signals. Similarly, depending on the entity forming the "uplink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, the uplink beam is an uplink receive beam, and if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0055] In 5G, the spectrum in which wireless nodes (e.g., base stations 102 / 180, UEs 104 / 182) operate is divided into multiple frequency ranges: FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and on the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common control channels and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured once an RRC connection is established between the UE 104 and the anchor carrier, and can be used to provide additional radio resources. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, signaling information and signals that are UE-specific may not be present in the secondary carrier, because both the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. This is also true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. For example, this is done to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier that a base station is using for communication, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

[0056] For example, still referring to Figure 1, one of the frequencies utilized by the macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCells"). In carrier aggregation, the base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100 MHz) bandwidth per carrier, with up to a total of Yx MHz (x component carriers) in each direction for transmission. The component carriers may or may not be adjacent to each other in the spectrum. The allocation of carriers may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than the uplink). Simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a two-fold increase in data rate (i.e., 40 MHz) compared to the data rate obtained by a single 20 MHz carrier.

[0057] In order to operate on multiple carrier frequencies, the base station 102 / UE 104 is equipped with multiple receivers and / or transmitters. For example, UE 104 may have two receivers, namely "receiver 1" and "receiver 2", where "receiver 1" is a multi-band receiver that can be tuned to band (i.e., carrier frequency) 'X' or band 'Y', and "receiver 2" is a single-band receiver that can be tuned to only band 'Z'. In this example, if UE 104 is being served in band 'X', band 'X' will be referred to as the PCell or active carrier frequency, and "receiver 1" will need to tune from band 'X' to band 'Y' (SCell) to measure band 'Y' (and vice versa). In contrast, regardless of whether the UE 104 is being served in band 'X' or band 'Y', due to the separate "receiver 2", the UE 104 can measure band 'Z' without interrupting service on band 'X' or band 'Y'.

[0058] The wireless communication system 100 may further include a UE 164, which may communicate with the macrocell base station 102 over the communication link 120 and / or communicate with the mmW base station 180 over the mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0059] The wireless communication system 100 may further include one or more UEs (such as UE 190) that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “side links”). Figure 1 In the example of FIG. 1 , UE 190 has a D2D P2P link 192 with a UE 104 connected to a base station 102 (e.g., UE 190 can indirectly obtain cellular connectivity therefrom), and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity therefrom). In an example, D2D P2P links 192 and 194 can use any well-known D2D RAT (such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), etc.) to support.

[0060] According to various aspects, Figure 2A An example wireless network structure 200 is illustrated. For example, 5GC 210 (also referred to as Next Generation Core (NGC)) can be functionally viewed as control plane functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane functions 212 (e.g., UE gateway functions, access to data networks, Internet Protocol (IP) routing, etc.), which operate in coordination to form a core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect gNB 222 to 5GC 210, in particular to control plane functions 214 and user plane functions 212. In an additional configuration, ng-eNB 224 may also be connected to 5GC 210 via NG-C 215 to control plane functions 214 and NG-U 213 to user plane functions 212. In addition, ng-eNB 224 may communicate directly with gNB 222 via backhaul connection 223. In some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include both one or more ng-eNBs 224 and one or more gNBs 222. The gNB 222 or the ng-eNB 224 may communicate with the UE 204 (e.g., Figure 1204). Another optional aspect may include a location server 230 that may be in communication with the 5GC 210 to provide location assistance for the UE 204. The location server 230 may be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules extended across multiple physical servers, etc.), or alternatively may each correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204, which may be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). In addition, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network.

[0061] According to various aspects, Figure 2B Another example wireless network structure 250 is illustrated. For example, the 5GC 260 can be functionally viewed as a control plane function (provided by the access and mobility management function (AMF) 264) and a user plane function (provided by the user plane function (UPF) 262), which operate in coordination to form a core network (i.e., the 5GC 260). The user plane interface 263 and the control plane interface 265 connect the ng-eNB 224 to the 5GC 260, in particular to the UPF 262 and the AMF 264, respectively. In an additional configuration, the gNB 222 may also be connected to the 5GC 260 via a control plane interface 265 to the AMF 264 and a user plane interface 263 to the UPF 262. In addition, the ng-eNB 224 may communicate directly with the gNB 222 via a backhaul connection 223 with or without gNB direct connectivity to the 5GC 260. In some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include both one or more ng-eNBs 224 and one or more gNBs 222. The gNB 222 or the ng-eNB 224 may communicate with the UE 204 (e.g., Figure 1 The base stations of the new RAN 220 communicate with the AMF 264 via the N2 interface and communicate with the UPF 262 via the N3 interface.

[0062] The functions of AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between UE 204 and session management function (SMF) 266, transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between UE 204 and short message service function (SMSF) (not shown), and security anchor functionality (SEAF). AMF 264 also interacts with authentication server function (AUSF) (not shown) and UE 204, and receives intermediate keys established as a result of the UE 204 authentication process. In the case of authentication based on UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), AMF 264 retrieves security materials from AUSF. The functions of AMF 264 also include security context management (SCM). SCM receives keys from SEAF, which are used by SCM to derive keys that vary from access network to access network. The functionality of AMF 264 also includes: location service management for regulatory services, transmission of location service messages between UE 204 and location management function (LMF) 270 (which acts as location server 230), transmission of location service messages between new RAN 220 and LMF 270, allocation of EPS bearer identifiers for interworking with Evolved Packet System (EPS), and notification of mobility events for UE 204. In addition, AMF 264 also supports the functionality of non-3GPP access networks.

[0063] The functions of the UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node. The UPF 262 may also support the transmission of location service messages on the user plane between the UE 204 and a location server (such as a secure user plane location (SUPL) location platform (SLP) 272).

[0064] The functions of SMF 266 include session management, UE IP address allocation and management, selection and control of user plane functions, traffic steering configuration for routing traffic to the correct destination at UPF 262, partial control of policy implementation and QoS, and downlink data notification. The interface that SMF 266 uses to communicate with AMF 264 is called the N11 interface.

[0065] Another optional aspect may include an LMF 270 that can be in communication with the 5GC 260 to provide location assistance for the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules extended across multiple physical servers, etc.), or alternatively can each correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). The SLP 272 may support similar functionality as the LMF 270, but the LMF 270 may communicate with the AMF 264, the new RAN 220, and the UE 204 on the control plane (e.g., using interfaces and protocols intended to convey signaling messages rather than voice or data), and the SLP 272 may communicate with the UE 204 and external clients (e.g., using protocols intended to carry voice and / or data, such as the Transmission Control Protocol (TCP) and / or IP) on the user plane. Figure 2B Communicate with the

[0066] In one aspect, the LMF 270 and / or SLP 272 may be integrated into a base station, such as a gNB 222 and / or ng-eNB 224. When integrated into a gNB 222 and / or ng-eNB 224, the LMF 270 and / or SLP 272 may be referred to as a "location management component" or "LMC." However, as used herein, references to the LMF 270 and SLP 272 include both the case where the LMF 270 and SLP 272 are components of a core network (e.g., 5GC 260) and the case where the LMF 270 and SLP 272 are components of a base station.

[0067] Figure 3A , 3B3C illustrate several exemplary components (represented by corresponding boxes) that may be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270) to support file transfer operations as taught herein. It will be appreciated that these components may be implemented in different types of devices (e.g., in an ASIC, in a system on a chip (SoC), etc.) in different implementations. The illustrated components may also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described to provide similar functionality. In addition, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0068] UE 302 and base station 304 each include a wireless wide area network (WWAN) transceiver 310 and 350, respectively, configured to communicate via one or more wireless communication networks (not shown) (such as NR network, LTE network, GSM network, etc.). WWAN transceivers 310 and 350 can be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc.) on a wireless communication medium of interest (e.g., a certain set of time / frequency resources in a specific spectrum) via at least one designated RAT (e.g., NR, LTE, GSM, etc.). WWAN transceivers 310 and 350 can be configured in various ways according to the designated RAT to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.), and vice versa, respectively, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively.

[0069] In at least some cases, the UE 302 and the base station 304 also include wireless local area network (WLAN) transceivers 320 and 360, respectively. The WLAN transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, for communicating via at least one designated RAT (e.g., WiFi, LTE-D, The WLAN transceivers 320 and 360 may be configured in various ways according to the specified RAT to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.), and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the WLAN transceivers 320 and 360 include one or more transmitters 324 and 364 to transmit and encode signals 328 and 368, respectively, and include one or more receivers 322 and 362 to receive and decode signals 328 and 368, respectively.

[0070] The transceiver circuitry including at least one transmitter and at least one receiver may include an integrated device (e.g., a transmitter circuit and a receiver circuit implemented as a single communication device) in some implementations, may include separate transmitter devices and separate receiver devices in some implementations, or may be implemented in other ways in other implementations. In one aspect, the transmitter may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366) such as an antenna array, which permits the respective device to perform transmit "beamforming" as described herein. Similarly, the receiver may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366) such as an antenna array, which permits the respective device to perform receive beamforming as described herein. In one aspect, the transmitter and receiver may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the respective device can only receive or transmit at a given time, but not both at the same time. The wireless communication devices of UE 302 and / or base station 304 (eg, one or both of transceivers 310 and 320 and / or one or both of transceivers 350 and 360) may also include a network listening module (NLM) or the like for performing various measurements.

[0071] In at least some cases, UE 302 and base station 304 also include satellite positioning system (SPS) receivers 330 and 370. SPS receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, for receiving SPS signals 338 and 378, respectively, such as global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian regional navigation satellite system (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. SPS receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing SPS signals 338 and 378, respectively. SPS receivers 330 and 370 request information and operations from other systems as appropriate, and perform the necessary calculations to determine the location of UE 302 and base station 304 using measurements obtained by any suitable SPS algorithm.

[0072] The base station 304 and the network entity 306 each include at least one network interface 380 and 390, respectively, for communicating with other network entities. For example, the network interfaces 380 and 390 (e.g., one or more network access ports) may be configured to communicate with one or more network entities via a wired backhaul connection or a wireless backhaul connection. In some aspects, the network interfaces 380 and 390 may be implemented as transceivers configured to support wired signal communication or wireless signal communication. The communication may involve, for example, sending and receiving: messages, parameters, and / or other types of information.

[0073] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with operations as disclosed herein. UE 302 includes processor circuitry that implements a processing system 332 for providing, for example, functionality related to wireless communications, and for providing other processing functionality. Base station 304 includes a processing system 384 for providing, for example, functionality related to wireless communications, as disclosed herein, and for providing other processing functionality. Network entity 306 includes a processing system 394 for providing, for example, functionality related to wireless communications, as disclosed herein, and for providing other processing functionality. In one aspect, processing systems 332, 384, and 394 may include, for example, one or more general purpose processors, multi-core processors, ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), or other programmable logic devices or processing circuitry.

[0074] UE 302, base station 304, and network entity 306 include memory circuitry that implements memory components 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). In some cases, UE 302, base station 304, and network entity 306 may include DRX components 342, 388, and 398, respectively. DRX components 342, 388, and 398, respectively, may be hardware circuits that are part of or coupled to processing systems 332, 384, and 394, respectively, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, DRX components 342, 388, and 398 may be external to processing systems 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the DRX components 342, 388, and 398 may be memory modules stored in the memory components 340, 386, and 396, respectively (e.g., Figures 3A-3C ), which, when executed by the processing systems 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein.

[0075] UE 302 may include one or more sensors 344 coupled to processing system 332 to provide movement and / or orientation information that is independent of motion data derived from signals received by WWAN transceiver 310, WLAN transceiver 320, and / or SPS receiver 330. As an example, sensor 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a 2D and / or 3D coordinate system.

[0076] In addition, the UE 302 includes a user interface 346 for providing indications to the user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when the user actuates a sensing device (such as a keypad, touch screen, microphone, etc.) Although not shown, the base station 304 and the network entity 306 may also include a user interface.

[0077] Referring to the processing system 384 in more detail, in the downlink, IP packets from the network entity 306 may be provided to the processing system 384. The processing system 384 may implement functionality for the RRC layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The processing system 384 may provide RRC layer functionality associated with system information (e.g., master information block (MIB), system information block (SIB)) broadcast, RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (ciphering, cipher decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through automatic repeat request (ARQ), concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0078] The transmitter 354 and the receiver 352 may implement layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 354 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine coding and modulation schemes and for spatial processing. The channel estimates may be derived from reference signals and / or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a corresponding spatial stream for transmission.

[0079] At UE 302, receiver 312 receives the signal through its corresponding antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides the information to processing system 332. Transmitter 314 and receiver 312 implement layer 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on the information to recover any spatial streams destined for UE 302. If there are multiple spatial streams destined for UE 302, they can be combined into a single OFDM symbol stream by receiver 312. Receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the signal constellation point most likely transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 304. These data and control signals are then provided to the processing system 332 that implements layer 3 and layer 2 functionality.

[0080] In the uplink, the processing system 332 provides demultiplexing between transport channels and logical channels, packet reassembly, encryption decoding, header decompression, and control signal processing to recover IP packets from the core network. The processing system 332 is also responsible for error detection.

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

[0082] Channel estimates derived by a channel estimator from a reference signal or feedback transmitted by base station 304 may be used by transmitter 314 to select appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by transmitter 314 may be provided to different antennas 316. Transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.

[0083] The uplink transmission is processed at the base station 304 in a manner similar to that described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to the processing system 384.

[0084] In the uplink, the processing system 384 provides demultiplexing between transport channels and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 302. The IP packets from the processing system 384 can be provided to the core network. The processing system 384 is also responsible for error detection.

[0085] For convenience, UE 302, base station 304 and / or network entity 306 may Figures 3A-3C 1 and 2. The illustrated example of a block diagram of a computer readable medium is shown to include various components that may be configured according to the various examples described herein. However, it will be appreciated that the illustrated blocks may have different functionality in different designs.

[0086] The various components of the UE 302, base station 304, and network entity 306 may communicate with one another over data buses 334, 382, ​​and 392, respectively. Figures 3A-3C The components of can be implemented in various ways. In some implementations, Figures 3A-3CThe components may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by the processor and memory components of UE 302 (e.g., by executing appropriate code and / or by appropriately configuring the processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and / or by appropriately configuring the processor components). In addition, some or all of the functionality represented by blocks 390 to 398 may be implemented by the processor and memory components of network entity 306 (e.g., by executing appropriate code and / or by appropriately configuring the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed by "UE", "by base station", "by positioning entity", etc. However, as will be appreciated, such operations, actions, and / or functions may actually be performed by specific components or combinations of components of the UE, base station, positioning entity, etc., such as processing systems 332, 384, 394, transceivers 310, 320, 350 and 360, memory components 340, 386 and 396, DRX components 342, 388 and 398, etc.

[0087] Figure 3D An exemplary architecture of a transceiver 381 capable of implementing carrier aggregation according to at least one aspect of the present disclosure is illustrated. The transceiver 381 may correspond to the WWAN transceiver 310 or the WLAN transceiver 320 of the UE 302 or the WWAN transceiver 350 or the WLAN transceiver 360 of the base station 304. The transceiver 381 may be coupled to the first antenna 303 and the second antenna 305. These antennas may correspond to the antennas 316 or 326 of the UE 302 or the antennas 356 or 366 of the base station 304.

[0088] Transceiver 381 includes receiver circuit system 341 and transmitter circuit system 351. Receiver circuit system 341 may correspond to receiver 312, 322, 352, or 362, and transmitter circuit system 351 may correspond to transmitter 314, 324, 354, or 364. Receiver circuit system 341 is capable of implementing carrier aggregation. Figure 3D In the example of FIG. 3 , the receiver circuit system 341 includes two radios 311 and 323 coupled to two antennas 303 and 305, respectively. Note that although Figure 3DOnly two antennas 303 and 305 and two radios 311 and 323 are illustrated, but it will be appreciated that there may be more than two antennas and two radios. Similar to the receiver circuitry 341, the transmitter circuitry 351 may also be capable of implementing carrier aggregation, but for simplicity, this is not shown. Figure 3D Shown in.

[0089] A transceiver (e.g., transceiver 381) typically includes a modem (e.g., modem 335) and a radio (e.g., radio 311 or 323). Broadly speaking, the radio handles selecting and converting RF signals to baseband or intermediate frequencies and converting RF signals to the digital domain. The modem is the rest of the transceiver.

[0090] See also Figure 3D , the radio 311 includes an amplifier 313, a mixer 315 (also referred to as a signal multiplier) for down-converting a signal, a frequency synthesizer 317 (also referred to as an oscillator) that provides a signal to the mixer 315, a baseband filter (BBF) 319, and an analog-to-digital converter (ADC) 321. Similarly, the radio 323 includes an amplifier 325, a mixer 327, a frequency synthesizer 329, a BBF 331, and an ADC 333. The ADCs 321 and 333 are coupled to a signal combiner / signal selector 337 of a modem 335, which is coupled to a demodulator 339 of the modem 335. The demodulator 339 is coupled to a packet processor 343. The demodulator 339 and the packet processor 343 provide a demodulated and processed single or multiple output signals to a communication controller and / or a processing system (e.g., processing system 332 or 384).

[0091] Note that not every component illustrated in FIG3 is required for system operation. For example, in a direct RF to baseband conversion receiver or any other direct conversion receiver (including certain software defined radio (SDR) implementations), the various components of the receiver circuit system 341 are not required, as is known in the art. In addition, although Figure 3D A single modem 335 is illustrated as being coupled to both radios 311 and 323, but it should be appreciated that each radio 311 and 323 may be coupled to a different modem and that the receiver circuitry 341 would therefore include the same number of radios and modems. Figure 3D Integrated transmitter circuitry 351 and receiver circuitry 341 (ie, transceiver 381) are illustrated, but in some implementations a UE or base station may include a separate transmitter device and a separate receiver device.

[0092] As mentioned above, carrier aggregation is a technique whereby a UE (e.g., any UE described herein) can receive and / or transmit on multiple carrier frequencies at the same time, thereby increasing downlink and uplink data rates. Thus, the UE can simultaneously tune to one carrier frequency (e.g., anchor carrier) using radio 311 and tune to a different carrier frequency (e.g., subcarrier) using radio 323. In addition, each radio 311 and 323 can be tunable to multiple different frequencies at a time.

[0093] Various frame structures may be used to support downlink and uplink transmissions between network nodes (eg, base stations and UEs). Figure 4A is a diagram 400 illustrating an example of a downlink frame structure in accordance with aspects of the present disclosure. Figure 4B is a diagram 430 illustrating an example of channels within a downlink frame structure in accordance with aspects of the present disclosure. Other wireless communication technologies may have different frame structures and / or different channels.

[0094] LTE and in some cases NR utilize OFDM on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency modulation, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15kHz, and the minimum resource allocation (resource block) can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0095] LTE supports a single parameter set (subcarrier spacing, symbol length, etc.). In contrast, NR may support multiple parameter sets (μ), for example, subcarrier spacing of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz or more may be available. Table 1 provided below lists some of the various parameters used for different NR parameter sets.

[0096]

[0097] Table 1

[0098] exist Figure 4A and 4B In the example of , a parameter set of 15 kHz is used. Thus, in the time domain, a 10 millisecond (ms) frame is divided into 10 equally sized subframes, each subframe is 1 ms, and each subframe includes one time slot. Figure 4A and 4B , time is represented horizontally (eg, on the X-axis), where time increases from left to right, and frequency is represented vertically (eg, on the Y-axis), where frequency increases (or decreases) from bottom to top.

[0099] A resource grid may be used to represent time slots, each of which includes one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into a plurality of resource elements (REs). An RE may correspond to one symbol length in the time domain and to one subcarrier in the frequency domain. Figure 4A and 4B In the parameter set of , for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0100] Some REs carry downlink reference (pilot) signals (DL-RS). DL-RS may include PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, etc. FIG. 4 illustrates an exemplary location of REs carrying DL-RS (labeled "R").

[0101] Figure 4B Examples of various channels within a downlink timeslot of a radio frame are illustrated. In NR, the channel bandwidth or system bandwidth is divided into multiple bandwidth parts (BWPs). A BWP is a group of contiguous PRBs selected from a contiguous subset of common RBs for a given parameter set for a given carrier. In general, a maximum value of 4 BWPs can be specified in the downlink and uplink. That is, the UE can be configured to have up to 4 BWPs on the downlink and up to 4 BWPs on the uplink. Only one BWP (uplink or downlink) can be active at a given time, which means that the UE can only receive or transmit on one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not contain the SSB.

[0102] Reference Figure 4B, the primary synchronization signal (PSS) is used by the UE to determine the subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the aforementioned DL-RS. The physical broadcast channel (PBCH) carrying the MIB can be logically grouped with the PSS and SSS to form an SSB (also referred to as SS / PBCH). The MIB provides the number of RBs in the downlink system bandwidth, and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information that is not transmitted through the PBCH (such as system information blocks (SIBs)), and paging messages.

[0103] The physical downlink control channel (PDCCH) carries downlink control information (DCI) in one or more control channel elements (CCEs), each CCE includes one or more RE group (REG) bundles (which can span multiple symbols in the time domain), each REG bundle includes one or more REGs, each REG corresponds to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The set of physical resources used to carry PDCCH / DCI is called a control resource set (CORESET) in NR. In NR, PDCCH is confined to a single CORESET and transmitted with its own DMRS. This enables UE-specific beamforming for PDCCH.

[0104] exist Figure 4B In the example of , there is one CORESET per BWP, and the CORESET spans three symbols in the time domain (although it could be just one symbol or two symbols). Unlike LTE control channels that occupy the entire system bandwidth, in NR, the PDCCH channel is localized to a specific region (i.e., CORESET) in the frequency domain. Thus, Figure 4B The frequency components of the PDCCH shown in FIG are illustrated as less than a single BWP in the frequency domain. Note that although the illustrated CORESETs are contiguous in the frequency domain, the CORESETs do not need to be contiguous. Additionally, the CORESETs may span less than three symbols in the time domain.

[0105] The DCI within the PDCCH carries information about uplink resource allocation (persistent and non-persistent) and a description of downlink data transmitted to the UE. Multiple (e.g., up to 8) DCIs can be configured in the PDCCH, and these DCIs can have one of a variety of formats. For example, there are different DCI formats for uplink scheduling, for non-MIMO downlink scheduling, for MIMO downlink scheduling, and for uplink power control. The PDCCH can be transmitted by 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or coding rates.

[0106] Even when there is no traffic transmitted from the network to the UE, the UE is expected to monitor every downlink subframe on the PDCCH. This means that the UE must always be "on" or active even when there is no traffic, because the UE cannot know exactly when the network will transmit data to it. However, being active all the time is a considerable power drain for the UE.

[0107] To address this issue, the UE can implement discontinuous reception (DRX) and / or connected mode discontinuous reception (CDRX) techniques. DRX and CDRX are mechanisms by which the UE enters a "sleep" mode during certain periods of time and "wakes up" during other periods of time. During the awake or active period, the UE checks to see if there is any data from the network, and if not, returns to sleep mode.

[0108] To implement DRX and CDRX, the UE and the network need to be synchronized. In the worst scenario, the network may try to send some data to the UE while the UE is in sleep mode, and the UE may wake up when there is no data to be received. To prevent such scenarios, the UE and the network should have a well-defined agreement on when the UE can be in sleep mode and when the UE should be awake / active. Note that DRX includes CDRX, and thus references to DRX refer to both DRX and CDRX, unless otherwise indicated.

[0109] The network (eg, serving cell) may use the RRC Connection Reconfiguration message (for CDRX) or the RRC Connection Setup message (for DRX) to configure the UE with DRX / CDRX timing. The network may signal the following parameters to the UE.

[0110]

[0111] Table 2

[0112] Figures 5A to 5D An exemplary DRX cycle in accordance with aspects of the present disclosure is illustrated. Figure 5AAn exemplary DRX cycle 500A is illustrated in which a long DRX cycle (the time from the start of one On Duration to the start of the next On Duration) is configured and no PDCCH is received during the cycle. Figure 5B An exemplary DRX cycle 500B is illustrated in which a long DRX cycle is configured and a PDCCH is received during the on duration 510 of the illustrated second DRX cycle. Note that the on duration 510 ends at time 512. However, based on the length of the DRX inactivity timer and the time at which the PDCCH is received, the time that the UE is awake / active ("active time") is extended to time 514. Specifically, when a PDCCH is received, the UE starts the DRX inactivity timer and remains in the active state until the timer expires (the timer is reset each time a PDCCH is received during the active time).

[0113] Figure 5C An exemplary DRX cycle 500C is illustrated in which a long DRX cycle is configured and a PDCCH and a DRX command MAC control element (MAC-CE) are received during the on duration 520 of the illustrated second DRX cycle. Note that due to the reception of the PDCCH at time 522 and the subsequent expiration of the DRX inactivity timer at time 524, the active time that started during the on duration 520 will normally end at time 524, as described above with reference to Figure 5B However, in Figure 5C In the example of , the active time is shortened to time 526 based on the time at which the DRX command MAC-CE instructing the UE to terminate the DRX inactivity timer and start the duration timer is received.

[0114] Figure 5D An exemplary DRX cycle 500D is illustrated in which both a long DRX cycle and a short DRX cycle are configured and no PDCCH is received during the cycle. Figure 5DIn the example of , the length of the DRX inactivity timer is three subframes, the length of the on duration timer is two subframes, the length of the short DRX cycle is five subframes, the length of the long DRX cycle is 10 subframes, the length of the DRX start offset is zero subframes, and the length of the DRX short cycle timer is three subframes. When CDRX is configured and the last DCI (i.e., PDCCH) has been received (e.g., SFN='0', subframe='0'), the UE starts the DRX inactivity timer and remains active until the DRX inactivity timer expires (e.g., SFN='0', subframe='3'). After the DRX inactivity timer expires, and if the UE is configured for a short DRX cycle, the short DRX cycle begins and the UE starts the DRX short cycle timer (e.g., SFN='0', subframe='5'). If no DCI (i.e., no PDCCH) is received before the DRX short cycle timer expires (e.g., SFN='1', subframe='9'), the long DRX cycle starts (e.g., SFN='2', subframe='0'). If any DCI (PDCCH) is received during the active time of any DRX cycle, the UE restarts the DRX inactivity timer and remains in the active state until it expires.

[0115] The active time of the DRX cycle is the time when the UE is considered to be monitoring the PDCCH. The active time may include the following times: the time when the start duration timer is running; the time when the DRX inactivity timer is running; the time when the DRX retransmission timer is running; the time when the MAC contention resolution timer is running; the time when a scheduling request has been sent on the physical uplink control channel (PUCCH) and is pending; the time when an uplink grant for a pending HARQ retransmission may occur and there is data in the corresponding HARQ buffer, the time when a PDCCH indicating a new transmission addressed to the UE's cellular radio network temporary identifier (C-RNTI) has not been received after successfully receiving a random access response (RAR) for a preamble not selected by the UE; and in non-contention-based random access, after receiving the RAR, the UE should be in the active state until the time when a PDCCH indicating a new transmission addressed to the UE's C-RNTI is received.

[0116] Note that the above timing is described in terms of subframes, but alternatively can be defined in terms of slots, milliseconds, etc. Currently, CDRX is defined per MAC entity even when carrier aggregation is implemented across different parameter sets (see Table 1). That is, the CDRX configuration is the same for each component carrier, regardless of the parameter set used on that carrier. For example, key parameters such as the DRX cycle, on-duration timer, and DRX inactivity timer are defined independently of the subcarrier spacing (SCS) on the component carrier. That is, they are defined in milliseconds rather than the number of slots or symbols. Table 3 illustrates various CDRX RRC parameters, their length units, and exemplary values.

[0117]

[0118] Table 3

[0119] As can be seen from Table 3, all timers except the DRX HARQ round trip time (RTT) timer and the DRX retransmission timer are defined independently of the SCS (in terms of symbol and slot length depending on the SCS). However, due to different parameter sets, there is no direct tradeoff between power saving and scheduling flexibility (for improving latency) for component carriers operating in different frequency ranges (such as FR1 and FR2). As such, for a UE in carrier aggregation mode, it would be beneficial to be able to apply one CDRX configuration to one component carrier and a different CDRX configuration to another component carrier (such as in FR1 plus FR2 carrier aggregation mode) to improve the UE's power consumption without sacrificing network-side scheduling latency.

[0120] Accordingly, the present disclosure provides techniques for enabling a UE to use multiple CDRX configurations (referred to herein as "multi-CDRX") when operating in a carrier aggregation mode. For example, in FR1 plus FR2 carrier aggregation (i.e., one or more FR1 component carriers and one or more FR2 component carriers), CDRX can be configured by frequency range. In inter-band carrier aggregation (i.e., one or more component carriers in one band and one or more component carriers in another band), CDRX can be configured by band. For mixed parameter set carrier aggregation (i.e., one or more component carriers with a first parameter set and one or more component carriers with a different parameter set), CDRX can be configured by cell group, where each cell group contains a single parameter set or a mixed parameter set.

[0121] There are at least two levels of independence between the CDRX configurations of different component carrier sets (e.g., component carrier sets in different frequency ranges, bands, or cell groups). As a first level of independence, the CDRX configurations can be completely independent. That is, all RRC parameters can be fully configurable per component carrier set, or only parameters not related to the SCS can be independent. The CDRX operations are completely independent within a component carrier set (similar to using different MAC entities). Note that in order to have complete independence, each component carrier set will need to have its own PUCCH configured.

[0122] As a second level of independence, the CDRX configurations may be partially independent. In this case, there may be independent parameters, but the DRX cycles are aligned. That is, the long DRX cycle in the CDRX parameters for one component carrier set will be a multiple of the other long DRX cycle in the CDRX parameters for another component carrier set. This is in Fig. 6A In other scenarios, there may be independent parameters and different CDRX configurations will have the same DRX cycle and offset (which means the start alignment of the on duration), but one set of CDRX parameters has a shorter on duration and inactivity timer than the other.

[0123] Fig. 6A An example of two partially independent CDRX configurations according to aspects of the present disclosure is illustrated. Fig. 6A In the example of , the on durations for a CDRX configuration 610 for FR2 and a CDRX configuration 620 for FR1 are shown. As can be seen, although the on durations for the CDRX configuration 610 for FR2 are shorter and more frequent than the on durations for the CDRX configuration 620 for FR1, the start of the on duration for the CDRX configuration 620 for FR1 starts at the start of every other on duration for the CDRX configuration 610 for FR2. As such, the length of the DRX cycle for the CDRX configuration 620 for FR1 is twice the length of the DRX cycle for the CDRX configuration 610 for FR2 (i.e., the multiple is '2'). Note that a longer DRX cycle will generally have a longer on duration, while a shorter DRX cycle will generally have a shorter on duration, as shown.

[0124] The benefit of aligning the start of different DRX cycles is that, while there may be separate RF components (e.g., radios 311, 323) for each frequency range, the baseband (e.g., modem 335) may still be shared. In terms of power savings and signaling efficiency, it is best for the UE to wake up both RF components together. In addition, the MAC entity is the same across different frequency ranges. In this way, different frequency ranges ( Fig. 6AFR1 and FR2 in the example can share the same PUCCH, making it easier to maintain HARQ processing and retransmissions.

[0125] Some independent CDRX configurations may have a common trigger using independent timers or have independent triggers. The different timers include drx-HARQ-RTT-timer DL, drx-HARQ-RTT-timer UL, drx-retransmission timer DL, drx-retransmission timer UL, drx-on duration timer, drx-inactivity timer, and drx-short cycle timer.

[0126] For a common trigger with independent timers, all component carrier sets become active (i.e., leave the inactive state) at the same time, e.g., based on an uplink grant (i.e., DCI format 0_0 or 0_1) in one component carrier set (e.g., FR1 component carriers). If one or more component carrier sets are already outside of their active time (e.g., FR2 component carriers), a certain offset may be allowed to prepare the radio to wake up for that component carrier set(s). Alternatively, those component carrier sets may start becoming active at the next on duration in that component carrier set. All component carrier sets become active during a pending scheduling request (SR) or a pending RAR.

[0127] Each component carrier set independently enters an inactive state (i.e., a closed state) for its own inactivity situation. That is, the active time of each component carrier set is based on the drx-on duration timer, drx-inactivity timer, drx-retransmission timer DL, and drx-retransmission timer UL timers for the component carrier set. In addition, the DRX command MAC-CE may be common to all component carrier sets, or may be applicable to the component carrier set receiving the MAC-CE, or may indicate one or more component carrier sets.

[0128] For independent triggering, each component carrier set becomes active based on an uplink grant or a downlink grant for the component carrier set. In one aspect, the grant may be a configured grant (i.e., semi-persistent scheduling). In this case, the trigger is based on a MAC PDU received via semi-persistent scheduling. In addition, the grant may be for a pending scheduling request or a pending RAR. A pending scheduling request affects a component carrier set in which a PUCCH (with a scheduling request) is received. A pending RAR affects a component carrier set in which a RACH is performed. Otherwise, the remaining aspects (such as each component carrier set entering an inactive state based on its own timer and the commonality of the DRX command MAC-CE (i.e., common to all component carrier sets, or component carrier sets receiving the MAC-CE, or component carrier sets indicated in the MAC-CE)) are the same, regardless of whether the trigger is common or independent. In addition, independent triggering can be used with both fully independent and partially independent CDRX configurations.

[0129] A UE in CDRX mode will occasionally need to handle non-periodic events (such as PUCCH and SRS transmissions). Non-periodic events are events that do not occur at regular intervals. Instead, non-periodic events may occur in response to certain events. For example, the UE may transmit channel state information (CSI) (on PUCCH) or SRS when requested by the base station, rather than at regular intervals. Such non-periodic events can be handled independently or jointly within a component carrier set. Regarding independent handling, in the current codeword, taking into account the received grant / assignment / DRX command MAC-CE / long DRX command MAC-CE and the sent scheduling request, if the MAC entity will not be in active time until, for example, 4ms before the codeword when evaluating all DRX active time conditions (as defined above), the UE does not transmit periodic SRS or semi-persistent SRS. Regarding PUCCH transmission, if CSI masking is set by upper layers, in the current symbol, the UE does not report CSI on PUCCH if the drx-on duration timer will not run until 4 ms before the symbol when evaluating all DRX active time conditions (as defined above) taking into account the received grant / assignment / DRX command MAC-CE / long DRX command MAC-CE. Otherwise, in the current symbol, the UE does not report CSI on PUCCH or semi-persistent CSI on the physical uplink shared channel (PUSCH) if the MAC entity will not be in active time until 4 ms before the symbol when evaluating all DRX active time conditions (as defined above) taking into account the received grant / assignment / DRX command MAC-CE / long DRX command MAC-CE and the sent SR. The MAC entity transmits HARQ feedback, aperiodic CSI on PUSCH and aperiodic SRS (when they are expected) regardless of whether the MAC entity is monitoring PDCCH. Independent handling of non-periodic events within a group can be implemented for fully independent CDRX configurations or partially independent CDRX configurations.

[0130] Joint treatment is applicable when there is a single PUCCH across all component carrier sets. In the current symbol, if the MAC entity is not in active time for all component carrier sets, or if the MAC entity is not in active time for a component carrier set with SRS, the UE does not transmit periodic SRS or semi-persistent SRS. If CSI masking is set by upper layers, in the current symbol, if the drx-on duration timer will not run for all component carrier sets, or if the drx-on duration timer will not run for a component carrier set with PUCCH, the UE does not report CSI on PUCCH. Otherwise, in the current symbol, if the MAC entity will not be in active time for all component carrier sets, or if the MAC entity will not be in active time for a component carrier set with PUCCH or semi-persistent CSI on PUSCH, the UE does not report CSI on PUCCH or semi-persistent CSI on PUSCH. Regardless of whether the MAC entity is monitoring the PDCCH (across component carrier sets), the MAC entity transmits HARQ feedback, aperiodic CSI on PUSCH, and aperiodic SRS (when they are expected).

[0131] The following is an example of dual CDRX in a FR1 plus FR2 carrier aggregation with a single PUCCH group. As mentioned above, CDRX is defined per MAC entity across carrier aggregations including different parameter sets. Currently, the CDRX configuration of the UE is shared even across FR1 and FR2. Certain parameters (such as DRX cycle, drx-on duration timer and drx-inactivity timer) are defined as values ​​independent of the SCS (i.e., defined in milliseconds, see Table 3). For both FR1 and FR2 component carriers, there is no direct tradeoff between power saving and scheduling flexibility (for reducing waiting time). As such, it would be beneficial to implement dual CDRX (i.e., CDRX per frequency range) for both FR1 and FR2 carrier aggregations.

[0132] Important CDRX parameters related to the power consumption of the UE include the drx-on duration duty cycle (i.e., together with the DRX cycle) and the drx-inactivity timer. For simplicity, the FR1 CDRX configuration and the FR2 CDRX configuration may share the same DRX cycle and offset, which means that the start of the on duration is aligned. However, the on duration and the inactivity timer may be independent, which means that the on duration and the inactivity timer of the FR2 CDRX configuration may be shorter than the on duration and the inactivity timer of the FR1 CDRX configuration. This is in Figure 6B6, where a CDRX configuration 650 for FR1 has the same DRX cycle and offset as a CDRX configuration 660 for FR2, but has a longer on-duration than the CDRX configuration 660 for FR2. As a specific example, the DRX long cycle may be 160 milliseconds, the drx-on-duration for FR1 may be 5 milliseconds, while the drx-on-duration for FR2 may be 1 millisecond, and the drx-inactivity timer for FR1 may be 100 milliseconds, while the drx-inactivity timer for FR2 may be 10 milliseconds.

[0133] Continuing with the dual CDRX in the FR1 plus FR2 carrier aggregation example, with respect to data handling, the FR1 and FR2 CDRX configurations can be independently triggered and have independent timers. With respect to independent triggering, each frequency range can become active based on a grant in that frequency range, each frequency range can become active based on a MAC PDU in an SPS in that frequency range, or only FR1 can become active during a pending scheduling request or a pending RAR. With respect to independent timers, each component carrier set (for FR1 and FR2) can independently enter a CDRX inactive state based on its own inactivity situation. More specifically, the active time of each component carrier set is independent per frequency range based on a drx-on duration timer, a drx-inactivity timer, a drx-retransmission timer DL, and a drx-retransmission timer UL. In addition, the timers are maintained independently. With respect to the reception of a DRX command MAC-CE, the DRX command MAC-CE will be common to each of FR1 and FR2.

[0134] Still referring to the dual CDRX in the FR1 plus FR2 carrier aggregation example, regarding SRS and non-periodic event handling, the example assumes a single PUCCH group. Regarding SRS handling, in the current symbol, taking into account the received grant / assignment / DRX command MAC-CE / long DRX command MAC-CE and the sent scheduling request, if the MAC entity will not be in active time for a frequency range (FR1 or FR2) until 4ms before the current symbol when evaluating all DRX active time conditions (as defined above), the UE does not transmit periodic SRS and semi-persistent SRS in the frequency range.

[0135] Regarding aperiodic event handling, the MAC entity transmits HARQ feedback, aperiodic CSI on PUSCH, and aperiodic SRS (when they are expected), regardless of whether the MAC entity is monitoring PDCCH (across FR1 and FR2). For HARQ feedback, PUCCH for HARQ feedback is still sent on FR1 when FR1 is in DRX off duration. For aperiodic CSI on PUSCH, CSI-RS monitoring occurs during active time within the frequency range with CSI-RS. It is the network's responsibility to ensure that the triggered aperiodic CSI-RS falls during the active time period.

[0136] Continuing with the dual CDRX in the FR1 plus FR2 carrier aggregation example, with respect to PUCCH handling, a single PUCCH group is assumed. A single PUCCH group means that PUCCH is configured in only one component carrier (e.g., PCell) in both FR1 and FR2 carrier aggregation. For CSI handling, if CSI masking is set by upper layers, then in the current symbol, taking into account the received grant / assignment / DRX Command MAC-CE / Long DRX Command MAC-CE, the UE does not report CSI on PUCCH if the drx-on duration timer for FR1 will not run until, for example, 4ms before the current symbol when evaluating all DRX active time conditions (as defined above). Otherwise, (1) in the current symbol, if the MAC entity will not be in active time until 4 ms before the current symbol for FR1 when evaluating all DRX active time conditions (as defined above) taking into account the received grant / assignment / DRX command MAC-CE / long DRX command MAC-CE and the sent SR, the UE does not report CSI on PUCCH. Or, (2) in the current symbol, if the MAC entity will not be in active time until 4 ms before the current symbol for a frequency range (FR1 or FR2) when evaluating all DRX active time conditions (as defined above) taking into account the received grant / assignment / DRX command MAC-CE / long DRX command MAC-CE and the sent scheduling request, the UE does not report semi-persistent CSI on PUSCH in that FR.

[0137] Figure 7An exemplary wireless communication method 700 according to various aspects of the present disclosure is illustrated. At 710, a base station 702 (e.g., any base station described herein) configures a first set of CDRX parameters for a first set of component carriers associated with a first set of parameter sets for a UE operating in a carrier aggregation mode (e.g., any UE described herein). The first set of CDRX parameters can be defined in absolute time (e.g., in symbols, slots, subframes, milliseconds, transmission time intervals (TTIs), etc.). For example, the first set of CDRX parameters can include a drx-on duration timer, a drx-inactivity timer, a drx-long cycle start offset, a drx-short cycle, a drx-short cycle timer, a drx-slot offset, or any combination thereof. The first set of component carriers can be a set of component carriers in a first FR (e.g., FR1 or FR2), in a first frequency band, or in a first cell group. The first set of parameter sets can be one or more parameter sets from Table 1.

[0138] At 720, the base station 702 configures a second set of CDRX parameters for the UE for a second set of component carriers associated with a second set of parameter sets. The second set of CDRX parameters may be defined in absolute time (e.g., in milliseconds). For example, the second set of CDRX parameters may include a drx-on duration timer, a drx-inactivity timer, a drx-long cycle start offset, a drx-short cycle, a drx-short cycle timer, a drx-slot offset, or any combination thereof. The second set of component carriers may be a set of component carriers in a second frequency range (e.g., FR1 or FR2), in a second frequency band, or in a second cell group that is different from the first set of component carriers. The second set of parameter sets may be one or more parameter sets from Table 1, the parameters of which may or may not be different from the parameters of the first set of parameter sets.

[0139] The UE communicates with the base station according to the first set of CDRX parameters at 730. For example, the UE receives downlink transmissions from the base station on the first set of component carriers during an on period of the first set of component carriers defined by the first set of CDRX parameters and sleeps during an off period of the first set of component carriers defined by the first set of CDRX parameters.

[0140] The UE communicates with the base station according to the second set of CDRX parameters at 740. For example, the UE receives downlink transmissions from the base station on the second set of component carriers during an on period of the second set of component carriers defined by the second set of CDRX parameters and sleeps during an off period of the second set of component carriers defined by the second set of CDRX parameters.

[0141] Figure 8An exemplary wireless communication method 800 is illustrated in accordance with aspects of the present disclosure. The method 800 may be performed by a UE operating in a carrier aggregation mode, such as any UE described herein.

[0142] At 810, the UE may be configured by a base station (e.g., any base station described herein) with a first set of CDRX parameters for a first set of component carriers associated with a first set of parameter sets. The first set of CDRX parameters may be defined in absolute time (e.g., in symbols, slots, subframes, milliseconds, TTIs, etc.). For example, the first set of CDRX parameters may include a drx-on duration timer, a drx-inactivity timer, a drx-long cycle start offset, a drx-short cycle, a drx-short cycle timer, a drx-slot offset, or any combination thereof. The first set of component carriers may be a set of component carriers in a first frequency range (e.g., FR1 or FR2), in a first frequency band, or in a first cell group. The first set of parameter sets may be one or more parameter sets from Table 1. In an aspect, operation 810 may be performed by a receiver 312 and / or a processing system 332 (which may be considered as a "means" for performing operation 810).

[0143] At 820, the UE may be configured by the base station with a second set of CDRX parameters for a second set of component carriers associated with a second set of parameter sets. The second set of CDRX parameters may be defined in absolute time (e.g., in milliseconds). For example, the second set of CDRX parameters may include a drx-on duration timer, a drx-inactivity timer, a drx-long cycle start offset, a drx-short cycle, a drx-short cycle timer, a drx-slot offset, or any combination thereof. The second set of component carriers may be a set of component carriers that is different from the first set of component carriers in a second frequency range (e.g., FR1 or FR2), in a second frequency band, or in a second cell group. The second set of parameter sets may be one or more parameter sets from Table 1, the parameters of which may or may not be different from the parameters of the first set of parameter sets. In one aspect, operation 820 may be performed by the receiver 312 and / or the processing system 332 (which may be considered as a "means" for performing operation 820).

[0144] Operations 810 and 820 are optional, as the UE may have been configured by a base station or network entity different from the base station with which it is communicating, or may have determined the CDRX parameters itself and signaled them to the base station, etc.

[0145] At 830, the UE communicates with the base station according to the first set of CDRX parameters. For example, the UE may receive downlink transmissions from the base station on the first set of component carriers during an on period of the first set of component carriers defined by the first set of CDRX parameters and sleep during an off period of the first set of component carriers defined by the first set of CDRX parameters. In one aspect, operation 830 may be performed by the receiver 312 and / or the processing system 332 (which may be considered as a "means" for performing operation 830).

[0146] At 840, the UE communicates with the base station according to the second set of CDRX parameters. For example, the UE may receive downlink transmissions from the base station on the second set of component carriers during an on period of the second set of component carriers defined by the second set of CDRX parameters and sleep during an off period of the second set of component carriers defined by the second set of CDRX parameters. In one aspect, operation 840 may be performed by the receiver and / or processing system 332 (which may be considered a "means" for performing operation 840).

[0147] Fig. 9 9 is a conceptual data flow diagram 900 illustrating data flow between different devices / components in exemplary apparatus 902 and 980 according to aspects of the present disclosure. Apparatus 902 may be a UE (e.g., any UE described herein) in communication with apparatus 980, which may be a base station (e.g., any base station described herein).

[0148] Equipment 902 includes a transmission component 904, which may correspond to Figure 3A The transmitter circuit system (including the transmitter 314 and / or the processing system 332) in the UE 302 depicted in FIG. 902 further includes a DRX component 906, which may correspond to Figure 3A 302 (including the processing system 332 and / or the DRX component 342). The apparatus 902 further includes a receiving component 908, which may correspond to Figure 3A Receiver circuitry (including receiver 312 and / or processing system 332) in UE 302 depicted in FIG.

[0149] The equipment 980 includes a receiving component 982, which may correspond to Figure 3B The receiver circuit system (including the receiver 352 and / or the processing system 384) in the base station 304 depicted in FIG. 980 further includes a DRX component 984, which may correspond to Figure 3BThe processor circuit system (including the DRX component 388 and / or the processing system 384) in the base station 304 depicted in FIG. 980 further includes a transmission component 986, which may correspond to Figure 3B 3. The transmission circuit system (including the transmitter 354 and / or the processing system 332) in the base station 304 depicted in FIG.

[0150] Reference Fig. 9 , the DRX component 984 generates sets of CDRX parameters for the equipment 902 for each component carrier that the equipment 902 uses to communicate with the equipment 980. The transmission component 986 transmits downlink data (including DCI communications, PDCCH communications, DRX configurations, or a combination thereof) to the receiving component 908. Some or all of these communications may convey the sets of CDRX parameters generated by the DRX component 984. The receiving component 908 receives the CDRX parameters and forwards them to the DRX component 906. The DRX component 906 uses the CDRX parameters to configure the transmission component 904 to transmit uplink data to the equipment 980 in accordance with the CDRX parameters. The transmission component 904 transmits uplink data to the receiving component 982 in accordance with the CDRX parameters. One or more components in the equipment 902 and the equipment 980 may perform Figure 7 and 8 Each box in the algorithm in the above flowchart. Thus, Figure 7 and 8 Each block in the aforementioned flow chart of can be performed by a component and the equipment 902 and / or the equipment 980 may include one or more of those components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0151] Fig.10 1000 is a diagram illustrating an example of a hardware implementation of an apparatus 902 employing a processing system 1014. The processing system 1014 may be implemented with a bus architecture generally represented by a bus 1024. The bus 1024 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1014. The bus 1024 links together various circuits including one or more processors and / or hardware components (represented by the processor 1004, components 904, 906, and 908, and computer-readable media / memory 1006). The bus 1024 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0152] The processing system 1014 may be coupled to the transceiver 1010. The transceiver 1010 is coupled to one or more antennas 1020. The transceiver 1010 provides a means for communicating with various other equipment via a transmission medium. The transceiver 1010 receives signals from the one or more antennas 1020, extracts information from the received signals, and provides the extracted information to the processing system 1014 (specifically, the receiving component 908). In addition, the transceiver 1010 receives information from the processing system 1014 (specifically, the transmitting component 904) and generates signals to be applied to the one or more antennas 1020 based on the received information. The processing system 1014 includes a processor 1004 coupled to a computer-readable medium / memory 1006. The processor 1004 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1006. The software, when executed by the processor 1004, causes the processing system 1014 to perform the various functions described above for any particular equipment. The computer-readable medium / memory 1006 may also be used to store data manipulated by the processor 1004 when executing software. The processing system 1014 further includes at least one of the components 904, 906, and 98. These components may be software components running in the processor 1004, software components resident / stored in the computer-readable medium / memory 1006, one or more hardware components coupled to the processor 1004, or some combination thereof. The processing system 1014 may be Figure 3A Components of the UE 302 and may include a memory component 340 and / or at least one of the following: a WWAN transceiver 310, a processing system 332, and a DRX component 342.

[0153] In one configuration, an apparatus 902 (e.g., UE) for wireless communication includes: a device for communicating with a base station according to a first set of CDRX parameters defined in absolute time for a first set of component carriers associated with a first set of parameter sets; and a device for communicating with the base station according to a second set of CDRX parameters defined in absolute time for a second set of component carriers associated with a second set of parameter sets. The aforementioned means may be the aforementioned components of the apparatus 902 and / or one or more components in the processing system 1014 of the apparatus 902 configured to perform the functions recited by the aforementioned means. As described above, the processing system 1014 may include the WWAN transceiver 310, the processing system 332, and the DRX component 342.

[0154] Fig.111100 is a diagram illustrating an example of a hardware implementation of an apparatus 980 employing a processing system 1114. The processing system 1114 may be implemented with a bus architecture generally represented by a bus 1124. Depending on the specific application of the processing system 1114 and the overall design constraints, the bus 1124 may include any number of interconnecting buses and bridges. The bus 1124 links together various circuits including one or more processors and / or hardware components (represented by the processor 1104, components 982, 984, and 986, and computer-readable media / memory 1106). The bus 1124 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0155] The processing system 1114 may be coupled to the transceiver 1110. The transceiver 1110 is coupled to one or more antennas 1120. The transceiver 1110 provides a means for communicating with various other equipment via a transmission medium. The transceiver 1110 receives signals from the one or more antennas 1120, extracts information from the received signals, and provides the extracted information to the processing system 1114 (specifically, the receiving component 982). In addition, the transceiver 1110 receives information from the processing system 1114 (specifically, the transmission component 986) and generates signals to be applied to the one or more antennas 1120 based on the received information. The processing system 1114 includes a processor 1104 coupled to a computer-readable medium / memory 1106. The processor 1104 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1106. The software, when executed by the processor 1104, causes the processing system 1114 to perform the various functions described above for any particular equipment. The computer-readable medium / memory 1106 may also be used to store data that is manipulated by the processor 1104 when executing software. The processing system 1114 further includes at least one of the components 982, 984, and 986. These components may be software components that run in the processor 1104, software components that reside / stored in the computer-readable medium / memory 1106, one or more hardware components coupled to the processor 1104, or some combination thereof. The processing system 1114 may be Figure 3B Components of the base station 304 and may include a memory component 386 and / or at least one of the following: the WWAN transceiver 350, the processing system 384, and the DRX component 388.

[0156] In one configuration, an apparatus 980 (e.g., a base station) for wireless communication includes: a device for communicating with a UE according to a first set of CDRX parameters defined in absolute time for a first set of component carriers associated with a first set of parameter sets; and a device for communicating with the UE according to a second set of CDRX parameters defined in absolute time for a second set of component carriers associated with a second set of parameter sets.

[0157] The aforementioned means may be the aforementioned components of the apparatus 980 and / or one or more components of the processing system 1114 of the apparatus 980 configured to perform the functions recited by the aforementioned means. As previously described, the processing system 1114 may include the WWAN transceiver 350, the processing system 384, and the DRX component 388.

[0158] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented with hardware, firmware, and / or a combination of hardware and software.

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

[0160] In addition, those skilled in the art will appreciate that the various illustrative logic blocks, modules, circuits, and algorithm steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of the two. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. The technician can implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0161] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed with a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in cooperation with a DSP core, or any other such configuration.

[0162] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read and write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and storage medium may reside in a user terminal as discrete components.

[0163] In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any media that facilitates the transfer of a computer program from one place to another. Storage media may be any available media that can be accessed by a computer. As an example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer. Similarly, any connection is also properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disk often reproduces data magnetically, while disc reproduces data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0164] Although the foregoing disclosure shows illustrative aspects of the present disclosure, it should be noted that various changes and modifications may be made therein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps, and / or actions in the method claims according to the various aspects of the present disclosure described herein do not have to be performed in any particular order. In addition, although the elements of the present disclosure may be described or claimed in the singular, the plural is also contemplated unless limitation to the singular is explicitly stated.

Claims

1. A wireless communication method performed by a user equipment (UE) operating in a carrier aggregation mode, comprising: communicating with a base station according to a first set of connected mode discontinuous reception (CDRX) parameters defined in milliseconds for a first set of component carriers associated with a first set of parameters, wherein the first set of CDRX parameters defined in milliseconds includes at least a first on duration timer and a first inactivity timer; as well as Communicating with the base station according to a second set of CDRX parameters defined in milliseconds for a second set of component carriers associated with a second set of parameters, wherein the second set of CDRX parameters defined in milliseconds includes at least a second on-duration timer and a second inactivity timer.

2. The method of claim 1, wherein the first set of CDRX parameters comprises a first set of radio resource control (RRC) parameters, and wherein the second set of CDRX parameters comprises a second set of RRC parameters.

3. The method of claim 2, wherein: The first set of RRC parameters further includes a first long cycle start offset timer, a first short cycle length, a first short cycle timer, a first slot offset, or any combination thereof, and The second set of RRC parameters further includes a second long cycle start offset timer, a second short cycle length, a second short cycle timer, a second slot offset, or any combination thereof. 4 . The method of claim 1 , wherein the CDRX parameters in the first set of CDRX parameters are configured independently of the CDRX parameters in the second set of CDRX parameters. 5 . The method of claim 1 , wherein a start time of a first CDRX cycle in the first set of CDRX parameters is aligned with a start time of a second CDRX cycle in the second set of CDRX parameters.

6. The method of claim 1, wherein each of the first set of component carriers and the second set of component carriers independently enters an inactive state based on one or more inactivity timers associated with the first set of CDRX parameters and the second set of CDRX parameters.

7. The method of claim 1, wherein each of the first set of component carriers and the second set of component carriers independently enters an active state based on a separate grant for each of the first set of component carriers and the second set of component carriers.

8. The method of claim 1, wherein the UE does not transmit a sounding reference signal (SRS) on the first set of component carriers based on: A medium access control (MAC) entity of the UE is not in an active state until a threshold time period before a symbol in which the SRS is scheduled to be transmitted.

9. The method of claim 8, wherein the SRS is associated with the first set of component carriers.

10. The method of claim 1, wherein the UE does not report channel state information (CSI) on a physical uplink control channel (PUCCH) based on: CSI masking is configured and the on-duration timer does not run until the PUCCH is scheduled within a threshold time period before a symbol in which it is transmitted. The method of claim 10 , wherein the PUCCH is associated with the first component carrier set.

12. The method of claim 1, wherein the UE does not report CSI on the PUCCH based on the following circumstances: The MAC entity of the UE is not in an active state until a threshold time period before the PUCCH is scheduled to be transmitted therein.

13. The method of claim 1, wherein the MAC entity of the UE transmits, whether in an inactive state or not: Hybrid Automatic Repeat Request (HARQ) feedback, Aperiodic CSI on the Physical Uplink Shared Channel (PUSCH), and Aperiodic SRS.

14. The method of claim 1, wherein the UE does not transmit an SRS on the first component carrier set based on: The MAC entity of the UE is not active for both the first component carrier set and the second component carrier set, or The MAC entity is not in an active state for the first component carrier set or the second component carrier set in which a grant regarding a PUCCH is received.

15. The method of claim 1, wherein the UE does not report CSI on the PUCCH based on the following circumstances: CSI masking is configured and the on-duration timer is not running for both the first set of component carriers and the second set of component carriers, or The on-duration timer is not running for the first component carrier set or the second component carrier set in which a grant for the PUCCH is received.

16. The method of claim 1, wherein the UE does not report CSI on the PUCCH based on the following circumstances: The MAC entity of the UE is not active for both the first component carrier set and the second component carrier set, or The MAC entity is not in an active state for the first component carrier set or the second component carrier set in which the grant regarding the PUCCH is received.

17. The method of claim 1, wherein: a subset of CDRX parameters in the first set of CDRX parameters is independent of a subcarrier spacing associated with the first set of parameters, a subset of CDRX parameters in the second set of CDRX parameters is independent of a subcarrier spacing associated with the second set of parameters, and The subset of CDRX parameters in the first set of CDRX parameters is independent of the subset of CDRX parameters in the second set of CDRX parameters.

18. The method of claim 17, wherein: The subset of CDRX parameters in the first set of CDRX parameters includes the first on duration timer, the first inactivity timer, a first long cycle start offset timer, a first short cycle length, a first short cycle timer, a first slot offset, or any combination thereof, and The subset of CDRX parameters in the second set of CDRX parameters includes the second on duration timer, the second inactivity timer, a second long cycle start offset timer, a second short cycle length, a second short cycle timer, a second slot offset, or any combination thereof.

19. The method of claim 1, wherein the first set of component carriers and the second set of component carriers become active during a pending scheduling request or a pending random access response.

20. The method of claim 1, further comprising: Receiving a MAC control element (MAC-CE) discontinuous reception (DRX) command, wherein the MAC-CE DRX command is common to both the first component carrier set and the second component carrier set, is common to the first component carrier set or the second component carrier set in which the MAC-CE DRX command is received, or indicates that both the first component carrier set and the second component carrier set are to enter an inactive state.

21. The method of claim 1, wherein: The first component carrier set includes one or more component carriers operating in a first frequency range, and The second set of component carriers includes one or more component carriers operating in a second frequency range.

22. The method of claim 1, wherein: The first component carrier set includes one or more component carriers operating in a first frequency band, and The second component carrier set includes one or more component carriers operating in a second frequency band.

23. The method of claim 1, wherein: The first component carrier set includes one or more component carriers of a first cell group, and The second component carrier set includes one or more component carriers of a second cell cluster.

24. The method of claim 23, wherein the first cell group, the second cell group, or both operate according to a single set of parameters.

25. The method of claim 23, wherein the first cell group, the second cell group, or both operate according to a plurality of parameter sets.

26. A user equipment (UE) configured to operate in a carrier aggregation mode, comprising: Memory; at least one transceiver; as well as at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: communicating, via the at least one transceiver, with a base station according to a first set of connected mode discontinuous reception (CDRX) parameters defined in milliseconds for a first set of component carriers associated with a first set of parameters, wherein the first set of CDRX parameters defined in milliseconds includes at least a first on duration timer and a first inactivity timer; as well as Communicating with the base station via the at least one transceiver according to a second set of CDRX parameters defined in milliseconds for a second set of component carriers associated with a second set of parameters, wherein the second set of CDRX parameters defined in milliseconds includes at least a second on duration timer and a second inactivity timer.

27. The UE of claim 26, wherein the first set of CDRX parameters comprises a first set of radio resource control (RRC) parameters, and wherein the second set of CDRX parameters comprises a second set of RRC parameters.

28. The UE of claim 26, wherein: The first set of RRC parameters further includes a first long cycle start offset timer, a first short cycle length, a first short cycle timer, a first slot offset, or any combination thereof, and The second set of RRC parameters further includes a second long cycle start offset timer, a second short cycle length, a second short cycle timer, a second slot offset, or any combination thereof.

29. The UE of claim 26, wherein the CDRX parameters in the first set of CDRX parameters are configured independently of the CDRX parameters in the second set of CDRX parameters.

30. The UE of claim 26, wherein a start time of a first CDRX cycle in the first set of CDRX parameters is aligned with a start time of a second CDRX cycle in the second set of CDRX parameters.

31. The UE of claim 26, wherein each of the first set of component carriers and the second set of component carriers independently enters an inactive state based on one or more inactivity timers associated with the first set of CDRX parameters and the second set of CDRX parameters.

32. The UE of claim 26, wherein each of the first component carrier set and the second component carrier set independently enters an active state based on a separate grant for each of the first component carrier set and the second component carrier set.

33. The UE of claim 26, wherein the at least one transceiver does not transmit a sounding reference signal (SRS) on the first set of component carriers based on: A medium access control (MAC) entity of the UE is not in an active state until a threshold time period before a symbol in which the SRS is scheduled to be transmitted.

34. The UE of claim 33, wherein the SRS is associated with the first component carrier set.

35. The UE of claim 26, wherein the at least one processor does not report channel state information (CSI) on a physical uplink control channel (PUCCH) based on: CSI masking is configured and the on-duration timer does not run until the PUCCH is scheduled within a threshold time period before a symbol in which it is transmitted.

36. The UE of claim 35, wherein the PUCCH is associated with the first component carrier set.

37. The UE of claim 26, wherein the at least one processor does not report CSI on the PUCCH based on: The MAC entity of the UE is not in an active state until a threshold time period before the PUCCH is scheduled to be transmitted therein.

38. The UE of claim 26, wherein the MAC entity of the UE transmits, whether in an inactive state or not: Hybrid Automatic Repeat Request (HARQ) feedback, Aperiodic CSI on the Physical Uplink Shared Channel (PUSCH), and Aperiodic SRS.

39. The UE of claim 26, wherein the at least one transceiver does not transmit an SRS on the first set of component carriers based on: The MAC entity of the UE is not active for both the first component carrier set and the second component carrier set, or The MAC entity is not in an active state for the first component carrier set or the second component carrier set in which a grant regarding a PUCCH is received.

40. The UE of claim 26, wherein the at least one processor does not report CSI on the PUCCH based on: CSI masking is configured and the on-duration timer is not running for both the first set of component carriers and the second set of component carriers, or The on-duration timer is not running for the first component carrier set or the second component carrier set in which a grant for the PUCCH is received.

41. The UE of claim 26, wherein the at least one processor does not report CSI on the PUCCH based on: The MAC entity of the UE is not active for both the first component carrier set and the second component carrier set, or The MAC entity is not in an active state for the first component carrier set or the second component carrier set in which the grant regarding the PUCCH is received.

42. The UE of claim 26, wherein: a subset of CDRX parameters in the first set of CDRX parameters is independent of a subcarrier spacing associated with the first set of parameters, a subset of CDRX parameters in the second set of CDRX parameters is independent of a subcarrier spacing associated with the second set of parameters, and The subset of CDRX parameters in the first set of CDRX parameters is independent of the subset of CDRX parameters in the second set of CDRX parameters.

43. The UE of claim 42, wherein: The subset of CDRX parameters in the first set of CDRX parameters includes the first on duration timer, the first inactivity timer, a first long cycle start offset timer, a first short cycle length, a first short cycle timer, a first slot offset, or any combination thereof, and The subset of CDRX parameters in the second set of CDRX parameters includes the second on duration timer, the second inactivity timer, a second long cycle start offset timer, a second short cycle length, a second short cycle timer, a second slot offset, or any combination thereof.

44. The UE of claim 26, wherein the first component carrier set and the second component carrier set become active during a pending scheduling request or a pending random access response.

45. The UE according to claim 26, wherein: The at least one processor is further configured to: A MAC control element (MAC-CE) discontinuous reception (DRX) command is received via the at least one transceiver, wherein the MAC-CE DRX command is common to both the first component carrier set and the second component carrier set, is common to the first component carrier set or the second component carrier set in which the MAC-CE DRX command is received, or indicates that both the first component carrier set and the second component carrier set are to enter an inactive state.

46. ​​The UE of claim 26, wherein: The first component carrier set includes one or more component carriers operating in a first frequency range, and The second set of component carriers includes one or more component carriers operating in a second frequency range.

47. The UE of claim 26, wherein: The first component carrier set includes one or more component carriers operating in a first frequency band, and The second component carrier set includes one or more component carriers operating in a second frequency band.

48. The UE of claim 26, wherein: The first component carrier set includes one or more component carriers of a first cell group, and The second component carrier set includes one or more component carriers of a second cell cluster.

49. The UE of claim 48, wherein the first cell group, the second cell group, or both operate according to a single set of parameters.

50. The UE of claim 48, wherein the first cell group, the second cell group, or both operate according to a plurality of parameter sets.

51. A user equipment (UE) configured to operate in a carrier aggregation mode, comprising: means for communicating with a base station according to a first set of connected mode discontinuous reception (CDRX) parameters defined in milliseconds for a first set of component carriers associated with a first set of parameters, wherein the first set of CDRX parameters defined in milliseconds comprises at least a first on duration timer and a first inactivity timer; as well as Means for communicating with the base station according to a second set of CDRX parameters defined in milliseconds for a second set of component carriers associated with a second set of parameters, wherein the second set of CDRX parameters defined in milliseconds includes at least a second on-duration timer and a second inactivity timer.

52. A non-transitory computer-readable medium storing computer-executable instructions for wireless communications, the computer-executable instructions comprising: at least one instruction to instruct a user equipment (UE) operating in a carrier aggregation mode to communicate with a base station according to a first set of connected mode discontinuous reception (CDRX) parameters defined in milliseconds for a first set of component carriers associated with a first set of parameters, wherein the first set of CDRX parameters defined in milliseconds includes at least a first on duration timer and a first inactivity timer; as well as At least one instruction instructing the UE to communicate with the base station according to a second set of CDRX parameters defined in milliseconds for a second set of component carriers associated with a second set of parameters, wherein the second set of CDRX parameters defined in milliseconds includes at least a second on-duration timer and a second inactivity timer.

Images