Prosecution Insights
Last updated: May 29, 2026
Application No. 18/854,130

UPDATE OF CONFIGURATIONS

Non-Final OA §103§OTHER
Filed
Oct 04, 2024
Priority
Apr 26, 2022 — FR 2203891 +1 more
Examiner
PHAN, RAYMOND NGAN
Art Unit
2175
Tech Center
2100 — Computer Architecture & Software
Assignee
Streamwide
OA Round
1 (Non-Final)
94%
Grant Probability
Favorable
1-2
OA Rounds
6m
Est. Remaining
90%
With Interview

Examiner Intelligence

Grants 94% — above average
94%
Career Allowance Rate
966 granted / 1030 resolved
+38.8% vs TC avg
Minimal -4% lift
Without
With
+-3.9%
Interview Lift
resolved cases with interview
Fast prosecutor
2y 1m
Avg Prosecution
23 currently pending
Career history
1052
Total Applications
across all art units

Statute-Specific Performance

§103
6.8%
-33.2% vs TC avg
§102
4.5%
-35.5% vs TC avg
§112
0.8%
-39.2% vs TC avg
Black line = Tech Center average estimate • Based on career data from 1030 resolved cases

Office Action

§103 §OTHER
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 . This application has been examined. Claims 11-20 are pending. Claims 1-11 are cancelling. The Group and/or Art Unit location of your application in the PTO has changed. To aid in correlating any papers for this application, all further correspondence regarding this application should be directed to Group Art Unit 2175. Specification The title of the invention is not descriptive. A new title is required that is clearly indicative of the invention to which the claims are directed. 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 t which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. Claims 13, 17, 19-20 are rejected under AIA 35 U.S.C. § 103 as being unpatentable over Etchegoyen (US Pub No. 2010/0333081) in view of Agarwal et al. (US No. 10,783,235). In order to expedite and avoid piecemeal prosecution, the following rejection is made to the extent that the claims are understood, by considering those elements which are understood and interpreting their function in a manner which is consistent with the recited goals of the claims, and then applying the best available art. The examiner relies on the entire teachings of Etchegoyen and Agarwal references; the applicant should carefully consider the entire teachings of the above-mentioned references to better understand the examiner’s position. In regard to claim 13, 17, 19-20, Etchegoyen discloses a computer program comprising instructions for implementing the method (see ¶ 73), a terminal configured for implementing a method (see ¶ 73), a non-transitory computer-readable storage medium in which is stored a program for implementing the method (see ¶ 73), a configuration method implemented by a terminal (item 100 of figure 1) capable of communicating with a server (item 110 and/or item 120 of figure 1), a back-end application and a corresponding front-end application being installed respectively on the server and on the terminal, the server having access to at least one database comprising: a list of sets of identifiers, each set of identifiers comprising a terminal identifier, a hardware layer identifier, and an operating system identifier; a lookup table mapping between each pair of hardware layer identifier and operating system identifier that exists in said list, and a configuration file, stored in the at least one database the method comprising, upon a communication session being opened between the terminal and the server: a. sending, from the terminal to the server, a set of identifiers comprising a terminal identifier, a hardware layer identifier for a hardware layer of the terminal, and an operating system identifier for the operating system implemented on the terminal; d. upon the terminal receiving a configuration file from the server, implementing said configuration file in the front-end application (as shown in Fig. 1, which is reproduced below for ease of reference and convenience, Etchegoyen discloses at least one computing/network client device 100 that is in operative communication via the Internet 102 with an audit server 110 and an update server 120. While only one client device 100. The unique device identifiers are sent to at least one of an audit server 110 and an update server 120, (step 240). The client device 100 receives an updated program configuration from the update server 120 (step 250). See ¶ 18, 35-36, 40-42, 48-60). PNG media_image1.png 721 562 media_image1.png Greyscale But Etchegoyen does not disclose implementing said configuration file in the front-end application and and if and only if said configuration file carries an indicator tagging the file as temporary, switching the front-end application to a test mode. In the same field of endeavor, Argawal teaches that a client requests to access a computing resource, a computing service may generate a first password value for the computing resource and transmit the first password value to the client. The client may then generate and transmit key data for entry of the first password value back to the computing service. The client may generate and transmit the key data on the user's behalf, without requiring any activation or selection of keys by the user. Upon receiving the key data, the computing service may enter the first password value into the computing resource, thereby allowing the client to access the computing resource. The client 110 may connect to the computing resource 123 in the administrative mode 225, for example to install and customize applications and software (e.g., modify configuration files, set registry settings, etc.), apply group policies, set restrictions, and perform other operations. Also, in some cases, client 110 may connect to computing resource 123 in the test mode 226, for example to test applications, customizations, settings, restrictions, and other features. Client 110 may often switch repeatedly between the administrative mode 225 and the test mode 226, such as to configure and test various different features application (as shown in Fig. 2, which is reproduced below for ease of reference and convenience, Argawal discloses selection of the Switch to Test Mode option from the drop down menu 620, may cause the browser 111 to display a test mode log-in interface 1010 for accessing the computing resource 123 in the test mode 226. The test mode log-in interface 1010 includes an entry field 1011 for entering of security information for accessing the computing resource 123 in the test mode 226. Selection of the Switch to Test Mode option may also cause the browser 111 to send a request to the computing service 120 to access the computing resource 123 in the test mode 226. Upon receiving this request, the computing service 120 may update (e.g., set, modify, etc.) a password or other security information for the user's account to access the computing resource 123 in the test mode 226. See ¶ 25-28). PNG media_image2.png 993 652 media_image2.png Greyscale It would have been obvious to a person of ordinary skill in the art before the effective filling date of the claimed invention to a person having ordinary skill in the art to modify the teaching of Etchegoyen to include that the customer may connect to the computing resource in order to configure the computing resource. In some cases, the customer may connect to the computing resource in an administrative mode or test mode, for example to install and customize and applications, apply group policies and set restrictions, and perform other operations, as taught by Argawal, in order to reduce the risk of security information being used by an unauthorized individuals. Examiner's note: Examiner has cited particular columns and line numbers in the references applied to the claims above for the convenience of the Applicant. Although the specified citations are representative of the teachings of the art and are applied to specific limitations within the individual claim, other passages and figures may apply as well. It is respectfully requested from the Applicant in preparing responses, to fully consider the references in entirety as potentially teaching all or part of the claimed invention, as well as the context of the passages as taught by the prior art or disclosed by the Examiner. Allowable Subject Matter Claims 11-12, 15-16, 18 are allowable over the prior of records. Claims 14 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. The following is an Examiner's statement of reasons for the indication of allowable subject matter: Claims 11, 14-15 are allowable over the prior art of record because the prior arts, cited in its entirety, or in combination, do not teach b. upon the server receiving the set of identifiers from the terminal, comparing this set with the content of the database, and in the event of no match between the set of identifiers sent and the sets of identifiers in said list, and in the event of a match with a pair of hardware layer and operating system identifiers in the lookup table, sending in return, from the server to the terminal, the configuration file associated with said pair in the lookup table; in the event of no match with a pair of hardware layer and operating system identifiers in the lookup table, identifying, in the lookup table and by applying pre-established rules, a pair of hardware layer and operating system identifiers which is closest to that in the set of identifiers sent from the terminal, then sending in return, from the server to the terminal, the configuration file associated with the combination identified according to the lookup table, said file being sent with an indicator tagging the configuration file as temporary; c. populating the database with the set of identifiers received and any association resulting from the identification (claims 11, 15); e. in response to a predetermined validation action by the user via the terminal, deleting an indicator tagging the file as temporary, on the terminal, switching the front-end application to a normal mode, sending, from the terminal to the server, a command to validate said temporary configuration file (claim 14). Conclusion Claims 13, 17, 19-20 1are rejected. Claims 11-12, 15-16, 18 are allowed. Claim 14 are objected. The prior arts made of record and not relied upon are considered pertinent to applicant's disclosure. Coelho, US Pub No. 2021/0200557, teaches a local computer system can be configured to initially access a first remote network element and obtain, from the first remote network element, selected information including the address information of the network element and a launcher application program configured to manage execution of the local craft terminal application on the local computer system. (Abstract, ¶ 26-27, 35-36, FIG. 1). Xing et al., US Pub No. 2024/0028660, teach a method includes: receiving a first message sent by a first application APP on a terminal device, where the first message includes a user agent UA; determining, based on the first message, a first address and a second address corresponding to the terminal device; and sending a second message to the first APP, where the second message includes the first address and the second address, and the second message is used by the first APP to first attempt to open a page corresponding to the first address after receiving the second message, and if the opening fails, open a page corresponding to the second address. Zhang, US Pub No. 2015/0134944, teaches a data terminal running mode switching method, a device and a data terminal. The method comprises: a data terminal booting into a first running mode, the data terminal judging whether the first running mode matches with a type of an operating system running on a computer or not, if yes, the data terminal continuing to normally run under the first running mode; if no, switching to a second running mode that matches with the type of the operating system running on the computer, and running under the second running mode. Montagna et al., US Pub No. 2012/0110142, teach the method involves capturing a reference snapshot of first configuration settings for a first server, and capturing a current snapshot of second configuration settings for a second server. Using a processing device, differences between the first configuration settings in the reference snapshot with the second configuration settings in the current snapshot are determined. Brown et al., US Pub No. 2002/0188701, teach a configuration manager (222) has a mapping mechanism (226) that maps at least one configuration settings for selected platform to corresponding configuration settings for different platform. Mysore Shantamurthy et al., US Pub No. 2022/0066766, teach system firmware sends a query to a management for updated configuration data used during a boot of the host computing device. The management subsystem sends the updated configuration data to the system firmware, and boot instructions in the system firmware compare the updated configuration data with configuration data stored on the host computing device. If the respective configuration data match, the boot instructions continue with booting the host computing device. If the configuration data do not match, then the boot instructions update the stored configuration data with the updated configuration data and then proceed to boot the host computing device. Any inquiry concerning this communication or earlier communications from the examiner should be directed to examiner Raymond Phan, whose telephone number is (571) 272-3630. The examiner can normally be reached on Monday-Friday from 6:30AM- 3:00PM. The Group Fax No. (571) 273-8300. Communications via Internet e-mail regarding this application, other than those under 35 U.S.C. 132 or which otherwise require a signature, may be used by the applicant and should be addressed to [raymond.phan@uspto.gov]. 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, Andrew Jung can be reached at (571) 270-3779. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. All Internet e-mail communications will be made of record in the application file. PTO employees do not engage in Internet communications where there exists a possibility that sensitive information could be identified or exchanged unless the record includes a properly signed express waiver of the confidentiality requirements of 35 U.S.C. 122. This is more clearly set forth in the Interim Internet Usage Policy published in the Official Gazette of the Patent and Trademark on February 25, 1997 at 1195 OG 89. 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 hop://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). Any inquiry of a general nature or relating to the status of this application should be directed to the TC 2100 central telephone number is (571) 272-2100. /RAYMOND N PHAN/ Primary Examiner, Art Unit 2175
Read full office action

Prosecution Timeline

Oct 04, 2024
Application Filed
Apr 17, 2026
Non-Final Rejection mailed — §103, §OTHER (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12641550
DYNAMIC POWER SCALING IN A SERVER SYSTEM USING A POWER RAMP CAP
3y 7m to grant Granted May 26, 2026
Patent 12638902
Data Center Power Management With Power Saving Mode
2y 4m to grant Granted May 26, 2026
Patent 12639034
ELECTRONIC DEVICE AND OPERATION METHOD OF ELECTRONIC DEVICE
2y 4m to grant Granted May 26, 2026
Patent 12632227
FLEXIBLE CONFIGURATION COMPONENTS
1y 9m to grant Granted May 19, 2026
Patent 12625836
System and Method for Flexibly Crossing Packets of Different Protocols
1y 9m to grant Granted May 12, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
94%
Grant Probability
90%
With Interview (-3.9%)
2y 1m (~6m remaining)
Median Time to Grant
Low
PTA Risk
Based on 1030 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month