TECHNIQUES FOR PROCESSING TRANSMISSION BURSTS IN A DISCONTINUOUS RECEIVE CYCLE

Aspects described herein relate to transmitting, to a network node, assistance information indicating one or more alignment parameters related to processing transmission bursts in a discontinuous receive (DRX) mode, receiving, from at least one of the network node or a second network node, a configuration of the one or more alignment parameters, and receiving, from at least one of the network node or the second network node, a transmission burst in a DRX ON duration of a DRX cycle in the DRX mode based on the one or more alignment parameters indicated by the configuration. Other aspects relate to receiving the assistance information and configuring the one or more alignment parameters.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to techniques for communicating using periodic transmission bursts.

DESCRIPTION OF RELATED ART

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. For example, a fifth generation (5G) wireless communications technology (which can be referred to as 5G new radio (5G NR)) is envisaged to expand and support diverse usage scenarios and applications with respect to current mobile network generations. In an aspect, 5G communications technology can include: enhanced mobile broadband addressing human-centric use cases for access to multimedia content, services and data; ultra-reliable-low latency communications (URLLC) with certain specifications for latency and reliability; and massive machine type communications, which can allow a very large number of connected devices and transmission of a relatively low volume of non-delay-sensitive information.

In some wireless communication technologies, such as 5G NR, data can be transmitted to devices in transmission bursts, which can have update rates measured in hertz (Hz), such as 60 Hz, 90 Hz, 45 Hz, 120 Hz, etc. for multimedia or extended reality (XR) data. In addition, in 5G NR, a device can operate in discontinuous receive (DRX) mode where the device can reduce or terminate power to radio frequency (RF) components in certain time periods where communications are not expected to occur to conserve device power and communication resources. The DRX mode can be defined by a DRX cycle having an OFF duration where the power is reduced or terminated and an ON duration where the power is restored for wireless communications. The OFF and ON durations can be measured or defined in periods of milliseconds.

SUMMARY

According to an aspect, a method for wireless communication is provided that includes transmitting, to a network node, assistance information indicating one or more alignment parameters related to processing transmission bursts in a discontinuous receive (DRX) mode, receiving, from at least one of the network node or a second network node, a configuration of the one or more alignment parameters, and receiving, from at least one of the network node or the second network node, a transmission burst in a DRX ON duration of a DRX cycle in the DRX mode based on the one or more alignment parameters indicated by the configuration.

In another aspect, a method for wireless communication is provided that includes receiving, from a user equipment (UE), assistance information indicating one or more alignment parameters related to processing transmission bursts in a DRX mode, and transmitting a configuration of the one or more alignment parameters.

In a further example, an apparatus for wireless communication is provided that includes a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled with the transceiver and the memory. The one or more processors are configured to execute the instructions to perform the operations of methods described herein. In another aspect, an apparatus for wireless communication is provided that includes means for performing the operations of methods described herein. In yet another aspect, a computer-readable medium is provided including code executable by one or more processors to perform the operations of methods described herein.

DETAILED DESCRIPTION

The described features generally relate to processing transmission bursts while operating in a discontinuous receive (DRX) mode. In some cases, a timing of a transmission burst may not align with an ON duration of a DRX cycle. This may be due to transmission bursts being transmitted according to a periodicity defined in hertz (Hz), whereas the ON duration, or a periodicity of the ON duration, of the DRX cycle may be defined in milliseconds (e.g., as an integer number of milliseconds (ms)). For example, in extended reality (XR) multimedia transmissions, a transmission burst rate can be 60 Hz, 90 Hz, 45 Hz, 120 Hz, etc. Where the transmission burst rate is 120 Hz, transmissions may have a burst arrival periodicity, of arriving at a receiving device, at 8.333 ms (a non-integer value). In this example, a DRX ON duration every 8 ms would not properly align to receiving the transmission burst, and a non-uniform DRX cycle (e.g., 8 ms, 8 ms, 9 ms) can be used to align to the cadence of the transmission burst at 120 Hz.

Enhanced connected mode DRX (ECDRX) is proposed to extend DRX mode definitions to allow for DRX cycles to handle transmission bursts. In a first example, a two-level DRX configuration can be defined having an outer DRX cycle and an inner DRX cycle. In this example, the outer DRX cycle can define a total time of multiple DRX cycles (e.g., 25 ms for the above example), and the inner DRX cycle can define the time for each DRX cycle within the outer DRX cycle (e.g., 8 ms, 8 ms, 9 ms for the above example). For example, the outer DRX can be defined using the parameters typically used to define DRX cycles (e.g., in 5G NR and previous releases of third generation partnership project (3GPP)). The inner DRX cycle can support a number of sub-cycles, which can be non-uniform. The start of the first inner DRX cycle can be aligned to the start of the outer DRX, and the end of the last inner DRX cycle can be aligned to the end of the outer DRX, where ON duration, inactivity timer, and other DRX parameters configuration for the inner DRX cycles can be the same as that of the outer DRX cycle. The inner DRX cycle that does not conform with the other inner DRX cycles in the outer DRX cycle (e.g., the 9 ms cycle in the above example) can be referred to as the leap DRX cycle. In this first example, the DRX configuration for configuring the DRX cycle can specify the DRX outer cycle and can be extended to also specify at least the conforming DRX inner cycle (and the device receiving the configuration can determine the leap DRX cycle based on a remainder of the outer DRX cycle added to the last conforming DRX inner cycle). In another example, the DRX configuration may also be extended to define the leap DRX cycle.

start the drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of subframe n. For example, for drx-ShortCadence=120 Hz, subframe n=8, 16, 25, 33, 41, 50, . . . can satisfy the criteria. In this example, the device can jump of 1 subframe every 3 cycles to accommodate the one-third subframe part when duty cycle is 8.33 ms for 120 Hz. The resulting sequence can be the same as in the leap DRX cycle concept in the first example.

