Latency analytics and reporting

Abstract

An access point (AP) may include one or more processors. The one or more processors may be configured to determine one or more latency metrics of one or more wireless traffic flows that are received from a first device associated with the AP. The one or more processors may be configured to generate a first frame including the one or more latency metrics to report the one or more latency metrics to the first device. The one or more processors may be configured to wirelessly transmit, via a transmitter, the generated first frame to the first device.

Description

[0001] Atorney Docket No.: 121439-1421 (FB-521PC)

[0002] LATENCY ANALYTICS AND REPORTING CROSS-REFERENCE TO RELATED APPLICATION

[0003] This application claims priority to U.S. Provisional Patent Application No. 63 / 688.809 filed on August 29, 2025, which is incorporated by reference herein in its entirety for all purposes.

[0004] FIELD OF DISCLOSURE

[0005] The present disclosure generally relates to telecommunications, and more particularly, to latency analytics and reporting for mixed reality traffic flows.

[0006] BACKGROUND

[0007] Latency reporting is increasingly used in wireless communication systems, with support expanding across a variety of devices and network configurations. Latency of data transmissions can be especially important to user experience of mixed reality (MR) devices, as high latency can impair responsiveness of MR devices, which can disrupt realism and interactivity' of a rendered scene. Latency reporting may allow dynamic adaptation of scheduling and resource allocation to maintain quality of service under varying network conditions.

[0008] SUMMARY

[0009] Various embodiments disclosed herein relate to an access point (AP) including one or more processors. In some embodiments, the one or more processors may be configured to determine one or more latency metrics of one or more wireless traffic flows that are received by a first device associated with the AP. Tn some embodiments, the one or more processors may be configured to generate a first frame including the one or more latency metrics to report the one or more latency metrics to the first device. In some embodiments, the one or more processors may be configured to wirelessly transmit, via a transmitter, the generated first frame to the first device.

[0010] In some embodiments, the one or more latency metrics may' include at least one of latency statistics, queue size metrics, received signal strength indicator (RSSI) metrics, or transmitted power metrics.

[0011] In some embodiments, as part of generating the first frame, the one or more processors may be configured to determine a latency type among a plurality of latency ty pes, determine a latency value of the one or more wireless traffic flows according to the latencytype, and set a first field and a second field of the first frame to indicate the latency ty pe and the latency value, respectively.

[0012] In some embodiments, the first field may be a bitmap in which each bit is set to

[0013] 1

[0014] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) indicate a corresponding latency type among the plurality of latency types.

[0015] In some embodiments, as part of generating the first frame, the one or more processors may be configured to determine whether the reporting is solicited or unsolicited, and set a third field to a first value indicating that the reporting is solicited, or a second value indicating that the reporting is unsolicited.

[0016] In some embodiments, the one or more processors may be configured to determine that the one or more latency metrics exceed one or more thresholds, and set the third field to the second value.

[0017] In some embodiments, the one or more processors may be configured to receive, from the first device, a third frame to solicit the reporting, and set the third field to the first value.

[0018] In some embodiments, as part of generating the first frame, the one or more processors may be further configured to generate a second frame including a field set to a value indicating to support reporting of latency metrics, and wirelessly transmit, via the transmitter, the generated second frame.

[0019] In some embodiments, as part of generating the first frame, the one or more processors may be further configured to determine that the one or more latency metrics include queue size metrics, set a fourth field to a value to indicate that the one or more latency metrics include queue size metrics, and set a fifth field to a value of the queue size metrics.

[0020] In some embodiments, as part of generating the first frame, the one or more processors may be further configured to determine that the one or more latency metrics include received signal strength indicator (RSSI) metrics, or transmitted power metric, set a sixth field to a value to indicate that the one or more latency metrics include RSSI metrics or transmitted power metrics, and set a seventh field to a value of the RSSI metrics or the transmitted power metrics.

[0021] Various embodiments disclosed herein are related to a method, including determining, by one or more processors of an access point (AP), one or more latency metrics of one or more wireless traffic flows that are received by a first device associated with the AP. The method may include generating, by the one or more processors of the AP, a first frame including the one or more latency metrics to report the one or more latency metrics to the first device. The method may include wirelessly transmitting, via a transmitter, the generated first frame to the first device.

[0022] BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings are not intended to be drawn to scale. Like reference

[0024] 2

[0025] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) numbers and designations in the various drawings indicate like elements. For purposes of clarity, not every component can be labeled in even’ drawing.

[0026] FIG. 1 is a diagram of an example wireless communication system, according to an example implementation of the present disclosure.

[0027] FIG. 2 is a diagram of a console and a head wearable display for presenting augmented reality or virtual reality, according to an example implementation of the present disclosure.

[0028] FIG. 3 is a diagram of a head wearable display, according to an example implementation of the present disclosure.

[0029] FIG. 4 is a block diagram of a computing environment according to an example implementation of the present disclosure.

[0030] FIG. 5 is a block diagram of a system in in which latency reporting can be implemented, according to an example implementation of the present disclosure.

[0031] FIGS. 6A-6D is a diagram showing example fields in an information element for latency reporting, according to an example implementation of the present disclosure.

[0032] FIG. 7 is a diagram showing an example sub element in an information element for latency reporting, according to an example implementation of the present disclosure.

[0033] FIG. 8 is a diagram showing an example field in a UHR capabilities element for latency reporting, according to an example implementation of the present disclosure.

[0034] FIG. 9 is a diagram showing a frame for initiating latency reporting, according to an example implementation of the present disclosure.

[0035] FIG. 10 is a flowchart show ing an example method of latency reporting, according to an example implementation of the present disclosure.

[0036] DETAILED DESCRIPTION

[0037] Before turning to the figures, which illustrate certain embodiments in detail, it should be understood that the present disclosure is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology used herein is for the purpose of description only and should not be regarded as limiting.

[0038] FIG. 1 illustrates an example wireless communication system 100. The wireless communication system 100 may include a base station 110 (also referred to as “a wireless communication node 110” or “a station 110”) and one or more user equipment (UEs) 120 (also referred to as “wireless communication devices 120” or “terminal devices 120”). The base station 110 and the UEs 120 may communicate through wireless commination links

[0039] 3

[0040] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0041] 130A, 130B, 130C. The wireless communication link 130 may be a cellular communication link conforming to 3G, 4G, 5G or other cellular communication protocols or a Wi-Fi communication protocol. In one example, the wireless communication link 130 supports, employs or is based on an orthogonal frequency division multiple access (OFDMA). In one aspect, the UEs 120 are located within a geographical boundary with respect to the base station 110, and may communicate with or through the base station 110. In some embodiments, the wireless communication system 100 includes more, fewer, or different components than shown in FIG. 1. For example, the wireless communication system 100 may include one or more additional base stations 110 than show n in FIG. 1.

[0042] In some embodiments, the UE 120 may be a user device such as a mobile phone, a smart phone, a personal digital assistant (PDA), tablet, laptop computer, wearable computing device, etc. Each UE 120 may communicate with the base station 110 through a corresponding communication link 130. For example, the UE 120 may transmit data to a base station 110 through a wireless communication link 130, and receive data from the base station 110 through the wireless communication link 130. Example data may include audio data, image data, text, etc. Communication or transmission of data by the UE 120 to the base station 110 may be referred to as an uplink communication. Communication or reception of data by the UE 120 from the base station 110 may be referred to as a downlink communication. In some embodiments, the UE 120A includes a wireless interface 122, a processor 124, a memory device 126, and one or more antennas 128. These components may be embodied as hardware, software, firmware, or a combination thereof. In some embodiments, the UE 120 A includes more, fewer, or different components than shown in FIG. 1. For example, the UE 120 may include an electronic display and / or an input device. For example, the UE 120 may include additional antennas 128 and wireless interfaces 122 than shown in FIG. 1.

[0043] The antenna 128 may be a component that receives a radio frequency (RF) signal and / or transmit a RF signal through a wireless medium. The RF signal may be at a frequency between 200 MHz to 100 GHz. The RF signal may have packets, symbols, or frames corresponding to data for communication. The antenna 128 may be a dipole antenna, a patch antenna, a ring antenna, or any suitable antenna for wireless communication. In one aspect, a single antenna 128 is utilized for both transmitting the RF signal and receiving the RF signal. In one aspect, different antennas 128 are utilized for transmitting the RF signal and receiving the RF signal. In one aspect, multiple antennas 128 are utilized to support multiple-in. multiple-out (MIMO) communication.

[0044] 4

[0045] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0046] The wireless interface 122 includes or is embodied as a transceiver for transmitting and receiving RF signals through a wireless medium. The wireless interface 122 may communicate with a wireless interface 112 of the base station 1 10 through a wireless communication link 130A. In one configuration, the wireless interface 122 is coupled to one or more antennas 128. In one aspect, the wireless interface 122 may receive the RF signal at the RF frequency received through antenna 128, and downconvert the RF signal to a baseband frequency (e.g., 0~l GHz). The wireless interface 122 may provide the downconverted signal to the processor 124. In one aspect, the wireless interface 122 may receive a baseband signal for transmission at a baseband frequency from the processor 124, and upconvert the baseband signal to generate a RF signal. The wireless interface 122 may transmit the RF signal through the antenna 128.

[0047] The processor 124 is a component that processes data. The processor 124 may be embodied as field programmable gate array (FPGA), application specific integrated circuit (ASIC), a logic circuit, etc. The processor 124 may obtain instructions from the memory device 126, and executes the instructions. In one aspect, the processor 124 may receive downconverted data at the baseband frequency from the wireless interface 122, and decode or process the downconverted data. For example, the processor 124 may generate audio data or image data according to the downconverted data, and present an audio indicated by the audio data and / or an image indicated by the image data to a user of the UE 120 A. In one aspect, the processor 124 may generate or obtain data for transmission at the baseband frequency, and encode or process the data. For example, the processor 124 may encode or process image data or audio data at the baseband frequency, and provide the encoded or processed data to the wireless interface 122 for transmission.

