Synchronization of traffic with discontinuous reception and / or semi-persistent scheduling

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a base station (BS) may receive an indication of a traffic mode for application traffic. The BS may determine one or more parameters of at least one of a discontinuous reception (DRX) configuration for the application traffic or a semi-persistent scheduling (SPS) configuration for the application traffic based at least in part on one or more measurements associated with the traffic mode. The BS may transmit an indication of at least one of the DRX configuration or the SPS configuration to a user equipment (UE) to receive the application traffic. Numerous other aspects are provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 856,503, filed on June 3, 2019, entitled “SYNCHRONIZATION OF TRAFFIC AND DISCONTINUOUS RECEPTION AND / OR SEMIPERSISTENT SCHEDULING,” and U.S. Non-Provisional Patent Application No. 16 / 890,747, filed on June 2, 2020, entitled “SYNCHRONIZATION OF TRAFFIC AND DISCONTINUOUS RECEPTION AND / OR SEMIPERSISTENT SCHEDULING,” which are hereby expressly incorporated herein by reference.

[0003] Public domain

[0004] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for synchronization of traffic with discontinuous reception (DRX) and / or semi-persistent scheduling (SPS).

[0005] background

[0006] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0007] A wireless communication network may include several base stations (BS) that can support communication of several user equipments (UEs). User equipments (UEs) may communicate with base stations (BSs) via downlinks and uplinks. Downlinks (or forward links) refer to the communication link from a BS to a UE, while uplinks (or reverse links) refer to the communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, a gNB, an Access Point (AP), a Radio Head, a Transmit Receive Point (TRP), a New Radio (NR) BS, a 5G Node B, and the like.

[0008] The above multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different user equipment to communicate at city, country, region, and even global levels. New Radio (NR) (which may also be referred to as 5G) is an enhancement set to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also referred to as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to better integrate with other open standards. However, as the demand for mobile broadband access continues to grow, there is a need for further improvements in LTE and NR technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that employ these technologies.

[0009] Overview

[0010] In some aspects, a wireless communication method performed by a user equipment (UE) may include: transmitting a request for at least one of a discontinuous reception (DRX) configuration for application traffic or a semi-persistent scheduling (SPS) configuration for application traffic to a base station (BS), wherein the request includes an indication of a traffic pattern associated with the application traffic; and receiving an indication of at least one of the DRX configuration or the SPS configuration from the BS and based at least in part on transmitting the request.

[0011] In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: transmit a request to a BS for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic, wherein the request includes an indication of a traffic mode associated with the application traffic; and receive an indication of at least one of the DRX configuration or the SPS configuration from the BS and based at least in part on transmitting the request.

[0012] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of an application server, may cause the one or more processors to: transmit a request to a BS for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic, wherein the request includes an indication of a traffic mode associated with the application traffic; and receive an indication of at least one of the DRX configuration or the SPS configuration from the BS and based at least in part on transmitting the request.

[0013] In some aspects, an apparatus for wireless communications may include: a device for transmitting a request for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic to a BS, wherein the request includes an indication of a traffic pattern associated with the application traffic; and a device for receiving an indication of at least one of the DRX configuration or the SPS configuration from the BS and based at least in part on transmitting the request.

[0014] In some aspects, a wireless communication method performed by an application server may include: transmitting a request for at least one of a DRX configuration for a UE or an SPS configuration for the UE to a BS; receiving an indication of at least one of the DRX configuration or the SPS configuration from the BS and based at least in part on transmitting the request; and adjusting a traffic mode for application traffic to be transmitted to the UE based at least in part on at least one of the DRX configuration or the SPS configuration.

[0015] In some aspects, an application server for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: transmit a request for at least one of a DRX configuration for a UE or an SPS configuration for the UE to a BS; receive an indication of at least one of the DRX configuration or the SPS configuration from the BS and based at least in part on transmitting the request; and adjust a traffic mode for application traffic to be transmitted to the UE based at least in part on at least one of the DRX configuration or the SPS configuration.

[0016] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of an application server, may cause the one or more processors to: transmit a request for at least one of a DRX configuration for a UE or an SPS configuration for the UE to a BS; receive an indication of at least one of the DRX configuration or the SPS configuration from the BS and based at least in part on transmitting the request; and adjust a traffic mode for application traffic to be transmitted to the UE based at least in part on at least one of the DRX configuration or the SPS configuration.

[0017] In some aspects, an apparatus for wireless communication may include: a device for transmitting a request for at least one of a DRX configuration for a UE or an SPS configuration for the UE to a BS; a device for receiving an indication of at least one of the DRX configuration or the SPS configuration from the BS and based at least in part on transmitting the request; and a device for adjusting a traffic mode for application traffic to be transmitted to the UE based at least in part on at least one of the DRX configuration or the SPS configuration.

[0018] In some aspects, a wireless communication method performed by a network controller may include: receiving a first request for at least one of a DRX configuration for a UE or an SPS configuration for the UE from an application server; transmitting the first request and a second request for a traffic offset between the application server and the BS to a BS; receiving an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration from the BS and at least partially based on transmitting the first request and the second request; and transmitting an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration to the application server.

[0019] In some aspects, a network controller for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive a first request for at least one of a DRX configuration for a UE or an SPS configuration for the UE from an application server; transmit the first request and a second request for a traffic offset between the application server and the BS to a BS; receive an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration from the BS and based at least in part on transmitting the first request and the second request; and transmit an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration to the application server.

[0020] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a network device, may cause the one or more processors to: receive a first request for at least one of a DRX configuration for a UE or an SPS configuration for the UE from an application server; transmit the first request and a second request for a traffic offset between the application server and the BS to a BS; receive an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration from the BS and based at least in part on transmitting the first request and the second request; and transmit an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration to the application server.

[0021] In some aspects, an apparatus for wireless communication may include: a device for receiving a first request for at least one of a DRX configuration for a UE or an SPS configuration for the UE from an application server; a device for transmitting the first request and a second request for a traffic offset between the application server and the BS to a BS; a device for receiving an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration from the BS and at least partially based on transmitting the first request and the second request; and a device for transmitting an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration to the application server.

[0022] In some aspects, a wireless communication method performed by an application server may include: receiving an indication of at least one of a DRX configuration associated with the UE or an SPS configuration associated with the UE from a UE or a network controller; and adjusting a traffic pattern associated with application traffic to be transmitted to the UE based at least in part on at least one of the DRX configuration or the SPS configuration.

[0023] In some aspects, an application server for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive an indication of at least one of a DRX configuration associated with the UE or an SPS configuration associated with the UE from a UE or a network controller; and adjust a traffic pattern associated with application traffic to be transmitted to the UE based at least in part on at least one of the DRX configuration or the SPS configuration.

[0024] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of an application server, may cause the one or more processors to receive an indication of at least one of a DRX configuration associated with the UE or an SPS configuration associated with the UE from a UE or a network controller; and adjust a traffic pattern associated with application traffic to be transmitted to the UE based at least in part on at least one of the DRX configuration or the SPS configuration.

[0025] In some aspects, an apparatus for wireless communications may include: a device for receiving an indication of at least one of a DRX configuration associated with the UE or an SPS configuration associated with the UE from a UE or a network controller; and a device for adjusting a traffic mode associated with application traffic to be transmitted to the UE based at least in part on at least one of the DRX configuration or the SPS configuration.

[0026] In some aspects, a wireless communication method performed by a base station (BS) may include: receiving an indication of a traffic mode for application traffic; determining one or more parameters of at least one of a DRX configuration for the application traffic or an SPS configuration for the application traffic based at least in part on one or more measurements associated with the traffic mode; and transmitting an indication of at least one of the DRX configuration or the SPS configuration to a UE that is to receive the application traffic.

[0027] In some aspects, a BS for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive an indication of a traffic pattern for application traffic; determine one or more parameters of at least one of a DRX configuration for the application traffic or an SPS configuration for the application traffic based at least in part on one or more measurements associated with the traffic pattern; and transmit an indication of at least one of the DRX configuration or the SPS configuration to a UE to receive the application traffic.

[0028] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a BS, may cause the one or more processors to receive an indication of a traffic pattern for application traffic; determine one or more parameters of at least one of a DRX configuration for the application traffic or an SPS configuration for the application traffic based at least in part on one or more measurements associated with the traffic pattern; and transmit an indication of at least one of the DRX configuration or the SPS configuration to a UE to receive the application traffic.

[0029] In some aspects, an apparatus for wireless communications may include: a device for receiving an indication of a traffic mode for application traffic; a device for determining one or more parameters of at least one of a DRX configuration for the application traffic or an SPS configuration for the application traffic based at least in part on one or more measurements associated with the traffic mode; and a device for transmitting an indication of at least one of the DRX configuration or the SPS configuration to a UE that is to receive the application traffic.

[0030] In some aspects, a wireless communication method performed by a BS may include: receiving a request for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic from a UE, wherein the request indicates a traffic pattern for the application traffic; determining one or more parameters for at least one of the DRX configuration or the SPS configuration based at least in part on one or more measurements associated with the traffic pattern; and transmitting an indication of at least one of the DRX configuration or the SPS configuration to the UE.

[0031] In some aspects, a BS for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive a request for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic from a UE, wherein the request indicates a traffic pattern for the application traffic; determine one or more parameters for at least one of the DRX configuration or the SPS configuration based at least in part on one or more measurements associated with the traffic pattern; and transmit an indication of at least one of the DRX configuration or the SPS configuration to the UE.

[0032] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a BS, may cause the one or more processors to: receive a request for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic from a UE, wherein the request indicates a traffic pattern for the application traffic; determine one or more parameters for at least one of the DRX configuration or the SPS configuration based at least in part on one or more measurements associated with the traffic pattern; and transmit an indication of at least one of the DRX configuration or the SPS configuration to the UE.

[0033] In some aspects, an apparatus for wireless communication may include: a device for receiving a request for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic from a UE, wherein the request indicates a traffic pattern for the application traffic; a device for determining one or more parameters for at least one of the DRX configuration or the SPS configuration based at least in part on one or more measurements associated with the traffic pattern; and a device for transmitting an indication of at least one of the DRX configuration or the SPS configuration to the UE.

[0034] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as substantially described herein with reference to and as illustrated in the accompanying drawings and description.

[0035] The foregoing has broadly outlined the features and technical advantages of examples according to the present disclosure in an effort to make the following detailed description better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures for implementing the same purpose as the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description and is not intended to define limitations on the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to understand the above-stated features of the present disclosure in detail, the above briefly summarized content may be described in more detail with reference to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and should not be considered to limit its scope, as the description may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0038] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.

[0039] Figure 2 is a block diagram conceptually illustrating an example of a base station in communication with a user equipment (UE) in a wireless communication network according to various aspects of the present disclosure.

[0040] Figure 3A is a block diagram conceptually illustrating an example of a frame structure in a wireless communication network in accordance with various aspects of the present disclosure.

[0041] Figure 3Bis a block diagram conceptually illustrating an example synchronous communication hierarchy in a wireless communication network in accordance with various aspects of the present disclosure.

[0042] Figure 4 is a block diagram conceptually illustrating an example slot format with a normal cyclic prefix in accordance with various aspects of the present disclosure.

[0043] Figure 5-8C is a diagram illustrating synchronization of traffic with discontinuous reception (DRX) and / or semi-persistent scheduling (SPS) in accordance with various aspects of the present disclosure.

[0044] Fig. 9 is a diagram illustrating example processes performed, for example, by a base station (BS) according to various aspects of the present disclosure.

[0045] Fig.10 is a diagram illustrating example processes performed, for example, by a UE according to various aspects of the present disclosure.

