STAGGERING TRANSMISSION TO WIRELESS CLIENTS BASED ON WIRELESS NETWORK INFORMATION

Certain aspects of the present disclosure provide techniques for staggering clients based on wireless network information. An example method generally includes obtaining, by a client from a modem, information associated with a wireless communication network. The method also includes transmitting, from the client to the server, at an application level, a first message including the information. The method further includes receiving, by the client from the server, data at a time determined based on the information.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims benefit of and priority to India Patent Application No. 202041035136, filed Aug. 14, 2020, which is herein incorporated by reference in its entirety for all applicable purposes.

BACKGROUND

Field of the Disclosure

Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for staggering clients for cloud-based services based on network information.

Description of Related Art

SUMMARY

The systems, methods, and devices of the disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure as expressed by the claims which follow, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled “Detailed Description” one will understand how the features of this disclosure provide advantages that include desirable latency at a client or desirable traffic capacity at serving cell and/or wireless network.

Certain aspects of the subject matter described in this disclosure can be implemented in a method for communicating, from a client to a server, information associated with a wireless communication network by a user equipment (UE). The method generally includes obtaining, by a client from a modem, information associated with a wireless communication network. The method also includes transmitting, from the client to the server, at an application level, a first message including the information. The method further includes receiving, by the client from the server, data at a time determined based on the information.

Certain aspects of the subject matter described in this disclosure can be implemented in a method for transmitting client data by a server. The method generally includes receiving, from a plurality of clients by a server, a plurality of messages, wherein at least two of the messages includes information associated with one or more wireless communication networks; and transmitting, from the server to at least one of the clients, client data, at one or more transmission occasions based on the information.

Certain aspects of the subject matter described in this disclosure can be implemented in an apparatus for communicating, from a client to a server, information associated with a wireless communication network. The apparatus generally includes a modem, a memory, and a processor, which is coupled to the memory and the modem. The processor and the memory are configured to obtain, by a client from the modem, information associated with a wireless communication network, transmit, from the client to the server, at an application level, a first message including the information, and receive, by the client from the server, data at a time determined based on the information.

Certain aspects of the subject matter described in this disclosure can be implemented in an apparatus for transmitting client data. The apparatus generally includes a memory and a processor, which is coupled to the memory. The processor and the memory are configured to receive, from a plurality of clients by the server, a plurality of messages, wherein at least two of the messages includes information associated with one or more wireless communication networks; and transmit, from the server to at least one of the clients, client data, at one or more transmission occasions based on the information.

Certain aspects of the subject matter described in this disclosure can be implemented in an apparatus for communicating, from a client to a server, information associated with a wireless communication network. The apparatus generally includes means for obtaining, by a client from a modem, information associated with a wireless communication network; means for transmitting, from the client to the server, at an application level, a first message including the information; and means for receiving, by the client from the server, data at a time determined based on the information.

Certain aspects of the subject matter described in this disclosure can be implemented in an apparatus for transmitting client data. The apparatus generally includes means for receiving, from a plurality of clients by a server, a plurality of messages, wherein at least two of the messages includes information associated with one or more wireless communication networks; and means for transmitting, from the server to at least one of the clients, client data, at one or more transmission occasions based on the information.

Certain aspects of the subject matter described in this disclosure can be implemented in a computer-readable medium. The computer readable medium includes computer-executable instructions that, when executed by one or more processors of a processing system, cause the processing system to perform obtaining, by a client from a modem, information associated with a wireless communication network; transmitting, from the client to the server, at an application level, a first message including the information; and receiving, by the client from the server, data at a time determined based on the information.

Certain aspects of the subject matter described in this disclosure can be implemented in a computer-readable medium. The computer readable medium includes computer-executable instructions that, when executed by one or more processors of a processing system, cause the processing system to perform receiving, from a plurality of clients by a server, a plurality of messages, wherein at least two of the messages includes information associated with one or more wireless communication networks; and transmitting, from the server to at least one of the clients, client data, at one or more transmission occasions based on the information.

DETAILED DESCRIPTION

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for staggering or distributing client sessions served by a server.

Under certain low-latency cloud-based services (such as split extended reality (XR) or live video streaming), the timelines of when packets for each of the clients are generated at a server and delivered may affect the traffic capacity of certain wireless communication networks (e.g., a 5G NR network and/or LTE network). For example, the server may send content to clients, which are camped on/served by the same cell, in overlapping periods. In certain cases, the content sent to the clients in the overlapping periods may exceed the traffic capacity at the cell that is serving the clients for the period. In such cases, the clients may experience lag or lower downlink data rates in content delivery from the server due to the traffic capacity of the cell. In certain cases, the lag and/or lower downlink data rates may translate to lower frame rates and/or lower resolutions for certain content, such as video frames. In certain cases, the overlapping content delivery may limit the number of users that a serving cell can serve for a given period.

Client traffic, for multiple clients, that shares network capacity, for example, at the same serving cell, may be spread out over time to enable a desirable number of users that can be served by a wireless communication network or provide desirable latency and/or downlink throughput for client data delivery at the clients. In certain aspects, the clients may send network information, such as cell identifiers of the serving cell, to the server, and the server may spread out transmission and/or generation of the client data based on the network information received from the clients. The network information may enable the server to map a client session to a specific network entity, such as a serving cell of the client, and the server may use the mapping between the client session and a specific network entity to determine a time at which content is delivered to the client. In a cluster of servers that provide content to clients, the servers may coordinate and adjust the transmission and/or generation of client data based on the network information associated with the clients. The various client data delivery schemes described herein may enable desirable latency at the clients, desirable downlink throughputs at the clients, and/or desirable user capacity for a wireless communication network, for example, at a specific serving cell.

The techniques described herein may be used for various wireless networks and radio technologies. While aspects may be described herein using terminology commonly associated with 3G, 4G, and/or new radio (e.g., 5G NR) wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems.

NR access may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or beyond), millimeter wave (mmW) targeting high carrier frequency (e.g., 24 GHz to 53 GHz or beyond), massive machine type communications MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements. In addition, these services may co-exist in the same subframe. NR supports beamforming and beam direction may be dynamically configured. MIMO transmissions with precoding may also be supported. MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE. Multi-layer transmissions with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells.

FIG.1illustrates an example wireless communication network100in which aspects of the present disclosure may be performed. For example, the wireless communication network100may be an NR system (e.g., a 5G NR network) or an Evolved Universal Terrestrial Radio Access (E-UTRA) system (e.g., an LTE network).

The UE120aincludes a client manager122that sends network information (e.g., a cell identifier) to the server134at an application level and receives client data at a time determined based on the network information, in accordance with aspects of the present disclosure. The server134includes a client manager136that generates and/or transmits client data at one or more occasions based on the network information, in accordance with aspects of the present disclosure.

The BSs110communicate with UEs120a-y(each also individually referred to herein as UE120or collectively as UEs120) in the wireless communication network100. The UEs120(e.g.,120x,120y, etc.) may be dispersed throughout the wireless communication network100, and each UE120may be stationary or mobile. Wireless communication network100may also include relay stations (e.g., relay station110r), also referred to as relays or the like, that receive a transmission of data and/or other information from an upstream station (e.g., a BS110aor a UE120r) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE120or a BS110), or that relays transmissions between UEs120, to facilitate communication between devices.

