Application-based transmission opportunity sharing

US12439437B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12439437-B2
Application numberUS-202117165335-A
CountryUS
Kind codeB2
Filing dateFeb 2, 2021
Priority dateFeb 2, 2021
Publication dateOct 7, 2025
Grant dateOct 7, 2025

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Application-based Transmission Opportunity (TXOP) sharing may be provided. First, a sharing AP may receive a request to share TXOPs with a requesting AP. The request may include information associated with an application executing on a client serviced by the requesting AP. Next, a TXOP duration for the requesting AP may be reserved based on the information associated with the application such that, in response to winning contention on the medium, the sharing AP may share a TXOP with the requesting AP for the TXOP duration.

First claim

Opening claim text (preview).

What is claimed is: 1. A method comprising: receiving, by a sharing Access Point (AP) prior to contending for medium access, an announcement shared across neighboring APs, the announcement comprising a request to share one or more Transmission Opportunities (TXOPs) with a requesting AP when the sharing AP wins contention for TXOPs, the request comprising an indication that the requesting AP is in need of additional TXOP for an application executing on a client serviced by the requesting AP and information comprising a traffic Access Category (AC) associated with the application; reserving, by the sharing AP, a TXOP duration for the requesting AP based on the information associated with the application received from the requesting AP, wherein reserving the TXOP duration for the requesting AP comprises: modifying Enhanced Distributed Channel Access (EDCA) parameters for the sharing AP to add EDCA parameters assigned to the traffic AC obtained from the information associated with the application, and contending for the medium access based on the modified EDCA parameters; and subsequent to gaining the medium access, sharing, by the sharing AP, a TXOP with the requesting AP for the TXOP duration. 2. The method of claim 1 , wherein the information associated with the application further includes at least one of: a traffic load, a traffic periodicity, or a latency sensitivity associated with the application. 3. The method of claim 2 , wherein reserving the TXOP duration for the requesting AP based on the information associated with the application comprises reserving the TXOP duration based on at least the traffic load. 4. The method of claim 1 , further comprising: computing a time period value; and determining that the requesting AP has not used a TXOP within at least a time period equal to the time period value. 5. The method of claim 4 , wherein the time period value is one of: a traffic periodicity of the application obtained from the information associated with the application; or a random value selected based on EDCA rules associated with traffic of the application. 6. The method of claim 1 , further comprising: receiving a notification that indicates an end of the request to share the TXOPs with the requesting AP. 7. The method of claim 1 , wherein the sharing AP is one of a subset of neighbor APs included in a TXOP sharing candidate list for the client that receives the request, the subset of neighbor APs including neighbor APs to the requesting AP that are determined to be within a predefined proximity to the client. 8. An apparatus comprising: a memory storage; and a processing unit coupled to the memory storage, wherein the processing unit is operative to: receive an announcement shared across neighboring Access Points (APs) prior to contending for medium access, the announcement comprising a request to share one or more Transmission Opportunities (TXOPs) with a requesting Access Point (AP) when the sharing AP wins contention for the TXOPs, the request comprising an indication that the requesting AP is in need of additional TXOPs for an application executing on a client serviced by the requesting AP and information comprising a traffic Access Category (AC) associated with the application; reserve a TXOP duration for the requesting AP based on the information associated with the application received from the requesting AP, wherein the processing unit being operative to reserve the TXOP duration for the requesting AP comprises the processing unit being operative to: modify Enhanced Distributed Channel Access (EDCA) parameters for the sharing AP to add EDCA parameters assigned to the traffic AC obtained from the information associated with the application, and contend for the medium access based on the modified EDCA parameters; and subsequent to gaining the medium access, share a TXOP with the requesting AP for the TXOP duration. 9. The apparatus of claim 8 , wherein the information associated with the application includes traffic load, and wherein the TXOP duration for the requesting AP is reserved based on at least the traffic load. 10. The apparatus of claim 8 , wherein the information associated with the application includes traffic periodicity, and wherein the processing unit is further operative to determine that the requesting AP has not used a TXOP within at least a time period equal to the traffic periodicity. 11. The apparatus of claim 8 , wherein the request is received from at least one of the requesting AP and a network management system in response to a detection of the application by at least one of the requesting AP or the network management system. 12. The apparatus of claim 8 , wherein the processing unit is further operative to: receive a notification that indicates an end of the request to share the one or more TXOPs with the requesting AP. 13. The apparatus of claim 8 , wherein the sharing AP is one of a subset of neighbor APs included in a TXOP sharing candidate list for the client that receives the request, the subset of neighbor APs including neighbor APs to the requesting AP that are determined to be within a predefined proximity to the client. 14. A method comprising: detecting, by a requesting Access Point (AP), an application executing on a client serviced by the requesting AP; transmitting, to at least one sharing AP prior to contending for medium access, a request to share one or more Transmission Opportunities (TXOPs) with the requesting AP when the sharing AP wins contention for TXOPs, the request comprising an indication that the requesting AP is in need of additional TXOPs for the application and information comprising a traffic Access Category (AC) associated with the application; subsequent to the at least one sharing AP gaining the medium access, receiving a TXOP shared from the at least one sharing AP, wherein a duration for the TXOPs is reserved for the requesting AP based on the information comprising a traffic Access Category (AC) associated with the application received from the requesting AP, wherein the at least one sharing AP gains the medium access by: modifying Enhanced Distributed Channel Access (EDCA) parameters for the sharing AP to add EDCA parameters assigned to the traffic AC obtained from the information associated with the application, and contending for the medium access based on the modified EDCA parameters; and using the TXOP to service the client for the duration. 15. The method of claim 14 , further comprising: determining a plurality of neighbor APs to the requesting AP, the plurality of neighbor APs including the at least one sharing AP; and determining whether proximity information of the plurality of neighbor APs to the client is available. 16. The method of claim 15 , further comprising: in response to determining the proximity information of the plurality of neighbor APs to the requesting AP is available: identifying a subset of the plurality of neighbor APs within a predefined proximity of the client; and transmitting the request to the subset of the plurality of neighbor APs, the subset including the at least one sharing AP. 17. The method of claim 16 , further comprising: including the subset of the plurality of neighbor APs in a TXOP sharing candidate list; and dynamically updating the TXOP sharing candidate list per TXOP or per traffic periodicity for the application. 18. The method of claim 15 , further comprising: in response to determining the proximity information of the plurality of neighbor APs to the requesting AP is not available:

Assignees

Inventors

Classifications

  • Scheduled access (hybrid access H04W74/02) · CPC title

  • H04W72/52Primary

    based on load · CPC title

  • with collision avoidance · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12439437B2 cover?
Application-based Transmission Opportunity (TXOP) sharing may be provided. First, a sharing AP may receive a request to share TXOPs with a requesting AP. The request may include information associated with an application executing on a client serviced by the requesting AP. Next, a TXOP duration for the requesting AP may be reserved based on the information associated with the application such t…
Who is the assignee on this patent?
Cisco Tech Inc
What technology area does this patent fall under?
Primary CPC classification H04W72/52. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Oct 07 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 11 related publications on this page (citations in our corpus or others sharing the same primary CPC).