[0048] The memory device 126 is a component that stores data. The memory device 126 may be embodied as random access memory (RAM), flash memory, read only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, a hard disk, a removable disk, a CD- ROM, or any device capable for storing data. The memory device 126 may be embodied as a non-transitory computer readable medium storing instructions executable by the processor 124 to perform various functions of the UE 120A disclosed herein. In some embodiments, the memory device 126 and the processor 124 are integrated as a single component.

[0049] In some embodiments, each of the UEs 120B. .. 120N includes similar components of the UE 120 A to communicate with the base station 110. Thus, detailed description of duplicated portion thereof is omitted herein for the sake of brevity.

[0050] 5

[0051] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0052] In some embodiments, the base station 110 may be an evolved node B (eNB), a serving eNB. a target eNB, a femto station, or a pico station. The base station 110 may be communicatively coupled to another base station 110 or other communication devices through a wireless communication link and / or a wired communication link. The base station 110 may receive data (or a RF signal) in an uplink communication from a UE 120. Additionally or alternatively, the base station 110 may provide data to another UE 120, another base station, or another communication device. Hence, the base station 110 allows communication among UEs 120 associated with the base station 110, or other UEs associated with different base stations. In some embodiments, the base station 110 includes a wireless interface 112, a processor 114. a memory device 116, and one or more antennas 118. These components may be embodied as hardware, software, firmware, or a combination thereof. In some embodiments, the base station 110 includes more, fewer, or different components than shown in FIG. 1. For example, the base station 110 may include an electronic display and / or an input device. For example, the base station 110 may include additional antennas 118 and wireless interfaces 112 than shown in FIG. 1.

[0053] The antenna 118 may be a component that receives a radio frequency (RF) signal and / or transmit a RF signal through a wireless medium. The antenna 118 may be a dipole antenna, a patch antenna, a ring antenna, or any suitable antenna for wireless communication. In one aspect, a single antenna 118 is utilized for both transmitting the RF signal and receiving the RF signal. In one aspect, different antennas 118 are utilized for transmitting the RF signal and receiving the RF signal. In one aspect, multiple antennas 1 18 are utilized to support multiple-in, multiple-out (MIMO) communication.

[0054] The wireless interface 112 includes or is embodied as a transceiver for transmitting and receiving RF signals through a wireless medium. The wireless interface 112 may communicate with a wireless interface 122 of the UE 120 through a wireless communication link 130. In one configuration, the wireless interface 112 is coupled to one or more antennas 118. In one aspect, the wireless interface 112 may receive the RF signal at the RF frequency- received through antenna 118, and downconvert the RF signal to a baseband frequency (e.g.. 0~l GHz). The wireless interface 112 may provide the downconverted signal to the processor 124. In one aspect, the wireless interface 122 may receive a baseband signal for transmission at a baseband frequency from the processor 114, and upconvert the baseband signal to generate a RF signal. The wireless interface 112 may transmit the RF signal through the antenna 118.

[0055] The processor 114 is a component that processes data. The processor 114 may be

[0056] 6

[0057] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) embodied as FPGA, ASIC, a logic circuit, etc. The processor 114 may obtain instructions from the memory’ device 116, and executes the instructions. In one aspect, the processor 114 may receive downconverted data at the baseband frequency from the wireless interface 112, and decode or process the downconverted data. For example, the processor 114 may generate audio data or image data according to the downconverted data. In one aspect, the processor 114 may generate or obtain data for transmission at the baseband frequency, and encode or process the data. For example, the processor 114 may encode or process image data or audio data at the baseband frequency, and provide the encoded or processed data to the wireless interface 112 for transmission. In one aspect, the processor 114 may set, assign, schedule, or allocate communication resources for different UEs 120. For example, the processor 114 may set different modulation schemes, time slots, channels, frequency bands, etc. for UEs 120 to avoid interference. The processor 114 may generate data (or UL CGs) indicating configuration of communication resources, and provide the data (or UL CGs) to the wireless interface 112 for transmission to the UEs 120.

[0058] The memory device 116 is a component that stores data. The memory device 116 may be embodied as RAM, flash memory, ROM, EPROM, EEPROM, registers, a hard disk, a removable disk, a CD-ROM, or any device capable for storing data. The memory device 116 may be embodied as a non-transi tory computer readable medium storing instructions executable by the processor 114 to perform various functions of the base station 110 disclosed herein. In some embodiments, the memory device 116 and the processor 114 are integrated as a single component.

[0059] In some embodiments, communication between the base station 110 and the UE 120 is based on one or more layers of Open Systems Interconnection (OSI) model. The OSI model may include layers including: a physical layer, a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Resource Control (RRC) layer, a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and other layer.

[0060] FIG. 2 is a block diagram of an example artificial reality system environment 200. In some embodiments, the artificial reality system environment 200 includes a HWD 250 worn by a user, and a console 210 providing content of artificial reality (e g., augmented reality, virtual reality, mixed reality) to the HWD 250. Each of the HWD 250 and the console 210 may be a separate UE 120. The HWD 250 may be referred to as, include, or be part of a head mounted display (HMD), head mounted device (HMD), head wearable device (HWD), head worn display (HWD) or head worn device (HWD). The HWD 250 may detect its location

[0061] 7

[0062] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) and / or orientation of the HWD 250 as well as a shape, location, and / or an orientation of the body / hand / face of the user, and provide the detected location / or orientation of the HWD 250 and / or tracking information indicating the shape, location, and / or orientation of the body / hand / face to the console 210. The console 210 may generate image data indicating an image of the artificial reality according to the detected location and / or orientation of the HWD 250, the detected shape, location and / or orientation of the body / hand / face of the user, and / or a user input for the artificial reality, and transmit the image data to the HWD 250 for presentation. In some embodiments, the artificial reality system environment 200 includes more, fewer, or different components than shown in FIG. 2. In some embodiments, functionality of one or more components of the artificial reality system environment 200 can be distributed among the components in a different manner than is described here. For example, some of the functionality of the console 210 may be performed by the HWD 250. For example, some of the functionality of the HWD 250 may be performed by the console 210. In some embodiments, the console 210 is integrated as part of the HWD 250.

[0063] In some embodiments, the HWD 250 is an electronic component that can be worn by a user and can present or provide an artificial reality experience to the user. The HWD 250 may render one or more images, video, audio, or some combination thereof to provide the artificial reality experience to the user. In some embodiments, audio is presented via an external device (e.g., speakers and / or headphones) that receives audio information from the HWD 250. the console 210, or both, and presents audio based on the audio information. In some embodiments, the HWD 250 includes sensors 255, a wireless interface 265, a processor 270, an electronic display 275, a lens 280, and a compensator 285. These components may operate together to detect a location of the HWD 250 and a gaze direction of the user wearing the HWD 250, and render an image of a view within the artificial reality corresponding to the detected location and / or orientation of the HWD 250. In other embodiments, the HWD 250 includes more, fewer, or different components than shown in FIG. 2.

[0064] In some embodiments, the sensors 255 include electronic components or a combination of electronic components and software components that detect a location and an orientation of the HWD 250. Examples of the sensors 255 can include: one or more imaging sensors, one or more accelerometers, one or more gyroscopes, one or more magnetometers, or another suitable type of sensor that detects motion and / or location. For example, one or more accelerometers can measure translational movement (e.g.. forward / back, up / down, left / right) and one or more gyroscopes can measure rotational movement (e.g., pitch, yaw, roll). In some embodiments, the sensors 255 detect the translational movement and the

[0065] 8

[0066] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) rotational movement, and determine an orientation and location of the HWD 250. In one aspect, the sensors 255 can detect the translational movement and the rotational movement with respect to a previous orientation and location of the HWD 250, and determine anew orientation and / or location of the HWD 250 by accumulating or integrating the detected translational movement and / or the rotational movement. Assuming for an example that the HWD 250 is oriented in a direction 25 degrees from a reference direction, in response to detecting that the HWD 250 has rotated 20 degrees, the sensors 255 may determine that the HWD 250 now- faces or is oriented in a direction 45 degrees from the reference direction. Assuming for another example that the HWD 250 w as located two feet aw ay from a reference point in a first direction, in response to detecting that the HWD 250 has moved three feet in a second direction, the sensors 255 may determine that the HWD 250 is now located at a vector multiplication of the two feet in the first direction and the three feet in the second direction.

[0067] In some embodiments, the sensors 255 include eye trackers. The eye trackers may include electronic components or a combination of electronic components and software components that determine a gaze direction of the user of the HWD 250. In some embodiments, the HWD 250, the console 210 or a combination of them may incorporate the gaze direction of the user of the HWD 250 to generate image data for artificial reality. In some embodiments, the eye trackers include two eye trackers, where each eye tracker captures an image of a corresponding eye and determines a gaze direction of the eye. In one example, the eye tracker determines an angular rotation of the eye, a translation of the eye, a change in the torsion of the eye, and / or a change in shape of the eye, according to the captured image of the eye, and determines the relative gaze direction with respect to the HWD 250, according to the determined angular rotation, translation and the change in the torsion of the eye. In one approach, the eye tracker may shine or project a predetermined reference or structured pattern on a portion of the eye, and capture an image of the eye to analyze the pattern projected on the portion of the eye to determine a relative gaze direction of the eye with respect to the HWD 250. In some embodiments, the eye trackers incorporate the orientation of the HWD 250 and the relative gaze direction with respect to the HWD 250 to determine a gate direction of the user. Assuming for an example that the HWD 250 is oriented at a direction 30 degrees from a reference direction, and the relative gaze direction of the HWD 250 is -10 degrees (or 350 degrees) with respect to the HWD 250, the eye trackers may determine that the gaze direction of the user is 20 degrees from the reference direction. In some embodiments, a user of the HWD 250 can configure the HWD 250 (e.g., via user

[0068] 9

[0069] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) settings) to enable or disable the eye trackers. In some embodiments, a user of the HWD 250 is prompted to enable or disable the eye trackers.