A network controller130may be in communication with a set of BSs110and provide coordination and control for these BSs110(e.g., via a backhaul). In aspects, the network controller130may be in communication with a core network132(e.g., a 5G Core Network (5GC)), which provides various network functions such as Access and Mobility Management, Session Management, User Plane Function, Policy Control Function, Authentication Server Function, Unified Data Management, Application Function, Network Exposure Function, Network Repository Function, Network Slice Selection Function, etc.

The core network132may be in communication with the server134, such that the core network132serves as a packet gateway for providing the UE120awith access to the server134. The core network132may include various servers and networking devices, such as switches, routers, and gateways. The server134may be or include a computer, computing device, or processing system that provides a service (e.g., split extended reality (XR), cloud-gaming, live streaming, etc.) to a client, such as the UE120a. The server may be or include a program, process, or thread running on the computer, computing device, or processing system. For example, the server134may be a virtual instance of a processing system or application, which is hosted on another processing system. That is, the server134may be virtualized in an application container or a virtual machine running on the host processing system. A computer-readable medium may include computer-executable instructions that, when executed by one or more processors of the host processing system, cause the host processing system to run the application container or virtual machine, which operates as the server. As further described herein with respect toFIG.4, split XR may offload the rendering of various content or data (e.g., video and/or audio streams) from the UE120to a server (e.g., the server134) with high-powered processors (e.g., graphics processing units (GPUs)) for virtual reality (VR), augmented reality (AR), or mixed reality (MR) applications. While the server134is depicted as a separate server entity in communication with the core network132to facilitate understanding, aspects of the present disclosure may be applied to the server134being integrated or co-located with the core network132, network controller130, and/or BS110a.

FIG.2illustrates example components of BS110aand UE120a(e.g., the wireless communication network100ofFIG.1), which may be used to implement aspects of the present disclosure.

At the BS110a, a transmit processor220may receive data from a data source212and control information from a controller/processor240. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), etc. The data may be for the physical downlink shared channel (PDSCH), etc. A medium access control (MAC)-control element (MAC-CE) is a MAC layer communication structure that may be used for control command exchange between wireless nodes. The MAC-CE may be carried in a shared channel such as a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), or a physical sidelink shared channel (PSSCH).

The memories242and282may store data and program codes for BS110aand UE120a, respectively. A scheduler244may schedule UEs for data transmission on the downlink and/or uplink.

Antennas252, processors266,258,264, and/or controller/processor280of the UE120aand/or antennas234, processors220,230,238, and/or controller/processor240of the BS110amay be used to perform the various techniques and methods described herein. As shown inFIG.2, the controller/processor280of the UE120ahas a client manager122that sends network information (e.g., a cell identifier) to a server (e.g., the server134) at an application level and receives client data at a time determined based on the network information, according to aspects described herein. Although shown at the controller/processor, other components of the UE120aand BS110amay be used to perform the operations described herein.

FIG.3is a diagram showing an example of a frame format300for certain wireless communication systems such as NR. The transmission timeline for each of the downlink and uplink may be partitioned into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be partitioned into 10 subframes, each of 1 ms, with indices of 0 through 9. Each subframe may include a variable number of slots (e.g., 1, 2, 4, 8, 16, . . . slots) depending on the SCS. Each slot may include a variable number of symbol periods (e.g., 7, 12, or 14 symbols) depending on the SCS. The symbol periods in each slot may be assigned indices. A mini-slot, which may be referred to as a sub-slot structure, refers to a transmit time interval having a duration less than a slot (e.g., 2, 3, or 4 symbols). Each symbol in a slot may indicate a link direction (e.g., DL, UL, or flexible) for data transmission and the link direction for each subframe may be dynamically switched. The link directions may be based on the slot format. Each slot may include DL/UL data as well as DL/UL control information.

In NR, a synchronization signal block (SSB) is transmitted. In certain aspects, SSBs may be transmitted in a burst where each SSB in the burst corresponds to a different beam direction for UE-side beam management (e.g., including beam selection and/or beam refinement). The SSB includes a PSS, a SSS, and a two symbol PBCH. The SSB can be transmitted in a fixed slot location, such as the symbols 0-3 as shown inFIG.3. The PSS and SSS may be used by UEs for cell search and acquisition. The PSS may provide half-frame timing, the SS may provide the CP length and frame timing. The PSS and SSS may provide the cell identity. The PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frame, SS burst set periodicity, system frame number, etc. The SSBs may be organized into SS bursts to support beam sweeping. Further system information such as, remaining minimum system information (RMSI), system information blocks (SIBs), other system information (OSI) can be transmitted on a physical downlink shared channel (PDSCH) in certain subframes. The SSB can be transmitted up to sixty-four times, for example, with up to sixty-four different beam directions for mmWave. The multiple transmissions of the SSB are referred to as a SS burst set. SSBs in an SS burst set may be transmitted in the same frequency region, while SSBs in different SS bursts sets can be transmitted at different frequency regions.

Certain cloud-based services (such as split XR) may offload the computation or rendering of various content or data (e.g., video and/or audio streams) to servers with high-powered processors (e.g., graphics processing units (GPUs)). In certain cases, a head mount display (HMD) may be equipped with a wireless modem, which provides access to a wireless communication network (e.g., the wireless communication network100) and enables a split XR session to be wirelessly streamed between the HMD and a server. For example,FIG.4is a diagram illustrating an example environment400in which a UE may communicate with a server through a cloud-based service or session. As shown, the UE120may receive various generated content402(e.g., encoded video stream(s), encoded audio stream(s), and/or instructions for haptic feedback) from the server134through a radio access network (RAN), such as the BS110and/or network controller130. For example, the server134may send the generated content402on a periodic basis (e.g., every 11, 13, 16, or 22 ms) at a high throughput level (e.g., >100 kilobytes). The UE120may send various information404to the server134through the BS110. For example, the UE120may send the information404on a periodic basis (e.g., every 2 ms) at relatively low throughput level (e.g., 100 bytes). The information may be pose information (e.g., the orientation of the user's head relative to a coordinate system) and/or control information (e.g., information from an input device such as a gamepad, controller, or wand). In certain aspects, the server134may generate the content402based on the information404. In an XR setting, the UE120may display the generated content to the user as a sequence of video frames in an HMD.

A split XR session may have various traffic flow characteristics to provide an acceptable XR experience to the user (i.e., an immersive, realistic, and comfortable experience). For example, a split XR session may have a low-latency (e.g., 5-20 ms delay) between the UE and server, a highly reliable bit error rate (e.g., a packet error rate (PER) of less than or equal to 10−3), high downlink throughputs (100-600 Mbit/s or 1-2.5 Gbit/s or higher), and periodic low downlink throughputs (e.g., <1 Mbps). As used herein, split XR may include various low-latency cloud-based services such as cloud gaming, split rendering, split computation, virtual reality (VR), augmented reality (AR), mixed reality (MR), or live video streaming.

Example of Staggering Clients Based on Wireless Network Information

Under certain low-latency cloud-based services (such as split XR or live video streaming), the timelines of when packets for each of the clients (e.g., the UE120) are generated at the server (e.g., the server134) and delivered may affect the traffic capacity of certain wireless communication networks (e.g., 5G NR network or LTE network). For example, the server may send content to clients, which are camped on/served by the same cell (e.g., BS110aofFIG.1), in overlapping periods. In certain cases, the content sent to the clients in the overlapping periods may exceed the traffic capacity at the cell that is serving the clients for the period. In such cases, the clients may experience lag or lower downlink data rates in content delivery from the server due to the traffic capacity of the cell. In certain cases, the lag and/or lower downlink data rates may translate to lower frame rates and/or lower resolutions for certain content, such as video frames. In certain cases, the overlapping content delivery may limit the number of users that a serving cell can serve for a given period.

Aspects of the present disclosure provide various apparatus and methods for providing staggered transmission and/or generation of client data based on wireless network information. For example, client traffic, for multiple clients, that shares network capacity, for example, at the same serving cell, may be spread out over time to enable a desirable number of users that can be served by a wireless communication network or provide desirable latency and/or downlink throughput for client data delivery at the clients. In certain aspects, the clients may send network information, such as cell identifiers of the serving cell, to the server, and the server may spread out transmission and/or generation of the client data based on the network information received from the clients. The network information may enable the server to map a client session to a specific network entity, such as a serving cell for the client, and the server may use the mapping between the client session and a specific network entity to determine a time at which content is delivered to the client. In a cluster of servers that provide content to clients, the servers may coordinate and adjust the transmission and/or generation of client data based on the network information associated with the clients. The various client data delivery schemes described herein may enable desirable latency and/or downlink throughputs at the clients and/or desirable user capacity for a wireless communication network, for example, at a specific serving cell.

FIG.5is a flow diagram illustrating example operations500for communicating, from a client to a server, information associated with a wireless communication network, in accordance with certain aspects of the present disclosure. The operations500may be performed, for example, by a user equipment (e.g., the UE120ain the wireless communication network100). The operations500may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor280ofFIG.2). Further, the transmission and reception of signals by the UE in the operations500may be enabled, for example, by one or more antennas (e.g., antennas252ofFIG.2). In certain aspects, the transmission and/or reception of signals by the UE may be implemented via a bus interface of one or more processors (e.g., controller/processor280) obtaining and/or outputting signals.

