Systems and methods with target wake time schedules based on NOA schedules

Abstract

A first device may include one or more processors configured to receive a NoA schedule of a second device as a group owner (GO) of a P2P group, generate a target wake time (TWT) schedule corresponding to the NoA schedule, the TWT schedule defining one or more service periods (SPs) during which the second device is available, and transmit, over a wireless network, one or more frames according to the TWT schedule. The NoA schedule and the TWT schedule have the same one or more activity periods or the same one or more non-activity periods.

Description

[0001] SYSTEMS AND METHODS WITH TARGET WAKE TIME SCHEDULES

[0002] BASED ON NOA SCHEDULES

[0003] CROSS-REFERENCE TO RELATED APPLICATION

[0004] This application claims priority to U.S. Provisional Patent Application No. 63 / 684,292 filed on August 16, 2024.

[0005] FIELD OF DISCLOSURE

[0006] The present disclosure is generally related to communications, including but not limited to, systems and methods with target wake time schedules based on notice of absence schedules.

[0007] BACKGROUND

[0008] Artificial reality, such as a virtual reality (VR), an augmented reality (AR), or a mixed reality (MR), provides immersive experience to a user. In one example, a user wearing a head wearable display (HWD) can turn the user’s head to one side, and an image of a virtual object corresponding to a location and / or an orientation of the HWD and a gaze direction of the user can be displayed on the HWD to allow the user to feel as if the user is moving within a space of an artificial reality (e.g., a VR space, an AR space, or a MR space). An image of a virtual object may be generated by a computing device communicatively coupled to the HWD. In some embodiments, the computing device may have access to a network.

[0009] SUMMARY

[0010] According to a first aspect of the present disclosure there is provided a first device comprising one or more processors configured to: receive a Notice of Absence (NoA) schedule of a second device as a group owner (GO) of a peer-to-peer (P2P) group; generate a target w ake time (TWT) schedule corresponding to the NoA schedule, the TWT schedule defining one or more service periods (SPs) during which the second device is available, wherein the NoA schedule and the TWT schedule have the same one or more activity periods or the same one or more non-activity periods; and transmit, over a wireless network, one or more frames according to the TWT schedule.

[0011] In some embodiments, the NoA schedule may include one or more absence periods during which the second device is not available, and the one or more SPs may not overlap with the one or more absence periods.

[0012] In some embodiments, each of the one or more SPs may start after a corresponding absence period of the one or more absence periods ends, and may end before an absence period next to the corresponding absence period starts.

[0013] In some embodiments, the TWT may be a broadcast TWT, the TWT may include fields of TWT ID, responder power management (PM) mode, and unavailability mode, and the one or more processors may be further configured to set the fields of TWT ID, responder PM mode, and unavailability mode to values of 0, 1, 1, respectively.

[0014] In some embodiments, the NoA schedule may include a field of count indicating the number of the one or more absence periods, the TWT schedule may include a field of persistence, and the one or more processors may be configured to set the persistence field to a value corresponding to a value of the count field such that the TWT schedule ends when the one or more absence periods end.

[0015] According to a second aspect of the present disclosure there is provided a first device comprising one or more processors configured to: identify a Notice of Absence (NoA) schedule of the first device for a first peer-to-peer (P2P) group; generate a first frame including information of a first target wake time (TWT) schedule corresponding to the NoA schedule, the first TWT schedule defining one or more service periods (SPs) during which the first device is available, wherein the NoA schedule and the first TWT schedule have the same one or more activity periods or the same one or more non-activity periods; and transmit, over a wireless network, the first frame to advertise the first P2P group.

[0016] In some embodiments, the one or more processors may be configured to: receive, from a second device, a request frame requesting to join the first TWT schedule; and in response to the request frame, include the second device in the first P2P group.

[0017] In some embodiments, the first P2P group may operate in a P2P connection compatibility (PCC) mode, and the second device does not support the PCC mode.

[0018] In some embodiments, the first TWT schedule may be transmitted using out-of-band signaling.

[0019] In some embodiments, the one or more processors may be configured to: generate a second frame including information of a second target wake time (TWT) schedule corresponding to the NoA schedule, the second TWT schedule defining one or more service periods (SPs) during which the first device is available; and transmit, over the wireless network, the second frame to advertise a second P2P group that is different from the first P2P group.

[0020] In some embodiments, the one or more processors may be configured to: concurrently manage the first P2P group and the second P2P group.

[0021] In some embodiments, the second P2P group may not support a P2P connection compatibility (PCC) mode.

[0022] In some embodiments, each of the first TWT and the second TWT may be a broadcast TWT.

[0023] According to a third aspect of the present disclosure there is provided a method comprising identifying, by one or more processors of a first device, a Notice of Absence (NoA) schedule of the first device for a first peer-to-peer (P2P) group; generating, by the one or more processors, a first frame including information of a first target wake time (TWT) schedule corresponding to the NoA schedule, the first TWT schedule defining one or more service periods (SPs) during which the first device is available, wherein the NoA schedule and the first TWT schedule have the same one or more activity periods or the same one or more non-activity periods; and transmitting, by the one or more processors, over a wireless network, the first frame to advertise the first P2P group.

[0024] In some embodiments, the method may further comprise: receiving, from a second device, a request frame requesting to join the first TWT schedule; and in response to the request frame, including the second device in the first P2P group.

[0025] In some embodiments, the first P2P group may operate in a P2P connection compatibility (PCC) mode, and the second device may not support the PCC mode.

[0026] In some embodiments, the first TWT schedule may be transmitted using out-of-band signaling.

[0027] In some embodiments, the method may further comprise: generating a second frame including information of a second target wake time (TWT) schedule corresponding to the NoA schedule, the second TWT schedule may define one or more service periods (SPs) during which the first device is available; and transmitting, over the wireless network, the second frame to advertise a second P2P group that is different from the first P2P group.

[0028] In some embodiments, the method may further comprise: concurrently managing the first P2P group and the second P2P group.

[0029] In some embodiments, the second P2P group may not support a P2P connection compatibility (PCC) mode.

[0030] Various embodiments disclosed herein are related to a method. The method may include receiving, by one or more processors, a Notice of Absence (NoA) schedule of a second device as a group owner (GO) of a peer-to-peer (P2P) group. The method may include generating, by the one or more processors, a target wake time (TWT) schedule corresponding to the NoA schedule, the TWT schedule defining one or more service periods (SPs) during which the second device is available. The method may include transmitting, by the one or more processors, over a wireless network, one or more frames according to the TWT schedule. It will be appreciated that any features described herein as being suitable for incorporation into one or more aspects or embodiments of the present disclosure are intended to be generalizable across any and all aspects and embodiments of the present disclosure. Other aspects of the present disclosure can be understood by those skilled in the art in light of the description, the claims, and the drawings of the present disclosure. The foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the claims.

[0031] BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The accompanying drawings are not intended to be drawn to scale. Like reference numbers and designations in the various drawings indicate like elements. For purposes of clarity, not every component can be labeled in even’ drawing.

[0033] FIG. 1 is a diagram of a system environment including an artificial reality system, according to one or more example implementations of the present disclosure.

[0034] FIG. 2 is a diagram of a head w earable display , according to one or more example implementations of the present disclosure.

[0035] FIG. 3 is a block diagram of a computing environment according to one or more example implementations of the present disclosure.

[0036] FIG. 4 is a timing diagram showing a wake-up / sleep schedule of a computing device utilizing TWT, according to one or more example implementations of the present disclosure.

[0037] FIG. 5 is an example system environment in which a Wi-Fi Direct Revision 2 device is unable to determine availability of a group owner (GO), one or more example implementations of the present disclosure.

[0038] FIG. 6 is an example system environment including group owner (GO) and group client (GC) devices, according to one or more example implementations of the present disclosure.

[0039] FIG. 7 is an example timing diagram showing a NoA schedule and an equivalent TWT schedule, according to one or more example implementations of the present disclosure.

[0040] FIG. 8 is an example system environment in which GC and / or GO devices maintain interoperability between an infrastructure network and a P2P group, according to one or more example implementations of the present disclosure.

[0041] FIG. 9 is a flow chart showing a process for TWT schedules based on NoA schedules, according to one or more example implementations of the present disclosure.

[0042] FIG. 10 is a flowchart showing a process for TWT schedules based on NoA schedules, according to one or more example implementations of the present disclosure. DETAILED DESCRIPTION

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

[0044] Streams of traffic may be characterized by different types of traffic. For instance, an application may be characterized by latency sensitive traffic (e.g., video / voice (VI / VO). real time interactive applications, and the like) or regular traffic (e.g., best effort / background applications (BE / BK)). Latency sensitive traffic may be identifiable, in part, based on its bursty nature (e.g.. periodic bursts of traffic), in some embodiments. For instance, video display traffic may be driven by a refresh rate of 60Hz, 72Hz, 90Hz, or 120Hz. An application and / or device may have combinations of traffic types (e.g., latency sensitive traffic and non-latency sensitive traffic). Further, each stream of traffic for the application and / or device may be more or less spontaneous and / or aperiodic as compared to the other streams of traffic for the application and / or device. Accordingly, traffic may vary according to applications and / or channel rate dynamics.

[0045] TWT can be a time agreed / negotiated upon by devices (e.g., access points (APs) and / or stations (STAs)), or specified / configured by one device (e.g., an AP). During the wake time, a first device (e.g., a STA) may be in an awake state (e.g.. its wireless communication module / interface is in a fully powered-up ready, or wake state) and is able to transmit and / or receive. When the first device is not awake (e.g., its wireless communication module / interface is in a powered-down, low power, or sleep state), the first device may enter a low power mode or other sleep mode. The first device may exist in the sleep state until a time instance / window as specified by the TWT.

[0046] TWT is a mechanism where a set of service periods (SPs) are defined and shared between devices to reduce medium contention and improve the power efficiency of the devices. For example, the first device can wake up periodically (e.g., at a fixed, configured time interval / period / cycle) based on the TWT. The TWT reduces energy consumption of the devices by limiting the awake time and associated power consumption of the devices.

