Patent Description:
<CIT> discloses method and apparatus for bidirectional applications where the source application entity and/or the destination application entity may align the uplink data transfer instances and the downlink transfer instances so that they are close to each other or overlap with each other. This may enable both uplink data transfer and downlink data transfer to take place in a single active state of the client terminal.

<CIT> discloses a method including obtaining a signal pattern defining resources for use in transmitting or receiving signals with variable signal density over time, the signals including a plurality of signals defining a signal burst, configuring the resources based on the signal pattern, including aligning a discontinuous reception (DRX) period with the signal burst, and transmitting or receiving the signals, including the signal burst aligned with the DRX period, according to the signal pattern to achieve variable density signal transmission or reception over time.

<CIT>discloses the GF uplink transmission of one ED or multiple ED of the group over the unlicensed spectrum is aligned to: a common GF transmission cycle; a downlink (DL) group common time alignment signal; a DL burst containing a Control Resource Set (CORESET) that includes ED-specific and/or group common DCI triggers; or a combination of two or more of the above.

<CIT>discloses that UE determines whether data arrives in a buffer of the UE and when a scheduling request occasion falls into a C-DRX off period (connected discontinuous reception off period). The UE also delays sending a scheduling request when uplink pre-scheduling is supported by a serving base station based on the determining and based on a periodicity of uplink (UL) prescheduling for periodic uplink prescheduling and/or a length of an uplink prescheduled grant for non-periodic uplink prescheduling.

This summary is not an extensive overview of all contemplated aspects and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects.

Extended reality (XR) may be used for different applications. XR may involve real and virtual combined environments and human-machine interactions generated by computer technology and wearables, for example. As an example, XR communication may be used for cloud gaming, virtual reality (VR) split rendering, and/or augmented reality (AR) split computation. XR communications may occur over a <NUM> NR system, in conjunction with an edge server. For example, a UE may receive XR data, which the UE may transmit to a base station, wherein the base station may provide the XR data to the core network. The core network may interface with the edge server and provide the XR data to the edge server. However, the <NUM> system and the edge server may be based on independent clocks, such that computation and communication might not be coordinated. The present disclosure allows for the <NUM> system and the edge server to be synchronized in order to improve and coordinate computation and communication.

Only <FIG>, <FIG>, and <FIG>, along with respective illustrations in the description, correspond to the claimed invention.

Frequency range bands include frequency range <NUM> (FR1), which includes frequency bands below <NUM>, and frequency range <NUM> (FR2), which includes frequency bands above <NUM>. Communications using the mmW / near mmW radio frequency (RF) band (e.g., <NUM> - <NUM>) has extremely high path loss and a short range. Base stations / UEs may operate within one or more frequency range bands.

Some of the UEs <NUM> may be referred to as loT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.).

Referring again to <FIG>, according to the claimed invention, the base station <NUM> is configured to align the uplink transmissions and downlink receptions for UEs. The base station <NUM> of <FIG> includes an offset time component <NUM> configured to select an offset time for transmitting a periodic downlink traffic burst to a UE based on a processing timeline associated with an application server. The base station <NUM> communicates with a UE using periodic uplink traffic bursts and periodic downlink traffic bursts. The base station <NUM> selects a time offset to at least one of uplink traffic or downlink traffic to align the uplink traffic bursts and the downlink traffic bursts. The base station <NUM> may send the time offset to an application function (AF).

Referring again to <FIG>, in certain aspects, the UE <NUM> is configured to adjust its uplink transmissions in order to be synchronized with a processing timeline associated with an application server. The UE <NUM> of <FIG> includes a synchronization component <NUM> configured to adjust periodic uplink traffic bursts from the UE based on an offset, such that the UE is synchronized with the processing timeline.

In the examples provided by <FIG>, the <NUM> NR frame structure is assumed to be TDD, with subframe <NUM> being configured with slot format <NUM> (with mostly DL), where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe <NUM> being configured with slot format <NUM> (with mostly UL).

For slot configuration <NUM>, different numerologies µ <NUM> to <NUM> allow for <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> slots, respectively, per subframe. <FIG> provide an example of slot configuration <NUM> with <NUM> symbols per slot and numerology µ=<NUM> with <NUM> slots per subframe. The slot duration is <NUM>, the subcarrier spacing is <NUM>, and the symbol duration is approximately <NUM>. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see <FIG>) that are frequency division multiplexed. Each BWP may have a particular numerology.

A PDCCH within one BWP may be referred to as a control resource set (CORESET). Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block (also referred to as SS block (SSB)).