The operations500may begin at502, where a client (e.g., the UE120) may obtain, from a modem (e.g., a cellular modem such as the modulators/demodulators in the transceivers254a-254r), information associated with a wireless communication network. At504, the client may transmit, to the server, at an application level, a first message including the information. Optionally, at506, the client may transmit, to the server, a second message including client information (e.g., headset orientation information, prediction coefficients, controller input, etc.). At508, the client may receive, from the server, data at a time determined based on the information. Optionally, the client may display the data as one or more video frames, for example, using a VR headset or other display device.

In aspects, the information sent to the server at504may enable the server to stagger or adjust the times at which the data is transmitted or generated for multiple clients, as further described herein with respect toFIG.6. That is, the time at which the data is received at508may be adjusted by the server based on the information provided by the client. For example, the server may stagger the data sent to clients camped at the same serving cell based on the information, as further described herein, for example, with respect toFIG.9B. As an example of staggering data, the server may distribute or adjust rendering timelines of specific clients (e.g., clients served at the same serving cell), such that the downlink traffic for the specific clients do not overlap with each other. In certain cases, staggering data may allow for partially overlapping downlink and/or uplink traffic for specific clients, for example, depending on the network or channel capacity of the RAN.

As used herein, an application level (or layer) may refer to a layer of a protocol stack in which the application layer is the topmost layer, and the remaining layers include a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer, in descending order. For example, the application level may be the level in which the payload for the protocol stack in a user plane is generated. The payload may be processed at various layers (e.g., the PDCP layer, RLC layer, MAC layer, and PHY layer) to enable transmission of the payload over wireless resources (e.g., frequency-time resources). In certain aspects, the application level may include Session Initiation Protocol (SIP) signaling used to establish, maintain, or terminate a real-time session between the client and server.

In certain aspects, obtaining the information at502may involve the client accessing the information via the modem. For example, the client may request the information from the modem, and the modem may provide the information to the client. In certain cases, an application programming interface (API) may be used to pass the information (such as cell identifier, beam identifier, etc.) from the modem to the client. In certain cases, an operating system of the UE (such as Android, Linux, Windows, iOS, macOS, etc.) may provide the API to access the modem at the application level via the client. That is, the operating system may serve as an intermediary between the client at the application level and modem at the hardware level. In certain aspects, the information may include various attributes of the client with respect to the wireless network. For example, the information may include at least one of a cell identifier of a serving cell (e.g., the BS110a) of the client, a beam identifier of the serving cell, quasi-colocation (QCL) information associated with a reference signal of the serving cell, a medium access control (MAC) address of an access point serving the client, or a network identifier of a network serving the client.

The cell identifier may be an enhanced cell identity (ECI) or a global cell identification such as a cell identity used to unambiguously identify a cell within a wireless network (e.g., a public land mobile network (PLMN)). The beam identifier may be an indication of a downlink beam that the client uses to receive the data at508. For example, the beam identifier may be an SSB identifier associated with an SSB. The QCL information may also be representative of the downlink beam that carries the data from the serving cell to the client. In certain cases, a reference signal (e.g., a channel state information reference signal (CSI-RS) or a DIVERS) may have a QCL relationship with another reference signal (e.g., an SSB or CSI-RS). The QCL information may include the reference signals, reference signal resources, or a QCL type included in a QCL configuration, such as a Transmission Configuration Indication (TCI) state. The network identifier may be, for example, a mobile country code (MCC), mobile network code (MNC), PLMN (which includes the MCC and MNC), a base station identifier (such as an eNodeB identifier or a gNodeB identifier), or a combination thereof.

In certain aspects, the wireless communication network may be a wireless wide area network (WWAN) (such as a 5G NR network or a LTE network) or a wireless local area network (WLAN) (such as a WiFi network). In aspects, the base station serving the client may be a wireless access point in a WLAN, and the information obtained at502may include the MAC address of the access point or a service set identifier (SSID) of a WLAN.

In certain aspects, the first message may be included in Session Description Protocol (SDP) signaling for various real-time transfer protocols (RTPs), such as session initiation protocol (SIP). That is, the first message may be an SDP message for SIP. In certain cases, the SDP message may include the information using an attribute field (e.g., “a=”). As an example, the attribute field may have the following format:

where X-cell is the name of the attribute field (other suitable names may be used), MNC is the mobile network code, MCC is the mobile country code, and CID is the cell identifier.

In certain cases, the client may report a wait time between when a frame is ready (e.g., received and decoded at the client) and when time the frame is consumed by the display or other display processing such as an asynchronous reprojection or asynchronous timewarp (ATW). In such cases, the server may adjust the transmission and/or generation times for client data across some or all of the clients by changing the order of render. In certain cases, the client may report a downlink time spread of packets (e.g., IP packets) arriving for a video frame. The downlink time spread may refer to the duration of time that it takes for a video frame to arrive at the client across multiple packets. In such cases, the server may adjust the transmission and/or generation times for the client based on such a time offset if possible.

As an example, the operations500may include the client transmitting, to the server, a third message including a wait time for processing the data at the client or a downlink time spread of packets arriving at the client and carrying the generated data, wherein the time is further determined based on the third message. In response to the third message, the client may receive, from the server, additional data at another time determined based on the information and the third message.

In certain aspects, the client may send updated information to the server, for example, when the client performs a handover to a target cell. As an example, the client may handover from a serving cell to a target cell, and based on the handing over, the client may transmit, to the server, updated information. In aspects, the updated information may include a cell identifier of the target cell, a beam identifier of the target cell, QCL information of the target cell, or a network identifier of the network serving the client. In certain aspects, the updated information may include a MAC address of an access point to which the client has transitioned.

