Wireless communications including extended reality (XR) traffic awareness

Abstract

A configuration that allows a base station to synchronize with an application server so that the base station can align an uplink transmission of a UE with a downlink reception period of the UE. The base station communicates with the UE using periodic uplink traffic bursts and periodic downlink traffic bursts. The base station selects a time offset from at least one of the uplink traffic or the downlink traffic to increase an overlap between the uplink traffic burst and the downlink traffic burst. The base station sends the time offset to an AF.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application SN 62 / 865849, entitled “Wireless Communication including XR Traffic Awareness,” filed on June 24, 2019, and U.S. Patent Application No. 16 / 903,312, entitled “Wireless Communication including XR Traffic Awareness,” filed on June 16, 2020, the entire contents of both of which are expressly incorporated herein by reference.

[0003] background Technical Field

[0004] The present disclosure relates generally to communication systems, and more particularly to wireless communications associated with extended reality (XR) traffic.

[0005] introduction

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

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

[0008] Overview

[0009] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be presented later.

[0010] Extended reality (XR) can be used for different applications. For example, XR may involve a combination of real and virtual environments and human-computer interactions generated by computer technology and wearable devices. As an example, XR communication may be used for cloud gaming, virtual reality (VR) split rendering, and / or augmented reality (AR) split computing. XR communication may occur in conjunction with an edge server on a 5G NR system. For example, a UE may receive XR data, which may be transmitted to a base station, which may provide the XR data to a core network. The core network may interface with the edge server and provide the XR data to the edge server. However, the 5G system and edge server may be based on independent clocks so that computing and communication may be uncoordinated. The present disclosure allows the 5G system and edge server to be synchronized to improve and coordinate computing and communication.

[0011] In one aspect of the present disclosure, a method, a computer readable medium, and an apparatus are provided. The apparatus may be a device at a base station. The apparatus may be a processor and / or a modem at a base station or the base station itself. The apparatus communicates with a user equipment (UE) using periodic uplink traffic bursts and periodic downlink traffic bursts. The apparatus selects a time offset from at least one of uplink traffic or downlink traffic to increase an overlap between the uplink traffic burst and the downlink traffic burst. The apparatus sends the time offset to an application function (AF).

[0012] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus at a UE. The apparatus may be a processor and / or a modem at a UE or the UE itself. The apparatus communicates with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts. The apparatus configures a discontinuous reception (DRX) cycle based on the periodic uplink traffic bursts and the periodic downlink traffic bursts, wherein the uplink transmission is based on a grant. The apparatus delays sending a scheduling request (SR) for uplink traffic until the start of the next DRX cycle.

[0013] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus at a UE. The apparatus may be a processor and / or a modem at a UE or the UE itself. The apparatus communicates with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts. The apparatus receives a configuration of a DRX cycle based on the periodic uplink traffic bursts and the periodic downlink traffic bursts, wherein uplink transmission is based on a grant. The apparatus transmits a scheduling request (SR) before the arrival of uplink traffic when the arrival of the uplink traffic burst is expected to arrive within the next DRX cycle.

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

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

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

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

[0019] Figure 4 This is a diagram explaining XR on the 5G system.

[0020] Figure 5A is a diagram illustrating the timeline of XR without synchronization.

[0021] Figure 5B is a diagram illustrating the periodic or quasi-periodic nature of XR traffic.

[0022] Figure 6 is a diagram illustrating an edge server synchronized with a 5G system according to certain aspects of the present disclosure.

[0023] Figure 7A-7B A diagram illustrating an edge server and a 5G system in accordance with certain aspects of the present disclosure.

[0024] Figures 8A-8BDiagram illustrating aligning uplink transmission with downlink reception periods in accordance with certain aspects of the present disclosure.

[0025] Fig. 9 is a call flow diagram of signaling between a UE and a base station according to certain aspects of the present disclosure.

[0026] Fig.10 is a flow chart of a wireless communication method.

[0027] Fig.11 is a diagram illustrating an example of a hardware implementation for a device employing a processing system.

[0028] Fig.12 is a flow chart of a wireless communication method.

[0029] Fig.13 is a flow chart of a wireless communication method.

[0030] Fig.14 is a flow chart of a wireless communication method.

[0031] Fig.15 is a flow chart of a wireless communication method.

[0032] Fig.16 is a flow chart of a wireless communication method.

[0033] Fig.17 is a diagram illustrating an example of a hardware implementation for a device employing a processing system.

[0034] Detailed Description

[0035] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid diluting such concepts.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0049] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmission reception point (TRP), or some other suitable term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a health care device, an implant, a sensor / actuator, a display, or any other similar functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, etc.). UE 104 may 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 communication 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.

[0050] Refer again Figure 1 In some aspects, base station 180 may be configured to align uplink transmissions and downlink receptions of a UE. For example, Figure 1The base station 180 may include an offset time component 198 configured to select an offset time for transmitting periodic downlink traffic bursts to the UE based on a processing timeline associated with the application server. The base station 180 may use periodic uplink traffic bursts and periodic downlink traffic bursts to communicate with the UE. The base station 180 may select a time offset with at least one of the uplink traffic or the downlink traffic to increase the overlap between the uplink traffic burst and the downlink traffic burst. The base station 180 may send the time offset to an application function (AF).

[0051] Refer again Figure 1 In some aspects, UE 104 may be configured to adjust its uplink transmissions to synchronize with a processing timeline associated with an application server. For example, Figure 1 The UE 104 may include a synchronization component 199 configured to adjust periodic uplink traffic bursts from the UE based on the offset to synchronize the UE with the processing timeline.

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

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

[0054] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ0 to 4 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration vary depending on parameter design. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter design 0 to 4. Thus, parameter design μ=0 has a subcarrier spacing of 15kHz, while parameter design μ=4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2DAn example of a slot configuration 0 with 14 symbols per slot and a parameter design μ=2 and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP may have a specific parameter design.

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

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

[0057] Figure 2BAn example of various DL channels within a subframe of a frame is illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including 9 RE groups (REGs), each REG including 4 consecutive REs in an OFDM symbol. The PDCCH within a BWP may be referred to as a control resource set (CORESET). Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth, and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH (such as the system information block (SIB)), and paging messages.

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

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

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

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

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

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

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

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

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

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

[0068] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 199 combined aspects.

[0069] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 198 combined aspects.

[0070] Table 1 illustrates examples of QoS parameters for different types of communications. The table indicates 5G QoS indicator (5QI) values ​​for corresponding packet delay budgets (PDBs), packet error rates (PERs), default maximum data burst (MDB) amounts, and example services for the 5QI values. The examples shown for 5QI values ​​1, 2, 6, 8, and 9 may correspond to eMBB use cases. The examples for eMBB may correspond to various different types of traffic. The example shown for 5QI value 80 may correspond to an XR use case, and the example shown for 5QI value 81 may correspond to a URLLC use case. For low data rate traffic, URLLC may have very low latency (e.g., PDB ≤ 5 milliseconds) and high reliability (e.g., PER ≤ 10 -5 ). XR communication can have high reliability (e.g., PER≤10 -3 ) and low latency (e.g., PDB in the range of 5ms≤PDB≤25ms). However, compared to URLLC, XR can have a higher bit rate.