Table <NUM> illustrates examples of QoS parameters for different types of communications. The table indicates a <NUM> QoS indicator (5QI) value for a corresponding packet delay budget (PDB), packet error rate (PER), default maximum data burst (MDB) volume, and example services for the 5QI value. The examples shown for 5QI values <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may correspond to eMBB uses cases. The examples for eMBB may correspond to various different types of traffic. The example shown for 5QI value <NUM> may correspond to an XR use case, and the example shown for 5QI value <NUM> may correspond to an URLLC use case. URLLC may have a very low latency, e.g., a PDB ≤ <NUM>, and a high reliability, e.g., a PER ≤ <NUM>-<NUM>, for low data rate traffic. XR communication may have a high reliability, e.g., a PER ≤ <NUM>-<NUM>, and a low latency, e.g., a PDB in the range of <NUM> ≤ PDB ≤ <NUM>. However, in contrast to URLLC, XR may have a high bit rate.

XR may be used for different applications. XR may involve real and virtual combined environments and human-machine interactions generated by computer technology and wearables, for example. As an example, XR communication may be used for cloud gaming, virtual reality (VR) split rendering, and/or augmented reality (AR) split computation. Table <NUM> illustrates a chart showing example uses for XR.

<FIG> illustrates an example system model <NUM> for XR communication over a <NUM> NR system. <FIG> illustrates a head mounted display (HMD) <NUM> that may be worn by a user. The HMD may send and receive XR communication with edge server <NUM> via a <NUM> communication system <NUM>, e.g., as described in detail in connection with <FIG>. The <NUM> system may also be referred to as an NR system. <FIG> illustrates the <NUM> system as comprising a UE <NUM> that transmits/receives communication with RAN <NUM> that transmits/receives communication with a network component <NUM>. The UE may correspond to UE <NUM> in <FIG>, and the core network component <NUM> may correspond to core network <NUM> in <FIG>. The RAN component may correspond to a base station <NUM>/<NUM> in <FIG>. Thus, the UE <NUM> may receive XR data from the HMD and transmit the XR data to a base station, which may provide the data to the core network <NUM>. The core network <NUM> may interface with the edge server <NUM> to provide the data to the edge server. Similarly, the edge server <NUM> may provide data to the HMD by providing the data to the core network <NUM>, which passes the data to a base station that transmits the data as downlink communication to UE <NUM>. The UE <NUM> may provide the received downlink data to the HMD, e.g., via a wireless or wired connection with the HMD. Thus, <NUM> system <NUM> may transmit and receive traffic with edge server <NUM> that is illustrated as comprising an XR edge data network (DN) and an XR edge application function (AF). As illustrated, the traffic may be communicated using an N5/N33 network external interface and/or an N6 interface between a 5GC-UPF and the XR edge DN, e.g., real-time transport protocol (RTP) - user datagram protocol (UDP).

The <NUM> system <NUM>, or NR system, may provide QoS for the XR communication. The XR session may be hosted at the edge server <NUM>, which may be an operator server or a third party server. The latency between the core network component <NUM> and the edge server <NUM> may be assumed to be negligible. Communication between Hypertext transfer protocol (HTTP) to transport control protocol (TCP) may use latency in the latency budget for the XR communication.

<FIG> illustrates an example graph <NUM> showing a periodic or quasi-periodic nature of XR traffic. The height of each line indicates a file size of the XR traffic. As illustrated, similar amounts and sizes of data may be communicated in periodic busts of traffic. XR may involve periodic rendering processes, each within a separate epoch corresponding to a length of time. The HMD may determine and send period bursts of information to the edge server, e.g., position/orientation information for the HMD. The edge server may process the position/orientation information and provide rendering information back to the HMD.

The <NUM> system <NUM>, edge server <NUM> computation, and device computation <NUM> may be based on independent clocks, e.g., a clock at the HMD <NUM> and a clock at the edge server <NUM>. Thus, computation and communication might not be coordinated. <FIG> illustrates an example timeline <NUM> for XR without synchronization showing resource contention between two users. Computation resources and wireless resources (e.g., <NUM> NR wireless resources) may be dimensioned for reliability at peak loads. At low delay budgets, higher resource contention may occur with peak loading, such as illustrated in <FIG>.

<FIG> provides a diagram <NUM> illustrating an edge server synchronized with a <NUM> system in accordance with certain aspects of the disclosure. The diagram <NUM> includes the edge server <NUM>, the <NUM> network generalized by box <NUM> which includes the core network and the RAN, and further includes a plurality of end system devices <NUM>. In some aspects, the edge server and device computation nodes and communication nodes may be configured to synchronize their respective clocks. The computations and communications may then be scheduled at deterministic times, due to the synchronization, which may minimize peak loading. At least one advantage of the disclosure is that synchronizing the <NUM> system and the edge server may optimize allocation of downlink and/or uplink resources. For example, the base station of the <NUM> system may schedule uplink resources for UEs to coincide with downlink receptions of the UEs. This may allow UEs to wake up from idle mode in order to transmit and receive during the same wake up duration, as opposed to waking up just to transmit, and then subsequently wake up again in order to receive, or vice versa.