In a third example, the DRX configuration for configuring the DRX cycle can specify a value for a DRX cycle using a rational number of multimedia periodicity. For example, a new set of values can be added for drx-LongCycleStartOffset and/or drx-ShortCycle (e.g., as a new information element (IE) under a MAC-CellGroupConfig) that correspond to close approximates of the expected periods of transmission burst (e.g., 8.33 ms, 11.11 ms, 16.67 ms, etc.). In this example, a ceiling operation can be used to choose the previous subframe for the DRX cycle (or corresponding DRX ON duration). For example, if the Short DRX cycle is used for a DRX group, and ceil{[(SFN×10)+subframe number]modulo(drx-ShortCycle)}=ceil{(drx-StartOffset)modulo(drx-ShortCycle)}, start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe. For example, if the Long DRX cycle is used for a DRX group, and ceil{[(SFN×10)+subframe number]modulo(drx-LongCycle)}=drx-StartOffset, start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe. In another example, a floor operation can be used to choose the next subframe for the DRX ON cycle. For example, if the Short DRX cycle is used for a DRX group, and floor{[(SFN×10)+subframe number]modulo(drx-ShortCycle)}=floor{(drx-StartOffset)modulo(drx-ShortCycle)}, start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe. For example, if the Long DRX cycle is used for a DRX group, and floor{[(SFN×10)+subframe number]modulo(drx-LongCycle)}=drx-StartOffset, start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe.

In the above examples, a user equipment (UE) can receive the DRX configuration for implementing the DRX cycles to receive the transmission bursts. In some example, a network node (e.g., a base station/gNB) can transmit the DRX configuration to the UE, and the configuration can indicate the parameters descried above, whether including the parameters defined for DRX cycles in 5G NR and/or the extended parameters or values defined in the first, second, and third examples above.

In a fourth example, for the DRX configuration for configuring the DRX cycle, a command can be sent to shift the start offset for the DRX cycle. For example, a network node (e.g., base station/gNB) can transmit the command to the UE as a media access control (MAC) control element (CE) to shift the offset (e.g., drx-StartOffset parameter in the DRX configuration). For example, in 3GPP TS 38.321, the start of the ON duration of the DRX cycle can be, for a Short DRX cycle: [(SFN×10)+subframe number]modulo(drx-ShortCycle)=(drx-StartOffset)modulo(drx-ShortCycle), or for a Long DRX cycle: [(SFN×10)+subframe number]modulo(drx-LongCycle)=(drx-StartOffset). The network node can send the MAC CE to signal a change of the offset inside the period. When the network node detects that an offset can be changed to match better the arrival time of the next transmission burst (e.g., a data burst from an XR application), the network node can send a MAC CE (e.g., ‘Offset Change Command’) to signal the UE that the next offset shall be changed. For example, the network node can send the UE an offset value of the list, such as absolute value lists, where each list contains the absolute values of the offsets, or relative value lists, where each list contains the number of slots to shift the current offset. The UE can accordingly adjust the offset to align the DRX ON cycle with the transmission burst.

Aspects described herein relate to indicating support, or supported parameter values, for receiving transmission bursts in DRX mode. In some aspects, a UE can transmit UE assistance or capability information to a network node to indicate a support or preference for certain DRX parameters. For example, the UE assistance information can indicate support for, or preference of, one or more of the above examples for aligning DRX ON durations with transmission bursts, parameter values for supporting one or more of the above examples, and/or the like. In some aspects, network nodes can communicate UE context management messages that can indicate a support or preference for certain DRX parameters for a UE. For example, the UE context management messages, which may be communicated between a centralized unit (CU) of a base station/gNB and a distributed unit (DU) of a base station/gNB, can indicate support for, or preference of, one or more of the above examples for aligning DRX ON durations with transmission bursts, parameter values for supporting one or more of the above examples, and/or the like. Moreover, aspects are described herein in terms of DRX, and may be used for specific types of DRX, such as connected-mode DRX (CDRX). The terms are used interchangeably herein.

In an example, indicating support or preference for certain DRX modes or related parameters can allow a network to transmit transmission bursts and configure UEs or other devices to receive the transmission busts while also supporting DRX. Allowing the UEs or other devices to support DRX in this regard while still receiving transmission bursts can facilitate the UEs or other devices receiving significant amounts of data (e.g., for XR applications) while conserving power by terminating or reducing power to RF components during the DRX OFF durations. This can allow the UE or other device to have a more desirable power profile such to improve power consumption when operating using a battery, which can improve user experience when using the UE or other device.

The described features will be presented in more detail below with reference toFIGS.1-8.

FIG.1is a diagram illustrating an example of a wireless communications system and an access network100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) can include base stations102, UEs104, an Evolved Packet Core (EPC)160, and/or a 5G Core (5GC)190. The base stations102may include macro cells (high power cellular base station) and/or small cells (low power cellular base station). The macro cells can include base stations. The small cells can include femtocells, picocells, and microcells. In an example, the base stations102may also include gNBs180, as described further herein. In one example, some nodes of the wireless communication system may have a modem240and UE communicating component342for transmitting assistance information related to receiving transmission bursts in CDRX mode, in accordance with aspects described herein. In addition, some nodes may have a modem340and BS communicating component442for receiving assistance information for a device related to receiving transmission bursts in CDRX mode, in accordance with aspects described herein. Though a UE104is shown as having the modem240and UE communicating component342and a base station102/gNB180is shown as having the modem340and BS communicating component442, this is one illustrative example, and substantially any node or type of node may include a modem240and UE communicating component342and/or a modem340and BS communicating component442for providing corresponding functionalities described herein.

