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 .
DETAILED ACTION
This communication is a Final Office Action in response to communications received on 1/29/26.
Claims 2, 5-6, 12, 15-16 have been canceled.
Claims 1, 11, 19 have been amended.
Therefore, Claims 1, 3-4, 7-11, 13-14, 17-20 are now pending and have been addressed below.
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 1, 3-4, 7-11, 13-14, 17-20 are rejected under 35 U.S.C. § 101 because the claimed invention is directed to a judicial exception (an abstract idea) without significantly more.
Step 1: Identifying Statutory Categories
In the instant case, claims 1, 3-4, 7-11, 13-14, 17-20 are directed to a system and claims 11, 13-15, 17-20 are directed to a system. Thus, the claims fall within one of the four statutory categories. Nevertheless, the claims fall within the judicial exception of an abstract idea.
Step 2A: Prong 1 Identifying a Judicial Exception
Under Step 2A, prong 1, Claims 1, 3-4, 7-11, 13-14, 17-20 are rejected under 35 U.S.C. 101 because the claimed invention recites an abstract idea without significantly more. Independent claims 1 and 11 recite methods directed to business process management including sending a first calling information comprising a first request information and a first response information to a business data course management; according to a first identifier loading a corresponding first extraction rule, so as to extract a first upstream business data type information, a first upstream business data identifier, a first downstream business data type information, and a first downstream business data type identifier comprising a first request information and a first response information from the first calling information according to the first extraction rule; wherein the first extraction rule describe how to extract data from the first calling information, creating a first upstream business data record according to the first upstream business data type information and the first upstream business data identifier; and creating a first downstream business data record according to the first downstream business data type information and the first downstream business data type identifier loads a corresponding second extraction rule, so as to extract a second upstream business data type information, a second upstream business data identifier, a second downstream business data type information, and a second downstream business data type identifier from the second calling information comprising a second request and a second response information according to the second extraction rule, wherein the second upstream business data type information and the second upstream business data identifier are identical to the first downstream business data type information and the first downstream business data type identifier; links the first downstream business data record and the second upstream business data record to generate a data set of business data records, sends a business data course search request to the business data course, the business data course traces the data set of business data records according to the business data course search request to return a searched business data record; the business data course management edits the first downstream business data record according to the second upstream business data type information and the second upstream business data identifier, and the business data course management creates a second downstream business data record according to the second downstream business data type information and the second downstream business data type identifier.
These limitations as drafted, are a process that, under its broadest reasonable interpretation, covers methods of organizing human activity (including commercial interactions such as business relations, managing personal behavior or relationships or interactions between people (including social activities, teaching, and following rules or instructions)), but for the recitation of generic computer components. That is, other than reciting the structural elements (such as a business data course management server, an electronic device, a first/second application programming interface, pre-defined algorithm), the claims are directed to creating business records based on extraction rules. If a claim limitation, under its broadest reasonable interpretation, covers performance of the limitation of organizing human activity but for the recitation of generic computer components, the claim recites an abstract idea.
Step 2A Prong 2 - This judicial exception is not integrated into a practical application because the claim merely describes how to generally “apply” the concept of receiving data, analyzing it, and providing business record. In particular, the claims only recites the additional element – as a business data course management server, an electronic device, a first/second application programming interface, pre-defined algorithm. These additional elements are recited at a high-level of generality such that it amounts to no more than mere instructions to apply the exception using a generic computer component. Simply implementing the abstract idea on generic components is not a practical application of the abstract idea. Accordingly, these additional element does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea. a) additional elements merely add the words “apply it” (or an equivalent) with the judicial exception, or mere instructions to implement an abstract idea on a computer, or merely uses a computer as a tool to perform an abstract idea, as discussed in MPEP 2106.05(f).
The claims are directed to an abstract idea. When considered in combination, the claims do not amount to improvements to the functioning of a computer, or to any other technology or technical field, as discussed in MPEP 2106.05(a), applying the judicial exception with, or by use of, a particular machine, as discussed in MPEP 2106.05(b), effecting a transformation or reduction of a particular article to a different state or thing, as discussed in MPEP 2106.05(c), or applying or using the judicial exception in some other meaningful way beyond generally linking the use of the judicial exception to a particular technological environment, such that the claim as a whole is more than a drafting effort designed to monopolize the exception, as discussed in MPEP 2106.05(e). Accordingly, the additional elements do not integrate the abstract idea into a practical application because they does not impose any meaningful limits on practicing the abstract idea. Therefore, the claims are directed to an abstract idea.
Step 2B: Considering Additional Elements
The claimed invention is directed to an abstract idea without significantly more. The claim does not include additional elements that are sufficient to amount significantly more than the judicial exception. As discussed above with respect to integration of the abstract idea into a practical application, the claims describe how to generally “apply” to; creating business records based on extraction rules. The claim(s) do not include additional elements that are sufficient to amount to significantly more than the judicial exception because mere instructions to apply an exception using a generic computer component cannot provide an inventive concept. The independent claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception. Even when viewed as a whole, nothing in the claim adds significantly more (i.e., an inventive concept) to the abstract idea. The claims are not patent eligible. The dependent claim(s) when analyzed as a whole are held to be patent ineligible under 35 U.S.C. 101 because the additional recited limitation(s) fail to establish that the claim(s) is/are not directed to an abstract idea. The dependent claims are not significantly more because they are part of the identified judicial exception. See MPEP 2106.05(g). The claims are not patent eligible. With respect to the as a business data course management server, an electronic device, a first/second application programming interface, pre-defined algorithm, these limitations are described in Applicant’s own specification as generic and conventional elements. See Applicants specification, Paragraph [0017] details “ The electronic device 120 includes a transmitting unit 121. In this embodiment, the electronic device 120 may be, for instance, a personal computer (PC), a tablet, a server, or any other computing device capable of performing computing functions, and the electronic device 120 is connected to the business data course management server 110. [0007] creating a corresponding business data course according to a calling result of each API service operated by a user [0018] a user may call an API by operating the electronic device 120, [0019]general purpose processor. [0020] the user may operate the electronic device 120 to call a first API first to obtain a first calling information (calling result). The extraction rule is set according to a pre-defined algorithm and is adapted to describe how to extract required data from the calling information of the API [0022] the user may operate the electronic device 120 and then call a second API to obtain a second calling information (calling result)”.
These are basic computer elements applied merely to carry out data processing such as, discussed above, receiving, analyzing, transmitting and displaying data. Powers (US2021/0294718) teaches various API’s (Fig 2A #1000 API dispatch, 1004b) Furthermore, the use of such generic computers to receive or transmit data over a network has been identified as a well understood, routine and conventional activity by the courts. See Symantec, 838 F.3d at 1321, 120 USPQ2d at 1362 (utilizing an intermediary computer to forward information); TLI Communications LLC v. AVAuto. LLC, 823 F.3d 607, 610, 118 USPQ2d 1744, 1745 (Fed. Cir. 2016) (using a telephone for image transmission); Presenting offers and gathering statistics, OIP Techs., 788 F.3d at 1362-63, 115 USPQ2d at 1092-93, OIP Techs., Inc., v. Amazon.com, Inc., 788 F.3d 1359, 1363, 115 USPQ2d 1090, 1093 (Fed. Cir. 2015) (sending messages over a network); buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355, 112 USPQ2d 1093, 1096 (Fed. Cir. 2014) (computer receives and sends information over a network); but see DDR Holdings, LLC v. Hotels.com, L.P., 773 F.3d 1245, 1258, 113 USPQ2d 1097, 1106 (Fed. Cir. 2014) ("Unlike the claims in Ultramercial, the claims at issue here specify how interactions with the Internet are manipulated to yield a desired result-a result that overrides the routine and conventional sequence of events ordinarily triggered by the click of a hyperlink." (emphasis added)); Also see MPEP 2106.05(d) discussing elements that the courts have recognized as well-understood, routine and conventional activities in particular fields. Lastly, the additional elements provides only a result-oriented solution which lacks details as to how the computer performs the claimed abstract idea. Therefore the additional elements amount to mere instructions to apply the exception. See MPEP 2106.05(f).
Furthermore, these steps/components are not explicitly recited and therefore must be construed at the highest level of generality and amount to mere instructions to implement the abstract idea on a computer. Therefore, the claimed invention does not demonstrate a technologically rooted solution to a computer-centric problem or recite an improvement to another technology or technical field, an improvement to the function of any computer itself, applying the exception with, or by use of, a particular machine, effect a transformation or reduction of a particular article to a different state or thing, add a specific limitation other than what is well-understood, routine and conventional in the field, add unconventional steps that confine the claim to a particular useful application, or provide meaningful limitations beyond generally linking an abstract idea to a particular technological environment such as computing. Viewing the limitations as an ordered combination does not add anything further than looking at the limitations individually. Taking the additional claimed elements individually and in combination, the computer components at each step of the process perform purely generic computer functions. Viewed as a whole, the claims do not purport to improve the functioning of the computer itself, or to improve any other technology or technical field. Use of an unspecified, generic computer does not transform an abstract idea into a patent-eligible invention. Thus, the claim does not amount to significantly more than the abstract idea itself.
Dependent claims 3-5, 7-10 and 13-15, 17-20 add additional limitations, for example but these only serve to further limit the abstract idea, and hence are nonetheless directed towards fundamentally the same abstract idea as representative claims 1 and 11.
Claims 3-4, 7-8, 13-14, 17-18 recites wherein the first calling information comprises a first request information and a first response information; records a first downstream associated information and a calling history of the first application programming interface into the first upstream business data record; records a first upstream associated information into the first downstream business data record; wherein the second calling information comprises a second request information and a second response information; records a second downstream associated information and a calling history of the second application programming interface into the first downstream business data record; records a first upstream associated information into the second downstream business data record. These limitations further narrow the abstract idea of a user using a computer as a tool to interact with the business data course management system. Claims 5, 15 recite similar limitations to claims 1 and 11. In addition, the claims recite additional element of a second API at high level of generality. Claims 9-10 and 19-20 recites receives a business data course search request, the business data course management server reads at least one upstream business data record or at least one downstream business data record according to a current business data type information and a current business data identifier in the business data course search request and traces the at least one upstream business data record or the at least one downstream business data record according to the business data course search request until data of a target business data type are found.
These limitations of merely adds the words apply it (or an equivalent) with the judicial exception , or mere instructions to implement an abstract idea on a computer, or merely uses a computer as a tool to perform an abstract idea as discussed in MPEP 2106.05(f). The receiving function is similar to a data gathering function. The dependent claims do not integrate into a practical application. As such, the additional elements individually or in combination do not integrate the exception into a practical application, but rather, the recitation of any additional element amounts to merely reciting the words “apply it” (or equivalent) with the judicial exception, or merely includes instructions to implement an abstract idea on a computer, or merely uses a computer as a tool to perform an abstract idea (See MPEP 2106.05(f)). The dependent claims also do not include additional elements that are sufficient to amount to significantly more than the judicial exception. As discussed above with respect to integration of the abstract idea into a practical application, the additional elements of a computing system is merely being used to apply the abstract idea to a technological environment. These limitations do not include an improvement to another technology or technical field, an improvement to the functioning of the computer itself, or meaningful limitations beyond generally linking the use of the abstract idea to a particular technological environment. See MPEP 2106.05d. Thus, the claims do not add significantly more to an abstract idea. The claims are ineligible. Therefore, since there are no limitations in the claim that transform the exception into a patent eligible application such that the claim amounts to significantly more than the exception itself, the claims are rejected under 35 USC 101 as being directed to non-statutory subject matter. See (Alice Corporation Pty. Ltd. v. CLS Bank International, et al.).
Examiner Note: Subject matter free of prior art
Regarding claims 1 and 11, Yin et al. (US 2023/0074740 A1) discloses the business data course management system (Abstract lines 1-2 an order data model for structuring data records in an order management system), comprising:
Yin discloses a business data course management server (Fig 1 # 130 order management system, [0020] The data model is operable in a processor (server) of an order management system for structuring data, the order management system is configured to manage product and/or service orders placed by users via a plurality of digital data channels); and an electronic device, connected to the business data course management server (Fig 2 # 136 processor, [0066] A processor 136 is provided to process offer records received from the offer management system 120 and/or product/service orders received from one of the digital sale channels 110 ),
Yin discloses wherein after the electronic device receives a call request and completes calling a first application programming interface, the electronic device sends a first calling information comprises a first request information and a first response information. (Fig 8 #110, 130 open order API (first calling information for API) and [0070] the order management system 130 is connected to a plurality of touchpoints 110, which are used by the users to place and manage orders. The orders generated at the touchpoints 110 are pushed in the form of event messages (a first request information) to the order management system 130, where the individual order items and corresponding sub-items contained in the order are extracted, and corresponding order item data record 231 and sub-item data records 331 are generated (a first response information), each linked to the main order data record 131. Fig 9 open API, 1352 service access module and [0071] the service access module 1352 is configured to provide access to connected service provider systems, via application programming interfaces (API), to the data records stored in the data module 132. The order processing module 136 is configured to process the input data streams received at the ignition module 1351 and commands issued at the access service module 1352, and accordingly perform the requested actions in the data module 132 e.g. generate new order data records 131 and corresponding fulfilment data records, and/or manage existing order data records 131, and the like. The order processing module 136 is configured to transmit order data to the assigned fulfilment provider 190, and/or other systems. , [0063] The order may have associated terms “Term: Refundable” and “Term: Refund penalty: 50 euro”. If the order is cancelled, the OMS will check the conditions to determine whether it can pass from the state “cancelled” to the state “refunded”.) corresponding to the first application programming interface to the business data course management server (Fig 8 #110, 130 open order API (call request, first calling information for API) and [0070] the order management system 130 is connected to a plurality of touchpoints 110, which are used by the users to place and manage orders. The orders generated at the touchpoints 110 are pushed in the form of event messages (API) to the order management system 130, Fig 9 open API, 1352 service access module and [0071] the service access module 1352 is configured to provide access to connected service provider systems, via application programming interfaces (API), to the data records stored in the data module 132., [0073] each service provided may initiate, via an API, a read request to retrieve data from a data container of the data layer. As such the data layer is configured to aggregate data from different data domains of the airline commercial platform 100 e.g. order domain, payment domain, offer domain, into a consolidated order representation, as shown in FIG. 12), and
Yin discloses according to a first application programming interface identifier corresponding to the first application programming interface (Fig 8 # 110, 130 open order API (identifier)), the business data course management server loads conditions/rules to extract a first upstream business data type information, a first upstream business data identifier ([0022] terms of service (rules) specify actions to be taken when certain conditions are activated, [0038] process each order input data to extract order data such as information on the order items, order sub items to generate record, [0066]extract information on the order items, sub items and contractual terms[0070] The orders generated at the touchpoints 110 are pushed in the form of event messages (upstream business data type information) to the order management system 130, where the individual order items (a first upstream business data type information) and corresponding sub-items (a first upstream business data identifier) contained in the order are extracted, and corresponding order item data record 231 and sub-item data records 331 are generated , each linked to the main order data record 131. [0073] each service provided may initiate, via an API, a read request to retrieve data from a data container of the data layer. As such the data layer is configured to aggregate data from different data domains of the airline commercial platform 100 e.g. order domain, payment domain, offer domain, into a consolidated order representation, as shown in FIG. 12, [0027] the contractual terms of service in each corresponding data record are in the form of an extensible mark-up language. For example, every term and/or condition may be represented by a key and a value.),
Yin discloses a first downstream business data type information, and a first downstream business data type identifier from the first request and the first response information ([0070]The order management system 130 is communicatively coupled with a range of peripheral systems, such as an airline passenger service system (PSS) acting as service provider 190, and a central data integration hub 160. The central data integration hub 160 is configured to receive notifications from the service providers 190 associated with the fulfilment of an order sub-item, and further may be communicatively coupled to partner systems 250 e.g. airport systems, air traffic systems, payment systems, and the like. (a first downstream business data type identifier, [0071] The ingestion module 1351 is configured to process the input data streams to event events associated with order data records 131, such as a change of an order item (downstream business data type), an error in fulfilment status (downstream business type identifier), the generation new order item, and the like. [0073] each service provided may initiate, via an API, a read request to retrieve data from a data container of the data layer. As such the data layer is configured to aggregate data from different data domains of the airline commercial platform 100 e.g. order domain, payment domain, offer domain (downstream business data), into a consolidated order representation, as shown in FIG. 12),
Yin discloses wherein the business data course management server creates a first upstream business data record according to the first upstream business data type information and the first upstream business data identifier ([0070]The orders generated at the touchpoints 110 are pushed in the form of event messages to the order management system 130, where the individual order items and corresponding sub-items contained in the order are extracted, and corresponding order item data record 231 and sub-item data records 331 are generated (creating upstream business record), each linked to the main order data record 131.) and creates a first downstream business data record according to the first downstream business data type information and the first downstream business data type identifier. ([0070] The central data integration hub 160 is configured to gather the data of interest from different systems and feed the information, in the form of feedback to the order management system 130 (creating a fist downstream business data record), where the feedback information is processed to determine the fulfilment status of an order sub-item and/or react to events that may affect the fulfilment of an order sub-item. For example, the airline PSS 190 may be configured for receiving the fulfilment item data records 241 for fulfilment and accordingly generate notifications associated with the fulfilment status of each fulfilment item data record 241, which are communicated to the central data integration hub 160, whereby they are aggregated with additional information collected from partner systems 250. The information collected by the central data integration hub 160 is fed back to the order management system 130 for further processing, which may include checking the fulfilment status, identifying changes/errors, initiating actions, and others., [0073] each service provided may initiate, via an API, a read request to retrieve data from a data container of the data layer. As such the data layer is configured to aggregate data from different data domains of the airline commercial platform 100 e.g. order domain, payment domain, offer domain (downstream business data), into a consolidated order representation)
Yin teaches wherein after the electronic device completes calling a second application programming interface, the electronic device sends a second calling information comprises a second request information and a second response information. (Fig 9 open API (second calling information for API) and [0070] the order management system 130 is connected to a plurality of touchpoints 110, which are used by the users to place and manage orders. The orders generated at the touchpoints 110 are pushed in the form of event messages (a second request information) to the order management system 130, where the individual order items and corresponding sub-items contained in the order are extracted, and corresponding order item data record 231 and sub-item data records 331 are generated (a second response information), each linked to the main order data record 131. Fig 9 open API, 1352 service access module and [0071] the service access module 1352 is configured to provide access to connected service provider systems, via application programming interfaces (API), to the data records stored in the data module 132. The order processing module 136 is configured to process the input data streams received at the ignition module 1351 and commands issued at the access service module 1352, and accordingly perform the requested actions in the data module 132 e.g. generate new order data records 131 and corresponding fulfilment data records, and/or manage existing order data records 131, and the like. The order processing module 136 is configured to transmit order data to the assigned fulfilment provider 190, and/or other systems.) corresponding to the second application programming interface to the business data course management server (Fig 8 #110, 130 open order API (second calling information for API) and [0070] the order management system 130 is connected to a plurality of touchpoints 110, which are used by the users to place and manage orders. The orders generated at the touchpoints 110 are pushed in the form of event messages (API) to the order management system 130, Fig 9 open API (second calling), (second API) 1352 service access module and [0071] the service access module 1352 is configured to provide access to connected service provider systems, via application programming interfaces (API), to the data records stored in the data module 132., [0073] each service provided may initiate, via an API, a read request to retrieve data from a data container of the data layer. As such the data layer is configured to aggregate data from different data domains of the airline commercial platform 100 e.g. order domain, payment domain, offer domain, into a consolidated order representation, as shown in FIG. 12, [0035] The order management system is configured to manage product or service orders placed by users via a plurality of digital data channels),
Yin teaches according to a second application programming interface identifier corresponding to the second application programming interface (Fig 9 open API service access path), the business data course management server loads rule/condition, to extract a second upstream business data type information([0070] The orders generated at the touchpoints 110 are pushed in the form of event messages (upstream business data type information) to the order management system 130, where the individual order items (a second upstream business data type information) and corresponding sub-items (a second upstream business data identifier) contained in the order are extracted, and corresponding order item data record 231 and sub-item data records 331 are generated , each linked to the main order data record 131. [0071] The ingestion module 1351 is configured to process the input data streams to extract events associated with order data records 131, such as a change of an order item, an error in fulfilment status, the generation new order item, and the like. [0073] each service provided may initiate, via an API, a read request to retrieve data from a data container of the data layer. As such the data layer is configured to aggregate data from different data domains of the airline commercial platform 100 e.g. order domain, payment domain, offer domain, into a consolidated order representation, as shown in FIG. 12, [0027] the contractual terms of service in each corresponding data record are in the form of an extensible mark-up language. For example, every term and/or condition may be represented by a key and a value.),,
Yin teaches a second upstream business data identifier, a second downstream business data type information, and a second downstream business data type identifier from the second calling information ([0070]The order management system 130 is communicatively coupled with a range of peripheral systems, such as an airline passenger service system (PSS) acting as service provider 190, and a central data integration hub 160. The central data integration hub 160 is configured to receive notifications from the service providers 190 associated with the fulfilment of an order sub-item, and further may be communicatively coupled to partner systems 250 e.g. airport systems, air traffic systems, payment systems, and the like. (a second downstream business data type identifier), [0071] The ingestion module 1351 is configured to process the input data streams to event events associated with order data records 131, such as a change of an order item (downstream business data type), an error in fulfilment status (downstream business type identifier), the generation new order item, and the like. [0073] each service provided may initiate, via an API, a read request to retrieve data from a data container of the data layer. As such the data layer is configured to aggregate data from different data domains of the airline commercial platform 100 e.g. order domain, payment domain, offer domain (downstream business data), into a consolidated order representation, as shown in FIG. 12),
Yin teaches wherein the second upstream business data type information and the second upstream business data identifier are identical to the first downstream business data type information and the first downstream business data type identifier ([[0055] receiving monitoring data from a central data integration hub associated with the fulfilment status of the data fulfilment object (second upstream business type (fulfilment) and data identifier (fulfilment object)); [0056] determining based on monitoring data and/or input data received from the touchpoints a change and/or an error in the fulfilment status; [0059] The order is processed and for each data sub-item a data fulfilment object is created which is communicated to an assigned provider. The status of the fulfilment is monitored to detect changes and/or errors that may violate the contractual conditions applied to the data object. Similarly, changes to an existing order may be received, which need to be checked for violation of the contractual conditions)
Yin teaches wherein the business data course management server links the first business data record and the second business data record ([0025] the present data model enables the linkage of each of the fulfilment item data records with a corresponding contractual term of service, specifying the terms and conditions agreed between the parties for the provision of the product or service at the purchase of the product or service., [0059] input data containing a data object associated with an order for product and/or service placed by a user at a digital touchpoint. Each data object comprising one or more data items associated with the order items of the order., [0068]). Yin further teaches service provider access the stored data and retrieve data from a data container of the data layer ([0073], [0071] the service access module 1352 is configured to provide access to connected service provider systems, via application programming interfaces (API), to the data records stored in the data module 132. Furthermore, the access service module 1352 enables service providers to manage their orders and view their fulfilment status. For example, via the access service module 1352, a service provider may issue a request for a change in an order item and/or an order sub-item. The order processing module 136 is configured to process the input data streams received at the ignition module 1351 and commands issued at the access service module 1352, and accordingly perform the requested actions in the data module 132 e.g. generate new order data records 131 and corresponding fulfilment data records, and/or manage existing order data records 131, and the like. ).
Yin teaches wherein the business data course management server monitors the first downstream business data record ([0042] upon registering a change and/or an error in the status of the fulfilment item data record, to identify and retrieve from the corresponding order sub-item data record the contractual terms of service to determine the conditions that need to be checked following the change and/or fulfilment error and initiate, based on the retrieved terms of service, a set of corresponding actions associated with the fulfilment status information,
Yin does not specifically teach the business data course management server loads a corresponding first extraction rule; extracting a first downstream business data type information downstream business data type identifier from the first calling information according to the first extraction rule; wherein the first extraction rule is set according to a pre-defined algorithm and is adapted to describe how to extract data from the first calling information of the first application programming interface. Yin however discloses conditions/terms of service for order ([0063], [0067]flexible rules for defining service)
Powers (US 2021/0294718 A1), teaches the business data course management server loads a corresponding first extraction rule ([0053] the services called and utilized during data processing for a particular correlations ID may be identified (extraction rules) and the order and/or flow through the services may be determined. The data flows may therefore identify how data is processed by the service provider's services and how the APIs of those services interact to process data (extraction rules). The data flows may also be associated with particular data parameters that are processed, which may be identified based on tags or metadata on nodes of the services.); extracting a first downstream business data type information downstream business data type identifier from the first calling information according to the first extraction rule (Fig 2C #200c payment serv auth call count and #1204 calls fulfilmentintervalserv, slingshotserver api for geo location AND [0048]-[0049] within environment 200c, two different iterations of the callstack data show divergent data processing flows based on the particular data parameters that go through an API. In this regard, callstack 1200 includes an authorize tag 1202 (upstream) that occurs when a transaction proceeds through an authorize data flow, such as to authorize and/or authenticate a user for transaction processing.) wherein the first extraction rule is set according to a pre-defined algorithm and is adapted to describe how to extract data ([0035] Flow mapping module 122 (first extraction rule) may correspond to one or more processes to execute software modules (pre-defined algorithm) and associated specialized hardware of service provider server 120 to determine data processing flows using services 132 based on unique identifiers (e.g., correlation IDs) assigned to data processing transactions when the transactions enter the system of service provider applications 130. For example, as a transaction is first initiated with service provider applications 130 for processing, a correlation ID may be assigned to the transaction, and callstack data (extraction rule) generated by APIs of services 132 may store the correlation IDs with data associated with processing the transaction. Flow mapping module 122 may utilize the correlation IDs to map data flows by accessing the callstack data and determine one or more of services 132 used to process the transaction, and the order of use of services 132 (how to extract data), using the correlation IDs.)
Yin does not specifically teach the business data course management server loads a corresponding second extraction rule; extracting a second downstream business data type information downstream business data type identifier from the second calling information according to the second extraction rule; wherein the first extraction rule is set according to a pre-defined algorithm and is adapted to describe how to extract data from the first calling information of the first application programming interface;
Powers (US2021/0294718) teaches the business data course management server loads a corresponding second extraction rule ([0053] the services called and utilized during data processing for a particular correlations ID may be identified and the order and/or flow through the services may be determined (extraction rule). The data flows may therefore identify how data is processed by the service provider's services and how the APIs of those services interact to process data. The data flows (extraction rules) may also be associated with particular data parameters that are processed, which may be identified based on tags or metadata on nodes of the services.); extracting a second downstream business data type information downstream business data type identifier from the second calling information according to the second extraction rule (Fig 2C #200c payment serv auth call count and #1204 calls fulfilmentintervalserv, slingshotserver api for geo location AND [0048]-[0049] within environment 200c, two different iterations of the callstack data show divergent data processing flows based on the particular data parameters that go through an API. In this regard, callstack 1200 includes an authorize tag 1202 (upstream) that occurs when a transaction proceeds through an authorize data flow, such as to authorize and/or authenticate a user for transaction processing). Further, powers teaches various API’s (Fig 2A #1000 API dispatch, 1004b)
Oliner (US 11,853,303 B1) teaches wherein the first extraction rule is set according to a pre-defined algorithm and is adapted to describe how to extract data from the first calling information of the first application programming interface (Col 6 lines 16-22 a field is defined by an extraction rule (e.g., a regular expression) that derives one or more values or a sub-portion of text from the portion of machine data in each event to produce a value for the field for that event. The set of values produced are semantically-related (such as IP address), even though the machine data in each event may be in different formats (e.g., semantically-related values may be in different positions in the events derived from different sources), Col 6 lines 56-65 applying extraction rules to events to extract values for specific fields during search time. More specifically, the extraction rule for a field can include one or more instructions that specify how to extract a value for the field from an event. An extraction rule can generally include any type of instruction for extracting values from events. In some cases, an extraction rule comprises a regular expression, where a sequence of characters form a search pattern.)
Hart et al (US 10,191,987B2) teaches wherein when the electronic device sends a business data course search request to the business data course management server (Col 1 lines 49-60 receive a user request for information associated with one or more transactions in the form of a search query, transmit the search query to a transaction search engine for identification of one or more concepts from the search query, and receive, from the transaction search engine, responsive transaction data determined based on the one or more concepts identified from the search query. Col 3 lines 12-17 a transaction search engine may search stored financial data to determine a result of a search query. The transaction search engine may be configured to interpret a received search query to determine the concepts, if any, that are implicated by the search query, Col 14 lines 30-34 FIG. 7, the search query 780 includes the word “starbucks” entered by user 112, for example. Transaction search engine 236 may receive the search query. Transaction search engine 236 may be configured to determine a result by parsing the search query 780 (e.g., via parsing engine 310) to parse terms/phrases of the search query (in this example, only “starbucks”) and identify concepts associated with the parsed terms/phrases (for example, “coffee shop”) (upstream)., Fig 8 # 810-840 apply the search query and generate results Col 23 lines 36-40 For example, transaction search engine 326 may communicate with another component of financial service provider (e.g., via a deals API) to return deals and offers (downstream) that may be associated with the information provided in the results report)
Nair (US 2022/0342733A1) discloses system determines which user action steps cause API invocations to non-edge cloud servers and generates a sequence of API invocations in an order associated with the sequence of user action steps of the customer journey. The sequence of API invocations may be chained and/or bundled and stored in a cache for replication at edge cloud servers
Thompson (US 12,0173,263B1) teaches wherein when the business data course management server receives a business data course search request (Col 1 lines 14-16 an API execution environment can receive from users a number of API requests associated with a particular API of a customer, in a format specified by the API. Col 1 lines 57-30 dynamic processing of API requests received by an API execution service in an API execution environment. The API execution service may map out a dependency graph based on the dependency relationships between actions involved in processing a particular type of API request, some of which can be determined from the API definitions and configurations. Col 3 lines 59-64 a user may operate a web browser or application on a smartphone (e.g., the user computing device), and that web browser or application may send an API request to the API execution service 110 (e.g., to use an API associated with a particular customer, Col 1 lines 59-67 The API execution service may map out a dependency graph based on the dependency relationships (upstream or downstream) between actions involved in processing a particular type of API request, some of which can be determined from the API definitions and configurations. From the dependency graph, an execution plan can be generated that represents a request processing pipeline conveying the ideal or optimal order and arrangement to perform the actions (e.g., serially, in parallel). The execution plan can be followed to process relevant API requests, and performance of the execution plan and/or its constituent actions can be monitored, Col 4 lines 62-67, Col 5 lines 1-3 the applications can send API requests to the API execution service 110 in order to obtain access to business logic, data (e.g., stored through data storage services 124), functionality (e.g., from the backend services 120), and so forth, as defined and permitted by the API.))
NPL, Jing, “IT implementation module study on system of supply chain management”, 2008 discloses The information of the supply chain covers from all links of suppliers, manufacturers to distributors and then retailers in the supply chain. Information flow distinct into information flow of demand and supply, these are two different flows of information flow. When demand information (such as customer orders, production planning, procurement, etc.) takes direction from the demand-side to the supply-side movement, it triggered logistics. Meanwhile supply information (such as storage lists, the inventory records for sales, deliver lists), together again along with materials for the direction of the supply chain from supply-side to demand-side movement
However, the prior art fails to teach or suggest at least “wherein the business data course management server links the first downstream business data record and the second upstream business data record to generate a data set of business data records, wherein when the electronic device sends a business data course search request to the business data course management server, the business data course management server traces the data set of business data records according to the business data course search request to return a searched business data record to the electronic device, wherein the business data course management server edits the first downstream business data record according to the second upstream business data type information and the second upstream business data identifier, and the business data course management server creates a second downstream business data record according to the second downstream business data type information and the second downstream business data type identifier.”. The prior art teachings as recited above fail to set forth any sufficient rationale for combining or otherwise modifying any of the relevant prior art to arrive at the claimed invention, as a whole. Thus, the aforementioned combination of features claimed, as a whole, are not anticipated nor rendered obvious for any sufficient rationale by any of the prior art teachings. Furthermore, the prior art of record does not anticipate nor render obvious the combination of limitations for the dependent claims due to their respective dependencies to the independent claims 1 and 11.
Response to Arguments
Applicant's arguments filed 1/29/26 have been fully considered but they are not persuasive.
Regarding 101 rejection, applicant states claims are not directed to abstract idea and provide practical application. Further, applicant states claims provide improvement to technical field and integrate to a practical application. Examiner has considered all arguments and respectfully disagrees. The additional elements are recited at high level of generality and such that it amounts to no more than mere instructions to apply the exception using a generic computer component. Simply implementing the abstract idea on generic components is not a practical application of the abstract idea. Accordingly, these additional element does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea. Specification [0018] a user may call an API by operating the electronic device 120, [0019]general purpose processor. [0020] the user may operate the electronic device 120 to call a first API first to obtain a first calling information
Regarding remarks that amended claims provide technological improvements to a computer system by using API calls…” . The additional element such as API calls is recited at apply it level and relying on a computer to perform routine tasks more quickly or more accurately is insufficient to render a claim patent eligible. OIP Techs., Inc. v. Amazon.com, Inc., 788 F.3d 1359, 1363 (Fed. Cir. 2015). It is well-settled that mere recitation of concrete, tangible components is insufficient to confer patent eligibility to an otherwise abstract idea" where those components simply perform their "well-understood, routine, conventional" functions. In re TLI Commc'ns LLC Patent Litig., 823 F.3d 607, 613 (Fed. Cir. 2016). “The inclusion of a generic computer to automate activity or behavior that has long existed does not suffice to meaningfully restrict the … patent from preempting the abstract idea ….” Voxathon LLC v. Alpine Elecs. Of America, Inc., No. 2:15-cv00562, Op. at 8-9 (E.D. Tex. Jan. 21, 2016). ("But relying on a computer to perform routine tasks more quickly or more accurately is insufficient to render a claim patent eligible.").
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
CN111737270 discloses obtaining the business data of the upstream business system; based on the service data, determining the target service rule corresponding to the service data from the pre-configured service rule; detecting whether the service data is matched with the target service rule; under the condition that the service data is matched with the target service rule, based on the target service rule, driving the downstream service system to perform the subsequent service operation
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 SANGEETA BAHL whose telephone number is (571)270-7779. The examiner can normally be reached 7:30 - 4PM.
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, Jessica Lemieux can be reached on 571-270-3445. 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.
/SANGEETA BAHL/Primary Examiner, Art Unit 3626