System and method for signaling target wake-up time scheduling
By using the Target Wake-up Time (TWT) scheduling mechanism in the artificial reality communication system, the delay problem during the rendering of the head wearable display image is solved, the user experience and system efficiency are improved, and the occurrence of motion sickness is reduced.
Patent Information
- Application Number
- CN202380028582.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-12-16
- Filing Date
- 2023-03-20
- Publication Date
- 2024-11-12
AI Technical Summary
In the existing artificial reality communication system, there is a problem of delay in the image rendering process of the wearable head display, which leads to a reduction in user experience and the occurrence of motion sickness, especially the delay between user movement and image presentation in augmented reality environment. May cause jitter.
Using the Target Wake-up Time (TWT) scheduling mechanism, the wireless local area network (WLAN) access point device generates and transmits frames containing TWT scheduling information, realizes separate addressing and effective transmission of scheduling information of the receiver device, and reduces the device wake-up time and improve power efficiency.
Through the TWT scheduling mechanism, the device wake-up time is reduced, energy consumption is reduced, and media access protection is improved, resource consumption of delay-sensitive services is reduced, user experience is improved, and motion sickness and images caused by delay are avoided. Jitter problem.
Smart Images

Figure CN118947178A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to communications for rendering artificial reality, including but not limited to improving scheduling in artificial reality communications by using a separate addressing frame to announce a target wake time (TWT) schedule. Background Art
[0002] Artificial reality (e.g., virtual reality (VR), augmented reality (AR), or mixed reality (MR)) provides an immersive experience to a user. In one example, a user wearing a head wearable display (HWD) can turn the user's 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).
[0003] In one embodiment, an image of a virtual object is generated by a console that is communicatively coupled to the HWD. In one example, the HWD includes various sensors that detect the position and / or orientation of the HWD, and the HWD transmits the detected position and / or orientation of the HWD to the console via a wired connection or a wireless connection. The console can determine the user's field of view of the artificial reality space based on the detected position and / or orientation of the HWD, and generate the following image data: the image data indicates an image of the artificial reality space corresponding to the user's field of view. The console can transmit the image data to the HWD, through which the image of the artificial reality space corresponding to the user's field of view can be presented to the user. In one aspect, the process of detecting the position of the HWD and the gaze direction of the user wearing the HWD and rendering the image to the user should be performed within one frame time (e.g., less than 11 milliseconds (ms)). Any delay between the movement of the user wearing the HWD and the display of the image corresponding to the movement of the user may cause jitter, which may cause motion sickness and may reduce the user experience.
[0004] The present disclosure attempts to at least partially address any or all of the above-mentioned shortcomings and disadvantages. Summary of the invention
[0005] According to a first aspect of the present disclosure, an access point (AP) device is provided, comprising: one or more processors, the one or more processors being configured to: generate a frame including information about a target wake time (TWT) schedule; set a first subfield of the frame to an address of a receiver device that receives the frame via a wireless local area network (WLAN); and wirelessly transmit the generated frame to the receiver device via the WLAN via a transmitter.
[0006] In some embodiments, the TWT scheduling may be a restricted TWT (R-TWT) scheduling. In some embodiments, the one or more processors may be configured to: determine whether a configuration value of the device is true; and in response to the configuration value of the device being true, set the first subfield of the frame to the address of the receiver device.
[0007] In some embodiments, the one or more processors may be configured to set the second subfield of the frame to a value indicating that the frame is to transmit the TWT schedule to one or more devices.
[0008] In some embodiments, the frame may be one of a probe response frame, an association response frame, a reassociation response frame, a TWT setup frame, or a TWT information frame.
[0009] In some embodiments, the TWT schedule may include multiple TWT schedules, including a first TWT schedule and a second TWT schedule; and the one or more processors may be configured to: set the second subfield of the frame to a first value indicating that the frame is to transmit the first TWT schedule to one or more devices, and set the third subfield of the frame to a second value indicating that the frame is related to a membership negotiation in the second TWT schedule.
[0010] In some embodiments, the frame may be an action frame; and the one or more processors may be configured to set the action subfield of the action frame to a value indicating TWT scheduling information.
[0011] In some embodiments, the one or more processors may be configured to: receive, via the receiver, another action frame from a receiver device, the action subfield of the other action frame being set to the value indicating the TWT scheduling information; determine whether the request subfield of the other action frame is set to a third value indicating a request for the TWT scheduling information; and in response to the request subfield of the other action frame being set to the third value, set the request subfield of the action frame to a fourth value, the fourth value being different from the third value and indicating a response to the request for the TWT scheduling information.
[0012] In some embodiments, the one or more processors may be configured to: receive another frame from a receiver device; determine whether a fourth subfield of the other frame is set to a sixth value indicating a request for TWT scheduling information; and generate the frame in response to the fourth subfield of the other frame being set to the sixth value, such that the frame is a response frame to the other frame.
[0013] In some embodiments, the other frame may be one of a probe request frame, a TWT information frame, or a TWT setup frame.
[0014] According to a second aspect of the present disclosure, a method is provided, which includes: generating, by one or more processors of an access point (AP) device, a frame including information about a target wake time (TWT) schedule; setting, by the one or more processors of the AP device, a first subfield of the frame to an address of a receiver device that receives the frame via a wireless local area network (WLAN); and wirelessly transmitting the generated frame to the receiver device via the WLAN via a transmitter.
[0015] In some embodiments, the TWT scheduling may be a restricted TWT (R-TWT) scheduling. In some embodiments, the AP device may determine whether a configuration value of the device is true; and in response to the configuration value of the device being true, the AP device may set the first subfield of the frame to the address of the receiver device.
[0016] In some embodiments, the AP device may set the second subfield of the frame to a value indicating that the frame is to transmit the TWT schedule to one or more devices.
[0017] In some embodiments, the TWT schedule may include multiple TWT schedules, including a first TWT schedule and a second TWT schedule; and the method may also include setting a second subfield of the frame to a first value indicating that the frame is to transmit the first TWT schedule to one or more devices; and setting a third subfield of the frame to a second value indicating that the frame is related to a membership negotiation in the second TWT schedule.
[0018] In some embodiments, the frame may be one of a probe response frame, an association response frame, a reassociation response frame, a TWT setup frame, or a TWT information frame.
[0019] In some embodiments, the frame may be an action frame; and the method may further include setting an action subfield of the action frame to a value indicating TWT scheduling information.
[0020] In some embodiments, the method may also include: receiving another action frame from a receiver device via the receiver, the action subfield of the other action frame being set to the value indicating the TWT scheduling information; determining whether the request subfield of the other action frame is set to a third value indicating a request for the TWT scheduling information; and in response to the request subfield of the other action frame being set to the third value, setting the request subfield of the action frame to a fourth value, the fourth value being different from the third value and indicating a response to the request for the TWT scheduling information.
[0021] In some embodiments, the method may also include: receiving another frame from a receiver device; determining whether a fourth subfield of the other frame is set to a sixth value indicating a request for TWT scheduling information; and generating the frame in response to the fourth subfield of the other frame being set to the sixth value, so that the frame is a response frame to the other frame.
[0022] In some embodiments, the other frame may be one of a probe request frame, a TWT information frame, or a TWT setup frame.
[0023] It will be understood that any feature described herein as being suitable for incorporation into one or more aspects or embodiments of the present disclosure is intended to be generalizable to any and all aspects and embodiments of the present disclosure. Other aspects of the present disclosure may be understood by those skilled in the art based on the specification, claims and drawings of the present disclosure. The above general overview and the following detailed description are exemplary and illustrative only, and are not limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] The accompanying drawings are not intended to be drawn to scale. Like reference numbers and names in the various drawings refer to like elements. For clarity, not every component may be labeled in every drawing.
[0025] Figure 1A is a schematic diagram of a system environment including an artificial reality system according to one or more embodiments of the present disclosure.
[0026] Figure 1B is a schematic diagram of a system environment including an artificial reality system according to one or more embodiments of the present disclosure.
[0027] Figure 2 is a schematic diagram of a head wearable display according to one or more embodiments of the present disclosure.
[0028] Figure 3 is a block diagram of a computing environment according to one or more embodiments of the present disclosure.
[0029] Figure 4An example format of a target wake time (TWT) element field is shown in accordance with one or more embodiments of the present disclosure.
[0030] FIG. 5A to FIG. 5D An example format of a separately addressed frame using a TWT element field to notify / send one or more TWT schedules according to one or more embodiments of the present disclosure is shown.
[0031] Figure 6 An example format of a separately addressed frame for notifying / sending one or more TWT schedules in accordance with one or more embodiments of the present disclosure is shown.
[0032] Figure 7 An example format of a modified TWT element field according to one or more embodiments of the present disclosure is shown.
[0033] FIG. 8A to FIG. 8C An example format of a frame including a modified TWT element field for requesting TWT scheduling information according to one or more embodiments of the present disclosure is shown.
[0034] Fig. 9 is a flowchart showing the process of using a separate addressing frame to notify / send one or more TWT schedules according to one or more embodiments of the present disclosure. DETAILED DESCRIPTION
[0035] 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 the purpose of description only and should not be considered as limiting.
[0036] Traffic flows can be characterized by different types of traffic. For example, an application can be characterized by delay-sensitive traffic (e.g., video / voice (VI / VO) and real-time interactive applications, etc.) or conventional traffic (e.g., best effort / background (BE / BK) applications). In some embodiments, delay-sensitive traffic can be identified or characterized based in part on the bursty nature of the delay-sensitive traffic (e.g., periodic bursts of traffic). For example, a video display service can be driven by a refresh rate of 60Hz, 72Hz, 90Hz, or 120Hz. Applications and / or devices can have a combination of traffic types (e.g., delay-sensitive traffic and non-delay-sensitive traffic). In addition, each traffic flow of an application and / or device can be more or less spontaneous and / or non-periodic compared to other traffic flows of the application and / or device. Therefore, traffic can change dynamically based on the application and / or channel rate.
[0037] TWT can be a wake-up time agreed / negotiated by each device (e.g., each access point (AP) and / or each station (STA)), or a wake-up time specified / configured by a device (e.g., AP). During the wake-up time, the first device (e.g., STA) can be in an awake state (e.g., the wireless communication module / interface of the first device is in a fully powered-on ready state, an active state, or an awake state) and can transmit and / or receive. When the first device is not awake (e.g., the wireless communication module / interface of the first device is in a power-off state, an inactive state, a low-power state, or a sleep state), the first device can enter a low-power mode or other sleep mode. The first device can be in a sleep state until the moment / window specified by the TWT.
[0038] TWT is a mechanism in which a set of service periods (SPs) are defined and shared among devices to reduce / avoid medium contention and improve the power efficiency of the devices. For example, a first device may wake up periodically (e.g., at fixed, configured time intervals / periods / time cycles) based on TWT. The TWT method reduces the energy consumption of a device by limiting the wake-up time of the device and the associated power consumption.
[0039] An AP (e.g., an AP operating as a soft AP / hotspot and / or other device) may enhance medium access protection and resource reservation by supporting restricted TWT (R-TWT). R-TWT SP may be used to deliver delay-sensitive services and / or any additional frames supporting delay-sensitive services.
[0040] Latency-sensitive services that are not prioritized (or protected) may degrade the user experience. For example, in the context of AR, the latency between the movement of a user wearing an AR device and the images corresponding to the user's movement and displayed to the user using the AR device may cause jitter, leading to motion sickness.
[0041] Disclosed herein are systems and methods related to notifying (e.g., sharing, providing, sending, reporting) one or more TWT schedules to a receiver device using a separately addressed frame (e.g., a probe response frame, an association response frame, a reassociation response frame, a TWT setup frame, a TWT information frame). In some embodiments, an AP device may have one or more processors. The one or more processors may generate a frame including information about a TWT schedule. The one or more processors may set the first subfield of the frame to the address of a receiver device that receives the frame via a wireless local area network (WLAN) (e.g., a MAC address, an IP address, or a port of a non-AP STA). The one or more processors may wirelessly transmit the generated frame to a receiver device via a transmitter via a WLAN.
[0042] Figure 1A 1 is a block diagram of an example artificial reality system environment 100. In some embodiments, the artificial reality system environment 100 includes a HWD 150 worn by a user, and a console (or computing device) 110 that provides artificial reality content to the HWD 150. The HWD 150 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). The HWD 150 may detect the position and / or orientation of the HWD 150, and the shape, position, and / or orientation of the user's body / hand / face, and provide the detected position and / or orientation of the HWD 150, and / or tracking information indicating the shape, position, and / or orientation of the body / hand / face to the console 110. The console 110 may generate image data indicative of an artificial reality image and send the image data to the HWD 150 for presentation based on: the detected position and / or orientation of the HWD 150; the detected shape, position and / or orientation of the user's body / hand / face; and / or user input of the artificial reality. In some embodiments, the artificial reality system environment 100 includes more, fewer, or different components than those shown in FIG. 1 . In some embodiments, the functionality of one or more components of the artificial reality system environment 100 may be distributed among the components in a manner different from that described herein. For example, some of the functions of the console 110 may be performed by the HWD 150. For example, some of the functions of the HWD 150 may be performed by the console 110. In some embodiments, the console 110 is integrated as part of the HWD 150.
[0043] 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, audio is presented via an external device (e.g., a speaker and / or headphones), which receives audio information from HWD 150, console 110, or both, and presents audio based on the audio information. In some embodiments, HWD 150 includes a sensor 155, an eye tracker 160, a hand tracker 162, a communication interface 165, a processor / image renderer 170, an electronic display 175, a lens 180, and a compensator 185. These components can work in concert to detect the position of HWD 150 and the gaze direction of the user wearing HWD 150, and render an image of an artificial reality internal field of view corresponding to the detected position and / or orientation of HWD 150. In other embodiments, HWD 150 includes more, fewer, or different components than those shown in FIG. 1 .
[0044] In some embodiments, sensor 155 includes electronic components, or a combination of electronic components and software components, that detect the position and 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 motion (e.g., forward / backward, up / down, left / right), and one or more gyroscopes may measure rotational motion (e.g., pitch, yaw, roll). In some embodiments, sensor 155 detects translational motion and rotational motion and determines the orientation and position of HWD 150. In one aspect, sensor 155 may detect translational motion and rotational motion relative to a previous orientation and position of HWD 150, and determine a new orientation and / or position of HWD 150 by accumulating or integrating the detected translational motion and / or rotational motion. 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 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 a second direction.
[0045] In some embodiments, the eye tracker 160 includes an electronic component or a combination of electronic components and software components 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 for 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, translation, and torsion change of the eye. In one method, the eye tracker 160 can illuminate or project a predetermined reference pattern or structured pattern on a portion of the eye, and capture an image of the eye to analyze the pattern projected on the portion of the eye, thereby determining the relative gaze direction of the eye relative to the HWD 150. In some embodiments, eye tracker 160 determines the user's gaze direction in conjunction with the orientation of HWD 150 and the relative gaze direction relative to HWD 150. For example, assuming that HWD 150 is oriented in a direction 30 degrees from a reference direction, and the relative gaze direction of HWD 150 is -10 degrees (or 350 degrees) relative to HWD 150, eye tracker 160 may determine that the user's gaze direction is 20 degrees from the reference direction. In some embodiments, a user of HWD 150 may configure HWD 150 (e.g., via user settings) to enable or disable eye tracker 160. In some embodiments, the user of HWD 150 is prompted to enable or disable eye tracker 160.
[0046] In some embodiments, hand tracker 162 includes electronic components, or a combination of electronic components and software components, that track the user's hands. 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 the hand. Hand tracker 162 can generate hand tracking measurements that indicate the shape, position, and orientation of the detected hand.
[0047] 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. Examples of the wireless link can include a cellular communication link, a near field communication link, Wi-Fi, Bluetooth, a 60 GHz wireless link, or any wireless communication link for communication. Through the communication link, the communication interface 165 can transmit the following data to the console 110: the data indicates the determined position and / or orientation of the HWD 150, the determined gaze direction of the user, and / or hand tracking measurement results. In addition, through the communication link, the communication interface 165 can receive instructions from the console 110 or image data corresponding to the image to be rendered, as well as additional data associated with the image.
[0048] In some embodiments, the processor / 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 electronic components and software components. In some embodiments, the processor / image renderer 170 is implemented as a processor (or a graphical processing unit (GPU)) that executes instructions to perform the various functions described herein. The processor / image renderer 170 may receive image data describing an artificial reality image to be rendered and additional data associated with the image through the communication interface 165, and may render the image through the electronic display 175. In some embodiments, the image data from the console 110 may be encoded, and the processor / image renderer 170 may decode the image data to render the image. In some embodiments, the processor / image renderer 170 receives object information and depth information in the additional data from the console 110, the object information indicating a virtual object in the virtual reality space, and the depth information indicating the depth of the virtual object (or the distance from the HWD 150). In one aspect, the processor / image renderer 170 may perform shading, reprojection, and / or blending based on the artificial reality image from the console 110, object information, depth information, and / or updated sensor measurements from the sensor 155 to update the artificial reality image 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 processor / 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 reconstructing the entire image in response to the updated sensor measurements. The processor / image renderer 170 may perform shading and / or blending on the appended edges. Thus, the processor / image renderer 170 may generate an artificial reality image without reconstructing the artificial reality image based on the updated sensor measurements. In some embodiments, the processor / image renderer 170 receives hand model data indicating the shape, position, and orientation of a hand model corresponding to the user's hand and overlays the hand model on the artificial reality image. Such a hand model can be presented as visual feedback to allow the user to provide various interactions within the artificial reality.
[0049] 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 processor / image renderer 170.
[0050] In some embodiments, lens 180 is a mechanical component that changes the light received from electronic display 175. Lens 180 can magnify the light from electronic display 175 and correct the 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 changes the light from electronic display 175. Although electronic display 175 is very close to the eye, the light from electronic display 175 can still pass through lens 180 to the pupil so that the user can see the image displayed by electronic display 175.
[0051] 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 the image to be rendered from processor / image renderer 170 to compensate for the distortion caused by lens 180, and apply the determined compensation to the image from processor / image renderer 170. Compensator 185 can provide the pre-distorted image to electronic display 175.
[0052] In some embodiments, the console 110 is an electronic component, or a combination of electronic components and software components, that provides content to be rendered to the HWD 150. In one aspect, the console 110 includes a communication interface 115, one or more processors 116, a scheduler 118, and a content provider 130. These components can work together to determine an artificial reality field of view (e.g., the user's field of view (FOV)) corresponding to the position of the HWD 150 and the gaze direction of the user of the HWD 150, and can generate image data indicating an artificial reality image corresponding to the determined field of view. In addition, these components can work together to generate additional data associated with the image. The additional data can be information associated with presenting or rendering artificial reality in addition to the artificial reality image. Examples of additional data include hand model data, mapping information (or simultaneous localization and mapping (SLAM) data) for converting the position and orientation of the HWD 150 in the physical space into the virtual space, eye tracking data, motion vector information, depth information, edge information, object information, etc. The console 110 may provide image data and additional data to the HWD 150 for use in presenting artificial reality. In other embodiments, the console 110 includes more, fewer, or different components than those shown in FIG. 1 . In some embodiments, the console 110 is integrated as part of the HWD 150.
[0053] In some embodiments, the communication interface 115 is an electronic component, or a combination of an electronic component and a software component, that communicates with the HWD 150. The communication interface 115 may be a counterpart of the communication interface 165, which is used to communicate with the communication interface 115 of the console 110 via a communication link (e.g., a wireless link). Through the communication link, the communication interface 115 may receive data from the HWD 150 indicating the determined position and / or orientation of the HWD 150, the determined user gaze direction, and hand tracking measurements. In addition, through the communication link, the communication interface 115 may transmit image data describing the image to be rendered and additional data associated with the artificial reality image to the HWD 150.
[0054] In some embodiments, the processor 116 includes or is implemented as one or more central processing units, one or more graphics processing units, one or more image processors, or any processor for generating artificial reality images. In some embodiments, the processor 116 can configure or cause the communication interface 115 to toggle, convert, cycle, or switch between a sleep mode and a wake-up mode. In the wake-up mode, the processor 116 can enable the communication interface 115 so that the communication interface 115 and the communication interface 165 can exchange data. In the sleep mode, the processor 116 can disable the communication interface 115 so that the communication interfaces 115 and 165 may not consume power, or may reduce power consumption.
[0055] In some embodiments, the scheduler 118 may request the R-TWT to use point-to-point (P2P) communication to transmit delay-sensitive traffic. The details of the scheduler 118 will be described in the following sections.
[0056] 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. In some embodiments, the content provider 130 may combine the gaze direction of the user of the HWD 150 and the user interaction based on the hand tracking measurement results in the artificial reality to generate the content to be rendered. In one aspect, the content provider 130 determines the field of view of the artificial reality based on the position and / or orientation of the HWD 150. For example, the content provider 130 maps the position of the HWD 150 in the physical space to the position in the artificial reality space, and determines the field of view of the artificial reality space from the position in the mapped artificial reality space, along the direction corresponding to the mapped orientation. The content provider 130 may generate image data describing an image of the determined field of view of the artificial reality space, and transmit the image data to the HWD 150 through the communication interface 115. The content provider 130 may also generate a hand model corresponding to the hand of the user of the HWD 150 based on the hand tracking measurement results, and generate hand model data indicating the shape, position and orientation of the hand model in the artificial reality space. In some embodiments, the content provider 130 may generate additional data associated with the image (the additional data includes motion vector information, depth information, edge information, object information, hand model data, etc.), and transmit the additional data and the image data to the HWD 150 through the communication interface 115. The content provider 130 may encode the image data describing the image, and may transmit the encoded data to the HWD 150. In some embodiments, the content provider 130 periodically (e.g., every 11 ms) generates image data and provides the image data to the HWD 150. In one aspect, the communication interface 115 may adaptively transmit the additional data to the HWD 150, as described below with respect to Figures 3 to 6as described.
[0057] Figure 1B is a block diagram of an example artificial reality system environment 1000. Figure 1B An example environment 1000 is provided in which devices may transmit traffic flows with different latency sensitivities / requirements. In some embodiments, the artificial reality system environment 1000 includes an access point (AP) 105, one or more head wearable displays (HWDs) 150 worn by a user (e.g., HWD 150A, HWD 150B), and one or more consoles or computing devices 110 (computing devices 110A, 110B) that provide artificial reality content to the HWD 150. The computing devices 110A, 110B may have a plurality of Figure 1A The HWD 150A and HWD 150B may have a configuration similar to that of the computing device 110 shown in FIG. Figure 1A The access point 105 may be a router or any network device that allows one or more computing devices 110 and / or one or more HWD 150 to access a network (e.g., the Internet). The access point 105 may be replaced by any communication device (cellular base station).
[0058] In some embodiments, computing devices 110A, 110B communicate with access point 105 via communication links 102A, 102B (e.g., interconnect links), respectively. In some embodiments, computing device 110A may communicate with HWD 150A via communication link 125A (e.g., internal link), and computing device 110B may communicate with HWD 150B via wireless link 125B (e.g., internal link).
[0059] In some embodiments, the scheduler 118 (e.g., the scheduler 118A of the computing device 118A and / or the scheduler 118B of the computing device 110B) may request that R-TWT use P2P communication to transmit delay-sensitive traffic. The scheduler 118 of the AP 105 and the computing device 110 may negotiate (e.g., perform a handshake process) and may establish membership of a restricted TWT schedule. In some embodiments, when the AP 105 and the scheduler 118 negotiate, the AP 105 may be considered a restricted TWT scheduling AP and the computing device 110 may be considered a restricted TWT scheduling STA.
[0060] In some embodiments, the HWD 150 may request to send P2P traffic to the computing device 110. Thus, the HWD 150 may be considered a TWT requesting STA (e.g., a TWT STA requesting TWT consent), and the computing device 110 may be considered a TWT responding STA (e.g., a TWT STA responding to a TWT request). The communication link 125 between the computing device 110 and the HWD 150 may be a P2P link (e.g., a link for transmission between two non-AP devices). The communication link 102 between the computing device 110 and the AP 105 may be any channel or other type of link. In some configurations, the HWD 150 may move / become out of range of the access point 105. In other embodiments, the computing device 110 may request to send P2P traffic to the HWD 150, such that the computing device 110 is considered a TWT requesting STA, and the HWD 150 is a TWT responding STA.
[0061] The scheduler 118 of the computing device 110 may use the AP 105 to schedule communications between the one or more computing devices 110 and the one or more HWDs 150 such that the communications between the one or more computing devices 110 and the one or more HWDs 150 are protected. The one or more computing devices 110 may initiate such protected P2P communications with the one or more HWDs 150 by indicating to the AP 105 that the one or more computing devices 110 wish to schedule P2P communications in an R-TWT service period (SP). The scheduler 118 of the one or more computing devices may schedule (or negotiate) the requested one or more R-TWT SPs. The scheduler 118 of the one or more computing devices may also indicate whether the one or more SPs are requested only for P2P communications (as compared to hybrid P2P communications and non-P2P communications).
[0062] 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 (not shown), sensor 155, eye trackers 160A and 160B, communication interface 165 and processor / image renderer 170. Figure 2 In the illustrated embodiment, the communication interface 165, the processor / image renderer 170, and the sensor 155 are located within the front rigid body 205 and may not be visible to the user. In other embodiments, the HWD 150 has a Figure 2For example, the communication interface 165, the processor / image renderer 170, the eye tracker 160A, 160B and / or the sensor 155 may be located in a different configuration than that shown. Figure 2 The positions shown in the figure are different positions.
[0063] Various operations described herein may be implemented on a computer system. Figure 3 A block diagram of a representative computing system 314 that can be used to implement the present disclosure is shown. In some embodiments, the console 110, HWD 150, or both of FIG. 1 are implemented by a computing system 314. The computing system 314 can be implemented as, for example, 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 is implemented using a distributed computing device. The computing system 314 can be implemented to provide a VR experience, an AR experience, an 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.
[0064] The network interface 720 can provide a connection to a wide area network (e.g., the Internet) to which a wide area network (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, LTE, etc.).
[0065] User input device 722 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.), etc.
[0066] User output device 324 may include any device through which computing system 314 can provide information to a user. For example, user output device 324 may include a display that displays images generated by or transmitted 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 that are used as both input devices 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.
[0067] Some embodiments include storing computer program instructions in a plurality of electronic components, such as microprocessors, storage devices and memories, in a computer-readable storage medium (e.g., non-transient computer-readable medium). Many features in each feature described in this specification may be implemented as a process designated as a group of program instructions encoded on a computer-readable storage medium. When these program instructions are executed by one or more processors, these program instructions cause the one or more processors to perform the various operations indicated in these program instructions. Examples of program instructions or computer codes include machine code 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. Through suitable programming, processor 316 can provide various functions for computing system 314, which are included in any function described herein as being executed by a server or client, or other functions associated with a message management service.
[0068] It should be appreciated that computing system 314 is illustrative, and various variations and modifications are possible. The computer system used in conjunction with the present disclosure may have other functions not specifically described herein. In addition, although computing system 314 is described with reference to specific blocks, it should be understood that these blocks are defined for the convenience of description and are not intended to imply a specific physical arrangement of the components. For example, different blocks may be located in the same facility, in the same server rack, or on the same motherboard. In addition, these blocks do not have to correspond to physically different components. Each block can be configured to perform various operations, for example, by programming a processor or providing suitable control circuits, and each block may or may not be reconfigurable, depending on the manner in which the initial configuration is obtained. The various embodiments of the present disclosure can be implemented in various devices, including electronic devices implemented using any combination of circuits and software.
[0069] In some embodiments, a broadcast TWT schedule (including a restricted TWT (R-TWT) schedule) may be notified via a TWT element whose negotiation type subfield is set to 2. Figure 4 An example format of a TWT element field (TWT Information Element (IE)) 400 according to an example embodiment of the present disclosure is shown. The TWT IE 400 may include the following fields: element ID 411; length 412; control 413; and TWT parameter information 414 (e.g., request type, target wake-up time, nominal minimum TWT wake-up duration, TWT wake-up interval tail number, and / or broadcast TWT information). In some embodiments, the control field 413 may include the following subfields: null data packet (NDP) paging indicator 421, responder power management (PM) mode 422, negotiation type 423, deactivate TWT information frame 424, wake-up duration unit 425, existence of link ID bitmap 426, and / or reservation 427.
[0070] In some embodiments, the negotiation type subfield 423 may indicate whether the information included in the TWT element is for parameter negotiation of one or more broadcast TWTs (including R-TWT) or for parameter negotiation of one or more separate TWTs. For example, a negotiation type subfield set to a value of 2 (referred to as "negotiation type 2") may indicate that the TWT element may carry scheduling information (e.g., scheduling information of one or more schedules) of all schedules (or a portion of schedules) present in a network (e.g., WLAN). In other words, a TWT element with negotiation type 2 may notify active and / or configured schedules. Upon receiving a TWT announcement frame including a TWT element with negotiation type 2, a station (STA) (e.g., an associated STA or another AP that receives a TWT announcement frame) may learn / identify / detect the notified schedule so that: (1) the STA may request membership in the notified schedule; and / or (2) the STA may follow multiple rules. In some embodiments, one of the multiple rules is that a STA receiving a TWT notification frame may stop transmitting before the start of the notified scheduled R-TWT service period (SP) (e.g., the STA may end its transmission opportunity before the start of the R-TWT SP), thereby reducing / avoiding interference or conflicts during the R-TWT SP. For example, the AP may issue these notifications (using a TWT element with negotiation type 2) via broadcast frames (including beacon frames, broadcast probe response frames, and / or fast initial link setup (FILS) discovery frames). Such broadcast frames may be transmitted from the AP and received by all STA devices. In some embodiments, TWT scheduling information (scheduled information carried in a TWT element with negotiation type 2) may be delivered as a notification via a broadcast frame (most commonly in a periodic beacon).
[0071] In the case where the TWT scheduling information is delivered as a notification via a broadcast frame, the STA (associated STA or another AP) may be limited in requesting the latest TWT scheduling information from the AP, so the STA may wait for the next broadcast notification to receive the TWT scheduling information. For example, a STA may join a network and may miss one or more beacons because the STA may be configured to sleep / power save and may periodically skip processing beacons. There may be no available mechanism for a neighboring AP to retrieve the TWT schedule in another basic service set (BSS).
[0072] In addition, using the TWT scheduling notification mechanism via broadcast frames, the AP may have limited capabilities in delivering TWT scheduling information to specific STAs. For example, the AP may only be configured to broadcast the TWT schedule to associated STAs by notifying all STAs of the schedule, so that all STAs may consume resources to process the received frames, resulting in inefficient resource management.
[0073] In addition, in some cases, depending on the device (for example, depending on whether the device is an associated STA or a neighboring AP), the request and / or delivery of TWT scheduling information can be used for different purposes. For example, for an associated STA, if the STA may miss periodic beacons (for example, due to sleep) and may not have the latest scheduling information related to the R-TWT scheduling, the STA may not be able to end the transmission at the beginning of the R-TWT scheduled SP, thereby causing interference. On the other hand, for a neighboring AP, it may be beneficial for the neighboring AP to be able to learn / identify / detect overlapping base station subsystem (OBSS) scheduling to coordinate scheduling to avoid interference.
[0074] To address these issues and / or benefits, disclosed herein are systems, devices, and methods including for requesting and / or delivering (or notifying) TWT scheduling to individual STAs and / or APs. In some embodiments, the AP may deliver / notify / provide TWT scheduling information in a separate addressed frame (e.g., a probe response frame, an association response frame, and a reassociation response frame, a TWT setup frame, a TWT information frame, or other action frame) (e.g., targeted at a specific recipient). In some embodiments, a new action frame with a "TWT scheduling information" category or type may be defined so that the new action frame may be flexibly used for scheduling delivery and / or request of TWT scheduling information.
[0075] In one method, the AP may deliver / notify / provide TWT scheduling information to a specific device (e.g., an associated STA or a neighboring AP) in a separately addressed frame. In some embodiments, a TWT element with negotiation type 2 may be included in a separately addressed probe response frame. For example, the address of a specific device may be specified / included in a destination address (DA) field in a MAC header of a probe response frame. The specific device may be configured to support broadcast TWT.
[0076] In some embodiments, the AP (or STA) may determine whether a first set of configuration values (e.g., dot11TWTOptionActivated, dot11HEOptionImplemented, and dot11FILSOmitReplicateProbeResponses) are true. For example, if the AP / STA determines that dot11TWTOptionActivated, dot11HEOptionImplemented, and dot11FILSOmitReplicateProbeResponses are true, a TWT element may be included or present in the broadcast probe response frame. In some embodiments, if the AP / STA determines that the AP / STA supports broadcast TWT, a TWT element may be included or present in the broadcast probe response frame. Otherwise, a TWT element may not be present in the probe response frame. If a TWT element is present in the (broadcast) probe response frame, the negotiation type subfield of the TWT element may be set to 2.
[0077] In some embodiments, the AP (or STA) may determine whether a second set of configuration values (e.g., dot11TWTOptionActivated and dot11HEOptionImplemented) are true. For example, if the AP / STA determines that dot11TWTOptionActivated and dot11HEOptionImplemented are true, a TWT element may be included or present in a separately addressed probe response frame (e.g., using the DA field in the MAC header of the probe response frame). In some embodiments, if the AP / STA determines that the AP / STA supports broadcast TWT, a TWT element may be included or present in a separately addressed probe response frame (e.g., using the DA field in the MAC header of the probe response frame). Otherwise, the TWT element may not be present in the probe response frame. If a TWT element is present in the (separately addressed) probe response frame, the negotiation type subfield of the TWT element may be set to 2.
[0078] In some embodiments, the AP (or STA) may include a TWT element with negotiation type 2 in a separately addressed association response frame and / or a separately addressed reassociation response frame (e.g., using the destination address (DA) field in the MAC header of the association response frame / reassociation response frame). In some embodiments, an association response frame / reassociation response frame including a TWT element with negotiation type 3 (the negotiation type subfield is set to a value of 3) may be viewed / interpreted / decoded as a TWT setup frame. Setting the negotiation type subfield to a value of 3 may indicate a membership negotiation in a TWT schedule (e.g., a negotiation using a request frame / response frame). A TWT element with negotiation type 3 may indicate a setup frame of one or more TWT SPs (e.g., indicating information about one or more specific TWT SPs). In some embodiments, an association response frame and a reassociation response frame may indicate multiple TWT elements (e.g., a first TWT element with negotiation type 2, a second TWT element with negotiation type 3, or some combination).
[0079] In some embodiments, the association response frame and / or the reassociation response frame may indicate whether there are one or more TWT elements with a negotiation type 3. For example, given an association response frame, the AP (or STA) may determine whether a third set of configuration values (e.g., dot11TWTOptionActivated) is true. If the AP / STA determines that dot11TWTOptionActivated is true, a TWT element with a negotiation type 3 may be included or present in the association response frame. In some embodiments, if the AP / STA determines that the AP / STA supports broadcast TWT, a TWT element with a negotiation type 3 may be included or present in the association response frame. The same indication method can be applied to the reassociation response frame.
[0080] In some embodiments, the association response frame and / or the reassociation response frame may indicate whether one or more TWT elements with negotiation type 2 are present therein. For example, given an association response frame, the AP (or STA) may determine whether (1) the fourth set of configuration values (e.g., dot11TWTOptionActivated and dot11HEOptionImplemented) are true; and (2) whether the TWT requester support field in the high-efficiency (HE) capability element in the association request frame (or reassociation request frame) that leads / solicites / triggers the association response frame is set to a specific value (e.g., 1). If the AP / STA determines that (1) dot11TWTOptionActivated and dot11HEOptionImplemented are true, and (2) the TWT requester support field is set to a value of 1, a TWT element with negotiation type 2 may be included or present in the association response frame. In some embodiments, if the AP / STA determines that (1) the AP / STA supports broadcast TWT and (2) the TWT requester support field is set to a value of 1, a TWT element with a negotiation type of 2 may be included or present in the association response frame. Otherwise, the TWT element may not be present in the association response frame. The same indication method can be applied to the reassociation response frame.
[0081] In some embodiments, for a given association response frame, if the STA determines that (1) there is a TWT element with a negotiation type 3 in the association request frame (or reassociation request frame) that elicits / solicites / triggering the association response frame, but (2) there is no TWT element with a negotiation type 3 in the association response frame, then the STA may send another TWT request frame to the AP after associating with the AP. The same method may be applied to the reassociation response frame.
[0082] In some embodiments, when the AP transmits a TWT element with a negotiation type 2, the TWT setup frame (or other action frame) may include the TWT element with a negotiation type 2. The TWT setup frame may be individually addressed (for example, using the DA field in the MAC header of the TWT setup frame). In some embodiments, the TWT setup frame may include a TWT element with a negotiation type 3. Additionally or alternatively, the TWT setup frame may include a TWT element with a negotiation type 2. For example, the TWT setup frame may include a first TWT element with a negotiation type 2, a second TWT element with a negotiation type 3, or some combination. In some embodiments, the TWT setup frame may indicate / include / contain one or more TWT elements.
[0083] In some embodiments, the AP may include one or more TWT elements with negotiation type 2, so that the AP can include TWT scheduling information (e.g., the latest TWT scheduling information) at the end of the TWT setup negotiation. For example, the AP and the STA can negotiate the membership of a specific TWT schedule. Near the end of the negotiation (e.g., the AP can accept the STA as a member of the TWT schedule), the AP can indicate the latest TWT schedule to the STA using a TWT element with negotiation type 2 in the TWT setup frame. Table 1 shows an example TWT setup frame action field format. In the TWT setup frame, the unprotected S1G action field (see Table 1) can be set to a value indicating "TWT setup".
[0084] order information 1 category 2 Unprotected S1G (Sub-1GHz) Action 3 Conversation Token 4 One or more TWT elements
[0085] Table 1. Example TWT Setup Frame Action Field Format
[0086] In some embodiments, a TWT element with negotiation type 2 may be included in a TWT information frame (or other action frame). The TWT setup frame may be individually addressed (e.g., using the DA field in the MAC header of the TWT information frame). Table 2 shows an example TWT information frame action field format. In a TWT information frame, the unprotected S1G action field (see Table 2) may be set to a value indicating "TWT information".
[0087] order information 1 category 2 Unprotected S1G Action 3 TWT Information (TWT Information field) 4 TWT element (optional)
[0088] Table 2. Example TWT InfoFrame Action Field Format
[0089] In one approach, a new action frame with a category or type of "TWT Scheduling Information" may be defined so that the new action frame may be flexibly used for scheduling delivery and / or request of TWT scheduling information. The TWT Scheduling Information frame may be a new unprotected S1G action frame. Table 3 shows an example TWT Scheduling Information frame action field format.
[0090] order information 1 category 2 Unprotected S1G Action 3 Dispatch information control 4 TWT element (optional)
[0091] Table 3. Example TWT Schedule Information Frame Action Field Format
[0092] Referring to Table 3, the newly defined TWT scheduling information frame may include the following fields: category, unprotected S1G action, scheduling information control and / or TWT element. The category field may be set to a value indicating "unprotected S1G action frame". The unprotected S1G action field may be set to a value indicating "TWT scheduling information" (e.g., the next available value or any other value). The scheduling information control field may be 1 octet (1 byte) long. In some embodiments, the scheduling information control field may include the following subfields: request and / or reservation. The request subfield may be 1 bit long, indicating whether the TWT scheduling information frame is a request frame or a response frame. In some embodiments, if the request subfield is set to a first value (e.g., 0), a TWT element with negotiation type 2 may be present in the TWT scheduling information frame. For example, the AP may set the request subfield to a value of 0 to respond to / transmit a TWT element with negotiation type 2 with the latest TWT scheduling information. On the other hand, for example, the STA may set the request subfield to a second value (e.g., 1) to request TWT scheduling. If the request subfield in the scheduling information control field is set to a second value (eg, 1), a TWT element may not exist in the TWT scheduling information frame.
[0093] In one method, a STA (e.g., a STA associated with an AP or another AP) may request / elicit / solicit TWT scheduling information (e.g., the latest TWT scheduling information) from an AP. In some embodiments, a STA may request TWT scheduling information from an AP using a TWT scheduling information frame as shown in Table 3. For example, a STA (an associated STA or another AP) may request the latest TWT scheduling information from an AP by sending a TWT scheduling information frame in which the request subfield (in the scheduling information control field) is set to a second value (e.g., 1). If an AP (e.g., a TWT scheduling AP) receives a TWT scheduling information frame in which the request subfield (in the scheduling information control field) is set to a second value (e.g., 1) from a STA (a STA associated with the AP or another AP), the TWT scheduling AP may deliver / notify / provide TWT scheduling information (e.g., the latest TWT scheduling information) to the corresponding STA by sending a TWT scheduling information frame carrying a TWT element with a negotiation type 2 in which the request subfield is set to a first value (e.g., 0).
[0094] In one method, a STA (e.g., a STA associated with an AP or another AP) may request / elicit / solicit TWT scheduling information from an AP by sending a request frame including a TWT element in a modified format (referred to as a "modified TWT (M-TWT) element"). In some embodiments, in the M-TWT element, the control field may be modified to indicate a request for TWT scheduling information. In some embodiments, one or more bits of the control field may be reused / appended / modified to indicate a request for TWT scheduling information. For example, in the M-TWT element, a reserved bit in the control field (e.g., bit 7 of the control field) may be reused for the following subfield: a "TWT Scheduling Request" subfield. The TWT Scheduling Request subfield of the control field in the M-TWT element may be set to a specific value (e.g., 1) to indicate that the frame including the M-TWT element is a request frame (for TWT scheduling information). Upon receiving the request frame carrying the modified TWT element, the AP may respond to the request frame based on the request frame (e.g., based on the frame type of the request frame).
[0095] In some embodiments, an M-TWT element may be included in a probe request frame. In some embodiments, the probe request frame may indicate whether one or more M-TWT elements are present therein. For example, given a probe request frame, the AP (or STA) may determine whether the fifth set of configuration values (e.g., dot11TWTOptionActivated and dot11HEOptionImplemented) is true. For example, if the AP / STA determines that dot11TWTOptionActivated and dot11HEOptionImplemented are true, an M-TWT element may be included or present in the probe request frame. In some embodiments, when an M-TWT element is present in a probe request frame, the TWT scheduling request subfield of the control field in the M-TWT element may be set to a specific value (e.g., 1), and the M-TWT element may not include one or more TWT parameter information fields. For example, if the TWT scheduling request subfield is set to a specific value (e.g., 1) in the M-TWT element included in the probe request frame, other subfields in the control field (including the negotiation type subfield) may be reserved, and the M-TWT element may not include a TWT parameter information field. If a TWT scheduled AP receives a probe request frame with an M-TWT element, the AP may include a TWT element with a negotiation type 2 in a probe response frame for TWT scheduled delivery.
[0096] In some embodiments, an M-TWT element may be included in a TWT information frame having a format similar to that shown in Table 2. For example, the STA may set the TWT scheduling request in the included M-TWT element to a specific value (e.g., 1), and the STA may not include any TWT parameter information field in the M-TWT element. If a TWT scheduling AP receives a TWT information frame carrying an M-TWT element in which the TWT scheduling request subfield is set to a specific value (e.g., 1) from a STA, the AP may send another TWT information frame to the corresponding STA, and may include a TWT element with a negotiation type 2 for TWT scheduling delivery.
[0097] In some embodiments, an M-TWT element may be included in a TWT setup frame having a format similar to that shown in Table 1. In this way, the STA may request TWT scheduling information using the existing TWT setup frame format as shown in Table 1 (except that the M-TWT element is included). For example, the STA may set the TWT scheduling request in the included M-TWT element to a specific value (e.g., 1), and the STA may not include any TWT parameter information field in the M-TWT element. If the STA wants / intends to request TWT scheduling information (e.g., the latest TWT schedule) from the AP and / or establish membership in one or more TWT schedules, the M-TWT element may be carried in the TWT setup frame.
[0098] In some embodiments, a STA may request TWT scheduling information (e.g., the latest TWT scheduling information) using a TWT setup frame including an M-TWT element in the following two ways. First, when establishing membership in a broadcast TWT schedule, the STA may set the negotiation type subfield in the M-TWT element to a value of 3, so that the M-TWT element may include / contain at least one TWT parameter information field, and the TWT scheduling request subfield may be set to a specific value (e.g., 1). Second, when requesting TWT scheduling information separately in a TWT setup frame without requesting membership in any broadcast TWT schedule, the STA may set the TWT scheduling request subfield to a specific value (e.g., 1), so that the M-TWT element may not include / contain any TWT parameter information field, and other subfields in the control field of the M-TWT element (e.g., the negotiation type subfield) may be reserved or ignored. In some embodiments, if the STA sets the TWT scheduling request subfield (in the control field of the M-TWT element) in the TWT setup frame to a specific value (e.g., 1), the TWT scheduling request subfield may indicate to the AP that the STA is requesting the latest broadcast TWT schedule. If a TWT scheduling AP receives a first TWT setup frame from a STA that carries an M-TWT element with a TWT scheduling request subfield set to a specific value (e.g., 1), the AP may include a TWT element with a negotiation type 2 in a second TWT setup frame and may send a second TWT setup frame (for TWT scheduling transfer) as a response to the first TWT setup frame.
[0099] In one method, an access point (AP) device may have one or more processors. The one or more processors may generate a frame including information about a target wake time (TWT) schedule. The one or more processors may set a first subfield of the frame to an address of a receiver device that receives the frame via a wireless local area network (WLAN). The one or more processors may wirelessly transmit the generated frame to the receiver device via a transmitter via the WLAN.
[0100] In some embodiments, the TWT schedule may be a restricted TWT (R-TWT) schedule. In some embodiments, the one or more processors may be configured to determine whether a configuration value of the device is true. In response to the configuration value of the device being true, the one or more processors may be configured to set a first subfield of the frame to an address of a receiver device. In some embodiments, the one or more processors may be configured to set a second subfield of the frame to a value indicating that the frame is to transmit a TWT schedule to one or more devices.
[0101] In some embodiments, the frame may be one of a probe response frame, an association response frame, a reassociation response frame, a TWT setup frame, or a TWT information frame. In some embodiments, the TWT schedule may include multiple TWT schedules, the multiple TWT schedules including a first TWT schedule and a second TWT schedule. The one or more processors may be configured to set the second subfield of the frame to a first value indicating that the frame is to transmit a first TWT schedule to one or more devices, and may set the third subfield of the frame to a second value indicating that the frame is related to a membership negotiation in a second TWT schedule.
[0102] In some embodiments, the frame may be an action frame. The one or more processors may be configured to set the action subfield of the action frame to a value indicating TWT scheduling information. The one or more processors may be configured to receive another action frame from a receiver device via a receiver, the action subfield of the other action frame being set to a value indicating TWT scheduling information. The one or more processors may be configured to determine whether the request subfield of the other action frame is set to a third value indicating a request for TWT scheduling information. In response to the request subfield of the other action frame being set to a third value, the one or more processors may be configured to set the request subfield of the action frame to a fourth value, the fourth value being different from the third value and indicating a response to the request for TWT scheduling information.
[0103] In some embodiments, the one or more processors may be configured to receive another frame from a receiver device. The one or more processors may be configured to determine whether a fourth subfield of the other frame is set to a sixth value indicating a request for TWT scheduling information. In response to the fourth subfield of the other frame being set to a sixth value, the one or more processors may be configured to generate the frame so that the frame is a response frame to the other frame. The other frame may be one of a probe request frame, a TWT information frame, or a TWT setting frame.
[0104] The embodiments of the present disclosure have at least the following advantages and benefits.
[0105] First, the embodiments of the present disclosure may provide useful techniques for: (1) notifying / delivering / providing TWT scheduling information to (e.g., addressed to) a specific device (e.g., a non-AP STA or a neighboring AP) using a separate addressing frame and (2) requesting / soliciting / eliciting TWT scheduling information from an AP. With this configuration, a STA may dynamically request the latest TWT scheduling information from an AP without having to wait for the next broadcast / scheduling notification to receive the TWT scheduling information.
[0106] Second, the embodiments of the present disclosure may provide a useful technique for notifying / delivering / providing TWT scheduling information only to a subset of all STAs. With this configuration, only a desired subset of all STAs may receive TWT scheduling information, so that it is not necessary / not necessary for all STAs to consume resources to process received frames, thereby achieving more efficient resource management.
[0107] Third, the embodiments of the present disclosure may provide useful techniques for coordinating TWT scheduling to avoid interference. For example, for an associated STA, if the STA will miss a periodic beacon (e.g., due to sleep), the STA may request TWT scheduling information and may receive the latest TWT scheduling information related to R-TWT scheduling from the AP. In this way, the STA may end transmission before / during / at the start of the SP scheduled by R-TWT (scheduling itself), thereby avoiding interference. For each neighboring AP, each neighboring AP may learn / identify / detect overlapping BSS (OBSS) scheduling to coordinate the scheduling to avoid interference.
[0108] FIG. 5A to FIG. 5D Each shows an example format of an individually addressed frame using a TWT element field to notify one or more TWT schedules according to an example implementation of the present disclosure. Figure 5A An example format of a separately addressed probe response frame 500 according to an example embodiment of the present disclosure is shown. The probe response frame 500 may include an address of a specific device (e.g., a MAC address of a specific STA or neighboring AP) in a destination address field 511 of a MAC header 510 of the probe response frame. The probe response frame 500 may include a TWT element 512.
[0109] In some embodiments, the probe response frame may indicate whether a TWT element exists therein. The AP (or STA) may determine whether a first set of configuration values (e.g., dot11TWTOptionActivated, dot11HEOptionImplemented, and dot11FILSOmitReplicateProbeResponses) is true. For example, if the AP / STA determines that dot11TWTOptionActivated, dot11HEOptionImplemented, and dot11FILSOmitReplicateProbeResponses are true, a TWT element may be included or present in the broadcast probe response frame. In some embodiments, if the AP / STA determines that the AP / STA supports broadcast TWT, a TWT element may be included or present in the broadcast probe response frame. Otherwise, a TWT element may not exist in the (broadcast) probe response frame. If a TWT element exists in the (broadcast) probe response frame, the negotiation type subfield of the TWT element (e.g., the negotiation type subfield 423 of the TWT element 400) may be set to 2.
[0110] In some embodiments, the AP (or STA) may determine whether the second set of configuration values (e.g., dot11TWTOptionActivated and dot11HEOptionImplemented) is true. For example, if the AP / STA determines that dot11TWTOptionActivated and dot11HEOptionImplemented are true, a TWT element (e.g., TWT IE 512) may be included or present in a separately addressed probe response frame (e.g., probe response frame 500). The probe response frame may be separately addressed using the DA field 511 in the MAC header 510 of the probe response frame 500. In some embodiments, if the AP / STA determines that the AP / STA supports broadcast TWT, a TWT element may be included or present in a separately addressed probe response frame (e.g., using the DA field in the MAC header of the probe response frame). Otherwise, a TWT element may not be present in the probe response frame. For example, if a TWT element 512 is present in the (separately addressed) probe response frame 500, the negotiation type subfield of the TWT element 512 may be set to 2.
[0111] Figure 5BAn example format of an individually addressed association (or reassociation) response frame 520 according to an example embodiment of the present disclosure is shown. The association response frame 520 may include an address of a specific device (e.g., a MAC address of a specific STA or neighboring AP) in a destination address field 531 of a MAC header 530 of the association response frame. The association response frame 520 may include one or more TWT elements 532-1, 532-2.
[0112] In some embodiments, the AP (or STA) may include a TWT element (e.g., TWT IE 532-1) with a negotiation type 2 in a separately addressed association response frame (e.g., association response frame 520). The association response frame 520 may be separately addressed using the destination address (DA) field 531 in the MAC header 530 of the association response frame 520. In some embodiments, an association frame / reassociation frame including a TWT element (e.g., TWT IE 532-2) with a negotiation type 3 (the negotiation type subfield is set to a value of 3) may be viewed / interpreted / decoded as a TWT setup frame. Setting the negotiation type subfield to a value of 3 may indicate a membership negotiation in a TWT schedule (e.g., a negotiation using a request frame / response frame). A TWT element with a negotiation type 3 may indicate a setup frame for one or more TWT SPs (e.g., indicating information about one or more specific TWT SPs). In some embodiments, the association response frame 520 may indicate multiple TWT IEs 532-1, 532-2 such that the first TWT IE 532-1 has a negotiation type 2 and the second TWT IE 532-2 has a negotiation type 3.
[0113] In some embodiments, the association response frame and / or the reassociation response frame may indicate whether there are one or more TWT elements with a negotiation type 3 therein. For example, given an association response frame (e.g., the association response frame 520), the AP (or STA) may determine whether a third set of configuration values (e.g., dot11TWTOptionActivated) is true. If the AP / STA determines that dot11TWTOptionActivated is true, a TWT element with a negotiation type 3 (e.g., TWT IE 532-2) may be included or present in the association response frame 520. In some embodiments, if the AP / STA determines that the AP / STA supports broadcast TWT, a TWT element with a negotiation type 3 (e.g., TWT IE 532-2) may be included or present in the association response frame 520. The same indication method may be applied to the reassociation response frame.
[0114] In some embodiments, the association response frame and / or the reassociation response frame may indicate whether there are one or more TWT elements with negotiation type 2 therein. For example, given an association response frame (e.g., the association response frame 520), the AP (or STA) may determine whether (1) the fourth set of configuration values (e.g., dot11TWTOptionActivated and dot11HEOptionImplemented) are true; and (2) the TWT requester support field in the high efficiency (HE) capability element (not shown) in the association request frame (not shown) that elicits / solicites / triggers the association response frame 520 is set to a specific value (e.g., 1). If the AP / STA determines that (1) dot11TWTOptionActivated and dot11HEOptionImplemented are true, and (2) the TWT requester support field is set to a value of 1, a TWT element with negotiation type 2 (e.g., TWT IE 532-1) may be included or present within the association response frame 520. In some embodiments, if the AP / STA determines that (1) the AP / STA supports broadcast TWT and (2) the TWT requester support field is set to a value of 1, a TWT element with a negotiation type 2 (e.g., TWT IE 532-1) may be included or present in the association response frame 520. Otherwise, the TWT element may not be present in the association response frame. The same indication method can be applied to the reassociation response frame.
[0115] In some embodiments, for a given association response frame (e.g., association response frame 520), if the STA determines that (1) there is a TWT element with a negotiation type 3 in an association request frame (not shown) that elicits / solicites / triggering the association response frame, but (2) there is no TWT element with a negotiation type 3 in the association response frame, the STA may send another TWT request frame to the AP after associating with the AP. The same method may be applied to a reassociation response frame.
[0116] Figure 5C An example format of an individually addressed TWT setup frame 540 according to an example implementation of the present disclosure is shown. The TWT setup frame 540 may include an address of a specific device (e.g., a MAC address of a specific STA or neighboring AP) in a destination address field 551 of a MAC header 550 of the TWT setup frame 540. The TWT setup frame 540 may have a format similar to that shown in Table 1. For example, the TWT setup frame 540 may include the following fields: a category 552, an unprotected S1G action 554, a dialog token 556, and / or one or more TWT elements 558-1, 558-2.
[0117] In some embodiments, when a TWT element with a negotiation type 2 (e.g., a TWT IE 558-1) is sent by an AP, the TWT element with a negotiation type 2 may be included in a TWT setup frame (e.g., a TWT setup frame 540). The TWT setup frame 540 may be individually addressed using the DA field 551 in the MAC header 550 of the TWT setup frame 540. In some embodiments, the TWT setup frame may include a TWT element with a negotiation type 3 (e.g., a TWT IE 558-2). Additionally or alternatively, the TWT setup frame may include a TWT element with a negotiation type 2 (e.g., a TWT IE 558-1). For example, the TWT setup frame 540 may include a first TWT IE 558-1 with a negotiation type 2, and a second TWT IE 558-2 with a negotiation type 3. In some embodiments, the TWT setup frame may indicate / include / contain one or more TWT elements.
[0118] In some embodiments, the AP may include one or more TWT elements with negotiation type 2, so that the AP can include TWT scheduling information (e.g., the latest TWT scheduling information) at the end of the TWT setup negotiation. For example, the AP and the STA can negotiate the membership of a specific TWT schedule. Near the end of the negotiation (e.g., the AP can accept the STA as a member of the TWT schedule), the AP can use a TWT element with negotiation type 2 (e.g., TWT IE 558-1) in the TWT setup frame 540 to indicate the latest TWT schedule to the STA. Table 1 shows an example TWT setup frame action field format. In the TWT setup frame 540, the unprotected S1G action field 554 (see Table 1) can be set to a value indicating "TWT setup".
[0119] Figure 5D An example format of a separately addressed TWT information frame 560 according to an example embodiment of the present disclosure is shown. The TWT information frame 560 may include an address of a specific device (e.g., a MAC address of a specific STA or a neighboring AP) in a destination address field 571 of a MAC header 570 of the TWT information frame 560. The TWT information frame 560 may have a format similar to that shown in Table 2. For example, the TWT information frame 560 may include the following fields: a category 572, an unprotected S1G action 574, TWT information 576, and / or a TWT element 578.
[0120] In some embodiments, a TWT element (e.g., TWTIE 578) with negotiation type 2 may be included in the TWT information frame 560. The TWT setup frame 560 may be individually addressed using the DA field 571 in the MAC header 570 of the TWT information frame 560. Table 2 shows an example TWT information frame action field format. In the TWT information frame 560, the unprotected S1G action field 574 (see Table 2) may be set to a value indicating "TWT information".
[0121] Figure 6 An example format of a separately addressed frame 600 for notifying / sending / transmitting one or more TWT schedules according to another example embodiment of the present disclosure is shown. Frame 600 may be an action frame having a newly defined "TWT scheduling information frame" type. In some embodiments, a new action frame (e.g., TWT scheduling information frame 600) having a "TWT scheduling information" category or type may be defined so that the new action frame may be flexibly used for scheduling delivery and / or request for TWT scheduling information. The TWT scheduling information frame 600 may be a new unprotected S1G action frame. Table 3 shows an example TWT scheduling information frame action field format.
[0122] refer to Figure 6, the TWT scheduling information frame 600 may include / indicate / specify the address of a specific device (e.g., the MAC address of a specific STA or a neighboring AP) in the destination address field 611 of the MAC header 610 of the TWT scheduling information frame 600. The TWT scheduling information frame 600 may include the following fields: category 612, unprotected S1G action 614, scheduling information control 616, and / or TWT element 618. The scheduling information control field 616 may include the following subfields: request 620 and / or reservation 622. The category field 623 may be set to a value indicating "unprotected S1G action frame". The unprotected S1G action field 614 may be set to a value indicating "TWT scheduling information" (e.g., the next available value or any other value). The scheduling information control field 616 may be 1 octet (1 byte) long. In some embodiments, the scheduling information control field 616 may include the following subfields: request 620 and / or reservation 622. The request subfield 620 can be 1 bit long, indicating whether the TWT scheduling information frame is a request frame or a response frame. In some embodiments, if the request subfield 620 is set to a first value (e.g., 0), a TWT element with negotiation type 2 (e.g., TWT IE 618) may be present in the TWT scheduling information frame. For example, the AP may set the request subfield to a value of 0 to respond / transmit a TWT element with negotiation type 2 (e.g., TWT IE 618) with the latest TWT scheduling information. On the other hand, for example, the STA may set the request subfield 620 to a second value (e.g., 1) to request TWT scheduling information. If the request subfield 620 in the scheduling information control field 616 is set to a second value (e.g., 1), a TWT element may not be present in the TWT scheduling information frame.
[0123] In some embodiments, a STA (e.g., a STA associated with an AP or another AP) may request / elicit / solicit TWT scheduling information (e.g., the latest TWT scheduling information) from an AP. In some embodiments, a STA may request TWT scheduling information from an AP using a TWT scheduling information frame (e.g., a TWT scheduling information frame 600). For example, a STA (an associated STA or another AP) may request the latest TWT scheduling information from an AP by sending a TWT scheduling information frame 600 in which the request subfield 620 (in the scheduling information control field 616) is set to a second value (e.g., 1). If an AP (e.g., a TWT scheduling AP) receives a TWT scheduling information frame 600 in which the request subfield 620 (in the scheduling information control field) is set to a second value (e.g., 1) from a STA (a STA associated with the AP or another AP), the TWT scheduling AP may deliver / notify / provide TWT scheduling information (e.g., the latest TWT scheduling information) to the corresponding STA by sending another TWT scheduling information frame carrying a TWT element with a negotiation type 2 and the request subfield set to a first value (e.g., 0).
[0124] Figure 7 An example format of a modified TWT (M-TWT) element field (M-TWT IE) 700 according to an example embodiment of the present disclosure is shown. In some embodiments, a STA (e.g., a STA associated with an AP or another AP) may request / elicit / solicit TWT scheduling information from an AP by sending a request frame including a TWT element in a modified format (referred to as a "modified TWT element (M-TWT IE)"). The M-TWT IE 700 may include the following fields: element ID 711, length 712, control 713, and TWT parameter information 714 (e.g., request type, target wake-up time, nominal minimum TWT wake-up duration, TWT wake-up interval tail, and / or broadcast TWT information). In some embodiments, the control field 713 may include the following subfields: NDP paging indicator 721, responder PM mode 722, negotiation type 723, deactivate TWT information frame 724, wake-up duration unit 725, existence link ID bitmap 726, and / or TWT scheduling request 430. Except that the M-TWT IE 700 includes a TWT scheduling request subfield 730 instead of a reserved subfield 427 (see Figure 4 ), M-TWT IE 700 may have a format similar to that of TWT IE 400.
[0125] refer to Figure 7, in the M-TWT element 700, the control field 713 may indicate a request for TWT scheduling information. In some embodiments, one or more bits of the control field 713 may be reused / appended / modified / configured / designed to indicate a request for TWT scheduling information. For example, in the M-TWT element 700, a reserved bit in the control field (e.g., bit 7 of the control field 413 (as a reserved subfield 427)) may be reused / configured for the following subfield: a "TWT scheduling request" subfield 730. The TWT scheduling request subfield 730 of the control field 713 in the M-TWT element 700 may be set to a specific value (e.g., 1) to indicate that the frame including the M-TWT element 700 is a request frame (for TWT scheduling information). Upon receiving a request frame carrying an M-TWT IE, the AP may respond to the request frame according to the frame type of the request frame (e.g., a probe request, TWT information, or TWT setup).
[0126] FIG. 8A to FIG. 8C An example embodiment of the present disclosure includes a modified TWT element field (e.g., Figure 7 One or more example formats of a frame of the M-TWT IE) shown.
[0127] Fig. 8AAn example format of a probe request frame 800 according to an example implementation of the present disclosure is shown. The probe request frame 800 may include an M-TWT element (M-TWT IE) 802 having a TWT scheduling request subfield 803. In some embodiments, the M-TWT IE 802 may be included in the probe request frame 800. In some embodiments, the probe request frame may indicate whether one or more M-TWT elements are present therein. For example, given a probe request frame, the AP (or STA) may determine whether the fifth set of configuration values (e.g., dot11TWTOptionActivated and dot11HEOptionImplemented) is true. For example, if the AP / STA determines that dot11TWTOptionActivated and dot11HEOptionImplemented are true, an M-TWT element may be included or present in the probe request frame. In some embodiments, when the M-TWT IE 802 is present in the probe request frame 800, the TWT scheduling request subfield 803 of the control field (not shown) in the M-TWT IE 802 may be set to a specific value (e.g., 1), and the M-TWT IE 802 may not include one or more TWT parameter information fields. For example, if the TWT scheduling request subfield 803 in the M-TWT IE 802 included in the probe request frame 800 is set to a specific value (e.g., 1), other subfields in the control field (including the negotiation type subfield) may be reserved, and the M-TWT IE 802 may not include the TWT parameter information field. If a TWT scheduling AP receives a probe request frame 800 including the M-TWT IE 802 (with the TWT scheduling request subfield 803 set to 1), the AP may include the TWT scheduling request subfield 803 in the probe response frame (e.g., 1) for TWT scheduling delivery. Figure 5A The probe response frame 500) includes a TWT element with negotiation type 2.
[0128] Figure 8BAn example format of a TWT information frame 830 according to an example implementation of the present disclosure is shown. The TWT information frame 830 may have a format similar to that shown in Table 2. For example, the TWT information frame 830 may include the following fields: a category 832, an unprotected S1G action 834, TWT information 836, and / or an M-TWT element 838 having a TWT scheduling request subfield 839. For example, the STA may set the TWT scheduling request 839 in the included M-TWT IE 838 to a specific value (e.g., 1), and the STA may not include any TWT parameter information field in the M-TWT IE 838. If a TWT scheduling AP receives a TWT information frame 830 carrying an M-TWT IE 838 with a TWT scheduling request subfield 839 set to a specific value (e.g., 1) from a STA, the AP may send another TWT information frame to the corresponding STA, and include the TWT scheduling request subfield 839 in the other TWT information frame for TWT scheduling delivery (e.g., 1). Figure 5D The TWT information frame 560) includes a TWT element with negotiation type 2.
[0129] Figure 8C An example format of a TWT setup frame 850 according to an example implementation of the present disclosure is shown. The TWT setup frame 850 may have a format similar to that shown in Table 1. For example, the TWT setup frame 850 may include the following fields: a category 852, an unprotected S1G action 854, a dialog token 856, and / or an M-TWT IE 858 having a TWT scheduling request subfield 859. In some embodiments, an M-TWTIE 858 may be included in a TWT setup frame 850 having a format similar to that shown in Table 1. In this way, a STA may request TWT scheduling information using an existing TWT setup frame format as shown in Table 1 (except that one or more TWT elements are replaced by one or more M-TWT elements). For example, a STA may set a TWT scheduling request 859 in the included M-TWTIE 858 to a specific value (e.g., 1), and the STA may not include any TWT parameter information field in the M-TWT IE 858. In some embodiments, if the STA wants / intends to request TWT schedule information (e.g., the latest TWT schedule) from the AP and / or establish membership in one or more TWT schedules, the M-TWT IE 858 may be carried in the TWT setup frame 850.
[0130] In some embodiments, the STA may request TWT scheduling information (e.g., the latest TWT scheduling information) using a TWT setup frame (e.g., TWT setup frame 850) including an M-TWT element (e.g., M-TWT IE858) in the following two ways. First, when establishing membership in a broadcast TWT schedule, the STA may set the negotiation type subfield in the M-TWT IE 858 to a value of 3, so that the M-TWT IE 858 may include at least one TWT parameter information field, and set the TWT scheduling request subfield 859 to a specific value (e.g., 1). Second, when requesting TWT scheduling information alone in a TWT setup frame (e.g., TWT setup frame 850) without requesting membership in any broadcast TWT schedule, the STA may set the TWT scheduling request subfield 859 to a specific value (e.g., 1), so that the M-TWT IE 858 may not include any TWT parameter information field, and other subfields (e.g., negotiation type subfield) in the control field of the M-TWT IE 858 may be reserved or ignored. In some embodiments, if the STA sets the TWT scheduling request subfield 859 in the control field of the M-TWT IE 858 to a specific value (e.g., 1) in the TWT setup frame 850, the TWT scheduling request subfield can indicate to the AP that the STA is requesting the latest broadcast TWT schedule. If the TWT scheduling AP receives a first TWT setup frame from the STA carrying an M-TWT element with the TWT scheduling request subfield set to a specific value (e.g., 1), the AP can set the TWT scheduling request subfield to a specific value (e.g., 1) in the second TWT setup frame (e.g., Figure 5C The TWT setup frame 540 in the transmission includes a TWT element with a negotiation type 2, and sends the second TWT setup frame (for TWT scheduling delivery) as a response to the first TWT setup frame.
[0131] Fig. 9 900 is a flow chart illustrating a process for notifying / providing / transmitting one or more TWT schedules using a separately addressed frame according to an example embodiment of the present disclosure. In some embodiments, process 900 is performed by an AP device (e.g., AP 105). In some embodiments, process 900 is performed by other entities. In some embodiments, process 900 includes: Fig. 9 There may be more, fewer, or more steps than those shown in FIG. 900 . Fig. 9 The steps shown are different steps.
[0132] In one method, the AP device may generate 902 a frame including information about TWT scheduling (e.g., a probe response frame 500, a (re)association response frame 520, a TWT setup frame 540, a TWT information frame 560, a TWT scheduling information frame 600). In some embodiments, the TWT scheduling may be a restricted TWT (R-TWT) scheduling.
[0133] In one approach, the AP device may set 904 the first subfield of the frame (e.g., the destination address field 511, 531, 551, 572) to the address of a receiver device (e.g., a non-AP STA associated with the AP device or a neighboring AP) that receives the frame via the WLAN. In some embodiments, the AP device may determine whether a configuration value of the device is true (e.g., whether dot11TWTOptionActivated and dot11HEOptionImplemented are true). In response to the configuration value of the device being true, the AP device may set the first subfield of the frame to the address of the receiver device.
[0134] In some embodiments, the AP device may set the second subfield of the frame (e.g., the negotiation type 423) to a value indicating that the frame is to transmit a TWT schedule to one or more devices (e.g., negotiation type 2). In some embodiments, the TWT schedule may include multiple TWT schedules, the multiple TWT schedules including a first TWT schedule (e.g., a TWT schedule specified in the TWT IE 532-1) and a second TWT schedule (e.g., a TWT schedule specified in the TWT IE 532-2). The AP device may set the second subfield of the frame (e.g., the negotiation type subfield of the TWT IE 532-1) to a first value indicating that the frame is to transmit the first TWT schedule to one or more devices (e.g., negotiation type 2). The AP device may set the third subfield of the frame (e.g., the negotiation type subfield of the TWT IE 532-2) to a second value indicating that the frame is related to the negotiation of membership in the second TWT schedule (e.g., negotiation type 3). In some embodiments, the frame can be one of a probe response frame (e.g., probe response frame 500), an association response frame (e.g., association response frame 520), a reassociation response frame (e.g., reassociation response frame 520), a TWT setting frame (e.g., TWT setting frame 540), or a TWT information frame (e.g., TWT information frame 560).
[0135] In some embodiments, the frame may be an action frame (e.g., a TWT setup frame 540, a TWT information frame 560, or a TWT scheduling information frame 600). The AP device may set the action subfield (e.g., the unprotected S1G action subfield 614) of the action frame to a value indicating the TWT scheduling information. The AP device may receive another action frame (e.g., a request frame for TWT scheduling information) from a receiver device via a receiver of the AP device, the action subfield of the other action frame being set to a value indicating the TWT scheduling information. The AP device may determine whether the request subfield (e.g., the request subfield 620) of the other action frame is set to a third value (e.g., 1) indicating a request for TWT scheduling information. In response to the request subfield of the other action frame being set to the third value, the AP device may set the request subfield (e.g., the request subfield 620) of the action frame (e.g., a response frame in response to the request frame for the TWT scheduling information) to a fourth value (e.g., 0), which is different from the third value and indicates a response to the request for the TWT scheduling information.
[0136] In some embodiments, the AP device may receive another frame (e.g., a probe request frame 800, a TWT information frame 830, a TWT setup frame 850) from a receiver device. The AP device may determine whether the fourth subfield (e.g., the TWT scheduling request subfield 730, 803, 839, 858) of the other frame is set to a sixth value (e.g., 1) indicating a request for TWT scheduling information. In response to the fourth subfield of the other frame being set to the sixth value, the AP device may generate the frame so that the frame is a response frame to the other frame. For example, the AP may generate a probe response frame (e.g., a probe response frame 500) in response to a probe request frame (e.g., a probe request frame 800). The AP may generate a response TWT information frame (e.g., a TWT information frame 560) in response to a request TWT information frame (e.g., a TWT information frame 830). The AP may generate a response TWT setup frame (e.g., a TWT setup frame 540) in response to a request TWT setup frame (e.g., a TWT setup frame 850). The other frame may be one of a probe request frame (eg, the probe request frame 800), a TWT information frame (eg, the TWT information frame 830), or a TWT setting frame (eg, the TWT setting frame 850).
[0137] In one approach, the AP device may wirelessly transmit the generated frames via a transmitter over a WLAN to a receiver device.
[0138] Now that some illustrative embodiments have been described, it is apparent that the foregoing, which has been presented by way of example, is illustrative and not restrictive. Specifically, 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 other embodiments or similar roles in the embodiments.
[0139] The hardware and data processing components for implementing the various processes, operations, illustrative logic, logic blocks, modules and circuits described in conjunction with the embodiments disclosed herein can be implemented or executed using the following components designed to perform the functions described herein: a general-purpose single-chip processor or a general-purpose multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. In some embodiments, specific processes and methods can be performed by circuits for given functions. The memory (e.g., memory, storage unit, storage device, etc.) may include one or more devices (e.g., random access memory (RAM), read-only memory (ROM), flash memory, hard disk storage, etc.) for storing data and / or computer code, which is used to complete or facilitate 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 communicatively connected to the processor via a processing circuit and includes computer code for executing (e.g., by a processing circuit and / or a processor) one or more processes described herein.
[0140] The present disclosure contemplates various methods, systems, and program products on any machine-readable medium for implementing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or may be implemented by a dedicated computer processor for a suitable system combined for this purpose and other purposes, or may be implemented by a hard-wired system. The embodiments within the scope of the present disclosure include program products, which 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 machines with a processor. As an example, such machine-readable media may include RAM, ROM, erasable programmable read-only memory (EPROM), electronic erasable read-only memory (EEPROM), or may include other optical disk storage, magnetic disk storage, or other magnetic storage devices, or may include any other medium as follows: the other medium may be used to carry or store the desired program code in the form of machine-executable instructions or data structures, and may be accessed by a general-purpose computer or a special-purpose computer, or other machines with a processor. The above combinations are also included in the scope of machine-readable media. Machine-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
[0141] 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 include the items listed thereafter, equivalents of those items, and additional items, as well as alternative embodiments consisting exclusively of the items listed thereafter. In one embodiment, the systems and methods described herein consist of one of the described elements, actions, or components, of various combinations of more than one of the described elements, actions, or components, or of all of the described elements, actions, or components.
[0142] Any reference to an embodiment or element or action of the system and method mentioned herein in the singular may also encompass an embodiment including a plurality of these elements, and reference to any embodiment or element or action herein in the plural may also encompass an embodiment including only a single element. Reference in the singular or plural form is not intended to limit the system or method of the present disclosure, their parts, actions or elements to a singular configuration or a plural configuration. Reference to any action or element based on any information, action or element may include that the action or element is based at least in part on an embodiment of any information, action or element.
[0143] 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, but 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.
[0144] Where technical features in the drawings, detailed description or any claims are followed by reference numerals, these reference numerals have been included to increase the intelligibility of the drawings, detailed description and claims. Therefore, the presence or absence of these reference numerals has no limiting effect on the scope of any claim element.
[0145] Without departing from the features of the present invention, the systems and methods described herein may be implemented in other specific forms. Unless otherwise expressly noted, reference to "approximately," "about," "substantially," or other degree terms includes a change of plus or minus 10% (+ / -10%) from a given measurement, unit, or range. The coupled elements may be electrically coupled, mechanically coupled, or physically coupled to each other directly or through intermediate elements. Therefore, the scope of the systems and methods described herein is indicated by the appended claims rather than the preceding description, and changes within the meaning and scope of the equivalents of the claims are included therein.
[0146] The term "coupled" and variations thereof include two members being directly or indirectly connected to one another. Such connection may be static (e.g., permanent or fixed) or movable (e.g., removable or releasable). Such connection may be achieved by the two members being directly coupled to one another or coupled to one another, by the two members being coupled to one another using a separate intermediate member, and by any additional intermediate member being coupled to one another, or by the two members being coupled to one another using an intermediate member that is integrally formed as a single, unitary 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 plain language meaning of the additional terms (e.g., "directly coupled" means that the two members are connected without any separate intermediate member), resulting in a narrower definition than the general definition of "coupled" provided above. Such coupling may be mechanical, electrical, or fluidic.
[0147] References to "or" may be interpreted as inclusive, such that any term described using "or" may mean all of the described terms singly, more than one, and all of the described terms. References to "at least one of 'A' and 'B'" may include only 'A', only 'B', and both 'A' and 'B'. Such references used in conjunction with "including" or other public terms may include additional items.
[0148] Without departing substantially from the teachings and advantages of the subject matter disclosed herein, modifications may be made to the elements and actions described, such as changes in the size, dimensions, structure, shape and proportion of the various elements, parameter values, mounting arrangement structures, use of materials, colors, orientations. For example, an element shown as being integrally formed may be composed of multiple parts or elements, the positions of these elements may be reversed or otherwise changed, and the nature or number or position of discrete elements may be altered or varied. Other substitutions, modifications, changes and omissions may also be made to the design, operating conditions and arrangements of the disclosed elements and operations without departing from the scope of the present disclosure.
[0149] References herein to the positions of elements (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 be different according to other example embodiments, and these variations are intended to be covered by the present disclosure.
Claims
1. An access point (AP) device, comprising: One or more processors configured to: generating a frame including information about a target wake time (TWT) schedule; setting a first subfield of the frame to an address of a receiver device receiving the frame over a wireless local area network (WLAN); as well as The generated frame is wirelessly transmitted via a transmitter to the receiver device over the WLAN.
2. The AP device according to claim 1, wherein: The TWT scheduling is restricted TWT (R-TWT) scheduling.
3. The AP device according to claim 1 or 2, wherein: The one or more processors are configured to: determining whether a configuration value of the device is true; and Responsive to the configuration value of the device being true, the first subfield of the frame is set to the address of the receiver device.
4. The AP device according to any one of the preceding claims, wherein: The one or more processors are configured to set the second subfield of the frame to a value indicating that the frame is to transmit the TWT schedule to one or more devices.
5. The AP device according to any one of claims 1 to 3, wherein: The TWT schedule includes a plurality of TWT schedules, the plurality of TWT schedules include a first TWT schedule and a second TWT schedule, and The one or more processors are configured to set a second subfield of the frame to a first value indicating that the frame is to transmit the first TWT schedule to one or more devices, and set a third subfield of the frame to a second value indicating that the frame is related to a membership negotiation in the second TWT schedule.
6. The AP device according to any one of the preceding claims, wherein: The frame is one of a probe response frame, an association response frame, a reassociation response frame, a TWT setup frame, or a TWT information frame.
7. The AP device according to any one of claims 1 to 5, wherein: The frame is an action frame, and The one or more processors are configured to set an action subfield of the action frame to a value indicating TWT scheduling information; And preferably, wherein the one or more processors are configured to: receiving, via a receiver, another action frame from the receiver device, the action subfield of the other action frame being set to the value indicating the TWT scheduling information; determining whether a request subfield of the other action frame is set to a third value indicating a request for the TWT scheduling information; and In response to the request subfield of the other action frame being set to the third value, the request subfield of the action frame is set to a fourth value, the fourth value being different from the third value and indicating a response to the request for the TWT scheduling information.
8. The AP device according to any one of the preceding claims, wherein: The one or more processors are configured to: receiving another frame from the receiver device; determining whether a fourth subfield of the another frame is set to a sixth value indicating a request for TWT scheduling information; as well as generating the frame in response to the fourth subfield of the other frame being set to the sixth value, such that the frame is a response frame to the other frame; And preferably, the other frame is one of a probe request frame, a TWT information frame or a TWT setting frame.
9. A method comprising: generating, by one or more processors of an access point (AP) device, a frame including information regarding a target wake time (TWT) schedule; setting, by the one or more processors of the AP device, a first subfield of the frame to an address of a receiver device receiving the frame over a wireless local area network (WLAN); as well as The generated frame is wirelessly transmitted via a transmitter to the receiver device over the WLAN.
10. The method according to claim 9, wherein: The TWT scheduling is restricted TWT (R-TWT) scheduling.
11. The method according to claim 9 or 10, further comprising: determining whether a configuration value of the device is true; as well as Responsive to the configuration value of the device being true, the first subfield of the frame is set to the address of the receiver device.
12. The method according to any one of claims 9 to 11, further comprising: The second subfield of the frame is set to a value indicating that the frame is to transmit the TWT schedule to one or more devices.
13. The method according to any one of claims 9 to 11, wherein: The TWT schedule includes a plurality of TWT schedules, the plurality of TWT schedules include a first TWT schedule and a second TWT schedule, and The method further comprises: setting a second subfield of the frame to a first value indicating that the frame is to transmit the first TWT schedule to one or more devices, and The third subfield of the frame is set to a second value indicating that the frame is related to membership negotiation in the second TWT schedule.
14. The method according to any one of claims 9 to 13, wherein: The frame is one of a probe response frame, an association response frame, a reassociation response frame, a TWT setup frame, or a TWT information frame.
15. The method according to any one of claims 9 to 13, wherein: The frame is an action frame, and The method further comprises: setting the action subfield of the action frame to a value indicating TWT scheduling information; And preferably, the method further comprises: receiving, via a receiver, another action frame from the receiver device, the action subfield of the other action frame being set to the value indicating the TWT scheduling information; determining whether a request subfield of the other action frame is set to a third value indicating a request for the TWT scheduling information; and In response to the request subfield of the other action frame being set to the third value, the request subfield of the action frame is set to a fourth value, the fourth value being different from the third value and indicating a response to the request for the TWT scheduling information.
16. The method according to any one of claims 9 to 15, further comprising: receiving another frame from the receiver device; determining whether a fourth subfield of the another frame is set to a sixth value indicating a request for TWT scheduling information; as well as generating the frame in response to the fourth subfield of the other frame being set to the sixth value, such that the frame is a response frame to the other frame; And preferably, the other frame is one of a probe request frame, a TWT information frame or a TWT setting frame.
Citation Information
Cited By
Communication method, communication device, and communication system
WO2026129211A1