<FIG> illustrate diagrams <NUM>, <NUM> of an edge server and a <NUM> system in accordance with certain aspects of the disclosure. The diagram <NUM> includes a <NUM> system <NUM> and an edge server <NUM>. The edge server <NUM> may be a server that is located close enough to the <NUM> network, such that latency between the edge server and the <NUM> network is small and negligible. Diagrams <NUM> and <NUM> disclose different aspects directed to conveying "burst arrival time" information. The "burst arrival time" may be the arrival time of the data burst at either the ingress of the RAN (e.g., downlink flow direction) or egress interface of the UE (e.g., uplink flow direction). Providing the burst arrival time assists in achieving the synchronized system. A synchronized system may occur when the clocks, for example, of the <NUM> system and the edge server are synchronized with respect to each other, or the respective clocks may by synchronized to a reference clock. As such, the time at which a burst of downlink traffic or uplink traffic may arrive may be specified by the <NUM> system back to the application or edge server, and back to the application function.

In some aspects, for example, the edge server <NUM> of <NUM> may be configured to know the periodicity of the burst of downlink traffic, such that the edge server <NUM> of <NUM> may decide the burst arrival time. Periodicity may refer to the time period between the start of two bursts. In some aspects, for example in diagram <NUM>, the edge server <NUM> may be configured to know the periodicity of the burst of downlink traffic, however, the <NUM> system <NUM> of <NUM> may be configured to decide the burst arrival time. Thus, the <NUM> system <NUM> of <NUM> may determine the burst arrive time in response to a request from the edge server <NUM> to server periodic traffic. In some aspects, UEs that are being served by the same cell are more likely to be offset than UEs in a different cell. In addition, UEs on non-orthogonal beams may be more likely to be offset than UEs on orthogonal beams.

<FIG> illustrate diagrams <NUM>, <NUM> directed to aligning uplink transmissions with downlink reception periods in accordance with certain aspects of the disclosure. Diagram <NUM> provides an example of the age of pose, which is the time from which a pose is first sampled (e.g., at <NUM>) until the pose is rendered (e.g., <NUM>). The rendering epoch <NUM> is the time when the downlink computation on the edge server starts, and when the pose is actually sent. For example, <NUM> is the first time the pose was actually sampled on the device (e.g., UE), and the time at which the pose was actually sent as an uplink transmission. The notion is that the older the pose, the more stale the pose information is going to be when the edge server starts its computation. It would be advantageous to reduce the age of the pose, in order to limit or minimize the staleness of the pose information. In some aspects, the UE may be configured to utilize the age of the pose or staleness of the pose information in order to capture pose information as close as possible to the uplink transmission time, because the UE would have an understanding of the server side data computation or rendering times.

The uplink transmission will not be sent at a random time, instead, the uplink transmission will be sent at <NUM>, which corresponds to an uplink slot. <NUM> has a slot structure wherein each slot has a set of duration, such that typical slot duration of the slot structure may be <NUM> (based on numerology) and each of the slots may be downlink only, uplink only, or can be a combination of uplink and downlink, which is what is indicated by the letter "S" in the slot structure of <FIG>. In the present disclosure, uplink transmissions may occur on S slots which supports uplink transmission because it has some uplink symbols. The S slot may include uplink symbols and the U slot may only comprise uplink symbols, such that uplink transmissions may occur on S or U slots. In some aspects, the uplink transmission may occur adjacent to a D or downlink slot where there was traffic allocated to the particular UE. Some D slots may have traffic allocated to the particular UE, but some D slot may not, because D slots may be shared across multiple users. If there is an allocation of downlink traffic for a particular UE, then the uplink traffic may be transmitted in the subsequent S and U slots, adjacent the D slot, such that the amount of time that the UE has to wake up may be reduced. As such, the UE may employ an increased idle time to facilitate transmission and reception of data during the same wake up duration, as shown, for example, in diagram <NUM> of <FIG>.

<FIG> is a call flow diagram of signaling between a base station and a UE in accordance with certain aspects of the disclosure. The diagram <NUM> of <FIG> includes a UE <NUM> and a base station <NUM>. The base station <NUM> may be configured to provide a cell. The UE <NUM> may be configured to communicate with the base station <NUM>. For example, in the context of <FIG>, the base station <NUM> may correspond to base station <NUM>/<NUM> and, accordingly, the cell may include a geographic coverage area <NUM> in which communication coverage is provided and/or small cell <NUM>' having a coverage area <NUM>'. Further, a UE <NUM> may correspond to at least UE <NUM>. In another example, in the context of <FIG>, the base station <NUM> may correspond to base station <NUM> and the UE <NUM> may correspond to UE <NUM>. Optional aspects are illustrated with a dashed line.

