System and method for reporting buffer status for wireless peer-to-peer (P2P) traffic

By defining a signaling method to request p2p buffer status reports within wireless communication systems, efficient resource allocation and power management are achieved in environments like virtual, augmented, or mixed reality systems.

CN119072991APending Publication Date: 2024-12-03CTRL-LABS CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380035469.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-03-22
Filing Date
2023-04-22
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

Existing wireless communication systems lack an efficient method for an access point to query the buffer status of peer-to-peer (p2p) services between wireless devices, leading to inefficient resource allocation in environments like virtual, augmented, or mixed reality systems.

Method used

A signaling method is defined to request and poll buffer status reports for p2p services, redefining the BSRP trigger frame to include specific subfields or bits indicating the need for p2p buffer status reporting, allowing wireless devices to report their p2p traffic status to the access point.

Benefits of technology

Enables efficient resource allocation by allowing the access point to accurately assess p2p service needs, optimizing transmission opportunities and power management in wireless local area networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072991A_ABST
    Figure CN119072991A_ABST
Patent Text Reader

Abstract

The first device may include one or more processors. The one or more processors may be configured to generate a first frame including buffer state data corresponding to wireless traffic between a first device and a second device. Each of the first device and the second device may not be an access point. The one or more processors may be configured to wirelessly transmit, via a transceiver, the generated first frame to an access point in a wireless local area network (WLAN).
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to communications, including but not limited to systems and methods for a wireless device (STA) to report buffer status of peer-to-peer (p2p) traffic of the STA, for example to improve resource allocation. Background Art

[0002] Artificial realities such as virtual reality (VR), augmented reality (AR), or mixed reality (MR) provide an immersive experience for users. In one example, a user wearing a head wearable display (HWD) can turn his head, and an image of a virtual object corresponding to the position of the HWD and the user's gaze direction can be displayed on the HWD to allow the user to feel as if the user is moving in an artificial reality space (e.g., VR space, AR space, or MR space). The image of the virtual object can be generated by a console that is communicatively coupled to the HWD. In some embodiments, the console can access a network. Summary of the invention

[0003] Various embodiments disclosed herein relate to a first device comprising one or more processors. In some embodiments, the one or more processors may be configured to generate a first frame comprising buffer status data corresponding to a wireless service between the first device and a second device. Each of the first device and the second device may not be an access point. The one or more processors may be configured to wirelessly transmit the generated first frame to an access point in a wireless local area network (WLAN) via a transceiver.

[0004] In some embodiments, the one or more processors may also be configured to wirelessly receive a second frame from an access point via a transceiver. The one or more processors may be configured to generate the first frame in response to the second frame. In some embodiments, the wireless service may include a peer-to-peer (p2p) service between the first device and the second device. In some embodiments, the first frame may include a control identifier field. The one or more processors may be configured to, when generating the first frame, set the control identifier field to a value indicating a buffer status report frame.

[0005] In some embodiments, the first frame may include a bitmap field, the bitmap field including a plurality of bits corresponding to a plurality of access categories. The one or more processors may be configured to, when generating the first frame, set each of the plurality of bits to a first value, the first value indicating that there is no service associated with the access category corresponding to the bit. In some embodiments, the first frame may include a service identifier quantity field, the service identifier quantity field indicating the number of service identifiers for which buffered services exist. The one or more processors may be configured to, when generating the first frame, set the service identifier quantity field to a second value, the second value indicating that the number of service identifiers for which buffered services exist is zero.

[0006] In some embodiments, the first frame may include a quality of service (QoS) control field, the QoS control field including a first field. The one or more processors may be configured to, when generating the first frame, set the first field to a value indicating the presence of wireless point-to-point (p2p) traffic. The QoS control field includes a second field. The one or more processors may be configured to, when generating the first frame, set the second field to a value indicating a queue size for wireless traffic between the first device and the second device.

[0007] In some embodiments, the first frame may include a control identifier field. The one or more processors may be configured to, when generating the first frame, set the control identifier field to a value indicating a point-to-point (p2p) buffer status report frame. The first frame may include a queue size field. The one or more processors may be configured to, when generating the first frame, set the queue size field to a value indicating a queue size of a wireless service between the first device and the second device.

[0008] Various embodiments disclosed herein are directed to a method that includes generating, by a first device, a first frame that includes buffer status data corresponding to wireless traffic between the first device and a second device. Each of the first device and the second device may not be an access point. The method may include wirelessly transmitting the generated first frame to an access point in a wireless local area network (WLAN) via a transceiver of the first device.

[0009] In some embodiments, the first device may wirelessly receive a second frame from the access point via the transceiver. The first device may generate a first frame in response to the second frame. In some embodiments, the wireless service may include a point-to-point (p2p) service between the first device and the second device. In some embodiments, the first frame may include a control identifier field. The first device may set the control identifier field to a value indicating a buffer status report frame when generating the first frame.

[0010] In some embodiments, the first frame may include a bitmap field, the bitmap field including a plurality of bits corresponding to a plurality of access categories. The first device may, when generating the first frame, set each of the plurality of bits to a first value, the first value indicating that there is no service associated with the access category corresponding to the bit. The first frame may include a service identifier quantity field, the service identifier quantity field indicating the number of service identifiers for which buffered services exist. The first device may, when generating the first frame, set the service identifier quantity field to a second value, the second value indicating that the number of service identifiers for which buffered services exist is zero.

[0011] In some embodiments, the first frame may include a quality of service (QoS) control field, the QoS control field including a first field. The first device may set the first field to a value indicating the presence of a wireless point-to-point (p2p) service when generating the first frame. The QoS control field includes a second field. The first device may set the second field to a value indicating a queue size of a wireless service between the first device and the second device when generating the first frame.

[0012] In some embodiments, the first frame may include a control identifier field. The first device may set the control identifier field to a value indicating a point-to-point (p2p) buffer status report frame when generating the first frame. The first frame may include a queue size field. The first device may set the queue size field to a value indicating a queue size of wireless traffic between the first device and the second device when generating the first frame.

[0013] It will be appreciated that any features described herein that are suitable for incorporation into one or more aspects or embodiments of the present disclosure are intended to be generalizable to any and all aspects and embodiments of the present disclosure. Other aspects of the present disclosure can be understood by those skilled in the art based on the specification, claims and drawings of the present disclosure. The foregoing general description and the following detailed description are exemplary and illustrative only, and are not limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings are not intended to be drawn to scale. In the various drawings, the same reference numerals and symbols indicate the same elements. For clarity, not every component will be labeled in every drawing.

[0015] Figure 1 is a schematic diagram of a system environment including an artificial reality system according to an example embodiment of the present disclosure.

[0016] Figure 2 is a schematic diagram of a head wearable display according to an exemplary embodiment of the present disclosure.

[0017] Figure 3 is a block diagram of a computing environment according to an example implementation of the present disclosure.

[0018] Figure 4A A schematic diagram of a buffer status report (BSR) request and a BSR response according to an exemplary embodiment of the present disclosure.

[0019] Figure 4B It is a schematic diagram of a system environment including a peer-to-peer (p2p) service in a wireless local area network (WLAN) according to an exemplary embodiment of the present disclosure.

[0020] Figure 5A , Figure 5B and Figure 5C An example buffer status report poll (BSRP) trigger frame format according to an example implementation of the present disclosure is shown.

[0021] Figure 5D An example trigger type subfield encoding according to an example implementation of the present disclosure is shown.

[0022] Figure 6 An example user information field format indicating a peer-to-peer (p2p) service according to an example embodiment of the present disclosure is shown.

[0023] Figure 7 An example common information field format indicating a p2p service according to an example embodiment of the present disclosure is shown.

[0024] Figure 8 An example trigger type subfield encoding of a BSR trigger frame indicating a p2p service according to an example embodiment of the present disclosure is shown.

[0025] Fig. 9 FIG. 4 is a flowchart illustrating a process of sending a request for buffer status data of a p2p service according to an exemplary embodiment of the present disclosure.

[0026] Fig. 10A An example quality of service (QoS) control field format according to an example implementation of the present disclosure is shown.

[0027] Fig. 10B An example format of an aggregation control (A-control) subfield of a control field for BSR control according to an example embodiment of the present disclosure is shown.

[0028] Fig.11An example format of a control information subfield of an A control subfield for reporting a buffer status of a p2p service according to an example embodiment of the present disclosure is shown.

[0029] Fig.12 An example QoS control field format for reporting the buffer status of p2p traffic according to an example embodiment of the present disclosure is shown.

[0030] Fig.13 An example format of the A control subfield of the control field for reporting the buffer status of p2p services according to an example embodiment of the present disclosure is shown.

[0031] Fig.14 FIG. 4 is a flowchart showing a process of reporting a buffer status of a p2p service according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] Before turning to the drawings showing certain embodiments in detail, it should be understood that the present disclosure is not limited to the details or methods set forth in the specification or shown in the drawings. It should also be understood that the terminology used herein is for descriptive purposes only and should not be considered as limiting.

[0033] Figure 1 1 is a block diagram of an example artificial reality system environment 100 in which a console 110 operates. Figure 1 An example environment is provided in which devices can transmit traffic flows with different latency sensitivities / requirements. In some embodiments, the artificial reality system environment 100 includes a HWD 150 worn by a user, and a console 110 that provides artificial reality content to the HWD 150. A head wearable display (HWD) may be referred to as, include, or be part of a head mounted display (HMD), a head mounted device (HMD), a head wearable device (HWD), a head worn display (HWD), or a head worn device (HWD). In one aspect, the HWD 150 may include various sensors for detecting the position, orientation, and / or gaze direction of a user wearing the HWD 150, and providing the detected position, orientation, and / or gaze direction to the console 110 via a wired connection or a wireless connection. The HWD 150 may also identify an object (e.g., body, hand, face).

