Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
Claim(s) 1, 2, 4-8, 11-12 and 14 is/are rejected under 35 U.S.C. 103 as being unpatentable over Yu et al (US Pub 2023/0328718), hereinafter referred as Yu in view of Ko et al (“TB PPDU Format Signaling in Trigger Frame” – IDS reference), hereinafter referred to as Ko.
Regarding claim 1, A base station [AP, see fig. 7a, 8a, 9, 11, 22], comprising:
control circuitry [control circuit within AP of fig. 7a, represented by communication apparatus 1000 in fig. 22, paragraphs 0303, 0320], which, in operation, generates a control signal for uplink transmission [generates/sends trigger signal/frame, see fig. 7a, 8a, 9,11, 19], and
transmission circuitry [transceiver 1002, configured to perform S203 of fig. 8a and fig. 22], which, in operation transmits the control signal [trigger signal/frame, see fig. 5a-6b, 7a, 8a, 9 and 11], wherein
the control signal signal [trigger signal/frame, see fig. 5a-6b, 7a, 8a, 9 and 11] contains common information [common information field, see figs. 5a, 5b, 6a, 6b, 11], including a first subfield [UL Spatial Reuse subframe 1 in the Common Information field, see figs. 5a, 5b, 6a, 6b, 7b, 8a, 11] and a second subfield [UL Spatial Reuse 2 subfield in the Common Information field, see figs. figs. 5a, 5b, 6a, 6b, 7b, 8a, 11], the first subfield and the second subfield being related to a type of the control signal [trigger type/trigger frame type subfield is present prior to first and second subfield for establishing relationship to the control signal, see fig. 5b, 6a-1, 11, ], the second subfield [UL Spatial Reuse 2 subfield in the Common Information field, see figs. figs. 5a, 5b, 6a, 6b, 7b, 8a, 11] indicating information on a version of a radio communication standard [EHT TB standard version identifier see table 3, 8, and 9] and a third subfield [EHT subfield in the trigger frame, see figs. 5a, 5b, 6a-1, 6b].
While Yu teaches in figs. 5a, 5b, 6a-1, 6b of a numerous other subfield such as a third subfield in the trigger frame and teaches in table 3, 8 and 9 of version identifier, Yu fails to explicitly teach that a third subfield configuration is varied depending on the version.
Ko teaches of common info field can include the version ID subfield and the trigger frame format is based on the Version ID subfield on slide 5. Ko further teaches on slides 6 that trigger type specifies whether the version ID subfield is present. In one example, it is determined if the version ID subfield is present based on the UL length mod 3. Thus slide 9 clearly indicates when the version ID subfield of a trigger frame indicated EHT (or beyond EHT), the Trigger frame should not include the User Info field with the AID12 subfield set to 0 or 2045. This clearly reads on the third subfield configuration setting to be varied based on the version ID subfield. Therefore, it would have been obvious to one or ordinary skills in the art prior to the effective filing date to incorporate the teachings of third subfield varying based on version as taught by Ko into the invention of Ye in order to determine the proper PPDU format to respond to a trigger frame.
Regarding claim 14, Yu teaches communication method, comprising:
generating, by a base station [AP, see fig. 7a, 8a, 9 and 11], a control signal for uplink transmission [sends trigger signal/frame, see fig. 7a, 8a, 9,11, 19]; and
transmitting, by the base station, the control signal [transceiver 1002, configured to perform S203 of fig. 8a; trigger signal/frame, see fig. 7a, 8a, 9 and 11], wherein
the control signal signal [trigger signal/frame, see fig. 5a-6b, 7a, 8a, 9 and 11] contains common information [common information field, see figs. 5a, 5b, 6a, 6b, 11], including a first subfield [UL Spatial Reuse subframe 1 in the Common Information field, see figs. 5a, 5b, 6a, 6b, 7b, 8a, 11] and a second subfield [UL Spatial Reuse 2 subfield in the Common Information field, see figs. figs. 5a, 5b, 6a, 6b, 7b, 8a, 11], the first subfield and the second subfield being related to a type of the control signal [trigger type/trigger frame type subfield is present prior to first and second subfield for establishing relationship to the control signal, see fig. 5b, 6a-1, 11, ], the second subfield [UL Spatial Reuse 2 subfield in the Common Information field, see figs. figs. 5a, 5b, 6a, 6b, 7b, 8a, 11] indicating information on a version of a radio communication standard [EHT TB standard version identifier see table 3, 8, and 9] and a third subfield [EHT subfield in the trigger frame, see figs. 5a, 5b, 6a-1, 6b].
While Yu teaches in figs. 5a, 5b, 6a-1, 6b of a numerous other subfield such as a third subfield in the trigger frame and teaches in table 3, 8 and 9 of version identifier, Yu fails to explicitly teach that a third subfield configuration is varied depending on the version.
Ko teaches of common info field can include the version ID subfield and the trigger frame format is based on the Version ID subfield on slide 5. Ko further teaches on slides 6 that trigger type specifies whether the version ID subfield is present. In one example, it is determined if the version ID subfield is present based on the UL length mod 3. Thus slide 9 clearly indicates when the version ID subfield of a trigger frame indicated EHT (or beyond EHT), the Trigger frame should not include the User Info field with the AID12 subfield set to 0 or 2045. This clearly reads on the third subfield configuration setting to be varied based on the version ID subfield. Therefore, it would have been obvious to one or ordinary skills in the art prior to the effective filing date to incorporate the teachings of third subfield varying based on version as taught by Ko into the invention of Ye in order to determine the proper PPDU format to respond to a trigger frame.
Regarding claim 2, Yu teaches wherein the information on the version is associated with a type of the control signal [see Yu, paragraphs 0296-0300, see table 3, 9, paragraph 0142, 0238, where version is associated with ETH or HE control/trigger signal/frame].
Regarding claim 4, Yu teaches further comprising reception circuitry [see fig. 20 transceiver unit 21 of a STA of fig. 7a, 8a], which, in operation, receives a response signal for the control signal based on the version associated with the type [see paragraph 0076, 0307, 0273, where response signal is associated with ETH or HE trigger frame].
Regarding claim 5, Yu teaches wherein the control circuitry [control circuit within AP of fig. 7a, represented by communication apparatus 1000 in fig. 22, paragraphs 0303, 0320] and the third subfield [ETH subfield] being different from the first subfield [UL Spatial Reuse 1] and second subfield [UL Spatial Reuse 2] [see figs. 10A and 10B, 6a-8a, and paragraph 0177 of a reserved field in a common information field of a trigger frame that is used for setting an uplink EHT PPDU bandwidth subfield, and HE/EHT subfield indicating an EEHT STA to send and EHT TB PPDU or an TB PPDU along with tables 3 and 9, paragraph 0142, 0238 version identifier, i.e. EHT or HE]. While Yu teaches in figs. 5a, 5b, 6a-1, 6b of a numerous other subfield such as a third subfield in the trigger frame and teaches in table 3, 8 and 9 of version identifier, Yu fails to explicitly teach that a third subfield configuration is varied depending on the version.
Ko teaches of common info field can include the version ID subfield and the trigger frame format is based on the Version ID subfield on slide 5. Ko further teaches on slides 6 that trigger type specifies whether the version ID subfield is present. In one example, it is determined if the version ID subfield is present based on the UL length mod 3. Thus slide 9 clearly indicates when the version ID subfield of a trigger frame indicated EHT (or beyond EHT), the Trigger frame should not include the User Info field with the AID12 subfield set to 0 or 2045. This clearly reads on the third subfield configuration setting to be varied based on the version ID subfield. Therefore, it would have been obvious to one or ordinary skills in the art prior to the effective filing date to incorporate the teachings of third subfield varying based on version as taught by Ko into the invention of Ye in order to determine the proper PPDU format to respond to a trigger frame.
Regarding claim 6, Yu teaches wherein the third subfield includes at least one of a UL Space Time Block Coding (STBC) subfield, a UL Spatial Reuse subfield, a Doppler subfield, and/or a Reserved subfield [see fig. 7b, 10a-A-b that has UL Spatial Reuse subfield or Doppler or EHT reserved subfield]. .
Regarding claim 7, Yu teaches wherein the control circuitry [control circuit within AP of fig. 7a, represented by communication apparatus 1000 in fig. 22, paragraphs 0303, 0320] configures the third subfield when the version is Extreme High Throughput (EHT) [see fig. 10A and 10B, 6a-8a ,type of control/trigger frame being EHT].
Regarding claim 8, Yu teaches wherein the transmission circuitry [transceiver 1002, configured to perform S203 of fig. 8a] transmits information on the type [trigger frame EHT TB PPDU type, see fig. 7a-8a] using both the first subfield and the second subfield [see fig. 10A and 10B, where UL EHT Spatial Reuse 1 is the first subfield and UL EHT Spatial Reuse 2 is a second subfield].
Regarding claim 11, Yu teaches wherein the second subfield is configured in a field in the control signal, the field is being interpreted as a Reserved field when the version is HE [see figs. 5a, 5b, 6a-1, 6b and paragraphs 0176-0177, where second subfield is a reserved field when the version is HE TB PPDU or spatial reuse].
Regarding claim 12, Yu teaches wherein the control circuitry [control circuit within AP of fig. 7a, represented by communication apparatus 1000 in fig. 22, paragraphs 0303, 0320] information on the type of the control signal for a terminal whose version corresponds to High Efficiency Throughput (EHT) using both the first subfield and the second subfield [see fig. 10A and 10B, where UL EHT Reuse 1 is the first subfield and UL EHT Spatial Reuse 2 is a second subfield].
Response to Arguments
Applicant’s arguments with respect to claim(s) have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to CHIRAG SHAH whose telephone number is 571-272-3144. The examiner can normally be reached Monday-Friday 6AM-4PM.
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.
The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/CHIRAG G SHAH/Supervisory Patent Examiner, Art Unit 2477
Prosecution Insights