The UE <NUM> and base station <NUM> communicate using period bursts of UL data traffic and periodic bursts of DL data traffic. The data traffic may comprise XR data traffic.

As illustrated at <NUM>, the base station selects an offset time for at least one of the uplink data traffic or downlink data traffic. The time offset may be based on a timing difference between the downlink data traffic and the uplink data traffic. For example, the time offset for uplink traffic may be relative to the timing of the periodic bursts of uplink data traffic to increase an overlap of the uplink data traffic with the downlink data traffic. The time offset for the downlink traffic may be relative to the timing of the periodic bursts of downlink data traffic to increase an overlap of the downlink data traffic with the uplink data traffic. The base station selects the offset time to be applied to at least one of the uplink data traffic or downlink data traffic to increase an overlap between the uplink traffic bursts and the downlink traffic bursts. When uplink and downlink traffic burst start times are periodic, the base station selects offsets to the uplink and downlink traffic, to be conveyed to the AF, to maximize alignment/overlap between UL and DL traffic bursts. For example, if uplink bursts occur every <NUM>, and downlink bursts occur every <NUM>, when an application starts uplink at <NUM> offset with respect to <NUM>, and downlink starts with offset <NUM> to <NUM>, the alignment can be maximized by sending an offset of -<NUM> and -<NUM> to the uplink and downlink respectively. The offset for the UL traffic is communicated from the base station <NUM> to the UE <NUM>.

As illustrated at <NUM>, the base station <NUM> may configure a DRX cycle for the UE <NUM>. The base station <NUM> may configure the DRX cycle for the UE <NUM> based on a periodicity of traffic arrival for the periodic uplink traffic bursts and the periodic downlink traffic bursts. The DRX cycle may be configured based on overall periodicity of uplink and downlink traffic arrival.

In some aspects, the UL or DL transmissions may be grant-free or periodic grant transmissions. For example, at <NUM>, the base station may preconfigure resources for uplink transmissions from the UE <NUM>.

When uplink and downlink traffic burst start times are periodic, and the RAN has allocated resources for grant-free uplink transmission, the RAN can further decide on an offset, at <NUM>, to the downlink traffic to maximize alignment between uplink transmission resources and downlink traffic arrival. The DRX cycle may be planned based on overall periodicity of uplink transmission resources and downlink traffic arrival.

When uplink and downlink traffic burst start times are periodic, and the RAN has allocated resources for grant-free uplink transmission, the RAN can further decide on an offset, at <NUM>, to the downlink traffic and the corresponding grant-free downlink resource allocation so as to maximize alignment between uplink transmission resources and downlink transmission resources, e.g., in which the DRX cycle is planned based on overall periodicity of uplink transmission resources and downlink transmission resources.

When uplink and downlink traffic burst start times are periodic, and the RAN has allocated resources for grant-free downlink transmission, the RAN can further decide on an offset, at <NUM>, to the uplink traffic so as to maximize alignment between downlink transmission resources and uplink traffic arrival, e.g., in which the DRX cycle is planned based on overall periodicity of uplink traffic arrival and downlink transmission resources.

As illustrated at <NUM>, the UE <NUM> may determine a processing timeline for the communication. For example, a processing timeline in XR communication may include a plurality of epochs, wherein the application server performs data processing at the conclusion of each epoch, e.g., as described in connection with <FIG>.

As illustrated at <NUM>, for grant-based uplink transmissions, the UE may transmit an SR to the base station <NUM> and may receive a grant <NUM> from the base station for the uplink transmission. In some aspects, when uplink traffic burst start times are periodic, and the uplink is grant-based, and the RAN has allocated a DRX cycle, the UE can decide to delay sending the SR to the start of next DRX on time. This may apply when the DRX on time is slightly delayed compared to uplink traffic arrival time. In some aspects, when uplink traffic burst start times are periodic, and the uplink is grant-based, and the RAN has allocated a DRX cycle, the UE can send the SR at the start of next DRX on time ahead of uplink traffic arrival. This applies when the DRX on time is slightly ahead of uplink traffic arrival time. In some aspects, when uplink traffic burst start times are periodic, and the periodicity is not conveyed to the RAN, and the uplink is grant-based, and the RAN has allocated a DRX cycle, the UE can learn the periodicity of the uplink traffic and send the SR at the start of next DRX on time ahead of uplink traffic arrival.