[0046] Fig.11 is a diagram illustrating example processes performed, for example, by a BS according to various aspects of the present disclosure.

[0047] Fig.12 is a diagram illustrating an example process performed, for example, by an application server, according to various aspects of the present disclosure.

[0048] Fig.13 is a diagram illustrating an example process performed, for example, by a network controller, according to various aspects of the present disclosure.

[0049] Fig.14 is a diagram illustrating an example process performed, for example, by an application server, according to various aspects of the present disclosure.

[0050] Figure 15-17 is a block diagram of an example device for wireless communications in accordance with various aspects of the present disclosure.

[0051] Detailed Description

[0052] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be implemented in many different forms and should not be interpreted as being limited to any specific structure or function given throughout the present disclosure. On the contrary, these aspects are provided to make the present disclosure thorough and complete, and it will fully convey the scope of the present disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using supplements or other other structures, functionality, or structures and functionality as the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein can be implemented by one or more elements of the claims.

[0053] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a 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.

[0054] It should be noted that although various aspects may be described herein using terminology typically associated with 3G and / or 4G wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations, such as 5G and later generations, including NR technologies.

[0055] Figure 1 1 is a diagram illustrating a wireless network 100 in which various aspects of the present disclosure may be practiced. The wireless network 100 may be an LTE network or some other wireless network, such as a 5G or NR network. The wireless network 100 may include several BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and may also be referred to as a base station, NR BS, B node, gNB, 5G B node (NB), access point, transmit receive point (TRP), etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to the coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0056] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in , BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. The BS may support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” may be used interchangeably herein. ”

[0057] In some aspects, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces, such as direct physical connections, virtual networks, and / or the like using any suitable transport network.

[0058] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and send transmissions of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown in , a relay station 110d may communicate with a macro BS 110a and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or the like.

[0059] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0060] The network controller 130 may be coupled to a set of BSs and may provide coordination and control of these BSs. The network controller 130 may communicate with each BS via a backhaul. These BSs may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul. In some aspects, the wireless network 100 may include one or more network controllers 130. For example, the wireless network 100 may include a network controller 130 that implements a network open function (NEF) device, a network controller 130 that implements an access and mobility management function (AMF) device, a network controller 130 that implements a session management function (SMF) device, a network controller 130 that implements a user plane function (UPF) device, a network controller 130 that implements a policy control function (PCF) device, etc. In some aspects, the NEF device, the PCF device, the AMF device, the SMF device and / or the UPF device may be included in the core network (e.g., 5G / NR core network) of the wireless network 100.

[0061] The application server 140 may host one or more applications, may receive, store and / or transmit application data associated with the one or more applications, may be coupled to one or more network controllers and / or one or more BSs (e.g., via one or more network controllers) to receive application data from one or more UEs, transmit application data to one or more UEs, etc. The UE may access the application hosted by the application server 140 via an application client installed on the UE, via a web browser installed on the UE, etc. In some aspects, the application server 140 may include one or more server devices, one or more mobile edge computing (MEC) devices, one or more cloud computing environments, etc.

[0062] UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. UEs may also be referred to as access terminals, terminals, mobile stations, subscriber units, stations, etc. A UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0063] Some UEs may be considered as machine type communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as client equipment (CPE). UE120 may be included inside a housing that houses components of UE 120, such as a processor component, a memory component, and the like.

[0064] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific RAT and may operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0065] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0066] As indicated above, Figure 1 are provided as examples. Other examples may differ from those described in Figure 1 Examples described.

[0067] Figure 2 A block diagram of a design 200 of a base station 110 and a UE 120 is shown, which may be Figure 1 One for each base station and one for each UE in the base station 110. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0068] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, position coding may be used to generate synchronization signals to convey additional information.

[0069] At UE 120, antennas 252a to 252r may receive downlink signals from base station 110 and / or other base stations and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0070] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 as well as other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236, if applicable, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and may communicate with network controller 130 via communication unit 244.

[0071] The network controller 130 may include a communication unit 294, a controller / processor 297, and a memory 292. The network controller 130 may communicate with the base station 110 and / or the application server 140 via the communication unit 294. The application server 140 may include a communication unit 298, a controller / processor 297, and a memory 296. The application server 140 may communicate with the network controller 130 via the communication unit 298.

[0072] Controller / processor 240 of base station 110, controller / processor 280 of UE 120, controller / processor 290 of network controller 130, controller / processor 297 of application server 140, and / or Figure 2 Any other component(s) of the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, the controller / processor 290 of the network controller 130, the controller / processor 297 of the application server 140, and / or Figure 2 Any other component(s) may perform or direct e.g. Fig. 9 The process of 900 Fig.10 The process of 1000 Fig.11 Process 1100, Fig.12 The process 1200 Fig.13 The process of 1300 Fig.14 The operations of process 1400, and / or other processes as described herein. Memories 242, 282, and 292 may store data and program codes for base station 110, UE 120, and network controller 130, respectively. Scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0073] In some aspects, UE 120 may include: means for transmitting to base station 110 a request for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic, wherein the request includes an indication of a traffic pattern associated with the application traffic; and means for receiving from base station 110 an indication of at least one of the DRX configuration or the SPS configuration based at least in part on transmitting the request, etc. In some aspects, such means may include in conjunction with Figure 2 One or more components of UE 120 are described.

[0074] In some aspects, the base station 110 may include: means for receiving an indication of a traffic pattern for application traffic; means for determining one or more parameters for at least one of a DRX configuration for the application traffic or an SPS configuration for the application traffic based at least in part on one or more measurements associated with the traffic pattern; and means for transmitting an indication of at least one of the DRX configuration or the SPS configuration to a UE 120 that is to receive the application traffic, etc. In some aspects, the base station 110 may include: means for receiving a request for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic from a UE 120, wherein the request indicates a traffic pattern for the application traffic; means for determining one or more parameters for at least one of the DRX configuration or the SPS configuration based at least in part on one or more measurements associated with the traffic pattern; and means for transmitting an indication of at least one of the DRX configuration or the SPS configuration to a UE 120, etc. In some aspects, such means may include a method for transmitting an indication of at least one of the DRX configuration or the SPS configuration to a UE 120, etc. Figure 2 One or more components of base station 110 are described.

[0075] In some aspects, network controller 130 may include: means for receiving a first request from an application server for at least one of a DRX configuration for UE 120 or an SPS configuration for UE 120; means for transmitting to base station 110 the first request and a second request for a traffic offset between the application server and BS 110; means for receiving from BS 110 and based at least in part on transmitting the first request and the second request, an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration; and means for transmitting to the application server an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration, etc. In some aspects, such means may include a means for combining Figure 2 One or more components of network controller 130 are described.

[0076] In some aspects, the application server 140 may include: means for transmitting a request for at least one of a DRX configuration for UE 120 or an SPS configuration for UE 120 to the base station 110; means for receiving an indication of at least one of the DRX configuration or the SPS configuration from the base station 110 and based at least in part on transmitting the request; and means for adjusting a traffic pattern for application traffic to be transmitted to the UE 120 based at least in part on at least one of the DRX configuration or the SPS configuration, etc. In some aspects, the application server 140 may include: means for receiving an indication of at least one of the DRX configuration for UE 120 or the SPS configuration for UE 120 from the UE 120 or the network controller 130; means for adjusting a traffic pattern associated with application traffic to be transmitted to the UE 120 based at least in part on at least one of the DRX configuration or the SPS configuration, etc. In some aspects, such means may include means for combining Figure 2 One or more components of application server 140 are described.

[0077] As indicated above, Figure 2 are provided as examples. Other examples may differ from those described in Figure 2 Examples described.

[0078] Figure 3A An example frame structure 300 for frequency division duplex (FDD) in a telecommunication system (e.g., NR) is shown. The transmission timeline for each of the downlink and uplink may be divided into units of radio frames (sometimes referred to as frames). Each radio frame may have a predetermined duration (e.g., 10 milliseconds (ms)) and may be divided into a set of Z (Z ≥ 1) subframes (e.g., with indices 0 to Z-1). Each subframe may have a predetermined duration (e.g., 1 ms) and may include a set of time slots (e.g., in Figure 3A Each subframe 2 is shown m time slots, where m is a parameter design for transmission, such as 0, 1, 2, 3, 4, etc.). Each time slot may include a set of L symbol periods. For example, each time slot may include fourteen symbol periods (e.g., Figure 3A ), seven symbol periods, or another number of symbol periods. In the case where a subframe includes two slots (e.g., when m=1), the subframe may include 2L symbol periods, where the 2L symbol periods in each subframe may be assigned indices 0 to 2L–1. In some aspects, the scheduling unit for FDD may be frame-based, subframe-based, slot-based, symbol-based, etc.

[0079] Although some techniques are described herein in conjunction with frames, subframes, time slots, etc., these techniques may be equally applicable to other types of wireless communication structures that may be referred to in 5G NR using terms other than "frames," "subframes," "time slots," etc. In some aspects, a wireless communication structure may refer to a periodic, time-bounded communication unit defined by a wireless communication standard and / or protocol. Additionally or alternatively, a wireless communication structure may be used in conjunction with Figure 3A The wireless communication structure configurations are different from those shown in FIG.

[0080] In certain telecommunications (e.g., NR), a base station may transmit synchronization signals. For example, a base station may transmit a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and the like on the downlink for each cell supported by the base station. The PSS and SSS may be used by the UE for cell search and acquisition. For example, the PSS may be used by the UE to determine symbol timing, and the SSS may be used by the UE to determine a physical cell identifier associated with the base station and frame timing. The base station may also transmit a physical broadcast channel (PBCH). The PBCH may carry some system information, such as system information that supports initial access of the UE.

[0081] In some aspects, a base station may transmit a PSS, SSS, and / or PBCH according to a synchronization communication level (e.g., a synchronization signal (SS) level) including multiple synchronization communications (e.g., SS blocks), as described below in conjunction with Figure 3B as described.

[0082] Figure 3B is a block diagram conceptually illustrating an example SS hierarchy, which is an example of a synchronous communication hierarchy. Figure 3B As shown in FIG. 1 , the SS hierarchy may include an SS burst set, which may include a plurality of SS bursts (identified as SS burst 0 to SS burst B-1, where B is the maximum number of repetitions of the SS burst that may be transmitted by the base station). As further shown, each SS burst may include one or more SS blocks (identified as SS block 0 to SS block (b max_SS -1), where b max_SS -1 is the maximum number of SS blocks that can be carried by an SS burst). In some aspects, different SS blocks may be beamformed differently. SS burst sets may be transmitted by a wireless node periodically, such as every X milliseconds, e.g. Figure 3B In some aspects, SS burst sets may have fixed or dynamic lengths, such as in Figure 3B is shown as Y milliseconds.

[0083] Figure 3B The SS burst set shown in is an example of a synchronous communication set, and other synchronous communication sets may be used in conjunction with the techniques described herein. Figure 3BThe SS blocks shown in are examples of synchronous communications, and other synchronous communications may be used in conjunction with the techniques described herein.

[0084] In some aspects, an SS block includes resources that carry PSS, SSS, PBCH, and / or other synchronization signals (e.g., a third synchronization signal (TSS)) and / or synchronization channels. In some aspects, multiple SS blocks are included in an SS burst, and the PSS, SSS, and / or PBCH may be identical for each SS block across an SS burst. In some aspects, a single SS block may be included in an SS burst. In some aspects, an SS block may be at least four symbol periods in length, with each symbol carrying one or more of a PSS (e.g., occupying one symbol), an SSS (e.g., occupying one symbol), and / or a PBCH (e.g., occupying two symbols).

