Peak traffic position adjustment for wireless communication

Methods, systems, and devices for wireless communication are described. A network node may determine a first time location associated with a peak in data traffic for multiple devices in communication with a communications network including the network node. The network node may determine a second time location for the peak in the data traffic for a subset of the devices based on a threshold for an overall peak in data traffic for the multiple devices. The network node may transmit a signal that indicates the second time location for the peak in the data traffic for the subset of devices. The network node may communicate the data with the subset of devices based on the signal indicating the second time location.

FIELD OF TECHNOLOGY

The following relates to wireless communication, including peak traffic position adjustment for wireless communication.

BACKGROUND

In some wireless communications systems, a network may communicate uplink data, downlink data, or both with multiple UEs. The data traffic for each UE may, in some cases, include one or more peaks or bursts associated with a relatively large quantity of bits of data being communicated at a time.

SUMMARY

The described techniques relate to improved methods, systems, devices, and apparatuses that support peak traffic position adjustment for wireless communication. Generally, the described techniques provide for a network node to adjust a time at which a peak in data traffic occurs for a subset of users supported by the network. The peak in the data traffic may correspond to a quantity of bits of the data traffic that is greater than quantities of bits of the data traffic at other times. The network node may offset the time at which the peaks occur to reduce a total quantity of bits of the data traffic at a time, which may provide for the network to support improved communication reliability and quality of service (QOS) parameters for each user. The network node may determine a first time associated with a first peak in data traffic that corresponds to a first quantity of bits of data for the multiple devices exceeding a threshold value. The network node may determine the first time based on communicating the data with the devices or based on an indication received via signaling from a logical entity of the network. In some examples, a device, such as a user equipment (UE) or an application client may determine the first time based on communicating data or based on an indication received from an application server. The device may transmit an indication of the first time to the network node. The network node may determine a second time associated with the first peak in the data traffic and that corresponds to a second quantity of bits of the data for the device or a subset of the devices. The second quantity of bits may be less than a threshold value and may satisfy QoS parameters for the subset of devices. The network node may determine an offset between the first time and the second time based on communication parameters associated with the subset of devices.

The network node may transmit a signal to a logical entity of the network, such as an edge server or a data network, to indicate the second time for the subset of devices. In some examples, the network node may transmit the signal indicating the second time to the UE, the application client, or both (e.g., via an application program interface (API)). The signal may indicate the second time, the offset between the first time and the second time, a periodicity associated with the second quantity of bits, the subset of devices associated with the second time, or any combination thereof. In some examples, the network node may transmit the signal to one or more of the devices (e.g., application clients). The network node may communicate the data with the subset of devices based on the second time indicated via the signal. For example, a second quantity of bits of the data for the subset of devices at the second time may be greater than a third quantity of bits of the data for the subset of devices at a third time. That is, the second time may be associated with an adjusted timing of the first peak in the data for the subset of devices that is offset from the first time at which there is a peak in the data for one or more other devices. The offset between peaks may support improved communication reliability and reduced latency for the devices.

DETAILED DESCRIPTION

Some wireless communications systems may support relatively low-latency applications, such as extended reality (XR) applications. Such applications may be associated with relatively low latency uplink or downlink video traffic or other data traffic. Such data traffic may be transmitted periodically or semi-periodically in bursts, such as per frame. A burst of data traffic may be referred to as a peak, and may correspond to a time at which a quantity of bits of the data traffic being transferred is a maximum quantity (e.g., higher than other quantities of bits of the data traffic at other times). Additionally or alternatively, a peak in data traffic may correspond to a time at which a quantity of bits of the data traffic being transferred is greater than a threshold quantity. In some examples, the threshold quantity may be based on a maximum data burst volume (MDBV) parameter for the data traffic. The MDBV parameter may be configured for or associated with a quality of service (QOS) flow via which the data traffic is communicated. The MDBV may indicate a quantity of bits of data transfer that the network supports at a time.

Each QoS flow may additionally or alternatively support one or more other QoS parameters, such as a packet delay budget (PDB), a packet error rate (PER), or both. If an amount of data being transmitted at a given time is less than the MDBV, the network may communicate the data traffic in accordance with the QoS parameters. The quantity of bits of the data traffic may, in some cases, exceed the MDBV if the network supports low-latency data traffic for multiple users. For example, one or more peaks in the data traffic for each user may overlap or collide, such that a total data volume exceeds the MDBV. If the quantity of bits of the data traffic exceeds the MDBV at a given time, the network may not be able to satisfy the QoS parameters for each user.

Techniques described herein provide for a network node, such as a base station, or some other node of a radio access network (RAN), to adjust a time location at which a peak in data traffic occurs for one or more users, which may reduce a total quantity of bits of data communicated by the network at a time. By adjusting the data traffic peaks, a total quantity of bits may not exceed a configured MDBV, such that the network may ensure that QoS parameters for each user are satisfied. The network node may determine an initial time location at which one or more bursts or peaks of the data traffic occur for each user by monitoring a data flow for multiple users or based on an indication conveyed via a QoS request. The network node may receive the QoS request message from an edge server or a data network to establish a connection and initiate communications using one or more QoS flows. In some examples, a device (e.g., a user equipment (UE) or an application client, or both) in communication with the network node may determine the initial timing of the one or more peaks based on communicating the data or based on an indication received from an application server. The device may transmit an indication of the initial timing to the network node. If a quantity of bits to be communicated at an identified time exceeds a threshold amount for an overall peak in the data traffic for the devices (e.g., the MDBV), the network node may determine to adjust a timing of the peak in data traffic for at least a subset of the users. The network node may determine a second time location at which the one or more peaks may occur for the subset of the users. The second time location may be offset from the initial time location of the peak for multiple users by an offset value. The network node may determine the subset of users, the offset value, or both based on communication parameters associated with the users.

The network node may transmit an indication of the offset value, which may be referred to as an offset to peak parameter, to a data network or to an edge server via a network exposure function (NEF) interface or some other interface between the data network and the network node. If the edge server (e.g., an access function (AF)) receives the offset to peak parameter, the edge server may forward the indication to the data network. The data network may adjust a data traffic flow for the subset of users according to the offset. In some examples, the network node may transmit an indication of the offset value to a UE, which may forward the indication to an application client, a corresponding application server, or both via an application program interface (API). The network node, the application client, or the application server may adjust the data traffic for the application client according to the offset. Adjusting the data traffic flow may include adjusting a timing of the data traffic such that a peak in the data traffic for the subset of users or for the application client may occur at the second time location based on the indicated offset value. Stated alternatively, a quantity of bits of data transferred at the second time location may be greater than a quantity of bits of the data transferred at other times. The data traffic may be downlink data traffic or uplink data traffic.

Particular aspects of the subject matter described herein may be implemented to realize one or more of the following potential advantages. By adjusting a timing of a peak in data traffic for one or more users, a network node may reduce a total quantity of bits of data communicated at a time, which may improve communication reliability and reduce latency. For example, the network node may satisfy QoS parameters for each user by adjusting the peak timing. The network node may thereby support efficient and reliable communications for more users than if the network node does not adjust the timing of the peaks in the data traffic. In some examples, the network node may determine the subset of users based on one or more communication parameters associated with the subset of users, such as a link condition of the subset of users, which may provide for improved communication reliability for the subset of users. The network node may receive signaling that indicates an initial timing of the peaks in the data traffic, which may improve coordination between devices, reduce latency, and reduce processing by the network node. Alternatively, the network node may determine the initial timing of the peaks in the data traffic by monitoring the data traffic, which may reduce overhead.

Aspects of the disclosure are initially described in the context of wireless communications systems. Additional aspects are described with reference to communications timelines, process flows, signaling paths, and flow diagrams. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to peak traffic position adjustment for wireless communication.

In some examples, one or more components of the wireless communications system100may operate as or be referred to as a network node. As used herein, a network node may refer to any UE115, base station105, entity of a core network130, apparatus, device, or computing system configured to perform any techniques described herein. For example, a network node may be a UE115. As another example, a network node may be a base station105. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE115, the second network node may be a base station105, and the third network node may be a UE115. In another aspect of this example, the first network node may be a UE115, the second network node may be a base station105, and the third network node may be a base station105. In yet other aspects of this example, the first, second, and third network nodes may be different. Similarly, reference to a UE115, a base station105, an apparatus, a device, or a computing system may include disclosure of the UE115, base station105, apparatus, device, or computing system being a network node. For example, disclosure that a UE115is configured to receive information from a base station105also discloses that a first network node is configured to receive information from a second network node. In this example, consistent with this disclosure, the first network node may refer to a first UE115, a first base station105, a first apparatus, a first device, or a first computing system configured to receive the information; and the second network node may refer to a second UE115, a second base station105, a second apparatus, a second device, or a second computing system

In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrow band IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.

In the wireless communications system100, the core network130may support communications with multiple UEs115via one or more network nodes or other network entities, such as a base station105. As described herein, a network node may adjust a time at which a peak in data traffic occurs for a subset of the UEs115supported by the core network130. The peak in the data traffic may correspond to a quantity of bits of the data traffic being greater than quantities of bits of the data traffic at other times. The network node may offset a time at which a peak occurs to reduce a total quantity of bits of the data traffic at a time, which may provide for the network to support improved communication reliability and QoS parameters for each UE115. The network node may determine a first time at which a first quantity of bits of data for the multiple UEs115exceeds a threshold value. The network node may determine the first time based on communicating the data with the UEs115or based on an indication received via signaling from a logical entity of the core network130. The network node may determine a second time that corresponds to a second quantity of bits of the data for a subset of the UEs115. The second quantity of bits may be less than a threshold value and may satisfy QoS parameters for the subset of UEs115. The network node may determine an offset between the first time and the second time based on communication parameters associated with the subset of UEs115.