Thus, the <NUM> system, e.g., <NUM> illustrated in <FIG>, may receive UL and DL traffic periodicities for UL traffic from the HMD <NUM> and DL traffic from the edge server <NUM>. The <NUM> system <NUM> may send an offset back to the HMD to maximize UL and DL alignment. The <NUM> system may also configure a DRX cycle for the UE, and therefore the HMD, based on the UL and DL traffic periodicities and the alignment based on offsets. Then, the <NUM> system may receive DL traffic from the edge server and UL traffic from the HMD via the UE. The DL traffic may be aligned with a DRX on portion of the DRX cycle configured for the UE. For example, the base station may hold DL traffic until the UE would be in DRX on. The hold time may be small, e.g., only accounting for jitter between the suggested offset and actual traffic arrival. The UL traffic may similarly be aligned with the DRX on state of the UE. The <NUM> system may.

UL traffic should be aligned with DRX on. The UE may hold UL traffic until the UE would be in DRX on. The hold time may be small, e.g., only accounting for jitter between the suggested offset and actual traffic arrival.

As illustrated at <NUM>, the UE <NUM> may adjust an uplink traffic burst. The UE <NUM> adjusts the uplink traffic burst based on the offset determined by the base station at <NUM>. The adjustment to the uplink traffic burst helps aligning transmission of uplink data burst(s) with the processing timeline such that uplink information, e.g., pose information, arrive just in time for rendering. The periodicity of the pose update(s) may be reduced to a periodicity of rendered traffic on the downlink. According to the claimed invention, the uplink traffic is adjusted adjusted to align the uplink transmission to the downlink reception time in order to prolong an idle time and the UE between the periodic traffic bursts and to save power. Thus, the UE may delay waking up, at <NUM>, until the UE's DRX on duration.

The UE may receive downlink traffic bursts, at <NUM>, and may transmit periodic uplink traffic bursts, at <NUM>, based on the adjustment at <NUM>.

<FIG> is a flowchart <NUM> of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., the base station <NUM>, <NUM>, <NUM>, <NUM>; the apparatus <NUM>; the baseband unit <NUM>, which may include the memory <NUM> and which may be the entire base station <NUM> or a component of the base station <NUM>, such as the TX processor <NUM>, the RX processor <NUM>, and/or the controller/processor <NUM>). One or more of the illustrated operations may be omitted, transposed, or contemporaneous. Optional aspects are illustrated with a dashed line. The method may allow a base station to be synchronized with the application server, such that the base station may align uplink transmissions of a UE with its downlink reception periods, thereby reducing resource consumption as well as power consumption.

At <NUM>, the base station may communicate with a UE. For example, <NUM> may be performed by reception component <NUM> of apparatus <NUM>. The base station communicates with the UE using periodic uplink traffic bursts and periodic downlink traffic bursts. The communication may comprise XR traffic, as described in connection with <FIG>.

At <NUM>, the base station selects a time offset to at least one of uplink traffic or downlink traffic. For example, <NUM> may be performed by offset component <NUM> of apparatus <NUM>. The base station selects the time offset to at least one of the uplink traffic of the downlink traffic to increase an overlap between the uplink traffic bursts and the downlink traffic bursts.

At <NUM>, the base station sends the time offset to an application function (AF). For example, <NUM> may be performed by offset component <NUM> of apparatus <NUM>. The base station may send the time offset to the application function via transmission component <NUM>.

In some aspects, for example at <NUM>, the UE may configure a DRX cycle for the UE. For example, <NUM> may be performed by DRX configuration component <NUM> of apparatus <NUM>. The UE may configure the DRX cycle for the UE based on a periodicity of traffic arrival for the periodic uplink traffic bursts and the periodic downlink traffic bursts.

In some aspects, for example at <NUM>, the base station may allocate resources for grant-free uplink transmission. For example, <NUM> may be performed by allocation component <NUM> of apparatus <NUM>. The time offset may be selected to increase an alignment between the resources allocated for the grant-free uplink transmission and downlink traffic arrival.

In some aspects, the time offset may be selected to offset the downlink traffic from the base station to increase an alignment between the resources allocated for the grant-free uplink transmission from a UE and downlink traffic arrival for the UE. When the base station configures the DRX cycle the base station may configure the DRX cycle for the UE based on a periodicity of the resources allocated for the grant-free uplink transmission and downlink traffic arrival.

In some aspects, the start times for the uplink traffic and the downlink traffic may be periodic. The time offset to the downlink traffic and the grant-free downlink resource allocation may be determined in a manner to increase alignment between uplink transmission resources and downlink transmission resources. The base station may configure the DRX cycle for the UE based on a periodicity of uplink transmission resources and downlink transmission resources.

