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 is in response to Application filed 08/30/24. Claims 1 – 20 have been examined and are pending.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s)1 - 20 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Gaur US 20250004766 A1.
Regarding claims 1 and 14, Gaur anticipates a method of creating an application comprising:
obtaining configuration information, wherein the configuration information indicates a plurality of processing entities for creating an application, the configuration information further comprising jump information associated with a target processing entity in the plurality of processing entities, the jump information comprising at least one jump control parameter, wherein the at least one jump control parameter is associated with a jump decision process at the target processing entity, and the jump decision process is performed by a jump control entity independent of the target processing entity (0080 – 0082, see jump/branch target); and
creating a target application based on the configuration information (0110, see creation management).
Regarding claims 2 and 15, the method of claim 1, wherein the at least one jump control
parameter comprises a first parameter indicating the jump control entity for performing the jump decision process [0112, see branch predictor].
Regarding claims 3 and 16, the method of claim 2, wherein the jump control entity is:
a dedicated model trained for a jump decision task [0210, see retrain and branch]; or
a general language model [0106, see high level language and machine language].
Regarding claims 4 and 17, the method of claim 3, further comprising:
in response to the first parameter indicating that the jump control entity is
the general language model, obtaining an input of a prompt text, wherein the prompt
text is provided to the jump control entity for performing the jump decision process [0112].
Regarding claims 5 and 18, the method of claim 3, wherein the general language model is configured to perform the jump decision process based on target prompt information,
wherein the target prompt information comprises at least one of:
description information of a set of associated processing entities to which the target processing entity is capable of jumping; context information associated with the target processing entity; a prompt text input by a user; or a target request to be processed [0112 – 0117].
Regarding claim 6 and 19, the method of claim 1, wherein the at least one jump control
parameter comprises a second parameter indicating that the jump control entity performs the jump decision process based on input information and/ or output information of the target processing entity [0112 – 0117].
Regarding claims 7 and 20, the method of claim 6, wherein in response to the second parameter indicating performing the jump decision process based on the input information, the jump control entity is configured to: before the target processing entity processes a first request, determine whether to jump to a further processing entity to process the first request based on the first request and first context information [0112 – 0117].
Regarding claim 8, the method of claim 6, wherein in response to the second parameter
indicating performing the jump decision process based on the output information, the jump control entity is configured to: after the target processing entity processes a second request, determine whether to jump to a further processing entity to process the second request based on the second request, second context information and output content for the second request of the target processing entity [0112 – 0117].
Regarding claim 9, the method of claim 1, wherein the at least one jump control
parameter comprises a third parameter, the third parameter indicating a range of
context information provided to the jump control entity to perform the jump
decision process [0112 – 0117].
Regarding claim 10, the method of claim 1, wherein:
during a processing of a target request by the target application, in response to the target application jumping from the target processing entity to a further processing entity to process the target request, context information associated with a target processing entity is provided to the further processing entity for processing the target request [0112 – 0117].
Regarding claim 11, a method for request processing, comprising: receiving, by a target application, a target request to be processed;
in response to determining that the target request is to be processed by a first processing entity of the target application, providing, using the first processing entity, a first output content for the target request; and in response to determining that the target request is processed by jumping from the first processing entity to a second processing entity, providing, using the second processing entity, a second output content for the target request [0112 – 0117].
Regarding claim 12, the method of claim 11, further comprising:
determining, based on configuration information of the target application, that processing the target request comprises jumping from the first processing entity to the second processing entity, wherein the configuration information comprises jump information associated with the first processing entity, the jump information comprises at least one jump control parameter, the at least one jump control parameter is associated with a jump decision process at the first processing entity, and the jump decision process is performed by a jump control entity independent of the first processing entity [0112 – 0117].
Regarding claim 13, the method of claim 12, wherein the at least one jump control
parameter indicates that the jump control entity performs the jump decision process at least based on a first input content of the first processing entity [0112 – 0117].
Correspondence Information
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Chuck Kendall whose telephone number is 571-272-3698. The examiner can normally be reached on 10:00 am - 6:30pm.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Hyung Sough can be reached on 571-272-6799. 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 [0060 – 0080].
For more information about the PAIR system, see http://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).
/CHUCK O KENDALL/
Primary Examiner, Art Unit 2192
Prosecution Insights