[0085] In some aspects, the symbols of the SS block are consecutive, such as Figure 3B In some aspects, the symbols of the SS block are non-contiguous. Similarly, in some aspects, one or more SS blocks of an SS burst may be transmitted in contiguous radio resources (e.g., contiguous symbol periods) during one or more time slots. Additionally or alternatively, one or more SS blocks of an SS burst may be transmitted in non-contiguous radio resources.

[0086] In some aspects, an SS burst may have a burst periodicity, whereby each SS block of the SS burst is transmitted by the base station according to the burst periodicity. In other words, the SS blocks may be repeated during each SS burst. In some aspects, an SS burst set may have a burst set periodicity, whereby each SS burst of the SS burst set is transmitted by the base station according to a fixed burst set periodicity. In other words, the SS burst may be repeated during each SS burst set.

[0087] The base station may transmit system information, such as system information blocks (SIBs), on a physical downlink shared channel (PDSCH) in certain time slots. The base station may transmit control information / data on a physical downlink control channel (PDCCH) in C symbol periods of a time slot, where B may be configurable for each time slot. The base station may transmit traffic data and / or other data on the PDSCH in the remaining symbol periods of each time slot.

[0088] As indicated above, Figure 3A and 3B are provided as examples. Other examples may vary from Figure 3A and 3B Examples described.

[0089] Figure 4An example slot format 410 with a normal cyclic prefix is ​​shown. Available time-frequency resources may be divided into resource blocks. Each resource block may cover a set of subcarriers (e.g., 12 subcarriers) in one slot and may include several resource elements. Each resource element may cover one subcarrier in one symbol period (e.g., in time) and may be used to send one modulation symbol, which may be a real value or a complex value.

[0090] For FDD in certain telecommunication systems (e.g., NR), an interleaving structure may be used for each of the downlink and uplink. For example, Q interleavings with indices 0 to Q–1 may be defined, where Q may be equal to 4, 6, 8, 10, or some other value. Each interleaving may include time slots spaced apart by Q frames. Specifically, interleaving q may include time slots q, q+Q, q+2Q, etc., where q∈{0,…,Q–1}.

[0091] The UE may be located within the coverage of multiple BSs. One of these BSs may be selected to serve the UE. The serving BS may be selected based at least in part on various criteria such as received signal strength, received signal quality, path loss, etc. The received signal quality may be quantified by a signal-to-noise-interference ratio (SNIR), or a reference signal received quality (RSRQ), or some other metric. The UE may operate in a strong interference scenario, in which the UE may observe high interference from one or more interfering BSs.

[0092] Although aspects of the examples described herein may be associated with NR or 5G technology, aspects of the present disclosure may be applicable to other wireless communication systems. A new radio (NR) may refer to a radio configured to operate according to a new air interface (e.g., an air interface different from an orthogonal frequency division multiple access (OFDMA)-based air interface) or a fixed transport layer (e.g., different from an Internet Protocol (IP)). In various aspects, NR may utilize OFDM with CP (referred to herein as cyclic prefix OFDM or CP-OFDM) and / or SC-FDM on the uplink, may utilize CP-OFDM on the downlink and include support for half-duplex operation using time division duplex (TDD). In various aspects, NR may, for example, utilize OFDM with CP (referred to herein as CP-OFDM) and / or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) on the uplink, may utilize CP-OFDM on the downlink and include support for half-duplex operation using TDD. NR may include enhanced mobile broadband (eMBB) services targeting wide bandwidth (e.g., 80 megahertz (MHz) and above), millimeter wave (mmW) targeting high carrier frequencies (e.g., 60 gigahertz (GHz)), massive MTC (mMTC) targeting non-backward compatible MTC technologies, and / or mission critical services targeting ultra-reliable low latency communications (URLLC) services.

[0093] In some aspects, a single component carrier bandwidth of 100 MHz may be supported. NR resource blocks may span 12 subcarriers with a subcarrier bandwidth of 60 or 120 kilohertz (kHz) over a duration of 0.1 milliseconds (ms). Each radio frame may include 40 slots and may have a length of 10 ms. Thus, each slot may have a length of 0.25 ms. Each slot may indicate a link direction (e.g., DL or UL) for data transmission and the link direction for each slot may be switched dynamically. Each slot may include DL / UL data and DL / UL control data.

[0094] Beamforming may be supported and the beam direction may be dynamically configured. MIMO transmission with precoding may also be supported. MIMO configuration in DL may support up to 8 transmit antennas (multi-layer DL transmission with up to 8 streams) and up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported using up to 8 serving cells. Alternatively, NR may support different air interfaces other than OFDM-based interfaces. NR networks may include entities such as central units or distributed units.

[0095] As indicated above, Figure 4 are provided as examples. Other examples may differ from those described in Figure 4 Examples described.

[0096] The UE and the application server may communicate via a wireless network. For example, the application server may transmit application traffic to the UE and / or the UE may transmit application traffic to the application server. Some application traffic may be periodic because the application traffic is transmitted according to a specific traffic cycle. If the application server is unaware of the UE's DRX cycle (e.g., a cycle in which the UE sleeps for a sleep period and wakes up at the expiration of the period to monitor downlink traffic) and / or the SPS cycle (e.g., a cycle in which the UE is permitted to transmit uplink traffic without having to wait for a dynamic scheduling grant), a misalignment may occur between the traffic cycle of the application traffic and the DRX cycle and / or the SPS cycle of the UE.

[0097] In addition, the communication path between the UE and the application server may include one or more devices and / or components included in a computer network (such as the Internet), one or more devices (such as one or more base stations) included in a wireless network, one or more core network devices and / or components (e.g., UPF devices, etc.), etc. As a result, transmission delays may be accumulated along the communication path between the UE and the application server, which may lead to further misalignment between the traffic cycle of the application traffic and the DRX cycle and / or SPS cycle of the UE.