The network node may transmit a signal to a logical entity of the network, such as an edge server or a data network, to indicate the second time for the subset of UEs115. The signal may indicate the second time, the offset between the first time and the second time, a periodicity associated with the second quantity of bits, the subset of devices associated with the second time, or any combination thereof. In some examples, the network node may transmit the signal to one or more of the UEs115(e.g., application clients). The network node may communicate the data with the subset of UEs115based on the second time indicated via the signal. For example, a second quantity of bits of the data for the subset of UEs115at the second time may be greater than a third quantity of bits of the data for the subset of UEs115at a third time. That is, the second time may be associated with a peak in the data for the subset of UEs115that is offset from the first time at which there is a peak in the data for one or more other UEs115. The offset between peaks may support improved communication reliability and reduced latency for the UEs115and the applications supported by the UEs115.

FIG.2illustrates an example of a wireless communications system200that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The wireless communications system200may implement or be implemented by aspects of the wireless communications system100as described with reference toFIG.1. For example, the wireless communications system200may include a base station105-aand UEs115-a,115-b, and115-c, which may represent examples of a base station105and a UE115as described with reference toFIG.1. The base station105-amay communicate with each of the UEs115within a geographic coverage area110-aand via a respective communication link215(e.g., communication links215-a,215-b, and215-c). The base station105-amay communicate with an edge server210via a backhaul link220. The edge server210may represent an example of a network node or a logical entity of the network, such as an edge cloud, an AF, or some other network entity. In some examples, the base station105-amay be referred to as a network node.

The UEs115may, in some examples, support one or more applications (e.g., cloud gaming applications, XR applications, virtual reality (VR) split rendering applications, augmented reality (AR) split computation applications, some other applications, or any combination thereof) that may be associated with relatively frequent uplink data traffic, downlink data traffic, or both. The data traffic for the one or more applications may be associated with relatively frequent changes (e.g., low latency). In some examples, each UE115may share computational or rendering processes with the edge server210(e.g., an edge cloud), which may result in frequent uplink and downlink transmissions with relatively small data packet sizes. In some examples, one or more of the UEs115may be a wearable device (e.g., an XR headset). Additionally or alternatively, one or more of the UEs115may represent an example of or be in communication with an application client or a client device (e.g., a gaming device or controller) via an API. In some examples, the application client may be software or a logical entity that is executed by the UE115.

The uplink data traffic, the downlink data traffic, or both for such applications may include encoded video data (e.g., cloud gaming traffic). The video traffic may be periodic or quasi-periodic based on a frame rate of the data. For example, the UE115-amay receive periodic or quasi-periodic bursts of data traffic every frame (e.g., at one frame-per-second (1/fps), or two possibly staggered per frame at1/(2*fps)). For example, the data traffic may occur every X seconds, where X may be 1/90 seconds, 1/60 seconds, or some other duration depending on a quantity of configured frames per second. A burst of data traffic may be referred to as a peak in data traffic and may correspond to a time at which a quantity of bits of data transmitted to or from one or more UEs115exceeds a threshold quantity of bits. Additionally or alternatively, the data bursts or peaks may correspond to times at which a quantity of bits of data transfer for one or more UEs115is greater than a quantity of bits of data transfer for the one or more UEs115at other times.

The frames for the uplink and downlink data traffic may be intra-coded (I) frames or predicted (P) frames. In some examples, the data traffic may be transmitted according to a group of pictures method, where some of the frames may be I-frames and some of the frames may be P-frames. The I-frames may be larger than the P-frames (e.g., a size ratio of three to one, or some other ratio). For example, the I-frames may include more bits or pixels than the P-frames. The data traffic may be transmitted using I-frames and P-frames in a periodic manner, or the transitions between I-frames and P-frames may be aperiodic. If the I-frames are transmitted in a periodic manner, the peaks in data traffic may be periodic based on the I-frames. Alternatively, if the I-frames are transmitted aperiodically or quasi-periodically, the peaks in the data traffic may be aperiodic or quasi-periodic.

The edge server210may be in communication with a core network directly or via one or more other layers or logical entities. The core network may represent an example of a core network130described with reference toFIG.1. The core network may establish one or more QoS flows for communicating data between each UE115and the network. Each QoS flow may be configured with or correspond to an MDBV, which may indicate a quantity of bits that the QoS flow may support at a time. The network may configure one or more QoS parameters for each QoS flow. The edge server210may forward a QoS request225to the base station105-a. The QoS request225may establish each QoS flow and indicate the QoS parameters for communications with one or more UEs115via the respective QoS flow. In some examples, the base station105-amay forward the QoS request225to one or more of the UEs115-a.115-b, and115-cto indicate the QoS parameters. The QoS parameters may include a PDB, a PER, one or more other QoS parameters, or any combination thereof.

The network may support communications with each UE115in accordance with or based on the QoS parameters for each QoS flow. For example, the network may ensure that a delay and an error rate of data traffic within each QoS flow do not exceed the PDB and PER for the QoS flow to improve communication reliability and support latency requirements for each application. The network may meet the QoS parameters (e.g., the PDB and PER at average bit-rates) for data traffic peaks that are the same as or less than the MDBV. The data traffic may exceed the MDBV if peaks for multiple UEs115overlap or collide in time. For example, if the network serves multiple UEs115at a time, and the peaks in data traffic for the UEs115overlap in time, a total quantity of bits of the traffic may exceed the MDBV. If a quantity of bits of data traffic transmitted via a QoS flow at a time exceeds the MDBV, the network may not support the QoS parameters. That is, the network may not be able to ensure that the QoS parameters are satisfied for each client if the data traffic exceeds the MDBV (e.g., a threshold value).

Techniques described herein provide for the network to adjust a time at which a peak in data traffic occurs for one or more UEs115based on a threshold for an overall peak in data traffic for the one or more UEs115. By adjusting the peak timing, the network may reduce a maximum quantity of bits of data transfer for multiple UEs115at a time and support communications with more UEs115while satisfying QoS parameters for each of the UEs115than if the network does not adjust the timing of the peaks. A network node, such as the base station105-a, or some other network node in communication with the edge server210, may identify a first time at which the data traffic for the UEs115exceeds a threshold value (e.g., a first peak data location) by monitoring the data traffic or by receiving an indication of the first time via the QoS request225. Additionally or alternatively, an application client or a UE115may determine the first time associated with the first peak in the data based on monitoring data traffic or receiving an indication of the first time from an application server in communication with the application client. In this case, the application client or the UE115may transmit an indication of the first time to the network node via an API (e.g., using a UE115as a relay device). Techniques for determining or identifying the peak data locations for each UE115are described in further detail with reference toFIGS.3-7.

The base station105-amay determine, in response to identifying that a quantity of bits of the data traffic for one or more users exceeds the threshold quantity at the first time, a second time that is associated with a second location of the peak in data traffic and that corresponds to a second quantity of bits of the data traffic for a subset of the multiple UEs115. The second time may correspond to a peak data location for the subset of UEs115that is offset from the first time (e.g., an adjusted peak data location). The base station105-amay transmit the QoS response message230to the edge server210to indicate the second time for the subset of UEs115, and the edge server210may forward the QoS response message230to a data network, as described with reference toFIG.6A. Additionally or alternatively, the base station105-amay transmit the QoS response message230directly to the data network, as described with reference toFIG.6B. In some examples, the QoS response message230may be referred to as a signal herein. In some examples, the base station105-a(e.g., a network node) may transmit the indication of the offset between the first time and the second time to a UE115, and the UE115may forward the indication to an application client via an API, as described with reference toFIG.7.

The data network may generate and transmit downlink data traffic to the subset of UEs115based on the indication of the second time. For example, a quantity of bits of the data traffic for the subset of UEs115at the second time may be greater than a quantity of bits of the data traffic for the subset of UEs115at other times. That is, the second time may correspond to an adjusted peak in the data traffic for the subset of UEs115that is offset from the peak in data traffic for other UEs115in communication with the network. A total quantity of bits of data communicated by the network at a given time may thereby be the same as or less than an MDBV value, such that the network may support efficient and reliable communications and support QoS parameters for each user.

In some examples, an application client may identify a location of the peaks in uplink data traffic for each user and indicate the peak location information to the base station105-a. In such cases, the base station105-amay determine a second time at which one or more peaks occur for a subset of users and transmit an indication of the second time to the application client via an API. In some examples, the base station105-amay transmit the indication of the second time to a UE115and the UE115may relay the indication to the application client. The application client and the base station105-amay communicate uplink data in accordance with the indicated second time. Such uplink data traffic adjustments are described in further detail with reference toFIG.7.

FIGS.3A and3Billustrate examples of communications timelines300that support peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The communications timelines300-aand300-bmay implement or be implemented by aspects of the wireless communications systems100and200described with reference toFIGS.1and2. For example, the communications timelines300may illustrate timing for data traffic310communicated by a user, which may be an example of a UE115or an application client as described with reference toFIGS.1and2. The data traffic310may be uplink data traffic or downlink data traffic transmitted to or received from a data network (e.g., via a base station105or another network node).

The data traffic310may include one or more peaks305(e.g., bursts) of data, and each peak305may correspond to a time at which a quantity of bits of the data traffic310is greater than a threshold quantity or greater than quantities of bits of the data traffic310at other times (e.g., a maximum quantity of bits of the data traffic310). For example, the users may transmit or receive fewer bits of data during the time periods between the peaks305than at the times at which the peaks305occur. The peaks305may represent a time instance at which a quantity of bits of data is relatively large or a time period (e.g., a peak window), where a quantity of bits of data received within the peak window is relatively large. The peaks305may occur periodically in the example ofFIGS.3A and3B. However, it is to be understood that in some examples, the peaks305may occur quasi-periodically or aperiodically for one or more users, as described with reference toFIG.2.

FIG.3Aillustrates a first communications timeline300-afor communications at a first user and a second user. The communications timeline300-aillustrates a timeline for receiving or transmitting data traffic310-aat a first user (e.g., User1) and data traffic310-bat a second user (e.g., User2). The first and second users may represent examples of UEs115, application clients, or some other wireless devices in communication with the network.