[0047] An AP (e.g., AP and / or other device operating as a soft AP / hotspot) may enhance medium access protection and resource reservation by supporting restricted TWT (R-TWT). The R-TWT SPs may be used to deliver latency sensitive traffic and / or any additional frame that supports latency sensitive traffic. Latency sensitive traffic that is not prioritized (or protected) may degrade a user experience. For example, in an AR context, latency between a movement of a user wearing an AR device and an image corresponding to the user movement and displayed to the user using the AR device may cause judder, resulting in motion sickness.

[0048] In one implementation, an image of a virtual object is generated by a remote computing device communicatively coupled to the HWD. and the image is rendered by the HWD to conserve computational resources and / or achieve bandwidth efficiency. In one example, the HWD includes various sensors that detect a location and / or orientation of the HWD and a gaze direction of the user wearing the HWD, and transmits sensor measurements indicating the detected location and gaze direction to a console device (and / or a remote server, e.g., in the cloud) through a wired connection or a wireless connection. The console device can determine a user’s view of the space of the artificial reality according to the sensor measurements, and generate an image of the space of the artificial reality corresponding to the user’s view. The console device can transmit the generated image to the HWD, by which the image of the space of the artificial reality corresponding to the user’s view can be presented to the user. In one aspect, the process of detecting the location of the HWD and the gaze direction of the user wearing the HWD, and rendering the image to the user should be performed within a frame time (e.g., less than 11 ms). Any latency between a movement of the user wearing the HWD and an image displayed corresponding to the user movement can cause judder, which may result in motion sickness and can degrade the user experience.

[0049] FIG. 1 is a block diagram of an example artificial reality' system environment. FIG. 1 provides an example environment in which devices may communicate traffic streams with different latency sensitivities / requirements. In some embodiments, the artificial reality system environment 100 includes an access point (AP) 105, one or more head wearable displays (HWD) 150 (e.g., HWD 150A, 150B) worn by a user, and one or more computing devices 110 (computing devices 110A, 110B) providing content of artificial reality to the HWDs 150.

[0050] The access point 105 may be a router or any network device allowing one or more computing devices 110 and / or one or more HWDs 150 to access a network (e.g., the Internet). The access point 105 may be replaced by any communication device (cell site). A HWD may be referred to as, include, or be part of a head mounted display (HMD), head mounted device (HMD), head wearable device (HWD), head worn display (HWD) or head worn device (HWD). In one aspect, the HWD 150 may include various sensors to detect a location, an orientation, and / or a gaze direction of the user wearing the HWD 150, and provide the detected location, orientation and / or gaze direction to the computing device 110 through a wired or wireless connection. The HWD 150 may also identify objects (e.g., body, hand face).

[0051] In some embodiments, the computing devices 110A, 11 OB communicate with the access point 105 through communication links 102A, 102B (e.g., interlinks), respectively. In some embodiments, the computing device 110A may communicate with the HWD 150A through a communication link 125A (e.g., intralink), and the computing device HOB may communicate with the HWD 150B through a wireless link 125B (e.g., intralink).

[0052] The computing device 110 may be a computing device or a mobile device that can retrieve content from the access point 105, and can provide image data of artificial reality to a corresponding HWD 150. Each HWD 150 may present the image of the artificial reality to a user according to the image data.

[0053] The computing device 110 may determine a view within the space of the artificial reality corresponding to the detected location, orientation and / or the gaze direction, and generate an image depicting the determined view detected by the HWD 150s. The computing device 110 may also receive one or more user inputs and modify the image according to the user inputs. The computing device 110 may provide the image to the HWD 150 for rendering. The image of the space of the artificial reality corresponding to the user’s view can be presented to the user.

[0054] In some embodiments, the artificial reality system environment 100 includes more, fewer, or different components than shown in FIG. 1. In some embodiments, functionality of one or more components of the artificial reality system environment 100 can be distributed among the components in a different manner than is described here. For example, some of the functionality of the computing device 110 may be performed by the HWD 150, and / or some of the functionality of the HWD 150 may be performed by the computing device 110. In some embodiments, the computing device 1 10 is integrated as part of the HWD 150.

[0055] In some embodiments, the 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. The HWD 150 may render one or more images, video, audio, or some combination thereof to provide the artificial reality experience to the user. In some embodiments, audio is presented via an external device (e g., speakers and / or headphones) that receives audio information from the HWD 150, the computing device 110, or both, and presents audio based on the audio information. In some embodiments, the HWD 150 includes sensors 155 (e.g., sensors 155A, 155B) including eye trackers and hand trackers for instance, a communication interface 165 (e.g., communication interface 165 A, 165B), an electronic display 175, and a processor 170 (e.g., processor 170A, 170B). These components may operate together to detect a location of the HWD 150 and / or a gaze direction of the user wearing the HWD 150, and render an image of a view within the artificial reality corresponding to the detected location of the HWD 150 and / or the gaze direction of the user. In other embodiments, the HWD 150 includes more, fewer, or different components than shown in FIG. 1.

[0056] In some embodiments, the sensors 155 include electronic components or a combination of electronic components and software components that detect a location and / or an orientation of the HWD 150. Examples of sensors 155 can include: one or more imaging sensors, one or more accelerometers, one or more gyroscopes, one or more magnetometers, hand trackers, eye trackers, or another suitable type of sensor that detects motion and / or location. For example, one or more accelerometers can measure translational movement (e.g., forward / back, up / down, left / right) and one or more gyroscopes can measure rotational movement (e.g., pitch, yaw, roll). In some embodiments, the sensors 155 detect the translational movement and / or the rotational movement, and determine an orientation and location of the HWD 150. In one aspect, the sensors 155 can detect the translational movement and / or the rotational movement with respect to a previous orientation and location of the HWD 150, and determine anew orientation and / or location of the HWD 150 by accumulating or integrating the detected translational movement and / or the rotational movement. Assuming for an example that the HWD 150 is oriented in a direction 25 degrees from a reference direction, in response to detecting that the HWD 150 has rotated 20 degrees, the sensors 155 may determine that the HWD 150 now faces or is oriented in a direction 45 degrees from the reference direction. Assuming for another example that the HWD 150 was located two feet away from a reference point in a first direction, in response to detecting that the HWD 150 has moved three feet in a second direction, the sensors 155 may determine that the HWD 150 is now located at a vector multiplication of the two feet in the first direction and the three feet in the second direction.

[0057] In some embodiments, the sensors 155 may also include eye trackers with electronic components or a combination of electronic components and software components that determine a gaze direction of the user of the HWD 150. In other embodiments, the eye trackers may be a component separate from sensors 155. In some embodiments, the HWD 150, the computing device 110 or a combination may incorporate the gaze direction of the user of the HWD 150 to generate image data for artificial reality'. In some embodiments, the eye trackers (as part of the sensors 155, for instance) include two eye trackers, where each eye tracker captures an image of a corresponding eye and determines a gaze direction of the eye. In one example, the eye tracker determines an angular rotation of the eye, a translation of the eye, a change in the torsion of the eye. and / or a change in shape of the eye, according to the captured image of the eye, and determines the relative gaze direction with respect to the HWD 150, according to the determined angular rotation, translation and the change in the torsion of the eye. In one approach, the eye tracker may shine or project a predetermined reference or structured pattern on a portion of the eye. and capture an image of the eye to analyze the pattern projected on the portion of the eye to determine a relative gaze direction of the eye with respect to the HWD 1 0. In some embodiments, the eye trackers incorporate the orientation of the HWD 150 and the relative gaze direction with respect to the HWD 150 to determine a gaze direction of the user. Assuming for an example that the HWD 150 is oriented at a direction 30 degrees from a reference direction, and the relative gaze direction of the HWD 150 is -10 degrees (or 350 degrees) with respect to the HWD 150, the eye trackers may determine that the gaze direction of the user is 20 degrees from the reference direction. In some embodiments, a user of the HWD 150 can configure the HWD 150 (e.g., via user settings) to enable or disable the eye trackers as part of the sensors 155. In some embodiments, a user of the HWD 150 is prompted to enable or disable the eye trackers as part of the sensor 155 configuration.

[0058] In some embodiments, the sensors 155 include the hand tracker, which includes an electronic component or a combination of an electronic component and a software component that tracks a hand of the user. In other embodiments, the hand tracker may be a component separate from sensors 155. In some embodiments, the hand tracker includes or is coupled to an imaging sensor (e.g., camera) and an image processor that can detect a shape, a location and / or an orientation of the hand. The hand tracker may generate hand tracking measurements indicating the detected shape, location and / or orientation of the hand.

[0059] In some embodiments, the communication interfaces 165 (e.g., communication interface 165A, 165B) of the corresponding HWDs 150 (e.g., HWD 150A, 150B) and / or communication interfaces 115 (e.g., communication interface 115A, 115B) of the corresponding computing devices (e.g., computing device 110A, HOB) include an electronic component or a combination of an electronic component and a software component that is used for communication.

[0060] The communication interface 165 may communicate with a communication interface 115 of the computing device 110 through an intralink communication link 125 (e.g., communication link 125 A, 125B). The communication interface 165 may transmit to the computing device 110 sensor measurements indicating the determined location of the HWD 150, orientation of the HWD 150, the determined gaze direction of the user, and / or hand tracking measurements. For example, the computing device 110 may receive sensor measurements indicating location and the gaze direction of the user of the HWD 150 and / or hand tracking measurements and provide the image data to the HWD 150 for presentation of the artificial reality, for example, through the wireless link 125 (e.g., intralink). For example, the communication interface 115 may transmit to the HWD 150 data describing an image to be rendered. The communication interface 165 may receive from the computing device 110 sensor measurements indicating or corresponding to an image to be rendered. In some embodiments, the HWD 150 may communicate with the access point 105.

[0061] Similarly, the communication interface 115 (e.g., communication interface 115A, 115B) of the computing devices 110 may communicate with the access point 105 through a communication link 102 (e.g., communication link 102A, 102B). In certain embodiments, the computing device 110 may be considered a soft access point (e.g., a hotspot device). Through the communication link 102 (e.g., interlink), the communication interface 115 may transmit and receive from the access point 105 AR / VR content. The communication interface 115 of the computing device 110 may also communicate with communication interface 115 of a different computing device 110 through communication link 185. As described herein, the communication interface 115 may be a counterpart component to the communication interface 165 to communicate with a communication interface 115 of the computing device 110 through a communication link (e.g.. USB cable, a wireless link).