[0071] Table 1

[0072]

[0073] XR can be used for different applications. For example, XR can involve a combination of real and virtual environments and human-computer interactions generated by computer technology and wearable devices. As an example, XR communications can be used for cloud gaming, virtual reality (VR) split rendering, and / or augmented reality (AR) split computing. Table 2 illustrates a chart showing example uses for XR.

[0074] surface"

[0075]

[0076] Figure 4 An example system model 400 for XR communications over a 5G NR system is illustrated. Figure 4 A head mounted display (HMD) 402 that can be worn by a user is illustrated. The HMD can send and receive XR communications with an edge server 408 via a 5G communication system 404, for example, as combined with Figure 1 Detailed description. The 5G system may also be referred to as the NR system. Figure 4 The 5G system is illustrated as including a UE 403 that transmits / receives communications with a RAN 405 that transmits / receives communications with a network component 407. The UE may correspond to Figure 1 UE 104 in, and the core network component 407 may correspond to Figure 1 The core network 190 in RAN may correspond to Figure 1 403. Thus, the UE 403 may receive XR data from the HMD and transmit the XR data to the base station, which may provide the data to the core network 407. The core network 407 may interface with an edge server 408 to provide the data to the edge server. Similarly, the edge server 408 may provide the data to the HMD by providing the data to the core network 407, which passes the data to the base station, which transmits the data to the UE 403 as a downlink communication. The UE 403 may provide the received downlink data to the HMD, for example, via a wireless or wired connection to the HMD. Thus, the 5G system 404 may transmit and receive traffic with an edge server 408, which is illustrated as including an XR edge data network (DN) and an XR edge application function (AF). As illustrated, traffic may be communicated using the N5 / N33 network external interface and / or the N6 interface (e.g., Real-time Transport Protocol (RTP)-User Datagram Protocol (UDP)) between the 5GC-UPF and the XR edge DN.

[0077] The 5G system 404 or the NR system may provide QoS for XR communications. The XR session may be hosted at an edge server 408, which may be an operator server or a third-party server. It may be assumed that the latency between the core network component 407 and the edge server 408 is negligible. Communications between the Hypertext Transfer Protocol (HTTP) to the Transmission Control Protocol (TCP) may use the latency in the latency budget for XR communications.

[0078] Figure 5BAn example graph 550 showing the periodic or quasi-periodic nature of XR traffic is illustrated. The height of each row indicates the file size of the XR traffic. As illustrated, similar amounts of data and data sizes may be communicated in periodic traffic bursts. XR may involve periodic rendering processes, each within a separate epoch corresponding to a length of time. The HMD may determine and send periodic bursts of information (e.g., position / orientation information of the HMD) to an edge server. The edge server may process the position / orientation information and provide rendering information back to the HMD.

[0079] The 5G system 404, edge server 408 computing, and device computing 402 may be based on independent clocks, for example, a clock at the HMD 402 and a clock at the edge server 408. Therefore, computing and communication may not be coordinated. Figure 5A An example timeline 500 of XR without synchronization is illustrated showing resource contention between two users. Computing resources and radio resources (e.g., 5G NR radio resources) may be dimensioned for reliability under peak load. Under low latency budgets, higher resource contention may occur in peak load situations, such as Figure 5A Explained in .

[0080] Figure 6 A diagram 600 is provided to illustrate an edge server synchronized with a 5G system according to certain aspects of the present disclosure. Diagram 600 includes an edge server 602, a 5G network (which includes a core network and a RAN) generalized by a box 604, and further includes a plurality of terminal system devices 606. In some aspects, the edge server and the device computing nodes and the communication nodes may be configured to synchronize their respective clocks. Then, due to synchronization, computing and communication can be scheduled at a deterministic time, which can minimize peak loads. At least one advantage of the present disclosure is that synchronizing the 5G system and the edge server can optimize the allocation of downlink and / or uplink resources. For example, a base station of a 5G system can schedule the uplink resources of each UE to be consistent with the downlink reception of the UE. This can allow the UE to wake up from an idle mode in order to transmit and receive during the same wake-up duration, rather than waking up only for transmission and then waking up again for reception, and vice versa.

[0081] Figure 7A-7BDiagrams 700 and 750 of edge servers and 5G systems according to certain aspects of the present disclosure are illustrated. Diagram 700 includes a 5G system 702 and an edge server 704. Edge server 704 can be a server located close enough to a 5G network so that the latency between the edge server and the 5G network is small and negligible. Diagrams 700 and 750 disclose different aspects involving the communication of "burst arrival time" information. "Burst arrival time" can be the arrival time of a data burst at the inlet of a RAN (e.g., downlink flow direction) or the egress interface of a UE (e.g., uplink flow direction). Providing burst arrival time assists in achieving a synchronized system. A synchronized system can occur, for example, when the clocks of a 5G system and an edge server are synchronized with each other or the corresponding clocks can be synchronized to a reference clock. In this way, the time at which a burst of downlink traffic or uplink traffic may arrive can be specified by the 5G system back to an application or edge server, and specified back to an application function.

[0082] In some aspects, for example, the edge server 704 of 700 may be configured to know the periodicity of the downlink traffic burst so that the edge server 704 of 700 can determine the burst arrival time. Periodicity may refer to the time period between the start of two bursts. In some aspects, for example, in diagram 750, the edge server 704 may be configured to know the periodicity of the downlink traffic burst, however, the 5G system 702 of 750 may be configured to determine the burst arrival time. Therefore, the 5G system 702 of 750 may determine the burst arrival time in response to the request for server periodic traffic from the edge server 704. In some aspects, the UE being served by the same cell is more likely to be offset than the UE in different cells. In addition, the UE on the non-orthogonal beam may be more likely to be offset than the UE on the orthogonal beam.

[0083] Figures 8A-8BIllustrated are diagrams 800, 850 relating to aligning uplink transmissions with downlink reception periods according to certain aspects of the present disclosure. Diagram 800 provides an example of a posture epoch, which is the time from when a posture is first sampled (e.g., at 802) until the posture is rendered (e.g., 804). The rendering epoch 804 is the time when the downlink calculation is started on the edge server and when the posture is actually sent. For example, 802 is the first time that a posture is actually sampled on a device (e.g., a UE), and the time when the posture is actually sent as an uplink transmission. The concept is that the older the posture is when the edge server starts its calculation, the older the posture information will be. In order to limit or minimize the staleness of the posture information, it would be advantageous to reduce the posture epoch. In some aspects, the UE may be configured to exploit the staleness of the posture epoch or posture information in order to capture posture information as close to the uplink transmission time as possible, because the UE will have an understanding of the server-side data calculation or rendering time.