[0070] In some embodiments, the wireless interface 265 includes an electronic component or a combination of an electronic component and a software component that communicates with the console 210. The wireless interface 265 may be or correspond to the wireless interface 122. The wireless interface 265 may communicate with a wireless interface 215 of the console 210 through a wireless communication link through the base station 110. Through the communication link, the wireless interface 265 may transmit to the console 210 data indicating the determined location and / or orientation of the HWD 250, and / or the determined gaze direction of the user. Moreover, through the communication link, the wireless interface 265 may receive from the console 210 image data indicating or corresponding to an image to be rendered and additional data associated with the image.

[0071] In some embodiments, the processor 270 includes an electronic component or a combination of an electronic component and a software component that generates one or more images for display, for example, according to a change in view of the space of the artificial reality. In some embodiments, the processor 270 is implemented as a part of the processor 124 or is communicatively coupled to the processor 124. In some embodiments, the processor 270 is implemented as a processor (or a graphical processing unit (GPU)) that executes instructions to perform various functions described herein. The processor 270 may receive, through the wireless interface 265, image data describing an image of artificial reality to be rendered and additional data associated with the image, and render the image to display through the electronic display 275. In some embodiments, the image data from the console 210 may be encoded, and the processor 270 may decode the image data to render the image. In some embodiments, the processor 270 receives, from the console 210 in additional data, object information indicating virtual objects in the artificial reality space and depth information indicating depth (or distances from the HWD 250) of the virtual objects. In one aspect, according to the image of the artificial reality, object information, depth information from the console 210, and / or updated sensor measurements from the sensors 255, the processor 270 may perform shading, reprojection, and / or blending to update the image of the artificial reality' to correspond to the updated location and / or orientation of the HWD 250. Assuming that a user rotated his head after the initial sensor measurements, rather than recreating the entire image responsive to the updated sensor measurements, the processor 270 may generate a small portion (e.g., 10 %) of an image corresponding to an updated view within the artificial reality according to the updated sensor measurements, and append the

[0072] 10

[0073] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) portion to the image in the image data from the console 210 through reprojection. The processor 270 may perform shading and / or blending on the appended edges. Hence, without recreating the image of the artificial reality according to the updated sensor measurements, the processor 270 can generate the image of the artificial reality.

[0074] In some embodiments, the electronic display 275 is an electronic component that displays an image. The electronic display 275 may. for example, be a liquid crystal display or an organic light emitting diode display. The electronic display 275 may be a transparent display that allows the user to see through. In some embodiments, when the HWD 250 is worn by a user, the electronic display 275 is located proximate (e.g., less than 3 inches) to the user’s eyes. In one aspect, the electronic display 275 emits or projects light towards the user’s eyes according to image generated by the processor 270.

[0075] In some embodiments, the lens 280 is a mechanical component that alters received light from the electronic display 275. The lens 280 may magnify the light from the electronic display 275, and correct for optical error associated with the light. The lens 280 may be a Fresnel lens, a convex lens, a concave lens, a filter, or any suitable optical component that alters the light from the electronic display 275. Through the lens 280, light from the electronic display 275 can reach the pupils, such that the user can see the image displayed by the electronic display 275, despite the close proximity of the electronic display 275 to the eyes.

[0076] In some embodiments, the compensator 285 includes an electronic component or a combination of an electronic component and a software component that performs compensation to compensate for any distortions or aberrations. In one aspect, the lens 280 introduces optical aberrations such as a chromatic aberration, a pin-cushion distortion, barrel distortion, etc. The compensator 285 may determine a compensation (e.g., predistortion) to apply to the image to be rendered from the processor 270 to compensate for the distortions caused by the lens 280, and apply the determined compensation to the image from the processor 270. The compensator 285 may provide the predistorted image to the electronic display 275.

[0077] In some embodiments, the console 210 is an electronic component or a combination of an electronic component and a software component that provides content to be rendered to the HWD 250. In one aspect, the console 210 includes a wireless interface 215 and a processor 230. These components may operate together to determine a view (e.g., a FOV of the user) of the artificial reality corresponding to the location of the HWD 250 and the gaze direction of the user of the HWD 250, and can generate image data indicating an image of the

[0078] 11

[0079] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) artificial reality corresponding to the determined view. In addition, these components may operate together to generate additional data associated with the image. Additional data may be information associated with presenting or rendering the artificial reality other than the image of the artificial reality. Examples of additional data include, hand model data, mapping information for translating a location and an orientation of the HWD 250 in a physical space into a virtual space (or simultaneous localization and mapping (SLAM) data), eye tracking data, motion vector information, depth information, edge information, object information, etc. The console 210 may provide the image data and the additional data to the HWD 250 for presentation of the artificial reality. In other embodiments, the console 210 includes more, fewer, or different components than shown in FIG. 2. In some embodiments, the console 210 is integrated as part of the HWD 250.

[0080] In some embodiments, the wireless interface 215 is an electronic component or a combination of an electronic component and a software component that communicates with the HWD 250. The wireless interface 215 may be or correspond to the wireless interface 122. The wireless interface 215 may be a counterpart component to the wireless interface 265 to communicate through a communication link (e.g., wireless communication link). Through the communication link, the wireless interface 215 may receive from the HWD 250 data indicating the determined location and / or orientation of the HWD 250, and / or the determined gaze direction of the user. Moreover, through the communication link, the wireless interface 215 may transmit to the HWD 250 image data describing an image to be rendered and additional data associated with the image of the artificial reality’.

[0081] The processor 230 can include or correspond to a component that generates content to be rendered according to the location and / or orientation of the HWD 250. In some embodiments, the processor 230 is implemented as a part of the processor 124 or is communicatively coupled to the processor 124. In some embodiments, the processor 230 may incorporate the gaze direction of the user of the HWD 250. In one aspect, the processor 230 determines a view of the artificial reality according to the location and / or orientation of the HWD 250. For example, the processor 230 maps the location of the HWD 250 in a physical space to a location within an artificial reality space, and determines a view of the artificial reality' space along a direction corresponding to the mapped orientation from the mapped location in the artificial reality space. The processor 230 may generate image data describing an image of the determined view of the artificial reality space, and transmit the image data to the HWD 250 through the wireless interface 215. In some embodiments, the processor 230 may generate additional data including motion vector information, depth

[0082] 12

[0083] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) information, edge information, object information, hand model data, etc., associated with the image, and transmit the additional data together with the image data to the HWD 250 through the wireless interface 215. The processor 230 may encode the image data describing the image, and can transmit the encoded data to the HWD 250. In some embodiments, the processor 230 generates and provides the image data to the HWD 250 periodically (e.g., every 11 ms).

[0084] In one aspect, the process of detecting the location of the HWD 250 and the gaze direction of the user wearing the HWD 250, and rendering the image to the user should be performed within a frame time (e.g., 11 ms or 16 ms). A latency between a movement of the user wearing the HWD 250 and an image displayed corresponding to the user movement can cause judder, which may result in motion sickness and can degrade the user experience. In one aspect, the HWD 250 and the console 210 can prioritize communication for AR / VR, such that the latency between the movement of the user wearing the HWD 250 and the image displayed corresponding to the user movement can be presented within the frame time (e.g., 11 ms or 16 ms) to provide a seamless experience.

[0085] FIG. 3 is a diagram of a HWD 250, in accordance with an example embodiment. In some embodiments, the HWD 250 includes a front rigid body 305 and a band 310. The front rigid body 305 includes the electronic display 275 (not shown in FIG. 3), the lens 280 (not shown in FIG. 3), the sensors 255, the wireless interface 265, and the processor 270. In the embodiment shown by FIG. 3. the wireless interface 265. the processor 270, and the sensors 255 are located within the front rigid body 205, and may not be visible externally. In other embodiments, the HWD 250 has a different configuration than shown in FIG. 3. For example, the wireless interface 265, the processor 270, and / or the sensors 255 may be in different locations than shown in FIG. 3.

[0086] Various operations described herein can be implemented on computer systems. FIG. 4 shows a block diagram of a representative computing system 414 usable to implement the present disclosure. In some embodiments, the source devices 110, the sink device 120, the console 210, the HWD 250 are implemented by the computing system 414. Computing system 414 can be implemented, for example, as a consumer device such as a smartphone, other mobile phone, tablet computer, wearable computing device (e.g., smart w atch, eyeglasses, head wearable display), desktop computer, laptop computer, or implemented with distributed computing devices. The computing system 414 can be implemented to provide VR, AR, MR experience. In some embodiments, the computing system 414 can include conventional computer components such as processors 416, storage device 418, network

[0087] 13

[0088] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) interface 420, user input device 422, and user output device 424.

[0089] Network interface 420 can provide a connection to a wide area network (e.g.. the Internet) to which WAN interface of a remote server system is also connected. Network interface 420 can include a wired interface (e.g., Ethernet) and / or a wireless interface implementing various RF data communication standards such as Wi-Fi, Bluetooth, or cellular data network standards (e.g.. 3G, 4G, 5G, 60 GHz, LTE, etc.).

[0090] The network interface 420 may include a transceiver to allow the computing system 414 to transmit and receive data from a remote device using a transmitter and receiver. The transceiver may be configured to support transmission / reception supporting industry standards that enables bi-directional communication. An antenna may be attached to transceiver housing and electrically coupled to the transceiver. Additionally or alternatively, a multi-antenna array may be electrically coupled to the transceiver such that a plurality of beams pointing in distinct directions may facilitate in transmitting and / or receiving data.