The 5GC190may include a Access and Mobility Management Function (AMF)192, other AMFs193, a Session Management Function (SMF)194, and a User Plane Function (UPF)195. The AMF192may be in communication with a Unified Data Management (UDM)196. The AMF192can be a control node that processes the signaling between the UEs104and the 5GC190. Generally, the AMF192can provide QoS flow and session management. User Internet protocol (IP) packets (e.g., from one or more UEs104) can be transferred through the UPF195. The UPF195can provide UE IP address allocation for one or more UEs, as well as other functions. The UPF195is connected to the IP Services197. The IP Services197may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services.

The base station may also be referred to as a gNB, Node B, evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station102provides an access point to the EPC160or 5GC190for a UE104. Examples of UEs104include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs104may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). IoT UEs may include machine type communication (MTC)/enhanced MTC (eMTC, also referred to as category (CAT)-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well as other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. The UE104may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

In an example, UE communicating component342can transmit assistance information related to the UE104receiving or processing transmission bursts when operating in CDRX mode. For example, UE communicating component342can transmit assistance information including one or more alignment parameters indicating a type of alignment supported or preferred to be perform in aligning CDRX durations for receiving transmission bursts, indicating values of parameters for performing a type of alignment, and/or the like. In an example, BS communicating component442can receive the assistance information and can configure one or more alignment parameters indicating a type of alignment for the UE104to perform, values of parameters for performing a type of alignment, and/or the like. For example, BS communicating component442can transmit the configuration of one or more alignment parameters to the UE104, to one or more other network nodes (e.g., to a DU where BS communicating component442is configured in a CU, to a RU where BS communicating component442is configured in a DU, etc., as described further herein).

In some aspects, the CU210may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU210. The CU210may be configured to handle user plane functionality (i.e., Central Unit — User Plane (CU-UP)), control plane functionality (i.e., Central Unit — Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU210can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the El interface when implemented in an0-RAN configuration. The CU210can be implemented to communicate with the DU230, as necessary, for network control and signaling.

Lower-layer functionality can be implemented by one or more RUs240. In some deployments, an RU240, controlled by a DU230, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s)240can be implemented to handle over the air (OTA) communication with one or more UEs104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s)240can be controlled by the corresponding DU230. In some scenarios, this configuration can enable the DU(s)230and the CU210to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

In an example, BS communicating component442, as described herein, can be at least partially implemented within a CU210, and can transmit the one or more alignment parameters to one or more DUs230. In this example, the one or more DUs230can configure the UE104with the alignment parameters for receiving the transmission burst in CDRX mode. In another example, BS communicating component442, as described herein, can be at least partially implemented within a DU230, and can transmit the one or more alignment parameters to one or more RUs240. In this example, the one or more RUs240can configure the UE104with the alignment parameters for receiving the transmission burst in CDRX mode.

Referring toFIG.3, one example of an implementation of UE104may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors312and memory316and transceiver302in communication via one or more buses344, which may operate in conjunction with modem340and/or UE communicating component342for modifying uplink transmission processes for CG resources to account for high RTT, in accordance with aspects described herein.

In an aspect, the one or more processors312can include a modem340and/or can be part of the modem340that uses one or more modem processors. Thus, the various functions related to UE communicating component342may be included in modem340and/or processors312and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, the one or more processors312may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with transceiver302. In other aspects, some of the features of the one or more processors312and/or modem340associated with UE communicating component342may be performed by transceiver302.

Also, memory316may be configured to store data used herein and/or local versions of applications375or UE communicating component342and/or one or more of its subcomponents being executed by at least one processor312. Memory316can include any type of computer-readable medium usable by a computer or at least one processor312, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory316may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining UE communicating component342and/or one or more of its subcomponents, and/or data associated therewith, when UE104is operating at least one processor312to execute UE communicating component342and/or one or more of its subcomponents.

Transceiver302may include at least one receiver306and at least one transmitter308. Receiver306may include hardware, firmware, and/or software code executable by a processor for receiving data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium). Receiver306may be, for example, a radio frequency (RF) receiver. In an aspect, receiver306may receive signals transmitted by at least one base station102. Additionally, receiver306may process such received signals, and also may obtain measurements of the signals, such as, but not limited to, Ec/Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. Transmitter308may include hardware, firmware, and/or software code executable by a processor for transmitting data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium). A suitable example of transmitter308may including, but is not limited to, an RF transmitter.

Moreover, in an aspect, UE104may include RF front end388, which may operate in communication with one or more antennas365and transceiver302for receiving and transmitting radio transmissions, for example, wireless communications transmitted by at least one base station102or wireless transmissions transmitted by UE104. RF front end388may be connected to one or more antennas365and can include one or more low-noise amplifiers (LNAs)390, one or more switches392, one or more power amplifiers (PAs)398, and one or more filters396for transmitting and receiving RF signals.

In an aspect, LNA390can amplify a received signal at a desired output level. In an aspect, each LNA390may have a specified minimum and maximum gain values. In an aspect, RF front end388may use one or more switches392to select a particular LNA390and its specified gain value based on a desired gain value for a particular application.

Further, for example, one or more PA(s)398may be used by RF front end388to amplify a signal for an RF output at a desired output power level. In an aspect, each PA398may have specified minimum and maximum gain values. In an aspect, RF front end388may use one or more switches392to select a particular PA398and its specified gain value based on a desired gain value for a particular application.

Also, for example, one or more filters396can be used by RF front end388to filter a received signal to obtain an input RF signal. Similarly, in an aspect, for example, a respective filter396can be used to filter an output from a respective PA398to produce an output signal for transmission. In an aspect, each filter396can be connected to a specific LNA390and/or PA398. In an aspect, RF front end388can use one or more switches392to select a transmit or receive path using a specified filter396, LNA390, and/or PA398, based on a configuration as specified by transceiver302and/or processor312.

