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 Arguments
Applicant’s arguments, filed 8/21/2026, with respect to 35 U.S.C. 112, 102 and 103 rejections have been fully considered and are persuasive. The rejections have been withdrawn.
Claim Rejections - 35 USC § 112
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention.
Claims 1-15 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention. The originally filed specification does not support “and in response to determining that the user information of the group of users requires cloud computing, aggregating the user information of the group of users and transmitting the aggregated user information of the at least one user to a computing server for processing the aggregated user information to generate graphics-related results for the same channel.”
The originally filed specification discloses “This collection of user information includes at least one of object states, visual effect data, or requests related to the game. The collected states and data are then transmitted to a state synchronization block 220. Within the state synchronization block 220, the states and data from the client device 120 are synchronized (at 203). This synchronization involves aggregating information from multiple users, if necessary, for a particular frame or frames. Optionally, the state synchronization block 220 may include a data conversion block 221, which compares and converts the received data into a same format to ensure compatibility (at 204). The synchronized states and data are subsequently sent to the cloud server 130 (at 205).”, see page 18, originally filed specification. [This disclosure does not support --- in response to determining that the user information of the group of users requires cloud computing, aggregating the user information of the group of users and transmitting the aggregated user information of the at least one user to a computing server for processing the aggregated user information to generate graphics-related results for the same channel.---]
The specification further discloses “Each unit may be implemented as a physical
hardware component, a software process, or a combination of both, operating within a single server. This modular architecture allows for flexible deployment and efficient resource management. In addition, if the three services 310, 320, 330 are provided in the same server, the state synchronization service 310 may still function as a relay between the client devices and the other two services, so that each time when the state synchronization service 310 receives states and/or data, it can synchronize them, ensuring that all user information is accurately aggregated and processed. This relay function enables the system to handle complex multi-user interactions and rendering/computation tasks efficiently.”, specification, pages 24, last paragraph and 25, first paragraph.
Also see, specification page 27, lines 12-20.
Allowable Subject Matter
Claims 1-15 are allowable over the prior art.
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 GLENTON B BURGESS whose telephone number is (571)272-3949. The examiner can normally be reached Monday-Friday, 8:30 am - 5:00 pm.
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.
/GLENTON B BURGESS/Supervisory Patent Examiner, Art Unit 2454
