Prosecution Insights
Last updated: July 17, 2026
Application No. 18/806,586

Resource Allocation in Multi-Access Point Coordination

Non-Final OA §102
Filed
Aug 15, 2024
Priority
Dec 27, 2023 — provisional 63/615,214
Examiner
WONG, XAVIER S
Art Unit
Tech Center
Assignee
Cisco Technology Inc.
OA Round
1 (Non-Final)
88%
Grant Probability
Favorable
1-2
OA Rounds
10m
Est. Remaining
98%
With Interview

Examiner Intelligence

Grants 88% — above average
88%
Career Allowance Rate
887 granted / 1010 resolved
+27.8% vs TC avg
Moderate +10% lift
Without
With
+10.3%
Interview Lift
resolved cases with interview
Typical timeline
2y 9m
Avg Prosecution
30 currently pending
Career history
1037
Total Applications
across all art units

Statute-Specific Performance

§101
1.4%
-38.6% vs TC avg
§103
82.8%
+42.8% vs TC avg
§102
9.3%
-30.7% vs TC avg
§112
1.4%
-38.6% vs TC avg
Black line = Tech Center average estimate • Based on career data from 1010 resolved cases

Office Action

§102
CTNF 18/806,586 CTNF 83277 Notice of Pre-AIA or AIA Status 07-03-aia AIA 15-10-aia The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA. Information Disclosure Statement The information disclosure statements (IDS) submitted on 15 th August 2024 and 3 rd June 2025 are in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner. ========== ========== ========== Claim Rejections - 35 USC § 102 07-07-aia AIA 07-07 The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless – 07-12-aia AIA (a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention. 07-15-03-aia AIA Claim s 1 – 14, 17, 18, 19 and 20 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Sun et al (US 2024/0090046 A1) . Claim 1 (similarly Claim 20 ). Sun shows a device (fig. 6), comprising: a processor (fig. 6: processor ); a network interface controller configured to provide access to a network (fig. 6: transceiver + antenna ); and a memory communicatively coupled to the processor (fig. 6: memory ), wherein the memory comprises a bandwidth allocation logic (fig. 6: code ; [0070]: resource allocations ) that is configured to: determine a first transmission opportunity (TXOP) schedule of the device (fig. 2; [0054]: the user information field may include an indication of a symbol, a slot or an absolute or relative time at which the allocated time resources begin for AP 105-a, identifying the first TXOP portion 203, and an indication of a symbol, a slot or an absolute or relative time at which the allocated time resources begin for AP 105-b, identifying the second TXOP portion 202 ; [0060]: the first AP 105-a may transmit or receive one or more data communications to or from one or more STAs in the BSS of AP 105-a using time resources during a first TXOP portion 203 ); obtain a second TXOP schedule of at least one network device ([0052]: following the TXOP indication process, and prior to time t 1 , the TXOP owner AP 105-b may transmit the MU-RTS frame 205 that includes, for each of the selected APs, TXOP scheduling information including an indication of the TXOP portions allocated to the respective APs, including the first TXOP portion 203 for AP 105-a and a second TXOP portion 202 for the TXOP owner AP 105-b ; [0056]: for the data communications 215, the TXOP owner AP 105-b may transmit or receive one or more data communications to or from one or more STAs in the BSS of the TXOP owner AP 105-b beginning at time t 3 using the time resources allocated to itself and the BSS during the second TXOP portion 202 ); generate an aggregate TXOP schedule based on the first TXOP schedule and the second TXOP schedule ([0033]: coordinated time domain multiple access (C-TDMA) may allow a group of access points (APs) to share or participate in a single transmission opportunity (TXOP) within a bandwidth ; [0075]: the first bandwidth 315 and the second bandwidth 310 may each use a resource unit (RU) allocation that is the same or different, even if the first bandwidth 315 and the second bandwidth 310 are the same bandwidth and share frequency resources ), wherein the aggregate TXOP schedule comprises at least one TXOP that has a first proportion of resource units (RUs) allocated to the device and a second proportion of RUs allocated to the at least one network device ([0052]: the TXOP owner AP 105-b may transmit the MU-RTS frame 205 that includes, for each of the selected APs, TXOP scheduling information including an indication of the TXOP portions allocated to the respective APs, including the first TXOP portion 203 for AP 105-a and a second TXOP portion 202 for the TXOP owner AP 105-b ); and transmit the aggregate TXOP schedule to the at least one network device ([0052]: the first TXOP portion 203 may be indicated as time resources usable by the respective AP 105-a to transmit data to, or receive data from, one or more respective associated wireless STAs and the second TXOP portion 202 may be indicated in the third frame as time resources usable by AP 105-b to transmit data to, or receive data from, one or more respective associated wireless STAs ). Claim 2. Sun shows the device of claim 1, wherein the bandwidth allocation logic is further configured to resolve at least one conflict between the first TXOP schedule and the second TXOP schedule ([0042]: the AP 105-a may perform a CCA for the overlapping portion of the bandwidth , and also for the nonoverlapping portion of the bandwidth ). Claim 3. Sun shows the device of claim 2, wherein the aggregate TXOP schedule is generated in response to resolving the at least one conflict between the first TXOP schedule and the second TXOP schedule ([0060]: there may be a guard (or “non-transmission”) interval (such as, for a SIFS duration) between the time resources allocated to a given one of the APs, such as the second TXOP portion 202, and the adjacent time resources allocated to another one of the APs, such as the first TXOP portion 203, to buffer and guard against interference that may result from overlapping communications that may result from timing errors ). Claim 4. Sun shows the device of claim 2, wherein the at least one conflict is caused by one or more overlapping RU requirements in the first TXOP schedule and the second TXOP schedule (figs. 3A, 3B and 3C; [0086]: the first bandwidth 315 and second bandwidth 355 may each use a resource unit (RU) allocation that is the same or different, for example for data communications, in first frequency portion 330 that is overlapping between the first bandwidth 315 and the second bandwidth 355 ). Claim 5. Sun shows the device of claim 1, wherein obtaining the second TXOP schedule comprises receiving the second TXOP schedule from the at least one network device ([0056]: the TXOP owner AP 105-b may transmit or receive one or more data communications to or from one or more STAs in the BSS of the TXOP owner AP 105-b beginning at time t 3 using the time resources allocated to itself and the BSS during the second TXOP portion 202 ). Claim 6. Sun shows the device of claim 1, wherein obtaining the second TXOP schedule comprises predicting the second TXOP based on a set of rules ([0104]: controlling the count and duration may allow for fairness to other APs scheduling stations of their respective BSSs to comply with count and duration rules for uplink transmissions during the shared TXOP ). Claim 7. Sun shows the device of claim 6, wherein the bandwidth allocation logic is further configured to learn the set of rules based on one or more historical TXOP schedules of the at least one network device ([0104]: controlling the count and duration may allow for fairness to other APs scheduling stations of their respective BSSs to comply with count and duration rules for uplink transmissions during the shared TXOP ). Claim 8. Sun shows the device of claim 1, wherein the second TXOP schedule comprises at least one of an uplink schedule or a downlink schedule ([0040]: after receiving the CTS the AP 105-b may transmit or receive, via downlink (DL) transmission , uplink (UL) reception , or both, the data communications with the STAs in coverage area within the TXOP ). Claim 9. Sun shows the device of claim 1, wherein the second TXOP schedule comprises at least one of : a TXOP count ([0103]: a participant AP may be restricted or restrict itself to schedule downlink transmissions to the wireless device such that the responses (such as BA or data transmissions) that the participant AP receives from wireless devices during a shared TXOP comply with a count threshold , a duration threshold , or both ), a transmission interval ([0104]: the STA 116 may limit or otherwise control the minimum interval between the frames and the total duration for the frames received from the STA 117 ), a transmission duration ( see above ), or an amount of traffic ([0051]: the TXOP owner AP 105-b may determine an amount of time resources of the TXOP to allocate to each of the selected APs after selecting the APs ). Claim 10. Sun shows the device of claim 1, wherein in response to transmitting the aggregate TXOP schedule ([0093]: the AP 105-a may continue the countdown of a backoff timer for the backoff procedure after receiving the scheduling information from the AP 105-b in an MU-RTS during the MU-RTS/CTS exchange 405 ), the bandwidth allocation logic is further configured to receive a proposed aggregate TXOP schedule from the at least one network device ( see above ). Claim 11. Sun shows the device of claim 10, wherein the proposed aggregate TXOP schedule comprises at least a third proportion of RUs allocated to the at least one network device that is different from the second proportion of RUs (fig. 5; [0102]: the third TXOP portion 504 may be scheduled between the second TXOP portion 502 and the first TXOP portion 503 between the AP 105-c uses an operating bandwidth that is equal to or no smaller than the second bandwidth 560 of the AP 105-b ). Claim 12. Sun shows the device of claim 1, wherein the first proportion of RUs and the second proportion of RUs are distributed in a time and frequency domain ([0067]: for the second frequency portion (the different, non-overlapping portion) AP 105-a may perform CCA and AP 105-a may not need to perform the backoff procedure in the overlapping, first frequency portion, for example because that portion is included within the time and frequency resources scheduled by the TXOP owner AP 105-b ). Claim 13. Sun shows the device of claim 1, wherein the first TXOP schedule comprises a first set of RU requirements associated with the device ([0100]: there may be a requirement that where an AP has shared or granted a portion of the TXOP of the AP with one or more other APs, those APs may start transmitting on a channel, such as a 20 MHz channel (subchannel), of their own operating bandwidth in the TXOP only if that channel, such as a 20 MHz channel, overlaps in frequency with preceding channels, including the channels (subchannels) of the TXOP owner AP ) and the second TXOP schedule comprises a second set of RU requirements associated with the at least one network device ([0100]: according to such a requirement , bandwidth for each successively-scheduled AP within the shared TXOP will have the bandwidth on which it may transmit constrained to be no more than the bandwidth of the immediately preceding AP – first and second TXOP schedules each has its own “requirement” ). Claim 14. Sun shows the device of claim 13, wherein the first set of RU requirements is represented in a first color in the first TXOP schedule ([0054]: the APID may be a MAC address of the AP, a BSSID associated with the AP, a BSS color associated with the AP , or a short identifier associated with the AP ) and the second set of RU requirements is represented in a second color in the second TXOP schedule ( see above : each of the first and second RU set requirement is associated with a BSS color ). Claim 17. Sun shows the device of claim 1, wherein prior to generating the aggregate TXOP schedule ([0033]: coordinated time domain multiple access (C-TDMA) may allow a group of access points (APs) to share or participate in a single transmission opportunity (TXOP) within a bandwidth ), the bandwidth allocation logic is further configured to establish Multi-Access Point (AP) coordination between the device and the at least one network device ([0036]: an extended network station (not shown) associated with the wireless communications system 100 may be connected to a wired or wireless distribution system that may allow multiple APs 105 to be connected in an ESS ). Claim 18. Sun shows the device of claim 1, wherein the second TXOP schedule is associated with a set of network devices coordinated by the at least one network device ([0052]: the second TXOP portion 202 may be indicated in the third frame as time resources usable by AP 105-b to transmit data to, or receive data from, one or more respective associated wireless STA s ). ---------- ---------- ---------- Claim 19 . Sun shows a device (fig. 6), comprising: a processor (fig. 6: processor ); a network interface controller configured to provide access to a network (fig. 6: transceiver + antenna ); and a memory communicatively coupled to the processor (fig. 6: memory ), wherein the memory comprises a bandwidth allocation logic (fig. 6: code ; [0070]: resource allocations ) that is configured to: transmit a first TXOP schedule to a network device, wherein the network device is a designated coordinator for Multi-Access Point (AP) coordination and has a second TXOP schedule (fig. 2; [0054]: the user information field may include an indication of a symbol, a slot or an absolute or relative time at which the allocated time resources begin for AP 105-a, identifying the first TXOP portion 203, and an indication of a symbol, a slot or an absolute or relative time at which the allocated time resources begin for AP 105-b, identifying the second TXOP portion 202 ; [0060]: the first AP 105-a may transmit or receive one or more data communications to or from one or more STAs in the BSS of AP 105-a using time resources during a first TXOP portion 203 ); and receive an aggregate TXOP schedule based on the first TXOP schedule and the second TXOP schedule ([0052]: following the TXOP indication process, and prior to time t 1 , the TXOP owner AP 105-b may transmit the MU-RTS frame 205 that includes, for each of the selected APs, TXOP scheduling information including an indication of the TXOP portions allocated to the respective APs, including the first TXOP portion 203 for AP 105-a and a second TXOP portion 202 for the TXOP owner AP 105-b ; [0056]: for the data communications 215, the TXOP owner AP 105-b may transmit or receive one or more data communications to or from one or more STAs in the BSS of the TXOP owner AP 105-b beginning at time t 3 using the time resources allocated to itself and the BSS during the second TXOP portion 202 ), wherein the aggregate TXOP schedule comprises at least one TXOP that has a first proportion of resource units (RUs) allocated to the device and a second proportion of RUs allocated to the network device ([0033]: coordinated time domain multiple access (C- TDMA) may allow a group of access points (APs) to share or participate in a single transmission opportunity (TXOP) within a bandwidth ; [0075]: the first bandwidth 315 and the second bandwidth 310 may each use a resource unit (RU) allocation that is the same or different, even if the first bandwidth 315 and the second bandwidth 310 are the same bandwidth and share frequency resources ; [0052]: the TXOP owner AP 105-b may transmit the MU-RTS frame 205 that includes, for each of the selected APs, TXOP scheduling information including an indication of the TXOP portions allocated to the respective APs, including the first TXOP portion 203 for AP 105-a and a second TXOP portion 202 for the TXOP owner AP 105-b ). ========== ========== ========== Allowable Subject Matter 12-151-08 AIA 07-43 12-51-08 Claim s 15 and 16 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims. ---------- --------- ---------- Conclusion The prior art made of record is considered pertinent to applicant’s disclosure. 1. Wang , US 2021/0378020 A1: a communication method that includes selecting, by user equipment (UE), a type of a random access message and determining one or more transmission opportunities based on one or more of a configuration message of a network device, a capability of the UE, and a preset rule set; and sending, by the UE, the random access message on one or more valid transmission opportunities in the one or more transmission opportunities. 2. Verma et al, US 11,405,164 B2: a method for sharing time resources of a wireless medium that relates more specifically to coordinated-AP (CAP) time-division-multiple-access (TDMA) techniques for sharing the time resources of a transmission opportunity (TXOP). Any inquiry concerning this communication or earlier communications from the examiner should be directed to Xavier Szewai Wong whose telephone number is 571.270.1780. The examiner can normally be reached on 11:30 am - 8:30 pm Mon to Fri. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Jeffrey Rutkowski can be reached on 571.270.1215. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /XAVIER S WONG/ Primary Examiner, Art Unit 2415 11 th June 2026 Application/Control Number: 18/806,586 Page 2 Art Unit: 2415 Application/Control Number: 18/806,586 Page 3 Art Unit: 2415 Application/Control Number: 18/806,586 Page 4 Art Unit: 2415 Application/Control Number: 18/806,586 Page 5 Art Unit: 2415 Application/Control Number: 18/806,586 Page 6 Art Unit: 2415 Application/Control Number: 18/806,586 Page 7 Art Unit: 2415 Application/Control Number: 18/806,586 Page 8 Art Unit: 2415
Read full office action

Prosecution Timeline

Aug 15, 2024
Application Filed
Jun 17, 2026
Non-Final Rejection mailed — §102 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12647348
Centralized approach to SR-TE paths with bandwidth guarantee using a single SID
2y 7m to grant Granted Jun 02, 2026
Patent 12647827
METHOD AND APPARATUS FOR PROVISIONING UPLINK STREAMING IN 5G NETWORKS
2y 7m to grant Granted Jun 02, 2026
Patent 12641454
RADIO ACCESS NETWORK (RAN)-CENTRIC DATA COLLECTION FOR DUAL CONNECTIVITY (DC)/CARRIER AGGREGATION (CA)
3y 9m to grant Granted May 26, 2026
Patent 12641016
ADDING NETWORK SERVICES TO MPLS NETWORK
3y 3m to grant Granted May 26, 2026
Patent 12640780
METHODS FOR UPLINK MULTIUSER SIGNALING AND TRANSMISSION
2y 10m to grant Granted May 26, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
88%
Grant Probability
98%
With Interview (+10.3%)
2y 9m (~10m remaining)
Median Time to Grant
Low
PTA Risk
Based on 1010 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month