[0091] A transmitter may be configured to wirelessly transmit frames, slots, or symbols generated by the processor unit 416. Similarly, a receiver may be configured to receive frames, slots or symbols and the processor unit 416 may be configured to process the frames. For example, the processor unit 416 can be configured to determine a type of frame and to process the frame and / or fields of the frame accordingly.

[0092] User input device 422 can include any device (or devices) via which a user can provide signals to computing system 414; computing system 414 can interpret the signals as indicative of particular user requests or information. User input device 422 can include any or all of a keyboard, touch pad, touch screen, mouse or other pointing device, scroll wheel, click wheel, dial, button, switch, keypad, microphone, sensors (e.g., a motion sensor, an eye tracking sensor, etc.), and so on.

[0093] User output device 424 can include any device via which computing system 414 can provide information to a user. For example, user output device 424 can include a display to display images generated by or delivered to computing system 414. The display can incorporate various image generation technologies, e.g., a liquid crystal display (LCD), lightemitting diode (LED) including organic light-emitting diodes (OLED). projection system, cathode ray tube (CRT), or the like, together with supporting electronics (e.g., digital-to- analog or analog-to-digital converters, signal processors, or the like). A device such as a touchscreen that function as both input and output device can be used. Output devices 424 can be provided in addition to or instead of a display. Examples include indicator lights, speakers, tactile ‘'display” devices, printers, and so on.

[0094] 14

[0095] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0096] Some implementations include electronic components, such as microprocessors, storage and memory that store computer program instructions in a computer readable storage medium (e.g., non-transitory computer readable medium). Many of the features described in this specification can be implemented as processes that are specified as a set of program instructions encoded on a computer readable storage medium. When these program instructions are executed by one or more processors, they cause the processors to perform various operation indicated in the program instructions. Examples of program instructions or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter. Through suitable programming, processor 416 can provide various functionality for computing system 414, including any of the functionality described herein as being performed by a server or client, or other functionality associated with message management services.

[0097] It will be appreciated that computing system 414 is illustrative and that variations and modifications are possible. Computer systems used in connection with the present disclosure can have other capabilities not specifically described here. Further, while computing system 414 is described with reference to particular blocks, it is to be understood that these blocks are defined for convenience of description and are not intended to imply a particular physical arrangement of component parts. For instance, different blocks can be located in the same facility, in the same server rack, or on the same motherboard. Further, the blocks need not correspond to physically distinct components. Blocks can be configured to perform various operations, e.g., by programming a processor or providing appropriate control circuitry, and various blocks might or might not be reconfigurable depending on how the initial configuration is obtained. Implementations of the present disclosure can be realized in a variety of apparatus including electronic devices implemented using any combination of circuitry and software.

[0098] In some embodiments, the disclosed technology relates to latency analytics and reporting for mixed reality traffic flows. Latency of traffic may be an important metric for mixed reality (MR) devices, such as wearable headsets. For example, large latency times may cause issues such as delay in graphics and poor responsiveness to user input that can negatively impact user experience. In some examples, devices can measure round trip time (RTT) latency to evaluate a state of a connection. For example, devices can measure RTT time to determine whether remedial actions, such as switching to another access point, should be taken. Devices may periodically measure RTT latency from device to a remote server

[0099] 15

[0100] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0101] (e.g., and passing through an access point) in a periodic manner. However, the RTT latency may include both last-hop Wi-Fi components (e.g., a downlink and uplink delay on the Wi-Fi network between the device and the access point) and the backhaul components (e.g., a downlink and uplink delay on a connection between the access point and the remote server). While the uplink delay on the Wi-Fi network may be measured by a chipset of the device, the downlink delay may not. For example, the device may lack transmission parameters, such as an initial time of transmission, used to determine the downlink delay. The AP may be able to determine the downlink delay on the Wi-Fi network. For example, the AP can determine the downlink delay based on a time difference between transmitting a data packet to the device and receiving an acknowledgement frame. How ever, APs may not be required to determine and / or report this downlink delay on Wi-Fi networks to associated devices under standard signaling methods.

[0102] Disclosed herein are systems and methods for generating and requesting latency reports. For example, according to the systems and methods, a frame may be generated that indicates a latency report including one or more latency metrics (e.g.. latency statistics, RSSI, and / or the like). The latency metrics can be included in an information element, which can be incorporated into various types of frames, such as a management frame or a control frame. According to the systems and methods, the device (e.g., non-AP station) may request the latency report from the AP. For example, the device can transmit a frame that solicits a response to request the latency report. Additionally, or alternatively, the AP can transmit a frame that indicates it supports latency reporting to the device. Based on the latency metrics included in the frame, the device can evaluate the downlink connection between the AP and the device.

[0103] Latency analytics on the downlink connection between the AP and the device may be useful for various operations of the device. For example, based on the downlink delay on this connection, the device can estimate RTT latency when backhaul components are stable without sending a packet roundtrip between the device and the remote server. As another example, the device can determine an amount of latency that offloading a task (e.g., such as executing an artificial intelligence model) to an external server would introduce based at least on the uplink and downlink delay over the Wi-Fi network. The device can then determine whether to offload the task to conserve battery pow er of the device based on whether the delay is acceptable or not (e.g., is below a threshold). As yet another example, the device can determine whether the downlink connection is a source of jitter based on the downlink delay. In the described example, other latency metrics, such as queue size or transmission power,

[0104] 16

[0105] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) may also be used to evaluate the downlink connection between the AP and the device. As a result, the described systems and methods can be used to reduce latency of transmissions between a device and an AP by informing the device on latency metrics of the downlink connection between the AP and the device. This may allows the device to optimize its operations based on current netw ork conditions, thereby reducing latency of transmissions.

[0106] The subject technology includes a number of advantageous features. For example, the disclosed solution, if adopted by Wi-Fi standards bodies (e.g., IEEE and Wi-Fi Alliance), will enhance Wi-Fi analytics and reporting framework by requiring APs to implement methods to provide such analytics and reports to devices, enhancing a key aspect of Wi-Fi ecosystem support for MR use cases.

[0107] It is to be understood that the present disclosure includes examples of the subject technology and does not limit the scope of the included clauses. Various aspects of the subject technology will now be disclosed according to particular but non-limiting examples. Various embodiments described in the present disclosure may be carried out in different ways and variations, and in accordance with a desired application or implementation.

[0108] FIG. 5 is a block diagram of a system 500 in in which latency reporting can be implemented, according to an example implementation of the present disclosure. The system 500 may include a device 502 , an access point (AP) 504, and a network server 506. The AP 504 can transmit downlink communications 550 to the device 502, and the device 502 can transmit uplink communications 552 to the AP 504. The AP 504 can transmit uplink communications 556 to the network server 506, and the network server 506 can transmit downlink communications 554 to the AP 504. The device 502 and the AP 504 may be similar to the devices components, elements, or hardware described above with reference to FIG. 1 - FIG. 4. For example, the device 502 may be similar to UEs 120, console 210, head wearable display 250, or any other type or form of user equipment. As another example, the AP 504 may be similar to base station 110, or any other type or form of access point. The device 502 and the AP 504 may include components, elements, hardware, etc. similar to the devices described above, such as processor(s) 124, memory 126, etc.

[0109] The device 502 may be a non-AP station that transmits and receives data from the AP 504. For example, the device 502 may be a mixed reality (MR) device that receives data associated with a virtual reality, such as graphics or audio data, from the AP 504 and transmits sensor data, such as data reflecting user movement, to the AP 504. In an example, the device 502 may display a virtual reality environment hosted by the network server 506. In

[0110] 17

[0111] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) this example, the network server 506 may render and stream the virtual environment to the device 502 in real time, while also processing user input (e.g., such as sensor data from the device 502) and updating the shared virtual world accordingly. Accordingly, the device 502 may display data managed in real time by the network server 506. As a result, latency in transmissions from the network server 506 may greatly affect user experience of a user interacting with the device 502.

[0112] The AP 504 may be device that enables connection to a network. For example, the AP 504 may generate a Wi-Fi network by broadcasting a wireless signal that allows nearby devices, such as device 502, to connect to a network. The AP may transmit information via a wireless transmitter, such as a such as a radio frequency (RF) module or Wi-Fi transceiver. In some examples, the AP 504 may manage communication to associated UEs, including the device 502. For example, the AP 504 can manage transmissions over the Wi-Fi network to maintain optimal performance of associated UEs. Parameters of transmissions that the AP 504 can manage can include channel selection, transmission power, data rate adaptation, traffic prioritization, and scheduling of transmission opportunities. The AP 504 may manage these parameters to reduce interference and / or reduce latency of transmissions. As an example, based on determining the device 502 is experiencing a threshold level of latency, the AP 504 can take remedial actions such as adjusting parameters of communications 550 and / or 552.

[0113] The network server 506 may be a remote computing system that hosts and manages data provided to the device 502. For example, the network server 506 may host and manage a virtual reality environment provided to device 502. Hosting and managing the state of the virtual reality environment can include rendering graphics, processing audio, updating the virtual reality’ environment in response to receiving sensor data from the device 502 and / or other associated devices (e.g., such as a hand-held controller), and / or synchronizing the experience with other devices (e.g., other headset devices associated with other users). The network server 506 can include application logic that governs the behavior of the virtual environment. In an example, the network server 506 may communicate with the device 502 via the AP 504, transmitting data such as rendered graphics and receiving user input data relayed through the AP to support real-time interaction within the virtual reality environment.

[0114] The AP 504 can transmit uplink communications 556 to the network server 506 and the network server 506 can transmit downlink communications 554 to the AP 504. In an example, communications 554 and 556 may be backhaul communications. These backhaul communications may cany' high-bandwidth data, such as rendered graphics or user input.

[0115] 18