As such, transceiver302may be configured to transmit and receive wireless signals through one or more antennas365via RF front end388. In an aspect, transceiver may be tuned to operate at specified frequencies such that UE104can communicate with, for example, one or more base stations102or one or more cells associated with one or more base stations102. In an aspect, for example, modem340can configure transceiver302to operate at a specified frequency and power level based on the UE configuration of the UE104and the communication protocol used by modem340.

In an aspect, modem340can be a multiband-multimode modem, which can process digital data and communicate with transceiver302such that the digital data is sent and received using transceiver302. In an aspect, modem340can be multiband and be configured to support multiple frequency bands for a specific communications protocol. In an aspect, modem340can be multimode and be configured to support multiple operating networks and communications protocols. In an aspect, modem340can control one or more components of UE104(e.g., RF front end388, transceiver302) to enable transmission and/or reception of signals from the network based on a specified modem configuration. In an aspect, the modem configuration can be based on the mode of the modem and the frequency band in use. In another aspect, the modem configuration can be based on UE configuration information associated with UE104as provided by the network during cell selection and/or cell reselection.

In an aspect, UE communicating component342can optionally include an assistance information component352for transmitting assistance information including one or more alignment parameters related to receiving transmission bursts in CDRX mode, a configuration processing component354for processing one or more alignment parameters received based on transmitting the assistance information, and/or a CDRX component356for operation in CDRX mode at the UE104and/or adjusting the CDRX mode based on the one or more alignment parameters to receive transmission bursts, in accordance with aspects described herein.

In an aspect, the processor(s)312may correspond to one or more of the processors described in connection with the UE inFIG.8. Similarly, the memory316may correspond to the memory described in connection with the UE inFIG.8.

Referring toFIG.4, one example of an implementation of base station102(e.g., a base station102and/or gNB180, as described above) may include a variety of components, some of which have already been described above, but including components such as one or more processors412and memory416and transceiver402in communication via one or more buses444, which may operate in conjunction with modem440and BS communicating component442for configuring devices for modifying uplink transmission processes for CG resources to account for high RTT, in accordance with aspects described herein.

The transceiver402, receiver406, transmitter408, one or more processors412, memory416, applications475, buses444, RF front end488, LNAs490, switches492, filters496, PAs498, and one or more antennas465may be the same as or similar to the corresponding components of UE104, as described above, but configured or otherwise programmed for base station operations as opposed to UE operations.

In an aspect, BS communicating component442can optionally include an assistance processing component452for processing assistance information including one or more alignment parameters related to receiving transmission bursts in CDRX mode as received for a UE, and/or an alignment configuring component454for configuring one or more alignment parameters for the UE, in accordance with aspects described herein. In an example, one or more of the assistance processing component452or alignment configuring component454can be provided in a CU, DU, or RU in a disaggregated BS. In one example, a CU can include the assistance processing component452for processing the assistance information received from the UE. The CU can also include the alignment configuring component454for configuring the one or more alignment parameters for the UE. In this example, alignment configuring component454can transmit the one or more alignment parameters to the DU and/or RU for use in communicating with the UE at a lower (e.g., physical or MAC) layer. In one example, the DU and/or RU can also include an alignment configuring component454to configure the UE with the one or more alignment parameters.

In an aspect, the processor(s)412may correspond to one or more of the processors described in connection with the base station inFIG.8. Similarly, the memory416may correspond to the memory described in connection with the base station inFIG.8.

FIG.5illustrates a flow chart of an example of a method500for transmitting assistance information related to receiving transmission bursts in CDRX mode, in accordance with aspects described herein. In an example, a UE104can perform the functions described in method400using one or more of the components described inFIGS.1and3.

In method500, at Block502, assistance information indicating one or more alignment parameters related to processing transmission bursts in CDRX mode can be transmitted to a network node. In an aspect, assistance information component352, e.g., in conjunction with processor(s)312, memory316, transceiver302, UE communicating component342, etc., can transmit, to the network node (e.g., a base station102, CU, DU, RU, of a disaggregated base station, etc.), assistance information indicating one or more alignment parameters related to processing transmission bursts in CDRX mode. For example, the assistance information can indicate one or more of a preferred or supported mechanism for aligning a CDRX cycle with expected arrival or receive time for a transmission burst from the network node (or another network node), one or more preferred or supported parameter values for implementing mechanism for aligning the CDRX cycle, and/or the like.

For the first example of the two-level DRX configuration, described above, assistance information component352can indicate, in the assistance information, a preference of, or support for, providing CDRX cycle alignment via the two-level DRX configuration. In an example, assistance information component352can also indicate at least one of the outer DRX cycle duration, or one or more inner DRX cycle durations.

For the second example of the DRX cycle formula and cadence parameter, described above, assistance information component352can indicate, in the assistance information, a preference of, or support for, providing CDRX cycle alignment via the DRX cycle formula and cadence parameter. In an example, assistance information component352can also indicate one or more preferred or supported cadences (e.g., in Hz instead of in ms). For example, assistance information component352can indicate preference or support of a cadence of 45 Hz, 60 Hz, 90 Hz, 120 Hz, etc. for the CDRX cycle.

For the third example of DRX cycle using rational number periodicity, described above, assistance information component352can indicate, in the assistance information, a preference of, or support for, providing CDRX cycle alignment via the DRX cycle using rational number periodicity. In an example, assistance information component352can also indicate one or more preferred or supported rational number periodicities. For example, assistance information component352can indicate preference or support of 8.33 ms, 11.11 ms, 16.67 ms, etc., for the CDRX cycle periodicity.