The first user may be scheduled to transmit or receive the data traffic310-a, which may be associated with three or more peaks305, such as the peaks305-a,305-b, and305-c. The second user may be scheduled to transmit or receive the data traffic310-b, which may be associated with three or more peaks305, such as the peaks305-d,305-e, and305-f. The peaks305for each user occur periodically in the example ofFIG.3A. However, it is to be understood that in some examples, the peaks305may occur quasi-periodically or aperiodically for one or more users, as described with reference toFIG.2. Each peak305may correspond to a time at which the respective user is scheduled to transmit or receive a quantity of bits of the data traffic310that is greater than a second quantity of bits of the data traffic310that is transmitted or received at one or more second times. For example, the users may transmit or receive fewer bits of data during the time periods between the peaks305than during the times at which the peaks305occur.

The network may allocate a quantity of time domain resources for each user to serve the data traffic310. A quantity of time domain resources allocated at the time of a peak305(e.g., within a time period before and/or after the time of the peak305) may be greater than a quantity of time domain resources allocated for the data traffic310at other times (e.g., for fewer quantities of bits of the data traffic310). For example, a relatively large quantity of time domain resources may be allocated within a time period to serve the data traffic310-afor the peak305-a. The time period may begin at the peak305-a, before the peak305-a, or after the peak305-a.

In the example ofFIG.3A, the peaks305for the first user may occur within a threshold time of the peaks305for the second user. Although not illustrated inFIG.3, it is to be understood that, in some examples, the peaks305for two or more users may occur at the same time. Peaks305for two or more users that occur at the same time or within a threshold time period may overlap or collide. For example, the peaks305-a,305-b, and305-cof the data traffic310-afor the first user may overlap or collide with the peaks305-d,305-e, and305-fof the data traffic310-bfor the second user in time. Time domain resources that are allocated to serve the data traffic310-aat each of the peaks305-a,305-b, and305-cmay overlap with time domain resources that are allocated to serve the data traffic310-bat each of the peaks305-d,305-e, and305-f, respectively. In such cases, supporting QoS parameters for the data traffic310-aand the data traffic310-bfor both the first and second users may not be feasible due to the relatively large quantity of overlapping time domain resources and corresponding bits of data traffic310.

A network node that supports communications with the first and second users may identify or determine a location of each of the peaks305in the data traffic310-aand310-bbased on communicating the data traffic310-aand310-bwith the first and second users, respectively, or based on signaling received from a logical entity, such as an edge server, as described in more detail with reference toFIGS.4through6. Additionally or alternatively, the network node may determine the location or time of each of the peaks305in the data traffic310-aand310-bbased on an indication received from an application client (e.g., if the data traffic is uplink data traffic), as described in further detail with reference toFIG.7.

Techniques described herein provide for the network node to adjust a time at which one or more peaks305in the data traffic310occur for a subset of users to reduce a total quantity of bits of data traffic that are communicated at a time. For example, the network node may determine a second time that corresponds to a second peak305in the data traffic310for a subset of one or more users that is offset from a first time that corresponds to a first peak305in the data traffic310for one or more other users. In some examples, the second peak305may represent an example of an adjustment of the first peak305. The network node may transmit a message to a data network that indicates the second time, the offset315, the subset of users, or any combination thereof. The data network may adjust the data traffic310(e.g., downlink data) for the subset of users in accordance with the message. Alternatively, the network node may transmit an indication of the second time to the subset of users, and each user may transmit the data traffic310(e.g., uplink data) in accordance with the second time, or the user may forward the indication to an application server, which may adjust the timing of the data traffic310.

FIG.3Billustrates a second communications timeline300-bfor communications at a first user and a second user. The communications timeline300-billustrates a timeline for receiving or transmitting data traffic310-aat the first user (e.g., User1) and data traffic310-cat the second user (e.g., User2) after adjusting a timing of one or more peaks305for the data traffic310-c. The first and second users may represent examples of UEs115, application clients, or some other wireless devices in communication with the network.

The first user may be scheduled to transmit or receive the data traffic310-a, which may represent an example of the data traffic310-adescribed with reference toFIG.3A. The second user may be scheduled to transmit or receive the data traffic310-c, which may be associated with three or more peaks305, such as the peaks305-g,305-h, and305-i. The data traffic310-cmay represent an example of the data traffic310-bdescribed with reference toFIG.3Aafter the network node adjusts a time at which the peaks305occur.

In some examples, a network node in communication with the first and second users may determine an initial time at which each peak305is scheduled based on communicating the data traffic310-aand310-bwith the first and second users, respectively, as described with reference toFIG.3A. For example, the network node may determine, after communicating the data traffic310-aand310-b, that one or more peaks305for each user overlap, and a total quantity of bits communicated at a time exceeds a threshold quantity. Additionally or alternatively, the network node may receive a message that indicates the location of the peaks305. For example, the message may indicate a time at which the peaks305occur and a periodicity of the peaks305.

As described with reference toFIG.2andFIG.3A, the network node may adjust the timing of one or more peaks305for a subset of users based on determining that a total quantity of bits of data traffic310for multiple users exceeds a threshold quantity (e.g., an MDBV). In the example ofFIG.3B, the subset of users may include the second user. The network node may determine a second time for the peaks305of the data traffic310-cthat is offset from the first time at which the peaks305in the data traffic310-aoccur by an offset315. The network node may determine to adjust the peak timing for the second user based on one or more communications parameters associated with the second user, as described in further detail with reference toFIGS.4and5. The network node may determine a value of the offset315based on one or more communications parameters, such as a quantity of users in communication with the network, a periodicity of the peaks305for each user, one or more link conditions associated with each user, or any combination thereof.

The second time may correspond to a time at which one or more of the peaks305-g,305-h, and305-ioccur. Each of the peaks305-g,305-h, and305-imay be associated with a quantity of bits of the data traffic310-cthat are less than a threshold value, such as an MDBV value. As such, the quantity of bits of the data traffic310-cmay satisfy QoS parameters for the second user. The network node may transmit a message to a data network to indicate the offset315(e.g., a peak location offset). The data network may generate the data traffic310-cfor the second user such that the peaks305of the data traffic310-care offset from the peaks305of the data traffic310-afor the first user by the indicated offset315. Alternatively, for uplink data, the network node may transmit an indication of the offset315to the second user, and the second user may transmit the data traffic310-cin accordance with the offset315, or the second user may forward the indication to an application server, and the application server may adjust a timing of the data traffic310-cbased on the offset315.

Although not illustrated inFIGS.3A and3B, in some examples, the peaks305may not occur periodically. In such cases, the network node may determine an offset for each individual peak305or for a subset of peaks305. By offsetting peaks305in data traffic310for a subset of users from peaks305in data traffic310for other users, the network node may reduce a total quantity of bits of data traffic and corresponding time domain resource allocations at a time, which may provide for the network to support QoS parameters for each user.

FIG.4illustrates an example of a process flow400that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The process flow400may implement or be implemented by aspects of the wireless communications systems100and200as described with reference toFIGS.1and2, respectively. For example, the process flow400may implement or be implemented by a RAN405and an edge server410. The RAN405may represent an example of a network or a network node (e.g., a base station105or some other network node) as described with reference toFIGS.1through3. For example, the RAN405may serve or support communications with a set of multiple users (e.g., clients or devices, such as UEs115). The edge server410may represent an example of an edge server210as described with reference toFIG.2. In this case, the edge server410may transmit a message to the RAN405to indicate a location or a time at which one or more peaks in data traffic occur.

In the following description of the process flow400, the operations between the RAN405and the edge server410may be performed in different orders or at different times. Some operations may also be left out of the process flow400, or other operations may be added. Although the RAN405and the edge server410are shown performing the operations of the process flow400, some aspects of some operations may also be performed by one or more other wireless devices.

The edge server410(e.g., a logical entity) may, in some examples, be referred to or represent an example of an AF as described herein. The edge server410may be in communication with a data network, as described with reference toFIG.2. As such, the edge server may identify (e.g., know, determine, or generate) peak locations for data traffic for multiple users. That is, the edge server410may identify one or more times at which a quantity of bits of the data traffic for the multiple users may exceed a threshold quantity. In some examples, the first time may correspond to peaks in data traffic for each of the multiple users, and a total quantity of bits for the multiple users may exceed the threshold value at the first time. The users may represent examples of UEs115as described with reference toFIGS.1through3, or the users may represent examples of application clients or other devices.

At415, the edge server410may transmit a QoS request to the RAN405. The QoS request may represent an example of the QoS request225described with reference toFIG.2. For example, the QoS request may be a message that establishes communications with multiple devices (e.g., via the RAN405). The QoS request may indicate one or more QoS flows for communicating with the multiple users and a set of QOS parameters associated with the multiple users. The QoS parameters may include a PER, a PDB, one or more other QoS parameters or any combination thereof. The QoS request may additionally or alternatively indicate an MDBV for the communications with the multiple users.

In the example ofFIG.4, the QoS request may indicate one or more peak locations for each user. For example, the QoS request may indicate, for each user, a time at which a burst in data traffic occurs, where the burst may correspond to a quantity of bits of the data traffic that is greater than a threshold quantity or greater than other quantities of bits of the data traffic at other times (e.g., a peak in the data traffic). In some examples, the QoS request may indicate a first time that corresponds to one or more peaks in the data traffic for multiple users. A quantity of bits of the data traffic for the multiple users or devices at the first time may be greater than a threshold value (e.g., the MDBV) based on the peaks for multiple users overlapping or colliding in time. In this case, the first time may be associated with a first peak in the data traffic.