In certain aspects, the server may be providing various cloud-based services to the client, such as split XR, split rendering, split computation, cloud gaming, live streaming, or the like. That is, the operations500may be implemented for a split XR session or cloud-gaming session. For example, the client information transmitted at506may include headset orientation information, prediction coefficients for the headset orientation, controller input, or other suitable processing input for generating the data. The data received at508may include one or more rendered video frames, where the server performs the rendering based on the client information. In aspects, the data received at508may include one or more rendered video frames (e.g., video frames for the right eye and video frames for the left eye), audio streams, and/or instructions for haptic feedback, and the client may display the one or more rendered video frames, play the audio streams, and/or provide the haptic feedback. As examples, the video frames may be displayed on an HMD in a split XR setting or television screen in a cloud gaming setting, the audio stream may be played through headset speakers, and the haptic feedback may vibrate a controller. The server may generate the data received at508based on various input provided by the client. That is, the data received at508may be generated based on the client information included in the second message at506.

In certain cases, the data received at508may be instructions or data for an Internet-of-Things (IOT) device in which the server provides low-latency split computation based on sensor data measured by the IOT device. That is, the client information at506may include various sensor measurements.

In certain aspects, the operations500may be implemented for live streams of various content, such as live video streams. For example, the data received at508and displayed at510may be video frames of a live video stream.

FIG.6is a flow diagram illustrating example operations600for transmitting client data, in accordance with certain aspects of the present disclosure. The operations600may be performed, for example, by a server (e.g., the server134in the wireless communication network100). The operations600may be complimentary to the operations500performed by the UE. The operations600may be implemented as software components that are executed and run on one or more processors (e.g., the processor1304ofFIG.13). Further, the transmission and reception of signals by the server in the operations600may be enabled, for example, by a network interface (e.g., the network interface1308ofFIG.13) through a wired or optical interface. In certain aspects, the transmission and/or reception of signals by the server may be implemented via a bus interface (e.g., the bus1306ofFIG.13) of one or more processors (e.g., the processor1304) obtaining and/or outputting signals.

The operations600may begin at602, where the server may receive, from a plurality of clients, a plurality of messages. In aspects, at least two of the messages may include information associated with one or more wireless communication networks, and the information may correspond to the information at502/504of the operations500. Optionally, at604, the server may receive, from the clients by the server, a plurality of additional messages including client information (e.g., headset orientation information, prediction coefficients for the headset orientation, controller input, or other suitable processing input). Optionally, at606, the server may, in response to the additional messages, generate client data for at least one of the clients based on the information and the client information. At608, the server may transmit, to the at least one of the clients, client data, at one or more transmission occasions based on the information. In aspects, the information received at602may enable the server to stagger or adjust the times at which the data is transmitted and/or generated for multiple clients. In certain cases, information received at602may enable the server to spread out or distribute the downlink data of multiple clients over time in order to prevent or reduce overloading the network capacity and/or channel capacity of a specific serving cell or wireless network.

In certain aspects, the server may be a computer, computing device, or processing system that provides a service (e.g., split XR rendering of video frames, audio streams, and/or haptic feedback) to the client. In certain aspects, the server may be a program, process, or thread running on the computer, computing device, or processing system. For example, the server134may be a virtual instance of a processing system or application, which is hosted on another processing system. That is, the server134may be virtualized in an application container or a virtual machine running on the host processing system.

In certain aspects, the same server may provide cloud-based services to certain clients (for example, clients with the same cell identifier). In certain cases, a cluster of servers may provide the cloud-based services to multiple clients, as further described herein with respect toFIG.8. The same server providing cloud-based services may facilitate the staggering of the generation and/or transmission of client data at desirable latencies, for example, due to an internal clock source at the server. As an example, the operations600may further include the server obtaining additional information associated with the one or more wireless communication networks and additional clients. For example, the server may obtain the additional information from a common database (or any suitable data structure) accessible by the servers in the cluster or another server managing the information. The server may select a group of clients among the clients and the additional clients based at least in part on the information and the additional information. In certain cases, instead of the server making the selection, the server may be instructed by another server to provide cloud-based services to the selected group of clients. Transmission of the client data at608may include the server transmitting the client data to the group of clients. In aspects, the other server may be integrated within the same computer, computing device, or processing system as the server. For example, the other server may be another virtual machine or application container running on a host machine that is hosting the virtual machine or application container for the server. In certain aspects, the other server may be a separate virtual machine, application container, computer, computing device, or processing system as the server and/or running on a separate virtual machine, computer, computing device, or processing system as the server.

The server may select the group of clients based on various attributes associated with the wireless communication networks. For example, the server may select the clients with the same cell identifier based on the information received at602and the additional information. As an example, selecting the group of clients may include selecting the group of clients with at least one of the same cell identifier of a serving cell of the group of clients, the same beam identifier of the serving cell, the same QCL information of the serving cell, the same MAC address of an access point, or the same network identifier of a network (e.g., a wireless communication network such as a PLMN) serving the group of clients.

In certain cases, multiple servers may provide cloud-based services to clients connected to the same network entity (e.g., the same serving cell or wireless network). In such cases, the servers may negotiate to agree on the times at which client data is generated (e.g., rendered at606) or transmitted at608. For example, the servers may determine the times at which client data is generated or transmitted based on the times when the sessions were established (e.g., a new session may set the times based on the available gap) or the round-trip latencies among the clients (e.g., the session with a lower latency may be shifted).

As an example, the operations600may further include the server obtaining additional information associated with the one or more wireless communication networks and additional clients. The server may select a group of clients among the clients and the additional clients based at least in part on the information and the additional information. For example, the server may identify clients connected to the same serving cell or wireless network (e.g., PLMN). The server may transmit, to another server, a schedule indicating the one or more transmission occasions or one or more processing occasions for the group of clients. The other server may use the schedule to generate or transmit data at the one or more transmission occasions or one or more processing occasions for the clients in the group served by the other server. In aspects, the schedule may be determined based on session establishment times of the group of clients or round-trip latencies of the group of clients. In certain cases, the server and the other server may be time synchronized with each other, for example via a time server, such as a precision time protocol (PTP) server or a network time protocol (NTP) server.

In certain cases, the generation of data at606or the transmission of data at608may be staggered or shifted based on the information received at602. For example, the server may initiate generating of the client data at one or more processing occasions, timing of which is based at least in part on the information. Suppose, for example, a first client and a second client are connected to the same serving cell. The server may initiate generating the client data for the first client at a first processing occasion and initiate generating the client data for the second client at a second processing occasion. For example, the second processing occasion may be offset from the first processing occasion by a specific duration (e.g., 5 or 10 ms).

In certain aspects, the transmission of the client data at608may include the server initiating transmitting of the client data at the one or more transmission occasions, timing of which is based at least in part on the information. For example, the server may initiate generating the client data for the first client at a first transmission occasion and initiate generating the client data for the second client at a second transmission occasion. The second transmission occasion may be offset from the first transmission occasion by a specific duration (e.g., 5 or 10 ms).

In certain aspects, the information may include various attributes of the clients with respect to the wireless networks. For example, the information may include at least one of one or more cell identifiers of serving cells (e.g., the BS110a) of the clients, one or more beam identifiers of the serving cells, QCL information associated with one or more reference signals of the serving cells, one or more MAC addresses of access points serving the clients, or one or more network identifiers of networks serving the clients.