In 5G NR, for example, a UE can transmit UE assistance information (e.g., in RRC signaling) to the network to inform of preference for certain DRX parameters, which can be carried in a DRX-Preference-r16 information element (IE). The DRX-Preference-r16 IE can be defined to include a preferredDRX-InactivityTimer-r16 IE with possible enumerations indicating a number of durations in milliseconds for the inactivity timer in DRX (e.g., ms0, ms1, ms2, ms3, . . . ms2560), and the IE may have some spare values in the enumeration as well. The DRX-Preference-r16 IE can also be defined to include a preferredDRX-LongCycle-r16 IE with possible enumerations indicating a number of durations in milliseconds for the long cycle in DRX (e.g., ms10, ms20, ms32, ms40, . . . ms10240), and the IE may have some spare values in the enumeration as well. The DRX-Preference-r16 IE can also be defined to include a preferredDRX-ShortCycle-r16 IE with possible enumerations indicating a number of durations in milliseconds for the short cycle in DRX (e.g., ms2, ms3, ms4, ms5, . . . ms640), and the IE may have some spare values in the enumeration as well. The DRX-Preference-r16 IE can also be defined to include a preferredDRX-ShortCycleTimer-r16 IE with a possible integer value of 1 to 16.

For the first example of the two-level DRX configuration, described above, parameters of the DRX-Preference-r16 IE (or a similar IE defined for a subsequent release of 3 GPP) can be extended or modified to indicate the durations of the outer DRX cycle and/or one or more inner DRX cycles. For example, preferredDRX-Short-Cycle-r16 (and/or preferredDRX-LongCycle-r16) IEs can be extended or enhanced to carry the durations of the outer DRX cycle and/or one or more inner DRX cycles. In one example, in addition to the enumerations included for DRX-Preference-r16 IE, a sequence of two enumerates outerCycle and innerCycle can be added. In any case, assistance information component352can indicate, in the assistance information, at least one of the outer DRX cycle duration, or one or more inner DRX cycle durations to allow the network to configure the DRX cycle for receiving transmission bursts.

For the second example of the DRX cycle formula and cadence parameter, described above, parameters of the DRX-Preference-r16 IE (or a similar IE defined for a subsequent release of 3 GPP) can be extended or modified to indicate the cadence parameter values, in Hz, that are supported or preferred. For example, preferredDRX-Short-Cycle-r16 (and/or preferredDRX-LongCycle-r16) IEs can be extended or enhanced to carry the new values in Hz (e.g., 45, 6-, 90, 120 Hz). In one example, in addition to the enumerations included for DRX-Preference-r16 IE, a second enumeration for the cadence values can be added. In any case, assistance information component352can indicate, in the assistance information, the preferred or supported cadence(s) to allow the network to configure the DRX cycle for receiving transmission bursts.

For the third example of DRX cycle using rational number periodicity, described above, parameters of the DRX-Preference-r16 IE (or a similar IE defined for a subsequent release of 3 GPP) can be extended or modified to indicate the new rational values in milliseconds (e.g., 8.33, 11.11, 16.67 ms). In one example, in addition to the enumerations included for DRX-Preference-r16 IE, a second enumeration for the rational values for the DRX cycle duration can be added. In any case, assistance information component352can indicate, in the assistance information, the preferred or supported rational value(s) for the DRX cycle duration to allow the network to configure the DRX cycle for receiving transmission bursts.

In method500, at Block504, a configuration of the one or more alignment parameters can be received from at least one of the network node or a second network node. In an aspect, configuration processing component354, e.g., in conjunction with processor(s)312, memory316, transceiver302, UE communicating component342, etc., can receive, from at least one of the network node or a second network node, the configuration of the one or more alignment parameters. For example, configuration processing component354can receive the configuration based on transmitting the assistance information (e.g., the configuration may include values for the alignment parameters that are indicated, in the assistance information, as preferred or supported). In an example, configuration processing component354can receive the configuration from the base station102, from a CU, or from a DU or RU. In one example, for a disaggregated base station, assistance information component352can transmit the assistance information to a first network node, such as a RU or DU, and the first network node can transmit the assistance information to a CU. In this example, the CU can specify the configuration, and can transmit the configuration to the UE, which may be via the DU or RU. Thus, for example, configuration processing component354can receive the configuration from the CU, DU, or RU, in some examples.

For example, the one or more alignment parameters may indicate one or more of the type of alignment to use (e.g., the first example of the two-level DRX configuration, the second example of the DRX cycle formula and cadence parameter, the third example of DRX cycle using rational number periodicity, etc.). In another example, the one or more alignment parameters may additionally or alternatively indicate the corresponding parameter values configured for one or more of the types of alignment (e.g., outer and/or inner cycle duration, cadence, rational cycle duration, etc.). In an example, configuration processing component354can receive the configuration in RRC signaling from the base station102. In another example, e.g., for the fourth example of shifting the offset, configuration processing component354can receive the configuration indicating the offset in a MAC CE.

In method500, at Block506, a transmission burst can be received, from at least one of the network node or the second network node, in a CDRX ON duration of a CDRX cycle in the CDRX mode based on the one or more alignment parameters indicated by the configuration. In an aspect, CDRX component356, e.g., in conjunction with processor(s)312, memory316, transceiver302, UE communicating component342, etc., can configure the CDRX mode based on the one or more parameters, and/or the CDRX component356can receive, from at least one of the network node or the second network node, the transmission burst in the CDRX ON duration of the CDRX cycle in the CDRX mode based on the one or more alignment parameters indicated by the configuration. For example, CDRX component356can use the one or more alignment parameters for aligning or determining a subframe, slot, etc. for a CDRX ON duration of a CDRX cycle to receive the transmission burst.