[0084] Uplink transmissions will not be sent at random times, instead, uplink transmissions will be sent at 806 corresponding to uplink time slots. 5G has a slot structure where each slot has a set duration such that a typical slot duration for the slot structure may be 0.5 ms (based on the parameter set), and each of the slots may be downlink only, uplink only, or a combination of uplink and downlink (this is in Fig. 8A In the present disclosure, an uplink transmission may occur on an S time slot that supports uplink transmission because the S time slot has some uplink symbols. The S time slot may include uplink symbols and the U time slot may include only uplink symbols so that the uplink transmission may occur on an S time slot or a U time slot. In some aspects, an uplink transmission may occur adjacent to a D time slot or a downlink time slot in which there is traffic allocated to a specific UE. Some D time slots may have traffic allocated to a specific UE, but some D time slots may not have traffic allocated to a specific UE because the D time slot may be shared across multiple users. If there is an allocation of downlink traffic for a specific UE, the uplink traffic may be transmitted in subsequent S time slots and U time slots adjacent to the D time slot so that the amount of time the UE must wake up may be reduced. In this way, the UE can employ increased idle time to facilitate the transmission and reception of data during the same wake-up duration, such as, for example, in Figure 8B As shown in diagram 850 .

[0085] Fig. 9 is a call flow diagram of signaling between a base station and a UE according to certain aspects of the present disclosure. Fig. 9The diagram 900 includes a UE 902 and a base station 904. The base station 904 can be configured to provide a cellular cell. The UE 902 can be configured to communicate with the base station 904. For example, in Figure 1 In the context of , base station 904 may correspond to base station 102 / 180, and accordingly, a cellular cell may include a geographic coverage area 110 in which communication coverage is provided and / or a small cellular cell 102' having a coverage area 110'. Further, UE 902 may correspond to at least UE 104. In another example, in Figure 3 In the context of , base station 904 may correspond to base station 310, and UE 902 may correspond to UE 350. Optional aspects are illustrated with dashed lines.

[0086] UE 902 and base station 904 may communicate using periodic bursts of UL data traffic and periodic bursts of DL data traffic. The data traffic may include XR data traffic.

[0087] As explained in 908, the base station can select an offset time for at least one of the uplink data traffic or the downlink data traffic. The time offset can be based on the timing difference between the downlink data traffic and the uplink data traffic. For example, the time offset for the uplink traffic can be relative to the timing of the periodic bursts of the uplink data traffic to increase the overlap of the uplink data traffic and the downlink data traffic. The time offset for the downlink traffic can be relative to the timing of the periodic bursts of the downlink data traffic to increase the overlap of the downlink data traffic and the uplink data traffic. The base station can select the offset time to be applied to at least one of the uplink data traffic or the downlink data traffic to increase the overlap between the uplink traffic burst and the downlink traffic burst. For example, in the case where the uplink and downlink traffic burst start times are periodic, the base station can select the offset to be communicated to the AF with the uplink and downlink traffic to maximize the alignment / overlap between the UL and DL traffic bursts. For example, if uplink bursts occur every 4 ms and downlink bursts occur every 8 ms, then in the case where the application starts the uplink with a 3 ms offset relative to 0 and the downlink with a 2 ms offset relative to 0, the alignment can be maximized by sending an offset of -3 ms and -2 ms for the uplink and downlink, respectively. The offset for UL traffic can be communicated from the base station 904 to the UE 902.

[0088] As illustrated at 910, the base station 904 may configure a DRX cycle for the UE 902. The base station 904 may configure the DRX cycle for the UE 902 based on the periodicity of traffic arrivals of periodic uplink traffic bursts and periodic downlink traffic bursts. The DRX cycle may be configured based on the overall periodicity of uplink and downlink traffic arrivals.

[0089] In some aspects, the UL or DL ​​transmission may be a grant-free transmission or a periodic grant transmission.For example, at 906, the base station may preconfigure resources for uplink transmissions from UE 902.

[0090] In the case that the uplink and downlink traffic burst start times are periodic and the RAN has allocated resources for grant-free uplink transmissions, the RAN may further decide on an offset from the downlink traffic to maximize the alignment between the uplink transmission resources and the downlink traffic arrival at 908. The DRX cycle may be planned based on the overall periodicity of the uplink transmission resources and the downlink traffic arrival.

[0091] In case the uplink and downlink traffic burst start times are periodic and the RAN has allocated resources for no-grant uplink transmission, the RAN may further determine at 908 an offset to the downlink traffic and the corresponding no-grant downlink resource allocation so as to maximize the alignment between the uplink transmission resources and the downlink transmission resources, for example, where the DRX cycle is planned based on the overall periodicity of the uplink transmission resources and the downlink transmission resources.

[0092] In case the uplink and downlink traffic burst start times are periodic and the RAN has allocated resources for ungranted downlink transmissions, the RAN may further determine an offset from the uplink traffic at 908 in order to maximize the alignment between the downlink transmission resources and the uplink traffic arrival, e.g., where the DRX cycle is planned based on the overall periodicity of the uplink traffic arrival and the downlink transmission resources.

[0093] As illustrated at 912, the UE 902 may determine a processing timeline for the communication. For example, a processing timeline in an XR communication may include multiple epochs, where an application server performs data processing at the end of each epoch, e.g., as described in conjunction with Figure 8B as described.

[0094] As illustrated at 914, for grant-based uplink transmissions, the UE may transmit an SR to the base station 904 and may receive a grant 916 for the uplink transmission from the base station. In some aspects, where the uplink traffic burst start time is periodic and the uplink is grant-based and the RAN has assigned a DRX cycle, the UE may decide to delay sending the SR to the start of the next DRX on time. This may be applicable when the DRX on time is slightly delayed compared to the uplink traffic arrival time. In some aspects, where the uplink traffic burst start time is periodic and the uplink is grant-based and the RAN has assigned a DRX cycle, the UE may send the SR at the start of the next DRX on time that is earlier than the uplink traffic arrival time. This is applicable when the DRX on time is slightly earlier than the uplink traffic arrival time. In some aspects, where the uplink traffic burst start time is periodic and the periodicity is not communicated to the RAN, and the uplink is grant-based and the RAN has assigned a DRX cycle, the UE can learn the periodicity of the uplink traffic and send an SR at the start of the next DRX on time earlier than the arrival of the uplink traffic.

[0095] Therefore, 5G systems (e.g. Figure 4 404 as explained in the figure) can receive UL traffic periodicity for UL traffic from HMD 402 and DL traffic periodicity for DL ​​traffic from edge server 408. 5G system 404 can send an offset back to the HMD to maximize UL and DL alignment. The 5G system can also configure a DRX cycle for the UE based on the UL and DL traffic periodicity and the alignment based on the offset, and thus configure a DRX cycle for the HMD. Subsequently, the 5G system can receive DL traffic from the edge server and UL traffic from the HMD via the UE. The DL traffic can be aligned with the DRX on portion of the DRX cycle configured for the UE. For example, the base station can hold the DL traffic until the UE is in DRX on. The holding time can be small, for example, only taking into account the jitter between the recommended offset and the actual traffic arrival. The UL traffic can be similarly aligned with the DRX on state of the UE.

[0096] 5G systems may

[0097] UL traffic should be aligned with DRX on. The UE may hold UL traffic until the UE is in DRX on. The holding time may be small, for example, only accounting for the jitter between the suggested offset and the actual traffic arrival.

[0098] As illustrated at 918, UE 902 may adjust uplink traffic bursts. UE 902 may adjust uplink traffic bursts based on the offset determined by the base station at 908. Adjustment of uplink traffic bursts may help align the transmission of (all) uplink data bursts with the processing timeline so that uplink information (e.g., posture information) arrives just in time for rendering. The periodicity of (all) posture updates may be reduced to the periodicity of rendered traffic on the downlink. In some aspects, uplink traffic may be adjusted to align uplink transmission with downlink reception time in order to extend the idle time of the UE between periodic traffic bursts and save power. Therefore, the UE may delay waking up at 920 until the DRX on duration of the UE.

[0099] The UE may receive a downlink traffic burst at 922 and may transmit a periodic uplink traffic burst based on the adjustment at 918 at 924 .

[0100] Fig.10 1000 is a flow chart of a wireless communication method. The method may be performed by a base station or a component of a base station (e.g., base station 102, 180, 310, 904; device 1102; baseband unit 1104, which may include memory 376 and which may be the entire base station 310 or a component of the base station 310 (such as TX processor 316, RX processor 370 and / or controller / processor 375)). One or more of the illustrated operations may be omitted, transposed, or performed simultaneously. Optional aspects are illustrated with dashed lines. The method may allow the base station to synchronize with an application server so that the base station can align the UE's uplink transmission with its downlink reception period, thereby reducing resource consumption and power consumption.

[0101] At 1002, a base station may communicate with a UE. For example, 1002 may be performed by a receiving component 1130 of the device 1102. The base station may communicate with the UE using periodic uplink traffic bursts and periodic downlink traffic bursts. The communication may include XR traffic, such as in conjunction with Figure 4-9 as described.

[0102] At 1004, the base station may select a time offset from at least one of the uplink traffic or the downlink traffic. For example, 1004 may be performed by the offset component 1140 of the device 1102. The base station may select a time offset from at least one of the uplink traffic or the downlink traffic to increase an overlap between the uplink traffic burst and the downlink traffic burst.

[0103] At 1006, the base station can send the time offset to an application function (AF). For example, 1006 can be performed by an offset component 1140 of the device 1102. The base station can send the time offset to the application function via a transmission component 1106.

[0104] In some aspects, for example, at 1008, the UE may configure a DRX cycle for the UE. For example, 1008 may be performed by a DRX configuration component 1142 of the device 1102. The UE may configure the DRX cycle for the UE based on the periodicity of traffic arrivals of the periodic uplink traffic bursts and the periodic downlink traffic bursts.

[0105] In some aspects, for example, a base station may allocate resources for a no-grant uplink transmission at 1010. For example, 1010 may be performed by an allocating component 1144 of device 1102. The time offset may be selected to increase alignment between resources allocated for no-grant uplink transmission and arrival of downlink traffic.

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

[0107] In some aspects, the start time of uplink traffic and downlink traffic may be periodic. The time offset from downlink traffic and no grant of downlink resource allocation may be determined in a manner that increases the alignment between uplink transmission resources and downlink transmission resources. The base station may configure a DRX cycle for the UE based on the periodicity of the uplink transmission resources and downlink transmission resources.

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

[0109] In some aspects, for example, at 1012, in the case where the start time of uplink traffic and downlink traffic is periodic, the base station may allocate resources for no grant downlink transmission. For example, 1012 may be performed by the allocation component 1144 of the device 1102. The base station may allocate resources for no grant downlink transmission for periodic uplink traffic and downlink traffic. The time offset may be determined for uplink traffic and no grant uplink resource allocation to increase the alignment between uplink traffic arrival and downlink transmission resources. The base station may configure a DRX cycle for the UE based on the periodicity of the uplink transmission resources and the downlink transmission resources.

[0110] In some aspects, the base station may configure a DRX cycle for the UE based on the periodicity of the uplink traffic arrival and the downlink transmission resources. In some aspects, the base station may allocate resources for no grant downlink transmission when the start time of the uplink traffic and the downlink traffic is periodic. The base station may determine a time offset from the uplink traffic and the no grant uplink resource allocation to increase the alignment between the uplink transmission resources and the downlink transmission resources. In some aspects, the base station may configure a DRX cycle for the UE based on the periodicity of the uplink transmission resources and the downlink transmission resources.

[0111] Fig.11 1102 is an example of a hardware implementation of the device 1100. The device 1102 is a BS and includes a baseband unit 1104. The baseband unit 1104 can communicate with the UE 104 through a cellular RF transceiver. The baseband unit 1104 may include a computer-readable medium / memory. The baseband unit 1104 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 1104, enables the baseband unit 1104 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 1104 when executing the software. The baseband unit 1104 further includes a receiving component 1130, a communication manager 1132, and a transmission component 1134. The communication manager 1132 includes one or more of the illustrated components. The components within the communication manager 1132 can be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 1104. The baseband unit 1104 may be a component of the BS 310 and may include a memory 376 and / or at least one of: the TX processor 316 , the RX processor 370 , and the controller / processor 375 .

[0112] The communication manager 1132 includes an offset component 1140 that can select a time offset from at least one of the uplink traffic or the downlink traffic, for example, as combined with Fig.10The offset component 1140 can send the time offset to the AF, for example, as described in conjunction with Fig.10 The communication manager 1132 further includes a DRX configuration component 1142, which configures a DRX cycle for the UE, for example, as described in conjunction with Fig.10 The communication manager 1132 further includes an allocation component 1144, which can allocate resources for ungranted uplink transmissions, for example, as described in conjunction with Fig.10 The allocation component 1144 described in 1010 can allocate resources for ungranted downlink transmissions, for example, as combined Fig.10 The receiving component 1130 of the device 1102 described in 1012 can communicate with the UE, for example, as combined Fig.10 As described in 1002.

[0113] The apparatus may include executing Fig.10 The additional components of each box of the algorithm in the preceding flowchart. Thus, Fig.10 Each block in the aforementioned flow chart of can be performed by a component and the device may include one or more of those components. These components can be one or more hardware components specially configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0114] In one configuration, the device 1102 and in particular the baseband unit 1104 include: a device for communicating with a UE using periodic uplink traffic bursts and periodic downlink traffic bursts. The device includes a device for selecting a time offset with at least one of the uplink traffic or downlink traffic to increase the overlap between the uplink traffic burst and the downlink traffic burst. The device includes a device for sending the time offset to the AF. The device further includes a device for configuring a DRX cycle for the UE based on the periodicity of traffic arrival of the periodic uplink traffic burst and the periodic downlink traffic burst. The device further includes a device for allocating resources for no grant uplink transmission, wherein the time offset is selected to increase the alignment between the resources allocated for no grant uplink transmission and the downlink traffic arrival. The device further includes a device for configuring a DRX cycle for the UE based on the resources allocated for no grant uplink transmission and the periodicity of downlink traffic arrival. The device further includes a device for allocating resources for no grant uplink transmission. The device further includes a device for determining a time offset with downlink traffic and no grant of downlink resource allocation to increase the alignment between uplink transmission resources and downlink transmission resources. The device further includes a device for configuring a DRX cycle for UE based on the periodicity of uplink transmission resources and downlink transmission resources. The device further includes a device for allocating resources for no grant of downlink transmission. The device further includes a device for determining a time offset for uplink traffic to increase the alignment between downlink transmission resources and uplink traffic arrival. The device further includes a device for configuring a DRX cycle for UE based on uplink traffic arrival and the periodicity of downlink transmission resources. The device further includes a device for allocating resources for no grant of downlink transmission. The device further includes a device for determining a time offset with uplink traffic and no grant of uplink resource allocation to increase the alignment between uplink transmission resources and downlink transmission resources. The device further includes a device for configuring a DRX cycle for UE based on the periodicity of uplink transmission resources and downlink transmission resources. The aforementioned means may be one or more of the aforementioned components in the device 1102 configured to perform the functions recited by the aforementioned means. As described above, the device 1102 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the aforementioned means.