In certain aspects, the messages received at602may be included in SDP signaling for various RTPs, such as SIP, for example, as described herein with respect to the operations500. As an example, the messages received at602may be SDP messages for SIP.

In certain aspects, the server may receive updated information from a client, for example, when the client performs a handover to a target cell. When the server receives the updated information, the server may adjust the times at which client data is generated or transmitted. For example, the operations600may further include the server receiving, from one of the clients, updated information. In aspects, the updated information may include a cell identifier of the target cell, a beam identifier of the target cell, QCL information of the target cell, or a network identifier of the network serving the client. In certain aspects, the updated information may include a MAC address of an access point to which the client has transitioned. The server may initiate transmitting or generating of the client data at one or more processing occasions or one or more transmission occasions, timing of which is based at least in part on the updated information (e.g., the cell identifier). For example, suppose the client moves to a cell where there are no other clients being served by the server. In such a case, the server may concurrently generate or transmit the data for this client with other clients. In certain cases, when the server receives the updated information, the server may request or instruct another server to process the client data for the client. For example, the server may handover processing of the client data to another server in response to receiving the updated information.

In certain cases, the server may receive, from a client, a wait time between when a frame is ready (e.g., received and decoded at the client) and when time the frame is consumed by the display or other display processing such as an asynchronous reprojection or ATW. The server may adjust the transmission and/or generation times for client data across some or all of the clients based on the wait time. That is, the server may adjust the order at which client data is generated or transmitted based on the wait time reported by a client. For example, the wait time may enable the server to shift the client to a later processing occasion or transmission occasion in the order. In certain cases, the server may receive a downlink time spread of packets (e.g., IP packets) arriving for a video frame. In such cases, the server may adjust the transmission and/or generation times for the client based on such a time offset.

As an example, the operations600may further include the server receiving, from the clients, a plurality of additional messages including wait times for processing the generated data at the clients or downlink time spreads of packets arriving at the clients and carrying the generated data. The server may initiate generating or transmitting of additional client data at one or more processing occasions or at one or more transmission occasions, timing of which is based at least in part on the wait times or the downlink time spreads.

In certain aspects, the server may be providing various cloud-based services to the client, such as split XR, split rendering, split computation, cloud gaming, live streaming, or the like. That is, the operations600may be implemented for a split XR session or cloud-gaming session. For example, the client information received at604may include headset orientation information, prediction coefficients for the headset orientation, controller input, or other suitable processing input for generating the data. The data generated at608may include one or more rendered video frames, where the server performs the rendering based on the client information. In aspects, the data generated at606and transmitted at608may include one or more rendered video frames (e.g., video frames for the right eye and video frames for the left eye), audio streams, and/or instructions for haptic feedback, and the client may display the one or more rendered video frames, play the audio streams, and/or provide the haptic feedback. As examples, the video frames may be displayed on an HMD in a split XR setting or television screen in a cloud gaming setting, the audio stream may be played through headset speakers, and the haptic feedback may vibrate a controller. The server may generate the data received at606based on various input provided by the client.

In certain aspects, the operations600may be implemented for split computation applications. For example, the data generated at606and transmitted at608may be instructions or data for IOT device in which the server provides low-latency split computation based on sensor data measured by the IOT device. That is, the client information at604may include various sensor measurements, and the server may generate at606output based on the sensor measurements. The server may stagger or adjust the generation and/or transmission of the data for various clients based on the information received at602.

In certain aspects, the operations600may be implemented for live streaming sessions of various content, such as live video streams. For example, the data transmitted at608may be video frames of a live video stream. The server may stagger or adjust the transmission of live streaming content to various clients based on the wireless received at602.

FIG.7is a signaling flow diagram illustrating example operations700for staggering clients based on wireless network information, in accordance with certain aspects of the present disclosure. In this example, the UEs120a,120bmay obtain wireless network information, at702aand702b, respectively. As described herein, the wireless network information may be information associated with a wireless communication to which the UE is connected. For example, the wireless network information may include a cell identifier of a serving cell, a beam identifier of the serving cell, QCL information the serving cell, a MAC address of an access point, or a network identifier of a network serving the client. At704aand704b, the UEs120a,120bmay transmit the wireless network information to the server134through the access network740. The UEs120a,120bmay send the wireless network information when establishing a session with the server134. In aspects, the access network740may include various network entities in a wireless communication network, such as a base station, access point, network controller, or core network. Optionally, at706aand706b, the UEs120a,120bmay transmit client information (such as headset orientation or controller input) to the server134, for example, in a split XR session or cloud-gaming session. Optionally, at708, the server134may generate client data based on the client information received at706aor706b.

In certain cases, the server134may stagger or adjust the generation of the client data for each of the UEs120a,120bdepending on the wireless network information. For example, suppose the UEs120a,120bare connected to the same serving cell. The server134may identify that the UEs120a,120bare connected to the same serving cell based on the cell identifiers included in the wireless network information and mapped to the sessions of the UEs120a,120b. Based on the identification, the server134may generate the client data for the UE120aat a first processing occasion and generate the client data for the UE120bat a second processing occasion, where the first processing occasion is offset from the second processing occasion by a specific duration. In certain cases, for example, where the UEs120a,120bare connected to separate cells or separate wireless networks, the server134may generate the client data for the UEs120a,120bconcurrently.

At710aand710b, the server134may transmit the client data to the UEs120a,120bthrough the access network740. In certain cases, the server134may stagger or adjust the transmission of the client data for each of the UEs120a,120bdepending on the wireless network information. For example, suppose the UEs120a,120bare connected to the same serving cell. The server134may transmit, at710a, the client data for the UE120aat a first transmission occasion and transmit, at710b, the client data for the UE120bat a second transmission occasion, where the first transmission occasion is offset from the second transmission occasion by a specific duration. In certain cases, for example, where the UEs120a,120bare connected to separate cells or separate wireless networks, the server134may transmit the client data, at710aand710b, for the UEs120a,120bconcurrently.

Optionally, at712aand712b, the UEs120a,120bmay display the client data as video frames. For example, at712a, the UE120amay display the video frames with a HMD from the generated client data. In certain cases, at712b, the UE120bdisplay the video frames with a display of a smartphone or tablet.

In certain aspects, the server described herein may be part of a cluster of servers that provide various cloud-based services to clients. For example,FIG.8is a diagram illustrating an example cluster of servers800in communication with UEs120a-dvia base stations110a,110b, in accordance with certain aspects of the present disclosure. In this example, the cluster of servers800may include a first server802and a second server804. The servers802,804may distribute the network information (e.g., the network information806,808) received from the UEs (e.g., the UEs120a,120b) along with other attributes of a client session. In some cases, the servers802,804may store the various attributes of a client session (including the network information) in a common data structure such as a common database810, which is accessible by the servers802,804. The common data structure may provide a mapping to various attributes of a client session. As an example, the attributes of a client session may include one or more of a user identifier, a session identifier, a cell identifier (or other wireless network information), and a frame rendering time offset (with respect to a preconfigured reference time). In certain cases, the servers802,804may exchange, with each other, the mapping of the attributes of clients. As an example, the servers802,804may coordinate to route all users with the same cell identifier to the same server, which may alleviate any inaccuracies in synchronizing the staggering of clients among servers. In some cases, a central server in the cluster of servers800may manage the mapping of the attributes of clients, and the servers802,804may query the central server for the attributes. In certain cases, the servers802,804may receive instructions (such as a schedule for processing or transmission occasions), from the central server, based on the mapping of the attributes of clients. The servers802,804may use the network information to determine which UEs can be staggered for generation and/or transmission of client data or which UEs can be handled concurrently for generation and/or transmission of client data.