[0116] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) between the AP 504 and the network server 506 to support real-time application performance. Uplink communications 556 and downlink communications 554 can be executed on a wired or wireless link that supports high-capacity, long-distance connectivity. In an example, round-trip time (RTT) latency may be used to evaluate a quality of data transmissions between two devices, such as the AP 504 and the network server 506. RTT latency may refer to the time it takes for a data packet to travel from a source device to a destination and back again. RTT latency may be the sum of delays from devices to sources. In the system 500, the RTT latency may be the sum of four delays on each of communications 550-556. Delay may refer to the time it takes for a data packet to travel from its source to its destination across a network. Each of communications 550-556 may be associated with a delay. In some examples, uplink communications 556 and downlink communications 554 may be associated with equivalent delays, such that uplink communications 556 and downlink communications 554 contribute equally, or near equally, to RTT latency of transmissions between the AP 504 and the network server 506.

[0117] The AP 504 can transmit downlink communications 550 to the device 502 and the device 502 can transmit uplink communications to the AP 504. In an example, communications 550 and 552 may be Wi-Fi communications. For example, communications 550 and 552 may be executed over a Wi-Fi netw ork managed by the AP 504. In some examples, a delay of uplink communications 552 may be measured by the device 502. For example, the device 502 may measure the delay of uplink communications 552 by calculating the time elapsed between transmitting a data packet and receiving a corresponding acknowledgment from the AP 504. The device 502 can include a Wi-Fi chipset that measures the delay of uplink communications by recording the time a data packet is transmitted and comparing it to the time an acknowledgment is received from the AP 504. However, the AP 504 may not measure a delay for downlink communications 550, since it does not receive immediate feedback from the device 502 indicating the exact time the data was received. This may make it difficult to determine a delay on downlink communications 550. According to protocols for Wi-Fi networks, the AP 504 may not be configured to calculate a delay on communications 550 or report this delay back to device 502. This may impede determining an overall RTT latency.

[0118] In some implementations, determining the delay on downlink communications 550 can reduce computing resources used to determine RTT latency. As an example, if the backhaul communications 554 and 556 are stable, monitoring Wi-Fi communications 550 and 552 can allow a device, such as device 502 to generate RTT measurements without doing

[0119] 19

[0120] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0121] RTT measurements at an application layer. Application layer may refer to communications between the AP 504 and the network server 506. Application layer measurements, such as the delay on communications 554 and 556, may be consume computing resources such as active radio use and CPU activity. In an example where application layer delay, including the delay of communications 554 and 556, is relatively stable, the device 502 can reduce computing resources used to determine RTT latency by determining a delay on communications 550 and 552, and determining the RTT latency based on the determined delays and previously measured delays of communications 554 and 556. This may reduce computing resources in comparison to conventional methods which may simply send a packet round trip across communications 550-556 between the device 502 and the network server 506 and determine the RTT latency based on how long it takes the packet to get back to the source device. For example, measuring delay on communications 550-552 may use less computing resources than measuring delay on communications 550-556.

[0122] In some implementations, the delay on downlink communications 550 may inform control actions of the device 502. For example, the device 502 can determine whether to offload computing tasks to an external computing device based on the delay on downlink communications 550. Offloaded tasks may be subject to latency introduced by delays in communications 550 to 552, delays that tasks executed locally at device 502 do not encounter. The device 502 can whether to offload tasks (e.g., to save power of a battery associated with device 502) based on whether this latency is acceptable. As an example, the device 502 can offload execution of an Al model to a remote cloud server based on determining that the delay on downlink communications 550 and uplink communications 552 is below a threshold indicating an acceptable amount of delay.

[0123] In some implementations, the delay on downlink communications 550 may be used to diagnose jitter in latency. Jitter may refer to variation in packet delay over time, which can negatively impact the consistency and quality of a virtual reality environment. The delay on downlink communications 550 may be used to determine if communications 550 and 552 are the source of the jitter. The device execute operations such as changing a Wi-Fi mode or moving to a different AP based on determining that communications 550 and 552 are the source of the jitter. This may allow the device 502 to remedy the jitter without interrupting the presentation of the virtual reality environment to the user.

[0124] In some embodiments, the AP 504 can generate a report indicating a delay on downlink communications 550. For example, the AP 504 can generate a frame including a latency reporting element. The latency reporting element can include various parameters of

[0125] 20

[0126] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) communications 550, such as latency statistics or received signal strength indicator (RSSI) metrics. In an example, the AP 504 can transmit the report to the device 502. Based on the report, the device 502 can reduce resources used to determine RTT latency and / or evaluate a quality^ of the connection for communications 550 to determine whether tasks should be offloaded or diagnose jitter. The device 502 can also determine whether remedial actions such as switching to another AP in response to receiving a report from the AP 504 indicating a poor connection for communications 550.

[0127] FIGS. 6A-6D is a diagram showing example fields in an information element 600 for latency reporting, according to an example implementation of the present disclosure. The example field may indicate information about a connection (e.g., communications 550 of FIG. 5) between an AP (e.g.. AP 504 of FIG. 5) and a device (e.g., device 502 of FIG. 5). In an example, the AP can transmit the information element 600 to the device indicate latency metrics and / or request latency metrics about a connection. This connection may be a connection for which latency is not usually measured, such as a downlink connection between the AP and the device. Based on receiving the information element 600. the device can take actions such as estimate RTT latency, determine whether to offload tasks, or modifying parameters of the connection to the AP.

[0128] The information element 600 can include fields 602-616. Fields 602-606 may be standard fields that identify a type and length of the information element 600. Element ID field 602 may identify the type or purpose of the information element 600. For example, the element ID field 602 may identify the information element 600 as a latency reporting information element. Length field 604 may specify a size (e.g., in bytes) of the information element 600. Element ID extension field 606 may extend a range of identifiable information elements beyond a standard element ID field. For example, element ID extension field 606 and element ID field 602 may jointly identify information element 600 as a latency reporting information element. Fields 608-616 may identify. For example, control field 608 can include information about the other fields such as length or whether they are present, request type field 610 can indicate if the AP is requesting information from the device, the RSSI report field 612 can indicate a signal strength of the downlink connection measured by the AP, the latency field 614 can indicate latency values on the downlink connection determined by the AP, and the queue size field 616 can indicate information about traffic flow' on the downlink connection. In some embodiments, the order of the fields and subfields of information element 600 may be different. In some embodiments, the information element 600 may only include a subset of the fields and subfields depicted in FIGS. 6A-6D.

[0129] 21

[0130] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0131] As depicted in FIG. 6A, the information element 600 can include the control field 608 with subfields 618-626. The control field 608 can include information about the subsequent fields in the information element 600. For example, the control field 608 can include a request type present subfield 618 that indicates whether the information element 600 includes request type field 610. Similarly, RSSI report present subfield 620 can indicate whether the information element 600 includes RSSI report field 612. As an example, a value of 0 (e.g., as opposed to 1) in the request type present subfield 618 may indicate that the request type field 610 is not present in the information element 600. The control field 608 can also include latency report subfield count subfield 622. The latency report subfield count subfield 622 can indicate how many subfields are present in latency field 614. In an example where the information element 600 does not include the latency field 614. the latency report subfield count subfield 622 can be set to 0. Similarly, the control field 608 can include the queue size report subfield count subfield 624. The queue size report subfield count subfield 624 can indicate how many subfields are present in the queue size field 616. In an example where the information element 600 does not include the queue size field 616, the queue size report subfield count subfield 624 can be set to 0. The control field 608 can also include reserve subfield 626. The reserve subfield 626 may set aside space for additional features. The reserve subfield 626 may be set to a default value, such as 0.

[0132] As depicted in FIG. 6B, the information element 600 can include the request type field 610 with subfields 618-626. The request type field 610 can include information about parameters and / or key performance indicators (KPIs) of the connection between the AP and the STA the AP is requesting. The request type field 610 can include a RSSI subfield 628 that can indicate whether the AP is requesting RSSI of frames transmitted by the AP to the device. In an example, the RSSI subfield 628 can be set to 1 if the AP is requesting a report of this information. The request type field 610 can include a latency type bitmap subfield 630. The latency ty pe bitmap subfield 630 can indicate w hich types of latency analytics are indicated. As an example, the latency type bitmap subfield 630 can indicate latency types according to table 1, as shown below. In table 1, the latency type may refer to percentiles. As an example, bit position 2 may be associated with the maximum latency associated with the fastest 75% of packets.

[0133] 22

[0134] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0135] Table 1 : latency type bitmap subfield values

[0136] The request ty pe field 610 can include a traffic ID ty pe subfield 632 and traffic ID subfield 634. The traffic ID ty pe subfield 632 can indicate which type of identifier the traffic ID subfield 634 indicates. As an example, a bit value of 0 can indicate all traffic, a bit value of 1 can indicate Access Category (AC), a bit value of 2 can indicate traffic identifier (TID), and a bit value of 3 can indicate small computer system identifier (SCSID). The traffic ID subfield 634 can include an identifier (e.g., of the type indicated by traffic ID type subfield 632) that indicates what type of traffic the latency report is requested for. In an example, if the traffic ID subfield 634 is set to a predetermined value (e.g., 255), the latency analytics may be requested for all traffic. The request ty pe field 610 can also include an unsolicited latency report subfield 636. The unsolicited latency report subfield 636 can indicate whether the device should send an updated latency report if latency parameters exceed a threshold (e.g., a bit value of 1 may indicate the device should send the updated latency report). In an example where the unsolicited latency report subfield 636 indicates that the device should send the updated latency report, the latency field 614 may define a threshold for sending this updated latency report. The request type field 610 can also include reserve subfield 638. The reserve subfield 626 may set aside space for additional features. The reserve subfield 638 may be set to a default value, such as 0.