[0115] Figure 12-161200, 1300, 1400, 1500, 1600 are flow charts of wireless communication methods. The method may be performed by a UE or a component of a UE (e.g., UE 104, 350, 902; device 1702; cellular baseband processor 1704, which may include memory 360 and may be the entire UE 350 or a component of UE 350 (such as TX processor 368, RX processor 356 and / or controller / processor 359)). One or more of the operations illustrated may be omitted, transposed, or performed simultaneously. Optional aspects are illustrated with dashed lines. The method may allow the UE to reduce power consumption by aligning uplink transmission with downlink reception, which may allow the UE to extend its idle time and save power.

[0116] At 1202, a UE communicates with a base station. For example, 1202 may be performed by a receiving component 1730 and / or a transmitting component 1734 of the device 1702. The UE may communicate with the base station using periodic uplink traffic bursts and periodic downlink traffic bursts. The communication may include XR traffic, such as in conjunction with Figure 4-9 Any of the ones described in .

[0117] At 1204, the UE may receive a configuration for a DRX cycle based on periodic uplink and downlink traffic bursts. For example, 1204 may be performed by a DRX component 1740 of the device 1702. Uplink transmissions from the UE may be based on grants. Example aspects of configuring a DRX cycle are in conjunction with Fig. 9 For example, the DRX component 1740 of the device 1702 may receive a DRX configuration.

