US2023379979A1PendingUtilityA1

Asynchronous channel access control of a wireless system

Assignee: QUALCOMM INCPriority: Mar 1, 2021Filed: May 22, 2023Published: Nov 23, 2023
Est. expiryMar 1, 2041(~14.6 yrs left)· nominal 20-yr term from priority
H04W 74/0883H04W 74/0816H04W 84/12
69
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

This disclosure provides systems, methods and apparatus for asynchronous channel access control of a wireless system. In some aspects, a device may adjust the priority of one or more PPDUs and may perform other operations to ensure control of a wireless medium at certain times while still allowing for other devices to communicate on the wireless medium. For example, the device may adjust a backoff counter or one or more EDCA parameters to ensure obtaining control of the wireless medium to transmit a first PPDU of an application file. For one or more subsequent PPDUs of the application file, the device may again adjust a backoff counter or one or more EDCA parameters to allow other devices to obtain control of the wireless medium in certain scenarios (such as a second device to provide information back to the device or to otherwise transmit using the shared wireless medium).

Claims

exact text as granted — not AI-modified
1 . A method performed by a device, comprising:
 rendering a plurality of frames to be provided to a second device;   splitting each frame of the plurality of frames into a plurality of application files; and   for each application file of the plurality of application files:
 generating a plurality of physical layer convergence protocol (PLCP) protocol data units (PPDUs) to include the application file, wherein:
 each PPDU includes one or more media access control layer (MAC) service data units (MSDUs) associated with the application file; and 
 the application file is identified by a port number and a differentiated services field codepoint (DSCP) value included in each MSDU of the plurality of PPDUs; and 
 
   queuing the MSDUs for transmission to the second device.   
     
     
         2 . The method of  claim 1 , wherein queuing the MSDUs includes generating an MSDU queue in software for each application file, wherein each MSDU queue is identified by an internet protocol (IP) address, port number, and DSCP value. 
     
     
         3 . The method of  claim 2 , wherein each application file is associated with a traffic identifier (TID) that is associated with an access category (AC) of the application file. 
     
     
         4 . The method of  claim 3 , wherein the AC of the application file is associated with a priority of the application file, and wherein the priority of the application file depends on whether the application file is a i-slice or a p-slice. 
     
     
         5 . (canceled) 
     
     
         6 . The method of  claim 4 , further comprising:
 rendering a first p-slice;   generating a first MSDU queue associated with the first p-slice;   rendering a second p-slice after rendering the first p-slice; and   flushing the first MSDU queue after rendering the second p-slice and before providing, to the second device, a PPDU including one or more MSDUs associated with the first p-slice.   
     
     
         7 . The method of  claim 4 , further comprising:
 rendering a first i-slice;   generating a first MSDU queue associated with the first i-slice;   rendering a second i-slice or p-slice after rendering the first i-slice;   generating a second MSDU queue associated with the second i-slice; and   providing, to the second device, a PPDU including one or more MSDUs associated with the first i-slice after generating the second MSDU queue.   
     
     
         8 . The method of  claim 4 , wherein for an MSDU associated with the application file:
 the MSDU is attempted to be transmitted to the second device up to a threshold number of times; and   the device flushes an MSDU queue associated with the application file after unsuccessfully attempting to transmit the MSDU to the second device the threshold number of times.   
     
     
         9 - 13 . (canceled) 
     
     
         14 . A device configured for an extended reality (XR) experience, comprising:
 an interface; and   a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to:
 render a plurality of frames to be provided to a second device; 
 split each frame of the plurality of frames into a plurality of application files; and 
 for each application file of the plurality of application files:
 generate a plurality of physical layer convergence protocol (PLCP) protocol data units (PPDUs) to include the application file, wherein: 
 each PPDU includes one or more media access control layer (MAC) service data units (MSDUs) associated with the application file; and 
 the application file is identified by a port number and a differentiated services field codepoint (DSCP) value included in each MSDU of the plurality of PPDUs; and 
 
 queue the MSDUs for transmission to the second device. 
   
     
     
         15 . The device of  claim 14 , wherein queuing the MSDUs includes generating an MSDU queue in software for each application file, wherein each MSDU queue is identified by an internet protocol (IP) address, port number, and DSCP value. 
     
     
         16 . The device of  claim 15 , wherein each application file is associated with a traffic identifier (TID) that is associated with an access category (AC) of the application file. 
     
     
         17 . The device of  claim 16 , wherein the AC of the application file is associated with a priority of the application file. 
     
     
         18 . The device of  claim 17 , wherein the priority of the application file depends on whether the application file is a i-slice or a p-slice. 
     
     
         19 . The device of  claim 18 , wherein the processing system is further configured to:
 render a first p-slice;   generate a first MSDU queue associated with the first p-slice;   render a second p-slice after rendering the first p-slice; and   flush the first MSDU queue after rendering the second p-slice and before providing, to the second device, a PPDU including one or more MSDUs associated with the first p-slice.   
     
     
         20 . The device of  claim 18 , wherein:
 the processing system is further configured to:
 render a first i-slice; 
 generate a first MSDU queue associated with the first i-slice; 
 render a second i-slice or p-slice after rendering the first i-slice; and 
 generate a second MSDU queue associated with the second i-slice; and 
   the interface is configured to provide, to the second device, a PPDU including one or more MSDUs associated with the first i-slice after generating the second MSDU queue.   
     
     
         21 . The device of  claim 18 , wherein for an MSDU associated with the application file:
 the interface is configured to attempt to transmit the MSDU to the second device up to a threshold number of times; and   the processing system is further configured to flush an MSDU queue associated with the application file after unsuccessfully attempting to transmit the MSDU to the second device the threshold number of times.   
     
     
         22 . The device of  claim 21 , wherein the processing system is further configured to:
 generate a replacement application file after flushing the MSDU queue; and   generate a replacement MSDU queue associated with the replacement application file.   
     
     
         23 . The device of  claim 21 , wherein the interface is further configured to indicate, to the second device, that the MSDU queue is flushed. 
     
     
         24 . The device of  claim 14 , wherein the device is configured to use forward error correction (FEC) for transmitting one or more PPDUs to the second device. 
     
     
         25 . The device of  claim 24 , wherein use of FEC for transmitting one or more PPDUs to the second device is associated with one or more of:
 a link quality between the device and the second device;   one or more parameters of the second device; or   one or more parameters of the plurality of frames.   
     
     
         26 . The device of  claim 14 , wherein:
 the device includes a software enabled access point (SAP); and   the second device includes a head mounted display (HMD).   
     
     
         27 . A method performed by a device, comprising:
 obtaining, from a second device, one or more physical layer convergence protocol (PLCP) protocol data units (PPDUs) associated with an application file, wherein:
 a plurality of PPDUs include the application file, each PPDU including one or more media access control layer (MAC) service data units (MSDUs) associated with the application file and the application file being identified by a port number and a differentiated services field codepoint (DSCP) value included in each MSDU of the plurality of PPDUs; 
   obtaining, at a reorder (REO) queue of the device, one or more MSDUs associated with the application file from the second device; and   flushing the REO queue in accordance with not obtaining a remainder of MSDUs associated with the application file before a REO timeout occurs or an indication that a transmit queue associated with the one or more MSDUs is flushed by the second device.   
     
     
         28 . The method of  claim 27 , further comprising:
 obtaining, at the REO queue of the device, a portion of MSDUs associated with the application file, the portion of MSDUs including the one or more MSDUs; and   flushing the REO queue after not obtaining the remainder of MSDUs associated with the application file before the REO timeout occurs.   
     
     
         29 . The method of  claim 27 , further comprising:
 obtaining the indication that the transmit queue associated with the one or more MSDUs is flushed by the second device; and   flushing the REO queue after obtaining the indication.   
     
     
         30 . A device configured for an extended reality (XR) experience, including:
 an interface configured to:
 obtain, from a second device, one or more physical layer convergence protocol (PLCP) protocol data units (PPDUs) associated with an application file, wherein:
 a plurality of PPDUs include the application file, each PPDU including one or more media access control layer (MAC) service data units (MSDUs) associated with the application file and the application file being identified by a port number and a differentiated services field codepoint (DSCP) value included in each MSDU of the plurality of PPDUs; and 
 
 obtain, at a reorder (REO) queue of the device, one or more MSDUs associated with the application file from the second device; and 
   a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to:
 flush the REO queue in accordance with not obtaining a remainder of MSDUs associated with the application file before a REO timeout occurs or an indication that a transmit queue associated with the one or more MSDUs is flushed by the second device. 
   
     
     
         31 . The device of  claim 30 , wherein:
 the interface is further configured to obtain, at the REO queue of the device, a portion of MSDUs associated with the application file, the portion of MSDUs including the one or more MSDUs; and   the processing system is configured to flush the REO queue after not obtaining the remainder of MSDUs associated with the application file before the REO timeout occurs.   
     
     
         32 . The device of  claim 31 , wherein the REO timeout is associated with an access category (AC) of the application file. 
     
     
         33 . The device of  claim 30 , wherein:
 the interface is further configured to obtain the indication that the transmit queue associated with the one or more MSDUs is flushed by the second device; and   the processing system is configured to flush the REO queue after obtaining the indication.   
     
     
         34 . The device of  claim 30 , wherein the device is configured to use forward error correction (FEC) for obtaining one or more PPDUs from the second device. 
     
     
         35 . The device of  claim 34 , wherein use of the FEC for obtaining one or more PPDUs from the second device is associated with one or more of:
 a link quality between the device and the second device;   one or more parameters of the second device; or   one or more parameters of a plurality of application files including the application file.   
     
     
         36 . The device of  claim 35 , wherein:
 the second device includes a software enabled access point (SAP); and   the device includes a head mounted display (HMD).

Join the waitlist — get patent alerts

Track US2023379979A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.