[0062] The communication interfaces 1 15 and 165 may receive and / or transmit information indicating a communication link (e.g., channel, timing) between the devices (e.g., between the computing devices 110A and HOB across communication link 185. between the HWD 150A and computing device 110A across communication link 125). According to the information indicating the communication link, the devices may coordinate or schedule operations to avoid interference or collisions.

[0063] The communication link may be a wireless link, a wired link, or both. In some embodiments, the communication interface 165 / 115 includes or is embodied as a transceiver for transmitting and receiving data through a wireless link. Examples of the wireless link can include a cellular communication link, a near field communication link, Wi-Fi, Bluetooth, or any communication wireless communication link. Examples of the wired link can include a USB. Ethernet. Firewire. HDMI, or any wired communication link. In embodiments in which the computing device 110 and the head wearable display 150 are implemented on a single system, the communication interface 165 may communicate with the computing device 110 through a bus connection or a conductive trace.

[0064] Using the communication interface, the computing device 110 (or HWD 150. or AP 105) may coordinate operations on links 102, 185 or 125 to reduce collisions or interferences by scheduling communication. For example, the computing device 110 may coordinate communication between the computing device 110 and the HWD 150 using communication link 125. Data (e g., a traffic stream) may flow in a direction on link 125. For example, the computing device 110 may communicate using a downlink (DL) communication to the HWD 150 and the HWD 150 may communicate using an uplink (UL) communication to the computing device 110. In some implementations, the computing device 110 may transmit a beacon frame periodically to announce / advertise a presence of a wireless link between the computing device 110 and the HWD 150 (or between HWDs 150 A and 150B). In an implementation, the HWD 150 may monitor for or receive the beacon frame from the computing device 110, and can schedule communication with the HWD 150 (e.g., using the information in the beacon frame, such as an offset value) to avoid collision or interference with communication between the computing device 110 and / or HWD 150 and other devices.

[0065] In some embodiments, the processor 170 may include an image Tenderer, for instance, which includes an electronic component or a combination of an electronic component and a software component that generates one or more images for display, for example, according to a change in view of the space of the artificial reality. In some embodiments, the image Tenderer is implemented as processor 170 (or a graphical processing unit (GPU), one or more central processing unit (CPUs), or a combination of them) that executes instructions to perform various functions described herein. In other embodiments, the image Tenderer may be a component separate from processor 170. The image Tenderer may receive, through the communication interface 165, data describing an image to be rendered, and render the image through the electronic display 175. In some embodiments, the data from the computing device 110 may be encoded, and the image Tenderer may decode the data to generate and render the image. In one aspect, the image Tenderer receives the encoded image from the computing device 110. and decodes the encoded image, such that a communication bandwidth between the computing device 110 and the HWD 150 can be reduced.

[0066] In some embodiments, the image Tenderer receives, from the computing device, 110 additional data including object information indicating virtual objects in the artificial reality space and depth information indicating depth (or distances from the HWD 150) of the virtual objects. Accordingly, the image Tenderer may receive from the computing device 110 object information and / or depth information. The image Tenderer may also receive updated sensor measurements from the sensors 155. The process of detecting, by the HWD 150, the location and the orientation of the HWD 150 and / or the gaze direction of the user wearing the HWD 150, and generating and transmitting, by the computing device 110, a high resolution image (e.g., 1920 by 1080 pixels, or 2048 by 1152 pixels) corresponding to the detected location and the gaze direction to the HWD 150 may be computationally exhaustive and may not be performed within a frame time (e.g.. less than 11 ms or 8 ms).

[0067] In some implementations, the image Tenderer may perform shading, reprojection, and / or blending to update the image of the artificial reality to correspond to the updated location and / or orientation of the HWD 150. Assuming that a user rotated their head after the initial sensor measurements, rather than recreating the entire image responsive to the updated sensor measurements, the image Tenderer may generate a small portion (e.g., 10 %) of an image corresponding to an updated view within the artificial reality according to the updated sensor measurements, and append the portion to the image in the image data from the computing device 110 through reprojection. The image Tenderer may perform shading and / or blending on the appended edges. Hence, without recreating the image of the artificial reality according to the updated sensor measurements, the image Tenderer can generate the image of the artificial reality.

[0068] In other implementations, the image Tenderer generates one or more images through a shading process and a reprojection process when an image from the computing device 110 is not received within the frame time. For example, the shading process and the reprojection process may be performed adaptively, according to a change in view of the space of the artificial reality'.

[0069] In some embodiments, the electronic display 175 is an electronic component that displays an image. The electronic display 175 may, for example, be 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 HWD 150 is worn by a user, the electronic display 175 is located proximate (e.g., less than 3 inches) to the user's eyes. In one aspect, the electronic display 175 emits or projects light towards the user's eyes according to image generated by the processor 170 (e.g.. image Tenderer).

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

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

[0072] In some embodiments, the computing device 110 is an electronic component or a combination of an electronic component and a software component that provides content to be rendered to the HWD 150. The computing device 110 may be embodied as a mobile device (e.g., smart phone, tablet PC, laptop, etc.). The computing device 110 may operate as a soft access point. In one aspect, the computing device 110 includes a communication interface 115, a processor 118. and a content provider 130 (e.g., content provider 130A, 130B). These components may operate together to determine a view (e.g., a field of view (FOV) of the user) of the artificial reality corresponding to the location of the HWD 150 and / or the gaze direction of the user of the HWD 150, and can generate an image of the artificial reality corresponding to the determined view.

[0073] The processors 118, 170 includes or is embodied as one or more central processing units, graphics processing units, image processors, or any processors for generating images of the artificial reality. In some embodiments, the processors 118, 170 may configure or cause the communication interfaces 115, 165 to toggle, transition, cycle or switch between a sleep mode and a wake up mode. In the wake up mode, the processor 118 may enable the communication interface 115 and the processor 170 may enable the communication interface 165, such that the communication interfaces 1 15, 165 may exchange data. In the sleep mode, the processor 118 may disable the wireless interface 115 and the processor 170 may disable (e.g., may implement low power or reduced operation in) the communication interface 165, such that the communication interfaces 115. 165 may not consume power, or may reduce power consumption. The processors 118, 170 may schedule the communication interfaces 115, 165 to switch between the sleep mode and the wake up mode periodically every frame time (e.g., 11 ms or 16 ms). For example, the communication interfaces 1 15, 165 may operate in the wake up mode for 2 ms of the frame time, and the communication interfaces 115, 165 may operate in the sleep mode for the remainder (e g., 9 ms) of the frame time. By disabling the wireless interfaces 115, 165 in the sleep mode, power consumption of the computing device 110 and the HWD 150 can be reduced or minimized.

[0074] In some embodiments, the processors 118, 170 may configure or cause the communication interfaces 115, 165 to resume communication based on stored information indicating communication between the computing device 110 and the HWD 150. In the wake up mode, the processors 118, 170 may generate and store information (e.g., channel, timing) of the communication between the computing device 110 and the HWD 150. The processors 118, 170 may schedule the communication interfaces 115, 165 to enter a subsequent wake up mode according to timing of the previous communication indicated by the stored information. For example, the communication interfaces 115, 165 may predict / determine when to enter the subsequent wake up mode, according to timing of the previous wake up mode, and can schedule to enter the subsequent wake up mode at the predicted time. After generating and storing the information and scheduling the subsequent wake up mode, the processors 118, 170 may configure or cause the wireless interfaces 115, 165 to enter the sleep mode. When entering the wake up mode, the processors 118, 170 may cause or configure the communication interfaces 115, 165 to resume communication via the channel or frequency band of the previous communication indicated by the stored information. Accordingly, the communication interfaces 115, in 165 entering the wake up mode from the sleep mode may resume communication, while bypassing a scan procedure to search for available channels and / or performing handshake or authentication. Bypassing the scan procedure allows extension of a duration of the communication interfaces 115, 165 operating in the sleep mode, such that the computing device 110 and the HWD 150 can reduce power consumption.

[0075] In some embodiments, the computing devices 110A, 110B may coordinate operations to reduce collisions or interferences. In one approach, the computing device 110A may transmit a beacon frame periodically to announce / advertise a presence of a wireless link 125A between the computing device 110A and the HWD 150A and can coordinate the communication between the computing device 110A and the HWD 150A. The computing device 110B may monitor for or receive the beacon frame from the computing device 110 A. and can schedule communication with the HWD 150B (e.g., using information in the beacon frame, such as an offset value) to avoid collision or interference with communication between the computing device 110A and the HWD 150A. For example, the computing device 110B may schedule the computing device 110B and the HWD 150B to enter a wake up mode, when the computing device 110A and the HWD 150A operate in the sleep mode. For example, the computing device HOB may schedule the computing device HOB and the HWD 15 OB to enter a sleep up mode, when the computing device 110A and the HWD 150A operate in the wake up mode. Accordingly, multiple computing devices 110 and HWDs 150 in proximity (e.g., within 20 ft) may coexist and operate with reduced interference.

[0076] The content provider 130 can include or correspond to a component that generates content to be rendered according to the location and / or orientation of the HWD 150, the gaze direction of the user and / or hand tracking measurements. In one aspect, the content provider 130 determines a view of the artificial reality according to the location and orientation of the HWD 150 and / or the gaze direction of the user of the HWD 150. For example, the content provider 130 maps the location of the HWD 150 in a physical space to a location within an artificial reality space, and determines a view of the artificial reality’ space along a direction corresponding to an orientation of the HWD 150 and / or the gaze direction of the user from the mapped location in the artificial reality space.

[0077] The content provider 130 may generate image data describing an image of the determined view of the artificial reality space, and transmit the image data to the HWD 150 through the communication interface 115. The content provider may also generate a hand model (or other virtual object) corresponding to a hand of the user according to the hand tracking measurement, and generate hand model data indicating a shape, a location, and an orientation of the hand model in the artificial reality space. The content provider 130 may encode the image data describing the image, and can transmit the encoded data to the HWD 150. In some embodiments, the content provider generates and provides the image data to the HWD 150 periodically (e.g., every 11 ms or 16 ms).