[0118] At 1206, the UE can delay sending a SR for uplink traffic until the start of the next DRX cycle. For example, 1206 can be performed by the SR component 1742 of the device 1702. The SR can be sent or delayed by the SR component 1742 of the device 1702.

[0119] At 1302, the UE may communicate with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts. For example, 1302 may be performed by a receiving component 1730 or a transmitting component 1734 of the device 1702. The communication may include XR traffic, for example, as combined with Figure 4-9 Any of the ones described in .

[0120] At 1304, the UE may receive a configuration for a DRX cycle based on periodic uplink and downlink traffic bursts. For example, 1304 may be performed by a DRX component 1740 of the device 1702. The uplink transmission of the UE may be based on a grant. Example aspects of configuring the DRX cycle are in conjunction with Fig. 9It is described by 910 in .

[0121] At 1306, the UE may transmit an SR in advance of the arrival of uplink traffic if the arrival of the uplink traffic burst is expected to arrive within the next DRX cycle. For example, 1306 may be performed by the SR component 1742 of the device 1702. The SR may be sent based on a prediction or estimate that uplink traffic will arrive (e.g., based on previous patterns of uplink traffic bursts).

[0122] At 1402, the UE may communicate with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts. For example, 1302 may be performed by a receiving component 1730 or a transmitting component 1734 of the device 1702. The communication may include XR traffic, for example, as combined with Figure 4-9 The periodicity of uplink traffic arrival may not be communicated to the UE.

[0123] At 1404, the UE can determine a periodicity of the uplink traffic. For example, 1304 can be performed by a determining component 1744 of the device 1702. The UE can determine the periodicity based on previous arrival patterns for uplink traffic transmitted to the base station.

[0124] At 1406, the UE may send an SR for uplink traffic at the beginning of the next DRX cycle before the uplink traffic burst arrives, if the uplink traffic burst is expected to arrive within the next DRX cycle. For example, 1406 may be performed by the SR component 1742 of the device 1702. The SR may be sent based on a prediction or estimate that uplink traffic will arrive (e.g., based on previous patterns of uplink traffic bursts).

[0125] At 1502, a UE may communicate with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts. For example, 1502 may be performed by a receiving component 1730 or a transmitting component 1734 of a device 1702. The communication may include XR traffic, for example, as combined with Figure 4-9 The periodicity of uplink traffic arrival may not be communicated to the UE.

[0126] At 1504, the UE can determine a periodicity of uplink traffic. For example, 1504 can be performed by a determining component 1744 of the device 1702. The UE can determine the periodicity based on previous arrival patterns for uplink traffic transmitted to the base station.

[0127] At 1506, the UE can delay sending a SR for uplink traffic until the start of the next DRX cycle. For example, 1506 can be performed by the SR component 1742 of the device 1702.

[0128] At 1602, the UE may communicate with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts. For example, 1602 may be performed by a receiving component 1730 or a transmitting component 1734 of the device 1702. The communication may include XR traffic, for example, as combined with Figure 4-9 The periodicity of uplink traffic arrival may not be communicated to the UE.

[0129] At 1604, the UE may select a time offset from at least one of the uplink traffic or the downlink traffic. For example, 1604 may be performed by an offset component 1746 of the device 1702. The UE may select a time offset from at least one of the uplink traffic or the downlink traffic to increase an overlap between the uplink traffic burst and the downlink traffic burst.

[0130] At 1606, the UE can send the time offset to the application client. For example, 1606 can be performed by the transmission component 1734 of the device 1702.

