CTNF 18/433,670 CTNF 86765 Notice of Pre-AIA or AIA Status 07-03-aia AIA 15-10-aia 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 The instant application having Application No. 18/433,670 filed on 2/06/2024 is presented for examination. Examiner Notes Examiner cites particular columns and line numbers in the references as applied to the claims below for the convenience of the applicant. Although the specified citations are representative of the teachings in the art and are applied to the specific limitations within the individual claim, other passages and figures may apply as well. It is respectfully requested that, in preparing responses, the applicant fully consider the references in entirety as potentially teaching all or part of the claimed invention, as well as the context of the passage as taught by the prior art or disclosed by the examiner. Drawings The applicant’s drawings submitted are acceptable for examination purposes. Authorization for Internet Communications The examiner encourages Applicant to submit an authorization to communicate with the examiner via the Internet by making the following statement (from MPEP 502.03): “Recognizing that Internet communications are not secure, I hereby authorize the USPTO to communicate with the undersigned and practitioners in accordance with 37 CFR 1.33 and 37 CFR 1.34 concerning any subject matter of this application by video conferencing, instant messaging, or electronic mail. I understand that a copy of these communications will be made of record in the application file.” Please note that the above statement can only be submitted via Central Fax, Regular postal mail, or EFS Web. Information Disclosure Statement As required by M.P.E.P. 609, the applicant’s submissions of the Information Disclosure Statement dated 2/07/2024 and 10/15/2025 are acknowledged by the examiner and the cited references have been considered in the examination of the claims now pending. Claim Rejections - 35 USC § 103 07-20-aia AIA 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. 07-21-aia AIA Claims 1-20 are rejecte d under 35 U.S.C. 103 as being unpatentable over Biwas (U S 2021/0133183) in view of Soderberg (US 2006/0248034). As per cl aim 1, Biwas discloses an integration platform system comprising: at least one computing device implementing a cloud environment (Paragraph 21 “Thus, a cloud provider network (or just “cloud”) typically refers to a large pool of accessible virtualized computing resources (such as compute, storage, and networking resources, applications, and services). A cloud can provide users with convenient, on-demand network access to a shared pool of configurable computing resources that can be programmatically provisioned and released in response to customer commands. These resources can be dynamically provisioned and reconfigured to adjust to variable load. Cloud computing can thus be considered as both the applications delivered as services over a publicly accessible network 106 (e.g., the Internet, a cellular communication network) and the hardware and software in cloud provider data centers that provide those services.”), the at least one computing device being programmed to execute: a database management system (Paragraph 20 “A provider network 100 (or, “cloud” provider network) provides users with the ability to utilize one or more of a variety of types of computing-related resources such as compute resources (e.g., executing virtual machine (VM) instances and/or containers, executing batch jobs, executing code without provisioning servers), data/storage resources (e.g., object storage, block-level storage, data archival storage, databases and database tables, etc.), network-related resources (e.g., configuring virtual networks including groups of compute resources, content delivery networks (CDNs), Domain Name Service (DNS)), application resources (e.g., databases, application build/deployment services), access policies or roles, identity policies or roles, machine images, routers and other data processing resources, etc.”) ; and an integration flow worker (Paragraph 41 “The controller 114, as part of the workflow, may also configure a load balancer 112, one or more routers 116A-116M, and the endpoint, so that the endpoint provides database statements (e.g., requests originated by clients that are destined to a database instance) to a database proxy instance (e.g., 120A), which may occur through the load balancer 112 to a router 116, which may identify a database proxy instance 120A, such as via an endpoint identifier of that where the database statement was received. The controller 114 may also configure a rule engine 141 of each database proxy instance 120 with rules to control how the database proxy instance 120A is to operate. The rules may be configured by the operator of the provider network 100 and/or by the user 102. For example, a user 102 may provide configuration data indicating if the user 102 wishes to pin certain client connections to certain database connections, and optionally an indication of how to determine which connections are to be so pinned (e.g., defining conditions of a client connections—such as the presence of a database statement that creates a prepared statement—that, when observed, are to cause the client connection to be pinned to a database connection). As another example, the user 102 may provide configuration data indicating if, when, and/or how to treat connections as being terminated (e.g., due to an amount of inactivity), whether connection multiplexing is to be enabled, whether pinning is to be enabled, what number of possible database connections may be utilized, whether (and/or how) to rewrite certain database statements, etc. During operation, each database proxy instance 120A may thus use this rule engine 141 and the associated rules to determine what operations to perform.”) , the integration flow worker comprising: an integration flow data source that is assigned an integration flow connection pool comprising a plurality of connections to the database management system (Paragraph 47 “The database proxy instance 120A may obtain a database connection 152 (between the proxy and the database instance) at circle (7) by opening a new database connection 152, identifying and thus selecting a database connection from a connection pool 145 of available open connections that matches the characteristics of the client connection, or update an existing connection from the pool 145 of open available connections to match an expected connection state for the client connection (e.g., by sending database statements/commands to the database instance to change a session state as described herein). In some embodiments, the database connection 152 may or may not be “pinned” to the client connection (i.e., dedicating it for that client's use) based on configured rules and/or thresholds, and further may be switched between being un-pinned (i.e., multiplexed) to pinned or between being pinned to un-pinned with similar rules and/or thresholds. When a particular client connection and database connection have been peered—either temporarily or when pinned—the database proxy instance 120A may update a peering map 143 data structure so that it can determine which connections are in use, which connections are peered, etc. In some embodiments, when a database connection that is in the pool 145 is selected and used, the database proxy instance 120A may thus remove that connection from the pool 145 (e.g., by removing an identifier of the connection, or updating a status flag associated with the connection, from the pool 145 structure) and/or update the peering map 143 to reflect the association of the connections.”); an internal data source that is assigned a reserved connection to the database management system (Paragraph 23 “Generally, the traffic and operations of a provider network may broadly be subdivided into two categories: control plane operations carried over a logical control plane and data plane operations carried over a logical data plane. While the data plane represents the movement of user data through the distributed computing system, the control plane represents the movement of control signals through the distributed computing system. The control plane generally includes one or more control plane components distributed across and implemented by one or more control servers. Control plane traffic generally includes administrative operations, such as system configuration and management (e.g., resource placement, hardware capacity management, diagnostic monitoring, system state information). The data plane includes customer resources that are implemented on the provider network (e.g., computing instances, containers, block storage volumes, databases, file storage). Data plane traffic generally includes non-administrative operations such as transferring customer data to and from the customer resources. The control plane components are typically implemented on a separate set of servers from the data plane servers, and control plane traffic and data plane traffic may be sent over separate/distinct networks.”); an internal service (Paragraph 17 “The database service may thus allow users to maintain predictable database performance by regulating the number of database connections that are opened and shedding unserviceable applications connections. The connection governance and management system can automatically perform management functions on behalf of its users, such as through automated provisioning, updating, scaling, and/or fault tolerance functionalities. Moreover, embodiments can scale capacity automatically in response to application load and can distribute workload across multiple fault-tolerance zones to minimize disruption from hardware or system failures.”) ; and a plurality of integration flows, a first integration flow of the plurality of integration flows configured to interface at least one message between a first software component and a second software component (Paragraph 26 “Generally, many types of modern computing applications rely on databases, and in particular, relational databases. Computing applications, such as websites or mobile application backends, may be implemented within a provider network 100 using one or more compute-type services 132 such as a hardware virtualization service or serverless code execution service, or in another location by one or more computing devices 105 (e.g., by applications executing in a data center, by applications executed by “client” devices such as personal computers, smart devices, mobile devices, etc.). At some point, these computing applications may use database functionality provided by one or more database instances 122A-122N of a database service 110 by sending messages carrying database statements (e.g., Structured Query Language (SQL) statements) to the database instance(s) 122A-122N, which can perform operations in response and optionally send back database results (e.g., status indicators, data stored by a database, data generated based on data stored by the database responsive to a query, etc.). In this manner, the computing applications act as a “client” application 130A-130B by requesting the database instance(s) 122A-122N to perform some operation(s) and thus act as a “server.”). Biwas does not expressly disclose but Soderberg discloses the integration flow worker being programmed to perform operations comprising: receiving, from the first integration flow, a first connection request for the database management system (Paragraph 36 “Many kinds of databases are in use. The first database model is widely attributed to Charles Bachman of General Electric in the early 1960's. This was called the Integrated Data Store, and followed the network data model. Later in the 1960's, IBM developed the Information Management System, which formed the basis for a hierarchical data model. In 1970, Edgar Codd of IBM proposed the relational data model, which proved to be a watershed in the development of database systems. The popularity of relational databases changed the commercial landscape. Their benefits were widely recognized, and the use of databases for managing corporate data became standard practice. While relational databases are the dominant model in use today, the various aspects of the invention are suitable for use in connection with any database presently in use or later developed that is capable of storing data of a plurality of data types. As described in the background section, this is particularly advantageous in the context of object-oriented data storage.”); assigning a first connection from the integration flow connection pool to the first integration flow (Paragraph 106 “In order to increase the level of reliability and responsibility, in one embodiment, the DAC of the invention executes on a separate (hidden) node with its own input/output (I/O) completion port and memory pool.”); receiving, from the internal service, a second connection request describing a second operation to be performed at the database management system (Paragraph 19 “On startup, database servers, such as SQL Server, allocate resources such as memory, threads, network ports to which the server will listen, etc. These resources are used during the regular execution of commands from different connections. In accordance with the invention, to enable a connection through the dedicated administrator connection (DAC), the server reserves some of these resources exclusively for use by this connection. In one embodiment, a pre-defined amount of memory, a few threads and a dedicated listener port are assigned, or reserved, for the DAC. When the administrator wants to makes use of this connection, the administrator initiates a request to connect to the assigned network port to which the assigned threads are listening. The request is then processed by the assigned threads.”) ; and assigning the reserved connection to the internal service (Paragraph 63 “Thus, in accordance with the invention, as illustrated in exemplary non-limiting detail in FIG. 3B, a database server may include a plurality of nodes N_1 to N_N with memory M_1 to M_N arranged accordingly. In accordance with the invention, a DAC Node D_N is provided having some pre-defined processing power and pre-defined memory M_DAC reserved in the overall system for a DAC node D_N, which uses the allocated resources to perform diagnostics on the other nodes N_1 to N_N. It should be noted that the invention is not limited to NUMA architectures, and that such NUMA description is provided merely for exemplary illustration of an embodiment of the invention. For instance, a DAC Node D_N is provided in accordance with the invention in non-NUMA implementations of the invention as well. For instance, in SMP architectures, a DAC node N_1 and an associated memory node M_1 are present, in addition to the DAC Node D_N.”). Therefore it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the method of Biwas to include the teachings of Soderberg because it enables diagnostic and administrative access when ordinary database connections fails. As per claim 2, Biwas further discloses the integration flow data source and the internal data source being accessible to the plurality of integration flows and the internal service via a common name data source (Paragraph 24 “To provide these and other computing resource services, provider networks 100 often rely upon virtualization techniques. For example, virtualization technologies may be used to provide users the ability to control or utilize compute instances (e.g., a VM using a guest operating system (O/S) that operates using a hypervisor that may or may not further operate on top of an underlying host O/S, a container that may or may not operate in a VM, an instance that can execute on “bare metal” hardware without an underlying hypervisor), where one or multiple compute instances can be implemented using a single electronic device. Thus, a user may directly utilize a compute instance (e.g., provided by a hardware virtualization service) hosted by the provider network to perform a variety of computing tasks. Additionally, or alternatively, a user may indirectly utilize a compute instance by submitting code to be executed by the provider network (e.g., via an on-demand code execution service), which in turn utilizes a compute instance to execute the code—typically without the user having any control of or knowledge of the underlying compute instance(s) involved.”). As per claim 3, Biwas further discloses the first connection request indicating that it is sent to the common name data source (Paragraph 96 “Conventionally, the provider network 1400, via the virtualization services 1410, may allow a customer of the service provider (e.g., a customer that operates one or more client networks 1450A-1450C including one or more customer device(s) 1452) to dynamically associate at least some public IP addresses 1414 assigned or allocated to the customer with particular resource instances 1412 assigned to the customer. The provider network 1400 may also allow the customer to remap a public IP address 1414, previously mapped to one virtualized computing resource instance 1412 allocated to the customer, to another virtualized computing resource instance 1412 that is also allocated to the customer. Using the virtualized computing resource instances 1412 and public IP addresses 1414 provided by the service provider, a customer of the service provider such as the operator of customer network(s) 1450A-1450C may, for example, implement customer-specific applications and present the customer's applications on an intermediate network 1440, such as the Internet. Other network entities 1420 on the intermediate network 1440 may then generate traffic to a destination public IP address 1414 published by the customer network(s) 1450A-1450C; the traffic is routed to the service provider data center, and at the data center is routed, via a network substrate, to the local IP address 1416 of the virtualized computing resource instance 1412 currently mapped to the destination public IP address 1414. Similarly, response traffic from the virtualized computing resource instance 1412 may be routed via the network substrate back onto the intermediate network 1440 to the source entity 1420.”). As per claim 4, Biwas further discloses the operations further comprising: receiving, from the internal service, a third connection (Paragraph 30 “For example, many applications have unpredictable workloads. Applications that support highly variable workloads may attempt to open a burst of new database connections to support surges. The DCMGS's 150 connection governance functionalities can allow users to gracefully scale applications dealing with unpredictable workloads by efficiently using database connections. The DCMGS 150 can reutilize established database connections to serve queries or transactions from multiple application requests. Thus, users can support more application connections over fewer database connections, providing the efficient use of database resources. The DCMGS 150 can allow users to maintain predictable database performance by regulating the number of database connections that are opened. In some embodiments, the DCMGS 150 can shed unserviceable application requests to preserve the overall performance and availability of the application.”); determining that the reserved connection to the database management system is unavailable (Paragraph 30); determining that the integration flow connection pool meets a threshold condition (Paragraph 47 “The database proxy instance 120A may obtain a database connection 152 (between the proxy and the database instance) at circle (7) by opening a new database connection 152, identifying and thus selecting a database connection from a connection pool 145 of available open connections that matches the characteristics of the client connection, or update an existing connection from the pool 145 of open available connections to match an expected connection state for the client connection (e.g., by sending database statements/commands to the database instance to change a session state as described herein). In some embodiments, the database connection 152 may or may not be “pinned” to the client connection (i.e., dedicating it for that client's use) based on configured rules and/or thresholds, and further may be switched between being un-pinned (i.e., multiplexed) to pinned or between being pinned to un-pinned with similar rules and/or thresholds. When a particular client connection and database connection have been peered—either temporarily or when pinned—the database proxy instance 120A may update a peering map 143 data structure so that it can determine which connections are in use, which connections are peered, etc. In some embodiments, when a database connection that is in the pool 145 is selected and used, the database proxy instance 120A may thus remove that connection from the pool 145 (e.g., by removing an identifier of the connection, or updating a status flag associated with the connection, from the pool 145 structure) and/or update the peering map 143 to reflect the association of the connections.”) ; and responsive to determining that the integration flow connection pool meets a threshold condition, assigning a connection of the integration flow connection pool to the internal service (Paragraph 47). As per claim 5, Biwas further discloses the determining that the integration flow connection pool meets the threshold condition comprising determining that less than a threshold portion of the plurality of connections of the integration flow connection pool are being used (Paragraph 47). As per claim 6, Biwas further discloses the operations further comprising, after assigning the connection of the integration flow connection pool, returning the connection to the integration flow connection pool (Paragraph 21 “Thus, a cloud provider network (or just “cloud”) typically refers to a large pool of accessible virtualized computing resources (such as compute, storage, and networking resources, applications, and services). A cloud can provide users with convenient, on-demand network access to a shared pool of configurable computing resources that can be programmatically provisioned and released in response to customer commands. These resources can be dynamically provisioned and reconfigured to adjust to variable load. Cloud computing can thus be considered as both the applications delivered as services over a publicly accessible network 106 (e.g., the Internet, a cellular communication network) and the hardware and software in cloud provider data centers that provide those services.”). As per claim 7, Soderberg further discloses the internal service being programmed to perform operations comprising generating the second connection request (Paragraph 24). As per claim 8, Soderberg further discloses the generating of the second connection request by the internal service comprising incorporating with the second connection request an indication that the second connection request is from an internal service (Paragraph 24) As per claim 9, Biwas further discloses the internal service utilizing the reserved connection to perform an operation at the database management system comprising at least one of: a request to write data describing performance of the integration flow worker; a request to write data regarding a relationship between a message received by at least one of the plurality of integration flows; a request to at the database management system; or a request describing a state of a timer (Paragraph 51 “Various types of state may be tracked in various embodiments depending on the particular types of database protocols in use. For example, the state may include system variables that have been set on a per-connection basis, including but not limited to a time zone value, a session timeout, a connection mode (e.g., read/write), a particular mode of interpretation the database uses (e.g., ANSI mode, traditional mode), etc. As another example, the state may include connection properties, including but not limited to a character set, a user name, whether the connection uses encryption, etc. As another example, the state may include database properties such as the existence of a temporary table or prepared statement (e.g., a SQL template) that was created during the connection (that may need to be referenced later).”). As per claims 10-18, they are method claims having similar limitations as cited in claims 1-9 and are rejected under the same rationale. As per claims 19-20, they are medium claims having similar limitations as cited in claims 1-3 and are rejected under the same rationale . Conclusion 07-96 AIA The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Wing (US 2017/0083386) discloses processing events generated by Internet of Things (IoT) devices. In particular, it relates to storing a machine-readable declarative specification of stateful event processing of an automated multi-step progression of monitoring of Internet of Things (IoT) devices that generate events. It includes compiling into tangible memory, in response to the declarative specification, a state processing network that implements a multi-step progression of monitoring events generated by the IoT devices. The state processing network implements both the time based transition triggers and the event based transition triggers after being initiated by the IoT devices. Further, data structures, which record monitoring status of particular IoT devices, are compiled. Finally, the state processing network further selects an alternative action to trigger, and triggers the selected action using at least some data from a particular event being processed. Any inquiry concerning this communication or earlier communications from the examiner should be directed to TIMOTHY A MUDRICK whose telephone number is (571)270-3374. The examiner can normally be reached 9am-5pm Central Time. 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, Pierre Vital can be reached at (571)272-4215. 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. /TIMOTHY A MUDRICK/Primary Examiner, Art Unit 2198 6/01/2026 Application/Control Number: 18/433,670 Page 2 Art Unit: 2198 Application/Control Number: 18/433,670 Page 3 Art Unit: 2198 Application/Control Number: 18/433,670 Page 4 Art Unit: 2198 Application/Control Number: 18/433,670 Page 5 Art Unit: 2198 Application/Control Number: 18/433,670 Page 6 Art Unit: 2198 Application/Control Number: 18/433,670 Page 7 Art Unit: 2198 Application/Control Number: 18/433,670 Page 8 Art Unit: 2198 Application/Control Number: 18/433,670 Page 9 Art Unit: 2198 Application/Control Number: 18/433,670 Page 10 Art Unit: 2198 Application/Control Number: 18/433,670 Page 11 Art Unit: 2198 Application/Control Number: 18/433,670 Page 12 Art Unit: 2198 Application/Control Number: 18/433,670 Page 13 Art Unit: 2198 Application/Control Number: 18/433,670 Page 14 Art Unit: 2198 Application/Control Number: 18/433,670 Page 15 Art Unit: 2198 Application/Control Number: 18/433,670 Page 16 Art Unit: 2198
Prosecution Insights