The QoS request may indicate, for each peak, a time at which the peak occurs, a quantity of bits of data associated with the peak, a periodicity associated with the peak, an arrival phase associated with the quantity of bits of data, or any combination thereof. In some examples, the time of a peak may correspond to a time that is common to the RAN405and the edge server410. For example, the RAN405may operate according to a first clock configuration and the edge server410may operate according to a second clock configuration that is the same as the first clock configuration (e.g., a common clock). The QoS request may indicate an absolute value of a common time (e.g., T0). An arrival phase may be based on the common time (e.g., the arrival phase may be T0±n(1/peak-periodicity)). As such, the edge server410may determine a location of multiple peaks in the data traffic for the subset of users based on the indication of the time at which a first peak occurs and a periodicity of the peaks. If the peaks do not occur periodically, the RAN405may transmit multiple indications via the QoS response message, or multiple QoS response messages to indicate adjusted times for each peak.

At420, the RAN405may determine a second peak location for a subset of users. That is, the RAN405may determine a second time associated with the first peak in the data traffic that corresponds to a second quantity of bits of the data for the subset of devices (e.g., a peak location), where the second quantity of bits may satisfy QoS parameters for the subset of devices. For example, the second quantity of bits may be less than the MDBV, such that the RAN405may ensure the QoS parameters are satisfied for each user. The second time may be offset from the first time.

The RAN405may determine which devices or users to include in the subset of devices randomly or based on communication parameters associated with the subset of devices. The RAN405may adjust a timing of the data traffic to the second time for the identified or selected subset of users. For example, the RAN405may randomly select a quantity of users, where the quantity may be random or a configured percentage of the multiple users in communication with the RAN405. Additionally or alternatively, the RAN405may include each user in the subset, or the RAN405may include each user that is scheduled with a peak in data traffic at the same time in the subset.

In some examples, the RAN405may determine to adjust the timing of data traffic for the subset of users based on the subset of users having or reporting a link condition that is less than a threshold link condition value. That is, users with a link condition worse than the threshold may be candidates for adjustment (e.g., optimization) of data traffic timing. Users with relatively low link conditions may occupy more resources than users with higher link conditions. As such, peaks in the data traffic for such users may be associated with relatively high resource utilization, which may increase a total resource utilization for all of the users in communication with the RAN405. In such cases, the RAN405may adjust a timing of the data traffic for the subset of users associated with link conditions less than a threshold, and the RAN405may refrain from adjusting a timing of the data traffic for other users. By adjusting a timing of the data traffic for the subset of users associated with relatively poor link conditions, the RAN405may support more efficient resource utilization and improved reliability.

The RAN405may determine a value or magnitude of the offset between the first time and the second time based on one or more communication parameters associated with the subset of devices. The communication parameters may include a quantity of users supported by the RAN405(e.g., in the system), a periodicity of the peaks in data traffic for the users, link conditions associated with each user, or any combination thereof. The offset value may, in some examples, be calculated as a function of the one or more communication parameters to optimize communications and a flow of the data traffic for the multiple users.

At425, the RAN405may transmit a QoS response message (e.g., a signal) that indicates the second time to the edge server410. The QoS response message may represent an example of the QoS response message230described with reference toFIG.2. For example, the QoS response message may indicate a value of the offset between the first time and the second time (e.g., an offset to peak value). In the example ofFIG.4, if the RAN405and the edge server410share a clock configuration, the offset value may indicate a common offset time. Additionally or alternatively, the offset value may be relative to arrival at a network node (e.g., a UPF). That is, the time offset from the first time at which the peak locations occur for multiple users determined by the RAN405may translate into a same offset value at one or more network nodes or logical entities.

The RAN405may transmit the QoS response message to the edge server410via an NEF, and the edge server410may forward the QoS response message to a data network, as described in further detail with reference toFIG.6A. Additionally or alternatively, the RAN405may transmit the QoS response message directly to a data network via an interface between a UPF of the RAN405and the data network, as described in further detail with reference toFIG.6B. The data network may adjust data traffic for the subset of users indicated via the QoS response message based on the indicated second time. For example, the data network may adjust the data traffic such that a peak in the data traffic for the subset of users occurs at the second time that is offset from the first time at which a peak in the data traffic occurs for other users in the system.

At430, the RAN405and the edge server410may communicate the data flow based on the QoS response message. For example, the edge server410may forward the data traffic via one or more QoS flows from the data network to the RAN405. The RAN405may transmit the data traffic to the multiple users. A quantity of bits of the data traffic for the subset of users at the second time indicated via the QoS response message may be greater than a quantity of bits of the data traffic for the subset of users at other times based on the QoS response message and the second time of the peak in the data traffic. That is, a peak in the data traffic for the subset of users may occur at the second time. A peak in data traffic for other users supported by the RAN405may occur at the first time, or some other time that is different than the second time. A total quantity of bits of data traffic communicated by the RAN405at a time may be less than a threshold quantity (e.g., the MDBV) based on the RAN405adjusting the timing. As such, the RAN405may support QoS parameters for each user.

FIG.5illustrates an example of a process flow500that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The process flow500may implement or be implemented by aspects of the wireless communications systems100and200as described with reference toFIGS.1and2, respectively. For example, the process flow500may implement or be implemented by a RAN505and an edge server510. The RAN505may represent an example of a network or a network node (e.g., a base station105or some other network node) as described with reference toFIGS.1through4. The RAN505may serve and/or be in communication with a set of multiple users (e.g., clients or devices, such as UEs115). The edge server510may represent an example of an edge server210as described with reference toFIG.2or an edge server410described with reference toFIG.4.

In the following description of the process flow500, the operations between the RAN505and the edge server510may be performed in different orders or at different times. Some operations may also be left out of the process flow500, or other operations may be added. Although the RAN505and the edge server510are shown performing the operations of the process flow500, some aspects of some operations may also be performed by one or more other wireless devices.

The edge server510(e.g., a logical entity) may, in some examples, be referred to or represent an example of an AF as described herein. The edge server510may be in communication with a data network, as described with reference toFIG.2. As such, the edge server may identify (e.g., know, determine, or generate) peak locations for data traffic for multiple users. That is, the edge server may know one or more times at which a quantity of bits of the data traffic for the multiple users may exceed a threshold quantity. In some examples, the first time may correspond to peaks in data traffic for each of the multiple users, and a total quantity of bits for the multiple users may exceed the threshold value at the first time. The users may represent examples of UEs115as described with reference toFIGS.1through4, or the users may represent examples of application clients or other devices.

At515, the edge server510may transmit a QoS request to the RAN505. The QoS request may represent an example of the QoS request225described with reference toFIG.2. For example, the QoS request may be a message that establishes communications with multiple devices (e.g., via the RAN505). The QoS request may indicate one or more QoS flows for communicating with the multiple users and a set of QoS parameters associated with the multiple users. The QoS parameters may include a PER, a PDB, one or more other QoS parameters or any combination thereof. The QoS request may additionally or alternatively indicate an MDBV for the communications with the multiple users.

At520, the RAN505may process the QoS request and determine an initial admission. At525, the RAN505may transmit a QoS response message to the edge server510in response to the QoS request. The QoS response message may initiate communications according to the QoS parameters indicated via the QoS request. At530, the edge server510and the RAN505may communicate data traffic in accordance with the set of QoS parameters indicated by the QoS request. For example, the edge server510may forward data traffic to the RAN505, and the RAN505may communicate the data traffic with one or more users.

At535, the RAN505may estimate or infer a location of one or more peaks in the data traffic. For example, the RAN505may identify, based on communicating the data at530, a first time at which a quantity of bits of the data traffic exceeds a threshold quantity (e.g., the MDBV). The first time may correspond to a peak in the data traffic for multiple users. The RAN505may not be able to support the QoS parameters for each of the users based on the quantity of bits exceeding the threshold value at the first time.

At540, the RAN505may determine a second peak location for a subset of users. That is, the RAN505may determine a second time associated with the peak in the data traffic that corresponds to a second quantity of bits of the data for the subset of devices (e.g., a peak location), where the second quantity of bits may satisfy QoS parameters for the subset of devices. For example, the second quantity of bits may be less than the MDBV, such that the RAN505may ensure the QoS parameters are satisfied for each user. The second time may be offset from the first time.

The RAN505may determine which devices or users to include in the subset of devices randomly or based on communication parameters associated with the subset of devices. The RAN505may adjust a timing of the data traffic to the second time for the identified or selected subset of users. For example, the RAN505may randomly select a quantity of users, where the quantity may be random or a configured percentage of the multiple users in communication with the RAN505. Additionally or alternatively, the RAN505may include each user in the subset, or the RAN505may include each user that is scheduled with a peak in data traffic at the same time in the subset. In some examples, the RAN505may determine to adjust the timing of data traffic for the subset of users based on the subset of users having or reporting a link condition that is less than a threshold link condition value, as described with reference toFIG.4.

The RAN505may determine a value or magnitude of the offset between the first time and the second time based on one or more communication parameters. The communication parameters may include a quantity of users supported by the RAN505(e.g., in the system), a periodicity of the peaks in data traffic for the users, link conditions associated with each user, or any combination thereof. The offset value may, in some examples, be calculated as a function of the one or more communication parameters to optimize communications and a flow of the data traffic for the multiple users.

At545, the RAN505may transmit a second QoS response message (e.g., a signal) to the edge server510to indicate a value of the offset between the first time and the second time (e.g., an offset to peak value). In the example ofFIG.5, if the RAN505and the edge server510share a clock configuration, the offset value may indicate a common offset time. Additionally or alternatively, if the RAN505operates according to a first clock and the edge server510operates according to a second clock that is different than the first clock, the offset value may be relative to arrival at a network node (e.g., a UPF). That is, the offset from the first time at which the peak locations occur for multiple users determined by the RAN505may translate into a same offset value at one or more network nodes or logical entities, including the edge server510.

In some examples, a first speed of the first clock for the RAN505may be different than a second speed of the second clock for the edge server510. That is, the clocks may tick at different rates. In some examples, the offset between clock rates may be referred to as drift. In such cases, a timing of the peaks for the subset of users may drift over time. As such, the RAN505may transmit a set of multiple QoS response messages periodically (e.g., during communications) to indicate an updated offset value. Each QoS response message may indicate an offset from a respective first time associated with peaks in the data traffic for a respective subset of devices. Each QoS response message may indicate a respective offset for the same subset of devices or a different subset of devices. The periodic indications of the offset values may provide for improved alignment between the RAN505and the edge server510.