[0131] Fig.171700 is an example of a hardware implementation of an illustrative device 1702. The device 1702 is a UE and includes a cellular baseband processor 1704 (also referred to as a modem) coupled to a cellular RF transceiver 1722 and one or more subscriber identity modules (SIM) cards 1720, an application processor 1706 coupled to a secure digital (SD) card 1708 and a screen 1710, a Bluetooth module 1712, a wireless local area network (WLAN) module 1714, a global positioning system (GPS) module 1716, and a power supply 1718. The cellular baseband processor 1704 communicates with the UE 104 and / or BS 102 / 180 through the cellular RF transceiver 1722. The cellular baseband processor 1704 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1704 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1704, causes the cellular baseband processor 1704 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1704 when executing the software. The cellular baseband processor 1704 further includes a receiving component 1730, a communication manager 1732, and a transmission component 1734. The communication manager 1732 includes one or more of the illustrated components. The components within the communication manager 1732 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1704. The cellular baseband processor 1704 may be a component of the UE 350 and may include a memory 360 and / or at least one of the following: a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1702 may be a modem chip and include only the baseband processor 1704, and in another configuration, the device 1702 may be the entire UE (e.g., see Figure 3 350) and includes the aforementioned additional modules of device 1702.

[0132] The communication manager 1732 includes a DRX component 1740 configured to configure a DRX cycle based on periodic uplink traffic bursts and periodic downlink traffic bursts, for example, as combined with Fig.12 The DRX component 1740 is configured to receive a configuration for a DRX cycle based on periodic uplink traffic bursts and periodic downlink traffic bursts, for example, as described in conjunction with Fig.13 The communication manager 1732 further includes an SR component 1742, which is configured to delay sending an SR for uplink traffic until the beginning of the next DRX cycle, for example, as described in conjunction with Fig.121206. The SR component 1742 can transmit the SR before the arrival of the uplink traffic if the arrival of the uplink traffic burst is expected to arrive within the next DRX cycle, for example, as combined with Fig.13 1306. The SR component 1742 can send an SR for uplink traffic at the beginning of the next DRX cycle before the uplink traffic burst arrives, if the uplink traffic burst arrives within the next DRX cycle, for example, as combined with Fig.14 1406. The SR component 1742 can delay sending the SR for uplink traffic until the beginning of the next DRX cycle, for example, as described in conjunction with Fig.15 The communication manager 1732 further includes a determining component 1744 configured to determine the periodicity of the uplink traffic, for example, as described in conjunction with Fig.14 The determining component 1744 determines the periodicity of the uplink traffic, for example, as described in conjunction with Fig.15 The communication manager 1732 further includes an offset component 1746 configured to select a time offset from at least one of the uplink traffic or the downlink traffic, for example, as described in conjunction with Fig.16 The receiving component 1730 or the transmitting component 1734 may be configured to communicate with a base station, for example, as described in conjunction with Fig.12 1202 Fig.13 1302 Fig.14 1402 Fig.15 1502 or Fig.16 The transmission component 1734 can be configured to send the time offset to the application client, for example, Fig.16 Described in 1606.

[0133] The apparatus may include executing Figure 12-15 The additional components of each box of the algorithm in the preceding flowchart. Thus, Figure 12-15 Each block in the aforementioned flow chart may be performed by a component and the device may include one or more of those components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0134] In one configuration, the device 1702 and in particular the cellular baseband processor 1704 includes: means for communicating with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts. The device includes means for configuring a DRX cycle based on the periodic uplink traffic bursts and the periodic downlink traffic bursts, wherein the uplink transmission is based on a grant. The device includes means for delaying the sending of a scheduling request (SR) for uplink traffic to the start of the next DRX cycle. The device includes means for receiving a configuration of a DRX cycle based on the periodic uplink traffic bursts and the periodic downlink traffic bursts, wherein the uplink transmission is based on a grant. The device includes means for transmitting the SR before the arrival of the uplink traffic if the arrival of the uplink traffic burst is expected to arrive within the next DRX cycle. The device includes means for communicating with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts, wherein the periodicity of the uplink traffic arrival is not communicated to the UE. The device includes a device for determining the periodicity of the uplink traffic by the UE. The device includes a device for sending a scheduling request (SR) for uplink traffic at the beginning of the next DRX cycle before the uplink traffic burst arrives, if the uplink traffic burst arrives within the next DRX cycle. The device includes a device for delaying the sending of the scheduling request (SR) for uplink traffic to the beginning of the next DRX cycle. The aforementioned device may be one or more of the aforementioned components in the device 1702 configured to perform the functions described by the aforementioned device. As described above, the device 1702 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the aforementioned device may be a TX processor 368, an RX processor 356, and a controller / processor 359 configured to perform the functions described by the aforementioned device.

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

[0136] The following examples are merely illustrative and may be combined with aspects of other embodiments or teachings described herein without limitation.

[0137] Example 1 is a method for wireless communication at a base station, comprising: using periodic uplink traffic bursts and periodic downlink traffic bursts to communicate with a UE; selecting a time offset from at least one of the uplink traffic or the downlink traffic to increase the overlap between the uplink traffic burst and the downlink traffic burst; and sending the time offset to an AF.

[0138] In Example 2, the method of Example 1 further includes configuring a DRX cycle for the UE based on a periodicity of traffic arrival of the periodic uplink traffic burst and the periodic downlink traffic burst.

[0139] In Example 3, the method of Example 1 or 2 further includes: allocating resources for a grant-free uplink transmission, wherein the time offset is selected to increase alignment between the resources allocated for the grant-free uplink transmission and the arrival of downlink traffic.

[0140] In Example 4, the method of any one of Examples 1-3 further includes configuring a DRX cycle for the UE based on resources allocated for no-grant uplink transmission and a periodicity of downlink traffic arrival.

[0141] In Example 5, the method of any one of Examples 1-4 further includes that the start time of the uplink traffic and the downlink traffic is periodic, and the method further includes allocating resources for ungranted uplink transmission; and determining a time offset from the downlink traffic and the ungranted downlink resource allocation to increase the alignment between the uplink transmission resources and the downlink transmission resources.

[0142] In Example 6, the method of any one of Examples 1-5 further includes configuring a DRX cycle for the UE based on a periodicity of the uplink transmission resources and the downlink transmission resources.

[0143] In Example 7, the method of any one of Examples 1-6 further includes that the start time of the uplink traffic and the downlink traffic is periodic, and the method further includes allocating resources for ungranted downlink transmission; and determining a time offset for the uplink traffic to increase the alignment between the downlink transmission resources and the arrival of the uplink traffic.

[0144] In Example 8, the method of any one of Examples 1-7 further comprises configuring a DRX cycle for the UE based on uplink traffic arrival and periodicity of downlink transmission resources.