In some aspects, the time offset determined for the uplink traffic may be determined to increase alignment between downlink transmission resources and uplink traffic arrival, e.g., when start times for the uplink traffic and the downlink traffic are periodic. The base station may configure the DRX cycle for the UE based on a periodicity of uplink transmission resources and downlink transmission resources.

In some aspects, for example at <NUM>, when start times for the uplink traffic and the downlink traffic are periodic, the base station may allocate resources for grant-free downlink transmission. For example, <NUM> may be performed by allocation component <NUM> of apparatus <NUM>. The base station may allocate resources for grant-free downlink transmission for uplink traffic and downlink traffic that are periodic. The time offset may be determined for the uplink traffic and the grant-free uplink resource allocation to increase alignment between uplink traffic arrival and downlink transmission resources. The base station may configure the DRX cycle for the UE based on a periodicity of uplink transmission resources and downlink transmission resources.

In some aspects, the base station may configure a DRX cycle for the UE based on a periodicity of uplink traffic arrival and downlink transmission resources. In some aspects, when the start times for the uplink traffic and downlink traffic are periodic, the base station may allocate resources for grant-free downlink transmission. The base station may determine the time offset to the uplink traffic and the grant-free uplink resource allocation to increase alignment between uplink transmission resources and downlink transmission resources. In some aspects, the base station may configure a DRX cycle for the UC based on a periodicity of uplink transmission resources and downlink transmission resources.

The apparatus <NUM> is a BS and includes a baseband unit <NUM>. The baseband unit <NUM> may communicate through a cellular RF transceiver with the UE <NUM>. The baseband unit <NUM> may include a computer-readable medium / memory. The baseband unit <NUM> is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the baseband unit <NUM>, causes the baseband unit <NUM> to perform the various functions described supra. The computer-readable medium / memory may also be used for storing data that is manipulated by the baseband unit <NUM> when executing software. The baseband unit <NUM> further includes a reception component <NUM>, a communication manager <NUM>, and a transmission component <NUM>. The components within the communication manager <NUM> may be stored in the computer-readable medium / memory and/or configured as hardware within the baseband unit <NUM>. The baseband unit <NUM> may be a component of the BS <NUM> and may include the memory <NUM> and/or at least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM>.

The communication manager <NUM> includes an offset component <NUM> that may select a time offset to at least one of uplink traffic or downlink traffic, e.g., as described in connection with <NUM> of <FIG>. The offset component <NUM> may send the time offset to an AF, e.g., as described in connection with <NUM> of <FIG>. The communication manager <NUM> further includes a DRX configuration component <NUM> that may configure a DRX cycle for the UE e.g., as described in connection with <NUM> of <FIG>. The communication manager <NUM> further includes an allocation component <NUM> that may allocate resources for grant-free uplink transmission, e.g., as described in connection with <NUM> of <FIG>. The allocation component <NUM> may allocate resources for grant-free downlink transmission, e.g., as described in connection with <NUM> of <FIG>. The reception component <NUM> of apparatus <NUM> may communicate with the UE, e.g., as described in connection with <NUM> of <FIG>.

In one configuration, the apparatus <NUM>, and in particular the baseband unit <NUM>, includes means for communicating with a UE using periodic uplink traffic bursts and periodic downlink traffic bursts. The apparatus includes means for selecting a time offset to at least one of uplink traffic or downlink traffic to increase an overlap between the uplink traffic bursts and the downlink traffic bursts. The apparatus includes means for sending the time offset to an AF. The apparatus further includes means for configuring a DRX cycle for the UE based on a periodicity of traffic arrival for the periodic uplink traffic bursts and the periodic downlink traffic bursts. The apparatus further includes means for allocating resources for grant-free uplink transmission, wherein the time offset is selected to increase an alignment between the resources allocated for the grant-free uplink transmission and downlink traffic arrival. The apparatus further includes means for configuring a DRX cycle for the UE based on a periodicity of the resources allocated for the grant-free uplink transmission and downlink traffic arrival. The apparatus further includes means for allocating resources for grant-free uplink transmission. The apparatus further includes means for determining the time offset to the downlink traffic and the grant-free downlink resource allocation to increase alignment between uplink transmission resources and downlink transmission resources. The apparatus further includes means for configuring a DRX cycle for the UE based on a periodicity of uplink transmission resources and downlink transmission resources. The apparatus further includes means for allocating resources for grant-free downlink transmission. The apparatus further includes means for determining the time offset for the uplink traffic to increase alignment between downlink transmission resources and uplink traffic arrival. The apparatus further includes means for configuring a DRX cycle for the UE based on a periodicity of uplink traffic arrival and downlink transmission resources. The apparatus further includes means for allocating resources for grant-free downlink transmission. The apparatus further includes means for determining the time offset to the uplink traffic and the grant-free uplink resource allocation to increase alignment between uplink transmission resources and downlink transmission resources. The apparatus further includes means for configuring a DRX cycle for the UE based on a periodicity of uplink transmission resources and downlink transmission resources. The aforementioned means may be one or more of the aforementioned components of the apparatus <NUM> configured to perform the functions recited by the aforementioned means. As described supra, the apparatus <NUM> may include the TX Processor <NUM>, the RX Processor <NUM>, and the controller/processor <NUM>.