For the first example of the two-level DRX configuration, described above, CDRX component356can implement CDRX based on a CDRX cycle defined by the outer cycle duration and one or more inner cycle durations, which may be indicated by, or determined based on, one or more alignment parameter values indicated in the configuration. As example is shown inFIG.6.

FIG.6illustrates an example of a timeline600for a CDRX mode. Timeline600includes three CDRX cycles, including a first CDRX cycle defined by CDRX ON duration602and CDRX OFF duration604, a second CDRX cycle defined by CDRX ON duration606and CDRX OFF duration608, and a third CDRX cycle defined by CDRX ON duration610and CDRX OFF duration612. Timeline600can correspond to a 120 Hz transmission burst cadence, where each transmission burst is expected to arrive 8.33 ms apart. Accordingly, for example, an outer cycle duration of 25 ms can be used to receive according to the 8.33 ms cadence, where inner cycle durations of 8 ms, 8 ms, 9 ms can be specified. This can ensure the CDRX cycles align, or substantially align, to the transmission burst at least every three cycles (e.g., based on the additional lms of the9ms inner cycle extending to the start of the fourth transmission burst). In any case, for example, assistance information component352can indicate support or preference for the 25 ms outer cycle, the 8 ms, 8 ms, 9 ms configuration of inner cycles, etc., and configuration processing component354can receive the one or more alignment parameters indicating to use at least the 25 ms outer cycle, but also, in some examples, at least the 8 ms inner cycle. In one example, CDRX component356can determine to use the 8 ms inner cycle and can compute the difference in duration for the last inner cycle (the leap cycle) based on a remainder (e.g., based on the outer cycle duration module the inner cycle duration). In another example, the configuration received by configuration processing component354may specify the leap cycle duration as well.

In receiving the transmission burst at Block506, optionally at Block508, an inner cycle duration for receiving the transmission burst can be determined based at least in part on a configured outer cycle duration. In an aspect, CDRX component356, e.g., in conjunction with processor(s)312, memory316, transceiver302, UE communicating component342, etc., can determine, based at least in part on the configured outer cycle duration, the inner cycle duration for receiving the transmission burst. For example, as described, the configuration may indicate the outer cycle duration, and CDRX component356can determine at least one inner cycle duration based on the outer cycle duration (e.g., where the at least one inner cycle duration is also not included in the configuration). For example, CDRX component356can determine the at least one inner cycle duration by adding a remainder of the outer cycle duration modulo the inner cycle duration to the last inner cycle.

In receiving the transmission burst at Block506, optionally at Block510, a subframe for the transmission burst can be determined based on computing a duration of each CDRX cycle based on the value in hertz. In an aspect, CDRX component356, e.g., in conjunction with processor(s)312, memory316, transceiver302, UE communicating component342, etc., can determine the subframe for the transmission burst based on computing the duration of each CDRX cycle based on the value in hertz. As described for the second example of using the DRX cycle formula and configured cadence, where n=[(SFN×10)+subframe number], where SFN is the system frame number, as defined in 3 GPP technical specification (TS) 38.321, if

CDRX component356can start the drx-onDurationTimer for this DRX cycle after drx-SlotOffset from the beginning of subframe n, based on the drx-ShortCadence indicated in the configuration, to receive the transmission burst in the DRX ON duration. For example, CDRX component356can determine the subframes for the DRX ON duration for receiving for 120 Hz cadence as shown inFIG.6(e.g., as 8 ms, 8 ms and then 9 ms to accommodate the one third subframe part for duty cycle of 8.33 ms for 120 Hz).

In receiving the transmission burst at Block506, optionally at Block512, a subframe for the transmission burst can be determined based on computing a duration of each CDRX cycle based at least in part on a rational value that relates to a duration of the CDRX cycle. In an aspect, CDRX component356, e.g., in conjunction with processor(s)312, memory316, transceiver302, UE communicating component342, etc., can determine the subframe for the transmission burst based on computing a duration of each CDRX cycle based at least in part on the rational value that relates to the duration of the CDRX cycle. As described for the third example, for a DRX cycle using a rational number periodicity, CDRX component356can determine the CDRX ON duration for receiving the transmission burst based on a ceiling or floor function for the Short DRX cycle or Long DRX cycle, where the cycle is configured as a rational value.

FIG.7illustrates a flow chart of an example of a method700for configuring a device for transmitting assistance information related to receiving transmission bursts in CDRX mode, in accordance with aspects described herein. In an example, a base station102, or components of a disaggregated base station (e.g., one or more of a CU, DU, RU, etc.) can perform the functions described in method700using one or more of the components described inFIGS.1and4.

In method700, at Block702, assistance information indicating one or more alignment parameters related to processing transmission bursts in CDRX mode can be received from a UE. In an aspect, assistance processing component452, e.g., in conjunction with processor(s)412, memory416, transceiver402, BS communicating component442, etc., can receive, from the UE (e.g., UE104), assistance information indicating one or more alignment parameters related to processing transmission bursts in CDRX mode. For example, assistance processing component452can receive the one or more alignment parameters from the UE104in RRC signaling, as described above, and the one or more alignment parameters may indicate types of alignment or corresponding parameter values that the UE104can support or prefers in performing alignment of CDRX ON durations of CDRX cycles to transmission bursts.

In method700, at Block704, a configuration of the one or more alignment parameters can be transmitted. In an aspect, alignment configuring component454, e.g., in conjunction with processor(s)412, memory416, transceiver402, BS communicating component442, etc., can transmit the configuration of the one or more alignment parameters. For example, alignment configuring component454can select values for the one or more alignment parameters, which may include selecting a type of alignment (e.g., the first example, second example, third example, or fourth example described above), values for parameters for performing the type of alignment, and/or the like.

