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 .
Response to Amendment
The Amendment filed 29 December, 2025 has been entered. Claims 1-5, 7-12, and 14-22 remain pending in the application. Applicant’s amendments to the Claims have necessitated further search and consideration. Rejections under 35 USC § 103 have been updated in response to amendments. Rejections under 35 USC § 112 have also been newly raised.
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
Claims 2-5 and 7 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor regards as the invention. Each claim contains a reference to “the protocol”, however two protocols are established in independent claim 1. It is unclear which protocol these claims refer to. Examiner suggests that Applicant amends the claims to resemble claims 9-12, 14, and 16-20.
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.
Claims 1-3, 5, 8-10, 12, 15-17, 19, and 21-22 are rejected under 35 U.S.C. 103 as being obvious over Malladi et al (U.S. Patent Pub. No. 2021/0311739), hereinafter referred to as Malladi, in combination with Vantrease (U.S. Patent No. 10,402,329), Satish et al (U.S. Patent No. 10,365,827), hereinafter referred to as Satish, and Guim Bernat et al (U.S. Patent Pub. No. 2022/0014588), hereinafter referred to as G-B.
In regard to claim 1, Malladi teaches a method comprising: receiving, at a computational device, a command, wherein the computational device comprises at least one computational resource and a memory (Paragraph 0005, lines 1-4 disclose function-in-memory circuits (110 in Fig. 2A) which receive instructions over a CXL protocol (Paragraph 0024); Fig. 4B shows FIM circuits include processing components and SRAM; Fig. 4A item 420 shows this is a single device); performing, using the at least one computational resource, based on the command, a computational operation, wherein the computational operation generates a result (Paragraph 0005, lines 6-9); and sending, from the computational device, using a protocol of a communication interface, the result (Paragraph 0014) and accessing, using the protocol, at least a portion of the memory (¶ 0057-0058 CXL protocol is used to access memory module 450 through interface 445);
Malladi does not teach storing, in the at least a portion of the memory, the command, however Satish discloses submission queues inside I/O controllers which store, in at least a portion of the memory, a command (Column 10, line 60 to Column 11, line 4), achieving the claimed limitation when implemented in the SRAM (Column 6, lines 42-50 I/O controllers utilize SRAM for storage) of the CXL interface circuit of the FIM circuits disclosed in Malladi, which utilize the CXL protocol for host communication (Malladi Paragraph 0059). It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine the disclosure of Satish in order to store commands and to improve storage array performance (Column 1, lines 61-63).
The previously cited references do not teach an embodiment wherein the communication interface is configured to modify a copy of data stored at a first location based on modifying the data stored at a second location. However, Vantrease discloses an arbitrated interconnect 114 in Fig 2D which can write a modified copy of a cache line back to memory when indicated (Column 9, lines 50-54), achieving the claimed limitation. It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine the disclosure of Vantrease in order to all for coherent data updates and provide a "minimally invasive method" to block transactions on unmodified cache data (Column 3, lines 29-33).
The previously cited references do not teach using an additional protocol for i.e. coherent writebacks/writethroughs, however G-B teaches a connected network of computational devices over CXL (¶ 0024) utilizing multiple CXL protocols (¶ 0024, lines 9-13). This includes the CXL.io protocol for memory access (¶ 0025, lines 1-7) and the CXL.mem or CXL.cache protocols for coherence (¶ 0026, lines 1-11). A person of ordinary skill would be able to combine these protocols in the CXL interface of Malladi in order to use differing protocols for memory access and for cache coherence. It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine the disclosure of G-B in order to separately handle certain memory access transactions and avoid the increased latency of multiple handshake operations in other protocol implementations (¶ 0022).
As for claim 2, the previously cited references teach the method of claim 1. Additionally, Malladi Paragraph 0048, describes a process by which the result of an operation is sent to memory. The interface of Malladi can be configured to use a protocol such as DDR2, DDR3, etc. (i.e. memory access protocol; Paragraph 0022), and storing the result in memory would functionally require use of one of the specified memory access protocols (see Fig. 2B, DRAM connected to FIM modules), achieving the claimed limitation.
As for claim 3, the previously cited references teach the method of claim 1. Additionally, Malladi teaches an embodiment wherein: the protocol comprises a cache protocol; and the sending the result is performed using the cache protocol (Paragraph 0014, lines 4-5), achieving the claimed limitation.
As for claim 5, the previously cited references teach the method of claim 1. Additionally, Malladi teaches an embodiment wherein the command is received using the protocol (Paragraph 0024), achieving the claimed limitation.
In regard to claim 8, Malladi discloses a physical apparatus (see Figs. 2A-2C) which carries out methods taught in the disclosure. As for the remaining limitations of claim 8, Applicant is directed to the rejection of claim 1 above as the claims share limitations and are therefore rejected on shared rationale. Additionally, while the nominal "first" and "second" protocols are switched in claim 8, the rationale of claim 1 would still address these limitations as they do not change the actual function of the apparatus.
In regard to claim 9, Applicant is directed to the rejection of claim 2 above as the claims share limitations and are therefore rejected on shared rationale.
In regard to claim 10, Applicant is directed to the rejection of claim 3 above as the claims share limitations and are therefore rejected on shared rationale. Additionally, the cited reference G-B in claim 1 includes the use of CXL.mem or CXL.cache for coherence (¶ 0026, lines 1-11), meaning a person of ordinary skill in the art would be capable of using the other, non-coherent protocol for typical memory transactions. Therefore, using CXL.cache to send a result (i.e. some normal operation of the cache protocol) and CXL.mem for coherence would achieve the claimed limitation.
In regard to claim 12, Applicant is directed to the rejection of claim 5 above as the claims share limitations and are therefore rejected on shared rationale. Additionally, G-B teaches communication using CXL.io (¶ 0025) as well as CXL.cache (¶ 0026) using requests and responses between devices, meaning both protocols can be used to receive commands, achieving the claimed limitation.
In regard to claim 15, Applicant is directed to the rejections of claims 1 and 8 above as the claims share limitations and are therefore rejected on shared rationale.
In regard to claim 16, Applicant is directed to the rejection of claim 9 above as the claims share limitations and are therefore rejected on shared rationale. While claim 16 specifies receiving at the host (control circuit) over a protocol, this is functionally captured by the addressed limitation of sending to the host over a protocol, achieving the claimed limitation.
In regard to claim 17, Applicant is directed to the rejection of claim 10 above as the claims share limitations and are therefore rejected on shared rationale. While claim 17 specifies receiving at the host (control circuit) over a protocol, this is functionally captured by the addressed limitation of sending to the host over a protocol, achieving the claimed limitation.
In regard to claim 19, Applicant is directed to the rejection of claim 12 above as the claims share limitations and are therefore rejected on shared rationale. While claim 19 specifies receiving at the host (control circuit) over a protocol, this is functionally captured by the addressed limitation of sending to the host over a protocol, achieving the claimed limitation.
In regard to claim 21, the previously cited references teach the method of claim 1. Additionally, Satish teaches command queues to store commands in a controller (Column 10, line 60 to Column 11, line 1) wherein commands are retrieved from (i.e. detected in) the queue (Column 11, lines 1-7), achieving the claimed limitation.
As for claim 22, the previously cited references teach the apparatus of claim 8. They do not teach the remaining limitations of claim 22. Additionally, Satish teaches completion queues to store completions in a controller (Column 11, lines 8-9) wherein completed commands are retrieved from (i.e. detected in) the queue (Column 11, lines 9-11), achieving the claimed limitation.
Claims 4, 11, and 18 are rejected under 35 U.S.C. 103 as being obvious over Malladi, Vantrease, Satish, G-B, and Johar et al (U.S. Patent Pub. No. 2015/0356019), hereinafter referred to as Johar.
As for claim 4, the previously cited references teach the method of claim 1. They do not teach the remaining limitations of claim 4. However, Johar teaches allocating, using the protocol, additional memory at the computational device; and storing, in the additional memory, at least a portion of the result. Paragraph 0016, lines 24-28 disclose a write allocate policy which achieves the claimed limitation. Paragraph 0006, lines 24-26 explain that the write allocate policy stores a local copy of accessed data, i.e. allocating and storing the result in additional memory that was not addressed originally. It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine the disclosure of Johar in order to cache accessed items (Paragraph 0016, lines 27-28) which would reduce access latency as known in the art.
In regard to claim 11, Applicant is directed to the rejection of claim 4 above as the claims share limitations and are therefore rejected on shared rationale. Additionally, the cited disclosure of Johar concerning a cache unit could be combined by one of ordinary skill in the art with any one of the various CXL protocols used by previously cited references for cache-type transactions (e.g. CXL.cache), achieving the claimed limitation.
In regard to claim 18, Applicant is directed to the rejection of claim 11 above as the claims share limitations and are therefore rejected on shared rationale.
Claims 7, 14, and 20 are rejected under 35 U.S.C. 103 as being obvious over Malladi, Vantrease, Satish, G-B, and Chirca et al (U.S. Patent Pub. No. 2022/0156192), hereinafter referred to as Chirca.
As for claim 7, the previously cited references teach the method of claim 1. They do not teach the remaining limitations of claim 7. However, Chirca discloses a data routing unit (DRU 300 in Fig. 3) which includes an MMU 328 for address translation (Paragraph 0041, lines 3-6; e.g. computational device which produces and sends a result after an operation of a computational resource (address translation by MMU)). The DRU is connected to at least two different interfaces with differing protocols (direct write of a MMR e.g. DMA, and a PSI-L interface; Paragraph 0031, lines 14-17) and can receive commands from one or more of said interfaces (Paragraph 0031, lines 13-14). When combined with the disclosure of Malladi, the claimed limitation is achieved. It would have been obvious to one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine the disclosure of Chirca in order to ensure responsiveness of processing networks (Paragraph 0016).
In regard to claim 14, Applicant is directed to the rejection of claim 7 above as the claims share limitations and are therefore rejected on shared rationale. Additionally, G-B teaches requests and responses over CXL.io, CXL.mem, and CXL.cache (¶ 0025-0026), meaning a third unused protocol could be used with the multiple interfaces in the disclosure of Chirca (¶ 0031) to maintain functionality and achieve the claimed limitation.
In regard to claim 20, Applicant is directed to the rejection of claim 14 above as the claims share limitations and are therefore rejected on shared rationale. While claim 20 specifies receiving at the host (control circuit) over a protocol, this is functionally captured by the addressed limitation of sending to the host over a protocol, achieving the claimed limitation.
Response to Arguments
Applicant's arguments filed 29 December, 2025 have been fully considered. Remarks directed to amended claims and the suitability of reference Chirca in teaching additional limitations (see page 7) were persuasive. Following further search and consideration, new reference Guim Bernat was found to teach the usage of additional protocols, as shown in the updated rejections of the claims. Therefore, the claims have been rejected under 35 USC § 103 on new grounds.
Conclusion
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.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ZAKARIA MOHAMMED BELKHAYAT whose telephone number is (571)270-0472. The examiner can normally be reached Monday thru Thursday 7:30AM-5:30PM 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, Reginald Bragdon can be reached at (571)272-4204. 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.
/ZAKARIA MOHAMMED BELKHAYAT/Examiner, Art Unit 2139
/REGINALD G BRAGDON/Supervisory Patent Examiner, Art Unit 2139