[0034] The console 110 may determine a field of view within the artificial reality space corresponding to the detected position, orientation, and / or gaze direction, and generate an image depicting the determined field of view. The console 110 may also receive one or more user inputs and modify the image based on the user inputs. The console 110 may provide the image to the HWD 150 for rendering. The image corresponding to the user's field of view in the artificial reality space may be presented to the user. In some embodiments, the artificial reality system environment 100 includes a plurality of Figure 1 More parts, fewer parts, or the same parts as shown in Figure 1 In some embodiments, the functionality of one or more components of artificial reality system environment 100 may be distributed among multiple components in a manner different from that described herein. For example, some functions of console 110 may be performed by HWD 150, and / or some functions of HWD 150 may be performed by console 110.

[0035] In some embodiments, HWD 150 is an electronic component that can be worn by a user and can present or provide an artificial reality experience to the user. HWD 150 can render one or more images, videos, audio, or some combination thereof to provide an artificial reality experience to the user. In some embodiments, the audio is presented via an external device (e.g., a speaker and / or headphones) that receives audio information from HWD 150, console 110, or both and presents the audio based on the audio information. In some embodiments, HWD 150 includes a sensor 155, an eye tracker 160, a communication interface 165, an image renderer 170, an electronic display 175, a lens 180, and a compensator 185. These components can operate together to detect the position of HWD 150 and the gaze direction of the user wearing HWD 150, and render an image of a field of view corresponding to the detected position and / or orientation of HWD 150 in artificial reality. In other ... Figure 1 More parts, fewer parts, or the same parts as shown in Figure 1 The components shown in the figure are different components.

[0036] In some embodiments, sensor 155 includes an electronic component, or a combination of an electronic component and a software component, that detects the position and / or orientation of HWD 150. Examples of sensor 155 may 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 position. For example, one or more accelerometers may measure translational movement (e.g., forward / backward, up / down, left / right), and one or more gyroscopes may measure rotational movement (e.g., pitch, yaw, roll). In some embodiments, sensor 155 detects translational movement and / or rotational movement, and determines the orientation and position of HWD 150. In one aspect, sensor 155 may detect translational movement and / or rotational movement relative to the previous orientation and position of HWD 150, and determine the new orientation and / or position of HWD 150 by accumulating or integrating the detected translational movement and / or rotational movement. For example, assuming that HWD 150 is facing a direction 25 degrees from a reference direction, sensor 155 may determine that HWD 150 is now facing or facing a direction 45 degrees from the reference direction in response to detecting that HWD 150 has turned 20 degrees. For another example, assuming that HWD 150 is located two feet away from a reference point in a first direction, sensor 155 may determine that HWD 150 is now located at the vector product of two feet in the first direction and three feet in the second direction in response to detecting that HWD 150 has moved three feet in the second direction.

[0037] In some embodiments, the eye tracker 160 includes an electronic component, or a combination of an electronic component and a software component, that determines the gaze direction of the user of the HWD 150. In some embodiments, the HWD 150, the console 110, or a combination thereof can generate image data of artificial reality in conjunction with the gaze direction of the user of the HWD 150. In some embodiments, the plurality of eye trackers 160 includes two eye trackers, wherein each eye tracker 160 captures an image of a corresponding eye and determines the gaze direction of the eye. In one example, the eye tracker 160 determines the angular rotation of the eye, the translation of the eye, the torsion change of the eye, and / or the shape change of the eye based on the captured image of the eye, and determines the relative gaze direction relative to the HWD 150 based on the determined angular rotation of the eye, the translation of the eye, and the torsion change of the eye. In one approach, the eye tracker 160 can illuminate or project a predetermined reference pattern or structure 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, thereby determining the relative gaze direction of the eye relative to the HWD 150. In some embodiments, the eye tracker 160 determines the user's gaze direction in conjunction with the orientation of the HWD 150 and the relative gaze direction relative to the HWD 150. For example, assuming that the HWD 150 is oriented in a direction 30 degrees from a reference direction, and the relative gaze direction of the HWD 150 is -10 degrees (or 350 degrees) relative to the HWD 150, the eye tracker 160 may determine that the user's gaze direction is 20 degrees from the reference direction. In some embodiments, the user of the HWD 150 may configure the HWD 150 (e.g., via user settings) to enable or disable the eye tracker 160. In some embodiments, the user of the HWD 150 is prompted to enable or disable the eye tracker 160.

[0038] In some embodiments, hand tracker 162 includes electronic components, or a combination of electronic components and software components, that track a user's hand. In some embodiments, hand tracker 162 includes or is coupled to an imaging sensor (e.g., a camera) and an image processor that can detect the shape, position, and orientation of a hand. Hand tracker 162 can generate hand tracking measurements that indicate the shape, position, and orientation of the detected hand.

[0039] In some embodiments, the communication interface 165 includes an electronic component, or a combination of an electronic component and a software component, that communicates with the console 110. The communication interface 165 can communicate with the communication interface 115 of the console 110 via a communication link. The communication link can be a wireless link, a wired link, or both. Examples of the wireless link can include a cellular communication link, a near field communication link, Wi-Fi, Bluetooth, or a wireless communication link of any communication. Examples of the wired link can include a universal serial bus (USB), Ethernet, FireWire, a high-definition multimedia interface (HDMI), or any wired communication link. In an embodiment where the console 110 and the head wearable display 150 are implemented on a single system, the communication interface 165 can communicate with the console 110 via a bus connection or a conductive trace. Through the communication link, the communication interface 165 can send sensor measurements to the console 110, which indicate the determined position of the HWD 150, the orientation of the HWD 150, the determined gaze direction of the user, and / or hand tracking measurements. Additionally, via the communication link, communication interface 165 may receive sensor measurements from console 110 that are indicative of or correspond to an image to be rendered.

[0040] Using the communication interface, the console 110 (or HWD 150) can coordinate operations on the link 101 to reduce conflicts or interference. For example, the console 110 can coordinate communications between the console 110 and the HWD 150. In some embodiments, the console 110 can periodically send beacon frames to announce / announce the existence of a wireless link between the console 110 and the HWD 150 (or between two HWDs). In an embodiment, the HWD 150 can monitor or receive beacon frames from the console 110, and can schedule communications with the HWD 150 (e.g., using information in the beacon frames, such as offset values) to avoid conflicts with or interference with communications between the console 110 and / or the HWD 150 and other devices.

[0041] The console 110 and the HWD 150 may communicate using a link 101 (e.g., an inline link). Data (e.g., a traffic flow) may flow in the direction of the link 101. For example, the console 110 may communicate using a downlink (DL) communication to the HWD 150, and the HWD 150 may communicate using an uplink (UL) communication to the console 110.

[0042] In some embodiments, the image renderer 170 includes, for example, an electronic component that generates one or more images for display according to a change in the field of view of the artificial reality space, or a combination of an electronic component and a software component. In some embodiments, the image renderer 170 is implemented as a processor (or a graphics processing unit (GPU)) that executes instructions to perform the various functions described herein. The image renderer 170 can receive data depicting an image to be rendered through a communication interface 165, and render the image through an electronic display 175. In some embodiments, the data from the console 110 can be encoded, and the image renderer 170 can decode the data to generate and render an image. In one aspect, the image renderer 170 receives an encoded image from the console 110 and decodes the encoded image so that the communication bandwidth between the console 110 and the HWD 150 can be reduced.

[0043] In some embodiments, the image renderer 170 receives additional data from the console 110, the additional data including object information indicating virtual objects in the artificial reality space and depth information indicating the depth of these virtual objects (or the distance from the HWD 150). Therefore, the image renderer 170 can receive the object information and / or the depth information from the console 110. The image renderer 170 can also receive updated sensor measurements from the sensor 155. The following process may be computationally exhaustive and may not be performed within the frame time (e.g., less than 11 milliseconds (ms) or 8ms): detecting the position and orientation of the HWD 150 and / or the gaze direction of the user wearing the HWD 150 by the HWD 150, and generating and sending a high-resolution image (e.g., 1920 pixels by 1080 pixels, or 2048 pixels by 1152 pixels) corresponding to the detected position and gaze direction by the console 110 to the HWD 150.

[0044] In some embodiments, the image renderer 170 may perform shading, reprojection, and / or blending to update the image of the artificial reality to correspond to the updated position and / or orientation of the HWD 150. Assuming that the user turns his head after the initial sensor measurements, the image renderer 170 may generate a small portion (e.g., 10%) of the image corresponding to the updated field of view in the artificial reality based on the updated sensor measurements and append the portion to the image in the image data from the console 110 by reprojection, rather than rebuilding the entire image in response to these updated sensor measurements. The image renderer 170 may perform shading and / or blending on the additional edges. Thus, the image renderer 170 may generate an artificial reality image without reconstructing the artificial reality image based on the updated sensor measurements.

[0045] In other embodiments, when no image is received from the console 110 within the frame time, the image renderer 170 generates one or more images through a shading process and a reprojection process. For example, the shading process and the reprojection process may be adaptively performed according to the change of the field of view of the artificial reality space.

[0046] In some embodiments, the electronic display 175 is an electronic component that displays an image. The electronic display 175 may be, for example, a liquid crystal display or an organic light emitting diode display. The electronic display 175 may be a transparent display that allows the user to see through. In some embodiments, when the user wears the HWD 150, the electronic display 175 is located near the user's eyes (e.g., less than 3 inches). In one aspect, the electronic display 175 emits light or projects light toward the user's eyes based on the image generated by the image renderer 170.

[0047] In some embodiments, lens 180 is a mechanical component that modifies the light received from electronic display 175. Lens 180 can magnify the light from electronic display 175 and correct optical errors associated with the light. Lens 180 can be a Fresnel lens, a convex lens, a concave lens, a filter, or any suitable optical component that modifies the light from electronic display 175. Although electronic display 175 is very close to the eye, through lens 180, the light from electronic display 175 can also reach the pupil so that the user can see the image displayed by electronic display 175.

[0048] In some embodiments, compensator 185 includes electronic components, or a combination of electronic components and software components, that perform compensation to compensate for any distortion or aberration. In one aspect, lens 180 introduces optical aberrations (e.g., chromatic aberration), pincushion distortion, barrel distortion, etc. Compensator 185 can determine compensation (e.g., pre-distortion) to be applied to an image to be rendered by image renderer 170 to compensate for the distortion caused by lens 180, and apply the determined compensation to the image from image renderer 170. Compensator 185 can provide the pre-distorted image to electronic display 175.

