CTNF 18/714,709 CTNF 99381 DETAILED ACTION 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. The preliminary amendment filed 5/30/2024 was received. PRIOR ART The following references are prior art: 1. Appl. No.: 18/257,073 (“Chit”) is prior are under 35 U.S.C. 102(a)(2) since it published as US 2024/0098712 A1, names another inventor (Rojan CHITRAKAR), and was effectively filed by Mar. 10, 2021 before Dec. 10, 2021 the effective filing date of the claimed invention. CLAIM REJECTIONS — 35 U.S.C. 102 07-06 AIA 15-10-15 In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. 07-07 AIA 07-07-aia 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: 35 U.S.C. 102 Conditions for patentability; novelty. (a) NOVELTY; PRIOR ART.—A person shall be entitled to a patent unless— 07-12-aia AIA (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. CLAIMS 37-56 07-15-03-aia AIA Claim s 37-56 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Chit for the reasons given below . Claim 37 With respect to claim 37, Chit disclosed: A method of controlling wireless transmissions in a wireless communication system, the method being performed by an access point of the wireless communication system ([0001] The present embodiments generally relate to communication apparatuses, and more particularly relate to methods and apparatuses for Coordinated Service Periods (SPs). [0008] According to an aspect of the present disclosure, there is provided a first Access Point (AP) comprising: circuitry, which in operation, generates a request frame indicating a request to setup one or more Coordinated service periods (SPs ); and a transmitter, which in operation, transmits the request frame to a second AP. [0033] FIG. 22 illustrates an example diagram of coordinated SPs for C-TDMA+C-OFDMA.), the method comprising: determining a set of one or more cooperation schemes for cooperating with one or more further access points of the wireless communication system ([0086] New Public Action frames, such as Coordinated SP Request Action frame 1600 of FIG. 16 and Coordinated SP Response Action frame 1800 of FIG. 18, may be used to negotiate the Coordinated SPs. For example, Coordinated SP Request frame 1600 may include a Schedule Element field 1602 that may indicate the requested SP parameters. The Schedule Element field 1602 may also include a Schedule Info field 1604 that may indicate a Coordinated SP Type value with reference to Table 1700 of FIG. 17. For example, a Coordinated SP Type value of 0 indicates that the Coordinated SP is for C-OFDMA, a Coordinated SP Type value of 1 indicates that the Coordinated SP is for C-TDMA, and so on. [FIG. 17] Coordinated SP Type value , Meaning; 0 , Coordinated SP is for C-OFDMA; 1, Coordinated SP is for C-TDMA; 2, Coordinated SP is for C-SR / C-BF; 3, Coordinated SP is for Joint Transmission; 4, Coordinated SP is for Low Latency traffic; 5, Coordinated SP is for NSEP traffic; 6-16, Reserved); determining a setup procedure for setting up cooperation among at least the access point and the one or more further access points based on a cooperation scheme selected from the set of one or more cooperation schemes ([0084] In various embodiments, a Coordinated SP may specify the Multi-AP Coordination schemes (C-OFDMA/CTDMA, C-SR/C-BF, Joint Transmission etc.) or the allowed traffic type within the SP. For example, referring to FIG. 15, Coordinated SP1 1502 may be Coordinated SPs for C-OFDMA/TDMA transmissions, while Coordinated SP2 1504 may be Coordinated SPs for C-SR/C-BF transmissions. [0085] An AP may request another AP to setup Coordinated SP for a particular type of MAP Coordination scheme, or for Coordinated SP for a particular type of traffic. During the SP negotiation phase, the requesting AP may also specify the desired 20 MHz sub-channels for itself for C-OFDMA; the Responding AP may specify the assigned 20 MHz sub-channels for requesting AP for C-OFDMA. Similarly the requesting AP may also specify the desired sub-time slots within the SP for itself for C-TDMA, or for prioritized traffic; the Responding AP may specify the assigned subtime slots for the requesting AP. [0086] New Public Action frames, such as Coordinated SP Request Action frame 1600 of FIG. 16 and Coordinated SP Response Action frame 1800 of FIG. 18, may be used to negotiate the Coordinated SPs. For example, Coordinated SP Request frame 1600 may include a Schedule Element field 1602 that may indicate the requested SP parameters. The Schedule Element field 1602 may also include a Schedule Info field 1604 that may indicate a Coordinated SP Type value with reference to Table 1700 of FIG. 17.); sending a message of the setup procedure to the one or more further access points, the message indicating a further part of the setup procedure ([0085] An AP may request another AP to setup Coordinated SP for a particular type of MAP Coordination scheme, or for Coordinated SP for a particular type of traffic. During the SP negotiation phase, the requesting AP may also specify the desired 20 MHz sub-channels for itself for C-OFDMA; the Responding AP may specify the assigned 20 MHz sub-channels for requesting AP for C-OFDMA. Similarly the requesting AP may also specify the desired sub-time slots within the SP for itself for C-TDMA, or for prioritized traffic; the Responding AP may specify the assigned subtime slots for the requesting AP. [0086] New Public Action frames, such as Coordinated SP Request Action frame 1600 of FIG. 16 and Coordinated SP Response Action frame 1800 of FIG. 18, may be used to negotiate the Coordinated SPs. For example, Coordinated SP Request frame 1600 may include a Schedule Element field 1602 that may indicate the requested SP parameters. The Schedule Element field 1602 may also include a Schedule Info field 1604 that may indicate a Coordinated SP Type value with reference to Table 1700 of FIG. 17. [FIG. 22] Coordinated SP negotiations. [0098] For example, the Sharing AP Ap1 may transmit MAP TF 2202 to Shared APs AP2 and AP3 to signal C-TDMA parameters for the C-TDMA portion 2204… the Sharing AP may transmit a second MAP TF 2206, at the end of its own C-TDMA portion 2204 of the TXOP, to allocate subchannels to the member APs during C-OFDMA portion 2208 of the Shared TXOP); and based on the setup procedure and the selected cooperation scheme, cooperating with at least one of the one or more further access points in using a transmission opportunity (TXOP) on a wireless medium ([0098] For example, referring to C-TDMA+C-OFDMA example diagram 2200 of FIG. 22, the Sharing AP AP1 uses the entire bandwidth during the initial portion of the Shared TXOP for transmissions to/from its own associated STAs via C-TDMA portion 2204 and assign the second portion of the Shared TXOP to other member APs of the coordinated SP. For example, the Sharing AP Ap1 may transmit MAP TF 2202 to Shared APs AP2 and AP3 to signal C-TDMA parameters for the C-TDMA portion 2204. During the second portion of the TXOP, the Sharing AP may further employ C-OFDMA and share the TXOP with member APs, allocating non-overlapping subchannels to each member AP. To achieve this, the Sharing AP may transmit a second MAP TF 2206, at the end of its own C-TDMA portion 2204 of the TXOP, to allocate subchannels to the member APs during C-OFDMA portion2208 of the Shared TXOP, i.e. the secondary 160 MHz channel to AP2 and the primary 160 MHz channel to AP3 (assuming the operating channel of all APs to be 320 MHz. [FIG. 22] C-TDMA 2204, C-OFDMA 2208 in Shared TXOP). Claim 38 With respect to claim 38, Chit disclosed: The method according to claim 37 (see rejection above), wherein the message indicates one or more of the following: whether the further part of the setup procedure requires a response to the message ([0058] Referring to FIG. 2, APs may negotiate time periods (Coordinated Service Periods) during which they agree to perform Multi-AP Coordinated transmissions. For example, coordinated SP negotiation between AP1 and AP2 occurs at SP negotiation 202. Such coordinated SPs for Multi-AP coordinated transmissions may include periodically repeating SPs such as Coordinated SP 206 and Coordinated SP 208, wherein a Sharing AP (the AP that wins the Shared TXOP) decides the actual Multi-AP Coordinated scheme to be used within each Coordinated SP. [0086] New Public Action frames, such as Coordinated SP Request Action frame 1600 of FIG. 16 and Coordinated SP Response Action frame 1800 of FIG. 18, may be used to negotiate the Coordinated SPs… Coordinated SP Response frame 1800 may include a Status field 1802 that may indicate whether the request was accepted or rejected. The frame may also include a Schedule Element field 1804 that may indicate the agreed SP parameters for the Coordinated SP.); and a number of further messages to be exchanged between the access point and the at least one of the one or more further access points in the setup procedure ([0061] APs can negotiate the following parameters for the Coordinated SPs. [0065] Number of Coordinated SPs: If greater than one, this parameter indicates the total number of periodically repeating Coordinated SPs.). Claim 39 With respect to claim 33, Chit disclosed: The method according to claim 37 (see rejection above), wherein the set of one or more cooperation schemes includes at least two cooperation schemes which differ with respect to a number of messages to be exchanged between the access point and the at least one of the one or more further access points during the setup procedure ([0097] FIG. 21 illustrates example diagram 2100 of coordinated SPs for C-TDMA. [FIG. 21] MAP TF in 2102. [0098] For example, referring to C-TDMA+C-OFDMA example diagram 2200 of FIG. 22, the Sharing AP AP1 uses the entire bandwidth during the initial portion of the Shared TXOP for transmissions to/from its own associated STAs via C-TDMA portion 2204 and assign the second portion of the Shared TXOP to other member APs of the coordinated SP. For example, the Sharing AP Ap1 may transmit MAP TF 2202 to Shared APs AP2 and AP3 to signal C-TDMA parameters for the C-TDMA portion 2204. During the second portion of the TXOP, the Sharing AP may further employ C-OFDMA and share the TXOP with member APs, allocating non-overlapping subchannels to each member AP. To achieve this, the Sharing AP may transmit a second MAP TF 2206, at the end of its own C-TDMA portion 2204 of the TXOP, to allocate subchannels to the member APs during C-OFDMA portion2208 of the Shared TXOP, i.e. the secondary 160 MHz channel to AP2 and the primary 160 MHz channel to AP3 (assuming the operating channel of all APs to be 320 MHz. [FIG. 22] MAP TF 2202 and MAP TF 2206.). Claim 40 With respect to claim 40, Chit disclosed: The method according to claim 37 (see rejection above), wherein one or more of the following applies: for at least one of the one or more cooperation schemes, a number of messages of the setup procedure transmitted from the access point to the at least one of the one or more further access points is one; and for at least one of the one or more cooperation schemes, a number of messages of the setup procedure transmitted from the access point to the at least one of the one or more further access points is two ([0097] FIG. 21 illustrates example diagram 2100 of coordinated SPs for C-TDMA. [FIG. 21] MAP TF in 2102. [0098] For example, referring to C-TDMA+C-OFDMA example diagram 2200 of FIG. 22, the Sharing AP AP1 uses the entire bandwidth during the initial portion of the Shared TXOP for transmissions to/from its own associated STAs via C-TDMA portion 2204 and assign the second portion of the Shared TXOP to other member APs of the coordinated SP. For example, the Sharing AP Ap1 may transmit MAP TF 2202 to Shared APs AP2 and AP3 to signal C-TDMA parameters for the C-TDMA portion 2204. During the second portion of the TXOP, the Sharing AP may further employ C-OFDMA and share the TXOP with member APs, allocating non-overlapping subchannels to each member AP. To achieve this, the Sharing AP may transmit a second MAP TF 2206, at the end of its own C-TDMA portion 2204 of the TXOP, to allocate subchannels to the member APs during C-OFDMA portion2208 of the Shared TXOP, i.e. the secondary 160 MHz channel to AP2 and the primary 160 MHz channel to AP3 (assuming the operating channel of all APs to be 320 MHz. [FIG. 22] MAP TF 2202 and MAP TF 2206.. Claim 41 With respect to claim 41, Chit disclosed: The method according to claim 37 (see rejection above), wherein the message indicates one of the following: the selected cooperation scheme, or at least one suggested cooperation scheme (([0086] New Public Action frames, such as Coordinated SP Request Action frame 1600 of FIG. 16 and Coordinated SP Response Action frame 1800 of FIG. 18, may be used to negotiate the Coordinated SPs. For example, Coordinated SP Request frame 1600 may include a Schedule Element field 1602 that may indicate the requested SP parameters. The Schedule Element field 1602 may also include a Schedule Info field 1604 that may indicate a Coordinated SP Type value with reference to Table 1700 of FIG. 17. For example, a Coordinated SP Type value of 0 indicates that the Coordinated SP is for C-OFDMA, a Coordinated SP Type value of 1 indicates that the Coordinated SP is for C-TDMA, and so on. [FIG. 17] Coordinated SP Type value , Meaning; 0 , Coordinated SP is for C-OFDMA; 1, Coordinated SP is for C-TDMA; 2, Coordinated SP is for C-SR / C-BF; 3, Coordinated SP is for Joint Transmission; 4, Coordinated SP is for Low Latency traffic; 5, Coordinated SP is for NSEP traffic; 6-16, Reserved). Claim 42 With respect to claim 42, Chit disclosed: The method according to claim 37 (see rejection above), wherein a further message transmitted by the access point in the further part of the setup procedure indicates one of the following: the selected cooperation scheme, or at least one suggested cooperation scheme (0098] For example, the Sharing AP Ap1 may transmit MAP TF 2202 to Shared APs AP2 and AP3 to signal C-TDMA parameters for the C-TDMA portion 2204. During the second portion of the TXOP, the Sharing AP may further employ C-OFDMA and share the TXOP with member APs, allocating non-overlapping subchannels to each member AP. To achieve this, the Sharing AP may transmit a second MAP TF 2206, at the end of its own C-TDMA portion 2204 of the TXOP, to allocate subchannels to the member APs during C-OFDMA portion2208 of the Shared TXOP, i.e. the secondary 160 MHz channel to AP2 and the primary 160 MHz channel to AP3 (assuming the operating channel of all APs to be 320 MHz.). Claim 43 With respect to claim 43, Chit disclosed: The method according to claim 37 (see rejection above), wherein one of the following indicates whether the selected cooperation scheme applies to downlink transmission, uplink transmission, or both downlink and uplink transmission: the message, or a further message transmitted by the access point in the further part of the setup procedure ([0075] AP2 transmits a Multi-AP Trigger frame 802 to another AP (AP1) to initiate coordinated uplink transmissions. The Multi-AP Trigger frame 802 instructs AP1 to initiate an UL transmission from STA2 and also assigns RU1 to be used for the UL transmission from STA2.). Claim 44 With respect to claim 44, Chit disclosed: The method according to claim 37 (see rejection above), wherein the one or more cooperation schemes include one or more of the following: a cooperation scheme based on coordinated time division multiple access, a cooperation scheme based on coordinated orthogonal frequency division multiple access, a cooperation scheme based on coordinated spatial reuse, a cooperation scheme based on coordinated beamforming, and a cooperation scheme based on joint transmission by two or more access points ([0086] New Public Action frames, such as Coordinated SP Request Action frame 1600 of FIG. 16 and Coordinated SP Response Action frame 1800 of FIG. 18, may be used to negotiate the Coordinated SPs. For example, Coordinated SP Request frame 1600 may include a Schedule Element field 1602 that may indicate the requested SP parameters. The Schedule Element field 1602 may also include a Schedule Info field 1604 that may indicate a Coordinated SP Type value with reference to Table 1700 of FIG. 17. For example, a Coordinated SP Type value of 0 indicates that the Coordinated SP is for C-OFDMA, a Coordinated SP Type value of 1 indicates that the Coordinated SP is for C-TDMA, and so on. [FIG. 17] Coordinated SP Type value , Meaning; 0 , Coordinated SP is for C-OFDMA; 1, Coordinated SP is for C-TDMA; 2, Coordinated SP is for C-SR / C-BF; 3, Coordinated SP is for Joint Transmission; 4, Coordinated SP is for Low Latency traffic; 5, Coordinated SP is for NSEP traffic; 6-16, Reserved). Claim 45 With respect to claim 45, Chit disclosed: The method according to claim 37 (see rejection above), further comprising one or more of the following sending an indication of a capability of the access point to at least one of the one or more further access points, wherein the cooperating in using the TXOP is based on the capability of the access point; and receiving, from at least one of the one or more further access points, respective indications of respective capabilities of the at least one further access point, wherein said cooperating in using the TXOP is based on the respective capabilities of the at least one further access point ([0078] An AP candidate Set is a set of APs that have performed basic negotiation and capabilities exchanges and agreed to participate in Multi-AP coordinated transmissions, either as a Sharing AP (AP that shares an obtained TXOPwith another AP) or a Shared AP (recipient of a shared TXOP). For this disclosure, it is assumed that all the participating APs are members of the AP candidate set. The APs are assumed to have completed the negotiation for the formation of the AP Candidate Set. used). [0082] Further, an AP or STA may indicate their supported features using an EHT capabilities element 1300 as shown in FIG. 13. For example, EHT MAC Capabilities field 1302 may include an Enhanced TWT field 1304 which indicate whether Enhanced TWT is supported. EHT MultiAP Capabilities field 1306 may include a C-OFDMA field, C-TDMA field, C-SR field, C-BF field and Joint Transmission field which may be used to indicate if a Multi-AP transmission scheme is supported. The EHT Multi-AP Capabilities field 1306 may also include a Coordinated SP field 1308 which may indicate whether a concerned AP supports Coordinated SPs, and a SP Information Solicitation field 1310 which may indicate whether a concerned AP supports solicitation of information about SPs. [0084] In various embodiments, a Coordinated SP may specify the Multi-AP Coordination schemes (C-OFDMA/CTDMA, C-SR/C-BF, Joint Transmission etc.) or the allowed traffic type within the SP. [0085] An AP may request another AP to setup Coordinated SP for a particular type of MAP Coordination scheme, or for Coordinated SP for a particular type of traffic. [0086] New Public Action frames, such as Coordinated SP Request Action frame 1600 of FIG. 16 and Coordinated SP Response Action frame 1800 of FIG. 18, may be used to negotiate the Coordinated SPs. For example, Coordinated SP Request frame 1600 may include a Schedule Element field 1602 that may indicate the requested SP parameters. The Schedule Element field 1602 may also include a Schedule Info field 1604 that may indicate a Coordinated SP Type value with reference to Table 1700 of FIG. 17. For example, a Coordinated SP Type value of O indicates that the Coordinated SP is for C-OFDMA, a Coordinated SP Type value of 1 indicates that the Coordinated SP is for C-TDMA, and so on. Further, Coordinated SP Response frame 1800 may include a Status field 1802 that may indicate whether the request was accepted or rejected. The frame may also include a Schedule Element field 1804 that may indicate the agreed SP parameters for the Coordinated SP.). Claim 46 Claim 46 recites limitations similar to claim 37, except that it is from the perspective of one of the “ further access points ” of claim 37, and is rejected by the same reasoning. Claim 47 Claim 47 recites limitations similar to claim 38 and is rejected by the same reasoning. Claim 48 Claim 48 recites limitations similar to claim 39 and is rejected by the same reasoning. Claim 49 Claim 49 recites limitations similar to claim 40 and is rejected by the same reasoning. Claim 50 Claim 50 recites limitations similar to claim 41 and is rejected by the same reasoning. Claim 51 Claim 51 recites limitations similar to claim 42 and is rejected by the same reasoning. Claim 52 Claim 52 recites limitations similar to claim 43 and is rejected by the same reasoning. Claim 53 Claim 53 recites limitations similar to claim 44 and is rejected by the same reasoning. Claim 54 Claim 54 recites limitations similar to claim 45 and is rejected by the same reasoning. Claim 55 Claim 55 recites limitations similar to claim 37, except that it further recites “ the access point comprising: at least one processor; and, a memory containing program code executable by the at least one processor, wherein execution of the program code by the at least one processor causes the access point to ” perform operations similar to those of claim 37 (Chit [0127] and [FIG. 32] CPU 3214 and Memory 3218), and is rejected by the same reasoning. Claim 56 Claim 56 recites limitations similar to claim 46, except that further recites “ the access point comprising: at least one processor; and a memory containing program code executable by the at least one processor, wherein execution of the program code by the at least one processor causes the access point to perform the method of claim 46 ” (Chit [0127] and [FIG. 32] CPU 3214 and Memory 3218), and is rejected by the same reasoning. PERTINENT PRIOR ART 07-96 AIA The prior art made of record and not relied upon is considered pertinent to applicant's disclosure : 1. US 2021/0111855 A1 (Verma) is prior art under 35 U.S.C. 102(a)(1) since it published Apr. 15, 2021 before Dec. 10, 2021 the effective filing date of the claimed invention. Verma describes coordinated AP (CAP) time-division-multiple-access (TDMA) techniques for sharing the time resources of a transmission opportunity (TXOP)… the winning AP may assign, grant or allocate (hereinafter used interchangeably) itself one or more of the time resources and also allocate each of one or more remaining time resources to one or more other ones of the coordinated APs. 2. Appl. No.: 17/838,096 (“Sha”) is prior are under 35 U.S.C. 102(a)(2) since it published as US 2022/0408355 A1, names another inventor (Rubayet Shafin), and was effectively filed by Jun. 23, 2021 before Dec. 10, 2021 the effective filing date of the claimed invention. Sha [Abtract] describes transmitting, to the second AP, a MAP coordination announcement that includes an indication that the first AP has obtained the TXOP and the parameters of the first TWT operation. The method further includes receiving, from the second AP, a MAP coordination response that indicates capabilities of the second AP and determining, based on the MAP coordination response, whether to perform MAP coordination with the second AP. CONCLUSION Any inquiry concerning this communication or earlier communications from the examiner should be directed to Christopher Davis whose telephone number is 703-756-1832. The examiner can normally be reached Mon-Fri from 11AM to 7PM ET. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ayaz Sheikh, can be reached at telephone number 571 - 272 - 3795. 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 Patent Center. Status information for published applications may be obtained from Patent Center. Status information for unpublished applications is available through Patent Center to authorized users only. Should you have questions about access to the USPTO patent electronic filing system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). Examiner interviews are available via a variety of formats see MPEP § 713.01. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) Form at https://www.uspto.gov/InterviewPractice. /C.R.D./ Examiner, Art Unit 2476 /AYAZ R SHEIKH/Supervisory Patent Examiner, Art Unit 2476 Application/Control Number: 18/714,709 Page 2 Art Unit: 2476 Application/Control Number: 18/714,709 Page 3 Art Unit: 2476 Application/Control Number: 18/714,709 Page 4 Art Unit: 2476 Application/Control Number: 18/714,709 Page 5 Art Unit: 2476 Application/Control Number: 18/714,709 Page 6 Art Unit: 2476 Application/Control Number: 18/714,709 Page 7 Art Unit: 2476 Application/Control Number: 18/714,709 Page 8 Art Unit: 2476 Application/Control Number: 18/714,709 Page 9 Art Unit: 2476 Application/Control Number: 18/714,709 Page 10 Art Unit: 2476 Application/Control Number: 18/714,709 Page 11 Art Unit: 2476 Application/Control Number: 18/714,709 Page 12 Art Unit: 2476 Application/Control Number: 18/714,709 Page 13 Art Unit: 2476 Application/Control Number: 18/714,709 Page 14 Art Unit: 2476
Prosecution Insights