In transmitting the configuration at Block704, optionally at Block706, the configuration can be transmitted to the UE. In an aspect, alignment configuring component454, e.g., in conjunction with processor(s)412, memory416, transceiver402, BS communicating component442, etc., can transmit the configuration to the UE104. In this regard, the UE104can receive the configuration, as described above, and can operate the CDRX mode according to the parameters to receive the transmission bursts during the CDRX ON duration.

In transmitting the configuration at Block704, optionally at Block708, the configuration can be transmitted to a DU or RU for providing to the UE. In an aspect, alignment configuring component454, e.g., in conjunction with processor(s)412, memory416, transceiver402, BS communicating component442, etc., can transmit the configuration to the DU or RU for providing to the UE. In an example, for a disaggregated base station, the CU can generate the configuration and can indicate the configured alignment parameters to the DU so that the DU can configure the UE104. For example, the CU can transmit a UE context message, such as a F1-AP message labeled “UE Context Setup Request” to the DU to request setup of the UE context. The context can be modified by the CU sending the F1-AP message labeled “UE Context Modification Request” to the DU, which can include context information changes to the DU. These messages, which are defined in 3 GPP TS 38.473, can include DRX cycle information, in a DRX Cycle IE, which can specify the DRX parameters for the UE104, such as Long DRX Cycle Length, Short DRX Cycle Length, and Short DRX Cycle Timer, which can have one of the enumerated values described above with respect to the DRX-Preference-r16 IE. These values can be extended, as described above, to support indication of the additional alignment parameters and values for aligning the CDRX mode for receiving transmission bursts.

For the first example of the two-level DRX configuration, described above, parameters of the DRX Cycle IE that can be indicated in the “UE Context Setup Request” or the “UE Context Modification Request” can be extended or modified to indicate the durations of the outer DRX cycle and/or one or more inner DRX cycles. For example, Short DRX Cycle Length (and/or Long DRX Cycle Length) IEs can be extended or enhanced to carry the durations of the outer DRX cycle and/or one or more inner DRX cycles. In one example, in addition to the enumerations included for DRX Cycle IE, a sequence of two enumerates outerCycle and innerCycle can be added. In any case, alignment configuring component454can configure, in the UE context message transmitted from CU to DU, at least one of the outer DRX cycle duration, or one or more inner DRX cycle durations to configure the DRX cycle for the UE for receiving transmission bursts.

For the second example of the DRX cycle formula and cadence parameter, described above, parameters of the DRX Cycle IE that can be indicated in the “UE Context Setup Request” or the “UE Context Modification Request” can be extended or modified to indicate the cadence parameter values, in Hz, that are supported or preferred. For example, Short DRX Cycle Length (and/or Long DRX Cycle Length) IEs can be extended or enhanced to carry the new values in Hz (e.g., 45, 6-, 90, 120 Hz). In one example, in addition to the enumerations included for DRX Cycle IE, a second enumeration for the cadence values can be added. In any case, alignment configuring component454can configure, in the UE context message transmitted from CU to DU, the preferred or supported cadence(s) to configure the DRX cycle for the UE for receiving transmission bursts.

For the third example of DRX cycle using rational number periodicity, described above, parameters of the DRX Cycle IE that can be indicated in the “UE Context Setup Request” or the “UE Context Modification Request” can be extended or modified to indicate the new rational values in milliseconds (e.g., 8.33, 11.11, 16.67 ms). In one example, in addition to the enumerations included for DRX Cycle IE, a second enumeration for the rational values for the DRX cycle duration can be added. In any case, alignment configuring component454can configure, in the UE context message transmitted from CU to DU, the preferred or supported rational value(s) to configure the DRX cycle for the UE for receiving transmission bursts.

In method700, optionally at Block710, a transmission burst can be transmitted, to the UE, based on the one or more alignment parameters indicated by the configuration. In an aspect, BS communicating component442, e.g., in conjunction with processor(s)412, memory416, transceiver402, etc., can transmit, to the UE (e.g., UE104), the transmission burst based on the one or more alignment parameters indicated by the configuration. For example, BS communicating component442can transmit the transmission burst according to the cadence, based on which alignment configuring component454can have configured the CDRX parameters for the UE104.

FIG.8is a block diagram of a MIMO communication system800including a base station102and a UE104. The MIMO communication system800may illustrate aspects of the wireless communication access network100described with reference toFIG.1. The base station102may be an example of aspects of the base station102described with reference toFIG.1. The base station102may be equipped with antennas834and835, and the UE104may be equipped with antennas852and853. In the MIMO communication system800, the base station102may be able to send data over multiple communication links at the same time. Each communication link may be called a “layer” and the “rank” of the communication link may indicate the number of layers used for communication. For example, in a 2×2 MIMO communication system where base station102transmits two “layers,” the rank of the communication link between the base station102and the UE104is two.

At the base station102, a transmit (Tx) processor820may receive data from a data source. The transmit processor820may process the data. The transmit processor820may also generate control symbols or reference symbols. A transmit MIMO processor830may perform spatial processing (e.g., precoding) on data symbols, control symbols, or reference symbols, if applicable, and may provide output symbol streams to the transmit modulator/demodulators832and833. Each modulator/demodulator832through833may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator/demodulator832through833may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a DL signal. In one example, DL signals from modulator/demodulators832and833may be transmitted via the antennas834and835, respectively.

The UE104may be an example of aspects of the UEs104described with reference toFIGS.1and3. At the UE104, the UE antennas852and853may receive the DL signals from the base station102and may provide the received signals to the modulator/demodulators854and855, respectively. Each modulator/demodulator854through855may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each modulator/demodulator854through855may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector856may obtain received symbols from the modulator/demodulators854and855, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A receive (Rx) processor858may process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE104to a data output, and provide decoded control information to a processor880, or memory882.