[0137] As depicted in FIG. 6C, the information element 600 can include the latency field 614 with subfields 640-646. The latency field 614 can indicate information about latency on a downlink connection (e.g.. communications 550 of FIG. 5) between the AP and the device. The latency field 614 can include traffic ID type subfield 640 that can indicate which type of traffic identifier is included in ID subfield 642. For example, a bit value of 0 can indicate all traffic types (e.g., aggregate latency), a bit value of 2 can indicate an AC, a bit value of 3 can indicate TID, and a bit value of 3 can indicate an SCSID. The ID subfield 642 can include a numerical identifier according to the type indicated by traffic ID type subfield 640. The latency7field 614 can also include latency type subfield 644 that indicates a ty pe of latency7

[0138] 23

[0139] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) provided in latency value subfield 646. In an example, the latency type subfield 644 can indicate one of the latency types included in table 1. The latency value subfield 646 can indicate a value of a latency associated with the percentile of latency indicated in the latency type subfield 644. In an example, the latency value subfield 646 may indicate a latency value associated with predetermined units. As an example, the information element 600 may be configured to report latency in ps.

[0140] As depicted in FIG. 6D, the information element can include the queue size field 616 with subfields 648-654. The queue size field 616 can indicate information about a queue size on a downlink connection (e.g., communications 550 of FIG. 5) between the AP and the device. Queue size may be relevant to latency as larger queue sizes can introduce longer wait times for packets to be processed and transmitted, which can increase the latency on a connection. The queue size field 616 can include a traffic ID type subfield 648 that, similar to the traffic ID type subfield 640 of FIG. 6C, indicates a type of an identifier included in ID subfield 650. The ID subfield 650 can include an identifier of w hat type of traffic the scaling factor subfield 652 and queue size subfield 654 are describing. The scaling factor subfield 652 can indicate a multiplicative factor to scale the value in the queue size subfield 654 by. This can reduce the number of bites used to indicate the queue size in queue size subfield 654. The queue size subfield 654 can indicate a size of the queue. For example, the queue size may be expressed in bytes, indicating the amount of data currently stored in the queue and waiting to be processed and transmitted.

[0141] FIG. 7 is a diagram showing an example subelement in an information element 700 for latency reporting, according to an example implementation of the present disclosure. In an example, the latency field 614 and queue size field 616 of FIGS. 6A-6D may be defined as subelements. A field may refer to a portion of a frame that holds a specific piece of information (e.g., specific identifier, specific value, and / or the like). A subelement may refer to a structure component that indicates more hierarchical and / or detailed information than a single field. The subelement may include one or more fields. In an example, the information element 700 can include a subelement ID field 702. The subelement ID field 702 can indicate a type or purpose of the information element 700. For example, the subelement ID field 702 can indicate that the information element 700 includes a latency report. The information element 700 can also include length field 704 that indicates a length of the data included in data field 706. The data field 706 can include latency report indicating information about a downlink connection (e.g.. communications 550 of FIG. 5). between an AP and a device. In an example, the data field 706 can include the latency field 614 and / or the queue size field

[0142] 24

[0143] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0144] 616 of FIGS. 6A-6D. In an example, the AP can indicate analytics information to the device by transmitting information element 700. Based on information element 700 the device can determine a latency on the downlink connection between the AP and the device. In some embodiments, the order of the fields and subfields of information element 700 may be different. In some embodiments, the information element 700 may only include a subset of the fields and subfields depicted in FIG. 7.

[0145] In some embodiments, an information element (e.g.. the information element 600 of FIGS. 6A-6D or the information element 700 of FIG. 7) may be included within an action frame. For example, a new action frame type (e.g., public action frame, unprotected sub-1 GHz (SIG) action frame, protected SIG action frame, and / or the like) associated with latency reporting may be defined. As an example, an unprotected SIG action frame may be defined wi th a first field indicating a category, a second field specifying the unprotected SIG action type, a third field identifying a latency reporting element, and an optional fourth field for additional elements. In an example, the new action frame type may be defined as response and request type frames. As an example, the device can transmit a request type frame to request latency reporting and the AP can response with a response type frame indicating the latency report. In this example, the request type field 610 of FIGS. 6A-6D may be present in the request type frame but not in the response type frame. In some examples, an unsolicited response type frame may be transmitted if an earlier request type frame “yes'’ (e.g., 1) to unsolicited latency report subfield 636 of request type field 610 of FIGS. 6A-6D.

[0146] In some embodiments, the information element (e.g., the information element 600 of FIGS. 6A-6D or the information element 700 of FIG. 7) may be included within another frame type, such as a management frame or a control frame. For example, a new management frame may be defined to carry the information element. As another example, a new control frame may be defined to carry the information element. Similar to the action frame, separate request and response frames may be defined for the new management frame or control frame. The latency report may be included in either frame type within a data field that is the same or similar to data field 706 of FIG. 7. For example, the latency report may be included within an aggregation control subfield (e.g.. A-Control field).

[0147] FIG. 8 is a diagram showing an example field in an ultra-high reliability (UHR) capabilities element 800 for latency reporting, according to an example implementation of the present disclosure. In an example, an AP (e.g., AP 504 of FIG. 5) may indicate to a device (e.g.., device 502 of FIG. 5) that latency reporting is supported by transmitting the UHR capabilities element 800 (e.g., or vice versa). The UHR capabilities element 800 can include

[0148] 25

[0149] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) element ID field 802 that identifies it as a UHR capabilities information element, a length field 804 that indicates a length of the UHR capabilities element 800. and an element ID extension field 806 to indicate whether the UHR capabilities element 800 includes an extended range of elements. The UHR capabilities element 800 can include a UHR mediaaccess control (MAC) capabilities information field 808 that indicates a latency reporting support subfield 812 that can indicate whether latency reporting is supported. For example, the latency reporting support subfield 812 can include a 1 or a 0 to indicate that it is or is not supported, respectively. Alternatively, the latency reporting support subfield 812 can be included in another field of the UHR capabilities element 800. For example, the latency reporting support subfield 812 can be included in a high efficiency (HE) capabilities field or an extremely high throughput (EHT) capabilities element. The UHR MAC capabilities information field 808 can also include a reserved subfield 814 that sets aside space for additional features. The UHR capabilities element 800 can also include a UHR physical (PHY) capabilities information field 810 that can indicate physical layer features supported by the AP or device. In some embodiments, the order of the fields and subfields of the UHR capabilities element 800 may be different. In some embodiments, the UHR capabilities element 800 may only include a subset of the fields and subfields depicted in FIG. 8.

[0150] FIG. 9 is a diagram showing a frame 900 for initiating latency reporting, according to an example implementation of the present disclosure. For example, the frame 900 may be transmitted to a station (e.g.. device 502 or AP 504 of FIG. 5) to solicit a latency report. The frame 900 can be any type of frame that solicits a response, such as a trigger frame, management frame with a solicitation function, and / or the like. In response to receiving the frame 900, the station can transmit the requested latency report (e.g., such as that indicated in information element 600 of FIGS. 6A-6D). As an example, the frame 900 may be transmitted from an AP to a non-AP station (e.g., device 502 of FIG. 5) on a downlink communication channel. In this example, the frame 900 may including instructions for how the response should be transmitted on the uplink channel from the non-AP station to the AP. Alternatively, the non-AP station may transmit the frame 900 to the AP. In this example, fields associated with scheduling uplink transmissions may not be present in the frame 900. In some embodiments, the order of the fields and subfields of frame 900 may be different. In some embodiments, the frame 900 may only include a subset of the fields and subfields depicted in FIG. 9.

[0151] The frame 900 can include a MAC header including a frame control field 902 that indicates what type of frame it is (e.g., trigger frame, management frame, control frame,

[0152] 26

[0153] 4913-6581-8456 1 Attorney Docket No.: 121439-1421 (FB-521PC) and / or the like), a duration field 904 that indicates a length of the frame 900, a receiver address (RA) field 906 indicating an intended recipient of the frame 900, and a transmitter address (TA) field 908 indicating an address of the device transmitting the frame 900. The frame 900 can include a common info field 910 that conveys information related to the action the frame 900 is intended to initiate. The frame 900 can include a user info list field 912 that indicates transmission parameters for a response to the frame 900. In an example, the frame 900 can include padding field 914 including a variable amount of padding and a frame check sequence (FCS) field 916 that may be used for error detection.

[0154] The common info field 910 can include subfields 918-950 that indicate various types of information associated with the action the frame 900 is intended to initiate. In an example where the frame 900 is atrigger frame, it may include trigger type subfield 918.

[0155] Alternatively, if the frame 900 is not a trigger frame, it may include a field with similar function. Trigger type subfield 918 can indicate which type of trigger frame the frame 900 is (e.g., latency reporting trigger frame). In an example, the trigger type subfield 918 may indicate one of the trigger types included in table 2, as shown below. Specifically, the trigger type subfield 918 can indicate that the frame 900 is associated with a request for a latency report. For example, a new trigger frame variant associated with latency reporting may be added as one of the reserved trigger type subfield values (e.g., one of values 8-15)

[0156] Table 2: Trigger Types

[0157] 27