[0145] In Example 9, the method of any one of Examples 1-8 further includes that the start time of the uplink traffic and the downlink traffic is periodic, and the method further includes allocating resources for ungranted downlink transmission; and determining a time offset with the uplink traffic and ungranted uplink resource allocation to increase the alignment between the uplink transmission resources and the downlink transmission resources.

[0146] In Example 10, the method of any one of Examples 1-9 further includes configuring a DRX cycle for the UE based on a periodicity of the uplink transmission resources and the downlink transmission resources.

[0147] Example 11 is a device comprising one or more processors and one or more memories in electronic communication with the one or more processors, the one or more memories storing instructions executable by the one or more processors to cause a system or device to implement a method as in any of Examples 1-10.

[0148] Example 12 is a system or apparatus comprising means for implementing a method as in any of Examples 1-10 or implementing an apparatus as in any of Examples 20-33.

[0149] Example 13 is a non-transitory computer-readable medium storing instructions executable by one or more processors, the instructions causing the one or more processors to implement the method as in any of Examples 1-10.

[0150] Example 14 is a method for wireless communication at a UE, comprising: communicating with a base station using periodic uplink traffic bursts and periodic downlink traffic bursts; receiving a configuration of a discontinuous reception (DRX) cycle based on the periodic uplink traffic bursts and the periodic downlink traffic bursts, wherein uplink transmission is grant-based; and delaying sending a scheduling request (SR) for uplink traffic until the beginning of the next DRX cycle.

[0151] Example 15 is a device comprising one or more processors and one or more memories in electronic communication with the one or more processors, the one or more memories storing instructions executable by the one or more processors to cause the system or device to implement the method as in Example 14.

[0152] Example 16 is a system or device, which includes a device for implementing the method as in Example 14 or a device for implementing the device as in Example 14.

[0153] Example 17 is a non-transitory computer-readable medium storing instructions executable by one or more processors, which cause the one or more processors to implement the method as in Example 14.

[0154] Example 18 is a method for wireless communication at a UE, comprising: using periodic uplink traffic bursts and periodic downlink traffic bursts to communicate with a base station; selecting a time offset from at least one of the uplink traffic or the downlink traffic to increase the overlap between the uplink traffic burst and the downlink traffic burst; and sending the time offset to an application client.

[0155] Example 19 is a device comprising one or more processors and one or more memories in electronic communication with the one or more processors, the one or more memories storing instructions executable by the one or more processors to cause the system or device to implement the method as in Example 18.

[0156] Example 20 is a system or device comprising means for implementing the method as in Example 18 or for implementing the device as in Example 14.

[0157] Example 21 is a non-transitory computer-readable medium storing instructions executable by one or more processors, which cause the one or more processors to implement the method as in Example 18.

[0158] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those skilled in the art, and the universal principles defined in this article can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown in this article, but should be granted the full scope consistent with the claims in language, wherein the singular reference of the elements is not intended to represent "there is and only one", but "one or more", unless otherwise stated. Terms such as "if", "when..." and "when..." should be interpreted as meaning "under the condition", rather than implying a direct time relationship or reaction. That is, these phrases (e.g., "when...") do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but only imply that an action will occur when the condition is met, and no specific or immediate time constraints are required for the action to occur. The wording "exemplary" is used herein to mean "used as an example, instance or explanation". Any aspect described as "exemplary" herein need not be interpreted as being superior to or superior to other aspects. Unless otherwise stated, the term "some / certain" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are currently or later known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. The terms "module," "mechanism," "element," "device," and the like may not be a substitute for the term "means." Thus, no claim element should be construed as a means-plus-function unless the element is explicitly recited using the phrase "means for..."

Claims

1. A method for wireless communication at a node, comprising: communicating with a user equipment (UE) using periodic uplink traffic bursts and periodic downlink traffic bursts; selecting, based on a processing timeline associated with an application function (AF), at least one of a time offset to be applied by the UE for uplink traffic to the AF or a time offset to be applied by the AF for downlink traffic to the UE, wherein the time offset aligns uplink transmission of the periodic uplink traffic bursts and downlink reception of the periodic downlink traffic bursts for the UE; as well as A time offset is sent to the UE to be applied by the UE to the uplink traffic to the AF, or a time offset is sent to the AF to be applied by the AF to the downlink traffic to the UE.

2. The method of claim 1, further comprising: A discontinuous reception (DRX) cycle for the UE is configured based on the periodic uplink traffic burst and the periodic downlink traffic burst's traffic arrival periodicity.

3. The method of claim 1, further comprising: Resources are allocated for grant-free uplink transmissions of the periodic uplink traffic bursts, wherein a time offset is selected to align the resources allocated for the grant-free uplink transmissions with downlink traffic arrivals.

4. The method of claim 3, further comprising: A discontinuous reception (DRX) cycle for the UE is configured based on the resources allocated for the grant-free uplink transmission and a periodicity of downlink traffic arrival.

5. The method according to claim 1, wherein the start time of the uplink traffic and the downlink traffic is periodic, and the method further comprises: allocating resources for no-grant uplink transmission; as well as A time offset from the downlink traffic and a corresponding no-grant downlink resource allocation is determined to align uplink transmission resources with downlink transmission resources.

6. The method of claim 5, further comprising: A discontinuous reception (DRX) cycle for the UE is configured based on the periodicity of uplink transmission resources and downlink transmission resources.

7. The method of claim 1, wherein the start time of the uplink traffic and the downlink traffic is periodic, and the method further comprises: allocating resources for grant-free downlink transmission of the periodic downlink traffic burst; as well as A time offset for the uplink traffic is determined to align downlink transmission resources with uplink traffic arrival.

8. The method of claim 7, further comprising: A discontinuous reception (DRX) cycle for the UE is configured based on uplink traffic arrival and periodicity of downlink transmission resources.

9. The method of claim 1, wherein the start time of the uplink traffic and the downlink traffic is periodic, and the method further comprises: allocating resources for grant-free downlink transmission; as well as A time offset from the uplink traffic and a corresponding no-grant uplink resource allocation is determined to align uplink transmission resources with downlink transmission resources.

10. The method of claim 9, further comprising: A discontinuous reception (DRX) cycle for the UE is configured based on the periodicity of uplink transmission resources and downlink transmission resources.

11. An apparatus for wireless communication at a node, comprising: Memory; as well as at least one processor coupled to the memory and configured to: communicating with a user equipment (UE) using periodic uplink traffic bursts and periodic downlink traffic bursts; selecting, based on a processing timeline associated with an application function (AF), at least one of a time offset to be applied by the UE for uplink traffic to the AF or a time offset to be applied by the AF for downlink traffic to the UE, wherein the time offset aligns uplink transmission of the periodic uplink traffic bursts and downlink reception of the periodic downlink traffic bursts for the UE; as well as A time offset is sent to the UE to be applied by the UE to the uplink traffic to the AF, or a time offset is sent to the AF to be applied by the AF to the downlink traffic to the UE.