[0078] In some embodiments, the content provider 130 generates metadata including motion vector information, depth information, edge information, object information, etc., associated with the image, and transmits the metadata with the image data to the HWD 150 through the communication interface 115. The content provider 130 may encode and / or encode the data describing the image, and can transmit the encoded and / or encoded data to the HWD 150. In some embodiments, the content provider 130 generates and provides the image to the HWD 150 periodically (e.g., every one second).

[0079] In some embodiments, a scheduler 1 18 (e.g., scheduler 118A of the computing device 118A and / or scheduler 118B of the computing device HOB) may request R-TWT to transmit latency sensitive traffic using P2P communication. The AP 105 and scheduler 118 of the computing devices 110 may negotiate (e.g., perform a handshake process) and may establish a membership of a restricted TWT schedule. In some embodiments, when the AP 105 and the scheduler 118 are negotiating, the AP 105 may be considered a restricted TWT scheduling AP and the computing devices 110 may be considered a restricted TWT scheduled STA.

[0080] In some embodiments, the HWD 150 may request to send P2P traffic to the computing device 110. Accordingly, the HWD 150 may be considered the TWT requesting STA (e.g., the TWT STA that requests the TWT agreement), and the computing device 110 may be considered TWT responding STA (e.g., the TWT STA that respond to the TWT request). The communication link 125 between the computing devices 110 and the HWDs 150 may be a P2P link (e.g., a link used for transmission between two non-AP devices). The communication link 102 between the computing devices 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 from 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 the TWT requesting STA and the HWD 150 is the TWT responding STA.

[0081] The schedulers 118 of the computing devices 110 may schedule communication between the computing device(s) 110 and the HWD(s) 150 with the AP 105 such that the communication between the computing device(s) 110 and HWD(s) 150 is protected. The computing device(s) 1 10 may initiate such protected P2P communication with the HWD(s) 150 by indicating, to the AP 105, that the computing device(s) HOwish to schedule P2P communication in R-TWT SPs. The scheduler 118 of the computing device(s) may schedule (or negotiate) the requested R-TWT SP(s). The scheduler 118 of the computing device(s) may also indicate if the SP(s) are requested only for P2P communication (as compared to mixed P2P communication and non-P2P communication).

[0082] FIG. 2 is a diagram of a HWD 150, in accordance with an example embodiment. In some embodiments, the HWD 150 includes a front rigid body 205 and a band 210. The front rigid body 205 includes the electronic display 175 (not shown in FIG. 2). the lens (not shown in FIG. 2), the sensors 155, the eye trackers the communication interface 165, and the processor 170. In the embodiment shown by FIG. 2, the sensors 155 are located within the front rigid body 205, and may not visible to the user. In other embodiments, the HWD 150 has a different configuration than shown in FIG. 2. For example, the processor 170, the eye trackers, and / or the sensors 155 may be in different locations than shown in FIG. 2. Various operations described herein can be implemented on computer systems. FIG. 3 shows a block diagram of a representative computing system 314 usable to implement the present disclosure. In some embodiments, the computing device 110, the HWD 150 or both of FIG. 1 are implemented by the computing system 314. Computing system 314 can be implemented, for example, as a consumer device such as a smartphone, other mobile phone, tablet computer, wearable computing device (e.g.. smart watch, eyeglasses, head wearable display), desktop computer, laptop computer, or implemented with distributed computing devices. The computing system 314 can be implemented to provide VR, AR, MR experience. In some embodiments, the computing system 314 can include conventional computer components such as processors 316, storage device 318, network interface 320, user input device 322, and user output device 324.

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

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

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

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

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

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

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

[0090] FIGs. 1-2 illustrate devices that communicate traffic streams some of which may be latency sensitive (e.g., those carrying periodic AR / VR information / content). As described herein, the periodic operation of TWT benefits communication of periodic traffic (e.g.. latency sensitive traffic) by predictably communicating the periodic traffic. FIG. 4 is a timing diagram 400 showing a wake-up / sleep schedule of a computing device utilizing TWT, according to an example implementation of the present disclosure. The TWT start time is indicated by the computing device 110 (e.g., a portion of its relevant modules / circuitry) waking up at 402. The computing device 110 may wake up for a duration 404 defined by a SP. After the SP duration 404, the computing device 110 may enter a sleep state until the next TWT start time at 408. The interval of time between TWT start time 402 and TWT start time 408 may be considered the SP interval 406.

[0091] A TWT schedule may be communicated and / or negotiated using broadcast TWT (B- TWT) and / or individual TWT (I-TWT) signaling. In some embodiments, to signal I-TWT, TWT schedule information may be communicated to particular (individual) devices using a mode such as a Network Allocation Vector (NAV) to protect the medium access of TWT SPs. In contrast, to signal B-TWT. in some embodiments, a device (such as AP 105) mayschedule TWT SPs with other devices (e.g.. computing devices 110 and / or HWDs 150) and may share schedule information in beacon frames and / or probe response frames. Sharing schedule information using B-TWT may reduce overhead (e.g., negotiation overhead) as compared to the overhead used when sharing information using I-TWT.

[0092] The TWT mechanism may also be used in P2P communication. For example, TWT may be defined for tunneled direct link setup (TDLS) pairs (e.g., non-AP STAs), soft APs (such as computing devices 110) and STAs (such as HWD 150), and / or P2P group owners (GO) and group clients (GC). For instance, a TDLS pair of devices (e.g., HWD 150 and computing device 110) can request TWT membership for its latency sensitive traffic over a channel. In another example, a group owner (GO), such as a computing device 110, may request TWT membership for latency sensitive traffic over the P2P link.

[0093] When P2P communication is established, various channel access rules may govern the P2P communication. An AP assisted P2P trigger frame sequence may reduce the contention / collision associated with TWT (or R-TWT) in P2P communication. Accordingly, a P2P model where a P2P STA (e.g., a HWD 150) is not associated with an infra-basic sen-ice set (BSS) AP, may improve P2P communication. Without AP’s assistance or coordination, a transmission over the P2P link may collide with another transmission in the BSS. In some embodiments, a reverse direction protocol (RDP) may be enabled for P2P communication. During RDP, when a transmitting STA has obtained a transmit opportunity (TXOP), the transmitting STA may grant permission for the receiving STA to transmit information back to the transmitting STA during the same TXOP. Accordingly, if a TWT setup allows P2P transmission and indicates RDP. the P2P communication can be performed after a triggered frame sequence (e.g., a reverse direction frame exchange). In other embodiments, other protocols may be enabled for P2P communication. In some embodiments, trigger-enabled TWT can reduce the medium contention and / or collisions between UL and DL transmissions. The trigger-enabled TWT may be indicated using a TWT information element (IE).

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

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

[0096] In one aspect, it would be beneficial to enable Wi-Fi Direct Revision 2 (R2) devices to operate within P2P groups that use NoA scheduling. For example, an R2 device may want to join a P2P group operating in P2P connection compatibility (PCC) mode, where the GO advertises availability using a NoA schedule. However, Wi-Fi Direct R2 devices that do not implement PCC mode lack support for NOA and therefore cannot interpret the GO’s availability schedule, making them unable to join or communicate within the group.

[0097] To address these problems and / or benefits, disclosed herein includes systems, devices and methods for enabling operation of Wi-Fi Direct R2 devices in P2P groups that use NoA scheduling. In some embodiments, a device (e.g., a GC) that does not support PCC mode can receive a NoA schedule advertised by a GO, and generate a TWT schedule corresponding to the received NoA schedule. For example, the TWT schedule can define one or more SPs aligned with the GO’s availability, allowing the R2 device to transmit and receive frames in coordination with the group’s schedule. In some embodiments, a system can support P2P group operation by translating or mirroring aNoA-based schedule into a TWT format, enabling broader compatibility without requiring the R2 device to implement NoA logic.

[0098] In some embodiments, a GO device may be a device configured to manage two or more P2P groups. The GO device may be configured to identify a NoA schedule of the GO for a first P2P group. The NoA schedule may define one or more absence periods during which the GO is not available to communicate within the first P2P group. For instance, the GO device may determine the NoA schedule based on internal timing, resource sharing across P2P groups, and / or coordination characteristics with other devices. By identifying the NoA schedule, the GO device can provide a basis for downstream scheduling mechanisms (e.g., TWT schedules) and coordinate group participation without overlapping periods of unavailability.

[0099] In some embodiments, the GO device may be configured to generate a first frame including information of a first target wake time (TWT) schedule corresponding to the NoA schedule. The first TWT schedule may define one or more SPs during which the GO is available to communicate with one or more GCs in the first P2P group. The generation of the first frame may include embedding the TWT schedule information into one or more fields of a management frame or other signaling message suitable for P2P communication. The first TWT schedule may be constructed based on the identified absence periods in the NoA schedule, such that the SPs occur during times when the GO is not marked as absent. By generating the first frame in this manner, the GO device enables GCs to align their communication attempts with the availability windows of the GO, reducing collisions and improving coordination in the first P2P group.

[0100] In some embodiments, the GO device may receive, from a GC, a request frame requesting to join the first TWT schedule. The request frame may be a management or action frame transmitted by the GC over the wireless network and may include information identifying the GC and the specific TWT schedule the GC wishes to join. In response to receiving the request frame, the GO device may include the GC in the first P2P group. This inclusion may involve updating the membership list of the first P2P group, allocating communication resources for the GC, or transmitting an acknowledgment or confirmation message back to the GC. The interaction ensures that the GC is able to participate in schedule communications with the GO during the defined SPs of the first TWT schedule.

[0101] In some embodiments, the first P2P group managed by the GO device may operate in a PCC mode. The PCC mode may define a compatibility protocol or signaling behavior that ensures coordination among P2P group members based on enhanced timing or scheduling mechanisms. However, in these embodiments, the GC device requesting to join the first TWT schedule may not support the PCC mode. For example, the GC device may be an older device, a device based on a specification that omits PCC mode functionality, or otherwise a device whose PCC mode functionality is unavailable. Despite the lack of PCC support in the GC, the GO device may still accommodate the GC within the first P2P group, for instance, by converting or translating schedules into a form that is compatible with the GC device. This scenario may arise in mixed deployments where backwards compatibility is important, and the GO acts as an intermediary that enables non-PCC-capable devices to participate in TWT- based scheduling.