In certain aspects, the cluster of servers800may be time synchronized via a time server812. In aspects, the timer server812may be a precision time protocol (PTP) server or a network time protocol (NTP) server. PTP may provide an accuracy in the range of microseconds or nanoseconds (e.g., 100 ns). NTP may provide an accuracy in the range of milliseconds or seconds (e.g., 1 ms). The time server812may provide a common clock source for the cluster of servers800in scheduling processing occasions and/or transmission occasions of client data to clients.

For example, suppose the first server802is serving a session for the first UE120a, and the second server804is serving a session for the second UE120b. Because the first UE120aand second UE120bare connected to the same serving cell, the servers802,804may coordinate to stagger the generation and/or transmission of client data to these UEs. As an example, the first server802may generate or transmit the client data for the first UE120abefore the second server804generates or transmits the client data for the second UE120b. Staggering the generation and/or transmission of client data for the UEs120a,120bmay reduce the traffic load at the base station110aand enable the base station110ato server more users. Staggering the generation and/or transmission of client data for the UEs120a,120bmay provide a desirable latency and/or downlink throughput for the cloud-based service at the UEs120a,120b.

FIG.9Ais a diagram illustrating an example architecture of a communications network900in which a client application901provides network information to a server134, in accordance with certain aspects of the present disclosure. As shown, the UEs120a,120bmay be connected to the base station110a, and the UEs120c,120dmay be connected to the base station110b. The base stations110a,110bmay be in communication with a RAN-centralized unit (RAN-CU)930, such as the network controller130. The RAN-CU930may be in communication with the core network132, which is in communication with the server134(e.g., an edge server). In this example, the client application901may obtain network information from the modem of the UE (e.g., the UE120d) and send the network information to the server134through the base station110b, RAN-CU930, and the core network132. The server134may use the network information to determine whether to stagger or adjust the generation and/or transmission of client data to the UE120d.

FIG.9Billustrates timing diagrams showing a server staggering transmission of client data, in accordance with certain aspects of the present disclosure. In this example, a server may be providing services to four UEs, such as the UEs120a-120dinFIG.9A. As inFIG.9A, the UEs120a,120bmay be connected to the base station110a(Cell1), and the UEs120c,120dmay be connected to the base station110b(Cell2). The server may stagger the transmission of client data to the UEs120a-120dbased on the serving cell serving the UEs. As depicted in the timing diagram902, the server may transmit the client data for the UEs120a,120cat a first transmission occasion906, transmit the client data for the UE120bat a second transmission occasion908, and transmit the client data for the UE120dat a third transmission occasion910. The server may repeat this schedule of staggering transmissions.

In aspects, the server may distribute the transmission of client data over the various transmission occasions906,908,910. In this example, the transmission occasions for clients from the same serving cell may be staggered such that the transmission occasions do not overlap with other, such as the first transmission occasion906and second transmission occasion908not overlapping for the UEs120a,120b, respectively. In certain cases, the transmission occasions for clients from the same serving cell may partially overlap with each other depending on the network or channel capacity of the RAN serving the clients. In certain aspects, the server may adjust or shift when client data is generated for specific clients at the server to provide the staggered transmission occasions. For example, the server may initiate the generation of client data for the UE120abefore initiating the generation of client data for the UE120bto provide the staggered transmission occasions906,908. In certain cases, the server may adjust or shift when the client data is sent to specific clients to provide the staggered transmission occasions. For example, in live streaming applications, the server may send a burst of live streaming content to the UE120aat the first transmission occasion906before sending a separate burst of live streaming content to the UE120bat the second transmission occasion908.

As depicted in the timing diagrams904, the client data may arrive at the UEs via the respective base stations in a staggered or distributed fashion. For example, at a first occasion912corresponding to the first transmission occasion906, the UE120amay receive the client data via the base station110a, and at a second occasion914corresponding to the second transmission occasion908, the UE120bmay receive the client data via the base station110a. For the base station110b, the UE120cmay receive the client data at a third occasion916corresponding to the first transmission occasion906, and the UE120dmay receive the client data at a fourth occasion918corresponding to the third transmission occasion910.

While the examples depicted inFIG.9Bare described herein with respect to staggering transmission occasions to facilitate understanding, aspects of the present disclosure may also be applied to staggering or adjusting processing occasions.

FIG.10is a timing diagram illustrating the delivery of client data from a server to a client, in accordance with certain aspects of the present disclosure. As shown, the client (e.g., the UE120a) may transmit client/network information1002(or network information) to the RAN, the client/network information1002may take a certain duration to travel to the RAN, which may take a certain period of time to forward the client/network information1002to the server. Optionally, the server may generate client data1004(e.g., video frames) based on the client information, such as headset orientation, controller input, or other processing input. In such cases, the server may initiate the generation of client data at a processing occasion1006. That is, the processing occasion1006may be when the server initiates generation of client data, such as video frames. The server may transmit the client data1004to the client through the RAN at a transmission occasion1008. That is, the transmission occasion1008may be when the server initiates transmission of client data. In certain aspects, the server may be transmitting a live stream to the client. In such a case, the server may only adjust or stagger the transmission occasion1008due to the negligible processing involved in streaming recorded content.

The RAN may forward the client data1004to the client, and this process may take a certain duration. The client may receive the client data1004. In some cases, the client may perform processing on the client data such as decoding video frames or audio streams. In certain cases, the client may display the client data via a display, for example, at the display occasion1010. The timeline, in this example, demonstrates that the server may shift the processing occasion1006or the transmission occasion1008to stagger, adjust, or distribute the arrival of client data at the RAN/UEs, for example, as described herein with respect toFIG.9B.

FIG.11are timing diagrams illustrating an example of distributing clients over time, in accordance with certain aspects of the present disclosure. As shown in a first timing diagram1102, the server may be serving multiple clients1106,1108,1110concurrently (e.g., transmitting or generating client data within the same time period or in overlapping time periods). As depicted in the timing diagram1104, the server may distribute the occasions when the client data is generated or transmitted for the clients1106,1108,1110.

While the various examples are described herein with respect to split XR applications to facilitate understanding, aspects of the present disclosure may also be applied to various other cloud-based or edge-based services, such as cloud-gaming, split rendering, split computation, and/or live streaming services.

FIG.12illustrates a communications device1200(e.g., the UE120) that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated inFIG.5. The communications device1200includes a processing system1202coupled to a transceiver1208(e.g., a transmitter and/or a receiver). The transceiver1208is configured to transmit and receive signals for the communications device1200via an antenna1210, such as the various signals as described herein. The processing system1202may be configured to perform processing functions for the communications device1200, including processing signals received and/or to be transmitted by the communications device1200.

The processing system1202includes a processor1204coupled to a computer-readable medium/memory1212via a bus1206. In certain aspects, the computer-readable medium/memory1212is configured to store instructions (e.g., computer-executable code) that when executed by the processor1204, cause the processor1204to perform the operations illustrated inFIG.5, or other operations for performing the various techniques discussed herein for staggering clients. In certain aspects, computer-readable medium/memory1212stores code for receiving1214, code for transmitting1216, code for obtaining1218, code for handing over1220, and/or code for displaying1222. In certain aspects, the processor1204has circuitry configured to implement the code stored in the computer-readable medium/memory1212. The processor1204includes circuitry for receiving1224, circuitry for transmitting1226, circuitry for obtaining1228, circuitry for handing over1230, and/or circuitry for displaying1232.

