DETAIL ACTION
Notice of Pre-AIA or AIA Status
1. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
2. This office action is in response to the communication(s) filed 08/14/2026. There are a total of 20 claims pending in the application; no claims have been amended, canceled, or added.
Response to Remarks
Applicant’s arguments have been fully considered and they are persuasive. Regarding rejections of independent claims 1, 12, and 17, Pages 8-12 of the Remarks uses Fig. 3 and portions of the specification to describe/map relevant components recited in the claims. Thus, Rejections of claims under 35 USC §112(a), first paragraph are withdrawn. The rejection under the non-statutory double patenting is maintained.
INFORMATION CONCERNING CLAIMS:
Double Patenting
3. 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.
4. Claims 1-7 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 9, and 13 of U.S. Patent No. 12,197,331 B2 (hereinafter “the patent”). Although the claims at issue are not identical, they are not patentably distinct from each other because:
For example, the claim 1 of current patent recites a set of data identifies a set of cache entries while claim 1 of the patent recite a set of addresses associated with a cache entries. The claim of the instant application recites L1 cache and L2 cache while claims of the patent recite first level cache and second level cache. Claim 3 of instant patent recites the first cache level is a level one data (L1D) cache level while claim of the patent recite first level cache, which may comprise first level data cache. The Examiner respectfully submits these minor differences do not make the claims patentably distinct from each other
5. Claims 1-7 of the instant application are compared with claims 1, 9, and 13 of the patent in the following table:
US Patent 12,197,331 B2
US Application 19/017,952
1. An integrated circuit device comprising:
a processor core;
a cache system coupled to the processor core that includes:
a first cache subsystem that includes:
a first cache controller coupled to the processor core;
a main cache memory coupled to the first cache controller and configured to store a first set of cache entries; and a victim cache memory coupled to the first cache controller and configured to store a second set of cache entries; and
a second cache subsystem that includes:
a second cache controller coupled to the first cache controller;
a shadow main cache memory coupled to the second cache controller and configured to store a first set of addresses associated with the first set of cache entries;
and a shadow victim cache memory coupled to the second cache controller and configured to store a second set of addresses associated with the second set of cache entries.
Claim 9:
wherein the second cache controller is configured to: receive a read request for a set of data; determine whether the read request is associated with a hit in either the first set of addresses or the second set of addresses; and
based on the read request being associated with a hit, provide a snoop request for the set of data to the first cache controller.
1. A circuit device comprising:
a processor core;
a first cache controller coupled to the processor core, wherein the first cache controller is associated with a first cache level;
a first cache memory coupled to the first cache controller, wherein: the first cache memory is associated with the first cache level; and the first cache memory is configured to store a set of cache entries;
a second cache controller coupled to the first cache controller, wherein the second cache controller is associated with a second cache level; and
a memory coupled to the second cache controller and configured to store a set of data that identifies the set of cache entries stored in the first cache memory;
wherein the second cache controller is configured to: receive a first request; determine, based on the set of data, whether the first request is a hit in the set of cache entries stored in the first cache memory; and
based on the first request being a hit in the set of cache entries, provide a second request associated with the first request to the first cache controller.
13. A method comprising: storing a set of cache entries in a cache memory of a first level cache; storing a set of identifiers associated with the set of cache entries in a shadow cache memory of a second level cache …
2. The circuit device of claim 1,
wherein: the first cache level is a level one (L1) cache level; and the second cache level is a level two (L2) cache level.
13. A method comprising: storing a set of cache entries in a cache memory of a first level cache; …
3.The circuit device of claim 2,
wherein the first cache level is a level one data (L1D) cache level.
9. The integrated circuit device of claim 1, wherein the second cache controller is configured to: receive a read request for a set of data;
determine whether the read request is associated with a hit in either the first set of addresses or the second set of addresses; and based on the read request being associated with a hit, provide a snoop request for the set of data to the first cache controller.
5. The circuit device of claim 1,
wherein: the first request is a read request; and
the second request is a snoop read request.
19. The method of claim 13 further comprising: receiving a first snoop request;
determining whether the first snoop request is associated with a hit in the set of identifiers; and based on the first snoop request being associated with a hit, providing a second snoop request for the set of data to the first level cache.
6. The circuit device of claim 5,
wherein the first request is a snoop read request.
11. The integrated circuit device of claim 1,
wherein the second cache controller is configured to: receive a write request for a first set of data;
determine whether the write request is associated with a hit in either the first set of addresses or the second set of addresses; and
based on the write request being associated with a hit,
provide a snoop and invalidate request to the first cache controller.
7. The circuit device of claim 1,
wherein: the first request is a write request; and
the second request is a snoop read and invalidate request.
Allowable Subject Matter
6. Claims 12-20 are allowed.
7. Claims 8-11 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
THIS ACTION IS MADE FINAL. 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.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to HASHEM FARROKH whose telephone number is (571)272-4193. The examiner can normally be reached Monday through Friday from 8:30 am - 5:00 pm.
If attempts to reach the examiner by telephone are unsuccessful, the examiner's supervisor, Mr. Tim Vo can be reached on (571)272-3642. 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 htto://pair-direct.uspto.gov. For questions regarding 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.
/HASHEM FARROKH/Primary Examiner, Art Unit 2138
Prosecution Insights