<FIG> are flowcharts <NUM>, <NUM>, <NUM>, <NUM>, <NUM> of methods of wireless communication. The methods may be performed by a UE or a component of a UE (e.g., the UE <NUM>, <NUM>, <NUM>; the apparatus <NUM>; the cellular baseband processor <NUM>, which may include the memory <NUM> and which may be the entire UE <NUM> or a component of the UE <NUM>, such as the TX processor <NUM>, the RX processor <NUM>, and/or the controller/processor <NUM>). One or more of the illustrated operations may be omitted, transposed, or contemporaneous. Optional aspects are illustrated with a dashed line. The methods may allow a UE to reduce power consumption by aligning uplink transmissions to downlink receptions, which may allow the UE to extend its idle time and save power.

At <NUM>, the UE communicates with a base station. For example, <NUM> may be performed by reception component <NUM> and/or transmission component <NUM> of apparatus <NUM>. The UE may communicate with the base station using periodic uplink traffic bursts and periodic downlink traffic bursts. The communication may comprise XR traffic, e.g., as described in connection with any of <FIG>.

At <NUM>, the UE may receive a configuration for a DRX cycle based on the periodic uplink and downlink traffic bursts. For example, <NUM> may be performed by DRX component <NUM> of apparatus <NUM>. Uplink transmissions from the UE may be grant based. Example aspects of configuring a DRX cycle are described in connection with <NUM> in <FIG>. For example, DRX component <NUM> of apparatus <NUM> may receive the DRX configuration.

At <NUM>, the UE may delay sending an SR for uplink traffic to a beginning of a next DRX cycle. For example, <NUM> may be performed by SR component <NUM> of apparatus <NUM>. The SR may be sent or delayed by SR component <NUM> of apparatus <NUM>.

At <NUM>, the UE communicates with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts. For example, <NUM> may be performed by reception component <NUM> or transmission component <NUM> of apparatus <NUM>. The communication may comprise XR traffic, e.g., as described in connection with any of <FIG>.

At <NUM>, the UE may receive a configuration for a DRX cycle based on the periodic uplink and downlink traffic bursts. For example, <NUM> may be performed by DRX component <NUM> of apparatus <NUM>. The UE's uplink transmissions may be grant based. Example aspects of configuring a DRX cycle are described in connection with <NUM> in <FIG>.

At <NUM>, the UE may transmit an SR prior to an arrival of the uplink traffic when the arrival of uplink traffic burst is expected to arrive within the next DRX cycle. For example, <NUM> may be performed by SR component <NUM> of apparatus <NUM>. The SR may be sent based on a prediction or estimation that uplink traffic will arrive, e.g., based on a previous pattern of uplink traffic bursts.

At <NUM>, the UE communicates with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts. For example, <NUM> may be performed by reception component <NUM> or transmission component <NUM> of apparatus <NUM>. The communication may comprise XR traffic, e.g., as described in connection with any of <FIG>. A periodicity of uplink traffic arrivals might not be conveyed to the UE.

At <NUM>, the UE determines the periodicity of the uplink traffic. For example, <NUM> may be performed by determination component <NUM> of apparatus <NUM>. The UE may determine the periodicity based on a previous pattern of arrival of uplink traffic for transmission to the base station.

At <NUM>, the UE may send an SR for the uplink traffic at a beginning of a next DRX cycle prior to an uplink traffic burst arrival when the uplink traffic burst arrival is expected to arrive within the next DRX cycle. For example, <NUM> may be performed by SR component <NUM> of apparatus <NUM>. The SR may be sent based on a prediction or estimation that uplink traffic will arrive, e.g., based on a previous pattern of uplink traffic bursts.

At <NUM>, the UE may delay sending an SR for uplink traffic to a beginning of a next DRX cycle. For example <NUM> may be performed by SR component <NUM> of apparatus <NUM>.

At <NUM>, the UE may communicate with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts. For example, <NUM> may be performed by reception component <NUM> or transmission component <NUM> of apparatus <NUM>. The communication may comprise XR traffic, e.g., as described in connection with any of <FIG>. A periodicity of uplink traffic arrivals might not be conveyed to the UE.