[0158] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0159] Uplink (UL) length subfield 920 can indicate a length of a solicited frame. For example UL length subfield 920 can indicate a length of an uplink response transmitted by the device in response to receiving frame 900 from the AP. Carrier sense (CS) subfield 922 can indicate whether a station receiving the frame 900 should consider the medium state (e.g., execute energy detection (ED)) when determining whether to response. UL bandwidth (BW) subfield 924 can indicate a bandwidth of the uplink transmission that the station receiving the frame 900 should use when transmitting the response. Guard interval (GI) and high efficiency long training field (HE-LTF) ty pe subfield 926 may indicate a combination of guard interval duration and the number of HE-LTF symbols that a station should use for its uplink transmission transmitted in response to the frame 900. Multi-user multiple input, multiple output (MU-MIMO) HE-LTD mode field 928 may indicate a ty pe of LTD signal used when multiple stations are transmitting using MU-MIMO. Number of HE-LTF symbols and midamble periodicity' subfield 930 may indicate a number of HE-LTF symbols used for channel estimation and / or a periodicity of mid-ambles used to improve channel tracking. UL spacetime block coding (STBC) subfield 932 may indicate whether STBC is enabled for the uplink response to the frame 900. Low-density parity7check (LDPC) extra symbol segment subfield 934 may indicate whether an additional LDPC symbol segment should be present in the response. AP transmission (Tx) power subfield 936 may indicate a transmission power used by the AP to transmit the frame 900. Pre forward error correction (FEC) padding factor 938 may indicate an amount of padding (e.g., in orthogonal frequency-division multiplexing (OFDM) symbols) that should be added before FEC encoding in the response to the frame 900. Packet extension (PE) disambiguity subfield 940 may indicate whether a disambiguation symbol is included in the response to the frame 900. UL spatial reuse subfield 942 may indicate whether the receiving station is permitted to apply spatial reuse techniques during uplink transmission. Doppler subfield 944 may indicate the response to frame 900 should be transmitted using a doppler-resistance configuration. UL high efficiency signal field a (HE- SIG-A 2 subfield 946 reserved may indicate future-use and / or vendor-specific features. Reserved subfield 948 may include space for future features. In an example where the frame 900 is a trigger frame, the frame 900 can include trigger dependent common info field 950. Alternatively, if the frame 900 is not a trigger frame, it may include a field with similar function. Trigger dependent common info field 950 can include information about the request for the latency report. For example, trigger dependent common info field 950 can include at least some of the fields associated with the information element 600 of FIGS. 6A-6D.

[0160] 28

[0161] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0162] Specifically, the trigger dependent common info field 950 can include at least part of the request t pe field 610 of FIG. 6B. The receiving station can then transmit an analytics report according to the parameters indicated in the trigger dependent common info field 950. As an example, the receiving station can indicate a latency report indicating latency of a certain percentile of traffic (e.g., such as a percentile indicated in latency ty pe bitmap subfield 630 of FIG. 6B) indicated in the trigger dependent common info field 950.

[0163] FIG. 10 is a flowchart showing an example method 1000 of latency reporting, according to an example implementation of the present disclosure. In some embodiments, the method may be performed by an AP. For example, the method may be performed by an AP (e.g., AP 504 of FIG. 5). Based on the method, the AP can generate a frame that can be transmitted to a first device (e.g., device 502 of FIG. 5). The frame may indicate latency metrics of a connection between the AP and the first device to the first device. For example, the frame can indicate latency metrics of a downlink connection (e.g., communications 550 of FIG. 5) between the AP and the first device.

[0164] At step 1002. the AP may determine one or more latency metrics associated with a first device. For example, the AP may determine one or more latency metrics of one or more wireless traffic flows that are received by the first device. The wireless traffic flows that are received by the first device may represent downlink transmissions (e.g., communications 550 of FIG. 5) transmitted by the AP via a transmitter to the first device. The AP may generate the latency metrics (e.g.. downlink latency metrics) by timestamping when a frame is transmitted to the first client device and measuring the time until an acknowledgement frame is received from the first client device. It may be difficult for the first device to determine the latency metrics for the downlink transmissions as the first device does not control when transmissions are executed. As a result, it may be difficult for the first device to timestamp the start of a downlink transmission.

[0165] In some embodiments, the latency metrics can include at least one of latency statistics, queue size metrics, received signal strength indicator (RSSI) metrics, or transmitted power metrics. The AP may track queue size metrics by monitoring a number of packets waiting in its transmission buffers. RSSI metrics based on values reported by associated devices, and / or transmitted power metrics based on a pow er level that the AP executed transmissions at. Latency statistics may include measured latency (e.g., time in between a transmission and receiving an acknowledgement frame) for various ty pes of traffic. As an example, the latency statistics can include a latency value (e.g.. in units of time) below which a certain percentage of traffic falls.

[0166] 29

[0167] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0168] At step 1004, the AP may generate a first frame to report one or more latency metrics to the first device. For example, the AP can generate the first frame including one or more fields to indicate the latency metrics. As an example, the first frame can include an information element (e.g., information element 600 of FIGS. 6A-6D and / or information element 700 of FIG. 7) that indicates latency metrics such as latency statistics or queue size metrics. The information element can be included within various types of frames, such as a management frame or control frame. In an example, a request and response frame for latency reporting may be defined within a frame type (e.g., such as a management frame type). In this example, the first frame may be associated with the response frame type for latency reporting.

[0169] In some embodiments, the AP may determine a latency type and set field values in the first frame according to the determined latency type. The latency type may represent a type of traffic that a latency value included in the first frame corresponds to. For example, latency type can indicate a certain percentile of traffic (e.g., latency types as shown in table 1). As an example, the latency type can indicate that the latency value corresponds to a value below which a certain percentile (e.g., 95%, and / or the like) of measured samples fall. The AP can determine a latency value of the one or more wireless traffic flows that align with the latency ty pe. For example, the AP can determine a latency value below which a certain percentile (e.g., indicated by the latency type) of packets in the one or more wireless traffic flows falls. In an example, the first field can include a first field representing a latency type field (e.g., latency type subfield 644 of FIG. 6C) and a second field latency value field (e.g.. latency value subfield 646 of FIG. 6C). The first field can indicate what percentile of latency a value included in the second field is associated with. In an example, the first field may be a bitmap. A bitmap may refer to a data structure that maps a set of bit values (e.g., 0 to 7) to a set of information (e.g., a plurality of latency types). The bitmap may include a mapping that is the same or similar to table 1. As a result, the bitmap may map each bit in the set of bit values to a certain type of latency.

[0170] In some embodiments, the AP may set a field value in the first frame according to whether latency reporting is solicited or unsolicited. For example, a solicited latency report can be sent to the first device in response to a third frame (e.g., frame 900 of FIG. 9) and an unsolicited latency report can be sent based on one or more logical rules. The third frame may be any type of frame that solicits a responses, such as a trigger frame or a management frame with a solicitation function. In an example, the first device may transmit a frame that indicates one or more thresholds for sending an unsolicited latency report. Based on determining that one or more parameters (e.g., KPIs) exceed the threshold, the AP can

[0171] 30

[0172] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) transmit the first frame including the latency report. The AP can set a field value of a third field (e.g., unsolicited latency report subfield 636 of FIG. 6B) according to whether the latency report is solicited or unsolicited. As an example, the AP can set the third field value to a first value (e.g., 1) to indicate the latency report is solicited or a second value (e.g., 0) to indicate that it is unsolicited.

[0173] In some embodiments, the AP may set a field value in the first frame according to whether the latency metrics exceed a threshold. For example, based on determining that one or more latency metrics (e.g., latency statistics, queue size, RSSI, and / or the like), exceed the threshold, the AP can determine that an unsolicited latency report should be sent. The threshold may be a value set by the first device and / or the AP. To indicate that the latency report is unsolicited, the AP can set the third value to the second value.

[0174] In some embodiments, the AP may set a field value in the first frame according to whether the first frame is being generated in response to a third frame (e.g., frame 900 of FIG. 9) transmitted by the first device. For example, in response to receiving the third frame, the AP can generate the first frame including latency metrics. Within the first frame, the AP can set the third field to the first value to indicate the latency report is solicited.

[0175] In some embodiments, the AP may generate a frame indicating support of latency metrics reporting. For example, the AP can generate a second frame, such as a beacon frame including a field set to indicate support of reporting latency. The AP can then transmit the second frame to the first device to indicate support for latency metrics reporting. As an example, the second frame may include a UHR capabilities element (e.g., UHR capabilities element 800 of FIG. 8) that indicates capabilities for latency reporting. In this example, the UHR capabilities information element may include a field (e.g., latency reporting support subfield 812 of FIG. 8) which indicates that the AP can generate analytics reports.

[0176] In some embodiments, the AP may set a field value in the first frame according to queue size metrics. For example, the AP can determine that the one or more latency metrics include queue size metrics and, based on that determination, include the queue size metrics in the first frame. The AP can include both a field indicating that the queue size metrics are present and a field indicating the queue size. For example, the AP may include a fourth field (e.g., queue size report subfield count subfield 624 of FIG. 6A) with a value set to indicate that the latency metrics include queue size metrics and a fifth field (e.g., queue size subfield 654 of FIG. 6D) with a value indicating the queue size metrics.

[0177] In some embodiments, the AP may set a field value in the first frame according to received signal strength (RSSI) metrics or transmitted power metrics. For example, the AP

[0178] 31

[0179] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) can determine that the one or more latency metrics include RSSI metrics and, based on that determination, include the RSSI metrics in the first frame. The AP can include a field indicating that the RSSI metrics are present and a field indicating a value of the RSSI metrics. For example, the AP may include a sixth field (e.g., RSSI report present subfield 620 of FIG. 6A) with a value set to indicate that the latency metrics include RSSI metrics and a seventh field (e g., RSSI report field 612 of FIG. 6A) to indicate a value of the RSSI metrics. Additionally, or alternatively, the AP may include fields indicating the presence and / or value of transmitted pow er metrics in the first frame.

[0180] At step 1006, the AP may transmit the first frame to the first device. For example, the AP may wirelessly transmit the first frame to the first device via a transmitter. Based on the first frame the first device may execute one or more operations. For example, the first device can determine an estimated RTT latency based on latency statistics included in the first frame. As another example, the first device can determine whether or not to offload operations (e.g., such as executing an artificial intelligence model) to an external server based on the latency metrics included in the first frame. As yet another example, the first device can use the first frame to diagnose jitter in latency. Specifically, the first device can determine whether the downlink connection between the AP and the first device is the cause of jitter in a connection based on the first frame. In the described examples, the first frame may provide latency metrics that are difficult for the first device to determine on its own, due to its lack of visibility into downlink transmission parameters on wireless traffic flows between the AP and the first device, such as transmission power or the time of initial transmission.