12. The apparatus of claim 11, wherein the at least one processor is configured to: A discontinuous reception (DRX) cycle for the UE is configured based on the periodic uplink traffic burst and the periodic downlink traffic burst's traffic arrival periodicity.

13. The apparatus of claim 11, wherein the at least one processor is configured to: Resources are allocated for grant-free uplink transmissions of the periodic uplink traffic bursts, wherein a time offset is selected to align the resources allocated for the grant-free uplink transmissions with downlink traffic arrivals.

14. The apparatus of claim 13, wherein the at least one processor is configured to: A discontinuous reception (DRX) cycle for the UE is configured based on the resources allocated for the grant-free uplink transmission and a periodicity of downlink traffic arrival.

15. The apparatus of claim 11, wherein the at least one processor is configured to: allocating resources for grant-free uplink transmission; and A time offset from the downlink traffic and a corresponding no-grant downlink resource allocation is determined to align uplink transmission resources with downlink transmission resources.

16. The apparatus of claim 15, wherein the at least one processor is configured to: A discontinuous reception (DRX) cycle for the UE is configured based on the periodicity of uplink transmission resources and downlink transmission resources.

17. The apparatus of claim 11, wherein the at least one processor is configured to: allocating resources for grant-free downlink transmission of the periodic downlink traffic burst; and A time offset for the uplink traffic is determined to align downlink transmission resources with uplink traffic arrival.

18. The apparatus of claim 17, wherein the at least one processor is configured to: A discontinuous reception (DRX) cycle for the UE is configured based on uplink traffic arrival and periodicity of downlink transmission resources.

19. The apparatus of claim 11, wherein the at least one processor is configured to: allocating resources for no-grant downlink transmission; and A time offset from the uplink traffic and a corresponding no-grant uplink resource allocation is determined to align uplink transmission resources with downlink transmission resources.

20. The apparatus of claim 19, wherein the at least one processor is configured to: A discontinuous reception (DRX) cycle for the UE is configured based on the periodicity of uplink transmission resources and downlink transmission resources.

21. A method of wireless communication at a user equipment (UE), comprising: communicating with a node using periodic uplink traffic bursts and periodic downlink traffic bursts; receiving a configuration of a discontinuous reception (DRX) cycle based on the periodic uplink traffic burst and the periodic downlink traffic burst, wherein uplink transmission is grant-based; receiving an allocation of resources for a grant-free uplink transmission associated with the periodic uplink traffic burst, wherein a time offset is provided to align the resources allocated for the grant-free uplink transmission with downlink traffic arrival, wherein the DRX cycle is based on the resources allocated for the grant-free uplink transmission and a periodicity of the downlink traffic arrival; as well as Sending a scheduling request (SR) for uplink traffic is delayed until the beginning of a next DRX cycle, wherein the periodic uplink traffic burst and the periodic downlink traffic burst are within the same DRX cycle.

22. The method of claim 21, wherein the DRX cycle of the UE is based on periodicity of traffic arrival to align the periodic uplink traffic bursts with the periodic downlink traffic bursts in the time domain.

23. The method of claim 21, further comprising: A resource allocation for a grant-free uplink transmission is received, wherein the start times of the uplink traffic and the downlink traffic are periodic, wherein a time offset between the grant-free uplink transmission and the downlink resource allocation aligns the uplink transmission resources with the downlink transmission resources.

24. The method of claim 21, further comprising: A resource allocation for a grant-free downlink transmission is received, wherein the start times of the uplink traffic and the downlink traffic are periodic, wherein the downlink transmission resources and uplink traffic arrival are aligned for a time offset of the uplink traffic.

25. The method of claim 21, further comprising: A resource allocation for a grant-free downlink transmission is received, wherein the start times of the uplink traffic and the downlink traffic are periodic, wherein a time offset for the uplink traffic and the grant-free uplink resource allocation is used to align uplink transmission resources with downlink transmission resources.

26. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as at least one processor coupled to the memory and configured to: communicating with a node using periodic uplink traffic bursts and periodic downlink traffic bursts; receiving a configuration of a discontinuous reception (DRX) cycle based on the periodic uplink traffic burst and the periodic downlink traffic burst, wherein uplink transmission is grant-based; receiving an allocation of resources for a grant-free uplink transmission associated with the periodic uplink traffic burst, wherein a time offset is provided to align the resources allocated for the grant-free uplink transmission with downlink traffic arrival, wherein the DRX cycle is based on the resources allocated for the grant-free uplink transmission and a periodicity of the downlink traffic arrival; as well as Sending a scheduling request (SR) for uplink traffic is delayed until the beginning of a next DRX cycle, wherein the periodic uplink traffic burst and the periodic downlink traffic burst are within the same DRX cycle.

27. The apparatus of claim 26, wherein the DRX cycle of the UE is based on periodicity of traffic arrival to align the periodic uplink traffic bursts with the periodic downlink traffic bursts in the time domain.

28. The apparatus of claim 26, wherein the at least one processor is further configured to: A resource allocation for a grant-free uplink transmission is received, wherein the start times of the uplink traffic and the downlink traffic are periodic, wherein a time offset between the grant-free uplink transmission and the downlink resource allocation aligns the uplink transmission resources with the downlink transmission resources.

29. The apparatus of claim 26, wherein the at least one processor is further configured to: A resource allocation for a grant-free downlink transmission is received, wherein the start times of the uplink traffic and the downlink traffic are periodic, wherein the downlink transmission resources and uplink traffic arrival are aligned for a time offset of the uplink traffic.

30. The apparatus of claim 26, wherein the at least one processor is further configured to: A resource allocation for a grant-free downlink transmission is received, wherein the start times of the uplink traffic and the downlink traffic are periodic, wherein a time offset for the uplink traffic and the grant-free uplink resource allocation is used to align uplink transmission resources with downlink transmission resources.

31. A method of wireless communication at a user equipment (UE), comprising: communicating with a node using periodic uplink traffic bursts and periodic downlink traffic bursts; receiving from the node a time offset to be applied to uplink traffic to an application function AF based on a processing timeline associated with the AF, wherein the time offset aligns uplink transmission of the periodic uplink traffic bursts with downlink reception of the periodic downlink traffic bursts; as well as The time offset is sent to the application client.

32. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as at least one processor coupled to the memory and configured to: communicating with a node using periodic uplink traffic bursts and periodic downlink traffic bursts; receiving from the node a time offset based on a processing timeline associated with an application function (AF) to be applied to uplink traffic to the AF, wherein the time offset aligns uplink transmission of the periodic uplink traffic bursts with downlink reception of the periodic downlink traffic bursts; as well as The time offset is sent to the application client.

Images