At <NUM>, the UE may select a time offset to at least one of uplink traffic or downlink traffic. For example, <NUM> may be performed by offset component <NUM> of apparatus <NUM>. The UE may select the time offset to at least one of uplink traffic or downlink traffic to increase overlap between the uplink traffic bursts and the downlink traffic bursts.

At <NUM>, the UE may send the time offset to an application client. For example, <NUM> may be performed by transmission component <NUM> of apparatus <NUM>.

The communication manager <NUM> includes a DRX component <NUM> that is configured to configure a DRX cycle based on the periodic uplink and downlink traffic bursts, e.g., as described in connection with <NUM> of <FIG>. The DRX component <NUM> is configured to receive a configuration for a DRX cycle based on the periodic uplink and downlink traffic bursts, e.g., as described in connection with <NUM> of <FIG>. The communication manager <NUM> further includes an SR component <NUM> that is configured to delay sending an SR for uplink traffic to a beginning of a next DRX cycle, e.g., as described in connection with <NUM> of <FIG>. The SR component <NUM> may transmit an SR prior to an arrival of the uplink traffic when the arrival of uplink traffic burst is expected to arrive within the next DRX cycle, e.g., as described in connection with <NUM> of <FIG>. The SR component <NUM> may send an SR for the uplink traffic at a beginning of a next DRX cycle prior to an uplink traffic burst arrival when the uplink traffic burst arrival is expected to arrive within the next DRX cycle, e.g., as described in connection with <NUM> of <FIG>. The SR component <NUM> may delay sending an SR for uplink traffic to a beginning of a next DRX cycle, e.g., as described in connection with <NUM> of <FIG>. The communication manager <NUM> further includes a determination component <NUM> that is configured to determine the periodicity of the uplink traffic, e.g., as described in connection with <NUM> of <FIG>. The determination component <NUM> determines the periodicity of the uplink traffic, e.g., as described in connection with <NUM> of <FIG>. The communication manager <NUM> further includes an offset component <NUM> that is configured to select a time offset to at least one of uplink traffic or downlink traffic, e.g., as described in connection with <NUM> of <FIG>. The reception component <NUM> or transmission component <NUM> may be configured to communicate with a base station, e.g., as described in connection with <NUM> of <FIG>, <NUM> of <FIG>, <NUM> of <FIG>, <NUM> of <FIG>, or <NUM> of <FIG>. The transmission component <NUM> may be configured to send a time offset to an application client, e.g., as described in <NUM> of <FIG>.

In one configuration, the apparatus <NUM>, and in particular the cellular baseband processor <NUM>, includes means for communicating with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts. The apparatus includes means for configuring a DRX cycle based on the periodic uplink and downlink traffic bursts, wherein uplink transmission are grant based. The apparatus includes means for delaying sending a scheduling request (SR) for uplink traffic to a beginning of a next DRX cycle. The apparatus includes means for receiving a configuration of a DRX cycle based on the periodic uplink and downlink traffic bursts, wherein uplink transmission are grant based. The apparatus includes means for transmitting an SR prior to an arrival of the uplink traffic when the arrival of uplink traffic burst is expected to arrive within the next DRX cycle. The apparatus includes means for communicating with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts, wherein a periodicity of uplink traffic arrivals is not conveyed to the UE. The apparatus includes means for determining, by the UE, the periodicity of the uplink traffic. The apparatus includes means for sending a scheduling request (SR) for the uplink traffic at a beginning of a next DRX cycle prior to an uplink traffic burst arrival when the uplink traffic burst arrival is expected to arrive within the next DRX cycle. The apparatus includes means for delaying sending a scheduling request (SR) for the uplink traffic to a beginning of a next DRX cycle. The aforementioned means may be one or more of the aforementioned components of the apparatus <NUM> configured to perform the functions recited by the aforementioned means. As described supra, the apparatus <NUM> may include the TX Processor <NUM>, the RX Processor <NUM>, and the controller/processor <NUM>.

Claim 1:
A method of wireless communication executed by a base station comprising:
communicating (<NUM>) with a user equipment, UE, using periodic uplink traffic bursts and periodic downlink traffic bursts;
selecting (<NUM>), based on a processing timeline associated with an application function, AF, a time offset to be applied by at least one of the UE to uplink traffic to the AF or by the AF to downlink traffic to the UE,
wherein the time offset aligns uplink transmissions of the periodic uplink traffic bursts and downlink receptions of the periodic downlink traffic bursts for the UE; and
sending (<NUM>) the time offset to the UE to be applied by the UE to the uplink traffic to the AF or to the AF to be applied by the AF to the downlink traffic to the UE.