[0102] In some embodiments, the first TWT schedule may be transmitted using out-of-band signaling. Out-of-band signaling may refer to communication that occurs through a separate channel or mechanism distinct from the main data channel used for standard P2P group operation. For instance, the GO device may transmit the first TWT schedule via a side communication link or management interface, such as a Wi-Fi management frame, Bluetooth Low Energy (BLE) signal, or another wireless signaling path that is not bound to the in-band P2P connection. This technique can be useful when a GC device that does not support certain compatibility modes (e.g., PCC mode) is intended to join a TWT-based group, and in-band negotiation is not feasible due to the device's characteristics. By sending the TWT schedule using out-of-band, the GO device enables the GC to interpret the group timing and synchronization without requiring full support of the PCC mode or standard TWT negotiation procedures.

[0103] In some embodiments, the GO device may transmit, over a wireless network, the first frame to advertise the first P2P group. The first frame may include information of the first TWT schedule, which corresponds to a NoA schedule and defines one or more SPs during which the GO device is available. By transmitting this frame wirelessly, the GO enables other nearby devices, including potential GCs, to become aw are of the availability and timing of the first P2P group and to synchronize their operations accordingly. For example, the transmission of the first frame may use beacon frames, probe responses, or other management frames defined in the Wi-Fi Direct standard or compatible protocols.

[0104] The advertisement of the first P2P group through the first frame allows a non-PCC- capable GC device to join and participate in coordinated group communication using TWT- based scheduling, even if the GC lacks full PCC support. The wireless transmission of the frame supports dynamic discovery and integration of compatible devices into the group.

[0105] In some embodiments, the GO device may generate a second frame including information of a second TWT schedule corresponding to the NoA schedule. The second TWT schedule may define one or more SPs during which the GO device is available to communicate with devices in a second P2P group that is different from the first P2P group. This second frame may be transmitted over the wireless network to advertise the availability of the second P2P group and its associated timing. The GO device may thereby enable multiple devices, including GCs supporting different compatibility modes or communication capabilities, to discover and join the second group.

[0106] By generating and transmitting the second frame, the GO device can advertise a different service management, tailored to distinct network or device characteristics, without conflicting with the timing of the first P2P group. For instance, while the first group maysupport PCC mode for legacy or advanced compatibility-, the second group may operate under a distinct TWT-only schedule. The availability of separate TWT schedules tied to the same NoA schedule allows the GO to efficiently segment its communication responsibilities across groups while maintaining predictability- in availability-.

[0107] In some embodiments, the GO device may concurrently manage the first P2P group and the second P2P group. For example, while the GO device maintains a first TWT schedule and corresponding communication sessions with a first group of devices, it may also manage a second TWT schedule and active communications with a second group of devices. The SPs of the first and second TWT schedules may be arranged in accordance with the same NoA schedule or other configuration logic, such that the GO remains available to each group during its respective schedule time windows. This concurrent management allows the GO to support mixed device capabilities and optimize resource allocation across different groups. For instance, one group may include devices compatible with PCC mode, while another may operate without PCC support. By maintaining multiple P2P groups with separate service schedules, the GO can ensure seamless support for legacy and next-generation device, improves scheduling flexibility', and increase the efficiency of P2P network operations.

[0108] In some embodiments, the second P2P group may not support the PCC mode. For example, the GO device may establish the second P2P group specifically for devices that do not implement or are not capable of operating in the PCC mode. In such cases, the second TWT schedule generated and advertised by the GO may support scheduling and coordination among non-PCC devices while maintaining compatibility and timing integrity7based on the GO’s availability periods (e.g., as defined by a NoA schedule). This enables the GO to effectively manage devices with different compatibility profile by isolating them in separate P2P groups while still coordinating their respective communications.

[0109] In some embodiments, each of the first TWT schedule and the second TWT schedule may be a broadcast TWT. A broadcast TWT enables the GO device to define a shared set of SPs that are made available to multiple GC devices, without requiring individualized unicast TWT sessions for each client. The use of broadcast TWTs can simplify group management and conserve overhead, particularly when coordinating wake times for multiple devices within the same P2P group. In this context, the first TWT schedule, which corresponds to a first P2P group, and the second TWT schedule, which corresponds to a second P2P group, may each define SPs that are shared among group clients using the broadcast TWT format.

[0110] In some embodiments, the GC device may receive a NoA schedule of the GO device that manages a P2P group. The NoA schedule may define one or more absence periods during which the GO is not available for communication within the group. The GC may receive the NoA schedule as part of a broadcast frame or management message transmitted by the GO. The GC may use the received NoA schedule to understand the timing patterns of GO unavailability' and to plan its communication schedule accordingly. This supports dynamic and power-efficient coordination between the GC and the GO while maintaining compatibility across different device capabilities and operating modes.

[0111] In some embodiments, the GC device may generate a TWT schedule corresponding to the received NoA schedule of the GO. The TWT schedule may define one or more SPs during which the GO is expected to be available for communication. Based on the NoA schedule, which indicates the timing of one or more absence periods, the GC may calculate or construct the TWT schedule by identifying windows of time that fall outside the absence periods. This TWT schedule may then be used by the GC to align its transmission or reception windows to the availability periods of the GO, thereby avoiding failed communication attempts and conserving power. The TWT schedule may be constructed dynamically or based on predefined rules that ensure coordination with the GO’s NoA schedule.

[0112] In some embodiments, the one or more SPs defined in the TWT schedule generated by the GC do not overlap with the one or more absence periods specified in the NoA schedule of the GO. By avoiding overlap, the GC ensures that its communication attempts are aligned with the GO’s availability, as defined outside of its announced absence periods. This non-overlapping structure improves communication efficiency and avoids failed transmission attempts during times when the GO is unavailable. For instance, the GC may use the NoA schedule as a reference to determine when the GO will not be present, and then allocate each SP in the TWT schedule to fall entirely between the end of one absence period and the start of the next.

[0113] In some embodiments, each of the one or more SPs defined by the GC may start after a corresponding absence period ends and end before the next absence period begins. For instance, the GC may parse the NoA schedule of the GO to identify’ a series of discrete absence periods. Using this schedule, the GC may calculate a time window following each absence period during which the GO is expected to be available, and assign the start and end of each SP within such window. This approach allows the GC to define a TWT schedule that is synchronized to the available operating intervals of the GO, thereby reducing the risk of missed transmissions and improving P2P communications reliability.

[0114] In some embodiments, the TWT schedule generated by the GC may be a broadcast TWT schedule that includes a set of fields configured to define parameters for coordinated wake time behavior. The TWT schedule may include a TWT ID field, a responder power management (PM) mode filed, and an unavailability mode filed. The one or more processors of the GC may set the TWT ID field to a value of 0, the responder PM mode field to a value of 1, and the unavailability mode field to a value of 1. Setting the TWT ID to 0 may indicate a default or general-purpose broadcast TWT. The responder PM mode set to 1 may signify that the responder (e.g., the GC or another peer) operates in a power-saving mode, while the unavailability mode set to 1 may indicate periods during which the responder is unavailable for communication. This configuration ensures that the TWT schedule is properly formatted to align with the broadcast communication behavior for coordination with the GO’s availability schedule.

[0115] In some embodiments, the NoA schedule received by the GC may include a field of count that indicates the number of absence periods defined within the schedule. For example, the count field may specify how may distinct absence periods the GO intends to observe. To coordinate wake times accordingly, the TWT schedule generated by the GC may include a field of persistence. The persistence field may define how long the TWT schedule should remain valid or how many times the defined SPs are to be repeated.

[0116] The one or more processors of the GC may set the persistence field to a value that corresponds to the value of the count field in the NoA schedule. By aligning the TWT schedule’s persistence with the number of absence periods in the NoA schedule, the GC can ensure that the broadcast TWT behavior is terminated at an appropriate time, for example, when the defined absence periods end. This correspondence may simplify’ coordination between devices and reduce redundant transmissions outside the availability window of the GO.

[0117] In some embodiments, the one or more processors of the GC may transmit one or more frames over a wireless network according to the generated TWT schedule. For instance, the GC may identify one or more SPs within the TWT schedule (e.g.. each corresponding to a time when the GO is expected to be available) and may transmit data frames, control frames, or other communications content during those SPs. This enables the GC to efficiently communicate with the GO without attempting transmission during the defined absence periods. By following the TWT schedule for transmission timing, the GC may conserve power and reduce channel contention, while maintaining reliable access to the GO in a P2P group. The one or more frames may be transmitted using standard procedures associated with TWT operation, such as initiating transmission at the beginning of an SP and completing or deferring transmission before the next absence period begins.

[0118] As a non-limiting example, GC and / or GO devices maintain interoperability between an infrastructure network and a P2P group. For example, a GO device may manage a PCC- mode P2P group that includes PCC-supporting devices. The GO device may advertise a NoA schedule that defines absence periods for itself with respect to the infrastructure network managed by the infrastructure AP. A GC device, which does not support PCC mode, may join the P2P group and interoperate with the GO device by receiving the NoA schedule and converting it into a TWT schedule, and then schedule SPs to transmit or receive data with the GO device, ensuring that the SPs fall outside the absence periods defined by the NoA schedule.

[0119] In some embodiments, a GC device may generate a TWT schedule corresponding to a received NoA schedule of a GO device. The TWT schedule may define one or more SPs during which the GC device is available to communicate with the GO device. In some examples, the GC device may generate the TWT schedule in a manner that preserves the same availability and unavailability patterns indicated in the NoA schedule. That is, the TWT schedule may include SPs that align with activity periods in the NoA schedule and omit SPs during the absence periods of the GO. In this way, the TWT schedule may effectively represent a translation of the NoA schedule into a format supported by the GC. allowing the GC to interoperate with the GO despite lacking direct support for NoA schedule.

[0120] In some embodiments, a first device may include one or more processors. The one or more processors may be configured to receive a Notice of Absence (NoA) schedule of a second device as a group owner (GO) of a peer-to-peer (P2P) group. The one or more processors may be configured to generate a target wake time (TWT) schedule corresponding to the NoA schedule, the TWT schedule defining one or more service periods (SPs) during which the second device is available. The one or more processors may be configured to transmit, over a wireless network, one or more frames according to the TWT schedule.

