Obviousness

Under 35 U.S.C. § 103, a patent claim is considered obvious if the differences between the claimed invention and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art (POSA) to which the subject matter pertains. This analysis considers the scope and content of the prior art, differences between the prior art and the claims, the level of ordinary skill in the art, and any secondary considerations of non-obviousness.

Claims to be Analyzed:

The independent claims of US11539663 broadly cover a system and method for ingesting data into a cloud-based service from an external network. The core elements are:

• A midserver functioning as an interface between an external network and a cloud-based service.
• The midserver is configured to:
  1. Receive data from a plurality of computing devices on the external network.
  2. Run one or more containerized services to process the received data.
  3. Securely transmit the processed data to a cloud-based service.

Prior Art Identified:

1. US15/229,476 (Priority Date: August 5, 2016, claiming priority to October 28, 2015): Titled "HIGHLY SCALABLE DISTRIBUTED CONNECTION INTERFACE FOR DATA CAPTURE FROM MULTIPLE NETWORK SERVICE SOURCES." This patent application is explicitly listed in the priority chain of US11539663.
2. General Knowledge of Containerization Technology (as of October 28, 2015): Technologies such as Docker were well-established and widely adopted by the priority date, offering known benefits for deploying and managing software applications in modular, isolated, and scalable ways.
3. Background of US11539663: The patent itself describes the state of the art and the problems it seeks to solve, implicitly revealing what was known or desired in the field. These include challenges related to agent-based monitoring, managing numerous network connections, scalability, security, bandwidth, and supporting heterogeneous data sources [cite: "Discussion of the State of the Art" in US11539663].

Obviousness Analysis:

A person having ordinary skill in the art (POSA) in enterprise IT and cloud integration, by the priority date of October 28, 2015, would have found the claimed invention obvious by combining US15/229,476 with the general knowledge of containerization technology, motivated by the known problems in the field.

Combination of Prior Art References:

Primary Reference: US15/229,476, "HIGHLY SCALABLE DISTRIBUTED CONNECTION INTERFACE FOR DATA CAPTURE FROM MULTIPLE NETWORK SERVICE SOURCES."

• This reference describes a "connection interface for data capture from multiple network service sources." A POSA would understand this to be an intermediary server system, analogous to the "midserver" in US11539663, operating between an external network (with multiple computing devices/service sources) and a destination system (e.g., a cloud service, given the known trends in enterprise IT). This fulfills the aspects of a server acting as an interface and receiving data from a plurality of computing devices on the external network. The term "Highly Scalable" directly addresses problems with managing large numbers of data sources and connections, as highlighted in the background of US11539663 [cite: "Background of the Invention" in US11539663].

Secondary Reference/General Knowledge: The widespread adoption and known advantages of containerization technology (e.g., Docker, LXC) for deploying and managing diverse software applications as of October 2015.

Differences Between Claims and Combined Prior Art:

The primary difference is the explicit recitation of "running one or more containerized services to process the received data" on the intermediary server (midserver). While US15/229,476 describes an interface for data capture, it may not explicitly detail the use of containerized services for processing the data.

Motivation for a POSA to Combine the References:

A POSA, facing the challenges articulated in the background of US11539663, would have been motivated to combine the teachings of US15/229,476 with the general knowledge of containerization for the following reasons:

1. Addressing Scalability and Management Complexity: US11539663's background highlights issues with "thousands of computing devices sending data to a cloud-based service on separate connections" and the "overall number of connections to monitor at the business network edge increases substantially" with agent-based monitoring [cite: "Detailed Description" in US11539663]. An intermediary "connection interface" (from US15/229,476) would naturally serve to aggregate these connections. To manage the diverse data processing tasks required on such an interface (e.g., collection, aggregation, analysis, transformation, secure transmission), containerization offers a modular and efficient solution. Containers allow different processing components (like the "traffic processors, sensors, management services, and utilities" mentioned in US11539663) to run in isolation on the same server, simplifying deployment, updates, and resource allocation, thereby enhancing the "highly scalable" aspect of US15/229,476. [cite: "Detailed Description" in US11539663].

2. Handling Heterogeneous Data and Protocols: The patent notes that "not all devices support secure data transport," and that data might need to be "wrapped in a secure protocol before leaving the network." [cite: "Detailed Description" in US11539663]. A POSA implementing a data capture interface would recognize the need to handle various data formats and protocols. Deploying specialized services, such as Nginx for reverse proxying, system log containers, or messaging containers (as described in US11539663), as containerized services on the intermediary server, would be a logical and efficient approach to perform necessary data transformations like "compression, protocol wrapping, port bending" and ensure secure transmission to the cloud. [cite: "Detailed Description" in US11539663].

3. Enhanced Security and Resilience: US11539663 describes the midserver as a potential "cyber security target" and suggests it "may be designed to operate as a bastion host." [cite: "Detailed Description" in US11539663]. Containerization provides a layer of isolation, which would be an obvious choice for a POSA seeking to enhance the security of an intermediary server handling sensitive enterprise data. This isolation limits the impact of a potential compromise of one service and facilitates the enforcement of "least privilege" for access to individual containerized services, aligning with best security practices. [cite: "Detailed Description" in US11539663]. Furthermore, US11539663 states that "A midserver can mitigate this risk by providing traffic buffering in the event that the backhaul connection goes down." [cite: "Detailed Description" in US11539663]. Such buffering could be implemented as a containerized service, further motivating the use of containers for resilient data handling.

In conclusion, a POSA, motivated by the known problems in enterprise data management for cloud services (as detailed in US11539663's background) and the widely recognized benefits of containerization, would have found it obvious to implement the data processing functions of a scalable data capture interface (as described in US15/229,476) using containerized services for efficient, modular, secure, and flexible data ingestion and transmission to a cloud-based service.