[0098] The misalignment between the traffic cycle of the application traffic and the DRX cycle of the UE may cause the UE to wake up from a sleep period to monitor downlink traffic when the application server is not transmitting application traffic to the UE (which results in wasteful consumption of the UE's processing and / or memory resources), may cause the UE to be in a sleep period when the application server is transmitting application traffic to the UE (which results in lost or discarded application traffic, increased retransmission of application traffic, etc.), etc. The misalignment between the traffic cycle of the application traffic and the SPS cycle of the UE may cause delays in the transmission of the application traffic from the UE to the application server, etc.

[0099] Some aspects described herein provide techniques and devices for synchronizing traffic with DRX and / or SPS. In some aspects, a BS may synchronize and / or align a traffic cycle for application traffic associated with an application server with a DRX cycle and / or SPS cycle associated with a UE. For example, a BS may receive an indication of a traffic pattern associated with application traffic, which may include an indication of a traffic cycle, and may generate or adjust a DRX configuration and / or SPS configuration so that the DRX cycle and / or SPS cycle are synchronized with the traffic cycle of the application traffic. In some aspects, an application server may synchronize and / or align a traffic cycle for application traffic associated with an application server with a DRX cycle and / or SPS cycle associated with a UE. For example, an application server may receive an indication of a DRX configuration and / or SPS configuration associated with a UE, and may adjust a traffic pattern associated with application traffic so that the traffic cycle of the application traffic is synchronized with the DRX cycle and / or SPS cycle associated with the UE.

[0100] In this way, the traffic pattern and the DRX cycle and / or the SPS cycle may be synchronized and / or aligned so that the UE wakes up from a sleep period to monitor downlink traffic when an application server is transmitting application traffic to the UE, so that the UE is in a sleep period when the application server is not transmitting application traffic to the UE, so that the UE is permitted to transmit application traffic to the application server without delay, etc. This reduces lost or discarded application traffic caused by misalignment between the traffic cycle of the application traffic and the DRX cycle of the UE and / or the SPS cycle of the UE, reduces retransmission of application traffic, reduces delays in transmitting application traffic from the UE to the application server, and reduces consumption of processing and / or memory resources of the UE.

[0101] Figure 5 is a diagram illustrating an example 500 of synchronization of traffic with DRX and / or SPS according to various aspects of the present disclosure. Figure 5 As shown in , example 500 may include one or more devices, such as a UE (e.g., UE 120), a BS (e.g., BS 110), an AMF device (e.g., network controller 130), an SMF device (e.g., network controller 130), a PCF device (e.g., network controller 130), a UPF device (e.g., network controller 130), a NEF device (e.g., network controller 130), an application server (e.g., application server 140), etc. In some aspects, example 500 may include Figure 5 Different numbers and / or configurations of devices are described in detail.

[0102] AMF devices, SMF devices, PCF devices, UPF devices, and NEF devices may be included in a core network of a wireless network (e.g., wireless network 100), such as a 5G / NR core network (e.g., next generation (NG) core). AMF devices may manage authentication, activation, deactivation, and / or mobility functions associated with a UE. AMF may facilitate the selection of a gateway (e.g., a serving gateway, a packet data network gateway, a UPF device, etc.) to serve traffic to and / or from the UE. SMF devices may be responsible for managing communication sessions associated with the UE. PCF devices may be responsible for generating, managing, and / or providing policy rules to other devices included in the core network, and may be responsible for establishing and / or managing quality of service (QoS) flows for traffic transmitted through the wireless network, and the like. NEF devices may support the opening of capabilities and / or events for other devices in and / or outside the wireless network in order to facilitate the discovery of network services for these other devices. UPF devices may act as a session anchor and / or gateway for a UE, and may forward traffic (e.g., user plane traffic, application traffic, etc.) between a UE and an application server, and the like. In this way, the UE can transmit application traffic to the application server via the UPF device, and / or the application server can transmit application traffic to the UE via the UPF device.

[0103] The application server may host one or more applications, store information associated with the one or more applications, transmit and / or receive application traffic associated with the one or more applications, etc. The application traffic may include various types of periodic traffic, such as voice traffic, video traffic, virtual reality traffic, augmented reality traffic, heartbeat signals, game traffic, etc. In some aspects, the application traffic may include non-time sensitive communications (non-TSC) that are not carried on a delay critical guaranteed bit rate (GBR) type QoS flow.

[0104] The application server may be communicatively connected to the UE via a UPF device, a BS, and / or another device. In addition, the application server may be communicatively connected to the UPF device via one or more networks outside the wireless network (such as the Internet and / or other types of public and / or private computers and / or telecommunications networks). In this case, various types of transmission delays may be accumulated along the communication path between the application server and the UE, such as Internet delays (e.g., delays caused by application traffic being transmitted from the application server to the UPF device on other public or private networks outside the Internet and / or wireless network), backhaul delays (e.g., delays caused by application traffic being transmitted between various components included in the wireless network), and the like. Therefore, the application server, the device included in the core network, the BS, and / or the UE may coordinate to synchronize and / or align the traffic cycle for the application traffic associated with the application server and the DRX cycle and / or SPS cycle associated with the UE so as to reduce, mitigate, and / or eliminate the impact of the transmission delay accumulated along the communication path between the application server and the UE.

[0105] like Figure 5 In the embodiment and indicated by reference numeral 502, the application server may transmit to the NEF device an indication of a traffic mode for application traffic associated with the application server. In some aspects, the application server may transmit the indication of the traffic mode based at least in part on determining that the application server is to transmit application traffic to the UE. In some aspects, the NEF device may forward the indication of the traffic mode to other devices included in the core network, such as PCF devices, etc.

[0106] In some aspects, the traffic pattern may specify a traffic cycle associated with the application traffic (e.g., the length of the time period between traffic bursts of the application traffic), a traffic burst size associated with the application traffic (e.g., the size of a burst of application traffic transmitted from an application server), a start time or phase of the application traffic, etc.

[0107] like Figure 5 , and as further indicated by reference numeral 504, the PCF device may receive an indication of a traffic pattern associated with application traffic and may initiate and / or establish a QoS flow for the application traffic. As indicated above, the QoS flow for the application traffic may be a non-delay critical and / or non-GBR type QoS flow.

[0108] In some aspects, a QoS flow may include one or more QoS parameters, such as a priority level, an allowed packet delay budget, an allowed packet error rate, etc. The one or more QoS parameters may be based at least in part on a traffic type associated with an application. For example, the one or more QoS parameters may be associated with a particular value if the application traffic is voice traffic, may be associated with other particular values ​​if the application traffic is video traffic, and so on.

[0109] As in Figure 5 , and further indicated by reference numeral 506, the PCF device may transmit an indication of the QoS flow to the BS. In some aspects, the PCF device may transmit the indication of the QoS flow to the BS via an AMF device, via an SMF device, etc. In some aspects, the PCF device may transmit the indication of the QoS flow based at least in part on initiating the QoS flow.

[0110] In some aspects, the indication of the QoS flow may include a QoS profile associated with the QoS flow. The QoS profile may include an indication of the QoS flow (e.g., a QoS flow identifier (QFI) associated with the QoS flow), may include an indication of one or more QoS parameters configured for the QoS flow, may include an indication of a QoS flow type associated with the QoS flow (e.g., a 5G QoS identifier (5QI) value associated with the QoS flow type), and the like. In addition, the PCF device may further include in the QoS profile an indication of a traffic pattern associated with the application traffic.

[0111] like Figure 5 , and further indicated by reference numeral 508, the BS may receive an indication of a QoS flow and may determine one or more parameters of a DRX configuration and / or SPS configuration associated with the UE for the application. In this manner, the BS may use the indication of the traffic pattern in the indication of the QoS flow to generate a DRX configuration and / or SPS configuration so that the DRX cycle and / or SPS cycle of the UE is synchronized and / or aligned with the traffic pattern (e.g., synchronized and / or aligned with the traffic cycle, traffic burst size, start time and / or phase, etc. of the application traffic).

[0112] In some aspects, the BS may determine one or more parameters for DRX configuration and / or SPS configuration by performing one or more measurements associated with a traffic pattern of application traffic. For example, the BS may perform one or more downlink traffic measurements associated with the traffic pattern to determine a first offset (e.g., a DRX offset) between a traffic cycle associated with the application traffic and a DRX cycle for the UE. As another example, the BS may perform one or more uplink traffic measurements associated with the traffic pattern to determine a second offset (e.g., an SPS offset) between a traffic cycle associated with the application traffic and an SPS cycle for the UE. The first offset and the second offset may account for various types of transmission delays along the communication path between the UE and the application server so as to synchronize and / or align the DRX cycle and / or SPS cycle of the UE with the traffic cycle of the application traffic. In some aspects, one or more measurements may include round trip time (RTT) measurements, latency measurements, and the like.

[0113] In some aspects, one or more parameters for DRX configuration may include a first offset, a traffic burst size for application traffic, a start time or phase of application traffic, a DRX cycle duration (e.g., which may correspond to the duration of a traffic cycle for application traffic), etc. In some aspects, one or more parameters for SPS configuration may include a second offset, a traffic burst size for application traffic, a start time or phase of application traffic, an SPS grant size, etc.

[0114] As in Figure 5 , and further illustrated by reference numeral 510, the BS may transmit an indication of a DRX configuration and / or an SPS configuration to the UE. In some aspects, the BS may transmit an indication of a DRX configuration and / or an SPS configuration to the UE based at least in part on generating the DRX configuration and / or the SPS configuration, based at least in part on receiving a request for the DRX configuration and / or the SPS configuration from the UE, and / or the like. In some aspects, the BS may transmit the indication of the DRX configuration and / or the SPS configuration in a radio resource control (RRC) communication, a downlink control information (DCI) communication, a media access control (MAC) control element (MAC-CE) communication, and / or the like.

[0115] As in Figure 5 , and as further indicated by reference numeral 512, the UE may receive an indication of a DRX configuration and / or an SPS configuration, and may transmit and / or receive application data associated with an application server based at least in part on the DRX configuration and / or the SPS configuration. For example, the UE may transition to or out of a sleep or idle mode based at least in part on the DRX configuration to receive application traffic from the application server, may transmit application traffic to the application server based at least in part on the SPS configuration, and so on.

[0116] In this way, the BS can synchronize and / or align the DRX cycle and / or SPS cycle associated with the UE with the traffic cycle for application traffic associated with the application server. In this way, the traffic pattern and the DRX cycle and / or SPS cycle can be synchronized and / or aligned so that the UE wakes up from the sleep period to monitor the downlink traffic when the application server is transmitting application traffic to the UE, so that the UE is in the sleep period when the application server is not transmitting application traffic to the UE, so that the UE is allowed to transmit application traffic to the application server without delay, etc. This reduces lost or discarded application traffic caused by misalignment between the traffic cycle of the application traffic and the DRX cycle of the UE and / or the SPS cycle of the UE, reduces retransmission of application traffic, reduces delays in transmitting application traffic from the UE to the application server, and reduces consumption of processing and / or memory resources of the UE.

[0117] As indicated above, Figure 5 is provided as one or more examples. Other examples may differ from the Figure 5 Examples described.

[0118] Fig. 6A and 6B 6 is a diagram illustrating an example 600 of synchronization of traffic with DRX and / or SPS according to various aspects of the present disclosure. Fig. 6A and 6B As shown in , example 600 may include one or more devices, such as a UE (e.g., UE 120), a BS (e.g., BS 110), an AMF device (e.g., network controller 130), an SMF device (e.g., network controller 130), a PCF device (e.g., network controller 130), a UPF device (e.g., network controller 130), a NEF device (e.g., network controller 130), an application server (e.g., application server 140), etc. In some aspects, example 600 may include Fig. 6A and 6B In some aspects, the AMF device, SMF device, PCF device, UPF device, and NEF device may be included in a core network (such as a 5G / NR core network (e.g., NG core)) of a wireless network (e.g., wireless network 100).

[0119] In some aspects, an application server may host one or more applications, store information associated with the one or more applications, transmit and / or receive application traffic associated with the one or more applications, etc. The application traffic may include various types of periodic traffic, such as voice traffic, video traffic, virtual reality traffic, augmented reality traffic, heartbeat signals, game traffic, etc. In some aspects, the application traffic may include non-TSCs that are not carried on a QoS flow of a delay-critical GBR type.

[0120] In some aspects, an application server, a device included in a core network, a BS and / or a UE may coordinate to synchronize and / or align a traffic cycle for application traffic associated with the application server and a DRX cycle and / or an SPS cycle associated with the UE so as to reduce, mitigate and / or eliminate the effects of transmission delays accumulated along a communication path between the application server and the UE.

[0121] like Fig. 6A In the figure and as shown by reference numeral 602, the UE may determine to initiate a QoS flow for application traffic. As indicated above, the QoS flow for application traffic may be a non-delay critical and / or non-GBR type QoS flow. In some aspects, the UE may initiate a QoS flow by transmitting a QoS flow request to a PCF device via a BS, an AMF device, and / or an SMF device, and the PCF device may establish a QoS flow for application traffic. In some aspects, the QoS flow may include one or more QoS parameters, such as a priority level, an allowed packet delay budget, an allowed packet error rate, etc. One or more QoS parameters may be based at least in part on the type of traffic associated with the application. For example, the one or more QoS parameters may be associated with a specific value when the application traffic is voice traffic, may be associated with other specific values ​​when the application traffic is video traffic, and so on.

[0122] like Fig. 6A , and further illustrated by reference numeral 604, the UE may transmit to the BS a request for a DRX configuration and / or an SPS configuration for application traffic associated with an application server. In some aspects, the request may include an indication of a traffic mode for the application traffic, an indication of a QoS flow for the application traffic (e.g., a 5QI value associated with the QoS flow, a QFI associated with the QoS flow, and / or another type of QoS flow indicator), and the like. In some aspects, the UE may transmit the request based at least in part on initiating a QoS flow for the application traffic. Additionally and / or alternatively, the UE may include an indication of a traffic mode for the application traffic to the BS, and / or the PCF device may transmit an indication of a QoS flow to the BS.

[0123] In some aspects, the traffic pattern can specify a traffic cycle associated with the application traffic (e.g., the length of the time period between traffic bursts of the application traffic), a traffic burst size associated with the application traffic (e.g., the time length of a burst of application traffic transmitted from an application server), a start time or phase of the application traffic, and the like.

[0124] In some aspects, the UE may transmit the request in one or more uplink communications, such as RRC communications, uplink control information (UCI) communications, MAC-CE communications, etc. For example, the request may be included in a DRX and / or SPS request in an RRC communication, may be included in a buffer status report (BSR) in a MAC-CE communication, and the like.

[0125] like Fig. 6A In the request and further indicated by reference numeral 606, the BS may receive the request and may determine one or more parameters of a DRX configuration and / or SPS configuration associated with the UE for the application. In this way, the BS may use the indication of the traffic pattern and / or QoS flow in the request to generate a DRX configuration and / or SPS configuration so that the DRX cycle and / or SPS cycle of the UE is synchronized and / or aligned with the traffic pattern (e.g., synchronized and / or aligned with the traffic cycle, traffic burst size, start time and / or phase, etc. of the application traffic).

[0126] In some aspects, the BS may determine one or more parameters for DRX configuration and / or SPS configuration by performing one or more measurements associated with a traffic pattern of application traffic. For example, the BS may perform one or more downlink traffic measurements associated with the traffic pattern to determine a first offset (e.g., a DRX offset) between a traffic cycle associated with the application traffic and a DRX cycle for the UE. As another example, the BS may perform one or more uplink traffic measurements associated with the traffic pattern to determine a second offset (e.g., an SPS offset) between a traffic cycle associated with the application traffic and an SPS cycle for the UE. The first offset and the second offset may account for various types of transmission delays along the communication path between the UE and the application server so as to synchronize and / or align the DRX cycle and / or SPS cycle of the UE with the traffic cycle of the application traffic. In some aspects, one or more measurements may include RTT measurements, latency measurements, and the like.

[0127] In some aspects, one or more parameters for DRX configuration may include a first offset, a traffic burst size for application traffic, a start time or phase of application traffic, a DRX cycle duration (e.g., which may correspond to the duration of a traffic cycle for application traffic), etc. In some aspects, one or more parameters for SPS configuration may include a second offset, a traffic burst size for application traffic, a start time or phase of application traffic, an SPS grant size, etc.

[0128] As in Fig. 6A 6 and further indicated by reference numeral 608, the BS may transmit an indication of the DRX configuration and / or the SPS configuration to the UE. In some aspects, the BS may transmit the indication of the DRX configuration and / or the SPS configuration to the UE based at least in part on generating the DRX configuration and / or the SPS configuration, based at least in part on receiving a request for the DRX configuration and / or the SPS configuration from the UE, etc. In some aspects, the BS may transmit the indication of the DRX configuration and / or the SPS configuration in an RRC communication, a DCI communication, a MAC-CE communication, etc.

[0129] As in Figure 6B , and as indicated by reference numeral 610, the UE may receive an indication of a DRX configuration and / or an SPS configuration, and may transmit and / or receive application data associated with an application server based at least in part on the DRX configuration and / or the SPS configuration. For example, the UE may transition to or out of a sleep or idle mode based at least in part on the DRX configuration to receive application traffic from the application server, may transmit application traffic to the application server based at least in part on the SPS configuration, and so on.

[0130] In this way, the BS can synchronize and / or align the DRX cycle and / or SPS cycle associated with the UE with the traffic cycle for application traffic associated with the application server. In this way, the traffic pattern and the DRX cycle and / or SPS cycle can be synchronized and / or aligned so that the UE wakes up from the sleep period to monitor the downlink traffic when the application server is transmitting application traffic to the UE, so that the UE is in the sleep period when the application server is not transmitting application traffic to the UE, so that the UE is allowed to transmit application traffic to the application server without delay, etc. This reduces lost or discarded application traffic caused by misalignment between the traffic cycle of the application traffic and the DRX cycle of the UE and / or the SPS cycle of the UE, reduces retransmission of application traffic, reduces delays in transmitting application traffic from the UE to the application server, and reduces consumption of processing and / or memory resources of the UE.

[0131] As indicated above, Fig. 6A and 6B are provided as examples. Other examples may vary from Fig. 6Aand Figure 6B Examples described.

[0132] Fig. 7A and 7B is a diagram illustrating an example 700 of synchronization of traffic with DRX and / or SPS according to various aspects of the present disclosure. Fig. 7A and 7B As shown in , example 700 may include one or more devices, such as a UE (e.g., UE 120), a BS (e.g., BS 110), an AMF device (e.g., network controller 130), an SMF device (e.g., network controller 130), a PCF device (e.g., network controller 130), a UPF device (e.g., network controller 130), a NEF device (e.g., network controller 130), an application server (e.g., application server 140), etc. In some aspects, example 700 may include Fig. 7A and 7B In some aspects, the AMF device, SMF device, PCF device, UPF device, and NEF device may be included in a core network (such as a 5G / NR core network (e.g., NG core)) of a wireless network (e.g., wireless network 100).

[0133] In some aspects, an application server may host one or more applications, store information associated with one or more applications, transmit and / or receive application traffic associated with one or more applications, etc. The application traffic may include various types of periodic traffic, such as voice traffic, video traffic, virtual reality traffic, augmented reality traffic, heartbeat signals, game traffic, etc. In some aspects, the application traffic may include non-TSCs that are not carried on a QoS flow of a delay-critical GBR type.

[0134] In some aspects, an application server, a device included in a core network, a BS and / or a UE may coordinate to synchronize and / or align a traffic cycle for application traffic associated with the application server and a DRX cycle and / or an SPS cycle associated with the UE so as to reduce, mitigate and / or eliminate the effects of transmission delays accumulated along a communication path between the application server and the UE.

[0135] like Fig. 7A , and as indicated by reference numeral 702, an application server may transmit a first request for a DRX configuration and / or an SPS configuration associated with a UE to an NEF device. In some aspects, the application server may transmit the first request based at least in part on determining that the application server is to transmit application traffic to the UE. In some aspects, the NEF device may forward the first request to other devices included in the core network, such as a PCF device, etc.

[0136] like Fig. 7A , and as further shown by reference numeral 704, the PCF device may receive a first request and may initiate and / or establish a QoS flow for application traffic. As indicated above, the QoS flow for application traffic may be a non-delay critical and / or non-GBR type QoS flow. In some aspects, the QoS flow may include one or more QoS parameters, such as a priority level, an allowed packet delay budget, an allowed packet error rate, etc. The one or more QoS parameters may be based at least in part on a traffic type associated with an application. For example, the one or more QoS parameters may be associated with a specific value when the application traffic is voice traffic, may be associated with other specific values ​​when the application traffic is video traffic, and so on.

[0137] like Fig. 7A In the figure and further shown by reference numeral 706, the PCF device can transmit a first request and a second request for a traffic offset between the BS and an application server (e.g., a transmission delay or latency between the BS and the application server) to the BS. In some aspects, the PCF device can transmit the first request and the second request to the BS via an AMF device, via an SMF device, etc. In some aspects, the PCF device can transmit the first request and the second request based at least in part on initiating a QoS flow. In some aspects, the AMF device and / or the SMF device can transmit the first request and the second request to the BS via an N2 interface and / or another type of interface.

[0138] As in Fig. 7A In and further shown by reference numeral 708, the BS may receive the first request and the second request, and may determine the traffic offset based at least in part on receiving the first request and the second request. In some aspects, the BS may determine the traffic offset by performing one or more measurements associated with a user plane communication link (e.g., a communication link including a UPF device) between an application server and the BS. For example, the BS may perform one or more downlink traffic measurements to determine the downlink traffic offset between the application server and the BS, may perform one or more uplink traffic measurements to determine the uplink offset between the application server and the BS, and so on. The first offset and the second offset may account for various types of transmission delays (such as Internet delays, backhaul delays, etc.) along the communication path between the UE and the application server, so as to synchronize and / or align the DRX cycle and / or SPS cycle of the UE with the traffic cycle of the application traffic. In some aspects, one or more measurements may include RTT measurements, waiting time measurements, and the like.

[0139] As in Figure 7BIn the figure and indicated by reference numeral 710, the BS may transmit an indication of the traffic offset and an indication of the DRX configuration and / or the SPS configuration to the application server. In some aspects, the BS may transmit the indication of the traffic offset and / or the indication of the DRX configuration and / or the SPS configuration to the application server via an AMF device, an SMF device, a PCF device, an NEF device, etc. In some aspects, the BS may transmit the indication of the traffic offset and / or the indication of the DRX configuration and / or the SPS configuration based at least in part on determining the traffic offset.

[0140] In some aspects, the indication of the DRX configuration may include an indication of a DRX cycle duration associated with the DRX cycle of the UE, an indication of a DRX offset associated with the DRX cycle of the UE, etc. In some aspects, the indication of the SPS configuration may include an indication of an SPS grant size associated with the SPS cycle of the UE, etc. In some aspects, the indication of the traffic offset may include an indication of a downlink traffic offset determined by the BS and / or an indication of an uplink traffic offset determined by the BS.

[0141] As in Figure 7B , and as further indicated by reference numeral 712, the application server may adjust a traffic pattern associated with application traffic of the application server. In some aspects, the traffic pattern may specify a traffic cycle associated with the application traffic (e.g., the length of a time period between traffic bursts of the application traffic), a traffic burst size associated with the application traffic (e.g., a burst size of the application traffic transmitted from the application server), a start time or phase of the application traffic, etc. In some aspects, the application server may adjust one or more of these parameters based at least in part on a DRX configuration and / or an SPS configuration associated with the UE, based at least in part on a traffic offset between the application server and the BS, etc. For example, the application server may adjust the traffic cycle, the traffic burst size, and / or the start time or phase based at least in part on the traffic offset, based at least in part on the DRX cycle duration, based at least in part on the SPS grant size, based at least in part on the DRX offset, etc.

[0142] As in Figure 7B , and as further indicated by reference numeral 714, the UE and the application server may transmit and / or receive application data associated with the application server based at least in part on the DRX configuration and / or the SPS configuration and the adjusted traffic pattern for the application traffic. For example, the UE may transition to or out of a sleep or idle mode based at least in part on the DRX configuration to receive application traffic from the application server, may transmit application traffic to the application server based at least in part on the SPS configuration, etc. As another example, the application server may transmit application traffic to the UE according to the adjusted traffic pattern.

[0143] In this way, the application server can adjust the traffic cycle for application traffic associated with the application server based at least in part on the DRX cycle and / or SPS cycle associated with the UE, based at least in part on the traffic offset between the application server and the BS, etc. In this way, the traffic pattern and the DRX cycle and / or SPS cycle can be synchronized and / or aligned so that the UE wakes up from a sleep period to monitor downlink traffic when the application server is transmitting application traffic to the UE, so that the UE is in a sleep period when the application server is not transmitting application traffic to the UE, so that the UE is permitted to transmit application traffic to the application server without delay, etc. This reduces lost or discarded application traffic caused by misalignment between the traffic cycle of the application traffic and the DRX cycle of the UE and / or the SPS cycle of the UE, reduces retransmission of application traffic, reduces delays in transmitting application traffic from the UE to the application server, and reduces consumption of processing and / or memory resources of the UE.

[0144] As indicated above, Fig. 7A and 7B are provided as examples. Other examples may vary from Fig. 7A and Figure 7B Examples described.

[0145] Figures 8A-8C 8 is a diagram illustrating an example 800 of synchronization of traffic with DRX and / or SPS according to various aspects of the present disclosure. Figures 8A-8C As shown in , example 800 may include one or more devices, such as a UE (e.g., UE 120), a BS (e.g., BS 110), an AMF device (e.g., network controller 130), an SMF device (e.g., network controller 130), a PCF device (e.g., network controller 130), a UPF device (e.g., network controller 130), a NEF device (e.g., network controller 130), an application server (e.g., application server 140), etc. In some aspects, example 800 may include Figures 8A-8C In some aspects, the AMF device, SMF device, PCF device, UPF device, and NEF device may be included in a core network (such as a 5G / NR core network (e.g., NG core)) of a wireless network (e.g., wireless network 100).

[0146] In some aspects, an application server may host one or more applications, store information associated with one or more applications, transmit and / or receive application traffic associated with one or more applications, etc. The application traffic may include various types of periodic traffic, such as voice traffic, video traffic, virtual reality traffic, augmented reality traffic, heartbeat signals, game traffic, etc. In some aspects, the application traffic may include non-TSCs that are not carried on a QoS flow of a delay-critical GBR type.

[0147] In some aspects, an application server, a device included in a core network, a BS and / or a UE may coordinate to synchronize and / or align a traffic cycle for application traffic associated with the application server and a DRX cycle and / or an SPS cycle associated with the UE so as to reduce, mitigate and / or eliminate the effects of transmission delays accumulated along a communication path between the application server and the UE.

[0148] like Fig. 8A 8 and as shown by reference numeral 802, the UE may transmit to the BS a request for a traffic offset between the BS and an application server (e.g., a transmission delay or latency between the BS and the application server). In some aspects, the UE may further transmit to the BS a request for a DRX configuration and / or an SPS configuration associated with the UE. In some aspects, the request for the traffic offset and / or the request for the DRX configuration / SPS configuration may be generated by an application client of the UE and provided from the application client of the UE to a modem (e.g., a receive processor 258, a transmit processor 264, a controller / processor 280, and / or another processing component) of the UE. The modem may receive the request(s) and may provide the request(s) to a transmit chain (e.g., a TX MIMO processor 266, a MOD 254, an antenna 252, and / or other components) of the UE, which may transmit the request(s) to the BS.

[0149] As in Fig. 8AIn and further shown by reference numeral 804, the BS may receive the request and may determine the traffic offset based at least in part on receiving the request. In some aspects, the BS may determine the traffic offset by performing one or more measurements associated with a user plane communication link (e.g., a communication link including a UPF device) between an application server and the BS. For example, the BS may perform one or more downlink traffic measurements to determine the downlink traffic offset between the application server and the BS, may perform one or more uplink traffic measurements to determine the uplink offset between the application server and the BS, and so on. The first offset and the second offset may account for various types of transmission delays (such as Internet delays, backhaul delays, etc.) along the communication path between the UE and the application server so as to synchronize and / or align the DRX cycle and / or SPS cycle of the UE with the traffic cycle of the application traffic. In some aspects, one or more measurements may include RTT measurements, waiting time measurements, and the like.

[0150] As in Fig. 8A 8 and further shown by reference numeral 806, the BS may transmit an indication of the traffic offset to the UE. In some aspects, the BS may further transmit an indication of a DRX configuration and / or an SPS configuration associated with the UE. In some aspects, a receive chain of the UE (e.g., antenna 252, DEMOD 254, MIMO detector 256, and / or other components) may receive an indication of the DRX configuration and / or SPS configuration and may provide the indication to a modem of the UE. The modem may provide an indication of the DRX configuration and / or SPS configuration to an application client of the UE.

[0151] In some aspects, the indication of the DRX configuration may include an indication of a DRX cycle duration associated with the DRX cycle of the UE, an indication of a DRX offset associated with the DRX cycle of the UE, etc. In some aspects, the indication of the SPS configuration may include an indication of an SPS grant size associated with the SPS cycle of the UE, etc. In some aspects, the indication of the traffic offset may include an indication of a downlink traffic offset determined by the BS and / or an indication of an uplink traffic offset determined by the BS.

[0152] As in Figure 8B In the figure and as indicated by reference numeral 808, the UE may transmit an indication of the traffic shift and an indication of the DRX configuration and / or the SPS configuration to the application server. For example, the UE may transmit an indication of the traffic shift and an indication of the DRX configuration and / or the SPS configuration to the application server via a UPF device and / or other device included in the wireless network and / or other network.

[0153] As in Figure 8BAs further shown in Figure 8 and by reference numeral 810, the application server may adjust a traffic pattern associated with application traffic of the application server. In some aspects, the traffic pattern may specify a traffic cycle associated with the application traffic (e.g., the length of a time period between traffic bursts of the application traffic), a traffic burst size associated with the application traffic (e.g., a burst size of the application traffic transmitted from the application server), a start time or phase of the application traffic, etc. In some aspects, the application server may adjust one or more of these parameters based at least in part on a DRX configuration and / or an SPS configuration associated with the UE, based at least in part on a traffic offset between the application server and the BS, etc. For example, the application server may adjust the traffic cycle, the traffic burst size, and / or the start time or phase based at least in part on the traffic offset, based at least in part on the DRX cycle duration, based at least in part on the SPS grant size, based at least in part on the DRX offset, etc.

[0154] As in Figure 8C 8 and indicated by reference numeral 812, the UE and the application server may transmit and / or receive application data associated with the application server based at least in part on the DRX configuration and / or the SPS configuration and the adjusted traffic pattern for the application traffic. For example, the UE may transition to or out of a sleep or idle mode based at least in part on the DRX configuration to receive application traffic from the application server, may transmit application traffic to the application server based at least in part on the SPS configuration, etc. As another example, the application server may transmit application traffic to the UE according to the adjusted traffic pattern.

[0155] In this way, the application server can adjust the traffic cycle for application traffic associated with the application server based at least in part on the DRX cycle and / or SPS cycle associated with the UE, based at least in part on the traffic offset between the application server and the BS, etc. In this way, the traffic pattern and the DRX cycle and / or SPS cycle can be synchronized and / or aligned so that the UE wakes up from a sleep period to monitor downlink traffic when the application server is transmitting application traffic to the UE, so that the UE is in a sleep period when the application server is not transmitting application traffic to the UE, so that the UE is permitted to transmit application traffic to the application server without delay, etc. This reduces lost or discarded application traffic caused by misalignment between the traffic cycle of the application traffic and the DRX cycle of the UE and / or the SPS cycle of the UE, reduces retransmission of application traffic, reduces delays in transmitting application traffic from the UE to the application server, and reduces consumption of processing and / or memory resources of the UE.

[0156] As indicated above, Figures 8A-8C are provided as examples. Other examples may vary from Figures 8A-8C Examples described.

[0157] Fig. 9 is a diagram illustrating an example process 900, performed, for example, by a BS, in accordance with various aspects of the present disclosure. Example process 900 is an example of operations in which a BS (eg, BS 110) performs synchronization of traffic with DRX and / or SPS.

[0158] like Fig. 9 As shown in , in some aspects, process 900 may include receiving an indication of a traffic mode for application traffic (block 910). For example, the BS (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may receive an indication of a traffic mode for application traffic, as described above.

[0159] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include determining one or more parameters of at least one of a DRX configuration for the application traffic or an SPS configuration for the application traffic based at least in part on one or more measurements associated with the traffic pattern (block 920). For example, the BS (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may determine one or more parameters of at least one of a DRX configuration for the application traffic or an SPS configuration for the application traffic based at least in part on one or more measurements associated with the traffic pattern, as described above.

[0160] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include transmitting an indication of at least one of the DRX configuration or the SPS configuration to a UE that is to receive the application traffic (block 930). For example, the BS (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may transmit an indication of at least one of the DRX configuration or the SPS configuration to a UE that is to receive the application traffic, as described above.

[0161] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0162] In a first aspect, the application traffic is periodic non-TSC and is not carried on a QoS flow of a delay-critical GBR type. In a second aspect, alone or in combination with the first aspect, the traffic pattern includes at least one of a traffic cycle associated with the application traffic, a traffic burst size associated with the application traffic, or a start time or phase of the application traffic. In a third aspect, alone or in combination with one or more of the first and second aspects, receiving an indication of a traffic pattern for the application traffic includes: receiving an indication of the traffic pattern via at least one of an NEF device, a PCF device, an AMF device, or an SMF device.

[0163] In a fourth aspect, alone or in combination with one or more of the first to third aspects, receiving an indication of a traffic mode for the application traffic includes: receiving an indication of the traffic mode in a QoS profile associated with a QoS flow for the application traffic. In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the one or more parameters include at least one of: a first offset between a traffic cycle associated with the application traffic and a DRX cycle associated with the UE, a second offset between a traffic cycle associated with the application traffic and an SPS cycle associated with the UE, a traffic burst size for the application traffic, an SPS grant size, or a start time of the application traffic. In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 900 further includes: performing one or more measurements associated with the traffic mode, and the one or more measurements include at least one of one or more downlink traffic measurements associated with the traffic mode or one or more uplink traffic measurements associated with the traffic mode.

[0164] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 900. Additionally or alternatively, two or more blocks of the process 900 may be executed in parallel.

[0165] Fig.10 is a diagram illustrating an example process 1000 performed, for example, by a UE in accordance with various aspects of the present disclosure. Example process 1000 is an example of operations in which a UE (eg, UE 120) performs synchronization of traffic with DRX and / or SPS.

[0166] like Fig.10As further shown in FIG. 1 , in some aspects, process 1000 may include transmitting to a BS a request for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic, wherein the request includes an indication of a traffic mode associated with the application traffic (block 1020). For example, a UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may transmit to a BS a request for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic, as described above. In some aspects, the request includes an indication of a traffic mode associated with the application traffic.

[0167] like Fig.10 As further shown in FIG. 1 , in some aspects, process 1000 may include receiving, from the BS and based at least in part on transmitting the request, an indication of at least one of the DRX configuration or the SPS configuration (block 1030). For example, the UE (e.g., using receive processor 258, transmit processor 264, controller / processor 280, memory 282, etc.) may receive, from the BS and based at least in part on transmitting the request, an indication of at least one of the DRX configuration or the SPS configuration, as described above.

[0168] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0169] In a first aspect, the application traffic is periodic non-TSC and is not carried on a GBR QoS flow. In a second aspect, alone or in combination with the first aspect, the traffic pattern includes at least one of a traffic cycle associated with the application traffic, a traffic burst size associated with the application traffic, or a start time of the application traffic. In a third aspect, alone or in combination with one or more of the first and second aspects, at least one of the DRX configuration or the SPS configuration includes at least one of the following: a first offset between a traffic cycle associated with the application traffic and a DRX cycle associated with the UE, a second offset between a traffic cycle associated with the application traffic and an SPS cycle associated with the UE, a traffic burst size for the application traffic, an SPS grant size, or a start time of the application traffic. In a fourth aspect, alone or in combination with one or more of the first to third aspects, transmitting the request includes transmitting the request in an RRC communication, or transmitting the request in a MAC-CE communication.

[0170] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1000 includes initiating a QoS flow for the application traffic, and transmitting the request based at least in part on initiating the QoS flow. In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, at least one of the DRX configuration or the SPS configuration is based at least in part on a traffic pattern associated with the application traffic. In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1000 includes providing the request from an application client of the UE to a modem of the UE, and providing the indication from the modem to the application client.

[0171] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 1000. Additionally or alternatively, two or more blocks of the process 1000 may be executed in parallel.

[0172] Fig.11 is a diagram illustrating an example process 1100, performed, for example, by a BS, in accordance with various aspects of the present disclosure. Example process 1100 is an example of operations in which a BS (eg, BS 110) performs synchronization of traffic with DRX and / or SPS.

[0173] like Fig.11 As shown in , in some aspects, process 1100 may include: receiving a request for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic from a UE, wherein the request indicates a traffic mode for the application traffic (block 1110). For example, a BS (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may receive a request for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic from a UE, as described above. In some aspects, the request indicates a traffic mode for the application traffic.

[0174] like Fig.11 As further shown in FIG. 1 , in some aspects, process 1100 may include determining one or more parameters for at least one of the DRX configuration or the SPS configuration based at least in part on one or more measurements associated with the traffic pattern (block 1120). For example, the BS (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may determine one or more parameters for at least one of the DRX configuration or the SPS configuration based at least in part on one or more measurements associated with the traffic pattern, as described above.

[0175] like Fig.11 As further shown in FIG. 1 , in some aspects, process 1100 may include transmitting an indication of at least one of the DRX configuration or the SPS configuration to the UE (block 1130). For example, the BS (e.g., using transmit processor 220, receive processor 238, controller / processor 240, memory 242, etc.) may transmit an indication of at least one of the DRX configuration or the SPS configuration to the UE, as described above.

[0176] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0177] In a first aspect, the application traffic is periodic non-TSC and is not carried on a GBR QoS flow. In a second aspect, alone or in combination with the first aspect, the traffic pattern includes at least one of a traffic cycle associated with the application traffic, a traffic burst size associated with the application traffic, or a start time of the application traffic. In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more parameters include at least one of: a first offset between a traffic cycle associated with the application traffic and a DRX cycle associated with the UE, a second offset between a traffic cycle associated with the application traffic and an SPS cycle associated with the UE, a traffic burst size for the application traffic, an SPS grant size, or a start time of the application traffic.

[0178] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1100 further includes: performing one or more measurements associated with the traffic pattern, and the one or more measurements include at least one of one or more downlink traffic measurements associated with the traffic pattern or one or more uplink traffic measurements associated with the traffic pattern. In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, receiving the request includes receiving the request in an RRC communication, or receiving the request in a MAC-CE communication.

[0179] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the request includes an indication of a QoS flow associated with the application traffic, and determining the one or more parameters includes determining the one or more parameters based at least in part on the QoS flow associated with the application traffic. In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the indication of the QoS flow includes a QFI associated with the QoS flow.

[0180] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the process 1100 may be executed in parallel.

[0181] Fig.12 is a diagram illustrating an example process 1200, performed, for example, by an application server, in accordance with various aspects of the present disclosure. The example process 1200 is an example of operations in which an application server (eg, application server 140) performs synchronization of traffic with DRX and / or SPS.

[0182] like Fig.12 As shown in , in some aspects, process 1200 may include transmitting a request for at least one of a DRX configuration for a UE or an SPS configuration for the UE to a BS (block 1210). For example, an application server (e.g., using memory 296, controller / processor 297, communication unit 298, etc.) may transmit a request for at least one of a DRX configuration for a UE or an SPS configuration for the UE to a BS, as described above.

[0183] like Fig.12 As further shown in FIG. 1 , in some aspects, process 1200 may include receiving, from the BS and based at least in part on transmitting the request, an indication of at least one of the DRX configuration or the SPS configuration (block 1220). For example, an application server (e.g., using memory 296, controller / processor 297, communication unit 298, etc.) may receive, from the BS and based at least in part on transmitting the request, an indication of at least one of the DRX configuration or the SPS configuration, as described above.

[0184] like Fig.12 As further shown in FIG. 1 , in some aspects, process 1200 may include adjusting a traffic pattern for application traffic to be transmitted to the UE based at least in part on at least one of the DRX configuration or the SPS configuration (block 1230). For example, an application server (e.g., using memory 296, controller / processor 297, communication unit 298, etc.) may adjust a traffic pattern for application traffic to be transmitted to the UE based at least in part on at least one of the DRX configuration or the SPS configuration, as described above.

[0185] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0186] In a first aspect, the application traffic is periodic non-TSC and is not carried on a GBR QoS flow. In a second aspect, alone or in combination with the first aspect, the process 1200 further includes: receiving an indication of a traffic offset between the application server and the BS based at least in part on transmitting the request from the BS, and adjusting the traffic pattern includes adjusting the traffic pattern based at least in part on the traffic offset. In a third aspect, alone or in combination with one or more of the first and second aspects, the traffic offset includes at least one of a downlink traffic offset between the application server and the BS or an uplink traffic offset between the application server and the BS.

[0187] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, at least one of the DRX configuration or the SPS configuration includes at least one of a DRX cycle duration, a DRX offset, or an SPS grant size. In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, transmitting the request includes transmitting the request to the BS via at least one of an NEF device, a PCF device, an AMF device, or an SMF device. In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, receiving an indication of at least one of the DRX configuration or the SPS configuration includes receiving an indication of at least one of the DRX configuration or the SPS configuration via at least one of an NEF device, a PCF device, an AMF device, or an SMF device.

[0188] although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 1200. Additionally or alternatively, two or more blocks of the process 1200 may be executed in parallel.

[0189] Fig.13 is a diagram illustrating an example process 1300, performed, for example, by a network controller, in accordance with various aspects of the present disclosure. The example process 1300 is an example of operations in which a network controller (eg, network controller 130) performs operations associated with synchronization of traffic with DRX and / or SPS.

[0190] like Fig.13As shown in , in some aspects, process 1300 may include receiving a first request for at least one of a DRX configuration for a UE or an SPS configuration for the UE from an application server (block 1310). For example, a network controller (e.g., using controller / processor 290, memory 292, communication unit 294, etc.) may receive a first request for at least one of a DRX configuration for a UE or an SPS configuration for the UE from an application server, as described above.

[0191] like Fig.13 As further shown in FIG. 1 , in some aspects, process 1300 may include transmitting to a BS a first request and a second request for a traffic offset between the application server and the BS (block 1320). For example, a network controller (e.g., using controller / processor 290, memory 292, communication unit 294, etc.) may transmit to a BS a first request and a second request for a traffic offset between the application server and the BS, as described above.

[0192] like Fig.13 As further shown in FIG. 1 , in some aspects, process 1300 may include receiving, from the BS and based at least in part on transmitting the first request and the second request, an indication of at least one of the traffic offset and the DRX configuration or the SPS configuration (block 1330). For example, a network controller (e.g., using controller / processor 290, memory 292, communication unit 294, etc.) may receive, from the BS and based at least in part on transmitting the first request and the second request, an indication of at least one of the traffic offset and the DRX configuration or the SPS configuration, as described above.

[0193] like Fig.13 As further shown in FIG. 1 , in some aspects, process 1300 may include transmitting an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration to the application server (block 1340). For example, a network controller (e.g., using controller / processor 290, memory 292, communication unit 294, etc.) may transmit an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration to the application server, as described above.

[0194] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0195] In a first aspect, at least one of the DRX configuration or the SPS configuration includes at least one of a DRX cycle duration, a DRX offset, or an SPS grant size. In a second aspect, alone or in combination with the first aspect, transmitting the first request and the second request includes: transmitting the first request and the second request to the BS via at least one of a PCF device, an AMF device, or an SMF device. In a third aspect, alone or in combination with one or more of the first and second aspects, receiving an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration includes: receiving an indication of the traffic offset and at least one of the DRX configuration or the SPS configuration via at least one of a PCF device, an AMF device, or an SMF device. In a fourth aspect, alone or in combination with one or more of the first to third aspects, the network controller device includes a NEF device or a PCF device. In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the traffic offset comprises at least one of a downlink traffic offset between the application server and the BS or an uplink traffic offset between the application server and the BS.

[0196] although Fig.13 Example blocks of process 1300 are shown, but in some aspects, process 1300 may include Fig.13 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 1300. Additionally or alternatively, two or more blocks of the process 1300 may be executed in parallel.

[0197] Fig.14 is a diagram illustrating an example process 1400, performed, for example, by an application server, in accordance with various aspects of the present disclosure. Example process 1400 is an example of operations in which an application server (eg, application server 140) performs synchronization of traffic with DRX and / or SPS.

[0198] like Fig.14 As shown in , in some aspects, process 1400 may include receiving an indication of at least one of a DRX configuration associated with the UE or an SPS configuration associated with the UE from a UE or a network controller (block 1410). For example, an application server (e.g., using memory 296, controller / processor 297, communication unit 298, etc.) may receive an indication of at least one of a DRX configuration associated with the UE or an SPS configuration associated with the UE from a UE or a network controller, as described above.

[0199] like Fig.14As further shown in FIG. 14 , in some aspects, process 1400 may include adjusting a traffic pattern associated with application traffic to be transmitted to the UE based at least in part on at least one of the DRX configuration or the SPS configuration (block 1420). For example, an application server (e.g., using memory 296, controller / processor 297, communication unit 298, etc.) may adjust a traffic pattern associated with application traffic to be transmitted to the UE based at least in part on at least one of the DRX configuration or the SPS configuration, as described above.

[0200] Process 1400 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0201] In a first aspect, the application traffic is periodic non-TSC and is not carried on a GBR QoS flow. In a second aspect, either alone or in combination with the first aspect, adjusting the traffic pattern comprises at least one of: adjusting a traffic cycle associated with the application traffic, adjusting a traffic burst size associated with the application traffic, or adjusting a start time of the application traffic. In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1400 further comprises: receiving an indication of at least one of a downlink traffic offset between the application server and the UE or an uplink traffic offset between the application server and the UE, and adjusting the traffic pattern associated with the application traffic comprises adjusting the traffic pattern based at least in part on at least one of the downlink traffic offset or the uplink traffic offset.