[0121] In some embodiments, the NoA schedule may include one or more absence periods during which the second device is not available, and the one or more SPs do not overlap with the one or more absence periods. In some embodiments, each of the one or more SPs may start after a corresponding absence period of the one or more absence periods ends, and may end before an absence period next to the corresponding absence period starts. In some embodiments, the TWT may be a broadcast TWT. The TWT may include fields of TWT ID, responder power management (PM) mode, and unavailability mode. The one or more processors may be configured to set the fields of TWT ID, responder PM mode, and unavailability mode to values of 0, 1, 1, respectively. In some embodiments, the NoA schedule may include a field of count indicating the number of the one or more absence periods. The TWT schedule may include a field of persistence. The one or more processors may be configured to set the persistence field to a value corresponding to a value of the count field such that the TWT schedule ends when the one or more absence periods end.

[0122] In some embodiments, a first device may include one or more processors. The one or more processors may be configured to identify a NoA schedule of the first device for a first P2P group. The one or more processors may be configured to generate a first frame including information of a first target wake time (TWT) schedule corresponding to the NoA schedule. The first TWT schedule may define one or more service periods (SPs) during which the first device is available. The one or more processors may be configured to transmit, over a wireless network, the first frame to advertise the first P2P group.

[0123] In some embodiments, the one or more processors may be configured to receive, from a second device, a request frame requesting to join the first TWT schedule. The one or more processors may be configured to, in response to the request frame, include the second device in the first P2P group. In some embodiments, the first P2P group may operate in a P2P connection compatibility (PCC) mode, and the second device does not support the PCC mode.

[0124] In some embodiments, the first TWT schedule was transmitted using out-of-band signaling. In some embodiments, the one or more processors may be configured to generate a second frame including information of a second target wake time (TWT) schedule corresponding to the NoA schedule, the second TWT schedule defining one or more service periods (SPs) during which the first device is available. The one or more processors may be configured to transmit, over the wireless network, the second frame to advertise a second P2P group that is different from the first P2P group.

[0125] In some embodiments, the one or more processors may be configured to concurrently manage the first P2P group and the second P2P group. In some embodiments, the second P2P group does not support a P2P connection compatibility (PCC) mode. In some embodiments, each of the first TWT and the second TWT may be a broadcast TWT.

[0126] In some embodiments, a method may include identifying, by one or more processors of a first device, a NoA schedule of the first device for a first P2P group. The method may include generating, by the one or more processors, a first frame including information of a first target wake time (TWT) schedule corresponding to the NoA schedule, the first TWT schedule defining one or more service periods (SPs) during which the first device is available. The method may include transmitting, by the one or more processors, over a wireless network, the first frame to advertise the first P2P group.

[0127] In some embodiments, the method may include receiving, from a second device, a request frame requesting to join the first TWT schedule. The method may include, in response to the request frame, including the second device in the first P2P group. In some embodiments, the first P2P group may operate in a P2P connection compatibility (PCC) mode, and the second device does not support the PCC mode. In some embodiments, the first TWT schedule was transmitted using out-of-band signaling. In some embodiments, the method may include generating a second frame including information of a second target wake time (TWT) schedule corresponding to the NoA schedule, the second TWT schedule defining one or more service periods (SPs) during which the first device is available. The method may include transmitting, over the wireless network, the second frame to advertise a second P2P group that is different from the first P2P group. In some embodiments, the method may include concurrently managing the first P2P group and the second P2P group. In some embodiments, the second P2P group does not support a P2P connection compatibility (PCC) mode.

[0128] Embodiments in the present disclosure have at least the following advantages and benefits. Embodiments in the present disclosure can provide useful techniques for enabling Wi-Fi Direct R2 devices that do not support P2P connection compatibility (PCC) mode to operate within P2P groups managed using NoA scheduling. By allowing such devices to generate corresponding Target Wake Time (TWT) schedules from received NoA schedules, these embodiments enable broader interoperability across mixed-generation devices without requiring R2 devices to implement legacy mechanisms. Second, embodiments in the present disclosure can reduce development cost and implementation complexity by avoiding the need to support both NoA and TWT logic within the same device, while still allowing the device to participate in PCC-mode P2P groups using a translated TWT schedule.

[0129] Furthermore, as described above, systems, devices, and methods disclosed herein address problems of a system environment (e.g., of FIG. 5) where Wi-Fi Direct R2 devices that do not implement PCC mode lack support for NOA. FIG. 5 is an example system environment 500 in which a Wi-Fi Direct R2 device is unable to determine availability of a GO based on the GO'S NoA schedule, resulting in failed communication attempts or inefficient power usage. This illustrates the interoperability challenge that arises when newer- generation devices attempt to participate in P2P groups managed using legacy NoA-based scheduling.

[0130] With the foregoing in mind, the figures and description below illustrate various examples of systems and / or methods with TWT schedules based on NoA schedules. It should be noted that the figures and description below are non-limiting examples and can be implemented as any of various other configurations while remaining within the scope of the present disclosure.

[0131] FIG. 6 is an example system environment 600 including a GO device 610 and GC devices 620, 630, according to an example implementation of the present disclosure. In some embodiments, the GO device 610 may be a device configured to manage two or more P2P groups. The GO device 610 may be configured to identify a NoA schedule 650 of the GO device 610 for a first P2P group. The NoA schedule 650 may define one or more absence periods during which the GO device 610 is not available to communicate within the first P2P group. For instance, the GO device 610 may determine the NoA schedule 650 based on internal timing, resource sharing across P2P groups, and / or coordination characteristics with other devices. By identifying the NoA schedule 650, the GO device 610 can provide a basis for downstream scheduling mechanisms (e.g., TWT schedules) and coordinate group participation without overlapping periods of unavailability.

[0132] In some embodiments, the GO device 610 may be configured to generate a first frame including information of a first target wake time (TWT) schedule 660 corresponding to the NoA schedule 650. The first TWT schedule 660 may define one or more SPs during which the GO device 610 is available to communicate with one or more GCs (e.g., the GC devices 620, 630) in the first P2P group. The generation of the first frame may include embedding the TWT schedule information into one or more fields of a management frame or other signaling message suitable for P2P communication. The first TWT schedule 660 may be constructed based on the identified absence periods in the NoA schedule 650, such that the SPs occur during times when the GO device 610 is not marked as absent. By generating the first frame in this manner, the GO device 610 enables GCs (e.g., the GC devices 620, 630) to align their communication attempts with the availability windows of the GO device 610, reducing collisions and improving coordination in the first P2P group.

[0133] In some embodiments, the GO device 610 may receive, from a GC (e.g., the GC devices 620, 630), a request frame requesting to join the first TWT schedule 660. The request frame may be a management or action frame transmitted by the GC (e.g.. the GC devices 620, 630) over the wireless network and may include information identifying the GC (e.g., the GC devices 620, 630) and a specific TWT schedule the GC (e.g., the GC devices 620, 630) wishes to join. In response to receiving the request frame, the GO device 610 may include the GC (e.g., the GC devices 620, 630) in the first P2P group. This inclusion may involve updating the membership list of the first P2P group, allocating communication resources for the GC (e.g., the GC devices 620, 630), or transmitting an acknowledgment or confirmation message back to the GC (e.g., the GC devices 620, 630). The interaction ensures that the GC (e.g., the GC devices 620. 630) is able to participate in schedule communications with the GO device 610 during the defined SPs of the specified TWT schedule. In some embodiments, the first P2P group managed by the GO device 610 may operate in a PCC mode. The PCC mode may define a compatibility protocol or signaling behavior that ensures coordination among P2P group members based on enhanced timing or scheduling mechanisms. However, in these embodiments, the GC device (e.g., the GC device 630) requesting to join the first TWT schedule 660 may not support the PCC mode. For example, the GC device (e.g., the GC device 630) may be an older device, a device based on a specification that omits PCC mode functionality, or otherwise a device whose PCC mode functionality is unavailable. Despite the lack of PCC support in the GC (e g., the GC device 630), the GO device 610 may still accommodate the GC (e.g., the GC device 630) within the first P2P group, for instance, by converting or translating schedules into a form that is compatible with the GC device (e.g., the GC device 630). This scenario may arise in mixed deployments where backwards compatibility is important, and the GO device 610 acts as an intermediary that enables non-PCC-capable devices (e.g., the GC device 630) to participate in TWT-based scheduling.

[0134] In some embodiments, the first TWT schedule 660 may be transmitted using out-of- band signaling (e.g., as an out-of-band signal 670). Out-of-band signaling may refer to communication that occurs through a separate channel or mechanism distinct from the main data channel used for standard P2P group operation. For instance, the GO device 610 may transmit the first TWT schedule 660 via a side communication link or management interface, such as a Wi-Fi management frame. Bluetooth Low Energy (BLE) signal, or another wireless signaling path that is not bound to the in-band P2P connection. This technique can be useful when a GC device (e.g., the GC device 630) that does not support certain compatibility modes (e.g., PCC mode) is intended to join a TWT-based group, and in-band negotiation is not feasible due to the device’s characteristics. By sending the TWT schedule 660 using out- of-band, the GO device 610 enables the GC device (e.g., the GC device 630) to interpret the group timing and synchronization without requiring full support of the PCC mode or standard TWT negotiation procedures.

[0135] In some embodiments, the GO device 610 may transmit, over a wireless network, the first frame to advertise the first P2P group. The first frame may include information of the first TWT schedule, which corresponds to the NoA schedule 650 and defines one or more SPs during which the GO device 610 is available. By transmitting this frame wirelessly, the GO device 610 enables other nearby devices, including potential GCs, to become aware of the availability and timing of the first P2P group and to synchronize their operations accordingly. For example, the transmission of the first frame may use beacon frames, probe responses, or other management frames defined in the Wi-Fi Direct standard or compatible protocols.

[0136] The advertisement of the first P2P group through the first frame allows a non-PCC- capable GC device (e.g., the GC device 630) to join and participate in coordinated group communication using TWT-based scheduling, even if the GC device (e.g., the GC device 630) lacks full PCC support. The wireless transmission of the frame supports dynamic discovers’ and integration of compatible devices into the group.