The RAN505may transmit the QoS response message to the edge server510via an NEF, and the edge server510may forward the QoS response message to a data network, as described in further detail with reference toFIG.6A. Additionally or alternatively, the RAN505may transmit the QoS response message directly to a data network via an interface between a UPF of the RAN505and the data network, as described in further detail with reference toFIG.6B. The data network may adjust data traffic for the subset of users indicated via the QoS response message based on the indicated second time. For example, the data network may adjust the data traffic such that a peak in the data traffic for the subset of users occurs at the second time that is offset from the first time at which a peak in the data traffic occurs for other users in the system. In the example ofFIG.5, the data network may adjust the timing after admission at520and transmission of a portion of the data traffic. The QoS parameters may not be met for each user for the portion of the data traffic, and the QoS parameters may be met for each user after the RAN505transmits the second QoS response that indicates the offset.

At550, the RAN505and the edge server510may communicate the data flow based on the QoS response message and the second time associated with the peak. For example, the edge server510may forward the data traffic via one or more QoS flows from the data network to the RAN505. The RAN505may transmit the data traffic to the multiple users. A quantity of bits of the data traffic for the subset of users at the second time indicated via the QoS response message may be greater than a quantity of bits of the data traffic for the subset of users at other times based on the QoS response message. That is, a peak in the data traffic for the subset of users may occur at the second time. A peak in data traffic for other users supported by the RAN505may occur at the first time, or some other time that is different than the second time. A total quantity of bits of data traffic communicated by the RAN505at a time may be less than a threshold quantity (e.g., the MDBV) based on the RAN505adjusting the timing. As such, the RAN505may support QoS parameters for each user.

FIGS.6A and6Billustrate examples of signaling paths600that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The signaling paths600-aand600-bmay implement or be implemented by aspects of the wireless communications systems100and200as described with reference toFIGS.1and2. For example, the signaling paths600may illustrate paths for a RAN605to receive a QoS request message645and transmit a QoS response message640. The RAN605may represent an example of a network node as described with reference toFIGS.1through5. The signaling paths600may include one or more other network nodes or logical entities, which may represent examples of corresponding logical entities as described with reference toFIGS.1through5.

The QoS request message645may represent an example of a QoS request message described with reference toFIGS.1through5. For example, the QoS request message645may establish communications with multiple users via the RAN605. The QoS request message645may indicate one or more QoS flows, an MDBV, one or more QoS parameters for each user, or any combination thereof. In some examples, the QoS request message645may indicate one or more peak locations. The one or more peak locations may correspond to a time at which one or more peaks in data traffic occur for one or more users. The QoS request message645may indicate a common time associated with each peak location if the RAN605and the AF610share a common clock configuration, as described with reference toFIG.4.

The QoS response message640may represent an example of a QoS response message described with reference toFIGS.1through5. For example, the QoS response message640may be transmitted in response to the QoS request message645and may indicate an offset value. The offset value may correspond to an offset to peak parameter as described with reference toFIGS.1through5. The QoS response message may indicate a time, an arrival phase, a periodicity, or any combination thereof of an adjusted peak in data traffic for a subset of users. The QoS response message may additionally indicate the subset of users. The RAN605may receive and transmit the QoS request message645and the QoS response message640, respectively, via an interface. The interface may be an NEF interface, or some other interface.

FIG.6Aillustrates an example of a signaling path600-abetween the RAN605and the AF610. The RAN605may represent an example of a network or a network node as described with reference toFIGS.1through5. The AF610may represent an example of a logical network entity, such as an edge server, as described with reference toFIGS.1through5.

In the example ofFIG.6A, the RAN605may receive a QoS request message645from the AF610via an NEF interface between the AF610and the RAN605. The NEF may correspond to a signal path (e.g., a QoS notification path) between multiple logical entities, such as the AMF/SMF615and the policy and charging control (PCC)620. The AMF/SMF615may include one or both of an AMF entity and an SMF entity. The AF610may transmit the QoS request message645(e.g., including the indication of the peak locations) to the PCC620. The PCC620may transmit the QoS request message645to the AMF/SMF615. The AMF/SMF615may transmit the QoS request message645to the RAN605.

The RAN605may transmit the QoS response message640to the AF610via the NEF interface. For example, the RAN605may transmit the QoS response message640to the AMF/SMF615. The AMF/SMF615may forward the QoS response message640to the PCC620. The PCC620may forward the QoS response message640to the AF610. In some examples, the AF610may forward the QoS response message640, or an indication of the offset parameter conveyed via the QoS response message640to a data network635. The data network635may adjust data traffic for a subset of users based on the QoS response message640.

FIG.6Billustrates an example of a signaling path600-bbetween the RAN605and a data network635. In the example ofFIG.6B, the RAN605may transmit the QoS response message640to the data network635via an interface between the RAN605, the UPF630of the RAN605, and the data network635. That is, the RAN605may transmit an indication of an offset value directly to the data network635without relaying the indication via the AF610. For example, the RAN605may transmit the QoS response message640to a UPF630. The UPF630may forward the QoS response message640to the data network635.

In some examples, the signaling path600-bbetween the RAN605and the data network635may be referred to as a data path for the data network635to transmit data to the RAN605. The data may be transmitted from the data network635to the UPF630to the RAN605. In the example ofFIG.6B, the indication of an offset value may be transmitted (e.g., “piggy-backed”) along the data path. By transmitting the indication of the offset value to the data network635via the data path, the RAN605may support more efficient signaling of the offset value with reduced overhead as compared with forwarding the signaling to the AF610via multiple logical entities.

FIG.7illustrates an example of a flow diagram700that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The flow diagram700may implement or be implemented by aspects of the wireless communications systems100and200as described with reference toFIGS.1and2. For example, the flow diagram700illustrates signaling between an application client710, a modem715, and a RAN705. The RAN705may represent an example of a RAN or other network node as described with reference toFIGS.1through6. The modem715may represent an example of a UE115or some other wireless device, as described with reference toFIGS.1through6. The application client710may represent an example of an application, a controller, or some other client that runs an application based on signaling received from the RAN705. In some examples, the application client710may represent an application that is executed by the modem715. The application client710may communicate with the modem715via an API. The modem715may relay communications between the application client and the RAN705via the API.

The application client may transmit uplink data traffic to the RAN705and receive downlink data traffic from the RAN705. The uplink and downlink data traffic may, in some examples, be transmitted in periodic or quasi-periodic bursts of data (e.g., data traffic peaks), as described with reference toFIGS.1through6. If a peak of the data traffic communicated by the application client710overlaps or collides with one or more other peaks of data traffic communicated by one or more other users of the RAN705, a quantity of bits of the data that are transmitted at a time may exceed a threshold value (e.g., an MDBV), which may provide for increased latency and reduced reliability of the communications. For example, the users, the RAN705, or both may not be able to meet one or more QoS parameters for the data traffic if a quantity of bits exceeds the threshold value.

In some examples, the application client710may identify a location of one or more initial peaks in data traffic communicated by the application client710. For example, the application client may identify a first time at which a quantity of bits of the uplink data traffic exceeds a threshold quantity. The application client710may identify the first time based on communicating the data traffic with the RAN705, based on a configuration of the uplink data at the application client710, or based on an indication of the first time received from an application server. The application client710may transmit a message to the modem715that indicates the first time (e.g., a peak location), one or more other times associated with other peaks in the data traffic, or both. If the uplink data traffic is transmitted periodically, the application client710may indicate a first time and a periodicity associated with the first time.

The modem715(e.g., a UE115) may identify the first time associated with the first peak in the data traffic that corresponds to a first quantity of bits for the application client710exceeding a threshold. The modem715may determine the first time based on the message received from the application client710(e.g., the application server) via the API, or based on communicating the data with the application client710via the API. The API may be an interface between the application client710and the RAN705that includes the modem715. The modem715may transmit a first signal that indicates the first time for the application client710to the RAN705. In some examples, the application client710, the modem715, the RAN705, or any combination thereof may share a clock configuration. In such cases, the message may indicate a time that is common to each of the application client710, the modem715, and the RAN705.

The RAN705may receive the indication of the first time, one or more other indications of times associated with relatively high quantities of bits of data for one or more other users, or both. The RAN705may determine a second time associated with an adjusted peak in data that corresponds to a quantity of bits of the data for a subset of one or more users. The quantity of bits of the data at the second time may satisfy one or more QoS parameters for the subset of users. The subset of users may include the application client710. The second time may be offset from the first time associated with the peak in data traffic by an offset value. The RAN705may determine the subset of users, the offset value, or both based on one or more communication parameters associated with the subset of users, as described with reference toFIGS.2through5.

The RAN705may transmit a second signal to the modem715that indicates the offset value. The second signal may thus indicate the second time associated with the peak in the data traffic for the application client. The modem715may forward the indication of the offset to the application client710via the API. The application client710, the application server in communication with the application client710, or both may adjust the data traffic based on the message and communicate the data with the modem715and the RAN705accordingly. For example, the application client710may transmit uplink data such that a quantity of bits as the second time that is offset from the first time by the indicated offset value is greater than a second quantity of bits of the uplink data traffic at other times. That is, the uplink data traffic may have a peak at the second time. Additionally or alternatively, the application client710may receive downlink data in accordance with the second time associated with the adjusted peak in the data traffic.

By offsetting the peak in the data traffic for the application client710(e.g., and one or more other application clients or other users), the RAN705may reduce a total quantity of data traffic at the RAN705to be less than a threshold quantity. Such techniques may provide for the RAN705to satisfy one or more QoS parameters for each user, which may improve communication reliability and reduce latency.

In some examples, the application client710may support downlink communications. In such cases, the application client710may determine a time at which one or more peaks in the downlink data traffic occur based on receiving the downlink traffic or based on an indication received by the application client. For example, the application client710may be in communication with an application server, and the application server may transmit a signal, such as a QoS request message, to the application client710to indicate the timing for the one or more peaks in the downlink data traffic. The signal and the indication of the peaks may represent examples of the QoS request message described with reference toFIG.4.