[0202] although Fig.14 Example blocks of process 1400 are shown, but in some aspects, process 1400 may include Fig.14 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 1400. Additionally or alternatively, two or more blocks of the process 1400 may be executed in parallel.

[0203] Fig.15 1 is a block diagram of an example apparatus 1500 for wireless communication. Apparatus 1500 may be a BS, or a BS may include apparatus 1500. In some aspects, apparatus 1500 includes a receiving component 1502 and a transmitting component 1504, which may be in communication with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1500 may use receiving component 1502 and transmitting component 1504 to communicate with another apparatus 1506 (such as a UE, a base station, an application server, a network controller, or another wireless communication device). As further shown, apparatus 1506 may include determining component 1508 and one or more of the other examples.

[0204] In some aspects, the apparatus 1500 may be configured to perform the Figure 5 , 6A , 6B, 7A, 7B and / or 8A-8C. Additionally or alternatively, the device 1500 may be configured to perform one or more processes described herein (such as Fig. 9 The process of 900 Fig.11 In some aspects, Fig.15 The apparatus 1500 and / or one or more components shown in FIG. 1 may include a combination of the above Figure 2 Additionally or alternatively, Fig.15 One or more of the components shown in the above may be combined Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0205] The receiving component 1502 may receive communications (such as reference signals, control information, data communications, or combinations thereof) from the apparatus 1506. The receiving component 1502 may provide the received communications to one or more other components of the apparatus 1500. In some aspects, the receiving component 1502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and may provide the processed signals to one or more other components of the apparatus 1506. In some aspects, the receiving component 1502 may include a combination of the above. Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described apparatus.