[0181] Having now described some illustrative implementations, it is apparent that the foregoing is illustrative and not limiting, having been presented by way of example. In particular, although many of the examples presented herein involve specific combinations of method acts or system elements, those acts and those elements can be combined in other ways to accomplish the same objectives. Acts, elements and features discussed in connection with one implementation are not intended to be excluded from a similar role in other implementations or implementations.

[0182] The hardware and data processing components used to implement the various processes, operations, illustrative logics, logical blocks, modules and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardw are

[0183] 32

[0184] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality7of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some embodiments, particular processes and methods may be performed by circuitry that is specific to a given function. The memory (e.g., memory, memory unit, storage device, etc.) may include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing data and / or computer code for completing or facilitating the various processes, layers and modules described in the present disclosure. The memory may be or include volatile memory or non-volatile memory, and may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. According to an exemplary embodiment, the memory7is communicably connected to the processor via a processing circuit and includes computer code for executing (e.g., by the processing circuit and / or the processor) the one or more processes described herein.

[0185] The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carry ing or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way7of example, such machine- readable media can comprise RAM, ROM, EPROM, EEPROM, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

[0186] 33

[0187] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC)

[0188] The phraseology and terminology' used herein is for the purpose of description and should not be regarded as limiting. The use of “including’' “comprising” “having” “containing” “involving” “characterized by” “characterized in that” and variations thereof herein, is meant to encompass the items listed thereafter, equivalents thereof, and additional items, as well as alternate implementations consisting of the items listed thereafter exclusively. In one implementation, the systems and methods described herein consist of one, each combination of more than one. or all of the described elements, acts, or components.

[0189] Any references to implementations or elements or acts of the systems and methods herein referred to in the singular can also embrace implementations including a plurality' of these elements, and any references in plural to any implementation or element or act herein can also embrace implementations including only a single element. References in the singular or plural form are not intended to limit the presently disclosed systems or methods, their components, acts, or elements to single or plural configurations. References to any act or element being based on any information, act or element can include implementations where the act or element is based at least in part on any information, act, or element.

[0190] Any implementation disclosed herein can be combined with any other implementation or embodiment, and references to “an implementation,” “some implementations,” “one implementation” or the like are not necessarily mutually exclusive and are intended to indicate that a particular feature, structure, or characteristic described in connection with the implementation can be included in at least one implementation or embodiment. Such terms as used herein are not necessarily all referring to the same implementation. Any implementation can be combined with any other implementation, inclusively or exclusively, in any manner consistent with the aspects and implementations disclosed herein.

[0191] Where technical features in the drawings, detailed description or any claim are followed by reference signs, the reference signs have been included to increase the intelligibility of the drawings, detailed description, and claims. Accordingly, neither the reference signs nor their absence have any limiting effect on the scope of any claim elements.

[0192] Systems and methods described herein may be embodied in other specific forms without departing from the characteristics thereof. References to “approximately,” “about” “substantially” or other terms of degree include variations of + / -10% from the given measurement, unit, or range unless explicitly indicated otherwise. Coupled elements can be electrically, mechanically, or physically coupled with one another directly or with intervening elements. Scope of the systems and methods described herein is thus indicated by the appended claims, rather than the foregoing description, and changes that come within the

[0193] 34

[0194] 4913-6581-8456 1 Atorney Docket No.: 121439-1421 (FB-521PC) meaning and range of equivalency of the claims are embraced therein.

[0195] The term “coupled’" and variations thereof includes the joining of two members directly or indirectly to one another. Such joining may be stationary (e.g., permanent or fixed) or moveable (e.g., removable or releasable). Such joining may be achieved with the two members coupled directly with or to each other, with the two members coupled with each other using a separate intervening member and any additional intermediate members coupled with one another, or with the two members coupled with each other using an intervening member that is integrally formed as a single unitary body with one of the two members. If “coupled” or variations thereof are modified by an additional term (e.g., directly coupled), the generic definition of “coupled” provided above is modified by the plain language meaning of the additional term (e.g.. “directly coupled” means the joining of two members without any separate intervening member), resulting in a narrower definition than the generic definition of “coupled” provided above. Such coupling may be mechanical, electrical, or fluidic.

[0196] References to “or” can be construed as inclusive so that any terms described using “or” can indicate any of a single, more than one, and all of the described terms. A reference to “at least one of ‘A’ and B’” can include only ‘A’, only ‘B’, as well as both ‘A’ and B’. Such references used in conjunction with “comprising” or other open terminology can include additional items.

[0197] Modifications of described elements and acts such as variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations can occur without materially departing from the teachings and advantages of the subject matter disclosed herein. For example, elements shown as integrally formed can be constructed of multiple parts or elements, the position of elements can be reversed or otherwise varied, and the nature or number of discrete elements or positions can be altered or varied. Other substitutions, modifications, changes and omissions can also be made in the design, operating conditions and arrangement of the disclosed elements and operations without departing from the scope of the present disclosure.

[0198] References herein to the positions of elements (e.g., “top,” “bottom,” “above.” “below”) are merely used to describe the orientation of various elements in the FIGURES. The orientation of various elements may differ according to other exemplary embodiments, and that such variations are intended to be encompassed by the present disclosure.

[0199] 35

[0200] 4913-6581-8456 1

Claims

Atorney Docket No.: 121439-1421 (FB-521PC)CLAIMSWhat is claimed is:

1. An access point (AP) comprising: one or more processors configured to: determine one or more latency metrics of one or more wireless traffic flows that are received by a first device associated with the AP; generate a first frame including the one or more latency metrics to report the one or more latency metrics to the first device; and wirelessly transmit, via a transmitter, the generated first frame to the first device.

2. The AP according to claim 1, wherein the one or more latency metrics comprise at least one of latency statistics, queue size metrics, received signal strength indicator (RSSI) metrics, or transmitted power metrics.

3. The AP according to claim 1, wherein in generating the first frame, the one or more processors are configured to: determine a latency type among a plurality of latency types; determine a latency value of the one or more wireless traffic flows according to the latency type; and set a first field and a second field of the first frame to indicate the latency ty pe and the latency value, respectively.

4. The AP according to claim 3, wherein the first field is a bitmap in which each bit is set to indicate a corresponding latency type among the plurality of latency types.

5. The AP according to claim 1, wherein in generating the first frame, the one or more processors are configured to: determine whether the reporting is solicited or unsolicited; and set a third field to a first value indicating that the reporting is solicited, or a second value indicating that the reporting is unsolicited.

6. The AP according to claim 5, wherein the one or more processors are configured to: determine that the one or more latency metrics exceed one or more thresholds; and set the third field to the second value.

7. The AP according to claim 5, wherein the one or more processors are configured to: receive, from the first device, a third frame to solicit the reporting; and set the third field to the first value.

8. The AP according to claim 1, wherein in generating the first frame, the one or more processors are configured to:364913-6581-8456 1Atorney Docket No.: 121439-1421 (FB-521PC) generate a second frame including a field set to a value indicating to support reporting of latency metrics; and wirelessly transmit, via the transmitter, the generated second frame.

9. The AP according to claim 1, wherein in generating the first frame, the one or more processors are configured to: determine that the one or more latency metrics include queue size metrics; set a fourth field to a value to indicate that the one or more latency metrics include queue size metrics; and set a fifth field to a value of the queue size metrics.

10. The AP according to claim 1, wherein in generating the first frame, the one or more processors are configured to: determine that the one or more latency metrics include received signal strength indicator (RSSI) metrics, or transmitted power metrics; set a sixth field to a value to indicate that the one or more latency metrics include RSSI metrics or transmitted power metrics; and set a seventh field to a value of the RSSI metrics or the transmitted power metrics.

11. A method comprising: determining, by one or more processors of an access point (AP), one or more latency metrics of one or more wireless traffic flows that are received by a first device associated with the AP; generating, by the one or more processors of the AP, a first frame including the one or more latency metrics to report the one or more latency metrics to the first device; and wirelessly transmitting, via a transmitter, the generated first frame to the first device.

12. The method according to claim 11, wherein the one or more latency metrics comprise at least one of latency statistics, queue size metrics, received signal strength indicator (RSSI) metrics, or transmitted power metrics.

13. The method according to claim 11, wherein generating the first frame comprises: determining a latency type among a plurality of latency types: determining a latency value of the one or more wireless traffic flows according to the latency type; and setting a first field and a second field of the first frame to indicate the latency type and the latency value, respectively.

14. The method according to claim 13, wherein the first field is a bitmap in which each bit is set to indicate a corresponding latency type among the plurality of latency types.374913-6581-8456 1Atorney Docket No.: 121439-1421 (FB-521PC)15. The method according to claim 11, wherein generating the first frame comprises: determining whether the reporting is solicited or unsolicited; and setting a third field to a first value indicating that the reporting is solicited, or a second value indicating that the reporting is unsolicited.

16. The method according to claim 15, further comprising: determining that the one or more latency metrics exceed one or more thresholds; and setting the third field to the second value.

17. The method according to claim 15, further comprising: receiving, from the first device, a third frame to solicit the reporting; and setting the third field to the first value.

18. The method according to claim 11, wherein generating the first frame comprises: generating a second frame including a field set to a value indicating to support reporting of latency metrics; and wirelessly transmitting, via the transmitter, the generated second frame.

19. The method according to claim 11, wherein generating the first frame comprises: determining that the one or more latency metrics include queue size metrics; setting a fourth field to a value to indicate that the one or more latency metrics include queue size metrics; and setting a fifth field to a value of the queue size metrics.

20. The method according to claim 11, wherein generating the first frame comprises: determining that the one or more latency metrics include received signal strength indicator (RSSI) metrics, or transmitted power metrics; setting a sixth field to a value to indicate that the one or more latency metrics include RSSI metrics or transmitted power metrics; and setting a seventh field to a value of the RSSI metrics or the transmitted power metrics.384913-6581-8456 1

Images