The application client710may forward the indication of the peaks to the RAN705, and the RAN705may determine an offset value for the application client710, as described with reference toFIGS.2through5. The RAN may transmit the indication of the offset value to the application client710via the modem715. Additionally or alternatively, the application client710may determine the offset value based on one or more communication parameters. The application client may transmit a message, such as a QoS response message, to the application server to indicate the offset value. The application server may communicate downlink data with the application client in accordance with the indicated offset value. For example, a peak in the downlink data traffic may occur at the second time that is offset from the first time by the indicated offset value.

FIG.8shows a block diagram800of a device805that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The device805may be an example of aspects of a Network Entity-ALPHA as described herein. The device805may include a receiver810, a transmitter815, and a communications manager820. The device805may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver810may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to peak traffic position adjustment for wireless communication). Information may be passed on to other components of the device805. The receiver810may utilize a single antenna or a set of multiple antennas.

The communications manager820, the receiver810, the transmitter815, or various combinations thereof or various components thereof may be examples of means for performing various aspects of peak traffic position adjustment for wireless communication as described herein. For example, the communications manager820, the receiver810, the transmitter815, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager820may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver810, the transmitter815, or both. For example, the communications manager820may receive information from the receiver810, send information to the transmitter815, or be integrated in combination with the receiver810, the transmitter815, or both to receive information, transmit information, or perform various other operations as described herein.

The communications manager820may support wireless communication at a network node in accordance with examples as disclosed herein. For example, the communications manager820may be configured as or otherwise support a means for determining a first time location for a peak in data traffic for a set of multiple devices in communication with a communications network including the network node. The communications manager820may be configured as or otherwise support a means for transmitting a signal that indicates a second time location for the peak in the data traffic for a subset of devices of the set of multiple devices based on a threshold for an overall peak in the data traffic for the set of multiple devices. The communications manager820may be configured as or otherwise support a means for communicating data including the data traffic with the subset of devices based on the signal indicating the second time location.

By including or configuring the communications manager820in accordance with examples as described herein, the device805(e.g., a processor controlling or otherwise coupled to the receiver810, the transmitter815, the communications manager820, or a combination thereof) may support techniques for reduced processing, reduced overhead and more efficient utilization of communication resources. By adjusting a timing of a peak in data traffic for one or more users, the device805may reduce a total quantity of bits of data communicated at a time, which may support efficient utilization of communication resources and reduced processing and overhead by the processor of the device805. The processor may support communication of the data in accordance with QoS parameters for each user, which may improve communication reliability.

FIG.9shows a block diagram900of a device905that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The device905may be an example of aspects of a device805or a Network Entity-ALPHA115as described herein. The device905may include a receiver910, a transmitter915, and a communications manager920. The device905may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The device905, or various components thereof, may be an example of means for performing various aspects of peak traffic position adjustment for wireless communication as described herein. For example, the communications manager920may include a peak timing component925a communications component930, or any combination thereof. The communications manager920may be an example of aspects of a communications manager820as described herein. In some examples, the communications manager920, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver910, the transmitter915, or both. For example, the communications manager920may receive information from the receiver910, send information to the transmitter915, or be integrated in combination with the receiver910, the transmitter915, or both to receive information, transmit information, or perform various other operations as described herein.

The communications manager920may support wireless communication at a network node in accordance with examples as disclosed herein. The peak timing component925may be configured as or otherwise support a means for determining a first time location for a peak in data traffic for a set of multiple devices in communication with a communications network including the network node. The peak timing component925may be configured as or otherwise support a means for transmitting a signal that indicates a second time location for the peak in the data traffic for a subset of devices of the set of multiple devices based on a threshold for an overall peak in the data traffic for the set of multiple devices. The communications component930may be configured as or otherwise support a means for communicating data including the data traffic with the subset of devices based on the signal indicating the second time location.

FIG.10shows a block diagram1000of a communications manager1020that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The communications manager1020may be an example of aspects of a communications manager820, a communications manager920, or both, as described herein. The communications manager1020, or various components thereof, may be an example of means for performing various aspects of peak traffic position adjustment for wireless communication as described herein. For example, the communications manager1020may include a peak timing component1025, a communications component1030, a QoS component1035, a QoS response component1040, a signal transmitter1045, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The communications manager1020may support wireless communication at a network node in accordance with examples as disclosed herein. The peak timing component1025may be configured as or otherwise support a means for determining a first time location for a peak in data traffic for a set of multiple devices in communication with a communications network including the network node. In some examples, the peak timing component1025may be configured as or otherwise support a means for transmitting a signal that indicates a second time location for the peak in the data traffic for a subset of devices of the set of multiple devices based on a threshold for an overall peak in the data traffic for the set of multiple devices. The communications component1030may be configured as or otherwise support a means for communicating data including the data traffic with the subset of devices based on the signal indicating the second time location.

In some examples, to support determining the first time location, the QoS component1035may be configured as or otherwise support a means for receiving a message that establishes communications with the set of multiple devices and that indicates a first set of QOS parameters associated with the set of multiple devices. In some examples, to support determining the first time location, the QoS component1035may be configured as or otherwise support a means for communicating the data with the set of multiple devices in accordance with the first set of QoS parameters. In some examples, to support determining the first time location, the peak timing component1025may be configured as or otherwise support a means for estimating the first time location based on communicating the data.

In some examples, to support determining the first time location, the communications component1030may be configured as or otherwise support a means for establishing communications with the set of multiple devices according to a first set of QoS parameters. In some examples, to support determining the first time location, the peak timing component1025may be configured as or otherwise support a means for receiving a message that indicates the first time location.

In some examples, to support receiving the message, the QoS component1035may be configured as or otherwise support a means for receiving a QoS request from an edge server that operates according to a first clock configuration that is the same as a second clock configuration for the network node. In some examples, the message indicates the first time location, a first quantity of bits of the data at the first time location, a periodicity associated with the first quantity of bits of the data, an arrival phase associated with the first quantity of bits of the data, or any combination thereof. In some examples, the first time location corresponds to a time common to the network node and a device that transmits the message.

In some examples, to support transmitting the signal, the QoS response component1040may be configured as or otherwise support a means for transmitting a QoS response message that indicates a value of an offset between the first time location and the second time location. In some examples, the offset between the first time location and the second time location is based on communications parameters associated with the subset of devices.

In some examples, to support transmitting the signal, the signal transmitter1045may be configured as or otherwise support a means for transmitting the signal to an edge server via an NEF interface. In some examples, to support transmitting the signal, the signal transmitter1045may be configured as or otherwise support a means for transmitting the signal to a data network via an interface between a UPF of the network node and the data network.

In some examples, the peak timing component1025may be configured as or otherwise support a means for receiving an indication of the first time location from a UE. In some examples, the signal transmitter1045may be configured as or otherwise support a means for transmitting the signal to the UE based on determining the second time location.

In some examples, to support transmitting the signal, the signal transmitter1045may be configured as or otherwise support a means for transmitting a set of signals including at least the signal periodically, where each signal of the set of signals indicates a respective offset from the first time location for a respective subset of devices of the set of multiple devices.

In some examples, to support communicating the data, the communications component1030may be configured as or otherwise support a means for receiving the data from a data network in accordance with the second time location. In some examples, to support communicating the data, the communications component1030may be configured as or otherwise support a means for forwarding the data from the data network to the subset of devices in accordance with the second time location, the data including downlink data.

In some examples, to support communicating the data, the communications component1030may be configured as or otherwise support a means for receiving the data from a UE via an API in accordance with the second time location, the data including uplink data, where the UE is in communication with the subset of devices.

In some examples, the threshold for the overall peak in the data traffic corresponds to a threshold quantity of bits of the data traffic for the set of multiple devices. In some examples, the peak in the data traffic at the first time location exceeds the threshold. In some examples, the peak in the data traffic at the second time location is less than the threshold. In some examples, the data traffic includes uplink data, downlink data, or both associated with intra-coded frames, predicted frames, or both.

FIG.11shows a diagram of a system1100including a device1105that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The device1105may be an example of or include the components of a device805, a device905, or a Network Entity-ALPHA as described herein. The device1105may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager1120, a network communications manager1110, a transceiver1115, an antenna1125, a memory1130, code1135, a processor1140, and an inter-station communications manager1145. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus1150).

The network communications manager1110may manage communications with a core network130(e.g., via one or more wired backhaul links). For example, the network communications manager1110may manage the transfer of data communications for client devices, such as one or more UEs115.

The memory1130may include RAM and ROM. The memory1130may store computer-readable, computer-executable code1135including instructions that, when executed by the processor1140, cause the device1105to perform various functions described herein. The code1135may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code1135may not be directly executable by the processor1140but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory1130may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor1140may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor1140may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor1140. The processor1140may be configured to execute computer-readable instructions stored in a memory (e.g., the memory1130) to cause the device1105to perform various functions (e.g., functions or tasks supporting peak traffic position adjustment for wireless communication). For example, the device1105or a component of the device1105may include a processor1140and memory1130coupled to the processor1140, the processor1140and memory1130configured to perform various functions described herein.

The communications manager1120may support wireless communication at a network node in accordance with examples as disclosed herein. For example, the communications manager1120may be configured as or otherwise support a means for determining a first time location for a peak in data traffic for a set of multiple devices in communication with a communications network including the network node. The communications manager1120may be configured as or otherwise support a means for transmitting a signal that indicates a second time location for the peak in the data traffic for a subset of devices of the set of multiple devices based on a threshold for an overall peak in the data traffic for the set of multiple devices. The communications manager1120may be configured as or otherwise support a means for communicating data including the data traffic with the subset of devices based on the signal indicating the second time location.