FIG.13illustrates a communications device1300(e.g., the server134) that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated inFIG.6. The communications device1300includes a processing system1302coupled to a network interface1308. The network interface1308is configured to transmit and receive signals for the communications device1300via a wired or optical interface, such as the various signals as described herein. As an example, the network interface1308may be in communication with one or more base stations, such as the base station110. The processing system1302may be configured to perform processing functions for the communications device1300, including processing signals received and/or to be transmitted by the communications device1300. The network interface1308may be coupled to the processing system via a bus1306.

The processing system1302includes a processor1304coupled to a computer-readable medium/memory1312via the bus1306. In certain aspects, the computer-readable medium/memory1312is configured to store instructions (e.g., computer-executable code) that when executed by the processor1304, cause the processor1304to perform the operations illustrated inFIG.6, or other operations for performing the various techniques discussed herein for staggering clients. In certain aspects, computer-readable medium/memory1312stores code for receiving1314, code for transmitting1316, code for generating1318, code for obtaining1320, code for selecting1322, and/or code for initiating1324. In certain aspects, the processor1304has circuitry configured to implement the code stored in the computer-readable medium/memory1312. The processor1304includes circuitry for receiving1326, circuitry for transmitting1328, circuitry for generating1330, circuitry for obtaining1332, circuitry for selecting1334, and/or circuitry for initiating1336.

Example Aspects

In addition to the various aspects described above, specific combinations of aspects are within the scope of the disclosure, some of which are detailed below:

Aspect 1: A client for communicating, to a server, information associated with a wireless communication network, comprising: a modem; a memory; and a processor coupled to the memory and the modem, the processor and the memory being configured to: obtain, from the modem, information associated with a wireless communication network, transmit, to the server, at an application level, a first message including the information, and receive, from the server, data at a time determined based on the information.

Aspect 2: The client of Aspect 1, wherein the information includes at least one of: a cell identifier of a serving cell of the client; a beam identifier of the serving cell; quasi-colocation (QCL) information associated with a reference signal of the serving cell; a medium access control (MAC) address of an access point serving the client; or a network identifier of a network serving the client.

Aspect 3: The client according to any one of Aspects 1 or 2, wherein the first message is a session description protocol (SDP) message for session initiation protocol (SIP).

Aspect 4: The client according to any one of Aspects 1-3, wherein the processor and the memory are further configured to: transmit, to the server, a second message including a wait time for processing the data at the client or a downlink time spread of packets arriving at the client and carrying the data, wherein the time is further determined based on the second message; and receive, by the client from the server in response to the second message, additional data at another time determined based on the information and the second message.

Aspect 5: The client according to any one of Aspects 1-4, wherein the processor and the memory are further configured to: hand over from a serving cell to a target cell, and transmit, to the server, updated information indicating a cell identifier of the target cell based on the handing over.

Aspect 6: The client according to any one of Aspects 1-5, wherein: the processor and the memory are further configured to transmit, to the server, a second message including client information; and the apparatus further comprises a display configured to display the data as one or more rendered video frames, wherein the data comprises the one or more rendered video frames, and the data is generated based on the client information included in the second message.

Aspect 7: A server for transmitting client data, comprising: a memory; and a processor coupled to the memory, the processor and the memory being configured to: receive, from a plurality of clients, a plurality of messages, wherein at least two of the messages includes information associated with one or more wireless communication networks; and transmit, to at least one of the clients, client data, at one or more transmission occasions based on the information.

Aspect 8: The server of Aspect 7, wherein the processor and the memory are further configured to: obtain additional information associated with the one or more wireless communication networks and additional clients, select a group of clients among the clients and the additional clients based at least in part on the information and the additional information, and transmit, to the group of clients, the client data.

Aspect 9: The server of Aspect 8, wherein the processor and the memory are configured to select the group of clients with at least one of: a same cell identifier of a serving cell, a same beam identifier of the serving cell, a same quasi-colocation (QCL) information associated with a reference signal of the serving cell, a same medium access control (MAC) address of an access point, or a same network identifier of a network.

Aspect 10: The server according to any one of Aspects 8 or 9, wherein the processor and the memory are configured to obtain the additional information from a database or another server.

Aspect 11: The server according to any one of Aspects 7-10, wherein the processor and the memory are further configured to: obtain additional information associated with the one or more wireless communication networks and additional clients, select a group of clients among the clients and the additional clients based at least in part on the information and the additional information, and transmit, to another server, a schedule indicating the one or more transmission occasions for the group of clients, wherein the server and the other server are time synchronized with each other.

Aspect 12: The server of Aspect 11, wherein the schedule is determined based on session establishment times of the group of clients or round-trip latencies of the group of clients.

Aspect 13: The server according to any one of Aspects 7-12, wherein the processor and the memory are further configured to: initiate generating of the client data at one or more processing occasions, timing of which is based at least in part on the information.

Aspect 14: The server according to any one of Aspects 7-13, wherein the processor and the memory are further configured to initiate transmitting of the client data at the one or more transmission occasions, timing of which is based at least in part on the information.

Aspect 15: The server according to any one of Aspects 7-14, wherein the information includes at least one of: one or more cell identifiers of serving cells of the clients; one or more beam identifiers of the serving cells; quasi-colocation (QCL) information associated with one or more reference signals of the serving cells; one or more medium access control (MAC) addresses of access points serving the clients; or one or more network identifiers of networks serving the clients.

Aspect 16: The server according to any one of Aspects 7-15, wherein the messages are session description protocol (SDP) messages for session initiation protocol (SIP).

Aspect 17: The server according to any one of Aspects 7-16, wherein the processor and the memory are further configured to: receive, from one of the clients, updated information indicating a cell identifier of a serving cell, and initiate generating of the client data at one or more processing occasions, timing of which is based at least in part on the cell identifier.

Aspect 18: The server according to any one of Aspects 7-17, processor and the memory are further configured to: receive, from the clients by the server, a plurality of additional messages including wait times for processing the data at the clients or downlink time spreads of packets arriving at the clients and carrying the data, and initiate generating or transmitting of additional client data at one or more processing occasions or at one or more transmission occasions, timing of which is based at least in part on the wait times or the downlink time spreads.

Aspect 19: The server according to any one of Aspects 7-18, wherein the processor and the memory are further configured to: receive, from the clients, a plurality of additional messages including client information, and render, in response to the additional messages, one or more video frames for at least one of the clients based on the information and the client information, wherein the client data includes the rendered one or more video frames.

Aspect 20: A method of communicating, from a client to a server, information associated with a wireless communication network, comprising: obtaining, by a client from a modem, information associated with a wireless communication network; transmitting, from the client to the server, at an application level, a first message including the information; and receiving, by the client from the server, data at a time determined based on the information.

Aspect 21: The method of Aspect 20, wherein the information includes at least one of: a cell identifier of a serving cell of the client; a beam identifier of the serving cell; quasi-colocation (QCL) information associated with a reference signal of the serving cell; a medium access control (MAC) address of an access point serving the client; or a network identifier of a network serving the client.

Aspect 22: The method according to any one of Aspects 20 or 21, further comprising: handing over, by the client, from a serving cell to a target cell; and based on the handing over, transmitting, from the client to the server, updated information indicating a cell identifier of the target cell.

