DETAILED ACTION
The Office Action is in response to Amendments filed 10/10/2025.
Claims 1 and 3-9 are pending.
Claim 2 is cancelled.
Claims 1, and 3-9 are currently amended.
The current rejection of claims 1 and 3-9 under 35 U.S.C. 112(b) have been withdrawn in view of applicant’s amendments to claims 1 and 3-9.
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 Objections
Claims 4, 6, and objected to because of the following informalities: The claims use the term “Paramters” which is misspelled. Appropriate correction is required.
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.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 1-9 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 (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Claims 1, 3-4, and 8-9 recite the limitation “event”. There is a lack of antecedent basis for these limitations in the claims. As recited it is unclear if “event” refers to “the event” in claim 1 or to something else entirely. Examiner has proposed amendments for the purpose of compact prosecution.
Claims 1, 4-5, and 9 recite the limitation “Invoke Tree” and “InvokeTree”. There is insufficient antecedent basis for these limitations in the claims. Examiner has proposed amendments for the purpose of compact prosecution.
Claims 3-9 recite the limitation “an Android Application micro-service driven by an application scenario” in lines 1-2 respectively. There is insufficient antecedent basis for these limitations in the claims. Examiner has proposed amendments for the purpose of compact prosecution.
Claims 4, 8, and 9 recite the limitation “componentId”. There is insufficient antecedent basis for these limitations in the claims. As recited, it is unclear if “componentId” refers to the “componentId” recited in claim 4 or to something else entirely. Examiner has proposed amendments for the purpose of compact prosecution.
Claims 7 and 9 recite the limitation “Event”. There is insufficient antecedent basis for these limitations in the claims. As recited, it is unclear if the term refers to “a set Events”, “event”, or to something else entirely. Examiner has proposed amendments for the purpose of compact prosecution.
Claims 4, 6, and 8 recite the limitation “Parameters”. There is insufficient antecedent basis for these limitations in the claims. As recited, it is unclear if the term refers to “method Parameters” or to something else entirely. Examiner has proposed amendments for the purpose of compact prosecution.
Claim 5 recites the limitation “the shortest character string sequence”. The limitation is rejected for indefiniteness. Examiner has proposed amendments for the purpose of compact prosecution.
Claims 6 and 8 recite the limitation “Input”. There is insufficient antecedent basis for these limitations in the claims. As recited it is unclear if the term refers to “Input” (S332) in claim 6 or to something else entirely. Examiner has proposed amendments for the purpose of compact prosecution.
Claim 8 recites the limitation “Input’” in line 9. There is insufficient antecedent basis for this limitation in the claim. As recited, it is unclear if the term refers to previously mentioned “Input’” of claim 8 or to something else entirely. Examiner has proposed amendments for the purpose of compact prosecution.
Claims 6, 8, and 9 recite the limitation “dispatch Touch Event”. There is insufficient antecedent basis for these limitations in the claims. As recited, it is unclear if “dispatch Touch Event” refers to “dispatchTouchEvent” in claim 1 or to something else entirely. Examiner has proposed amendments for the purpose of compact prosecution.
Claim 9 recites the limitation “Output”. There is insufficient antecedent basis for this limitation in the claim. As recited, It is unclear if “Output” refers to “Output” in claim 8 or to something else entirely. Examiner has proposed amendments for the purpose of compact prosecution.
Claim 9 recites the limitation “the first page”. The limitation is rejected for indefiniteness. Examiner has proposed amendments for the purpose of compact prosecution.
Claim 9 recites the limitation “the first event”. The limitation is rejected for indefiniteness. Examiner has proposed amendments for the purpose of compact prosecution.
Claim 9 recites the limitation “the two formulas”. The limitation is rejected for indefiniteness. Examiner has proposed amendments for the purpose of compact prosecution.
Examiner has attempted to contact Attorney Jose Cherson Weissbrot Reg No. 80539 to discuss potential amendments to the case.
(Currently Amended) An automatic generation method for an Android application micro-service driven by an application scenario, comprising the following steps:
S1: reconstructing a software architecture when an application runs based on application interface information;
S2: executing an objective function multiple times, and recording a method calling sequence of the objective function to form calling instances of multiple objective function based on a runtime model;
S3: analyzing the calling instances to acquire a service module of the Android application micro-service with the objective function; and
S4: with respect to a given user input, executing the service module of the Android application micro-service to obtain a result identical to the objective function;
the S2 specifically comprises:
S21: creating event according to information of current method in the method calling sequence when detecting that the current method is a dispatch Touch Event or setText method;
S22: considering the methods after the current method as the methods triggered by a current operation of a user, and adding them into Invoke Tree of the event created in the S21, the Invoke Tree is a portion in the event, the Invoke Tree represents a subsequent calling sequence of [[the]]an application after the user executes the current operation; and
S23: adding event creator in the S21 and processed in the S22 into a set Events.
(Currently Amended) The automatic generation method for [[an]]the Android application micro-service driven by [[an]]the application scenario according to claim 1, wherein creating the event according to the information of the current method in the S21 specifically comprises:
S211: calling a method of a caller object in the current method to acquire component Id and path; and
S212: respectively filling activity Id, method and parameter of the event with activityId, method Name and method Parameters of the current method.
(Currently Amended) The automatic generation method for [[an]]the Android application micro-service driven by [[an]]the application scenario according to claim 3, wherein the S3 specifically comprises:
S31: generating portions in the event: the activity Id, the component Id and the path, indicating which component in which page simulates a user operation, wherein the activity Id indicates a 'user's page', the component Id and the path indicates components in [[the]]a user page, and
S32: generating the Invoke Tree in the event, and solving a subsequence of the Invoke Tree so as to obtain a series of methods that will be called by the application after simulating the user operation; and
S33: generating portions in the event: method and the method Parameters indicating which operation of the user will be simulated so as to obtain a service template corresponding to the Android application micro-service.
5. (Currently Amended) The automatic generation method for [[an]]the Android application micro-service driven by [[an]]the application scenario according to claim 4, wherein the S32 specifically comprises the following steps:
S321: filling a data pool with data of a specific method in the Invoke Tree, wherein the specific method is a method and a sub-method thereof of a method caller for the component in the page, and the data filled is a call of the specific method and the sub-method thereof, a calling parameter and a called returned value;
S322: deleting the series of methods in the Invoke Tree that do not exist in [[the]]a previous data pool according to the data filled;
S323: converting the Invoke Tree into character string sequences so as to obtain n character string sequences;
S324: finding out [[the]]a shortest character string sequence, and sequentially checking whether character strings in the same positions in other character string sequences are identical based on the character string sequence, and if all the character strings in the same positions are identical, adding the character string into a final result until completely checking the character strings in all positions of the shortest character string sequence so as to obtain a final character string form of the subsequence; and
S325: reversely parsing the final character string form of the subsequence to the Invoke Tree.
(Currently Amended) The automatic generation method for [[an]]the Android application micro-service driven by [[an]]the application scenario according to claim 5, wherein the S33 specifically comprises:
S331: dividing the user operation into an input operation and a click operation;
S332: with respect to the click operation, setting method to be the dispatch Touch Event, wherein the method Parameters represents a position of the current component in a screen, and its value is not needed to be acquired from Input and may be obtained directly by a method of calling a component object Motion Event itself;
S333: with respect to the input operation, setting method to be the setText method, wherein the method Parameters represents input data of the user, the method Parameters is originated from input data of the user, and a sequence of inputting the parameter is identical to a sequence in the setText method; and
S334: therefore, traversing sequences in the service template by an input type parameter algorithm, and replacing <Ti, Vi> in the method Parameters with <T1, j> when it is the setText method, the <Ti, Vi> in the method Parameters is the method type (touch event or set text event) and specific user respectively, namely, the parameter of the method is data input by the j user to represent that the Input is mapped with data in the method Parameters.
(Currently Amended) The automatic generation method for [[an]]the Android application micro-service driven by [[an]]the application scenario according to claim 6 , wherein the S4 specifically comprises:
S41: instantiating the set Events of the Android application micro-service according to the user input; and
S42: executing the set Events of the service template of the Android application micro- service, wherein the page represented after executing the set Events of the service template of the Android application micro-service is Output of the Android application micro-service.
(Currently Amended) The automatic generation method for [[an]]the Android application micro-service driven by [[an]]the application scenario according to claim 7, wherein the S41 specifically comprises:
S411: determining a specific value of the method Parameters according to a mapping relation between the Input in the service template of the Android application micro-service and the method Parameters in the event; and
S412: with respect to a specific user input Input', when method in the event is the setText method, if a certain parameter in the method Parameters is <T1, j>, assigning V of the jth data in the Input' to it, namely, the parameter in the method Parameters becomes a specific value <T1,V>; and when method in the event is the dispatch Touch Event, stipulating that there is only one parameter in the method Parameters, and generating a Motion Event object according to the position of a view component on the page corresponding to the component Id and assigning a value to the parameter in the method Parameters.
(Currently Amended) The automatic generation method for [[an]]the Android application micro-service driven by [[an]]the application scenario according to claim 7, wherein the S42 specifically comprises:
S421: setting that the event of each service is started from [[a]] first page of the application, namely, the page indicated by the activity Id of is the first page of the application, and then sequentially executing the set Events;
S422: with respect to execution of each of the event, first performing execution in the page indicated by the activity Id, then determining an object view for simulating the user operation in the interface according to the component Id and the path, and simulating the user operation by means of the setText method or the dispatch Touch Event method;
S423: after simulating the user operation, monitoring the method call performed next by the application to obtain an Execution Invoke Tree, and comparing it with the method in the Invoke Tree of the currently executed event; and if the method and the currently executed event are completely identical, considering that execution of current event has been finished and executing a next event; and
S424: after executing all the set Events in the service template, wherein the page represented by the application is the Output of the Android application micro-service.
Allowable Subject Matter
Claims 1, 3-9 are allowed.
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 TRAVIS VIET TRAN whose telephone number is (571)272-3720. The examiner can normally be reached Monday-Friday 8:30AM-5PM.
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, Wei Mui can be reached at 571-272-3708. 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.
/T.V.T./Examiner, Art Unit 2191 /WEI Y MUI/Supervisory Patent Examiner, Art Unit 2191