By including or configuring the communications manager1120in accordance with examples as described herein, the device1105may support techniques for improved communication reliability, reduced latency, more efficient utilization of communication resources, improved coordination between devices, and improved utilization of processing capability.

In some examples, the communications manager1120may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver1115, the one or more antennas1125, or any combination thereof. Although the communications manager1120is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager1120may be supported by or performed by the processor1140, the memory1130, the code1135, or any combination thereof. For example, the code1135may include instructions executable by the processor1140to cause the device1105to perform various aspects of peak traffic position adjustment for wireless communication as described herein, or the processor1140and the memory1130may be otherwise configured to perform or support such operations.

The receiver1210may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to peak traffic position adjustment for wireless communication). Information may be passed on to other components of the device1205. The receiver1210may utilize a single antenna or a set of multiple antennas.

The transmitter1215may provide a means for transmitting signals generated by other components of the device1205. For example, the transmitter1215may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to peak traffic position adjustment for wireless communication). In some examples, the transmitter1215may be co-located with a receiver1210in a transceiver module. The transmitter1215may utilize a single antenna or a set of multiple antennas.

The communications manager1220, the receiver1210, the transmitter1215, or various combinations thereof or various components thereof may be examples of means for performing various aspects of peak traffic position adjustment for wireless communication as described herein. For example, the communications manager1220, the receiver1210, the transmitter1215, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager1220may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver1210, the transmitter1215, or both. For example, the communications manager1220may receive information from the receiver1210, send information to the transmitter1215, or be integrated in combination with the receiver1210, the transmitter1215, or both to receive information, transmit information, or perform various other operations as described herein.

The communications manager1220may support wireless communication at a UE in accordance with examples as disclosed herein. For example, the communications manager1220may be configured as or otherwise support a means for transmitting a first signal that indicates a first time location for a peak in data traffic for the UE. The communications manager1220may be configured as or otherwise support a means for receiving a second signal that indicates a second time location for the peak in the data traffic based on a threshold for an overall peak in data traffic for the UE. The communications manager1220may be configured as or otherwise support a means for communicating data including the data traffic based on the second signal indicating the second time location.

By including or configuring the communications manager1220in accordance with examples as described herein, the device1205(e.g., a processor controlling or otherwise coupled to the receiver1210, the transmitter1215, the communications manager1220, or a combination thereof) may support techniques for reduced processing, reduced overhead and more efficient utilization of communication resources. By adjusting a timing of a peak in data traffic, the device1205may reduce a total quantity of bits of data communicated at a time, which may support efficient utilization of communication resources and reduced processing and overhead by the processor of the device1205. The processor may support communication of the data in accordance with QoS parameters for the device1205, which may improve communication reliability.

FIG.13shows a block diagram1300of a device1305that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The device1305may be an example of aspects of a device1205or a UE115as described herein. The device1305may include a receiver1310, a transmitter1315, and a communications manager1320. The device1305may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver1310may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to peak traffic position adjustment for wireless communication). Information may be passed on to other components of the device1305. The receiver1310may utilize a single antenna or a set of multiple antennas.

The transmitter1315may provide a means for transmitting signals generated by other components of the device1305. For example, the transmitter1315may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to peak traffic position adjustment for wireless communication). In some examples, the transmitter1315may be co-located with a receiver1310in a transceiver module. The transmitter1315may utilize a single antenna or a set of multiple antennas.

The device1305, or various components thereof, may be an example of means for performing various aspects of peak traffic position adjustment for wireless communication as described herein. For example, the communications manager1320may include a peak timing component1325, a signal receiver1330, a communications component1335, or any combination thereof. The communications manager1320may be an example of aspects of a communications manager1220as described herein. In some examples, the communications manager1320, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver1310, the transmitter1315, or both. For example, the communications manager1320may receive information from the receiver1310, send information to the transmitter1315, or be integrated in combination with the receiver1310, the transmitter1315, or both to receive information, transmit information, or perform various other operations as described herein.

The communications manager1320may support wireless communication at a UE in accordance with examples as disclosed herein. The peak timing component1325may be configured as or otherwise support a means for transmitting a first signal that indicates a first time location for a peak in data traffic for the UE. The signal receiver1330may be configured as or otherwise support a means for receiving a second signal that indicates a second time location for the peak in the data traffic based on a threshold for an overall peak in data traffic for the UE. The communications component1335may be configured as or otherwise support a means for communicating data including the data traffic based on the second signal indicating the second time location.

FIG.14shows a block diagram1400of a communications manager1420that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The communications manager1420may be an example of aspects of a communications manager1220, a communications manager1320, or both, as described herein. The communications manager1420, or various components thereof, may be an example of means for performing various aspects of peak traffic position adjustment for wireless communication as described herein. For example, the communications manager1420may include a peak timing component1425, a signal receiver1430, a communications component1435, a signal transmitter1440, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The communications manager1420may support wireless communication at a UE in accordance with examples as disclosed herein. The peak timing component1425may be configured as or otherwise support a means for transmitting a first signal that indicates a first time location for a peak in data traffic for the UE. The signal receiver1430may be configured as or otherwise support a means for receiving a second signal that indicates a second time location for the peak in the data traffic based on a threshold for an overall peak in data traffic for the UE. The communications component1435may be configured as or otherwise support a means for communicating data including the data traffic based on the second signal indicating the second time location.

In some examples, to support determining the first time location, the communications component1435may be configured as or otherwise support a means for communicating the data with a device via a cross-layer API. In some examples, to support determining the first time location, the peak timing component1425may be configured as or otherwise support a means for estimating the first time location based on communicating the data.

In some examples, to support determining the first time location, the communications component1435may be configured as or otherwise support a means for establishing communications between the UE and a device. In some examples, to support determining the first time location, the signal receiver1430may be configured as or otherwise support a means for receiving, from the device via a cross-layer API, a message that indicates the first time location.

In some examples, the signal transmitter1440may be configured as or otherwise support a means for transmitting, to a device via a cross-layer API, a third signal that indicates the second time location, where the communicating is based on the third signal. In some examples, an offset between the first time location and the second time location is based on communications parameters associated with a device in communication with the UE. In some examples, the data includes uplink data, downlink data, or both.

FIG.15shows a diagram of a system1500including a device1505that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The device1505may be an example of or include the components of a device1205, a device1305, or a UE115as described herein. The device1505may communicate wirelessly with one or more base stations105, UEs115, or any combination thereof. The device1505may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager1520, an input/output (I/O) controller1510, a transceiver1515, an antenna1525, a memory1530, code1535, and a processor1540. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus1545).

The I/O controller1510may manage input and output signals for the device1505. The I/O controller1510may also manage peripherals not integrated into the device1505. In some cases, the I/O controller1510may represent a physical connection or port to an external peripheral. In some cases, the I/O controller1510may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I/O controller1510may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller1510may be implemented as part of a processor, such as the processor1540. In some cases, a user may interact with the device1505via the I/O controller1510or via hardware components controlled by the I/O controller1510.

In some cases, the device1505may include a single antenna1525. However, in some other cases, the device1505may have more than one antenna1525, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver1515may communicate bi-directionally, via the one or more antennas1525, wired, or wireless links as described herein. For example, the transceiver1515may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver1515may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas1525for transmission, and to demodulate packets received from the one or more antennas1525. The transceiver1515, or the transceiver1515and one or more antennas1525, may be an example of a transmitter1215, a transmitter1315, a receiver1210, a receiver1310, or any combination thereof or component thereof, as described herein.

The memory1530may include random access memory (RAM) and read-only memory (ROM). The memory1530may store computer-readable, computer-executable code1535including instructions that, when executed by the processor1540, cause the device1505to perform various functions described herein. The code1535may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code1535may not be directly executable by the processor1540but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory1530may contain, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor1540may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor1540may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor1540. The processor1540may be configured to execute computer-readable instructions stored in a memory (e.g., the memory1530) to cause the device1505to perform various functions (e.g., functions or tasks supporting peak traffic position adjustment for wireless communication). For example, the device1505or a component of the device1505may include a processor1540and memory1530coupled to the processor1540, the processor1540and memory1530configured to perform various functions described herein.

The communications manager1520may support wireless communication at a UE in accordance with examples as disclosed herein. For example, the communications manager1520may be configured as or otherwise support a means for transmitting a first signal that indicates a first time location for a peak in data traffic for the UE. The communications manager1520may be configured as or otherwise support a means for receiving a second signal that indicates a second time location for the peak in the data traffic based on a threshold for an overall peak in data traffic for the UE. The communications manager1520may be configured as or otherwise support a means for communicating data including the data traffic based on the second signal indicating the second time location.

In some examples, the communications manager1520may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver1515, the one or more antennas1525, or any combination thereof. Although the communications manager1520is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager1520may be supported by or performed by the processor1540, the memory1530, the code1535, or any combination thereof. For example, the code1535may include instructions executable by the processor1540to cause the device1505to perform various aspects of peak traffic position adjustment for wireless communication as described herein, or the processor1540and the memory1530may be otherwise configured to perform or support such operations.

FIG.16shows a flowchart illustrating a method1600that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The operations of the method1600may be implemented by a Network Entity-ALPHA or its components as described herein. For example, the operations of the method1600may be performed by a Network Entity-ALPHA as described with reference toFIGS.1through11. In some examples, a Network Entity-ALPHA may execute a set of instructions to control the functional elements of the Network Entity-ALPHA to perform the described functions. Additionally or alternatively, the Network Entity-ALPHA may perform aspects of the described functions using special-purpose hardware.

At1605, the method may include determining a first time location for a peak in data traffic for a set of multiple devices in communication with a communications network including the network node. The operations of1605may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1605may be performed by a peak timing component1025as described with reference toFIG.10.

At1610, the method may include transmitting a signal that indicates a second time location for the peak in the data traffic for a subset of devices of the set of multiple devices based on a threshold for an overall peak in the data traffic for the set of multiple devices. The operations of1610may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1610may be performed by a peak timing component1025as described with reference toFIG.10.