[0206] Transmission component 1504 may transmit communications (such as reference signals, control information, data communications, or a combination thereof) to device 1506. In some aspects, one or more other components of device 1506 may generate communications and may provide the generated communications to transmission component 1504 for transmission to device 1506. In some aspects, transmission component 1504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications and may transmit the processed signals to device 1506. In some aspects, transmission component 1504 may include a combination of the above. Figure 2One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described apparatus. In some aspects, the transmitting component 1504 can be co-located with the receiving component 1502 in a transceiver.

[0207] In some aspects, the receiving component 1502 may receive an indication of a traffic pattern for application traffic (e.g., from a device 1506), the determining component 1508 may determine one or more parameters of at least one of a DRX configuration for the application traffic or an SPS configuration for the application traffic based at least in part on one or more measurements associated with the traffic pattern, the transmitting component 1504 may transmit an indication of at least one of the DRX configuration or the SPS configuration to another device 1506 that is to receive the application traffic, and so on. In some aspects, the receiving component 1502 may receive (e.g., from the device 1506) a request for at least one of a DRX configuration for application traffic or an SPS configuration for application traffic, wherein the request indicates a traffic pattern for the application traffic, the determining component 1508 may determine one or more parameters for at least one of the DRX configuration or the SPS configuration based at least in part on one or more measurements associated with the traffic pattern, the transmitting component 1504 may transmit (e.g., to the device 1506) an indication of at least one of the DRX configuration or the SPS configuration, and so on.