The processor880may in some cases execute stored instructions to instantiate a UE communicating component342(see e.g.,FIGS.1and3).

On the uplink (UL), at the UE104, a transmit processor864may receive and process data from a data source. The transmit processor864may also generate reference symbols for a reference signal. The symbols from the transmit processor864may be precoded by a transmit MIMO processor866if applicable, further processed by the modulator/demodulators854and855(e.g., for single carrier-FDMA, etc.), and be transmitted to the base station102in accordance with the communication parameters received from the base station102. At the base station102, the UL signals from the UE104may be received by the antennas834and835, processed by the modulator/demodulators832and833, detected by a MIMO detector836if applicable, and further processed by a receive processor838. The receive processor838may provide decoded data to a data output and to the processor840or memory842.

The processor840may in some cases execute stored instructions to instantiate a BS communicating component442(see e.g.,FIGS.1and4).

The components of the UE104may, individually or collectively, be implemented with one or more ASICs adapted to perform some or all of the applicable functions in hardware. Each of the noted modules may be a means for performing one or more functions related to operation of the MIMO communication system800. Similarly, the components of the base station102may, individually or collectively, be implemented with one or more application specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Each of the noted components may be a means for performing one or more functions related to operation of the MIMO communication system800.

The following aspects are illustrative only and aspects thereof may be combined with aspects of other embodiments or teaching described herein, without limitation.

Aspect 1 is a method for wireless communication including transmitting, to a network node, assistance information indicating one or more alignment parameters related to processing transmission bursts in a DRX mode, receiving, from at least one of the network node or a second network node, a configuration of the one or more alignment parameters, and receiving, from at least one of the network node or the second network node, a transmission burst in a DRX ON duration of a DRX cycle in the DRX mode based on the one or more alignment parameters indicated by the configuration.

In Aspect 2, the method of Aspect 1 includes where the one or more alignment parameters relate to aligning arrival transmission bursts with DRX ON durations of DRX cycles in the DRX mode.

In Aspect 3, the method of any of Aspects 1 or 2 includes where the one or more alignment parameters include an outer cycle duration of an outer cycle that is supported for the DRX mode, and one or more inner cycle durations of one or more inner cycles within the outer cycle that are supported for the DRX mode.

In Aspect 4, the method of Aspect 3 includes where the one or more inner cycle durations include multiple inner cycle durations of different values.

In Aspect 5, the method of any of Aspects 1 to 4 includes where the one or more alignment parameters include a value in hertz that relates to a DRX cycle duration of the DRX mode, and where receiving the transmission burst in the DRX ON duration of the DRX cycle includes determining a subframe for the transmission burst based on computing a duration of each DRX cycle based on the value in hertz.

In Aspect 6, the method of Aspect 5 includes where computing the duration of each DRX cycle includes computing a number of milliseconds for a duty cycle based on the value in hertz and dividing by a number of subframes for the transmission burst.

In Aspect 7, the method of any of Aspects 1 to 6 includes where the one or more alignment parameters include a rational value that relates to a duration of the DRX cycle, and where receiving the transmission burst in the DRX ON duration of the DRX cycle is based on the rational value.

In Aspect 8, the method of Aspect 7 includes where receiving the transmission burst includes determining a subframe for the transmission burst based on the duration of the DRX cycle.

In Aspect 9, the method of Aspect 8 includes where determining the subframe is based on applying one of a ceiling operation or a floor operation to the duration of the DRX cycle for the transmission burst.

Aspect 10 is a method for wireless communication including receiving, from a UE, assistance information indicating one or more alignment parameters related to processing transmission bursts in a DRX mode, and transmitting a configuration of the one or more alignment parameters.

In Aspect 11, the method of Aspect 10 includes where the one or more alignment parameters relate to aligning arrival transmission bursts, at the UE, with DRX ON durations of DRX cycles in the DRX mode.

In Aspect 12, the method of any of Aspects 10 or 11 includes where transmitting the configuration includes transmitting, to a DU, the configuration for providing to the UE.

In Aspect 13, the method of any of Aspects 10 to 12 includes where transmitting the configuration includes transmitting, to the UE, the configuration.

In Aspect 14, the method of any of Aspects 10 to 13 includes transmitting, to the UE, a transmission burst based on the one or more alignment parameters indicated by the configuration.

In Aspect 15, the method of any of Aspect 10 to 14 includes where the one or more alignment parameters include an outer cycle duration of an outer cycle that is supported for the DRX mode, and one or more inner cycle durations of one or more inner cycles within the outer cycle that are supported for the DRX mode.

In Aspect 16, the method of Aspect 15 includes where the one or more inner cycle durations include multiple inner cycle durations of different values.

In Aspect 17, the method of any of Aspects 10 to 16 includes where the one or more alignment parameters include a value in hertz that relates to a duration of a DRX cycle.

In Aspect 18, the method of any of Aspects 10 to 17 includes where the one or more alignment parameters include a rational value that relates to a duration of a DRX cycle.

Aspect 19 is an apparatus for wireless communication including a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled with the memory and the transceiver, where the one or more processors are configured to execute the instructions to cause the apparatus to perform any of the methods of Aspects 1 to 18.

Aspect 20 is an apparatus for wireless communication including means for performing any of the methods of Aspects 1 to 18.

Aspect 21 is a computer-readable medium including code executable by one or more processors for wireless communications, the code including code for performing any of the methods of Aspects 1 to 18.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a specially programmed device, such as but not limited to a processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein. A specially programmed processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A specially programmed processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.