[0049] In some embodiments, console 110 is an electronic component, or a combination of electronic and software components, that provides content to be rendered to HWD 150. In one aspect, console 110 includes communication interface 115 and content provider 130. These components can operate together to determine a field of view in artificial reality corresponding to the position of HWD 150 and / or the gaze direction of a user of HWD 150 (e.g., the user's field of view (FOV)), and can generate an image of the artificial reality corresponding to the determined field of view. In other embodiments, console 110 includes more than 100 components. Figure 1 More parts, fewer parts, or the same parts as shown in Figure 1 150. In some embodiments, the console 110 is integrated as a part of the HWD 150. In some embodiments, the communication interface 115 is an electronic component that communicates with the HWD 150, or a combination of an electronic component and a software component. The communication interface 115 can be a corresponding component of the communication interface 165, which communicates with the communication interface 115 of the console 110 via a communication link (e.g., a USB cable, a wireless link). Through the communication link, the communication interface 115 can receive sensor measurements from the HWD 150, which indicate the determined position and / or orientation of the HWD 150, the determined gaze direction of the user, and / or hand tracking measurements. In addition, through the communication link, the communication interface 115 can send data depicting the image to be rendered to the HWD 150.

[0050] The content provider 130 may include or correspond to a component that generates content to be rendered based on the position and / or orientation of the HWD 150, the gaze direction of the user, and / or the hand tracking measurement results. In one aspect, the content provider 130 determines the field of view of the artificial reality based on the position and orientation of the HWD 150, and / or the gaze direction of the user of the HWD 150. For example, the content provider 130 maps the position of the HWD 150 in the physical space to a position in the artificial reality space, and determines the field of view of the artificial reality space from the mapped position in the artificial reality space along a direction corresponding to the orientation of the HWD 150 and / or the gaze direction of the user.

[0051] The content provider 130 may generate image data describing an image of the determined field of view of the artificial reality space, and send the image data to the HWD 150 via the communication interface 115. The content provider may also generate a hand model (or other virtual object) corresponding to the user's hand based on the hand tracking measurements, and generate hand model data indicating the shape, position, and orientation of the hand model in the artificial reality space.

[0052] In some embodiments, the content provider 130 generates metadata including motion vector information, depth information, edge information, object information, etc. associated with the image, and sends the metadata together with the image data to the HWD 150 through the communication interface 115. The content provider 130 may encode and / or add code to the data depicting the image, and may send the encoded and / or added code data to the HWD 150. In some embodiments, the content provider 130 generates an image periodically (e.g., every second) and provides the image to the HWD 150.

[0053] Figure 2 1 is a schematic diagram of HWD 150 according to an exemplary embodiment. In some embodiments, HWD 150 includes a front rigid body 205 and a belt 210. Front rigid body 205 includes electronic display 175 ( Figure 2 Not shown), lens 180 ( Figure 2 ), sensor 155, eye tracker 160A, eye tracker 160B, communication interface 165 and image renderer 170. Figure 2 In the illustrated embodiment, the sensor 155 is located within the front rigid body 205 and may not be visible to the user. In other embodiments, the HWD 150 may have a Figure 2 For example, the image renderer 170, the eye tracker 160A, the eye tracker 160B, and / or the sensor 155 may be located in a different configuration than that shown. Figure 2 The positions shown vary by location.

[0054] Various operations described herein may be implemented on a computer system. Figure 3 1 shows a block diagram of a typical computing system 314 that can be used to implement the present disclosure. In some embodiments, Figure 1 The console 110, HWD 150, or both are implemented by a computing system 314. The computing system 314 can be implemented as a consumer device, such as a smartphone, other mobile phone, tablet computer, wearable computing device (e.g., smart watch, glasses, head wearable display), desktop computer, laptop computer, or the computing system 314 can be implemented using a distributed computing device. The computing system 314 can be implemented to provide VR, AR, MR experience. In some embodiments, the computing system 314 may include conventional computer components, such as a processor 316, a storage device 318, a network interface 320, a user input device 322, and a user output device 324.

[0055] The network interface 320 can provide a connection to a wide area network (e.g., the Internet) to which the WAN interface of the remote server system is also connected. The network interface 320 can include a wired interface (e.g., Ethernet) and / or a wireless interface that implements various radio frequency (RF) data communication standards such as Wi-Fi, Bluetooth, or cellular data network standards (e.g., 3G, 4G, 5G, 60GHz, Long Term Evolution (LTE), etc.).

[0056] The network interface 320 may include a transceiver that allows the computing system 314 to send data to a remote device (e.g., AP, STA) using a transmitter and receive data from a remote device using a receiver. The transceiver may be configured to support transmission / reception as follows: the transmission / reception supports industrial standards that enable two-way communication. An antenna may be attached to the housing of the transceiver and electrically coupled to the transceiver. Additionally or alternatively, a multi-antenna array may be electrically coupled to the transceiver so that multiple beams pointing in different directions may facilitate sending data and / or receiving data.

[0057] The transmitter may be configured to wirelessly transmit frames, time slots, or symbols generated by the processor unit 316. Similarly, the receiver may be configured to receive frames, time slots, or symbols, and the processor unit 316 may be configured to process the frames. For example, the processor unit 316 may be configured to determine the type of frame and process the frame and / or fields of the frame accordingly.

[0058] User input device 322 may include any device (or devices) via which a user may provide signals to computing system 314; computing system 314 may interpret these signals as indicating a particular user request or information. User input device 322 may include any or all of the following: a keyboard, a touch pad, a touch screen, a mouse or other pointing device, a scroll wheel, a click wheel, a dial, a button, a switch, a keypad, a microphone, a sensor (e.g., a motion sensor, an eye tracking sensor, etc.), and the like.

[0059] User output device 324 may include any device via which computing system 314 can provide information to a user. For example, user output device 324 may include a display for displaying images generated by computing system 314 or delivered to computing system 314. The display may combine various image generation technologies (e.g., liquid crystal display (LCD), light-emitting diodes (LED) including organic light-emitting diodes (OLED), projection systems, or cathode ray tubes (CRT), etc.) with supporting electronic devices (e.g., digital-to-analog converters or analog-to-digital converters, or signal processors, etc.). Devices such as touch screens used as input and output devices may be used. Output device 324 may be provided in addition to or in place of a display. Examples include indicator lights, speakers, tactile "display" devices, printers, etc.

[0060] Some embodiments include electronic components, such as microprocessors, storage devices, and memory, storing computer program instructions in computer-readable storage media (e.g., non-transient computer-readable media). Many features described in this specification can be implemented as the following process: the process is specified as a set of program instructions encoded on a computer-readable storage medium. These program instructions, when executed by one or more processors, cause these processors to perform various operations indicated in these program instructions. Examples of program instructions or computer codes include machine codes and files, which are generated, for example, by a compiler, and these files include high-level codes executed by a computer, electronic component, or microprocessor using an interpreter. Processor 316 can provide various functions for computing system 314 by appropriate programming, including any of the following functions: functions described herein as being executed by a server or client, or other functions associated with a message management service.

[0061] It will be appreciated that computing system 314 is illustrative and can be modified and amended. The computer system used in conjunction with the present disclosure may have other capabilities not specifically described herein. In addition, although computing system 314 is described with reference to specific blocks, it will be understood that these blocks are defined for the convenience of description and are not intended to imply a specific physical arrangement structure of component parts. For example, different blocks can be located in the same facility, in the same server frame, or on the same motherboard. In addition, these blocks do not need to correspond to physically different components. Each block can be configured to perform various operations, such as by programming a processor or providing appropriate control circuits, and each block may or may not be reconfigurable, depending on how the initial configuration is obtained. Embodiments of the present disclosure can be implemented in a variety of devices, including electronic devices implemented using any combination of circuits and software.

[0062] 1. Request buffer status report for wireless point-to-point (p2p) services

[0063] IEEE 802.11be Extremely High Throughput (EHT) may be the next generation 802.11 IEEE standard, which may be designated as Wi-Fi 7. According to some embodiments of the present disclosure, a signaling method for requesting / polling a buffer status report (BSR) may be defined. The BSR operation may be performed as follows. The AP may send a trigger frame (e.g., a buffer status report polling (BSRP) trigger frame) to the STA to inquire about the buffer status. The buffer status may be a quantitative indication of how much traffic (e.g., quality of service (QoS) data) is queued at the STA. The STA may indicate the buffer status in data units (e.g., bytes) by including either a QoS control field or a BSR control field in a frame sent to the AP. The STA may indicate the buffer status in response to a BSRP trigger frame or as its own active response.

[0064] Figure 4A4 is a diagram 400 of a buffer status report (BSR) request (e.g., a BSRP trigger frame 402) and a BSR response (e.g., a high-efficiency (HE) trigger-based (TB) uplink (UL) aggregate MAC Protocol Data Unit (A-MPDU) frame 406) according to an example embodiment of the present disclosure. As shown in FIG. 4, the AP may send a BSRP trigger frame 402. After a short inter-frame space (SIFS) 404, STAs (e.g., STA1 to STA4) may respectively send the buffer status of these STAs contained in HE TB ULA-MPDU frames 406, which may be acknowledged by a multi-STA block acknowledgment (M-BA) frame 410 after another SIFS 408. The buffer status may be contained in a QoS control field or a BSR HE control field in a QoS data frame or a QoS null frame. The STA may acknowledge (ACK) or may not acknowledge the BSR request.

[0065] Figure 4B 1 is a schematic diagram of a system environment including a point-to-point (p2p) service in a wireless local area network (WLAN) according to an exemplary embodiment of the present disclosure. A first non-AP STA device 470 may be configured to send UL / downlink (DL) service 472 to / receive UL / DL service 472 from an AP device 460, and the first non-AP STA device 470 may be configured to send / receive p2p service 474 to / from a second non-AP device 480. A third non-AP STA device 490 may be configured to send / receive UL / DL service 492 to / from the AP device 460.

[0066] Figure 5A , Figure 5B and Figure 5C An example of a BSR trigger frame format 500 (eg, BSRP trigger frame) according to an example embodiment of the present disclosure is shown. Figure 5D An example trigger type subfield encoding 590 is shown according to an example implementation of the present disclosure. FIG. 5A to FIG. 5DThe BSR trigger frame format 500 may include: a frame control field 501, a duration field 502, a receiver address field 503, a transmitter address field 504, a common information ("Common Info") field 550, a user information list field 510 including multiple user information (User Info) fields (for example, user information ("User Info") field format 520), a padding field 505 and / or a frame check sequence (FCS) field 506. The user information field format 520 may include an association identifier (AID12) subfield 521, a resource unit (RU) allocation subfield 522, a UL forward error correction (FEC) coding type subfield 523, a UL high efficiency modulation and coding scheme (HE modulation coding scheme, HE-MCS) subfield 524, a UL dual carrier modulation (DCM) subfield 525, a spatial stream (SS) allocation / RA-RU information subfield 526, a UL target received power subfield 527, a reserved subfield 528 and / or a trigger dependent user information (trigger dependent user information) subfield 529. The trigger dependent user information 529 may or may not be present in the trigger frame.The common information field 550 may include: a trigger type subfield 551, a UL length subfield 552, a more trigger frame (TF) subfield 553, a carrier sense (CS) required subfield 554, a UL BW (bandwidth) subfield 555, a guard interval (GI) subfield and a long training field (LTF) type subfield 556, a multi-user (MU)-multiple-input multiple-output (MIMO) HE-LTF mode subfield 557, a HE-LTF symbol number and a mid-amble periodicity subfield 558, a UL space-time block coding (STBC) subfield 559, a low-density parity check (LDPC) additional symbol segment subfield 560, and an AP Tx power subfield 561, pre-FEC fill factor subfield 562, packet extension (PE) disambiguation subfield 563, UL spatial reuse (UL spatial reuse) subfield 564, Doppler subfield 565, UL HE-S1G-A2 reserved subfield 566, reserved subfield 567 and / or trigger-related common information subfield 568. The trigger type subfield 551 may be set to a value (e.g., 4) indicating the BSRP defined in item 592 in the trigger type subfield encoding 590. The trigger-related common information 568 may be present in the trigger frame or may not be present.

[0067] refer to FIG. 5A to FIG. 5D , the AP may send a BSRP trigger frame having a trigger frame format 500. The trigger type subfield of the BSRP trigger (eg, trigger type subfield 551) may be set to 4, which is used to indicate a BSRP trigger frame (see Figure 5D). The BSRP trigger frame may instruct one or more STAs to report the UL buffer status of the one or more STAs in a response frame (e.g., a QoS data frame or a QoS empty frame). These BSR operations may be used in a target wake time (TWT) mechanism (e.g., restricted TWT (R-TWT)) defined in a wireless local area network (WLAN) protocol (e.g., 802.11be). In the TWT mechanism, STAs (wireless devices such as smart phones or HWDs) may adopt a wake-up time schedule that periodically wakes up these STAs to send / receive data. R-TWT may force all other 802.11be compatible devices to complete the transmission of these devices before the start of the TWT service period (SP). R-TWT may be used to provide point-to-point (p2p) services (e.g., Figure 4B 474 of the device 470 in the STA). Such a TWT mechanism (e.g., R-TWT) may require the ability to report buffer status in order to efficiently perform the p2p service of the STA. For example, an AP (e.g., Figure 4B The AP 460 in the R-TWT SP can allocate resources (e.g., transmission opportunities (TXOP)) to the p2p service of the STA (e.g., the p2p service 474 of the device 470) according to the buffer status during the R-TWT SP. During the ongoing SP, if the AP can query the status of the point-to-point (p2p) service of the STA, this will help efficient operation (e.g., help the AP to allocate resources efficiently). For example, the STA can indicate an empty buffer for p2p to the AP to indicate that the STA has completed the delivery of latency-sensitive traffic (LatencySensitive Traffic, LST). The TWT SP can be terminated (if the uplink / downlink (UL / DL) LST has also been delivered) to save power, and the AP can serve other STAs. The STA can indicate a non-empty buffer for p2p to the AP near the end of the SP to convey that the STA still has an LST. The AP can extend the SP for the STA to deliver the remaining buffered traffic. The AP can also query its own buffer status to facilitate the above operations.

[0068] However, other / traditional buffer status request / polling (BSRP) trigger mechanisms may only request the uplink (UL) buffer status of a STA. The AP may not be able to query the status of a STA's point-to-point (p2p) service using a BSRP trigger frame. Therefore, it is necessary / beneficial to define a new request method for the AP to query / poll the buffer status of a p2p service.

[0069] To solve this problem, a signaling method for requesting / polling a buffer status report for p2p services may be provided / defined. In some embodiments, the format of the BSRP trigger frame may be redefined to indicate a request for the buffer status of a p2p service. For example, a subfield / bit of a common information ("common information") field or a subfield / bit of a user information ("user information") field may be redefined to indicate a request for the buffer status of a p2p service. A new trigger type for a p2p service may be defined using the trigger type field of the common information field.

[0070] In one approach, one or more bits ("first p2p bit") (e.g., reserved bits) in the user information field of a BSRP trigger frame may be used to indicate a p2p buffer status request. When the first p2p bit in a trigger frame sent by an AP is set, the trigger frame may indicate / request / trigger the STA to include the buffer status of its p2p traffic in the response using a BSR procedure. For example, when the first p2p bit is set to a first value (e.g., 1), the STA may or should send the buffer status of its p2p traffic in response to the trigger frame. When the first p2p bit is set to a second value (e.g., 0), the STA may send the buffer status of its uplink (UL) traffic in response to the trigger frame. Since the trigger frame uses the user information field, using or not using this triggering method may be user or STA dependent. For example, the user information list field may include multiple user information fields, wherein the first user information field may indicate a p2p buffer status request to a first user / STA, and the second user information field may indicate a UL buffer status request to a second user / STA. In some embodiments, one or more defined / repurposed bits from any one or more fields (e.g., "reserved bits" other than the user information field or other than the user information field) may be used to indicate to the STA to include the buffer status of its p2p traffic and / or other types of traffic (e.g., UL and / or DL).

[0071] In one approach, one or more bits ("second p2p bit") (e.g., reserved bits) in the common information field of the BSRP trigger frame can be used to indicate a p2p buffer status request. When the second p2p bit in the trigger frame sent by the AP is set, the trigger frame can indicate / request / trigger the STA to include the buffer status of its p2p traffic in the response using the BSR process. For example, when the second p2p bit is set to a first value (e.g., 1), the STA can or should send the buffer status of its p2p traffic in response to the trigger frame. When the second p2p bit is set to a second value (e.g., 0), the STA can send the buffer status of its uplink traffic in response to the trigger frame. Because the trigger frame uses the common information field, all users or all STAs receiving the trigger frame can use (or trigger) this triggering method. In some embodiments, one or more defined / reused bits from any one or more fields (e.g., different from the common information field) can be used to indicate to the STA its buffer status including its p2p traffic and / or other types of traffic (e.g., UL and / or DL).

[0072] In one approach, a new BSRP-p2p trigger frame may be defined to indicate a p2p buffer status request. A new / specific trigger frame type for p2p traffic (e.g., "BSRP-p2p trigger frame type") may be added / introduced / defined as a value used in the trigger type field of the common information field. For example, a value such as 8 or any value not used by other types may be used. In some embodiments, the frame format may be the same or similar to the format of the BSRP trigger frame. When a STA receives a BSRP-p2p trigger frame with the trigger type field set to the BSRP-p2p trigger frame type, the STA may or should include its buffer status for its p2p traffic in the response using the BSR procedure.

[0073] In one approach, an access point may include one or more processors. The one or more processors may be configured to generate a first frame, the first frame being used to trigger a receiver device to send a response frame, the response frame including buffer status data corresponding to a wireless traffic between the receiver device and another device. The one or more processors may be configured to wirelessly send the generated first frame to one or more devices via a transmitter.

[0074] In one approach, the wireless service may include a peer-to-peer (p2p) service between the receiver device and another device. In some embodiments, the one or more processors may be configured to, when generating the first frame, set a frame type field of the first frame to indicate a type of a buffer status trigger frame.

[0075] In one embodiment, the first frame may include a first user information field associated with the first device. The one or more processors may be configured to, when generating the first frame, set a subfield of the first user information field to a first value, the first value indicating a buffer status request for a wireless service between the first device and the second device. The first frame may include a second user information field associated with a third device. The one or more processors may be configured to, when generating the first frame, set a subfield of the second user information field to a second value, the second value indicating a buffer status request for a wireless service between the access point and the third device, to trigger the third device to send a response frame, the response frame including buffer status data corresponding to the wireless service between the access point and the third device.

[0076] In one approach, the first frame may include a common information field that carries information related to multiple users or receiver devices. The one or more processors may be configured to, when generating the first frame, set a subfield of the common information field to a value indicating a buffer status request for wireless traffic between the receiver device and another device.

[0077] In one embodiment, the first frame may include a common information field. The one or more processors may be configured to, when generating the first frame, set a subfield of the common information field to a value that is used to trigger multiple users or receiver devices to send corresponding response frames including corresponding buffer status data corresponding to a point-to-point (p2p) service.

[0078] In one approach, the first frame may include a frame type field. The one or more processors may be configured to, when generating the first frame, set the frame type field to indicate a type of a buffer status trigger frame for a peer-to-peer (p2p) service.

[0079] In one approach, the first frame may include a common information field that carries information related to multiple users or receiver devices. The frame type field may be a subfield of the common information field.

[0080] In one embodiment, the first frame may include a frame type field. The one or more processors may be configured to, when generating the first frame, set the frame type field to a type that is used to trigger multiple users or receiver devices to send corresponding response frames including corresponding buffer status data corresponding to a wireless point-to-point (p2p) service.

[0081] The embodiments of the present disclosure have at least the following advantages and benefits. The embodiments of the present disclosure may provide a useful technique for querying the point-to-point (p2p) service status of a STA using a BSRP trigger frame, thereby providing a new request method for an AP to query / poll the buffer status of a p2p service. In some embodiments, a new request method may be provided by redefining the format of a BSRP trigger frame or by defining a new BSR-p2p trigger frame type. In this way, an AP may query / poll the buffer status of a p2p service of a specific user (e.g., using a user information field) or all users (e.g., using a common information field).

[0082] Figure 6 An example user information ("user information") field format 600 indicating a peer-to-peer (p2p) service according to an example embodiment of the present disclosure is shown. Except for subfield 601, user information field format 600 may be the same or similar to user information field format 520. In some embodiments, subfield 601 of user information field format 600 may redefine reserved bit 528 (see Figure 5B), to indicate / request / trigger the STA to include the buffer status of its p2p traffic in the response using the BSR process. In some embodiments, subfield 601 may be a single bit (e.g., bit B39 of user information field format 600). When bit B39 in the trigger frame is set, the trigger frame sent by the AP (e.g., AP 460) may indicate / request / trigger the STA (e.g., device 470) to include the buffer status of its p2p traffic (e.g., p2p traffic 474 between device 470 and device 480) in the response. For example, when bit B39 is set to a first value (e.g., 1), the STA may or should send the buffer status of its p2p traffic in response to the trigger frame. When bit B39 is set to a second value (e.g., 0), the STA may send the buffer status of its uplink (UL) traffic (e.g., UL traffic 472 from device 470 to AP 460) in response to the trigger frame. Because the trigger frame uses the user information field, the use or non-use of the trigger method may be dependent on the user or STA (e.g., the user or STA defined by the association ID in the AID12 subfield 521). For example, the user information list field may include multiple user information fields (each user information field having the user information field format 600), wherein a first user information field may indicate a p2p buffer status request to a first user / STA (e.g., device 470), and a second user information field may indicate a UL buffer status request to a second user / STA (e.g., device 490). In some embodiments, one or more defined / repurposed bits (e.g., different from the user information field 600 or different from the "reserved bit" B39 of the user information field) from any one or more fields may be used to indicate to the STA its buffer status including its p2p traffic and / or other types of traffic (e.g., UL and / or DL).

[0083] Figure 7 An example public information ("public information") field format 700 indicating a p2p service according to an example embodiment of the present disclosure is shown. The public information field format 700 may be the same or similar to the public information field format 550 except for the subfield 701. In some embodiments, the subfield 701 of the public information field format 700 may redefine the reserved bit 567 (see Figure 5C) to indicate a p2p buffer status request. In some embodiments, subfield 701 may be a single bit (e.g., bit B63 of common information field format 700). When bit B63 in a trigger frame sent by an AP (e.g., AP 460) is set, the trigger frame may indicate / request / trigger a STA (e.g., device 470) to include its buffer status for its p2p service (e.g., p2p service 474 between device 470 and device 480) in a response using a BSR procedure. For example, when bit B63 is set to a first value (e.g., 1), the STA may or should send the buffer status of its p2p service in response to the trigger frame. When bit B63 is set to a second value (e.g., 0), the STA may send the buffer status of its uplink service in response to the trigger frame. Because the trigger frame uses a common information field, all users or all STAs (e.g., all STAs associated with AP 460, including devices 470 and 490) that receive the trigger frame may use (or trigger) the trigger method. In some embodiments, one or more defined / repurposed bits from any one or more fields (e.g., other than the common information field) may be used to indicate to the STA its buffer status including its p2p traffic and / or other types of traffic (e.g., UL and / or DL).

[0084] Figure 8 An example trigger type subfield encoding 800 of a BSR trigger frame indicating p2p traffic according to an example embodiment of the present disclosure is shown. In one approach, a new BSRP-p2p trigger frame may be defined to indicate a p2p buffer status request. A new trigger frame type 802 for p2p traffic (e.g., "BSRP-p2p trigger frame type") may be added / introduced / defined as a trigger type field in a common information field (e.g., Figure 7 The value used in the trigger type field 702 of the common information field 700 in the BSRP trigger frame. For example, a value such as 8 or any value not used by other types can be used (for example, when using the trigger type subfield encoding 800, 8≤N≤15). In some embodiments, the frame format can be different from the format of the BSRP trigger frame (for example, Figure 5A , Figure 5B and Figure 5C When a STA (e.g., device 470) receives a BSRP-p2p trigger frame with a trigger type field set to a BSRP-p2p trigger frame type from an AP (e.g., AP 460), the STA may or should use a BSR procedure to include the buffer status of its p2p traffic in the response.

[0085] Fig. 910 is a flow chart illustrating a process 900 of sending a request for buffer status data for a p2p service according to an example embodiment of the present disclosure. In some embodiments, the process 900 is performed by an access point (e.g., AP 460 or a soft-enabled AP (soft AP)). In some embodiments, the process 900 is performed by other entities. In some embodiments, the process 900 includes more steps or fewer steps than those shown in FIG. 10, or includes steps different from those shown in FIG. 10.

[0086] In one approach, an access point (e.g., AP 460) may generate 902 a first frame (e.g., a BSRP trigger frame including a user information field format 600, a BSRP trigger frame including a common information format 700, or a trigger frame having a new BSRP-p2p type 802) to trigger a receiver device (e.g., device 470) to send a response frame (e.g., a BSR response frame) including buffer status data corresponding to wireless traffic (e.g., p2p traffic 474) between the receiver device (e.g., device 470) and another device (e.g., device 480). In some embodiments, the wireless traffic may include point-to-point (p2p) traffic between the receiver device and the other device. In some embodiments, the access point may set a frame type field (e.g., trigger type subfield 702) of the first frame to indicate a type of buffer status trigger frame (e.g., BSRP type 592) when generating the first frame, because the first frame reuses / redefines the format of an existing BSR trigger type frame.

[0087] In some embodiments, the first frame (e.g., a BSRP trigger frame including the user information field format 600) may include a first user information field associated with the first device (e.g., the user information field format 600 having the AID12 subfield set to be associated with the first device 470). The access point may set the subfield of the first user information field (e.g., subfield 601) to a first value (e.g., 1) when generating the first frame, the first value indicating a buffer status request for wireless traffic between the first device (e.g., device 470) and the second device (e.g., device 480). The first frame may include a second user information field associated with a third device (e.g., the user information field format 600 having the AID12 subfield set to be associated with the third device 490). The access point may, when generating the first frame, set a subfield (e.g., subfield 601) of the second user information field to a second value (e.g., 0), wherein the second value indicates a buffer status request for a wireless service (e.g., UL / DL service 492) between the access point (e.g., AP 460) and a third device (e.g., device 490), thereby triggering the third device to send a response frame including buffer status data corresponding to the wireless service between the access point and the third device (e.g., UL service 492 from the third device 490).

[0088] In some embodiments, the first frame (e.g., a BSRP trigger frame including the common information format 700) may include a common information field carrying information related to multiple users or receiver devices. The access point (e.g., AP 460) may set a subfield (e.g., subfield 701) of the common information field (e.g., common information format 700) to a value (e.g., 1) when generating the first frame, which indicates a buffer status request for wireless traffic between the receiver device (e.g., device 470) and another device (e.g., device 480).

[0089] In some embodiments, the first frame (e.g., a BSRP trigger frame including the common information format 700) may include a common information field. The access point (e.g., AP 460) may, when generating the first frame, set a subfield (e.g., subfield 701) of the common information field (e.g., common information format 700) to a value (e.g., 1) for triggering a plurality of user or receiver devices (e.g., device 470 and device 490) to send corresponding response frames including corresponding buffer status data corresponding to a point-to-point (p2p) service.

[0090] In some embodiments, the first frame (e.g., a trigger frame with the new BSRP-p2p type 802) may include a frame type field (e.g., the trigger type subfield 702). The access point may set the frame type field to indicate the type of buffer status trigger frame for point-to-point (p2p) traffic (e.g., the new BSRP-p2p type 802) when generating the first frame. The first frame may include a common information field that carries information related to multiple users or receiver devices (e.g., device 470 and device 490). The frame type field may be a subfield of the common information field (e.g., the trigger type subfield 702 of the common information field format 700).

[0091] In some embodiments, the first frame (e.g., a trigger frame with the new BSRP-p2p type 802) may include a frame type field (e.g., the trigger type subfield 702 of the common information field format 700). The access point may set the frame type field to a type (e.g., the new BSRP-p2p type 802) when generating the first frame: the type is used to trigger multiple users or receiver devices (e.g., device 470 and device 490) to send corresponding response frames including corresponding buffer status data corresponding to wireless point-to-point (p2p) services.

[0092] In one approach, an access point (eg, AP 460) may wirelessly transmit 904 the generated first frame to one or more devices (eg, device 470 and device 490) via a transmitter of the access point.

[0093] 2. Provide buffer status reporting for wireless point-to-point (p2p) services

[0094] Fig. 10A and Fig. 10B (1) using the Quality of Service (QoS) control field format ( Fig. 10A ) and (2) using the Aggregate Control (A-Control) subfield format ( Fig. 10B )'s two buffer status reporting processes.

[0095] Fig. 10AAn example QoS control field format 1000 is shown according to an example implementation of the present disclosure. The QoS control field format 1000 may include a subfield 1001 (bits 0-3), a subfield 1002 (bit 4), a subfield 1003 (bits 5-6), a subfield 1004 (bit 7), and / or a subfield 1005 (bits 8-15). A STA (e.g., device 470) may report its buffer status by specifying a queue size in a QoS control field of a frame (e.g., a QoS data frame or a QoS null frame) and sending the frame to an AP (e.g., AP 460). For example, in response to a buffer status report request (e.g., a BSRP trigger frame) from an AP (e.g., AP 460), a receiver STA (e.g., device 470) may send a QoS data frame or a QoS data contention free (CF)-ACK frame 1010 to the AP to report buffer status data related to UL traffic of a specific traffic identifier (TID). The STA may set, in the QoS control field of frame 1010, (1) subfield 1001 to the TID; (2) subfield 1002 to 1; (3) subfield 1003 to an Ack policy indicator; (4) subfield 1004 to a value indicating the presence of an aggregated MAC service data unit (A-MSDU); and / or (5) subfield 1005 to the queue size for the UL traffic of the TID set in subfield 1001. In response to a buffer status report request from the AP, the receiver STA may send a QoS null frame 1020 to the AP to report buffer status data related to the UL traffic of a specific TID. The STA may set, in the QoS Control field of frame 1020, (1) subfield 1001 to the TID; (2) subfield 1002 to 1; (3) subfield 1003 to the Ack policy indicator; and / or (4) subfield 1005 to the queue size for UL traffic of the TID set in subfield 1001. For QoS null frames, subfield 1004 may not be used (or may be "reserved") when reporting buffer status data.

[0096] Fig. 10BAn example format of an Aggregation Control (A-Control) subfield 1050 of a control field for BSR control according to an example embodiment of the present disclosure is shown. The A-Control subfield format 1050 of a High Efficiency (HE) variant High Throughput (HT) Control field may include a plurality of HE Control fields 1060 (including an HE Control-1 field 1060-1, an HE Control-2 field 1060-2, ..., 1060-N) and a padding field 1061. Each HE Control may include a Control ID field 1070 and a Control Information field 1080. For a BSR response, the Control ID field 1070 may be set to a value indicating a BSR (e.g., 3) (see Table 1). The control information field (or BSR control field) 1080 may include: an access category identifier (ACI) bitmap subfield 1081, an incremental TID subfield 1082, an ACI high subfield 1083, a scaling factor subfield 1084, a queue size high subfield 1085, and / or an all queue size (queue size all) subfield 1086. For example, in response to a buffer status report request (e.g., a BSRP trigger frame) from an AP (e.g., AP 460), a receiver STA (e.g., device 470) may report its buffer status by specifying a queue size in an 'all queue size' subfield 1086 of a frame and sending the frame to the AP. The queue size of the ACI indicated in the ACI bitmap subfield 1081 may be reported, and the ACI bitmap subfield 1081 indicates an access category (or multiple access categories) intended for data stored in the buffer of the STA. Each bit in the ACI bitmap subfield 1081 may indicate the presence of a service intended for the corresponding AC. The value set in the Incremental TID subfield 1082 may indicate the number of TIDs corresponding to the number of bits set to 1 in the ACI Bitmap subfield 1081. For example, if (1) the number of bits set to 1 in the ACI Bitmap subfield is equal to 1, and (2) the Incremental TID is set to a value of 1, the Incremental TID may indicate 2 TIDs. If the number of bits set to 1 in the ACI Bitmap subfield is equal to 0, the values ​​0 to 2 in the Incremental TID may not be applicable, for example, may not indicate the number of TIDs. The value set in the All Queue Sizes subfield 1086 may indicate / report the combined queue size of all ACs indicated in the ACI Bitmap subfield 1081. The value set in the Queue Size High subfield 1085 may indicate / report the queue size of the ACI indicated in the ACI High subfield 1083.

[0097]

[0098] Table 1. Control ID subfield values

[0099] WLAN protocols (e.g., 802.11be) may define TWT mechanisms, such as restricted TWT (R-TWT). In the TWT mechanism, STAs may adopt a wake-up time schedule that periodically wakes up these STAs to send / receive data. R-TWT may force all other 802.11be compatible devices to complete / terminate their transmissions before the TWT SP starts. R-TWT may be used to provide priority access and media access protection to STA's p2p services. Such a TWT mechanism (e.g., R-TWT) may require the ability to report buffer status in order to efficiently perform STA's p2p services. For example, the AP may allocate resources to STA's p2p services based on the buffer status during the R-TWT SP. During the ongoing SP, if the AP can query the status of the STA's p2p services, this will contribute to efficient operation (e.g., helping the AP to allocate resources efficiently). For example, the STA may indicate an empty buffer for p2p to the AP to indicate that the STA has completed the delivery of delay-sensitive services (LST). The TWT SP may be terminated to save power, and the AP may serve other STAs. The STA may indicate a non-empty buffer for p2p to the AP near the end of the SP to communicate that the STA still has LST. The SP may be extended to deliver the remaining buffered traffic. The AP may also query its own buffer status to facilitate the above operations.

[0100] The conventional buffer status reporting mechanism may only be able to report the buffer status of the STA's uplink traffic. The STA may not be able to report the buffer status of its p2p traffic. For example, the QoS control field in the QoS data frame and / or the QoS empty frame (see Fig. 10A ) may not indicate or report the buffer status of p2p traffic. HE variants The BSR control field in the A control subfield of the HT control field (see Fig. 10B ) may not be able to indicate or report the buffer status of p2p services. It is necessary / beneficial to define a new request method for STA to report the buffer status of p2p services to AP.

[0101] To address this issue, the QoS control field (e.g., QoS control field 1000) or the BSR control field (e.g., control information subfield 1080) may be redefined / reutilized to indicate (reporting of) the buffer status of p2p traffic. In some embodiments, the BSR control field (or other field) may be modified or redefined to indicate (reporting of) p2p traffic. According to some subfield encodings, the BSR control subfield may have an invalid combination of values. For example, according to the incremental TID encoding, setting the ACI bitmap subfield (or other subfield / bit) to 0 and setting the incremental TID subfield (or other subfield / bit) to 0 may be an invalid combination. The encoding may be modified or redefined so that when (1) the ACI bitmap subfield (or other subfield / bit) is set to 0 and (2) the incremental TID subfield (or other subfield / bit) is set to 0 or any inapplicable number (e.g., values ​​0 to 2), the combination of the value in the ACI bitmap subfield and the value in the incremental TID subfield may indicate that the buffer status reported in the 'All Queue Sizes' subfield is for the p2p traffic of the STA. In this case, the ACI High subfield (or other subfield / bit) and the Queue Size High subfield (or other subfield / bit) may be reserved. In some embodiments, the 'All Queue Sizes' subfield and the Queue Size High subfield (or other subfield / bit) may be combined into a single Queue Size subfield (e.g., a 16-bit Queue Size subfield). In this case, the ACI High subfield (or other alternative subfield / bit) may be reserved.

[0102] In some embodiments, the QoS control field (or other fields / bits) in the QoS data frame and the QoS null frame may be modified or redefined to indicate (reporting of) p2p traffic. According to some definitions of the QoS control field, when a STA sends a QoS null frame including a QoS control field whose bit 4 is set to 1, bit 7 of the QoS control field may be reserved, and bits 8 to 15 of the QoS control field may indicate a queue size. In some embodiments, the bits (or other fields / bits) of the QoS control field may be modified or redefined. For example, when bit 4 is set to 1 and bit 7 is set to 0, the queue size may be uplink (UL) traffic for the STA belonging to the TID indicated in bits 0 to 3. As a non-limiting example, when bit 4 is set to 1 and bit 7 is set to 1, the queue size may be p2p traffic for the STA, and the TID subfield (bits 0-3) and bits 5-7 may be reserved.

[0103] In some embodiments, a new BSR-p2p control field (type), such as a BSR-p2p control field (or other field / bit), may be added and defined for the A-control subfield (or other subfield) of the HE variant HT control field (or other field). A new control ID may be defined / used to indicate a BSR-p2p frame. For example, a control ID value of 7 or any other available value (e.g., 8 to 14 reserved in Table 1) may be redefined and used. See Table 2, which includes new control ID values. The format of the new control field may include a scaling factor field (e.g., 2 bits) and a queue size subfield (e.g., 8 bits). The scaling factor (SF) subfield (or other subfield / bit) may define an SF octet, and the queue size subfield (or other subfield / bit) may indicate the buffered p2p traffic in units of SF octets (e.g., according to the definition of the SF octet as shown in Table 3), which is intended for a peer STA of a STA on one or more p2p links.

[0104] Control ID value meaning Length of the control information subfield (bits) 0 Triggered Response Scheduling (TRS) 26 1 Operating Mode (OM) 12 2 HE Link Adaptation (HLA) 26 3 Buffer Status Report (BSR) 26 4 UL Power Headroom (UPH) 8 5 Bandwidth Query Report (BQR) 10 6 Command and Status (CAS) 8 7 Buffer Status Report for p2p Services (BSR-p2p) 16 8-14 Reserve 15 A category that definitely needs to be expanded (ONES) 26

[0105] Table 2. Control ID subfield values ​​(newly added control ID values)

[0106] The value in the Scale Factor subfield Scaling factor, SF (octets) 0 16 1 256 2 2048 3 32768

[0107] Table 3. Scaling Factor Subfield Coding

[0108] In one approach, the first device may include one or more processors. The one or more processors may be configured to generate a first frame, the first frame including buffer status data corresponding to wireless traffic between the first device and the second device. Each of the first device and the second device may not be an access point. The one or more processors may be configured to wirelessly send the generated first frame to an access point in a wireless local area network (WLAN) via a transceiver.

[0109] In one approach, the one or more processors may also be configured to wirelessly receive a second frame from the access point via the transceiver. The one or more processors may be configured to generate the first frame in response to the second frame.

[0110] In one approach, the wireless service may include a point-to-point (p2p) service between the first device and the second device. In some embodiments, the first frame may include a control identifier field. The one or more processors may be configured to, when generating the first frame, set the control identifier field to a value indicating a buffer status report frame.

[0111] In one approach, the first frame may include a bitmap field including a plurality of bits corresponding to a plurality of access categories. The one or more processors may be configured to, when generating the first frame, set each of the plurality of bits to a first value indicating that there is no service associated with the access category corresponding to the bit.

[0112] In one embodiment, the first frame may include a service identifier quantity field, the service identifier quantity field indicating the number of service identifiers for which buffered services exist. The one or more processors may be configured to, when generating the first frame, set the service identifier quantity field to a second value, the second value indicating that the number of service identifiers for which buffered services exist is zero.

[0113] In one embodiment, the first frame may include a quality of service (QoS) control field, the QoS control field including a first field. The one or more processors may be configured to, when generating the first frame, set the first field to a value indicating the presence of wireless point-to-point (p2p) traffic. The QoS control field includes a second field. The one or more processors may be configured to, when generating the first frame, set the second field to a value indicating a queue size of wireless traffic between the first device and the second device.

[0114] In one approach, the first frame may include a control identifier field. The one or more processors may be configured to, when generating the first frame, set the control identifier field to a value indicating a point-to-point (p2p) buffer status report frame. The first frame may include a queue size field. The one or more processors may be configured to, when generating the first frame, set the queue size field to a value indicating a queue size of wireless traffic between the first device and the second device.

[0115] The embodiments of the present disclosure have at least the following advantages and benefits. The embodiments of the present disclosure may provide a useful technique for STAs to report the buffer status of their p2p services. In some embodiments, the QoS control field (e.g., Fig. 10A QoS control field 1000 in the BSR control field (e.g., Fig. 10B The control information subfield 1080 in the STA is used to indicate (the reporting of) the buffer status of the p2p service, thereby defining a new request method for the STA to report the buffer status of the p2p service to the AP.

[0116] Fig.11An example format of a control information subfield (or BSR control subfield) 1100 of an A control subfield for reporting a buffer status of a p2p service according to an example embodiment of the present disclosure is shown. The control information field (or BSR control field) 1100 may include: an ACI bitmap subfield 1101, an incremental TID subfield 1102, an ACI high subfield 1103, a scaling factor subfield 1104, a queue size high subfield 1105, and / or an all queue size subfield 1106. In some embodiments, the BSR control subfield (or other field) 1100 may be modified or redefined to indicate (reporting of) p2p services. According to some subfield encodings, the BSR control subfield may have an invalid value combination. For example, according to the incremental TID encoding, setting the ACI bitmap subfield (or other subfield / bit) to 0 and setting the incremental TID subfield (or other subfield / bit) to 0-2 may be an invalid combination. The coding may be modified or redefined so that when (1) the ACI bitmap subfield 1101 (or other subfield / bit) is set to 0 and (2) the incremental TID subfield 1102 (or other subfield / bit) is set to 0 or any previously inapplicable number M (e.g., 0≤M≤2), the combination of the value in the ACI bitmap subfield and the value in the incremental TID subfield may indicate that the buffer status reported in the all queue size subfield 1106 is for p2p traffic of the STA. In this case, the ACI high subfield 1103 (or other subfield / bit) and the queue size high subfield 1105 (or other subfield / bit) may be reserved. For example, in response to a buffer status report request (e.g., a BSRP trigger frame) from an AP (e.g., AP 460), a receiver STA (e.g., device 470) may report the buffer status of its p2p traffic to / from a peer device (e.g., device 480) by: (1) setting both the ACI bitmap subfield 1101 and the incremental TID subfield 1102 of the frame to 0, (2) specifying a queue size for the p2p traffic in the all queue size subfield 1106 of the frame, and (3) sending the frame to the AP. In some embodiments, the all queue size subfield 1106 and the queue size high subfield 1105 (or other subfields / bits) may be combined into a single queue size subfield (e.g., a 16-bit queue size subfield). In this case, the ACI high subfield 1103 (or other alternative subfields / bits) may be reserved.

[0117] Fig.12An example QoS control field format 1200 for reporting the buffer status of p2p traffic according to an example embodiment of the present disclosure is shown. The QoS control field format 1200 may include a subfield 1201 (bits 0-3), a subfield 1202 (bit 4), a subfield 1203 (bits 5-6), a subfield 1204 (bit 7), and / or a subfield 1205 (bits 8-15). In some embodiments, the QoS control field (or other fields / bits) in the QoS data frame and the QoS null frame may be modified or redefined to indicate (the reporting of) p2p traffic. According to the QoS control field (e.g., Fig. 10A 1000), when a STA sends a QoS null frame (e.g., QoS null frame 1020) including a QoS control field (e.g., subfield 1002) having bit 4 set to 1, bit 7 of the QoS control field (e.g., subfield 1004) may be reserved, and bits 8 to 15 of the QoS control field (e.g., subfield 1005) may indicate a queue size. In some implementations, the bits of the QoS control field (or other fields / bits) may be modified or redefined. Reference Fig.12 , when subfield 1202 (bit 4) of QoS null frame 1220 is set to 1 and subfield 1204 (bit 7) of QoS null frame 1220 is set to 0, the queue size set in subfield 1205 may be UL traffic for STA belonging to the TID indicated in subfield 1201 (bits 0-3). As a non-limiting example, when subfield 1202 (bit 4) is set to 1 and subfield 1204 (bit 7) is set to 1, the queue size may be p2p traffic for STA, and TID subfield 1201 (bits 0-3) and subfield 1203 (bits 5-6) may be reserved. For example, in response to a buffer status report request (e.g., a BSRP trigger frame) from an AP (e.g., AP 460), a receiver STA (e.g., device 470) may report the buffer status of its p2p traffic to / from a peer device (e.g., device 480) by (1) setting both subfield 1202 (bit 4) and subfield 1204 (bit 7) of a QoS null frame to 1, (2) specifying a queue size for the p2p traffic in subfield 1205 (bits 8-15) of a QoS null frame, and (3) sending the QoS null frame to the AP.

[0118] Fig.13An example A control subfield format 1300 of a control field for reporting a buffer status of a p2p service according to an example embodiment of the present disclosure is shown. The A control subfield format 1300 of the HE variant HT control field may include a plurality of HE control fields 1310 (including an HE control-1 field 1310-1, an HE control-2 field 1310-2, ..., 1310-N) and a padding field 1311. Each HE control may include a control ID field 1320 and a control information field 1330. In some embodiments, a new BSR-p2p control field (type), such as a BSR-p2p control field (or other field / bit), may be added and defined for the A-control subfield (or other subfield) of the HE variant HT control field (or other field). A new control ID may be defined / used to indicate a BSR-p2p frame. For example, a control ID value of 7 or any other available value (e.g., reserved 8 to 14 in Table 1) may be redefined / specifically used. See Table 2, which includes new / specific control ID values. For a BSR-p2p response, the control ID field 1320 may be set to a new / specific value (e.g., 7) indicating the BSR-p2p (see Table 2). The control information field (or BSR control field) 1330 may include a scaling factor subfield 1331, a queue size subfield 1332, and / or a reserved subfield 1333. In some embodiments, the scaling factor subfield 1331 may be 2 bits and the queue size subfield 1332 may be 8 bits. The scaling factor (SF) subfield 1331 may define a SF octet, and the queue size subfield 1332 may indicate the buffered p2p traffic in units of SF octets (e.g., according to the definition of the SF octet as shown in Table 3) intended for a peer STA of the STA on one or more p2p links. For example, in response to a buffer status report request (e.g., a BSRP trigger frame) from an AP (e.g., AP 460), a receiver STA (e.g., device 470) may report the buffer status of its p2p traffic to / from a peer device (e.g., device 480) by (1) setting the control ID subfield 1320 of the frame to a new value indicating BSR-p2p, (2) specifying the queue size for the p2p traffic in the queue size subfield 1332 of the frame, and (3) sending the frame to the AP.

[0119] Fig.14 1 is a flow chart illustrating a process 1400 for reporting a buffer status of a p2p service according to an example embodiment of the present disclosure. In some embodiments, the process 1400 is performed by a first device (e.g., STA device 470 or 490). In some embodiments, the process 1400 is performed by other entities. In some embodiments, the process 1400 includes: Fig.14The steps shown in the figure are more steps or fewer steps, or include the steps shown in the figure. Fig.14 The steps shown are different steps.

[0120] In one approach, a first device (e.g., device 470) may generate 1402 a first frame (e.g., a frame including a control information subfield 1100, a QoS null frame including a QoS control field 1200, a frame including an A control subfield 1300 for reporting a buffer status of a p2p service), the first frame including buffer status data corresponding to wireless services (e.g., p2p services 474) between the first device (e.g., device 470) and a second device (e.g., device 480). Each of the first device and the second device may not be an access point.

[0121] In some embodiments, the first device may wirelessly receive a second frame (eg, as shown in FIG. 1 ) from an access point (eg, AP 460) via a transceiver. FIG. 5A to FIG. 8 BSRP trigger frame shown in TABLE 1). The first device may generate the first frame in response to the second frame. In some embodiments, the wireless service may include a point-to-point (p2p) service between the first device and the second device (e.g., p2p service 474). In some embodiments, the first frame may include a control identifier field (e.g., control ID subfield 1070). When generating the first frame, the first device may set the control identifier field to a value indicating a buffer status report frame (e.g., a value 3 indicating a BSR as shown in Tables 1 and 2), because the method reuses / redefines an existing A control subfield format for reporting the buffer status of UL / DL services.

[0122] In some embodiments, a first frame (e.g., a frame including a control information subfield 1100) may include a bitmap field (e.g., an ACI bitmap 1101) including a plurality of bits corresponding to a plurality of access categories. When generating the first frame, the first device may set each of the plurality of bits to a first value (e.g., 0), the first value indicating that there is no service associated with the access category corresponding to the bit. The first frame may include a service identifier quantity field (e.g., incremental TID 1102), the service identifier quantity field indicating the number of service identifiers for which buffered services exist. The first device may, when generating the first frame, set the service identifier quantity field to a second value (e.g., 0), the second value indicating that the number of service identifiers for which buffered services exist is zero.

[0123] In some embodiments, the first frame may include a quality of service (QoS) control field (e.g., QoS control field 1200), which includes a first field (e.g., subfield 1204). The first device may set the first field (e.g., subfield 1204) to a value (e.g., 1) indicating the presence of wireless point-to-point (p2p) traffic when generating the first frame. The QoS control field includes a second field (e.g., subfield 1205). The first device may set the second field (e.g., subfield 1205) to a value indicating a queue size of wireless traffic (e.g., p2p traffic 474) between the first device (e.g., device 470) and the second device (e.g., device 480) when generating the first frame.

[0124] In some embodiments, the first frame may include a control identifier field (e.g., control ID 1320). The first device may set the control identifier field to a value (e.g., value 7) indicating a point-to-point (p2p) buffer status report frame when generating the first frame (see Table 2). The first frame may include a queue size field (e.g., queue size 1332). The first device may set the queue size field to a value indicating a queue size of wireless traffic (e.g., p2p traffic 474) between the first device (e.g., device 470) and the second device (e.g., device 480) when generating the first frame.

[0125] In one approach, the first device may wirelessly transmit 1404 the generated first frame to an access point (eg, AP 460 ) in a wireless local area network (WLAN) via a transceiver of the first device.

[0126] Having now described some illustrative embodiments, it will be apparent that the foregoing, which has been presented by way of example, is illustrative and not restrictive. In particular, although many of the examples presented herein relate to specific combinations of method actions or system elements, these actions and these elements may be combined in other ways to achieve the same purpose. The actions, elements, and features discussed in conjunction with one embodiment are not intended to be excluded from similar roles or embodiments in other embodiments.

[0127] The hardware and data processing components can be implemented or executed using a general purpose single-chip processor or a general purpose multi-chip processor designed to perform the functions described herein, 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 hardware components, or any combination thereof, which are used to implement the various processes, operations, illustrative logic, logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein. A general purpose processor can be a microprocessor, or can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some embodiments, specific processes and methods can be performed by circuits dedicated 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, which are used to complete or promote 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 memory is connected to the processor via a processing circuit and includes a computer code for executing (e.g., executed by a processing circuit and / or a processor) one or more processes described herein.

[0128] The present disclosure contemplates methods, systems, and program products on any machine-readable medium for implementing various operations. The embodiments of the present disclosure may be implemented using an existing computer processor, or may be implemented by a dedicated computer processor for a suitable system that is combined for this purpose or other purposes, or may be implemented by a hard-wired system. Embodiments within the scope of the present disclosure include program products that include machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media may be any available medium that can be accessed by a general-purpose computer or a special-purpose computer or other machine with a processor. By way of example, such machine-readable media may include RAM, ROM, EPROM, EEPROM, or may include other optical disk storage, disk storage, or other magnetic storage devices, or may include any other medium that can be used to carry or store the desired program code in the form of machine-executable instructions or data structures and can be accessed by a general-purpose computer or a special-purpose computer or other machine with a processor. The above combinations are also included in the scope of machine-readable media. Machine-executable instructions, for example, include instructions and data that cause a general-purpose computer, a special-purpose computer, or a special-purpose processing machine to perform a certain function or a certain group of functions.

[0129] The words and terms used herein are for descriptive purposes and should not be considered limiting. The use of "including," "comprising," "having," "containing," "involving," "characterized by," "characterized by," and variations thereof herein is meant to encompass the items listed thereafter, their equivalents and additions, and multiple alternative embodiments consisting exclusively of the items listed thereafter. In one embodiment, the systems and methods described herein include one, various combinations of more than one, or all of the described elements, actions, or components.

[0130] Any reference to the embodiments, elements or actions of the systems and methods mentioned herein in the singular may also encompass embodiments including a plurality of these elements, and any reference to any embodiments, elements or actions herein in the plural may also encompass embodiments including only a single element. References in the singular or plural are not intended to limit the systems or methods of the present disclosure, their parts, actions or elements to singular or plural configurations. References to any actions or elements based on any information, action or element may include embodiments based at least in part on any information, action or element.

[0131] Any embodiment disclosed herein may be combined with any other embodiment or example, and references to "an embodiment," "some embodiments," or "an embodiment," etc. are not necessarily mutually exclusive and are intended to indicate that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment or example. These terms as used herein do not necessarily all refer to the same embodiment. Any embodiment may be combined, inclusively or exclusively, with any other embodiment in any manner consistent with the various aspects and embodiments disclosed herein.

[0132] Where reference signs follow technical features in the drawings, detailed description or any claims, these reference signs are included to increase the intelligibility of the drawings, detailed description and claims. Therefore, the presence or absence of a reference sign has no limiting effect on the scope of any claim element.

[0133] The systems and methods described herein may be embodied in other specific forms without departing from the features of these systems and methods. Unless otherwise expressly stated, references to "approximately," "about," "substantially," or other terms of degree include variations of + / -10% from a given measurement, unit, or range. Multiple coupling elements may be directly electrically, mechanically, or physically coupled to each other, or may be electrically, mechanically, or physically coupled through intermediate elements. Accordingly, the scope of the systems and methods described herein is indicated by the appended claims rather than the foregoing description, and modifications within the meaning and range of equivalents of the claims are intended to be encompassed therein.

[0134] The term "coupled" and variations thereof include two members being joined directly or indirectly to one another. Such joining may be constant (e.g., permanent or fixed) or movable (e.g., removable or releasable). Such joining may be achieved by two members being directly coupled to one another, two members being coupled to one another using a separate intermediate member and any additional intermediate members that are coupled to one another, or two members being coupled to one another using an intermediate member that is integrally formed as a single unified body with one of the two members. If "coupled" or variations thereof are modified by additional terms (e.g., directly coupled), the general definition of "coupled" provided above is modified by the ordinary language meaning of the additional terms (e.g., "directly coupled" means that the joining of two members does not require any separate intermediate member), thereby producing a narrower definition than the general definition of "coupled" provided above. Such coupling may be mechanical, electrical, or fluidic.

[0135] References to "or" may be interpreted as inclusive, such that any term described using "or" may mean any of the following: a single term, more than one term, and all of the terms described. References to "at least one of 'A' and 'B'" may include only 'A', only 'B', and both 'A' and 'B'. These references used in conjunction with "including" or other open-ended terms may include additional items.

[0136] Without departing substantially from the teachings and advantages of the subject matter disclosed herein, a variety of modifications to the described elements and actions may be made, such as changes in the size, dimensions, structure, shape and proportion of the various elements, parameter values, mounting arrangements, use of materials, colors, orientations. For example, an element shown as integrally formed may be composed of multiple parts or elements, the position of the elements may be reversed or otherwise changed, and the nature, quantity, or position of discrete elements may be altered or changed. Other substitutions, modifications, changes, and omissions may 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.

[0137] References to element positions herein (e.g., "top," "bottom," "above," "below") are only used to describe the orientation of the various elements in the drawings. The orientation of the various elements may vary according to other exemplary embodiments, and these variations are intended to be encompassed by the present disclosure.

Claims

1. A first device, the first device comprising: One or more processors configured to: generating a first frame including buffer status data corresponding to wireless traffic between the first device and a second device, wherein each of the first device and the second device is not an access point; and The generated first frame is wirelessly transmitted via a transceiver to an access point in a wireless local area network (WLAN).

2. The first device according to claim 1, wherein: The one or more processors are further configured to: wirelessly receiving, via the transceiver, a second frame from the access point; and The first frame is generated in response to the second frame.

3. The first device according to claim 1 or 2, wherein: The wireless service includes a peer-to-peer (p2p) service between the first device and the second device.

4. A first device according to claim 1, 2 or 3, wherein: The first frame includes a control identifier field, and The one or more processors are configured to, when generating the first frame, set the control identifier field to a value indicative of a buffer status report frame.

5. A first device according to any one of the preceding claims, wherein: The first frame includes a bitmap field including a plurality of bits corresponding to a plurality of access categories, and The one or more processors are configured to, when generating the first frame, set each bit of the plurality of bits to a first value indicating an absence of traffic associated with an access category corresponding to the bit.

6. A first device according to any one of the preceding claims, wherein: The first frame includes a service identifier number field, the service identifier number field indicating the number of service identifiers for which buffered services exist, and The one or more processors are configured to, when generating the first frame, set the number of traffic identifiers field to a second value, the second value indicating that the number of traffic identifiers for which buffered traffic exists is zero.

7. A first device according to any one of the preceding claims, wherein: The first frame includes a quality of service (QoS) control field, the QoS control field includes a first field, and The one or more processors are configured to, when generating the first frame, set the first field to a value indicating the presence of a wireless point-to-point (p2p) service; and preferably, in: The QoS control field includes a second field, and The one or more processors are configured to, when generating the first frame, set the second field to a value indicating a queue size of the wireless traffic between the first device and the second device.

8. A first device according to any one of the preceding claims, wherein: The first frame includes a control identifier field, and The one or more processors are configured to, when generating the first frame, set the control identifier field to a value indicating a point-to-point (p2p) buffer status report frame; and / or preferably, in, The first frame includes a queue size field, and The one or more processors are configured to, when generating the first frame, set the queue size field to a value indicating a queue size for the wireless traffic between the first device and the second device.

9. A method comprising: generating, by a first device, a first frame including buffer status data corresponding to wireless traffic between the first device and a second device, wherein each of the first device and the second device is not an access point; and The generated first frame is wirelessly transmitted via a transceiver of the first device to an access point in a wireless local area network (WLAN).

10. The method according to claim 9, further comprising: wirelessly receiving, via the transceiver, a second frame from the access point; as well as The first frame is generated in response to the second frame.

11. The method according to claim 9 or 10, wherein: The wireless service includes a peer-to-peer (p2p) service between the first device and the second device.

12. The method according to claim 9, 10 or 11, wherein: The first frame includes a control identifier field, and Generating the first frame includes setting the control identifier field to a value indicative of a buffer status report frame.

13. The method according to any one of claims 9 to 12, wherein: The first frame includes a bitmap field including a plurality of bits corresponding to a plurality of access categories, and Generating the first frame comprises setting each of the plurality of bits to a first value, the first value indicating that there is no service associated with the access category corresponding to the bit; and / or preferably, in: The first frame includes a service identifier number field, the service identifier number field indicating the number of service identifiers for which buffered services exist, and Generating the first frame includes setting the number of traffic identifiers field to a second value, the second value indicating that the number of traffic identifiers for which buffered traffic exists is zero.

14. A method according to any one of claims 9 to 13, wherein: The first frame includes a quality of service (QoS) control field, the QoS control field includes a first field, and Generating the first frame includes setting the first field to a value indicating the presence of wireless point-to-point (p2p) service; and preferably, in: The QoS control field includes a second field, and Generating the first frame includes setting the second field to a value indicating a queue size for the wireless traffic between the first device and the second device.

15. The method according to any one of claims 9 to 14, wherein: The first frame includes a control identifier field, and Generating the first frame comprises setting the control identifier field to a value indicating a point-to-point (p2p) buffer status report frame; and / or preferably, in, The first frame includes a queue size field, and Generating the first frame includes setting the queue size field to a value indicating a queue size for the wireless traffic between the first device and the second device.