[0208] Fig.15 The number and arrangement of components shown in the drawings are provided as examples. In practice, there may be additional components, fewer components, different components, or different Fig.15 In addition, Fig.15 Two or more components shown in may be implemented in a single component, or Fig.15 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.15 The component set (e.g., one or more components) shown in FIG. 1 may perform the operations described by Fig.15 One or more functions performed by another set of components shown in .

[0209] Fig.16 1 is a block diagram of an example apparatus 1600 for wireless communication. Apparatus 1600 may be a UE, or a UE may include apparatus 1600. In some aspects, apparatus 1600 includes a receiving component 1602 and a transmitting component 1604, which may be in communication with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1600 may use receiving component 1602 and transmitting component 1604 to communicate with another apparatus 1606 (such as a UE, a base station, or another wireless communication device).

[0210] In some aspects, the apparatus 1600 may be configured to perform the Figure 5 , 6A , 6B, 7A, 7B and / or 8A-8C. Additionally or alternatively, the device 1600 may be configured to perform one or more processes described herein (such as Fig.10 In some aspects, the apparatus 1600 and / or Fig.16 One or more components shown in the figure may include the above combination Figure 2 Additionally or alternatively, Fig.16 One or more of the components shown in the above may be combined Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0211] The receiving component 1602 may receive a communication (such as a reference signal, control information, data communication, or a combination thereof) from the device 1606. The receiving component 1602 may provide the received communication to one or more other components of the device 1600. In some aspects, the receiving component 1602 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communication and may provide the processed signal to one or more other components of the device 1606. In some aspects, the receiving component 1602 may include a combination of the above. Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0212] Transmission component 1604 may transmit communications (such as reference signals, control information, data communications, or a combination thereof) to device 1606. In some aspects, one or more other components of device 1606 may generate communications and may provide the generated communications to transmission component 1604 for transmission to device 1606. In some aspects, transmission component 1604 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, and other examples) on the generated communications and may transmit the processed signals to device 1606. In some aspects, transmission component 1604 may include a combination of the above. Figure 2One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof of the described UE. In some aspects, the transmitting component 1604 can be co-located with the receiving component 1602 in a transceiver.