[0137] In some embodiments, the GO device 610 may generate a second frame including information of a second TWT schedule corresponding to the NoA schedule 650. The second TWT schedule may define one or more SPs during which the GO device 610 is available to communicate with devices in a second P2P group that is different from the first P2P group. This second frame may be transmitted over the wireless network to advertise the availability of the second P2P group and its associated timing. The GO device 610 may thereby enable multiple devices, including GCs (e.g., the GC devices 620, 630) supporting different compatibility modes or communication capabilities, to discover and join the second group.

[0138] By generating and transmitting the second frame, the GO device 610 can advertise a different sendee management, tailored to distinct network or device characteristics, without conflicting with the timing of the first P2P group. For instance, while the first group may support PCC mode for legacy or advanced compatibility, the second group may operate under a distinct TWT-only schedule. The availability of separate TWT schedules tied to the same NoA schedule 650 allows the GO device 610 to efficiently segment its communication responsibilities across groups while maintaining predictability in availability.

[0139] In some embodiments, the GO device 610 may concurrently manage the first P2P group and the second P2P group. For example, while the GO device 610 maintains the first TWT schedule 660 and corresponding communication sessions with the first group of devices, it may also manage the second TWT schedule and active communications with the second group of devices. The SPs of the first and second TWT schedules may be arranged in accordance with the same NoA schedule 650 or other configuration logic, such that the GO device 610 remains available to each group during its respective schedule time windows. This concurrent management allows the GO device 610 to support mixed device capabilities and optimize resource allocation across different groups. For instance, one group (e.g., the GC device 620) may include devices compatible with PCC mode, while another (e.g., the GC device 630) may operate without PCC support. By maintaining multiple P2P groups with separate service schedules, the GO device 610 can ensure seamless support for legacy and next-generation device, improves scheduling flexibility, and increase the efficiency of P2P network operations.

[0140] As discussed above, in some embodiments, the second P2P group (e.g., the GC device 630) may not support the PCC mode. For example, the GO device 610 may establish the second P2P group specifically for devices (e.g., the GC device 630) that do not implement or are not capable of operating in the PCC mode. In such cases, the second TWT schedule generated and advertised by the GO device 610 may support scheduling and coordination among non-PCC devices while maintaining compatibility and timing integrity based on the GO’s availability periods (e.g., as defined by the NoA schedule 650). This enables the GO device 610 to effectively manage devices with different compatibility profile by isolating them in separate P2P groups while still coordinating their respective communications.

[0141] In some embodiments, each of the first TWT schedule 660 and the second TWT schedule may be a broadcast TWT. A broadcast TWT enables the GO device 610 to define a shared set of SPs that are made available to multiple GC devices (e.g., the GC devices 620, 630), without requiring individualized unicast TWT sessions for each client. The use of broadcast TWTs can simplify group management and conserve overhead, particularly when coordinating wake times for multiple devices within the same P2P group. In this context, the first TWT schedule 660, which corresponds to a first P2P group, and the second TWT schedule, which corresponds to a second P2P group, may each define SPs that are shared among group clients using the broadcast TWT format.

[0142] In some embodiments, the GC device (e g., the GC devices 620, 630) may receive the NoA schedule 650 of the GO device 610 that manages a P2P group. The NoA schedule 650 may define one or more absence periods during which the GO device 610 is not available for communication within the group. The GC device (e g., the GC devices 620, 630) may receive the NoA schedule 650 as part of a broadcast frame or management message transmitted by the GO device 610. The GC device (e.g., the GC devices 620, 630) may use the received NoA schedule 650 to understand the timing patterns of GO unavailability and to plan its communication schedule accordingly. This supports dynamic and power-efficient coordination between the GC device (e.g.. the GC devices 620. 630) and the GO device 610 while maintaining compatibility across different device capabilities and operating modes.

[0143] In some embodiments, the GC device (e.g., the GC devices 620, 630) may generate a TWT schedule corresponding to the received NoA schedule 650 of the GO device 610. The generated TWT schedule may define one or more SPs during which the GO device 610 is expected to be available for communication. Based on the NoA schedule 650, which indicates the timing of one or more absence periods, the GC (e.g., the GC devices 620, 630) may calculate or construct the TWT schedule by identifying windows of time that fall outside the absence periods. This TWT schedule may then be used by the GC (e.g., the GC devices 620, 630) to align its transmission or reception windows to the availability periods of the GO device 610, thereby avoiding failed communication attempts and conserving power. The TWT schedule may be constructed dynamically or based on predefined rules that ensure coordination with the GO’S NoA schedule 650.

[0144] In some embodiments, the one or more SPs defined in the TWT schedule generated by the GC device (e.g., the GC devices 620, 630) do not overlap with the one or more absence periods specified in the NoA schedule 650 of the GO device 610. By avoiding overlap, the GC device (e.g.. the GC devices 620. 630) ensures that its communication attempts are aligned with the GO’s availability, as defined outside of its announced absence periods. This non-overlapping structure improves communication efficiency and avoids failed transmission attempts during times when the GO device 610 is unavailable. For instance, the GC device (e.g., the GC devices 620, 630) may use the NoA schedule 650 as a reference to determine when the GO device 610 will not be present, and then allocate each SP in the TWT schedule to fall entirely between the end of one absence period and the start of the next.

[0145] FIG. 7 is an example timing diagram 700 showing a NoA schedule (e.g., the NoA schedule 650) and an equivalent TWT schedule 721 (e.g., generated by the GC device), according to an example implementation of the present disclosure. The NoA schedule 650 may include one or more absence periods 710. The equivalent TWT schedule may include one or more TWT availabilities 720. As shown, in some embodiments, each of the one or more SPs defined by the GC device (e.g., the GC devices 620, 630) may start after a corresponding absence period 710 ends, and end before the next absence period 710 begins. For instance, the GC device (e.g., the GC devices 620, 630) may parse the NoA schedule 650 of the GO device 610 to identify a series of absence periods 710. Using this schedule, the GC device (e.g., the GC devices 620, 630) may calculate a time window following each absence period 710 during which the GO device 610 is expected to be available, and assign the start and end of each SP within such window. This approach allows the GC device (e.g., the GC devices 620, 630) to define the TWT schedule 721 that is synchronized to the available operating intervals of the GO device 610, thereby reducing the risk of missed transmissions and improving P2P communications reliability-.

[0146] In some embodiments, the TWT schedule 721 generated by the GC device (e.g., the GC devices 620, 630) may be a broadcast TWT schedule that includes a set of fields configured to define parameters for coordinated wake time behavior. The TWT schedule 721 may include a TWT ID field, a responder power management (PM) mode filed, and an unavailability mode filed. The GC device (e.g., the GC devices 620, 630) may set the TWT ID field to a value of 0, the responder PM mode field to a value of 1, and the unavailability mode field to a value of 1. Setting the TWT ID to 0 may indicate a default or general-purpose broadcast TWT. The responder PM mode set to 1 may signify that the responder (e.g., the GC or another peer) operates in a power-saving mode, while the unavailability mode set to 1 may indicate periods during which the responder is unavailable for communication. This configuration ensures that the TWT schedule 721 is properly formatted to align with the broadcast communication behavior for coordination with the GO's availability schedule.

[0147] In some embodiments, the NoA schedule 650 received by the GC device (e.g., the GC devices 620, 630) may include a field of count that indicates the number of absence periods defined within the schedule. For example, the count field may specify how may distinct absence periods the GO device 610 intends to observe. To coordinate wake times accordingly, the TWT schedule 721 generated by the GC device (e.g., the GC devices 620, 630) may include a field of persistence. The persistence field may define how long the TWT schedule 721 should remain valid or how many times the defined SPs are to be repeated.

[0148] The GC device (e.g., the GC devices 620, 630) may set the persistence field to a value that corresponds to the value of the count field in the NoA schedule 650. By aligning the TWT schedule's persistence with the number of absence periods in the NoA schedule 650. the GC device (e.g., the GC devices 620, 630) can ensure that the broadcast TWT behavior is terminated at an appropriate time, for example, when the defined absence periods end. This correspondence may simplify' coordination between devices and reduce redundant transmissions outside the availability window of the GO device 610.

[0149] In some embodiments, the GC device (e.g., the GC devices 620, 630) may transmit one or more frames over a wireless network according to the generated TWT schedule 721. For instance, the GC device (e.g., the GC devices 620, 630) may identify one or more SPs within the TWT schedule 721 (e.g., each corresponding to a time when the GO device 610 is expected to be available) and may transmit data frames, control frames, or other communications content during those SPs. This enables the GC device (e.g., the GC devices 620, 630) to efficiently communicate with the GO device 610 without attempting transmission during the defined absence periods. By following the TWT schedule 721 for transmission timing, the GC device (e.g., the GC devices 620, 630) may conserve power and reduce channel contention, while maintaining reliable access to the GO device 610 in a P2P group. The one or more frames may be transmited using standard procedures associated with TWT operation, such as initiating transmission at the beginning of an SP and completing or deferring transmission before the next absence period begins.

[0150] In some embodiments, the GC device 620 (and / or the GC device 630) may generate the TWT schedule 721 corresponding to the NoA schedule 650 of the GO device 610. In some embodiments, the GC device 620 (and / or the GC device 630) may translate the NoA schedule 650 of the GO device 610 to a corresponding TWT schedule 721 that has the same one or more activity / wake / availability periods and the same one or more non- activity / sleep / unavailability periods as those of the NoA schedule. The TWT schedule 721 may define one or more SPs during which the GC device 620 (and / or the GC device 630) is available to communicate with the GO device 610. In some examples, the GC device 620 (and / or the GC device 630) may generate the TWT schedule 721 in a manner that preserves the same availability and unavailability paterns indicated in the NoA schedule 650. That is, the TWT schedule 721 may include SPs that align with activity periods in the NoA schedule 650 and omit SPs during the absence periods of the GO device 610. In this way, the TWT schedule 721 may effectively represent a translation of the NoA schedule 650 into a format supported by the GC device 620 (and / or the GC device 630), allowing the GC device 620 (and / or the GC device 630) to interoperate with the GO device 610 despite lacking direct support for NoA schedule 650.