At1615, the method may include communicating data including the data traffic with the subset of devices based on the signal indicating the second time location. The operations of1615may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1615may be performed by a communications component1030as described with reference toFIG.10.

FIG.17shows a flowchart illustrating a method1700that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The operations of the method1700may be implemented by a Network Entity-ALPHA or its components as described herein. For example, the operations of the method1700may be performed by a Network Entity-ALPHA as described with reference toFIGS.1through11. In some examples, a Network Entity-ALPHA may execute a set of instructions to control the functional elements of the Network Entity-ALPHA to perform the described functions. Additionally or alternatively, the Network Entity-ALPHA may perform aspects of the described functions using special-purpose hardware.

At1705, the method may include receiving a message that establishes communications with the set of multiple devices and that indicates a first set of QoS parameters associated with the set of multiple devices. The operations of1705may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1705may be performed by a QoS component1035as described with reference toFIG.10.

At1710, the method may include communicating the data with the set of multiple devices in accordance with the first set of QoS parameters. The operations of1710may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1710may be performed by a QoS component1035as described with reference toFIG.10.

At1715, the method may include estimating a first time location for a peak in data traffic for a set of multiple devices in communication with a communications network including the network node based on communicating the data. The operations of1715may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1715may be performed by a peak timing component1025as described with reference toFIG.10.

At1720, the method may include transmitting a signal that indicates a second time location for the peak in the data traffic for a subset of devices of the set of multiple devices based on a threshold for an overall peak in the data traffic for the set of multiple devices. The operations of1720may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1720may be performed by a peak timing component1025as described with reference toFIG.10.

At1725, the method may include communicating data including the data traffic with the subset of devices based on the signal indicating the second time location. The operations of1725may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1725may be performed by a communications component1030as described with reference toFIG.10.

FIG.18shows a flowchart illustrating a method1800that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The operations of the method1800may be implemented by a Network Entity-ALPHA or its components as described herein. For example, the operations of the method1800may be performed by a Network Entity-ALPHA as described with reference toFIGS.1through11. In some examples, a Network Entity-ALPHA may execute a set of instructions to control the functional elements of the Network Entity-ALPHA to perform the described functions. Additionally or alternatively, the Network Entity-ALPHA may perform aspects of the described functions using special-purpose hardware.

At1805, the method may include establishing communications with the set of multiple devices according to a first set of QoS parameters. The operations of1805may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1805may be performed by a communications component1030as described with reference toFIG.10.

At1810, the method may include receiving a message that indicates a first time location for a peak in data traffic for a set of multiple devices in communication with a communications network including the network node. The operations of1810may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1810may be performed by a peak timing component1025as described with reference toFIG.10.

At1815, the method may include determining the first time location based on the message. The operations of1815may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1815may be performed by a peak timing component1025as described with reference toFIG.10.

At1820, the method may include transmitting a signal that indicates a second time location for the peak in the data traffic for a subset of devices of the set of multiple devices based on a threshold for an overall peak in the data traffic for the set of multiple devices. The operations of1820may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1820may be performed by a peak timing component1025as described with reference toFIG.10.

At1825, the method may include communicating data including the data traffic with the subset of devices based on the signal indicating the second time location. The operations of1825may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1825may be performed by a communications component1030as described with reference toFIG.10.

FIG.19shows a flowchart illustrating a method1900that supports peak traffic position adjustment for wireless communication in accordance with aspects of the present disclosure. The operations of the method1900may be implemented by a Network Entity-ALPHA or its components as described herein. For example, the operations of the method1900may be performed by a Network Entity-ALPHA as described with reference toFIGS.1through11. In some examples, a Network Entity-ALPHA may execute a set of instructions to control the functional elements of the Network Entity-ALPHA to perform the described functions. Additionally or alternatively, the Network Entity-ALPHA may perform aspects of the described functions using special-purpose hardware.

At1905, the method may include determining a first time location for a peak in data traffic for a set of multiple devices in communication with a communications network including the network node. The operations of1905may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1905may be performed by a peak timing component1025as described with reference toFIG.10.

At1910, the method may include transmitting a QoS response message that indicates a value of an offset between the first time location and a second time location for the peak in the data traffic for a subset of devices of the set of multiple devices based on a threshold for an overall peak in the data traffic for the set of multiple devices. The operations of1910may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1910may be performed by a peak timing component1025as described with reference toFIG.10.

At1915, the method may include communicating data including the data traffic with the subset of devices based on the QoS response message indicating the second time location. The operations of1915may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1915may be performed by a communications component1030as described with reference toFIG.10.

At2005, the method may include transmitting a first signal that indicates a first time location for a peak in data traffic for the UE. The operations of2005may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2005may be performed by a peak timing component1425as described with reference toFIG.14.

At2010, the method may include receiving a second signal that indicates a second time location for the peak in the data traffic based on a threshold for an overall peak in data traffic for the UE. The operations of2010may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2010may be performed by a signal receiver1430as described with reference toFIG.14.

At2015, the method may include communicating data including the data traffic based on the second signal indicating the second time location. The operations of2015may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2015may be performed by a communications component1435as described with reference toFIG.14.

Aspect 1: A method for wireless communication at a network node, comprising: determining a first time location for a peak in data traffic for a plurality of devices in communication with a communications network comprising the network node: transmitting a signal that indicates a second time location for the peak in the data traffic for a subset of devices of the plurality of devices based at least in part on a threshold for an overall peak in the data traffic for the plurality of devices; and communicating data comprising the data traffic with the subset of devices based at least in part on the signal indicating the second time location.

Aspect 2: The method of aspect 1, wherein determining the first time location comprises: receiving a message that establishes communications with the plurality of devices and that indicates a first set of QoS parameters associated with the plurality of devices: communicating the data with the plurality of devices in accordance with the first set of QoS parameters; and estimating the first time location based at least in part on communicating the data.

Aspect 3: The method of aspect 1, wherein determining the first time location comprises: establishing communications with the plurality of devices according to a first set of QoS parameters; and receiving a message that indicates the first time location.

Aspect 4: The method of aspect 3, wherein receiving the message comprises: receiving a QoS request from an edge server that operates according to a first clock configuration that is the same as a second clock configuration for the network node.

Aspect 5: The method of any of aspects 3 through 4, wherein: the message indicates the first time location, a first quantity of bits of the data at the first time location, a periodicity associated with the first quantity of bits of the data, an arrival phase associated with the first quantity of bits of the data, or any combination thereof; and the first time location corresponds to a time common to the network node and a device that transmits the message.

Aspect 6: The method of any of aspects 1 through 5, wherein transmitting the signal comprises: transmitting a QoS response message that indicates a value of an offset between the first time location and the second time location.

Aspect 7: The method of aspect 6, wherein the offset between the first time location and the second time location is based at least in part on communications parameters associated with the subset of devices.

Aspect 8: The method of any of aspects 1 through 7, wherein transmitting the signal comprises: transmitting the signal to an edge server via an NEF interface.

Aspect 9: The method of any of aspects 1 through 7, wherein transmitting the signal comprises: transmitting the signal to a data network via an interface between a UPF of the network node and the data network.

Aspect 10: The method of any of aspects 1 through 9, further comprising: receiving an indication of the first time location from a UE; and transmitting the signal to the UE based at least in part on determining the second time location.

Aspect 11: The method of any of aspects 1 through 10, wherein transmitting the signal comprises: transmitting a set of signals comprising at least the signal periodically, wherein each signal of the set of signals indicates a respective offset from the first time location for a respective subset of devices of the plurality of devices.

Aspect 12: The method of any of aspects 1 through 11, wherein communicating the data comprises: receiving the data from a data network in accordance with the second time location; and forwarding the data from the data network to the subset of devices in accordance with the second time location, the data comprising downlink data.

Aspect 13: The method of any of aspects 1 through 1112, wherein communicating the data comprises: receiving the data from a UE via an API in accordance with the second time location, the data comprising uplink data, wherein the UE is in communication with the subset of devices.

Aspect 14: The method of any of aspects 1 through 13, wherein: the threshold for the overall peak in the data traffic corresponds to a threshold quantity of bits of the data traffic for the plurality of devices: the peak in the data traffic at the first time location exceeds the threshold; and the peak in the data traffic at the second time location is less than the threshold.

Aspect 15: The method of any of aspects 1 through 14, wherein the data traffic comprises uplink data, downlink data, or both associated with intra-coded frames, predicted frames, or both.

Aspect 16: A method for wireless communication at a UE, comprising: transmitting a first signal that indicates a first time location for a peak in data traffic for the UE: receiving a second signal that indicates a second time location for the peak in the data traffic based at least in part on a threshold for an overall peak in data traffic for the UE; and communicating data comprising the data traffic based at least in part on the second signal indicating the second time location.

Aspect 17: The method of aspect 16, wherein determining the first time location comprises: communicating the data with a device via a cross-layer API; and estimating the first time location based at least in part on communicating the data.

Aspect 18: The method of aspect 16, wherein determining the first time location comprises: establishing communications between the UE and a device; and receiving, from the device via a cross-layer API, a message that indicates the first time location.

Aspect 19: The method of any of aspects 16 through 18, further comprising: transmitting, to a device via a cross-layer API, a third signal that indicates the second time location, wherein the communicating is based at least in part on the third signal.

Aspect 20: The method of any of aspects 16 through 19, wherein an offset between the first time location and the second time location is based at least in part on communications parameters associated with a device in communication with the UE.

Aspect 21: The method of any of aspects 16 through 20, wherein the data comprises uplink data, downlink data, or both.

Aspect 22: An apparatus for wireless communication at a network node, comprising a processor: memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 15.

Aspect 23: An apparatus for wireless communication at a network node, comprising at least one means for performing a method of any of aspects 1 through 15.

Aspect 24: A non-transitory computer-readable medium storing code for wireless communication at a network node, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 15.

Aspect 26: An apparatus for wireless communication at a UE, comprising at least one means for performing a method of any of aspects 16 through 21.