[0213] Transmitting component 1604 can transmit (e.g., to device 1506) a request for at least one of a DRX configuration for the application traffic or an SPS configuration for the application traffic based at least in part on initiating a QoS flow, wherein the request includes an indication of a traffic pattern associated with the application traffic. Receiving component 1602 can receive (e.g., from device 1606) an indication of at least one of the DRX configuration or the SPS configuration based at least in part on transmitting the request.

[0214] Fig.16 The number and arrangement of components shown in the drawings are provided as examples. In practice, there may be additional components, fewer components, different components, or different Fig.16 In addition, Fig.16 Two or more components shown in may be implemented in a single component, or Fig.16 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.16 The component set (e.g., one or more components) shown in FIG. 1 may perform the operations described by Fig.16 One or more functions performed by another set of components shown in .

[0215] Fig.17 1 is a block diagram of an example apparatus 1700 for wireless communication. Apparatus 1700 may be an application server, or an application server may include apparatus 1700. In some aspects, apparatus 1700 includes a receiving component 1702 and a transmitting component 1704, which may be in communication with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1700 may use receiving component 1702 and transmitting component 1704 to communicate with another apparatus 1706 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 1706 may include an adjustment component 1708 and one or more of the other examples.

[0216] In some aspects, the apparatus 1700 may be configured to perform the Figure 5 , 6A , 6B, 7A, 7B and / or 8A-8C. Additionally or alternatively, the device 1700 may be configured to perform one or more processes described herein (such as Fig.14 In some aspects, the apparatus 1700 and / or Fig.17 One or more components shown in the figure may include the above combination Figure 2 Additionally or alternatively, Fig.17 One or more of the components shown in the above may be combined Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0217] The receiving component 1702 may receive a communication (such as a reference signal, control information, data communication, or a combination thereof) from the device 1706. The receiving component 1702 may provide the received communication to one or more other components of the device 1700. In some aspects, the receiving component 1702 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communication and may provide the processed signal to one or more other components of the device 1706. In some aspects, the receiving component 1702 may include a combination of the above. Figure 2 One or more antennas, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described application servers.

[0218] Transmission component 1704 may transmit communications (such as reference signals, control information, data communications, or a combination thereof) to device 1706. In some aspects, one or more other components of device 1706 may generate communications and may provide the generated communications to transmission component 1704 for transmission to device 1706. In some aspects, transmission component 1704 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, encoding, and other examples) on the generated communications and may transmit the processed signals to device 1706. In some aspects, transmission component 1704 may include a combination of the above. Figure 2 One or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described application servers. In some aspects, the transmission component 1704 can be co-located with the reception component 1702 in a transceiver.

[0219] Receiving component 1702 can receive (e.g., from device 1706) an indication of at least one of a DRX configuration associated with the device 1706 or an SPS configuration associated with the device 1706. Adjusting component 1708 can adjust a traffic pattern associated with application traffic to be transmitted to device 1706 based at least in part on at least one of the DRX configuration or the SPS configuration.

[0220] Fig.17 The number and arrangement of components shown in the drawings are provided as examples. In practice, there may be additional components, fewer components, different components, or different Fig.17 In addition, Fig.17 Two or more components shown in may be implemented in a single component, or Fig.17 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.17 The component set (e.g., one or more components) shown in FIG. 1 may perform the operations described by Fig.17 One or more functions performed by another set of components shown in .

[0221] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired by practice of the various aspects.

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

[0223] It will be apparent that the systems and / or methods described herein can be implemented in different forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the various aspects. Thus, the operation and behavior of these systems and / or methods are described herein without reference to specific software codes-it is understood that software and hardware can be designed to implement these systems and / or methods based at least in part on the description herein.

[0224] Although specific feature combinations are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. Although each dependent claim listed below can be directly subordinate to only one claim, the disclosure of various aspects includes that each dependent claim is combined with each other claim in this group of claims. The phrase quoting "at least one of" a column of items refers to any combination of these items, including single members. As an example, "at least one of a, b or c" is intended to cover: a, b, c, ab, ac, bc, and abc, and any combination with multiple identical elements (for example, aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other sorting of a, b and c).

[0225] Elements, actions or instructions used herein should not be interpreted as critical or necessary unless explicitly described as such. Moreover, as used herein, the articles "one" and "a" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, non-related items, combinations of related and non-related items, etc.), and can be used interchangeably with "one or more". In the case of intending to have only one item, the phrase "only one" or similar language is used. Moreover, as used herein, the terms "having", "containing", "including", etc. are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated.

Claims

1. A wireless communication method performed by a base station (BS), comprising: receiving an indication of a traffic mode for application traffic; determining, based at least in part on one or more measurements associated with the traffic pattern, one or more parameters for at least one of: a discontinuous reception (DRX) configuration for the application traffic, wherein the one or more parameters are configured to synchronize the traffic pattern with a DRX cycle of a user equipment (UE), or a semi-persistent scheduling (SPS) configuration for the application traffic, wherein the one or more parameters are configured to synchronize the traffic pattern with an SPS cycle of the UE; as well as An indication of the at least one of the DRX configuration or the SPS configuration is transmitted to the UE that is to receive the application traffic.

2. The method of claim 1, wherein the application traffic is periodic non-time sensitive communication (non-TSC) and is not carried on a delay critical guaranteed bit rate (GBR) type quality of service (QoS) flow.

3. The method of claim 1, wherein the traffic pattern comprises at least one of: a traffic cycle associated with said application traffic, the traffic burst size associated with the application traffic, or The starting time or phase of the application traffic.

4. The method of claim 1 , wherein receiving the indication of the traffic mode for the application traffic comprises: The indication of the traffic mode is received via at least one of: Network Open Function (NEF) devices, Policy Control Function (PCF) device, Access and Mobility Management Function (AMF) equipment, or Session Management Function (SMF) device.

5. The method of claim 1 , wherein receiving the indication of the traffic mode for the application traffic comprises: The indication of the traffic pattern is received in a quality of service (QoS) profile associated with a QoS flow for the application traffic.

6. The method of claim 1, wherein the one or more parameters include at least one of: a first offset between a traffic cycle associated with the application traffic and the DRX cycle, a second offset between the traffic cycle associated with the application traffic and the SPS cycle, The traffic burst size for the application traffic, SPS grant size, or The start time of the application traffic.

7. The method of claim 1, further comprising: The one or more measurements associated with the traffic pattern are performed.

8. The method of claim 7, wherein the one or more measurements include at least one of: one or more downlink traffic measurements associated with the traffic pattern, or One or more uplink traffic measurements associated with the traffic pattern.

9. A wireless communication method performed by a user equipment (UE), comprising: A request is transmitted to a base station (BS) for at least one of: a discontinuous reception (DRX) configuration for application traffic, wherein the DRX configuration is used to synchronize a traffic pattern with a DRX cycle of the UE, or a semi-persistent scheduling (SPS) configuration for the application traffic, wherein the SPS configuration is used to synchronize the traffic pattern with an SPS cycle of the UE, wherein the request includes an indication of a traffic pattern associated with the application traffic; and An indication of the at least one of the DRX configuration or the SPS configuration is received from the BS and based at least in part on transmitting the request.

10. The method of claim 9, wherein the at least one of the DRX configuration or the SPS configuration is based at least in part on the traffic pattern associated with the application traffic.

11. The method of claim 9, wherein the application traffic is periodic non-time sensitive communication (non-TSC) and is not carried on a guaranteed bit rate (GBR) type QoS flow.

12. The method of claim 9, wherein the traffic pattern comprises at least one of: a traffic cycle associated with said application traffic, the traffic burst size associated with the application traffic, or The start time of the application traffic.

13. The method of claim 9, wherein the at least one of the DRX configuration or the SPS configuration comprises at least one of: a first offset between a traffic cycle associated with the application traffic and the DRX cycle, a second offset between the traffic cycle associated with the application traffic and the SPS cycle, The traffic burst size for the application traffic, SPS grant size, or The start time of the application traffic.

14. The method of claim 9, further comprising: providing the request from an application client of the UE to a modem of the UE; as well as The indication of the traffic pattern associated with the application traffic or the indication of the at least one of the DRX configuration or the SPS configuration is provided from the modem to the application client.

15. The method of claim 9, further comprising: Initiating a quality of service (QoS) flow for the application traffic; as well as The request is transmitted based at least in part on initiating the QoS flow.

16. A wireless communication method performed by a base station (BS), comprising: Receiving a request from a user equipment (UE) for at least one of: a discontinuous reception (DRX) configuration for application traffic, wherein the DRX configuration is used to synchronize a traffic pattern with a DRX cycle of the UE, or a semi-persistent scheduling (SPS) configuration for the application traffic, wherein the SPS configuration is used to synchronize the traffic pattern with an SPS cycle of the UE, wherein the request indicates a traffic mode for the application traffic; determining one or more parameters for the at least one of the DRX configuration or the SPS configuration based at least in part on one or more measurements associated with the traffic pattern; as well as An indication of the at least one of the DRX configuration or the SPS configuration is transmitted to the UE.

17. The method of claim 16, wherein the application traffic is periodic non-time sensitive communication (non-TSC) and is not carried on a guaranteed bit rate (GBR) quality of service (QoS) flow.

18. The method of claim 16, wherein the traffic pattern comprises at least one of: a traffic cycle associated with said application traffic, the traffic burst size associated with the application traffic, or The start time of the application traffic.

19. The method of claim 16, wherein the one or more parameters include at least one of the following: a first offset between a traffic cycle associated with the application traffic and the DRX cycle, a second offset between the traffic cycle associated with the application traffic and the SPS cycle, The traffic burst size for the application traffic, SPS grant size, or The start time of the application traffic.

20. The method of claim 16, further comprising: The one or more measurements associated with the traffic pattern are performed.

21. The method of claim 20, wherein the one or more measurements include at least one of: one or more downlink traffic measurements associated with the traffic pattern, or One or more uplink traffic measurements associated with the traffic pattern.

22. The method of claim 16, wherein receiving the request comprises: receiving the request in a radio resource control (RRC) communication, or The request is received in a Medium Access Control (MAC) Control Element (MAC-CE) communication.

23. The method of claim 16, wherein the request includes an indication of a quality of service (QoS) flow associated with the application traffic.

24. The method of claim 23, wherein determining the one or more parameters comprises: The one or more parameters are determined based at least in part on the QoS flow associated with the application traffic.

25. The method of claim 24, wherein the indication of the QoS flow comprises: A QoS flow indicator (QFI) associated with the QoS flow.

26. A wireless communication method performed by an application server, comprising: Receiving an indication from a user equipment (UE) or a network controller of at least one of: a discontinuous reception (DRX) configuration associated with the UE, wherein the DRX configuration is used to synchronize a traffic pattern with a DRX cycle of the UE, or a semi-persistent scheduling (SPS) configuration associated with the UE, wherein the SPS configuration is used to synchronize the traffic pattern with an SPS cycle of the UE; as well as A traffic pattern associated with application traffic to be transmitted to the UE is adjusted based at least in part on at least one of the DRX configuration or the SPS configuration.

27. The method of claim 26, wherein the application traffic is periodic non-time sensitive communication (non-TSC) and is not carried on a guaranteed bit rate (GBR) quality of service (QoS) flow.

28. The method of claim 26, wherein adjusting the traffic pattern comprises at least one of: adjusting a traffic cycle associated with the application traffic, adjusting a traffic burst size associated with the application traffic, or Adjust the start time of the application traffic.

29. The method of claim 26, further comprising: Receiving an indication of at least one of: downlink traffic offset between the application server and the UE, or Uplink traffic offset between the application server and the UE.

30. The method of claim 29, wherein adjusting the traffic pattern associated with the application traffic comprises: The traffic pattern is adjusted based at least in part on the at least one of the downlink traffic offset or the uplink traffic offset.

Images