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 .
Claims 1-20 have been examined.
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) 11-12 and 15-20 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Eisner.
In regard to claim 11, Eisner discloses:
11. A method comprising: See e.g. Eisner Fig. 2, broadly depicting a method.
determining, using a deep neural network model of a predictive framework configured to enable sequence-based forecasting of future events using external data calls, a plurality of past events for an entity over a time period, wherein the plurality of past events include feature data for features processed by the deep neural network model; Eisner ¶ 0028, “each training example including an example error condition, and an example data-flow program fragment for responding to the error. For example, previously-trained code-generation machine 104 may be trained with regard to a large plurality of annotated dialogue histories …” Also ¶ 0029, “In examples, a context-specific dialogue history includes a plurality of events arranged in a temporal order, e.g., time-stamped events, …”
determining, using the deep neural network model, a first predictive forecast of a first future event at a first future time after the time period based on the feature data; Eisner, ¶ 0045, “As an alternative, latency may be reduced by predicting and speculatively executing function calls while the user is still speaking based on partial results from automatic speech recognition (ASR) and the current state of execution.”
determining a first external data call required for the first future event based on at least one of the plurality of past events; executing the first external data call to a first external service prior to the first future time, wherein the first external service includes data used during the first future event; Eisner, ¶ 0017, “… invoking an API to perform an action using the API, e.g., ordering food from a restaurant, scheduling a ride with a ride-hailing service, scheduling a meeting in a calendar service, placing a phone call.” ¶ 0030, “The example data-flow program may include any suitable functions in any suitable sequence/arrangement, so that via training, the code-generation machine is configured to output suitable functions in a suitable sequence.” Also ¶ 0045, “As an alternative, latency may be reduced by predicting and speculatively executing function calls while the user is still speaking based on partial results from automatic speech recognition (ASR) and the current state of execution.”
receiving the data from the first external service based on the executing; and storing the data for the first future time of the first future event. Eisner, ¶ 0045, “As an alternative, latency may be reduced by predicting and speculatively executing function calls while the user is still speaking based on partial results from automatic speech recognition (ASR) and the current state of execution.” Also ¶ 0051, “the user is not presented any output until their utterance is complete.” Note that the output of speculative execution is first received and stored until an associated utterance is complete.
In regard to claim 12, Eisner also discloses:
12. The method of claim 11, wherein the deep neural network model is trained using a long short-term memory (LSTM) algorithm, gated recurrent unit (GRU) algorithm, or other recurrent neural network (RNN) algorithm with one-dimensional convolutional layers for the sequence-based forecasting of the future events based on past sequences of events associated with past executions of the external data calls, and Eisner ¶ 0123, “Non-limiting examples of techniques that may be incorporated in an implementation of one or more machines include support vector machines, multi-layer neural networks, convolutional neural networks (e.g., including spatial convolutional networks for processing images and/or videos, temporal convolutional neural networks for processing audio signals and/or natural language sentences, and/or any other suitable convolutional neural networks configured to convolve and pool features across one or more temporal and/or spatial dimensions), recurrent neural networks (e.g., long short-term memory networks), …” Also ¶ 0123, “… temporal convolutional neural networks …” Note that a temporal convolutional network utilizes 1D convolutional layers.
wherein, prior to the determining the plurality of past events, the method further comprises: executing the predictive framework for the entity based on the entity utilizing a computing service associated with the first future event. Eisner ¶ 0029, “In examples, a context-specific dialogue history includes a plurality of events arranged in a temporal order, e.g., time-stamped events, …”
In regard to claim 15, Eisner also discloses:
15. The method of claim 11, further comprising: retrieving, at the first future time, the stored data for the first future event; and loading the stored data during a data processing operation for the first future event. Also ¶ 0051, “the user is not presented any output until their utterance is complete.”
In regard to claim 16, Eisner also discloses:
16. The method of claim 11, wherein prior to the determining the first predictive forecast, the method further comprises: determining a plurality of vectors from sequences of the plurality of past events during different time intervals over the time period, wherein each of the plurality of vectors comprise encoded data identifying each of the sequences, and Eisner, ¶ 0019, “the previously-trained code-generation machine 104 includes an encoder machine configured to encode the user utterance 102 as a semantic feature, e.g., a vector in a semantic vector space learned by the previously-trained code-generation machine 104 and a decoder machine configured to decode the semantic feature by outputting one or more functions from the plurality of pre-defined functions 110.”
wherein the first predictive forecast comprises one of a vector or a score provided as an output from the deep neural network model that identifies a likelihood of occurrence of the first future event occurring. Eisner, ¶ 0098, “If the same invocation appears in multiple plans with different embeddings, these embeddings can be pooled before converting to a score.” Also ¶ 0134, “In any of the preceding examples, or any other example, the change in execution cost is additionally or alternatively based on one or more of an expected latency, a total computing cost, and a likelihood distribution indicating a probability that the program node will appear in a final dataflow program.”
In regard to claim 17, Eisner discloses:
17. A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising: See Eisner Fig. 6 element 604 and ¶ 0119, “Storage subsystem 604 includes one or more physical devices configured to temporarily and/or permanently hold computer information such as data and instructions executable by the logic subsystem.”
receiving training data for a recurrent neural network (RNN) model, wherein the training data comprising feature data for model features selected for the RNN model over a time period associated with a plurality of past computing events for an entity; Eisner ¶ 0028, “each training example including an example error condition, and an example data-flow program fragment for responding to the error. For example, previously-trained code-generation machine 104 may be trained with regard to a large plurality of annotated dialogue histories …” Also ¶ 0029, “In examples, a context-specific dialogue history includes a plurality of events arranged in a temporal order, e.g., time-stamped events, …” Also ¶ 0123, “Non-limiting examples of techniques that may be incorporated in an implementation of one or more machines include … recurrent neural networks (e.g., long short-term memory networks), …”
encoding the plurality of past computing events using the feature data; Eisner, ¶ 0019, “the previously-trained code-generation machine 104 includes an encoder machine configured to encode the user utterance 102 as a semantic feature, e.g., a vector in a semantic vector space learned by the previously-trained code-generation machine 104 and a decoder machine configured to decode the semantic feature by outputting one or more functions from the plurality of pre-defined functions 110.”
training the RNN model using the training data and the encoding of the plurality of past computing events, wherein the RNN model is trained to enable predictive forecasting of a future computing event; Eisner ¶ 0028, “each training example including an example error condition, and an example data-flow program fragment for responding to the error. For example, previously-trained code-generation machine 104 may be trained with regard to a large plurality of annotated dialogue histories …”
predicting the future computing event using the RNN model; executing a computing call during a data processing of the future computing event on behalf of the entity; and Eisner, ¶ 0045, “As an alternative, latency may be reduced by predicting and speculatively executing function calls while the user is still speaking based on partial results from automatic speech recognition (ASR) and the current state of execution.”
preloading, based on the executing the computing call, data for the data processing of the future computing event prior to an occurrence of the future computing event. Eisner, ¶ 0045, “Identifying and pre-executing partial programs while the user is still speaking provides the technical benefit of expediting the final response to the user, thus improving user satisfaction due to improved computer-human interaction.”
In regard to claim 18, Eisner also discloses:
18. The non-transitory machine-readable medium of claim 17, wherein a predictive framework includes the RNN model and one or more operations that integrate outputs by the RNN model into a plurality of downstream services that utilize the data and additional data for predictive computing call executions by the predictive framework, and Eisner, ¶ 0045, “As an alternative, latency may be reduced by predicting and speculatively executing function calls while the user is still speaking based on partial results from automatic speech recognition (ASR) and the current state of execution.” Also ¶ 0051, “the user is not presented any output until their utterance is complete.”
wherein the RNN model comprises one of a long short-term memory (LSTM) model or a gated recurrent unit (GRU) model that use one-dimensional convolutional layers. Eisner, ¶ 0123, “… temporal convolutional neural networks … recurrent neural networks (e.g., long short-term memory networks).” Note that a temporal convolutional network utilizes 1D convolutional layers.
In regard to claim 19, Eisner also discloses:
19. The non-transitory machine-readable medium of claim 18, wherein the output comprises at least one of a regression output type or a classification output type associated with the future computing event, and Eisner, ¶ 0098, “Even if a function invocation is classified as positive, the actual invocation must be delayed until its arguments have been computed.”
wherein the outputs utilize at least one recurrent cell for the RNN model. ¶ 0123, e.g. “… recurrent neural networks (e.g., long short-term memory networks), …” Note that recurrent cells are elements of an RNN and are thereby an inherent element.
In regard to claim 20, Eisner also discloses:
20. The non-transitory machine-readable medium of claim 17, wherein the operations further comprise: detecting the occurrence of the future computing event; and loading the data from a local storage for a computing service requiring the data for the data processing. Eisner, ¶ 0045, “Identifying and pre-executing partial programs while the user is still speaking provides the technical benefit of expediting the final response to the user, thus improving user satisfaction due to improved computer-human interaction.” Also see Fig. 6 and ¶ 0115-0116 describing local implementation.
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.
Claim(s) 1-5, 7 and 13-14 is/are rejected under 35 U.S.C. 103 as being unpatentable over U.S. Patent Application Publication 20230367602 by Eisner et al. ("Eisner") in view of U.S. Patent Application Publication 20190332451 by Tamjidi et al. ("Tamjidi").
In regard to claim 1, Eisner discloses:
1. A service provider system comprising: a non-transitory memory; and one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the service provider system to perform operations comprising: See Fig. 6 along with ¶ 0118-0121, e.g. “Storage subsystem 604 includes one or more physical devices configured to temporarily and/or permanently hold computer information such as data and instructions executable by the logic subsystem.”
obtaining input feature data for an entity, wherein the input feature data is associated with sequence-based data for neural network features over a past time period; Eisner ¶ 0028, “each training example including an example error condition, and an example data-flow program fragment for responding to the error. For example, previously-trained code-generation machine 104 may be trained with regard to a large plurality of annotated dialogue histories …” Also ¶ 0029, “In examples, a context-specific dialogue history includes a plurality of events arranged in a temporal order, e.g., time-stamped events, …”
executing a predictive call execution framework comprising a deep neural network model trained for forecasting of future events associated with the entity, Eisner, Fig. 1, element 104 along with ¶ 0019, “The previously-trained code-generation machine 104 may be based on any suitable technology, such as state-of-the-art or future machine learning (ML), artificial intelligence (AI), and/or natural language processing (NLP) technologies.” Also ¶ 0123, “Non-limiting examples of techniques that may be incorporated in an implementation of one or more machines include … multi-layer neural networks, … recurrent neural networks (e.g., long short-term memory networks), …”
wherein the deep neural network model is trained using training data associated with the neural network features for event sequences from past events associated with the entity; Eisner ¶ 0029, “In examples, a context-specific dialogue history includes a plurality of events arranged in a temporal order, e.g., time-stamped events, …”
determining a first predictive forecast of one of the future events for the entity at a future time using the input feature data and the deep neural network model; and Eisner, ¶ 0045, “As an alternative, latency may be reduced by predicting and speculatively executing function calls while the user is still speaking based on partial results from automatic speech recognition (ASR) and the current state of execution.”
adding, based on the first predictive forecast, an API call for data from an external computing service to a … processing event, wherein the data is usable for the one of the future events at the future time. Eisner, ¶ 0017, “… invoking an API to perform an action using the API, e.g., ordering food from a restaurant, scheduling a ride with a ride-hailing service, scheduling a meeting in a calendar service, placing a phone call.” ¶ 0030, “The example data-flow program may include any suitable functions in any suitable sequence/arrangement, so that via training, the code-generation machine is configured to output suitable functions in a suitable sequence.” Also ¶ 0045, “As an alternative, latency may be reduced by predicting and speculatively executing function calls while the user is still speaking based on partial results from automatic speech recognition (ASR) and the current state of execution.”
Eisner does not expressly disclose: batch. This is taught by Tamjidi. See Tamjidi ¶ 0008, “The disclosed batch REST API enables the batch REST server to receive and process the batch request and to respond with a single batch response. As such, the disclosed batch REST system dramatically reduces overhead (e.g., network round trip delay, authentication delay, session setup delay, and so forth) by enabling multiple requested items to be combined into a single batch request.” It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to use Tamjidi’s batch service with Eisner’s API in order to reduce overhead as suggested by Tamjidi.
In regard to claim 2, Eisner also discloses:
2. The service provider system of claim 1, wherein the deep neural network model comprises a long short-term memory (LSTM) architecture, gated recurrent unit (GRU) architecture, or other recurrent neural network (RNN) architecture trained using a plurality of event sequences encoded from occurrences of past events associated with the future events to be forecasted, and Also ¶ 0123, “Non-limiting examples of techniques that may be incorporated in an implementation of one or more machines include support vector machines, multi-layer neural networks, convolutional neural networks (e.g., including spatial convolutional networks for processing images and/or videos, temporal convolutional neural networks for processing audio signals and/or natural language sentences, and/or any other suitable convolutional neural networks configured to convolve and pool features across one or more temporal and/or spatial dimensions), recurrent neural networks (e.g., long short-term memory networks), …”
wherein the deep neural network model uses one-dimensional convolutional layers with the LSTM architecture, the GRU architecture, or the RNN architecture. ¶ 0123, “… temporal convolutional neural networks …” Note that a temporal convolutional network utilizes 1D convolutional layers.
In regard to claim 3, Eisner also discloses:
3. The service provider system of claim 1, wherein the sequence-based data comprises time-based data of computing events executed by the entity over the past time period using a computing service of the service provider system provided to the entity. Eisner, ¶ 0017, “… invoking an API to perform an action using the API, e.g., ordering food from a restaurant, scheduling a ride with a ride-hailing service, scheduling a meeting in a calendar service, placing a phone call.”
In regard to claim 4, Eisner also discloses:
4. The service provider system of claim 1, wherein the operations further comprise: executing the batch processing event with the external computing service for the API call; storing the data for the one of the future events detecting a computing operation occurring that is associated with the one of the future events; retrieving the stored data; and loading the stored data to at least one downstream computing service during the one of the future events. Eisner, ¶ 0045, “As an alternative, latency may be reduced by predicting and speculatively executing function calls while the user is still speaking based on partial results from automatic speech recognition (ASR) and the current state of execution.” Also ¶ 0051, “the user is not presented any output until their utterance is complete.” Note that the output of speculative execution is first received and stored until an associated utterance is complete.
In regard to claim 5, Eisner also discloses:
5. The service provider system of claim 1, wherein the input feature data comprises data corresponding to at least one string of computing events processed for the entity during the past time period, and Eisner, ¶ 0020, “Accordingly, the user utterance 102, data-flow program 106 generated for the user utterance 102, and/or any relevant assistant response 120 by the automated assistant may be stored in the context-specific dialogue history 130.”
wherein the operations further comprise: encoding the data corresponding to the at least one string of computing events from at least one sequence of computing events occurring during the past time period and the neural network features. Eisner, ¶ 0019, “the previously-trained code-generation machine 104 includes an encoder machine configured to encode the user utterance 102 as a semantic feature, e.g., a vector in a semantic vector space learned by the previously-trained code-generation machine 104 and a decoder machine configured to decode the semantic feature by outputting one or more functions from the plurality of pre-defined functions 110.”
In regard to claim 7, Eisner also discloses:
7. The service provider system of claim 1, wherein the predictive call execution framework comprises one or more modules that are implemented with downstream services of the service provider system that provides stored data in real-time during the one of the future events at the future time. Eisner, ¶ 0045, “As an alternative, latency may be reduced by predicting and speculatively executing function calls while the user is still speaking based on partial results from automatic speech recognition (ASR) and the current state of execution.” Also ¶ 0051, “the user is not presented any output until their utterance is complete.”
In regard to claim 13, Eisner also discloses:
13. The method of claim 11, wherein the executing the first external data call comprises executing a … processing operation including the first external data call, wherein the … processing operation comprises using at least a portion of the external data calls that are processed prior to the future events. Eisner, ¶ 0017, “… invoking an API to perform an action using the API, e.g., ordering food from a restaurant, scheduling a ride with a ride-hailing service, scheduling a meeting in a calendar service, placing a phone call.” ¶ 0030, “The example data-flow program may include any suitable functions in any suitable sequence/arrangement, so that via training, the code-generation machine is configured to output suitable functions in a suitable sequence.” Also ¶ 0045, “As an alternative, latency may be reduced by predicting and speculatively executing function calls while the user is still speaking based on partial results from automatic speech recognition (ASR) and the current state of execution.”
Eisner does not expressly disclose: batch. This is taught by Tamjidi. See Tamjidi ¶ 0008, “The disclosed batch REST API enables the batch REST server to receive and process the batch request and to respond with a single batch response. As such, the disclosed batch REST system dramatically reduces overhead (e.g., network round trip delay, authentication delay, session setup delay, and so forth) by enabling multiple requested items to be combined into a single batch request.” It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to use Tamjidi’s batch service with Eisner’s API in order to reduce overhead as suggested by Tamjidi.
In regard to claim 14, Eisner also discloses:
14. The method of claim 13, further comprising: determining, using the deep neural network model, a second predictive forecast of a second future event at a second future time after the time period based on the feature data, wherein the second future event occurs after the first future event with a computing service provided to the entity; and determining a second external data call required for the second future event based on at least one of the plurality of past events, wherein the executing the batch processing operation includes executing the second external data call with the first external data call. See Fig. 5 and ¶ 0111, “At 515, actions are described that apply to each sequentially received utterance prefix.” Each sequential prefix corresponds to a future time with respect to a previous prefix.
Claim(s) 6 is/are rejected under 35 U.S.C. 103 as being unpatentable over Eisner and Tamjidi as applied above, and further in view of U.S. Patent 9697524 to Fischer et al. ("Fischer").
In regard to claim 6, Eisner does not expressly disclose:
6. The service provider system of claim 1, wherein the future events are associated with one of a transaction processing request, an account authentication request, or a network token fetching request, and wherein the API call comprises one of a bank account balance inquiry from an open source banking data platform, a network token prefetch request from a network token service provider, an available fund balance inquiry, an authentication confirmation, or a risk analysis. This is taught by Fischer. See Fischer, col. 25, line 64 – col. 26 line 7, “Requests for information such as requests for the status of an application, account balance, status of a deposit, copies of media (e.g., image copies of checks), delivery of correspondence and statements, servicing of non-conforming images, and providing of contact and transaction history, may also be automatically processed. This category of service requests may also include service requests that contain minimum financial risks to the customer or the bank, such as those requests for adjustment of amounts posted for less than $200 due to misreads, unreadability or other related claims.” It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to use Fischer’s service requests with Eisner’s API in order to automatically process financial services as suggested by Fischer.
Claim(s) 8-10 is/are rejected under 35 U.S.C. 103 as being unpatentable over Eisner and Tamjidi as applied above, and further in view of U.S. Patent Application Publication 20230326193 by Zia et al. ("Zia").
In regard to claim 8, Eisner also discloses:
8. The service provider system of claim 1, wherein prior to obtaining the input feature data, the operations further comprise: training the deep neural network model using a first portion of training data associated with the neural network features and an LSTM architecture, GRU architecture, or RNN architecture with one-dimensional convolutional layers; and Eisner ¶ 0028, “each training example including an example error condition, and an example data-flow program fragment for responding to the error. For example, previously-trained code-generation machine 104 may be trained with regard to a large plurality of annotated dialogue histories …” Also ¶ 0029, “In examples, a context-specific dialogue history includes a plurality of events arranged in a temporal order, e.g., time-stamped events, …”
Eisner does not expressly disclose:
testing the deep neural network model for deployment with the predictive call execution framework using a second portion of the training data. This is taught by Zia. See ¶ 0119, “As shown in FIG. 4G, some training methods may divide the training data into a training data subset, 435a, a validation data subset 435b, and a test data subset 435c. … Once the architecture has been trained, the method may assess the architecture's effectiveness by applying the architecture to all or a portion of the test data subsets 435c. … Testing at block 430c may be used to confirm the effectiveness of the trained architecture. Once the model is trained, inference 430d may be performed on a newly received inference input.” It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to use Zia’s testing with Eisner’s model in order to confirm training effectiveness as suggested by Zia.
In regard to claim 9, Eisner also discloses:
9. The service provider system of claim 8, wherein the training and the testing are performed using the training data specific to at least one of the entity or an event type that is designated for the forecasting of the future events based on sequences of other events occurring in a temporal association with each of the other events. Eisner, ¶ 0020, “Accordingly, the context-specific dialogue history 130 defines a plurality of concepts, e.g., concepts 130A through 130N. “Concept” is used herein to refer to any relevant or potentially relevant aspects of the interaction between the user and the automated assistant. For example, a concept may include an entity (e.g., a person, place, thing, number, date), …”
In regard to claim 10, Eisner also discloses:
10. The service provider system of claim 8, wherein prior to the training, the operations further comprise: generating training sequences of events from the training data and the network features; and converting the training sequences to vectors, wherein the training is performed using at least the vectors. ¶ 0019, “In some examples, the previously-trained code-generation machine 104 includes an encoder machine configured to encode the user utterance 102 as a semantic feature, e.g., a vector in a semantic vector space learned by the previously-trained code-generation machine 104.”
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to James D Rutten whose telephone number is (571)272-3703. The examiner can normally be reached M-F 9:00-5:30 ET.
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, Li B Zhen can be reached at (571)272-3768. 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.
/James D. Rutten/Primary Examiner, Art Unit 2121
Prosecution Insights