DETAILED ACTION
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 § 112
The following is a quotation of 35 U.S.C. 112(d):
(d) REFERENCE IN DEPENDENT FORMS.—Subject to subsection (e), a claim in dependent form shall contain a reference to a claim previously set forth and then specify a further limitation of the subject matter claimed. A claim in dependent form shall be construed to incorporate by reference all the limitations of the claim to which it refers.
The following is a quotation of pre-AIA 35 U.S.C. 112, fourth paragraph:
Subject to the following paragraph [i.e., the fifth paragraph of pre-AIA 35 U.S.C. 112], a claim in dependent form shall contain a reference to a claim previously set forth and then specify a further limitation of the subject matter claimed. A claim in dependent form shall be construed to incorporate by reference all the limitations of the claim to which it refers.
Claim 17 is rejected under 35 U.S.C. 112(d) or pre-AIA 35 U.S.C. 112, 4th paragraph, as being of improper dependent form for failing to further limit the subject matter of the claim upon which it depends, or for failing to include all the limitations of the claim upon which it depends. Claim 17 recites “wherein the response data comprises a converted Bluetooth (BT) clock and a clock accuracy value, and wherein the clock synchronization request comprises a request for an ultra-wideband (UWB) clock value”, which consists of identical claim language as lines 7-9 of its parent claim 12. Applicant may cancel the claim(s), amend the claim(s) to place the claim(s) in proper dependent form, rewrite the claim(s) in independent form, or present a sufficient showing that the dependent claim(s) complies with the statutory requirements.
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 1-20 rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-19 of U.S. Patent No. 12,035,266 B2. Although the claims at issue are not identical, they are not patentably distinct from each other because all claimed features of the current Application are disclosed in US 12,035,266 B2.
Current Application
US 12,035,266 B2
1. A method for wireless communication comprising: receiving a clock synchronization request over a wireless communication link from a remote device; generating response data to respond to the clock synchronization request, the response data being configured for synchronizing a remote clock of the remote device and a local clock of a device; wherein the response data comprises a converted Bluetooth (BT) clock value and a clock accuracy value, and wherein the clock synchronization request comprises a request for an ultra-wideband (UWB) clock value; and preparing, for transmission to the remote device, the response data to the clock synchronization request.
1. A method comprising: receiving a clock synchronization request, the request being received over a wireless communication link from a remote device; generating, by at least one processor, response data to respond to the synchronization request, the response data being configured for synchronizing a remote clock of the remote device and a local clock of a device; wherein generating the response data comprises, prior to receiving the request, precomputing the response data to respond to the synchronization request, the precomputed response data comprising L2CAP layer data; and preparing, for transmission to the remote device, the response data to the synchronization request.
6. The method of claim 1, wherein the response data comprises a converted Bluetooth (BT) clock value and a clock accuracy value, and wherein the synchronization request comprises a request for an ultra-wideband (UWB) clock value.
2. The method of claim 1, wherein at least one processor is configured for generating the response data without accessing an application processor (AP) of the device.
2. The method of claim 1, wherein the at least one processor is configured for generating the response data without accessing an application processor (AP) of the device.
3. The method of claim 1, further comprising: maintaining an application processor (AP) of the device in a hibernation state while generating the response data, wherein the AP of the device consumes a reduced power in the hibernation state relative to an increased power consumed during an active state in which the AP is enabled to process data.
3. The method of claim 1, further comprising: maintaining an application processor (AP) of the device in a hibernation state while generating the response, wherein the AP of the device consumes a reduced power in the hibernation state relative to an increased power consumed during an active state in which the AP is enabled to process data.
4. The method of claim 1, wherein a firmware layer of the device comprises a Logical Link Control and Adaptation Protocol L2CAP layer.
4. The method of claim 1, wherein a firmware layer associated with the at least one processor comprises a Logical Link Control and Adaptation Protocol L2CAP layer.
5. The method of claim 1, wherein generating the response data to respond to the clock synchronization request comprises: obtaining, from the request, a first clock value for the remote clock; accessing a second clock value for the local clock corresponding to receiving the request from the remote device; determining an adjustment value for the first clock value of the remote clock, the second clock value of the local clock, or both the first clock value and the second clock value; and generating the response data representing the determined adjustment, the response data configured to enable the remote device to synchronize the remote clock with the local clock.
5. The method of claim 1, wherein generating the response data to respond to the synchronization request comprises: obtaining, from the request, a first clock value for the remote clock; accessing a second clock value for the local clock corresponding to receiving the request from the remote device; determining an adjustment for a first frequency of the remote clock, a second frequency value of the local clock, or both the first frequency and the second frequency; and generating data representing the determined adjustment, the response data configured to enable the remote device to synchronize the remote clock with the local clock.
6. The method of claim 1, wherein generating the response data comprises, prior to receiving the request, precomputing the response data to respond to the clock synchronization request, the precomputed response data comprising L2CAP layer data.
1. A method comprising: receiving a clock synchronization request, the request being received over a wireless communication link from a remote device; generating, by at least one processor, response data to respond to the synchronization request, the response data being configured for synchronizing a remote clock of the remote device and a local clock of a device; wherein generating the response data comprises, prior to receiving the request, precomputing the response data to respond to the synchronization request, the precomputed response data comprising L2CAP layer data; and preparing, for transmission to the remote device, the response data to the synchronization request.
7. The method of claim 1, further comprising: generating Bluetooth (BT) credit data, the BT credit data for use in controlling transmission to the remote device while an application processor (AP) is in hibernation; sending the BT credit data to a firmware layer associated with at least one processor that generates the response data; and causing the AP to initiate hibernation.
7. The method of claim 1, further comprising: generating Bluetooth (BT) credit data, the BT credit data for use in controlling transmission to the remote device while an application processor (AP) is in hibernation; sending the BT credit data to firmware layer associated with the at least one processor; and causing the AP to initiate hibernation.
8. The method of claim 1, wherein the wireless communications link comprises a Bluetooth link.
8. The method of claim 1, wherein the wireless communications link comprises a Bluetooth link.
9. The method of claim 8, wherein the Bluetooth link comprises a Bluetooth Low Energy Long Range (LE-LR) link or a Bluetooth Low Energy (LE) Coded Physical Layer (PHY) link.
9. The method of claim 8, wherein the Bluetooth link comprises a Bluetooth Low Energy Long Range (LE-LR) link or a Bluetooth Low Energy (LE) Coded Physical Layer (PHY) link.
10. The method of claim 1, wherein the wireless communications link comprises an ultra-wideband (UWB) link.
10. The method of claim 8, wherein the wireless communications link comprises an ultra-wideband (UWB) link.
11. The method of claim 1, wherein the remote device comprises a vehicle.
11. The method of claim 1, wherein the remote device comprises a vehicle.
12. An apparatus comprising processing circuitry: configured to perform operations comprising: receiving data representing a clock synchronization request from a remote device; generating response data to respond to the clock synchronization request, the response data being configured for synchronizing a remote clock of the remote device and a local clock; wherein the response data comprises a converted Bluetooth (BT) clock value and a clock accuracy value, and wherein the clock synchronization request comprises a request for an ultra-wideband (UWB) clock value; and preparing, for transmission to the remote device, the response data to the clock synchronization request.
12. An apparatus comprising processing circuitry configured to perform operations comprising: receiving data representing a clock synchronization request from a remote device; generating response data to respond to the synchronization request, the response data being configured for synchronizing a remote clock of the remote device and a local clock; wherein generating the response data comprises, prior to receiving the request, precomputing the response data to respond to the synchronization request, the precomputed response data comprising L2CAP layer data; and preparing, for transmission, to the remote device, the response data to the synchronization request.
17. The apparatus of claim 12, wherein the response data comprises a converted Bluetooth (BT) clock value and a clock accuracy value, and wherein the synchronization request comprises a request for an ultra-wideband (UWB) clock value.
13. The apparatus of claim 12, wherein the processing circuitry is configured for generating the response data without accessing an application processor (AP).
13. The apparatus of claim 12, wherein the processing circuitry is configured for generating the response data without accessing an application processor (AP).
14. The apparatus of claim 12, the operations further comprising: maintaining an application processor (AP) in a hibernation state while generating the response data, wherein the AP consumes a reduced power in the hibernation state relative to an increased power consumed during an active state in which the AP is enabled to process data.
14. The apparatus of claim 12, the operations further comprising: maintaining an application processor (AP) in a hibernation state while generating the response, wherein the AP consumes a reduced power in the hibernation state relative to an increased power consumed during an active state in which the AP is enabled to process data.
15. The apparatus of claim 12, wherein a firmware layer associated with the processing circuitry comprises a Logical Link Control and Adaptation Protocol L2CAP layer.
15. The apparatus of claim 12, wherein a firmware layer associated with the processing circuitry comprises a Logical Link Control and Adaptation Protocol L2CAP layer.
16. The apparatus of claim 12, wherein generating the response data to respond to the clock synchronization request comprises: obtaining, from the request, a first clock value for the remote clock; accessing a second clock value for the local clock corresponding to receiving the request from the remote device; determining an adjustment value for the first clock value of the remote clock, the second clock value of the local clock, or both the first clock value and the second clock value; and generating the response data representing the determined adjustment, the response data configured to enable the remote device to synchronize the remote clock with the local clock.
16. The apparatus of claim 12, wherein generating the response data to respond to the synchronization request comprises: obtaining, from the request, a first clock value for the remote clock; accessing a second clock value for the local clock corresponding to receiving the request from the remote device; determining an adjustment for a first frequency of the remote clock, a second frequency value of the local clock, or both the first frequency and the second frequency; and generating response data representing the determined adjustment, the response data configured to enable the remote device to synchronize the remote clock with the local clock.
17. The apparatus of claim 12, wherein the response data comprises a converted Bluetooth (BT) clock value and a clock accuracy value, and wherein the clock synchronization request comprises a request for an ultra-wideband (UWB) clock value.
17. The apparatus of claim 12, wherein the response data comprises a converted Bluetooth (BT) clock value and a clock accuracy value, and wherein the synchronization request comprises a request for an ultra-wideband (UWB) clock value.
18. One or more processors comprising circuitry configured to perform operations comprising: decoding data representing a clock synchronization request from a remote device; encoding response data to respond to the clock synchronization request, the response data being configured for synchronizing a remote clock of the remote device and a local clock; wherein generating the response data comprises, prior to receiving the clock synchronization request, precomputing the response data to respond to the clock synchronization request, the precomputed response data comprising L2CAP layer data; and preparing, for transmission to the remote device, the response data to the clock synchronization request.
18. One or more non-transitory, computer-readable storage media having instructions stored thereon, that when executed by one or more processors, cause the one or more processors to perform operations comprising: receiving data representing a clock synchronization request from a remote device; generating response data to respond to the synchronization request, the response data being configured for synchronizing a remote clock of the remote device and a local clock; and preparing, for transmission to the remote device, the response data to the synchronization request, wherein the response data comprises a converted Bluetooth (BT) clock value and a clock accuracy value, and wherein the synchronization request comprises a request for an ultra-wideband (UWB) clock value.
19. The one or more non-transitory, computer-readable storage media of claim 18, wherein generating the response data comprises, prior to receiving the request, precomputing the response data to respond to the synchronization request, the precomputed response data comprising L2CAP layer data.
19. The one or processors of claim 18, wherein the response data comprises a converted Bluetooth (BT) clock value and a clock accuracy value, and wherein the synchronization request comprises a request for an ultra-wideband (UWB) clock value.
18. One or more non-transitory, computer-readable storage media having instructions stored thereon, that when executed by one or more processors, cause the one or more processors to perform operations comprising: receiving data representing a clock synchronization request from a remote device; generating response data to respond to the synchronization request, the response data being configured for synchronizing a remote clock of the remote device and a local clock; and preparing, for transmission to the remote device, the response data to the synchronization request, wherein the response data comprises a converted Bluetooth (BT) clock value and a clock accuracy value, and wherein the synchronization request comprises a request for an ultra-wideband (UWB) clock value.
20. The one or processors of claim 18, the operations further comprising: maintaining an application processor (AP) in a hibernation state while generating the response data, wherein the AP consumes a reduced power in the hibernation state relative to an increased power consumed during an active state in which the AP is enabled to process data.
14. The apparatus of claim 12, the operations further comprising: maintaining an application processor (AP) in a hibernation state while generating the response, wherein the AP consumes a reduced power in the hibernation state relative to an increased power consumed during an active state in which the AP is enabled to process data.
As shown above, all of the claimed features of the current application are disclosed in the claims of US 12,035,266 B2 that are patentably identical (shown in bold) or almost identical (shown in italic) in the above table. Claims 1-20 of the current Application must therefore be rejected under double-patenting rejections.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Anvari (US 11,250,696) discloses synchronization communication between two IoT devices using Bluetooth or WiFi (Fig. 10D) as pertain to claims 1, 5, 8, 11, 12, 16 and 18 of the current Application.
Bhat Noojady Krishna (US 10,771,294) disclose synchronization communication using a firmware layer associated with the mobile device (abstract, column s 18-19) as pertain to claims 1-3, 12-14 and 18 of the current Application.
Kuang (US 2018/0083884) discloses the use of L2CAP in the BLUETOOTH upper layer protocol data exchange (paragraph [0253]) as pertain to claims 4 and 15 of the current Application.
Su (US 2023/0071506) discloses a format of a Bluetooth packet of a Low Energy coded Physical Layer ink (paragraph [0021]) as pertain to claim 9 of the current application.
Van Hecke (US 2023/0072580) discloses clock synchronization using wireless communication relating to Ultra-wideband (paragraph [0001]) as pertain to claim 10 of the current Application.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JUTAI KAO whose telephone number is (571)272-9719. The examiner can normally be reached Monday-Friday 8:00-17:00 EST.
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, Kwang Yao can be reached at (571)272-3182. 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.
/JUTAI KAO/Primary Examiner, Art Unit 2473
Prosecution Insights