Aspect 23: A method of transmitting client data, comprising: receiving, from a plurality of clients by a server, a plurality of messages, wherein at least two of the messages includes information associated with one or more wireless communication networks; and transmitting, from the server to at least one of the clients, client data, at one or more transmission occasions based on the information.

Aspect 24: The method of Aspect 23, further comprising: obtaining additional information associated with the one or more wireless communication networks and additional clients; selecting a group of clients among the clients and the additional clients based at least in part on the information and the additional information; wherein transmitting the client data comprises transmitting, from the server to the group of clients, the client data.

Aspect 25: The method according to any one of Aspects 23 or 24, further comprising: obtaining additional information associated with the one or more wireless communication networks and additional clients; selecting a group of clients among the clients and the additional clients based at least in part on the information and the additional information; and transmitting, to another server, a schedule indicating the one or more transmission occasions for the group of clients, wherein the server and the other server are time synchronized with each other.

Aspect 26: The method according to any one of Aspects 23-25, further comprising initiating generating of the client data at one or more processing occasions, timing of which is based at least in part on the information.

Aspect 27: The method according to any one of Aspects 23-26, wherein the information includes at least one of: one or more cell identifiers of serving cells of the clients; one or more beam identifiers of the serving cells; quasi-colocation (QCL) information associated with one or more reference signals of the serving cells; one or more medium access control (MAC) addresses of access points serving the clients; or one or more network identifiers of networks serving the clients.

Aspect 28: The method according to any one of Aspects 23-27, further comprising: receiving, from one of the clients by the server, updated information indicating a cell identifier of a serving cell; and initiating generating of the client data at one or more processing occasions, timing of which is based at least in part on the cell identifier.

Aspect 29: The method according to any one of Aspects 23-28, further comprising: receiving, from the clients by the server, a plurality of additional messages including wait times for processing the data at the clients or downlink time spreads of packets arriving at the clients and carrying the data; and initiating generating or transmitting of additional client data at one or more processing occasions or at one or more transmission occasions, timing of which is based at least in part on the wait times or the downlink time spreads.

Aspect 30: The method according to any one of Aspects 23-29, further comprising: receiving, from the clients by the server, a plurality of additional messages including client information; and in response to the additional messages, rendering, by the server, one or more video frames for at least one of the clients based on the information and the client information, wherein the client data includes the rendered one or more video frames.

Aspect 31: A method of communicating, from a client to a server, information associated with a wireless communication network, comprising: obtaining, by a client from a modem, information associated with a wireless communication network; transmitting, from the client to the server, at an application level, a first message including the information; and receiving, by the client from the server, data at a time determined based on the information.

Aspect 32: The method of Aspect 31, wherein the information includes at least one of: a cell identifier of a serving cell of the client; a beam identifier of the serving cell; quasi-colocation (QCL) information associated with a reference signal of the serving cell; a medium access control (MAC) address of an access point serving the client; or a network identifier of a network serving the client.

Aspect 33: The method according to any one of Aspects 31 or 32, wherein the first message is a session description protocol (SDP) message for session initiation protocol (SIP).

Aspect 34: The method according to any one of Aspects 31-33, further comprising: transmitting, from the client to the server, a second message including a wait time for processing the data at the client or a downlink time spread of packets arriving at the client and carrying the data, wherein the time is further determined based on the second message; and in response to the second message, receiving, by the client from the server, additional data at another time determined based on the information and the second message.

Aspect 35: The method according to any one of Aspects 31-34, further comprising handing over, by the client, from a serving cell to a target cell; and based on the handing over, transmitting, from the client to the server, updated information indicating a cell identifier of the target cell.

Aspect 36: The method according to any one of Aspects 31-35, further comprising: transmitting, from the client to the server, a second message including client information; displaying, by the client, the data as one or more rendered video frames, wherein the data comprises the one or more rendered video frames, and the data is generated based on the client information included in the second message.

Aspect 37: A method of transmitting client data, comprising: receiving, from a plurality of clients by a server, a plurality of messages, wherein at least two of the messages includes information associated with one or more wireless communication networks; and transmitting, from the server to at least one of the clients, client data, at one or more transmission occasions based on the information.

Aspect 38: The method of Aspect 37, further comprising: obtaining additional information associated with the one or more wireless communication networks and additional clients; selecting a group of clients among the clients and the additional clients based at least in part on the information and the additional information; wherein transmitting the client data comprises transmitting, from the server to the group of clients, the client data.

Aspect 39: The method of Aspect 38, wherein selecting the group of clients comprises selecting the group of clients with at least one of: a same cell identifier of a serving cell, a same beam identifier of the serving cell, a same quasi-colocation (QCL) information associated with a reference signal of the serving cell, a same medium access control (MAC) address of an access point, or a same network identifier of a network.

Aspect 40: The method according to any one of Aspects 38 or 39, wherein obtaining the additional information comprises obtaining the additional information from a database or another server.

Aspect 41: The method according to any one of Aspects 37-40, further comprising: obtaining additional information associated with the one or more wireless communication networks and additional clients; selecting a group of clients among the clients and the additional clients based at least in part on the information and the additional information; and transmitting, to another server, a schedule indicating the one or more transmission occasions for the group of clients, wherein the server and the other server are time synchronized with each other.

Aspect 42: The method of Aspect 41, wherein the schedule is determined based on session establishment times of the group of clients or round-trip latencies of the group of clients.

Aspect 43: The method according to any one of Aspects 37-42, further comprising: initiating generating of the client data at one or more processing occasions, timing of which is based at least in part on the information.

Aspect 44: The method according to any one of Aspects 37-43, transmitting the client data comprises initiating transmitting of the client data at the one or more transmission occasions, timing of which is based at least in part on the information.

Aspect 45: The method according to any one of Aspects 37-44, wherein the information includes at least one of: one or more cell identifiers of serving cells of the clients; one or more beam identifiers of the serving cells; quasi-colocation (QCL) information associated with one or more reference signals of the serving cells; one or more medium access control (MAC) addresses of access points serving the clients; or one or more network identifiers of networks serving the clients.

Aspect 46: The method according to any one of Aspects 37-45, wherein the messages are session description protocol (SDP) messages for session initiation protocol (SIP).

Aspect 47: The method according to any one of Aspects 37-46, further comprising: receiving, from one of the clients by the server, updated information indicating a cell identifier of a serving cell; and initiating generating of the client data at one or more processing occasions, timing of which is based at least in part on the cell identifier.

Aspect 48: The method according to any one of Aspects 37-47, further comprising: receiving, from the clients by the server, a plurality of additional messages including wait times for processing the data at the clients or downlink time spreads of packets arriving at the clients and carrying the data; and initiating generating or transmitting of additional client data at one or more processing occasions or at one or more transmission occasions, timing of which is based at least in part on the wait times or the downlink time spreads.

Aspect 49: An apparatus, comprising: a memory comprising computer-executable instructions; one or more processors configured to execute the computer-executable instructions and cause the processing system to perform a method in accordance with any one of Aspects 20-48.

Aspect 50: An apparatus, comprising means for performing a method in accordance with any one of Aspects 20-48.

Aspect 51: A computer-readable medium comprising computer-executable instructions that, when executed by one or more processors of a processing system, cause the processing system to perform a method in accordance with any one of Aspects 20-48.

Aspect 52: A computer program product embodied on a computer-readable storage medium comprising code for performing a method in accordance with any one of Aspects 20-48.