[0151] FIG. 8 is an example system environment 800 in which GC and / or GO devices maintain interoperability between an infrastructure network and a P2P group, according to an example implementation of the present disclosure. The system environment 800 may include an infrastructure AP 801, a first device (e.g., Glasses; Wi-Fi Direct R2 GC, not supporting PCC mode) 810, a second device (e.g., GC managing a PCC mode PCP Group) 820, a third device (e.g., Smartphone; Wi-Fi Direct R1 GC) 830, and a fourth device (e.g., Casting device; Wi-Fi Direct R1 GC) 840. In the example shown, the second device 820 may act as a GO device (e.g., the GO device 610) and manage a PCC-mode P2P group (e.g., the GC device 620) that includes the third and fourth devices 830 and 840. The second device 820 may advertise a NoA schedule that defines absence periods for itself with respect to the infrastructure network managed by the infrastructure AP 801. The first device 810 (e.g., similar to the GC device 630), which does not support PCC mode, may join the P2P group and interoperate with the GO device 820 by receiving the NoA schedule and converting it into a TWT schedule. The first device 810 may then schedule SPs to transmit or receive data with the GO device 820, ensuring that the SPs fall outside the absence periods defined by the NoA schedule.

[0152] FIG. 9 is a flowchart showing a process 900 for TWT schedules based on NoA schedules, according to an example implementation of the present disclosure. In some embodiments, the process 900 is performed by a GO device (e.g., the GO device 610) including one or more processors (e.g., processors 316) and a transceiver (e.g., network interface 320). In some embodiments, the process 900 is performed by other entities. In some embodiments, the process 900 includes more, fewer, or different steps than shown in FIG. 9.

[0153] In some embodiments, the one or more processors of a first device (e.g., the GO device 610) may identify 902 a NoA schedule (e.g., the NoA schedule 650) of the first device for a first P2P group. In some embodiments, the one or more processors may receive, from a second device (e.g., the GC devices 620, 630), a request frame requesting to join the first TWT schedule (e.g., the TWT schedule 660). In response to the request frame, the one or more processors may include the second device in the first P2P group. For example, the first P2P group may operate in a P2P connection compatibility (PCC) mode, and the second device does not support the PCC mode.

[0154] In some embodiments, the one or more processors may generate 904 a first frame including information of a first target wake time (TWT) schedule (e.g., the TWT schedule 660) corresponding to the NoA schedule (e.g., the NoA schedule 650). The first TWT schedule may define one or more service periods (SPs) during which the first device is available. In some embodiments, the one or more processors may generate a second frame including information of a second target wake time (TWT) schedule corresponding to the NoA schedule. The second TWT schedule may define one or more service periods (SPs) during which the first device is available.

[0155] In some embodiments, the one or more processors may transmit 906 over a wireless network, the first frame to advertise the first P2P group. In some embodiments, the one or more processors may transmit, over the wireless network, the second frame to advertise a second P2P group that is different from the first P2P group. For example, the second P2P group does not support a P2P connection compatibility (PCC) mode. In some embodiments, the one or more processor may concurrently manage the first P2P group and the second P2P group. In some embodiments, the first TWT schedule may be transmitted using out-of-band signaling.

[0156] FIG. 10 is a flowchart showing a process 1000 for TWT schedules based on NoA schedules, according to an example implementation of the present disclosure. In some embodiments, the process 1000 is performed by a GC device (e.g., the GC devices 620, 630) including one or more processors (e.g., processors 316) and a transceiver (e.g., network interface 320). In some embodiments, the process 1000 is performed by other entities. In some embodiments, the process 1000 includes more, fewer, or different steps than shown in FIG. 10.

[0157] In some embodiments, the one or more processors of the first device (e.g., the GC devices 620, 630) may receive 1002 aNotice of Absence (NoA) schedule (e.g., the NoA schedule 650) of a second device (e.g., the GO device 610) as a group owner (GO) of a peer- to-peer (P2P) group.

[0158] In some embodiments, the one or more processors of the first device (e.g., the GC devices 620, 630) may generate 1004 a target wake time (TWT) schedule (e.g.. the TWT schedule 721) corresponding to the NoA schedule. The TWT schedule may define one or more service periods (SPs) during which the second device is available. In some embodiments, the NoA schedule may include one or more absence periods during which the second device is not available, and the one or more SPs do not overlap with the one or more absence periods. In some embodiments, each of the one or more SPs may start after a corresponding absence period of the one or more absence periods ends, and may end before an absence period next to the corresponding absence period starts.

[0159] In some embodiments, the TWT may be a broadcast TWT. The TWT may include fields of TWT ID, responder power management (PM) mode, and unavailability mode, and the one or more processors may be configured to set the fields of TWT ID, responder PM mode, and unavailability mode to values of 0, 1 , 1 , respectively. In some embodiments, the NoA schedule may include a field of count indicating the number of the one or more absence periods. The TWT schedule may include a field of persistence, and the one or more processors may be configured to set the persistence field to a value corresponding to a value of the count field such that the TWT schedule ends when the one or more absence periods end.

[0160] In some embodiments, the one or more processors of the first device (e.g., the GC devices 620, 630) may transmit 1006, over a wireless network, one or more frames according to the TWT schedule.

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

[0162] The hardware and data processing components used to implement the various processes, operations, illustrative logics, logical blocks, modules and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some embodiments, particular processes and methods may be performed by circuitry that is specific to a given function. The memory (e.g., memory, memory unit, storage device, etc.) may include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing data and / or computer code for completing or facilitating the various processes, layers and modules described in the present disclosure. The memory may be or include volatile memory or non-volatile memory, and may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. According to an exemplary embodiment, the memory is communicably connected to the processor via a processing circuit and includes computer code for executing (e.g., by the processing circuit and / or the processor) the one or more processes described herein.

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

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

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

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

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

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

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

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

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

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

Claims

WHAT IS CLAIMED IS:

1. A first device, comprising: one or more processors configured to: receive a Notice of Absence (NoA) schedule of a second device as a group owner (GO) of a peer-to-peer (P2P) group; generate a target wake time (TWT) schedule corresponding to the NoA schedule, the TWT schedule defining one or more service periods (SPs) during which the second device is available, wherein the NoA schedule and the TWT schedule have the same one or more activity periods or the same one or more non-activity periods; and transmit, over a wireless network, one or more frames according to the TWT schedule.

2. The first device according to claim 1, wherein the NoA schedule includes one or more absence periods during which the second device is not available, and the one or more SPs do not overlap with the one or more absence periods.

3. The first device according to claim 2, wherein each of the one or more SPs starts after a corresponding absence period of the one or more absence periods ends, and ends before an absence period next to the corresponding absence period starts.

4. The first device according to claim 2 or 3, wherein the TWT is a broadcast TWT, the TWT includes fields of TWT ID, responder power management (PM) mode, and unavailability' mode, and the one or more processors are further configured to set the fields of TWT ID, responder PM mode, and unavailability mode to values of 0, 1, 1, respectively.

5. The first device according to any one of claims 2 to 4, wherein the NoA schedule includes a field of count indicating the number of the one or more absence periods, the TWT schedule includes a field of persistence, and the one or more processors are configured to set the persistence field to a value corresponding to a value of the count field such that the TWT schedule ends when the one or more absence periods end.

6. A first device comprising: one or more processors configured to:identify a Notice of Absence (NoA) schedule of the first device for a first peer-to-peer (P2P) group; generate a first frame including information of a first target wake time (TWT) schedule corresponding to the NoA schedule, the first TWT schedule defining one or more sendee periods (SPs) during which the first device is available, wherein the NoA schedule and the first TWT schedule have the same one or more activity periods or the same one or more non-activity periods; and transmit, over a wireless network, the first frame to advertise the first P2P group.

7. The first device according to claim 6, wherein the one or more processors are configured to: receive, from a second device, a request frame requesting to join the first TWT schedule; and in response to the request frame, include the second device in the first P2P group; preferably wherein the first P2P group operates in a P2P connection compatibility (PCC) mode, and the second device does not support the PCC mode.

8. The first device according to claim 6 or 7, wherein the first TWT schedule was transmitted using out-of-band signaling.

9. The first device according to any one of claims 6 to 8, wherein the one or more processors are configured to: generate a second frame including information of a second target wake time (TWT) schedule corresponding to the NoA schedule, the second TWT schedule defining one or more sendee periods (SPs) during which the first device is available; and transmit, over the wireless network, the second frame to advertise a second P2P group that is different from the first P2P group; preferably wherein the one or more processors are configured to: concurrently manage the first P2P group and the second P2P group.

10. The first device according to claim 9, wherein the second P2P group does not support a P2P connection compatibility (PCC) mode; and / or wherein each of the first TWT and the second TWT is a broadcast TWT.

11. A method comprising: identifying, by one or more processors of a first device, a Notice of Absence (NoA)schedule of the first device for a first peer-to-peer (P2P) group; generating, by the one or more processors, a first frame including information of a first target wake time (TWT) schedule corresponding to the NoA schedule, the first TWT schedule defining one or more service periods (SPs) during which the first device is available, wherein the NoA schedule and the first TWT schedule have the same one or more activity periods or the same one or more non-activity periods: and transmitting, by the one or more processors, over a wireless network, the first frame to advertise the first P2P group.

12. The method according to claim 11, further comprising: receiving, from a second device, a request frame requesting to join the first TWT schedule: and in response to the request frame, including the second device in the first P2P group; preferably wherein the first P2P group operates in a P2P connection compatibility (PCC) mode, and the second device does not support the PCC mode.

13. The method according to claim 11 or 12, wherein the first TWT schedule was transmitted using out-of-band signaling.

14. The method according to any one of claims 11 to 13, further comprising: generating a second frame including information of a second target wake time (TWT) schedule corresponding to the NoA schedule, the second TWT schedule defining one or more service periods (SPs) during which the first device is available; and transmitting, over the wireless network, the second frame to advertise a second P2P group that is different from the first P2P group.

15. The method according to claim 14, further comprising: concurrently managing the first P2P group and the second P2P group; and / or wherein the second P2P group does not support a P2P connection compatibility (PCC) mode.

Images