Patent ID: 12254014

DETAILED DESCRIPTION

Example methods, devices, and systems are described herein. It should be understood that the words “example” and “exemplary” are used herein to mean “serving as an example, instance, or illustration.” Any embodiment or feature described herein as being an “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or features unless stated as such. Thus, other embodiments can be utilized and other changes can be made without departing from the scope of the subject matter presented herein.

Accordingly, the example embodiments described herein are not meant to be limiting. It will be readily understood that the aspects of the present disclosure, as generally described herein, and illustrated in the figures, can be arranged, substituted, combined, separated, and designed in a wide variety of different configurations. For example, the separation of features into “client” and “server” components may occur in a number of ways.

Further, unless context suggests otherwise, the features illustrated in each of the figures may be used in combination with one another. Thus, the figures should be generally viewed as component aspects of one or more overall embodiments, with the understanding that not all illustrated features are necessary for each embodiment.

Additionally, any enumeration of elements, blocks, or steps in this specification or the claims is for purposes of clarity. Thus, such enumeration should not be interpreted to require or imply that these elements, blocks, or steps adhere to a particular arrangement or are carried out in a particular order.

Unless clearly indicated otherwise herein, the term “or” is to be interpreted as the inclusive disjunction. For example, the phrase “A, B, or C” is true if any one or more of the arguments A, B, C are true, and is only false if all of A, B, and C are false.

I. Introduction

A large enterprise is a complex entity with many interrelated operations. Some of these are found across the enterprise, such as human resources (HR), supply chain, information technology (IT), and finance. However, each enterprise also has its own unique operations that provide essential capabilities and/or create competitive advantages.

To support widely-implemented operations, enterprises typically use off-the-shelf software applications, such as customer relationship management (CRM), IT service management (ITSM), IT operations management (ITOM), and human capital management (HCM) packages. However, they may also need custom software applications to meet their own unique requirements. A large enterprise often has dozens or hundreds of these custom software applications. Nonetheless, the advantages provided by the embodiments herein are not limited to large enterprises and may be applicable to an enterprise, or any other type of organization, of any size.

Many such software applications are developed by individual departments within the enterprise. These range from simple spreadsheets to custom-built software tools and databases. But the proliferation of siloed custom software applications has numerous disadvantages. It negatively impacts an enterprise's ability to run and grow its operations, innovate, and meet regulatory requirements. The enterprise may find it difficult to integrate, streamline, and enhance its operations due to lack of a single system that unifies its subsystems and data.

To efficiently create custom applications, enterprises would benefit from a remotely-hosted application platform that eliminates unnecessary development complexity. The goal of such a platform would be to reduce time-consuming, repetitive application development tasks so that software engineers and individuals in other roles can focus on developing unique, high-value features.

In order to achieve this goal, the concept of Application Platform as a Service (aPaaS) has been introduced to intelligently automate workflows throughout the enterprise. An aPaaS system is hosted remotely from the enterprise, but may access data, applications, and services within the enterprise by way of secure connections. Such an aPaaS system may have a number of advantageous capabilities and characteristics. These advantages and characteristics may be able to improve the enterprise's operations and workflows for IT, HR, CRM, customer service, application development, and security. Nonetheless, the embodiments herein are not limited to enterprise applications or environments, and can be more broadly applied.

The aPaaS system may support development and execution of model-view-controller (MVC) applications. MVC applications divide their functionality into three interconnected parts (model, view, and controller) in order to isolate representations of information from the manner in which the information is presented to the user, thereby allowing for efficient code reuse and parallel development. These applications may be web-based, and offer create, read, update, and delete (CRUD) capabilities. This allows new applications to be built on a common application infrastructure. In some cases, applications structured differently than MVC, such as those using unidirectional data flow, may be employed.

The aPaaS system may support standardized application components, such as a standardized set of widgets and/or web components for graphical user interface (GUI) development. In this way, applications built using the aPaaS system have a common look and feel. Other software components and modules may be standardized as well. In some cases, this look and feel can be branded or skinned with an enterprise's custom logos and/or color schemes.

The aPaaS system may support the ability to configure the behavior of applications using metadata. This allows application behaviors to be rapidly adapted to meet specific needs. Such an approach reduces development time and increases flexibility. Further, the aPaaS system may support GUI tools that facilitate metadata creation and management, thus reducing errors in the metadata.

The aPaaS system may support clearly-defined interfaces between applications, so that software developers can avoid unwanted inter-application dependencies. Thus, the aPaaS system may implement a service layer in which persistent state information and other data are stored.

The aPaaS system may support a rich set of integration features so that the applications thereon can interact with legacy applications and third-party applications. For instance, the aPaaS system may support a custom employee-onboarding system that integrates with legacy HR, IT, and accounting systems.

The aPaaS system may support enterprise-grade security. Furthermore, since the aPaaS system may be remotely hosted, it should also utilize security procedures when it interacts with systems in the enterprise or third-party networks and services hosted outside of the enterprise. For example, the aPaaS system may be configured to share data amongst the enterprise and other parties to detect and identify common security threats.

Other features, functionality, and advantages of an aPaaS system may exist. This description is for purpose of example and is not intended to be limiting.

As an example of the aPaaS development process, a software developer may be tasked to create a new application using the aPaaS system. First, the developer may define the data model, which specifies the types of data that the application uses and the relationships therebetween. Then, via a GUI of the aPaaS system, the developer enters (e.g., uploads) the data model. The aPaaS system automatically creates all of the corresponding database tables, fields, and relationships, which can then be accessed via an object-oriented services layer.

In addition, the aPaaS system can also build a fully-functional application with client-side interfaces and server-side CRUD logic. This generated application may serve as the basis of further development for the user. Advantageously, the developer does not have to spend a large amount of time on basic application functionality. Further, since the application may be web-based, it can be accessed from any Internet-enabled client device. Alternatively or additionally, a local copy of the application may be able to be accessed, for instance, when Internet service is not available.

The aPaaS system may also support a rich set of pre-defined functionality that can be added to applications. These features include support for searching, email, templating, workflow design, reporting, analytics, social media, scripting, mobile-friendly output, and customized GUIs.

Such an aPaaS system may represent a GUI in various ways. For example, a server device of the aPaaS system may generate a representation of a GUI using a combination of HyperText Markup Language (HTML) and JAVASCRIPT®. The JAVASCRIPT® may include client-side executable code, server-side executable code, or both. The server device may transmit or otherwise provide this representation to a client device for the client device to display on a screen according to its locally-defined look and feel. Alternatively, a representation of a GUI may take other forms, such as an intermediate form (e.g., JAVA® byte-code) that a client device can use to directly generate graphical output therefrom. Other possibilities exist, including but not limited to metadata-based encodings of web components, and various uses of JAVASCRIPT® Object Notation (JSON) and/or eXtensible Markup Language (XML) to represent various aspects of a GUI.

Further, user interaction with GUI elements, such as buttons, menus, tabs, sliders, checkboxes, toggles, etc. may be referred to as “selection”, “activation”, or “actuation” thereof. These terms may be used regardless of whether the GUI elements are interacted with by way of keyboard, pointing device, touchscreen, or another mechanism.

An aPaaS architecture is particularly powerful when integrated with an enterprise's network and used to manage such a network. The following embodiments describe architectural and functional aspects of example aPaaS systems, as well as the features and advantages thereof.

II. Example Computing Devices and Cloud-Based Computing Environments

FIG.1is a simplified block diagram exemplifying a computing device100, illustrating some of the components that could be included in a computing device arranged to operate in accordance with the embodiments herein. Computing device100could be a client device (e.g., a device actively operated by a user), a server device (e.g., a device that provides computational services to client devices), or some other type of computational platform. Some server devices may operate as client devices from time to time in order to perform particular operations, and some client devices may incorporate server features.

In this example, computing device100includes processor102, memory104, network interface106, and input/output unit108, all of which may be coupled by system bus110or a similar mechanism. In some embodiments, computing device100may include other components and/or peripheral devices (e.g., detachable storage, printers, and so on).

Processor102may be one or more of any type of computer processing element, such as a central processing unit (CPU), a graphical processing unit (GPU), another form of co-processor (e.g., a mathematics or encryption co-processor), a digital signal processor (DSP), a network processor, and/or a form of integrated circuit or controller that performs processor operations. In some cases, processor102may be one or more single-core processors. In other cases, processor102may be one or more multi-core processors with multiple independent processing units. Processor102may also include register memory for temporarily storing instructions being executed and related data, as well as cache memory for temporarily storing recently-used instructions and data.

Memory104may be any form of computer-usable memory, including but not limited to random access memory (RAM), read-only memory (ROM), and non-volatile memory (e.g., flash memory, hard disk drives, solid state drives, compact discs (CDs), digital video discs (DVDs), and/or tape storage). Thus, memory104represents both main memory units, as well as long-term storage.

Memory104may store program instructions and/or data on which program instructions may operate. By way of example, memory104may store these program instructions on a non-transitory, computer-readable medium, such that the instructions are executable by processor102to carry out any of the methods, processes, or operations disclosed in this specification or the accompanying drawings.

As shown inFIG.1, memory104may include firmware104A, kernel104B, and/or applications104C. Firmware104A may be program code used to boot or otherwise initiate some or all of computing device100. Kernel104B may be an operating system, including modules for memory management, scheduling and management of processes, input/output, and communication. Kernel104B may also include device drivers that allow the operating system to communicate with the hardware modules (e.g., memory units, networking interfaces, ports, and buses) of computing device100. Applications104C may be one or more user-space software programs, such as web browsers or email clients, as well as any software libraries used by these programs. Memory104may also store data used by these and other programs and applications.

Network interface106may take the form of one or more wireline interfaces, such as Ethernet (e.g., Fast Ethernet, Gigabit Ethernet, 10 Gigabit Ethernet, Ethernet over fiber, and so on). Network interface106may also support communication over one or more non-Ethernet media, such as coaxial cables or power lines, or over wide-area media, such as Synchronous Optical Networking (SONET), Data Over Cable Service Interface Specification (DOCSIS), or digital subscriber line (DSL) technologies. Network interface106may additionally take the form of one or more wireless interfaces, such as IEEE 802.11 (Wifi), BLUETOOTH®, global positioning system (GPS), or a wide-area wireless interface. However, other forms of physical layer interfaces and other types of standard or proprietary communication protocols may be used over network interface106. Furthermore, network interface106may comprise multiple physical interfaces. For instance, some embodiments of computing device100may include Ethernet, BLUETOOTH®, and Wifi interfaces.

Input/output unit108may facilitate user and peripheral device interaction with computing device100. Input/output unit108may include one or more types of input devices, such as a keyboard, a mouse, a touch screen, and so on. Similarly, input/output unit108may include one or more types of output devices, such as a screen, monitor, printer, and/or one or more light emitting diodes (LEDs). Additionally or alternatively, computing device100may communicate with other devices using a universal serial bus (USB) or high-definition multimedia interface (HDMI) port interface, for example.

In some embodiments, one or more computing devices like computing device100may be deployed. The exact physical location, connectivity, and configuration of these computing devices may be unknown and/or unimportant to client devices. Accordingly, the computing devices may be referred to as “cloud-based” devices that may be housed at various remote data center locations.

FIG.2depicts a cloud-based server cluster200in accordance with example embodiments. InFIG.2, operations of a computing device (e.g., computing device100) may be distributed between server devices202, data storage204, and routers206, all of which may be connected by local cluster network208. The number of server devices202, data storages204, and routers206in server cluster200may depend on the computing task(s) and/or applications assigned to server cluster200.

For example, server devices202can be configured to perform various computing tasks of computing device100. Thus, computing tasks can be distributed among one or more of server devices202. To the extent that these computing tasks can be performed in parallel, such a distribution of tasks may reduce the total time to complete these tasks and return a result. For purposes of simplicity, both server cluster200and individual server devices202may be referred to as a “server device.” This nomenclature should be understood to imply that one or more distinct server devices, data storage devices, and cluster routers may be involved in server device operations.

Data storage204may be data storage arrays that include drive array controllers configured to manage read and write access to groups of hard disk drives and/or solid state drives. The drive array controllers, alone or in conjunction with server devices202, may also be configured to manage backup or redundant copies of the data stored in data storage204to protect against drive failures or other types of failures that prevent one or more of server devices202from accessing units of data storage204. Other types of memory aside from drives may be used.

Routers206may include networking equipment configured to provide internal and external communications for server cluster200. For example, routers206may include one or more packet-switching and/or routing devices (including switches and/or gateways) configured to provide (i) network communications between server devices202and data storage204via local cluster network208, and/or (ii) network communications between server cluster200and other devices via communication link210to network212.

Additionally, the configuration of routers206can be based at least in part on the data communication requirements of server devices202and data storage204, the latency and throughput of the local cluster network208, the latency, throughput, and cost of communication link210, and/or other factors that may contribute to the cost, speed, fault-tolerance, resiliency, efficiency, and/or other design goals of the system architecture.

As a possible example, data storage204may include any form of database, such as a structured query language (SQL) database or a No-SQL database (e.g., MongoDB). Various types of data structures may store the information in such a database, including but not limited to files, tables, arrays, lists, trees, and tuples. Furthermore, any databases in data storage204may be monolithic or distributed across multiple physical devices.

Server devices202may be configured to transmit data to and receive data from data storage204. This transmission and retrieval may take the form of SQL queries or other types of database queries, and the output of such queries, respectively. Additional text, images, video, and/or audio may be included as well. Furthermore, server devices202may organize the received data into web page or web application representations. Such a representation may take the form of a markup language, such as HTML, XML, JSON, or some other standardized or proprietary format. Moreover, server devices202may have the capability of executing various types of computerized scripting languages, such as but not limited to Perl, Python, PHP Hypertext Preprocessor (PUP), Active Server Pages (ASP), JAVASCRIPT®, and so on. Computer program code written in these languages may facilitate the providing of web pages to client devices, as well as client device interaction with the web pages. Alternatively or additionally, JAVA® may be used to facilitate generation of web pages and/or to provide web application functionality.

III. Example Remote Network Management Architecture

FIG.3depicts a remote network management architecture, in accordance with example embodiments. This architecture includes three main components—managed network300, remote network management platform320, and public cloud networks340—all connected by way of Internet350.

A. Managed Networks

Managed network300may be, for example, an enterprise network used by an entity for computing and communications tasks, as well as storage of data. Thus, managed network300may include client devices302, server devices304, routers306, virtual machines308, firewall310, and/or proxy servers312. Client devices302may be embodied by computing device100, server devices304may be embodied by computing device100or server cluster200, and routers306may be any type of router, switch, or gateway.

Virtual machines308may be embodied by one or more of computing device100or server cluster200. In general, a virtual machine is an emulation of a computing system, and mimics the functionality (e.g., processor, memory, and communication resources) of a physical computer. One physical computing system, such as server cluster200, may support up to thousands of individual virtual machines. In some embodiments, virtual machines308may be managed by a centralized server device or application that facilitates allocation of physical computing resources to individual virtual machines, as well as performance and error reporting. Enterprises often employ virtual machines in order to allocate computing resources in an efficient, as needed fashion. Providers of virtualized computing systems include VMWARE® and MICROSOFT®.

Firewall310may be one or more specialized routers or server devices that protect managed network300from unauthorized attempts to access the devices, applications, and services therein, while allowing authorized communication that is initiated from managed network300. Firewall310may also provide intrusion detection, web filtering, virus scanning, application-layer gateways, and other applications or services. In some embodiments not shown inFIG.3, managed network300may include one or more virtual private network (VPN) gateways with which it communicates with remote network management platform320(see below).

Managed network300may also include one or more proxy servers312. An embodiment of proxy servers312may be a server application that facilitates communication and movement of data between managed network300, remote network management platform320, and public cloud networks340. In particular, proxy servers312may be able to establish and maintain secure communication sessions with one or more computational instances of remote network management platform320. By way of such a session, remote network management platform320may be able to discover and manage aspects of the architecture and configuration of managed network300and its components.

Possibly with the assistance of proxy servers312, remote network management platform320may also be able to discover and manage aspects of public cloud networks340that are used by managed network300. While not shown inFIG.3, one or more proxy servers312may be placed in any of public cloud networks340in order to facilitate this discovery and management.

Firewalls, such as firewall310, typically deny all communication sessions that are incoming by way of Internet350, unless such a session was ultimately initiated from behind the firewall (i.e., from a device on managed network300) or the firewall has been explicitly configured to support the session. By placing proxy servers312behind firewall310(e.g., within managed network300and protected by firewall310), proxy servers312may be able to initiate these communication sessions through firewall310. Thus, firewall310might not have to be specifically configured to support incoming sessions from remote network management platform320, thereby avoiding potential security risks to managed network300.

In some cases, managed network300may consist of a few devices and a small number of networks. In other deployments, managed network300may span multiple physical locations and include hundreds of networks and hundreds of thousands of devices. Thus, the architecture depicted inFIG.3is capable of scaling up or down by orders of magnitude.

Furthermore, depending on the size, architecture, and connectivity of managed network300, a varying number of proxy servers312may be deployed therein. For example, each one of proxy servers312may be responsible for communicating with remote network management platform320regarding a portion of managed network300. Alternatively or additionally, sets of two or more proxy servers may be assigned to such a portion of managed network300for purposes of load balancing, redundancy, and/or high availability.

B. Remote Network Management Platforms

Remote network management platform320is a hosted environment that provides aPaaS services to users, particularly to the operator of managed network300. These services may take the form of web-based portals, for example, using the aforementioned web-based technologies. Thus, a user can securely access remote network management platform320from, for example, client devices302, or potentially from a client device outside of managed network300. By way of the web-based portals, users may design, test, and deploy applications, generate reports, view analytics, and perform other tasks. Remote network management platform320may also be referred to as a multi-application platform.

As shown inFIG.3, remote network management platform320includes four computational instances322,324,326, and328. Each of these computational instances may represent one or more server nodes operating dedicated copies of the aPaaS software and/or one or more database nodes. The arrangement of server and database nodes on physical server devices and/or virtual machines can be flexible and may vary based on enterprise needs. In combination, these nodes may provide a set of web portals, services, and applications (e.g., a wholly-functioning aPaaS system) available to a particular enterprise. In some cases, a single enterprise may use multiple computational instances.

For example, managed network300may be an enterprise customer of remote network management platform320, and may use computational instances322,324, and326. The reason for providing multiple computational instances to one customer is that the customer may wish to independently develop, test, and deploy its applications and services. Thus, computational instance322may be dedicated to application development related to managed network300, computational instance324may be dedicated to testing these applications, and computational instance326may be dedicated to the live operation of tested applications and services. A computational instance may also be referred to as a hosted instance, a remote instance, a customer instance, or by some other designation. Any application deployed onto a computational instance may be a scoped application, in that its access to databases within the computational instance can be restricted to certain elements therein (e.g., one or more particular database tables or particular rows within one or more database tables).

For purposes of clarity, the disclosure herein refers to the arrangement of application nodes, database nodes, aPaaS software executing thereon, and underlying hardware as a “computational instance.” Note that users may colloquially refer to the graphical user interfaces provided thereby as “instances.” But unless it is defined otherwise herein, a “computational instance” is a computing system disposed within remote network management platform320.

The multi-instance architecture of remote network management platform320is in contrast to conventional multi-tenant architectures, over which multi-instance architectures exhibit several advantages. In multi-tenant architectures, data from different customers (e.g., enterprises) are comingled in a single database. While these customers' data are separate from one another, the separation is enforced by the software that operates the single database. As a consequence, a security breach in this system may affect all customers' data, creating additional risk, especially for entities subject to governmental, healthcare, and/or financial regulation. Furthermore, any database operations that affect one customer will likely affect all customers sharing that database. Thus, if there is an outage due to hardware or software errors, this outage affects all such customers. Likewise, if the database is to be upgraded to meet the needs of one customer, it will be unavailable to all customers during the upgrade process. Often, such maintenance windows will be long, due to the size of the shared database.

In contrast, the multi-instance architecture provides each customer with its own database in a dedicated computing instance. This prevents comingling of customer data, and allows each instance to be independently managed. For example, when one customer's instance experiences an outage due to errors or an upgrade, other computational instances are not impacted. Maintenance down time is limited because the database only contains one customer's data. Further, the simpler design of the multi-instance architecture allows redundant copies of each customer database and instance to be deployed in a geographically diverse fashion. This facilitates high availability, where the live version of the customer's instance can be moved when faults are detected or maintenance is being performed.

In some embodiments, remote network management platform320may include one or more central instances, controlled by the entity that operates this platform. Like a computational instance, a central instance may include some number of application and database nodes disposed upon some number of physical server devices or virtual machines. Such a central instance may serve as a repository for specific configurations of computational instances as well as data that can be shared amongst at least some of the computational instances. For instance, definitions of common security threats that could occur on the computational instances, software packages that are commonly discovered on the computational instances, and/or an application store for applications that can be deployed to the computational instances may reside in a central instance. Computational instances may communicate with central instances by way of well-defined interfaces in order to obtain this data.

In order to support multiple computational instances in an efficient fashion, remote network management platform320may implement a plurality of these instances on a single hardware platform. For example, when the aPaaS system is implemented on a server cluster such as server cluster200, it may operate virtual machines that dedicate varying amounts of computational, storage, and communication resources to instances. But full virtualization of server cluster200might not be necessary, and other mechanisms may be used to separate instances. In some examples, each instance may have a dedicated account and one or more dedicated databases on server cluster200. Alternatively, a computational instance such as computational instance322may span multiple physical devices.

In some cases, a single server cluster of remote network management platform320may support multiple independent enterprises. Furthermore, as described below, remote network management platform320may include multiple server clusters deployed in geographically diverse data centers in order to facilitate load balancing, redundancy, and/or high availability.

C. Public Cloud Networks

Public cloud networks340may be remote server devices (e.g., a plurality of server clusters such as server cluster200) that can be used for outsourced computation, data storage, communication, and service hosting operations. These servers may be virtualized (i.e., the servers may be virtual machines). Examples of public cloud networks340may include Amazon AWS Cloud, Microsoft Azure Cloud (Azure), Google Cloud Platform (GCP), and IBM Cloud Platform. Like remote network management platform320, multiple server clusters supporting public cloud networks340may be deployed at geographically diverse locations for purposes of load balancing, redundancy, and/or high availability.

Managed network300may use one or more of public cloud networks340to deploy applications and services to its clients and customers. For instance, if managed network300provides online music streaming services, public cloud networks340may store the music files and provide web interface and streaming capabilities. In this way, the enterprise of managed network300does not have to build and maintain its own servers for these operations.

Remote network management platform320may include modules that integrate with public cloud networks340to expose virtual machines and managed services therein to managed network300. The modules may allow users to request virtual resources, discover allocated resources, and provide flexible reporting for public cloud networks340. In order to establish this functionality, a user from managed network300might first establish an account with public cloud networks340, and request a set of associated resources. Then, the user may enter the account information into the appropriate modules of remote network management platform320. These modules may then automatically discover the manageable resources in the account, and also provide reports related to usage, performance, and billing.

D. Communication Support and Other Operations

Internet350may represent a portion of the global Internet. However, Internet350may alternatively represent a different type of network, such as a private wide-area or local-area packet-switched network.

FIG.4further illustrates the communication environment between managed network300and computational instance322, and introduces additional features and alternative embodiments. InFIG.4, computational instance322is replicated, in whole or in part, across data centers400A and400B. These data centers may be geographically distant from one another, perhaps in different cities or different countries. Each data center includes support equipment that facilitates communication with managed network300, as well as remote users.

In data center400A, network traffic to and from external devices flows either through VPN gateway402A or firewall404A. VPN gateway402A may be peered with VPN gateway412of managed network300by way of a security protocol such as Internet Protocol Security (IPSEC) or Transport Layer Security (TLS). Firewall404A may be configured to allow access from authorized users, such as user414and remote user416, and to deny access to unauthorized users. By way of firewall404A, these users may access computational instance322, and possibly other computational instances. Load balancer406A may be used to distribute traffic amongst one or more physical or virtual server devices that host computational instance322. Load balancer406A may simplify user access by hiding the internal configuration of data center400A, (e.g., computational instance322) from client devices. For instance, if computational instance322includes multiple physical or virtual computing devices that share access to multiple databases, load balancer406A may distribute network traffic and processing tasks across these computing devices and databases so that no one computing device or database is significantly busier than the others. In some embodiments, computational instance322may include VPN gateway402A, firewall404A, and load balancer406A.

Data center400B may include its own versions of the components in data center400A. Thus, VPN gateway402B, firewall404B, and load balancer406B may perform the same or similar operations as VPN gateway402A, firewall404A, and load balancer406A, respectively. Further, by way of real-time or near-real-time database replication and/or other operations, computational instance322may exist simultaneously in data centers400A and400B.

Data centers400A and400B as shown inFIG.4may facilitate redundancy and high availability. In the configuration ofFIG.4, data center400A is active and data center400B is passive. Thus, data center400A is serving all traffic to and from managed network300, while the version of computational instance322in data center400B is being updated in near-real-time. Other configurations, such as one in which both data centers are active, may be supported.

Should data center400A fail in some fashion or otherwise become unavailable to users, data center400B can take over as the active data center. For example, domain name system (DNS) servers that associate a domain name of computational instance322with one or more Internet Protocol (IP) addresses of data center400A may re-associate the domain name with one or more IP addresses of data center400B. After this re-association completes (which may take less than one second or several seconds), users may access computational instance322by way of data center400B.

FIG.4also illustrates a possible configuration of managed network300. As noted above, proxy servers312and user414may access computational instance322through firewall310. Proxy servers312may also access configuration items410. InFIG.4, configuration items410may refer to any or all of client devices302, server devices304, routers306, and virtual machines308, any components thereof, any applications or services executing thereon, as well as relationships between devices, components, applications, and services. Thus, the term “configuration items” may be shorthand for part of all of any physical or virtual device, or any application or service remotely discoverable or managed by computational instance322, or relationships between discovered devices, applications, and services. Configuration items may be represented in a configuration management database (CMDB) of computational instance322.

As stored or transmitted, a configuration item may be a list of attributes that characterize the hardware or software that the configuration item represents. These attributes may include manufacturer, vendor, location, owner, unique identifier, description, network address, operational status, serial number, time of last update, and so on. The class of a configuration item may determine which subset of attributes are present for the configuration item (e.g., software and hardware configuration items may have different lists of attributes).

As noted above, VPN gateway412may provide a dedicated VPN to VPN gateway402A. Such a VPN may be helpful when there is a significant amount of traffic between managed network300and computational instance322, or security policies otherwise suggest or require use of a VPN between these sites. In some embodiments, any device in managed network300and/or computational instance322that directly communicates via the VPN is assigned a public IP address. Other devices in managed network300and/or computational instance322may be assigned private IP addresses (e.g., IP addresses selected from the 10.0.0.0-10.255.255.255 or 192.168.0.0-192.168.255.255 ranges, represented in shorthand as subnets 10.0.0.0/8 and 192.168.0.0/16, respectively). In various alternatives, devices in managed network300, such as proxy servers312, may use a secure protocol (e.g., TLS) to communicate directly with one or more data centers.

IV. Example Discovery

In order for remote network management platform320to administer the devices, applications, and services of managed network300, remote network management platform320may first determine what devices are present in managed network300, the configurations, constituent components, and operational statuses of these devices, and the applications and services provided by the devices. Remote network management platform320may also determine the relationships between discovered devices, their components, applications, and services. Representations of these devices, components, applications, and services may be referred to as configuration items.

The process of determining the configuration items and relationships therebetween within managed network300is referred to as discovery, and may be facilitated at least in part by proxy servers312. To that point, proxy servers312may relay discovery requests and responses between managed network300and remote network management platform320.

Configuration items and relationships may be stored in a CMDB and/or other locations. Further, configuration items may be of various classes that define their constituent attributes and that exhibit an inheritance structure not unlike object-oriented software modules. For instance, a configuration item class of “server” may inherit all attributes from a configuration item class of “hardware” and also include further server-specific attributes. Likewise, a configuration item class of “LINUX® server” may inherit all attributes from the configuration item class of “server” and also include further LINUX®-specific attributes. Additionally, configuration items may represent other components, such as services, data center infrastructure, software licenses, units of source code, configuration files, and documents.

While this section describes discovery conducted on managed network300, the same or similar discovery procedures may be used on public cloud networks340. Thus, in some environments, “discovery” may refer to discovering configuration items and relationships on a managed network and/or one or more public cloud networks.

For purposes of the embodiments herein, an “application” may refer to one or more processes, threads, programs, client software modules, server software modules, or any other software that executes on a device or group of devices. A “service” may refer to a high-level capability provided by one or more applications executing on one or more devices working in conjunction with one another. For example, a web service may involve multiple web application server threads executing on one device and accessing information from a database application that executes on another device.

FIG.5provides a logical depiction of how configuration items and relationships can be discovered, as well as how information related thereto can be stored. For sake of simplicity, remote network management platform320, public cloud networks340, and Internet350are not shown.

InFIG.5, CMDB500, task list502, and identification and reconciliation engine (IRE)514are disposed and/or operate within computational instance322. Task list502represents a connection point between computational instance322and proxy servers312. Task list502may be referred to as a queue, or more particularly as an external communication channel (ECC) queue. Task list502may represent not only the queue itself but any associated processing, such as adding, removing, and/or manipulating information in the queue.

As discovery takes place, computational instance322may store discovery tasks (jobs) that proxy servers312are to perform in task list502, until proxy servers312request these tasks in batches of one or more. Placing the tasks in task list502may trigger or otherwise cause proxy servers312to begin their discovery operations. For example, proxy servers312may poll task list502periodically or from time to time, or may be notified of discovery commands in task list502in some other fashion. Alternatively or additionally, discovery may be manually triggered or automatically triggered based on triggering events (e.g., discovery may automatically begin once per day at a particular time).

Regardless, computational instance322may transmit these discovery commands to proxy servers312upon request. For example, proxy servers312may repeatedly query task list502, obtain the next task therein, and perform this task until task list502is empty or another stopping condition has been reached. In response to receiving a discovery command, proxy servers312may query various devices, components, applications, and/or services in managed network300(represented for sake of simplicity inFIG.5by devices504,506,508,510, and512). These devices, components, applications, and/or services may provide responses relating to their configuration, operation, and/or status to proxy servers312. In turn, proxy servers312may then provide this discovered information to task list502(i.e., task list502may have an outgoing queue for holding discovery commands until requested by proxy servers312as well as an incoming queue for holding the discovery information until it is read).

IRE514may be a software module that removes discovery information from task list502and formulates this discovery information into configuration items (e.g., representing devices, components, applications, and/or services discovered on managed network300) as well as relationships therebetween. Then, IRE514may provide these configuration items and relationships to CMDB500for storage therein. The operation of IRE514is described in more detail below.

In this fashion, configuration items stored in CMDB500represent the environment of managed network300. As an example, these configuration items may represent a set of physical and/or virtual devices (e.g., client devices, server devices, routers, or virtual machines), applications executing thereon (e.g., web servers, email servers, databases, or storage arrays), as well as services that involve multiple individual configuration items. Relationships may be pairwise definitions of arrangements or dependencies between configuration items.

In order for discovery to take place in the manner described above, proxy servers312, CMDB500, and/or one or more credential stores may be configured with credentials for the devices to be discovered. Credentials may include any type of information needed in order to access the devices. These may include userid/password pairs, certificates, and so on. In some embodiments, these credentials may be stored in encrypted fields of CMDB500. Proxy servers312may contain the decryption key for the credentials so that proxy servers312can use these credentials to log on to or otherwise access devices being discovered.

There are two general types of discovery—horizontal and vertical (top-down). Each are discussed below.

A. Horizontal Discovery

Horizontal discovery is used to scan managed network300, find devices, components, and/or applications, and then populate CMDB500with configuration items representing these devices, components, and/or applications. Horizontal discovery also creates relationships between the configuration items. For instance, this could be a “runs on” relationship between a configuration item representing a software application and a configuration item representing a server device on which it executes. Typically, horizontal discovery is not aware of services and does not create relationships between configuration items based on the services in which they operate.

There are two versions of horizontal discovery. One relies on probes and sensors, while the other also employs patterns. Probes and sensors may be scripts (e.g., written in JAVASCRIPT®) that collect and process discovery information on a device and then update CMDB500accordingly. More specifically, probes explore or investigate devices on managed network300, and sensors parse the discovery information returned from the probes.

Patterns are also scripts that collect data on one or more devices, process it, and update the CMDB. Patterns differ from probes and sensors in that they are written in a specific discovery programming language and are used to conduct detailed discovery procedures on specific devices, components, and/or applications that often cannot be reliably discovered (or discovered at all) by more general probes and sensors. Particularly, patterns may specify a series of operations that define how to discover a particular arrangement of devices, components, and/or applications, what credentials to use, and which CMDB tables to populate with configuration items resulting from this discovery.

Both versions may proceed in four logical phases: scanning, classification, identification, and exploration. Also, both versions may require specification of one or more ranges of IP addresses on managed network300for which discovery is to take place. Each phase may involve communication between devices on managed network300and proxy servers312, as well as between proxy servers312and task list502. Some phases may involve storing partial or preliminary configuration items in CMDB500, which may be updated in a later phase.

In the scanning phase, proxy servers312may probe each IP address in the specified range(s) of IP addresses for open Transmission Control Protocol (TCP) and/or User Datagram Protocol (UDP) ports to determine the general type of device and its operating system. The presence of such open ports at an IP address may indicate that a particular application is operating on the device that is assigned the IP address, which in turn may identify the operating system used by the device. For example, if TCP port135is open, then the device is likely executing a WINDOWS® operating system. Similarly, if TCP port22is open, then the device is likely executing a UNIX® operating system, such as LINUX®. If UDP port161is open, then the device may be able to be further identified through the Simple Network Management Protocol (SNMP). Other possibilities exist.

In the classification phase, proxy servers312may further probe each discovered device to determine the type of its operating system. The probes used for a particular device are based on information gathered about the devices during the scanning phase. For example, if a device is found with TCP port22open, a set of UNIX®-specific probes may be used. Likewise, if a device is found with TCP port135open, a set of WINDOWS®-specific probes may be used. For either case, an appropriate set of tasks may be placed in task list502for proxy servers312to carry out. These tasks may result in proxy servers312logging on, or otherwise accessing information from the particular device. For instance, if TCP port22is open, proxy servers312may be instructed to initiate a Secure Shell (SSH) connection to the particular device and obtain information about the specific type of operating system thereon from particular locations in the file system. Based on this information, the operating system may be determined. As an example, a UNIX® device with TCP port22open may be classified as AIX®, HPUX, LINUX®, MACOS®, or SOLARIS®. This classification information may be stored as one or more configuration items in CMDB500.

In the identification phase, proxy servers312may determine specific details about a classified device. The probes used during this phase may be based on information gathered about the particular devices during the classification phase. For example, if a device was classified as LINUX®, a set of LINUX®-specific probes may be used. Likewise, if a device was classified as WINDOWS® 10, as a set of WINDOWS®-10-specific probes may be used. As was the case for the classification phase, an appropriate set of tasks may be placed in task list502for proxy servers312to carry out. These tasks may result in proxy servers312reading information from the particular device, such as basic input/output system (BIOS) information, serial numbers, network interface information, media access control address(es) assigned to these network interface(s), IP address(es) used by the particular device and so on. This identification information may be stored as one or more configuration items in CMDB500along with any relevant relationships therebetween. Doing so may involve passing the identification information through IRE514to avoid generation of duplicate configuration items, for purposes of disambiguation, and/or to determine the table(s) of CMDB500in which the discovery information should be written.

In the exploration phase, proxy servers312may determine further details about the operational state of a classified device. The probes used during this phase may be based on information gathered about the particular devices during the classification phase and/or the identification phase. Again, an appropriate set of tasks may be placed in task list502for proxy servers312to carry out. These tasks may result in proxy servers312reading additional information from the particular device, such as processor information, memory information, lists of running processes (software applications), and so on. Once more, the discovered information may be stored as one or more configuration items in CMDB500, as well as relationships.

Running horizontal discovery on certain devices, such as switches and routers, may utilize SNMP. Instead of or in addition to determining a list of running processes or other application-related information, discovery may determine additional subnets known to a router and the operational state of the router's network interfaces (e.g., active, inactive, queue length, number of packets dropped, etc.). The IP addresses of the additional subnets may be candidates for further discovery procedures. Thus, horizontal discovery may progress iteratively or recursively.

Patterns are used only during the identification and exploration phases—under pattern-based discovery, the scanning and classification phases operate as they would if probes and sensors are used. After the classification stage completes, a pattern probe is specified as a probe to use during identification. Then, the pattern probe and the pattern that it specifies are launched.

Patterns support a number of features, by way of the discovery programming language, that are not available or difficult to achieve with discovery using probes and sensors. For example, discovery of devices, components, and/or applications in public cloud networks, as well as configuration file tracking, is much simpler to achieve using pattern-based discovery. Further, these patterns are more easily customized by users than probes and sensors. Additionally, patterns are more focused on specific devices, components, and/or applications and therefore may execute faster than the more general approaches used by probes and sensors.

Once horizontal discovery completes, a configuration item representation of each discovered device, component, and/or application is available in CMDB500. For example, after discovery, operating system version, hardware configuration, and network configuration details for client devices, server devices, and routers in managed network300, as well as applications executing thereon, may be stored as configuration items. This collected information may be presented to a user in various ways to allow the user to view the hardware composition and operational status of devices.

Furthermore, CMDB500may include entries regarding the relationships between configuration items. More specifically, suppose that a server device includes a number of hardware components (e.g., processors, memory, network interfaces, storage, and file systems), and has several software applications installed or executing thereon. Relationships between the components and the server device (e.g., “contained by” relationships) and relationships between the software applications and the server device (e.g., “runs on” relationships) may be represented as such in CMDB500.

More generally, the relationship between a software configuration item installed or executing on a hardware configuration item may take various forms, such as “is hosted on”, “runs on”, or “depends on”. Thus, a database application installed on a server device may have the relationship “is hosted on” with the server device to indicate that the database application is hosted on the server device. In some embodiments, the server device may have a reciprocal relationship of “used by” with the database application to indicate that the server device is used by the database application. These relationships may be automatically found using the discovery procedures described above, though it is possible to manually set relationships as well.

In this manner, remote network management platform320may discover and inventory the hardware and software deployed on and provided by managed network300.

B. Vertical Discovery

Vertical discovery is a technique used to find and map configuration items that are part of an overall service, such as a web service. For example, vertical discovery can map a web service by showing the relationships between a web server application, a LINUX® server device, and a database that stores the data for the web service. Typically, horizontal discovery is run first to find configuration items and basic relationships therebetween, and then vertical discovery is run to establish the relationships between configuration items that make up a service.

Patterns can be used to discover certain types of services, as these patterns can be programmed to look for specific arrangements of hardware and software that fit a description of how the service is deployed. Alternatively or additionally, traffic analysis (e.g., examining network traffic between devices) can be used to facilitate vertical discovery. In some cases, the parameters of a service can be manually configured to assist vertical discovery.

In general, vertical discovery seeks to find specific types of relationships between devices, components, and/or applications. Some of these relationships may be inferred from configuration files. For example, the configuration file of a web server application can refer to the IP address and port number of a database on which it relies. Vertical discovery patterns can be programmed to look for such references and infer relationships therefrom. Relationships can also be inferred from traffic between devices—for instance, if there is a large extent of web traffic (e.g., TCP port80or8080) traveling between a load balancer and a device hosting a web server, then the load balancer and the web server may have a relationship.

Relationships found by vertical discovery may take various forms. As an example, an email service may include an email server software configuration item and a database application software configuration item, each installed on different hardware device configuration items. The email service may have a “depends on” relationship with both of these software configuration items, while the software configuration items have a “used by” reciprocal relationship with the email service. Such services might not be able to be fully determined by horizontal discovery procedures, and instead may rely on vertical discovery and possibly some extent of manual configuration.

C. Advantages of Discovery

Regardless of how discovery information is obtained, it can be valuable for the operation of a managed network. Notably, IT personnel can quickly determine where certain software applications are deployed, and what configuration items make up a service. This allows for rapid pinpointing of root causes of service outages or degradation. For example, if two different services are suffering from slow response times, the CMDB can be queried (perhaps among other activities) to determine that the root cause is a database application that is used by both services having high processor utilization. Thus, IT personnel can address the database application rather than waste time considering the health and performance of other configuration items that make up the services.

In another example, suppose that a database application is executing on a server device, and that this database application is used by an employee onboarding service as well as a payroll service. Thus, if the server device is taken out of operation for maintenance, it is clear that the employee onboarding service and payroll service will be impacted. Likewise, the dependencies and relationships between configuration items may be able to represent the services impacted when a particular hardware device fails.

In general, configuration items and/or relationships between configuration items may be displayed on a web-based interface and represented in a hierarchical fashion. Modifications to such configuration items and/or relationships in the CMDB may be accomplished by way of this interface.

Furthermore, users from managed network300may develop workflows that allow certain coordinated activities to take place across multiple discovered devices. For instance, an IT workflow might allow the user to change the common administrator password to all discovered LINUX® devices in a single operation.

V. CMDB Identification Rules and Reconciliation

A CMDB, such as CMDB500, provides a repository of configuration items and relationships. When properly provisioned, it can take on a key role in higher-layer applications deployed within or involving a computational instance. These applications may relate to enterprise IT service management, operations management, asset management, configuration management, compliance, and so on.

For example, an IT service management application may use information in the CMDB to determine applications and services that may be impacted by a component (e.g., a server device) that has malfunctioned, crashed, or is heavily loaded. Likewise, an asset management application may use information in the CMDB to determine which hardware and/or software components are being used to support particular enterprise applications. As a consequence of the importance of the CMDB, it is desirable for the information stored therein to be accurate, consistent, and up to date.

A CMDB may be populated in various ways. As discussed above, a discovery procedure may automatically store information including configuration items and relationships in the CMDB. However, a CMDB can also be populated, as a whole or in part, by manual entry, configuration files, and third-party data sources. Given that multiple data sources may be able to update the CMDB at any time, it is possible that one data source may overwrite entries of another data source. Also, two data sources may each create slightly different entries for the same configuration item, resulting in a CMDB containing duplicate data. When either of these occurrences takes place, they can cause the health and utility of the CMDB to be reduced.

In order to mitigate this situation, these data sources might not write configuration items directly to the CMDB. Instead, they may write to an identification and reconciliation application programming interface (API) of RE514. Then, IRE514may use a set of configurable identification rules to uniquely identify configuration items and determine whether and how they are to be written to the CMDB.

In general, an identification rule specifies a set of configuration item attributes that can be used for this unique identification. Identification rules may also have priorities so that rules with higher priorities are considered before rules with lower priorities. Additionally, a rule may be independent, in that the rule identifies configuration items independently of other configuration items. Alternatively, the rule may be dependent, in that the rule first uses a metadata rule to identify a dependent configuration item.

Metadata rules describe which other configuration items are contained within a particular configuration item, or the host on which a particular configuration item is deployed. For example, a network directory service configuration item may contain a domain controller configuration item, while a web server application configuration item may be hosted on a server device configuration item.

A goal of each identification rule is to use a combination of attributes that can unambiguously distinguish a configuration item from all other configuration items, and is expected not to change during the lifetime of the configuration item. Some possible attributes for an example server device may include serial number, location, operating system, operating system version, memory capacity, and so on. If a rule specifies attributes that do not uniquely identify the configuration item, then multiple components may be represented as the same configuration item in the CMDB. Also, if a rule specifies attributes that change for a particular configuration item, duplicate configuration items may be created.

Thus, when a data source provides information regarding a configuration item to IRE514, IRE514may attempt to match the information with one or more rules. If a match is found, the configuration item is written to the CMDB or updated if it already exists within the CMDB. If a match is not found, the configuration item may be held for further analysis.

Configuration item reconciliation procedures may be used to ensure that only authoritative data sources are allowed to overwrite configuration item data in the CMDB. This reconciliation may also be rules-based. For instance, a reconciliation rule may specify that a particular data source is authoritative for a particular configuration item type and set of attributes. Then, TRE514might only permit this authoritative data source to write to the particular configuration item, and writes from unauthorized data sources may be prevented. Thus, the authorized data source becomes the single source of truth regarding the particular configuration item. In some cases, an unauthorized data source may be allowed to write to a configuration item if it is creating the configuration item or the attributes to which it is writing are empty.

Additionally, multiple data sources may be authoritative for the same configuration item or attributes thereof. To avoid ambiguities, these data sources may be assigned precedences that are taken into account during the writing of configuration items. For example, a secondary authorized data source may be able to write to a configuration item's attribute until a primary authorized data source writes to this attribute. Afterward, further writes to the attribute by the secondary authorized data source may be prevented.

In some cases, duplicate configuration items may be automatically detected by IRE514or in another fashion. These configuration items may be deleted or flagged for manual de-duplication.

VI. Example Document Generation System

FIG.6illustrates an example document generation system600. Document generation system600may include query selector608, response selector612, text summarization model616, generative ML model620, and validation model624. Document generation system600may be configured to generate updated document628based on query sources602, response sources604, and document prompt606. Document generation system600may be implemented using hardware, software, or a combination thereof.

Document prompt606may include a request for generation of a document and may specify a subject for the document. Document prompt606may include and/or form part of an instruction to generate the document. The subject of the document may span one or more topics. That is, each of the one or more topics may be a subset of the subject that describes and/or relates to a corresponding aspects of the subject. When each of the one or more topics is described by the document, the document may be considered to sufficiently, adequately, and/or completely address the subject.

In some examples, document prompt606may include a textual description of the subject. In other examples, document prompt606may describe the subject using other data types, such as images and/or audio, among other possibilities. In some cases, document prompt606may be at least partly generated and/or provided to document generation system600by a user. In other cases, document prompt606may be at least partly generated and/or provided to document generation system600by another computing system.

Document prompt606may describe and/or indicate one or more attributes/properties of updated document628. The one or more attributes/properties of updated document628may include, for example, a length, an extent of conciseness, an extent of technical complexity, a tone, and/or a style, among others. Document prompt606may also include one or more user-specified queries to be answered by updated document628and/or one or more user-specified topics to be covered by updated document628. Thus, in addition to allowing the user to specify the subject for the document, document generation system600may also allow the user to provide specific queries that the user would like the document to answer and/or specific topics that the user would like the document to cover.

Document generation system600may operate to generate updated document628by identifying queries and responses that are related to document prompt606, and generating text that addresses the identified queries using the identified responses. Thus, updated document628may describe the subject by, for example, addressing one or more queries related to the one or more topics spanned by the subject. For example, updated document628may be a knowledge base article that addresses one or more queries that are frequently asked in connection with the subject specified by document prompt606. The knowledge base article may be directed to a technical subject and may thus facilitate usage and/or operation of one or more computing resources.

Query selector608may be configured to determine queries610based on document prompt606and query sources602, and response selector612may be configured to determine information source(s)614likely to contain information responsive to queries610. The queries in query sources602and the information in response sources604might be unstructured. For example, the queries and/or the information might not be explicitly mapped to any given subject or topic. As another example, a given query might not be mapped to a corresponding response/answer. Thus, although it may be possible to use query sources602and/or response sources604to find information on a given subject, it may be impractical and/or impossible to do so without using document generation system600, especially as the size of and/or number of documents in sources602and604increases. Accordingly, query selector608and response selector612may filter sources602and604, respectively, to identify information that is relevant to document prompt606.

Queries610may include one or more queries that are relevant and/or related to document prompt606. For example, query selector608may be configured to identify queries610in query sources602based on a similarity between document prompt606(e.g., the subject specified by document prompt606) and each of queries610. The similarity may be measured using a model and/or algorithm configured to quantify a semantic similarity between document prompt606and each of queries610. The model and/or algorithm may include, for example, the best match25(BM25) algorithm, cosine similarity, Euclidean distance, Levenshtein distance, Jaccard index, and/or a neural network trained to quantify the semantic similarity, among other possibilities.

Query selector608may be configured to determine, for each respective query of a plurality of queries in query sources602, a corresponding similarity value that represents a similarity between the respective query and document prompt606(e.g., the subject specified therein). Query selector608may select each of queries610based on each of queries610having a corresponding similarity value that exceeds a threshold query similarity value (e.g., 0.5, 0.6, 0.7, 0.75, etc.). Additionally or alternatively, query selector608may be configured to determine queries610by selecting up to a predetermined number of queries that are most similar to document prompt606. Thus, queries610may include queries that, if addressed, are likely to assist with responding to document prompt606, and may exclude queries that are likely to be irrelevant to document prompt606.

Query sources602may include any data sources that are likely to include one or more queries and/or questions associated with document prompt606. The data sources may include email(s), recording(s) and/or transcript(s) of meeting(s), documentation of product(s), documentation of process(es), contents of performed task(s), forum(s), blog post(s), chat group(s), and/or phone call(s), among other possibilities. The data sources may include textual data and/or non-textual data (e.g., audio, video, etc.) that may be used to generate textual data.

In some cases, document prompt606may be provided in connection with a representation of a scope and/or context that can be used to identify query sources602. For example, the scope and/or context may be defined by and/or associated with a particular managed network in connection with which document prompt606is provided (e.g., by a user and/or computing system). Thus, query sources602may include data sources associated with the particular managed network, but may exclude data sources associated with other managed networks. As another example, the scope and/or context may be defined by and/or associated with a particular computational instance of remote network management platform320in connection with which document prompt606is provided. Thus, query sources602may include data sources associated with the particular computational instance of remote network management platform320, but may exclude data sources associated with other computational instances.

Accordingly, by considering the scope and/or context associated with document prompt606, updated document628may include content that is likely to be relevant to the user and/or system that provided document prompt606. Accordingly, as the scope and/or context associated with document prompt606changes, document generation system600may be configured to generate different versions of updated document628based on the same document prompt606. For example, two different users in two different managed networks, each of which provides a different scope and/or context, may obtain different versions of updated document628using the same document prompt606.

Text summarization model616may be configured to determine topic(s)618based on queries610. Topic(s)618may provide a summary of queries610. Specifically, text summarization model616may be configured to summarize each of queries610using a corresponding topic of topic(s)618. In some cases, multiple queries may be summarized using a single topic. For example, multiple queries that are similar and/or redundant may be represented using a single topic, thus reducing the amount of redundant information provided as input to generative ML model620.

Topic(s)618may provide a basis for at least partly describing the subject indicated by document prompt606. For example, topic(s)618may include information spanning the subject to the extent that such information is present in query sources602and/or response sources604. Providing topic(s)618, rather than queries610, as an input to generative ML model620may facilitate generation of documents that are concise and/or non-redundant, since text summarization model616may filter out redundancies and/or repetitions from queries610in the process of generating topic(s)618.

For example, a particular topic of topic(s)618may summarize ten different queries, each of which asks approximately the same question in a different way. Thus, explicitly providing each of these ten different queries as input to generative ML model620may result in document622including redundant content, whereas providing the particular topic as input to generative ML model620instead of these ten different queries is more likely to result in a concise answer to the question.

Response selector612may be configured to determine information source(s)614based on document prompt606and response sources604, and possibly also based on queries610and/or topic(s)618. Information source(s)614may include one or more information sources that are relevant and/or related to document prompt606, queries610, and/or topic(s)618. For example, response selector612may be configured to identify information source(s)614in response sources604based on a similarity between (i) document prompt606(e.g., the subject specified by document prompt606), queries610, and/or topic(s)618and (ii) each of information source(s)614. The similarity may be measured using model(s) and/or algorithm(s) that are similar to and/or the same as those discussed above with respect to query selector608.

Response selector612may be configured to determine, for each respective information source of a plurality of information sources in response sources604, a corresponding similarity value that represents a similarity between (i) the respective information source and (i) document prompt606(e.g., the subject specified therein), queries610, and/or topic(s)618. Response selector612may select each of information source(s)614based on each of information source(s)614having a corresponding similarity value that exceeds a threshold information similarity value (e.g., 0.5, 0.6, 0.7, 0.75, etc.). Additionally or alternatively, response selector612may be configured to determine information source(s)614by selecting up to a predetermined number of information sources with contents that are most similar to document prompt606, queries610, and/or topic(s)618. Thus, information source(s)614may include information sources that are likely to assist with responding to document prompt606, and may exclude information sources that are likely to be irrelevant to document prompt606.

Response sources604may include any data sources that are likely to include information and/or responses associated with document prompt606, queries610, and/or topic(s)618. The data sources may be similar to and/or the same as the data sources discussed above in connection with query sources602. In some cases, response sources604may be indicated by and/or selected based on a scope and/or context associated with document prompt606(e.g., a managed network and/or a computational instance in connection with which document prompt606is provided), as discussed above in connection with query sources602.

In some implementations, response selector612may be configured to determine whether each of queries610is addressable using response sources604. For example, response selector612may be configured to (i) determine candidate information sources that are similar to document prompt606, queries610, and/or topic(s)618and (ii) identify, within the candidate information sources, information source(s)614that address queries610. Thus, some of the candidate information sources might be excluded from information source(s)614due to failing to address any of queries610.

Response selector612may include a query answering model configured to attempt to identify, for each respective query of queries610, a corresponding response/answer in the candidate information sources. The query answering model may be configured to address a respective query by identifying, within the candidate information sources, a textual string that contains the corresponding response/answer. The respective query may be considered addressable when the textual string selected by the query answering model in response to the query is associated with at least a threshold confidence value, as determined by the query answering model. In some cases, each of information source(s)614may include the textual string of the respective query, but might not include other parts of the corresponding candidate information source. That is, each of information source(s)614may include the answer to a corresponding question, but may exclude surrounding text found in the corresponding candidate information source to reduce and/or minimize the amount of irrelevant information provided as input to generative ML model620.

In some implementations, when a particular query of queries610is not addressable using response sources604, generation of document622and/or updated document628may be aborted. That is, document generation system600might not generate a document when response sources604are determined to lack sufficient information to answer all of queries610. In other implementations, when the particular query of queries610is not addressable using response sources604, the particular query may be removed from queries610, and document622and/or updated document628may be generated independently of the particular query. Document generation system600may also add to document622and/or updated document628an indication of the particular query to explicitly indicate information that may be missing from these documents.

Generative ML model620may be configured to generate document622based on document prompt606, topic(s)618, and/or information source(s)614.FIG.8illustrates an example of how such data may be structured when provided as input to generative ML model620. Specifically, document prompt606may instruct generative ML model620on the subject for document622, topic(s)618may indicate different aspects of the subject that are to be described by document622, and information source(s)614may provide the information to be used in describing topic(s)618. Document622may represent an initial attempt by generative ML model620to describe the subject of document prompt606. An initial version of document622may be generated by generative ML model620without explicitly providing thereto as input any of queries610.

Query selector608, response selector612, text summarization model616, generative ML model620, and/or validation model624may include and/or be based on a large language model (LLM). For example, each respective model of query selector608, response selector612, text summarization model616, generative ML model620, and/or validation model624may include and/or be based on an LLM that has been trained to perform at least some of the operations of the respective model as described herein.

An LLM is an advanced computational model, primarily functioning within the domain of natural language processing (NLP) and machine learning. An LLM can be configured to understand, interpret, generate, and respond to human language in a manner that is both contextually relevant and syntactically coherent. The underlying structure of an LLM is typically based on a neural network architecture, more specifically, a variant of the transformer model. Transformers are notable for their ability to process sequential data, such as text, with high efficiency.

The operation of an LLM involves layers of interconnected processing units, known as neurons, which collectively form a deep neural network. This network can be trained on vast datasets comprising text from diverse sources, thereby enabling the LLM to learn a wide array of language patterns, structures, and colloquial nuances for prose, poetry, and program code. The training process involves adjusting the weights of the connections between neurons using algorithms such as backpropagation, in conjunction with optimization techniques like stochastic gradient descent, to minimize the difference between the LLM's output and expected output.

An aspect of an LLM's functionality is its use of attention mechanisms, particularly self-attention, within the transformer architecture. These mechanisms allow the model to weigh the importance of different parts of the input text differently, enabling it to focus on relevant aspects of the data when generating responses or analyzing language. The self-attention mechanism facilitates the model's ability to generate contextually relevant and coherent text by understanding the relationships and dependencies between words or tokens in a sentence (or longer parts of texts), regardless of their position.

Upon receiving an input, such as a text query or a prompt, the LLM may process this input through its multiple layers, generating a probabilistic model of the language therein. It predicts the likelihood of each word or token that might follow the given input, based on the patterns it has learned during its training. The model then generates an output, which could be a continuation of the input text, an answer to a query, or other relevant textual content, by selecting words or tokens that have the highest probability of being contextually appropriate.

Furthermore, an LLM can be fine-tuned after its initial training for specific applications or tasks. This fine-tuning process involves additional training (e.g., with reinforcement from humans), usually on a smaller, task-specific dataset, which allows the model to adapt its responses to suit particular use cases more accurately. This adaptability makes LLMs highly versatile and applicable in various domains, including but not limited to, chatbot development, content creation, language translation, and sentiment analysis.

Some LLMs are multimodal in that they can receive prompts in formats other than text and can produce outputs in formats other than text. Thus, while LLMs are predominantly designed for understanding and generating textual data, multimodal LLMs extend this functionality to include multiple data modalities, such as visual and auditory inputs, in addition to text.

A multimodal LLM can employ an advanced neural network architecture, often a variant of the transformer model that is specifically adapted to process and fuse data from different sources. This architecture integrates specialized mechanisms, such as convolutional neural networks for visual data and recurrent neural networks for audio processing, allowing the model to effectively process each modality before synthesizing a unified output.

The training of a multimodal LLM involves multimodal datasets, enabling the model to learn not only language patterns but also the correlations and interactions between different types of data. This cross-modal training results in multimodal LLMs being adept at tasks that require an understanding of complex relationships across multiple data forms, a capability that text-only LLMs do not possess. This makes multimodal LLMs particularly suited for advanced applications that necessitate a holistic understanding of multimodal information, such as chatbots that can interpret and produce images and/or audio.

In some cases, document622might not provide a complete description of the subject specified by document prompt606. For example, document622might not address each of queries610and/or aspects of topic(s)618, and thus might lack some information on the subject specified by document prompt606. That is, the initial document generated by generative ML model620may be an incomplete draft, and thus should be revised and/or updated to more completely address document prompt606.

To address this possibility, document generation system600may be configured to provide review and revision of instantiations of document622. Specifically, document generation system600may include validation model624configured to determine whether document622adequately, sufficiently, and/or completely addresses document prompt606(e.g., adequately, sufficiently, and/or completely covers the subject specified by document prompt606). Validation model624may be configured to quantify the quality of document622by identifying unaddressed query626based on document622and queries610. Unaddressed query626may represent a subset of queries610that is not addressed (e.g., partially or completely) by document622. Document622may be considered complete when document622addresses (e.g., includes an answer to) each of queries610, and may be considered incomplete when validation model624identifies one or more instantiations of unaddressed query626.

Validation model624may include a query answering model configured to attempt to identify, for each respective query of queries610, a corresponding response/answer in document622and/or updated versions thereof. The query answering model may be configured to determine that the respective query is addressed by identifying, within document622, a generated textual string that contains the corresponding response/answer to the respective query. The respective query may be considered addressed by document622when the generated textual string selected by the query answering model is associated with at least a threshold confidence value (e.g., 0.7, 0.75, 0.8, etc.), as determined by the query answering model. In some implementations, the query answering model of validation model624may be the same as or similar to the query answering model of response selector612.

Additionally or alternatively, the respective query may be considered addressed by document622when the generated textual string is sufficiently similar (e.g., as quantified using a similarity value determined using any of the approached discussed herein) to the corresponding response/answer identified by response selector612for the respective query. Thus, validation model624may be configured to determine that, in determining the generated textual string, generative ML model620has not substantially modified the content of the corresponding response/answer identified by response selector612in response sources604.

To correct for any deficiencies identified by validation model624in document622, document generation system600may be configured to cause generative ML model620to generate an updated version of document622further based on unaddressed query626. That is, based on validation model624determining unaddressed query626, unaddressed query626may be provided to generative ML model620as an additional input, thus prompting generative ML model620to more explicitly, clearly, and/or accurately address unaddressed query626when generating the updated version of document622. Thus, generative ML model620may be configured to generate an updated version of document622based on document prompt606, topic(s)618, information source(s)614, and/or unaddressed query626.

In some cases, generative ML model620may be configured to generate the updated version of document622further based on contextual data associated with generating document622. The contextual data may include all input provided to generative ML model620in connection with generating document622, state(s) of generative ML model620reached in connection with generating document622, and/or document622itself, among other possibilities. Thus, updated version of document622may be based on information associated with generating prior version of document622.

The operations of generative ML model620and/or validation model624may be repeated one or more times until validation model624does not identify any unaddressed queries in the updated version of document622. That is, validation model624may cause generative ML model620to generate updated versions of document622until each of queries610is addressed by the updated version of document622. Updated document628may represent a version of document622that addresses all of queries610. Thus, updated document628may provide a sufficient, adequate, and/or complete description of the subject specified by document prompt606, and may be the result of two or more iterations of generative ML model620and/or validation model624.

In some implementations, data related to information source(s)614may be stored in association with updated document628. Further, each respective information source of information source(s)614may be mapped to a corresponding portion of updated document628, where the corresponding portion is based on the respective information source. Thus, document generation system600may be configured to create an association between the contents of updated document628and the underlying data used for generating these contents, thereby allowing the information in updated document628to be verified. For example, a particular textual string (identified in response sources604) that addresses a given query of queries610may be stored in association with a generated textual string present in updated document628. The generated textual string may also address the given query but may differ from the particular textual string. For example, the generated textual string may be a rewritten version of the particular textual string.

The accuracy of the generated textual string may be verifiable by viewing the particular textual string. For example, updated document628may be transmitted to a client device along with a user interface that includes user interface components configured to allow a user to request and/or view the underlying data on which different portions of updated document628are based. For example, each respective portion (e.g., textual string) of updated document628may be displayed using and/or in association with a corresponding user interface component that, if selected and/or interacted with, is configured to cause the client device to request the underlying data on which the respective portion has been generated by generative ML model620. The user interface component may include a button, icon, dropdown, tag, and/or tooltip, among other possibilities.

Thus, by interacting with (e.g., clicking, dragging, selecting, hovering over, etc.) the user interface component associated with the generated textual string, a user may cause the client device to request the particular textual string (identified in response sources604) that provides an answer to the same query as the generated textual string. That is, the user interface may allow the user to view the underlying data in response sources604used for generating each of the different portions of updated document628. Alternatively, the underlying data may be included as part of updated document628, and thus selection and/or interaction with the user interface component may cause the client device to display the underlying data without a separate request to document generation system600for the underlying data.

In some implementations, document generation system600may be configured to monitor query sources602and/or response sources604to determine whether any queries and/or information sources used in generating updated document628have been modified. When a modification to any queries and/or information sources used in generating updated document628is identified, document generation system600may be configured to regenerate updated document628and/or a portion thereof based on the queries and/or information sources as updated. Thus, document generation system600may be configured to automatically keep updated document628up-to-date with any relevant new information in query sources602and/or response sources604.

For example, response selector612may be configured to determine that a particular information source has been modified. Based on this determination, response selector612may be configured to determine that the particular information source as modified provides a first response to a corresponding query, where the first response differs from a second response to the corresponding query provided by updated document628and/or a prior version of the particular information source as used for generating updated document628. That is, response selector612may be configured to determine that response sources604include a new and/or improved answer to the corresponding query, thus indicating that updated document628may be improved by incorporating this new and/or improved answer. Accordingly, based on determining that the first response differs from the second response, generative ML model620may be configured to generate another version of updated document628based on the particular information source as modified, and possibly based additionally on any of the inputs discussed above.

In some implementations, portions of updated document628may be modified by one or more users. For example, a user may manually edit the content of updated document628to provide additional responses, improve existing responses, and/or adjust a writing style of updated document628, among other potential modifications. Such user modifications of updated document628may be tracked by document generation system600. When a new version of updated document628is generated that alters any user-modified portions of a prior version of updated document628, these alterations may be presented to a user and/or administrator for approval before the new version of updated document628is published and/or released.

For example, document generation system600may be configured to determine a difference between the new version and the prior version of updated document628, and may cause this difference to be displayed to the user and/or administrator using a user interface. The user and/or administrator may be prompted, using the user interface, to select the content of the new version, select the content of the prior version, and/or provide new content for the new version of updated document628. That is, when updated document628includes user-specified content, document generation system600may ask the user and/or administrator to resolve any conflicts between the contents of different versions of updated document628, thus increasing the likelihood of updated document628correctly addressing queries610.

VII. Example Message Flow Diagram

FIG.7illustrates an example message flow diagram that illustrates operations of generative ML model620, validation model624, and document database700. Document database700may be configured to store documents that have been generated by generative ML model620and validated by validation model624. Document database700may represent, for example, a knowledge database configured to store a plurality of knowledge base articles.

Generative ML model620may be configured to generate a document based on a topic and an information source, as indicated by block702. Generation of the document may be prompted by a document prompt. For example, the document generated at block702may correspond to document622. Based on and/or in response to generation of the document at block702, generative ML model620may be configured to provide the document to validation model624, as indicated by arrow704. That is, prior to storage and/or publication of the document using document database700, the document may be assessed for sufficiency, adequacy, and/or completeness using validation model624.

Based on and/or in response to reception of the document at arrow704, validation model624may be configured to determine a query that is not addressed by the document, as indicated by block706. That is, validation model624may determine that the document is insufficient, inadequate, and/or incomplete at least in that it fails to address the query. Based on and/or in response to identifying the query at block706, validation model624may be configured to provide the query to generative ML model620, as indicated by arrow708.

Based on and/or in response to reception of the query at arrow708, generative ML model620may be configured to generate an updated document based on the topic, the information source, and the query, as indicated by block710. Thus, the query may be explicitly provided to generative ML model620as an additional input, thus prompting generative ML model620to address the query in a subsequent version of the document. The query might not be provided as an input to generative ML model620as part of the operations at block702. That is, generative ML model620may generate the document at block702based on the topic corresponding to the query determined at block706, but independently of the query itself. This approach may promote conciseness and reduce the likelihood of redundant content in the document, while allowing any unaddressed questions to be addressed by revised versions of the document.

Based on and/or in response to generation of the updated document at block710, generative ML model620may be configured to provide the updated document to validation model624, as indicated by arrow712. Since the updated document is based on the query identified at block706, it is more likely that the updated document addresses the query, and thus provides a more complete response to the document prompt.

In some cases, based on and/or in response to reception of the updated document at arrow712, validation model624may be configured to determine that an additional query is not addressed by the updated document. That is, the operations of block706through arrow712may be repeated, as indicated by arrow720, to identify and address the additional query. Thus, generative ML model620may generate, and validation model624may evaluate, one or more updated versions of the updated article before generating a version that is adequate, sufficient, and/or complete, with each version of the document being generated further based on any questions that have not been addressed by a prior version of the document.

Based on and/or in response to reception of the updated document at arrow712(possibly following generation of multiple versions of the updated document), validation model624may be configured to determine that the updated document addresses all queries, as indicated by block714. That is, validation model624may be configured to determine that the updated document is adequate, sufficient, and/or complete at least in that it addresses all queries that are semantically related to the document prompt.

Based on and/or in response to determining that the updated document addresses all queries at block714, validation model624may be configured to provide the updated document to document database700, as indicated by arrow716. Based on and/or in response to reception of the updated document at arrow716, document database700may be configured to store the updated document, as indicated by block718. Storage of the updated document in document database700may allow the updated document to be accessed and/or viewed by one or more users and/or computing systems.

VIII. Example Generative ML Model Input

FIG.8illustrates an example structure of the input data for generative ML model620. Specifically, generative ML model input830provides an example textual representation of document prompt606, topic(s)618, information source(s)614, and unaddressed query626.

Lines800,801,808, and809of generative ML model input830represent aspects of document prompt606. Specifically, the text on lines800and801may represent a default portion of document prompt606, while the text on line809may be supplied by a user and/or computing system to specify subject836as the subject for the document. For example, subject836may relate to setting up one or more technical aspects of remote network management platform320in connection with a managed network.

Lines803-806of generative ML model input830represent information source(s)614. Information source(s)614may include textual representations of information source832through information source834(“information sources832-834”). For example, each respective information source of information sources832-834may include a corresponding textual string extracted from response sources604to answer a corresponding query of queries610.

Lines811-814of generative ML model input830represent topic(s)618. Topic(s)618may include textual representations of topic838through topic840(“topics838-840”). For example, each respective topic of topics838-840may include a corresponding textual string generated by text summarization model616based on corresponding one or more of queries610.

Lines816-819of generative ML model input830represent unaddressed query626and/or any queries included as part of document prompt606. These queries may include textual representations of query842through query844(“queries842-844”). For example, each respective query of queries842-844may include a corresponding textual string representing unaddressed query626and/or any queries included as part of document prompt606.

In some cases, generative ML model input830used in connection with a first iteration of generative ML model620might not include any queries (i.e., lines816-819might be empty). As validation model624identifies unanswered queries, queries may be added to generative ML model input830. For example, over the course of multiple iterations of generative ML model620, the “queries” portion of generative ML model input830may get successively longer as additional unanswered queries are accumulated. That is, for a given iteration of generative ML model620, generative ML model input830may include all queries that have not been addressed by all prior versions of a given document, thus prompting generative ML model to address all previously-identified deficiencies in the document.

IX. Example Technical Improvements

These embodiments provide a technical solution to a technical problem. One technical problem being solved is how to programmatically facilitate the generation and review of documents by generative ML models. In practice, this is problematic because it may be difficult to objectively asses when a document completely covers and/or describes a particular subject.

In the prior art, the adequacy, sufficiency, and/or completeness of a document was typically unknown. Document evaluations relied on subjective decision making, which led to wildly varying outcomes from instance to instance. Thus, prior art techniques did little if anything to address the variability in the quality of documents, much less being able to quickly and accurately generate and review large numbers of documents.

The embodiments herein overcome these limitations by combining a generative ML model with a validation model configured to determine whether documents generated by the generative ML model answer each of a plurality of questions associated with a subject of the document. In this manner, accurate review and evaluation of documents generated by generative ML models can be accomplished in a more accurate and robust fashion. This results in several advantages. First, documents generated in this manner may address each of a plurality of questions associated with a given subject, and may thus be more likely to provide complete and/or accurate coverage of the subject for the document. Second, the documents may be generated and revised quickly and in a scalable fashion. Third, the generation and review may be based on a large number of different sources of information, thereby increasing the likelihood of produced documents being comprehensive and useful.

Other technical improvements may also flow from these embodiments, and other technical problems may be solved. Thus, this statement of technical improvements is not limiting and instead constitutes examples of advantages that can be realized from the embodiments.

X. Example Operations

FIG.9is a flow chart illustrating an example embodiment. The process illustrated byFIG.9may be carried out by a computing device, such as computing device100, and/or a cluster of computing devices, such as server cluster200. However, the process can be carried out by other types of devices or device subsystems. For example, the process could be carried out by a computational instance of a remote network management platform or a portable computer, such as a laptop or a tablet device.

The embodiments ofFIG.9may be simplified by the removal of any one or more of the features shown therein. Further, these embodiments may be combined with features, aspects, and/or implementations of any of the previous figures or otherwise described herein.

Block900may involve obtaining a topic of a document and an information source associated with the document.

Block902may involve generating, using a generative ML model, the document based on the topic and the information source.

Block904may involve identifying a query that is associated with the topic.

Block906may involve determining, using a validation model, that the query is not addressed by the document.

Block908may involve, based on determining that the query is not addressed by the document, generating an updated document using the generative ML model based on the topic, the information source, and the query.

Block910may involve determining, using the validation model, that the query is addressed by the updated document.

Block912may involve outputting the updated document.

In some examples, the document may include a knowledge base article.

In some examples, an instruction to generate the document may be obtained. The instruction may indicates a subject for the document. The subject may span a plurality of topics that includes the topic. The generative ML, model may be configured to generate the document and the updated document further based on the instruction.

In some examples, the document may be associated with a subject that spans a plurality of topics including the topic. Identifying the query may include identifying one or more queries associated with the subject based on a similarity between the subject and the one or more queries. The one or more queries may include the query. The topic may be determined by processing the one or more queries using a text summarization model.

In some examples, the one or more queries may include a plurality of queries. The text summarization model may be configured to summarize two or more queries of the plurality of queries by determining the topic to collectively represent the two or more queries.

In some examples, identifying the one or more queries may include determining, for each respective query of a plurality of queries associated with the subject, a corresponding similarity value representing a similarity between the subject and the respective query. The one or more queries may be selected from the plurality of queries based on each of the one or more queries having a corresponding similarity value that exceeds a threshold query similarity value.

In some examples, the document may be associated with a subject that spans a plurality of topics including the topic. Obtaining the information source may include identifying one or more information sources associated with the subject based on a similarity between the subject and the one or more information sources. The one or more information sources may include the information source. Obtaining the information source may also include determining, using a query answering model, that the query is addressable using the one or more information sources. The document may be generated based on determining that the query is addressable using the one or more information sources.

In some examples, identifying the one or more information sources may include determining, for each respective information source of a plurality of information sources associated with the subject, a corresponding similarity value representing a similarity between the subject and the respective information source. The one or more information sources may be selected from the plurality of information sources based on each of the one or more information sources having a corresponding similarity value that exceeds a threshold information similarity value.

In some examples, determining that the query is addressable using the one or more information sources may include identifying within the one or more information sources a textual string that answers the query. The information source may include the textual string exclusive of other parts of the one or more information sources.

In some examples, a textual string selected from the information source to answer the query may be stored. The query may be addressed by the updated document using a generated textual string that differs from the textual string. Instructions configured to cause display of the updated document using a user interface may be transmitted to a client device. The user interface may include a user interface component associated with the generated textual string and configured to receive a request for the textual string selected from the information source to answer the query. The request for the textual string may be received, from the client device, based on an interaction with the user interface component. Based on receiving the request for the textual string, additional instructions may be transmitted to the client device. The additional instructions may be configured to cause display of the textual string using the user interface.

In some examples, a user-specified query to be answered by the document may be received. The generative ML model may be configured to generate the document and the updated document further based on the user-specified query.

In some examples, the generative ML model may be configured to generate the updated document further based on contextual data associated with generating the document.

In some examples, a second query that is associated with the topic may be identified. It may be determined, using the validation model, that the second query is not addressed by the updated document. Based on determining that the second query is not addressed by the document, a second updated document may be generated using the generative ML model based on the topic, the information source, the query, and the second query. Using the validation model, it may be determined that each of the query and the second query is addressed by the second updated document. The second updated document may be output.

In some examples, generating the document may include generating the document using the generative ML model based on a plurality of topics for the document and a plurality of information sources associated with the document. Identifying the query may include identifying a plurality of queries. Determining that the query is not addressed by the document may include determining, using the validation model, that a plurality of queries are not addressed by the document. Generating the updated document may include, based on determining that the plurality of queries are not addressed by the document, generating the updated document using the generative ML model based on the plurality of topics, the plurality of information sources, and the plurality of queries. Determining that the query is addressed by the updated document may include determining, using the validation model, that each of the plurality of queries is addressed by the updated document.

In some examples, the generative ML model may include a large language model that has been trained to generate documents using a target writing style represented by a plurality of sample documents.

In some examples, the updated document may be generated for a managed network. Each of the query and the information source may be determined based on one or more of: (i) an email associated with the managed network, (ii) a meeting associated with the managed network, (iii) documentation of a product associated with the managed network, (iv) documentation of a process associated with the managed network, (v) contents of a task performed in association with the managed network, (vi) a forum associated with the managed network, (vii) a blog posts associated with the managed network, (viii) a chat group associated with the managed network, or (ix) a phone call associated with the managed network.

In some examples, it may be determined that the information source has been modified. Based on determining that the information source has been modified, it may be determined, using a query answering model, that a first response to the query provided by the updated document is different from a second response to the query provided by the information source as modified. Based on determining that the first response is different from the second response, a second updated document may be generated using the generative ML model based on the topic and the information source as modified. The second updated document may be output.

In some examples, a modification to the updated document may be received by way of a user interface. A second updated document may be generated using the generative ML model. It may be determined that a first portion of the updated document differs from a second portion of the second updated document. The first portion may correspond to the modification received by way of the user interface. The second portion may correspond to the first portion at least in that the second portion addresses a same query as the first portion. Based on determining that the first portion differs from the second portion, display may be caused of a representation of a difference between the first portion and the second portion by way of the user interface. A specification of content for the second portion may be received by way of the user interface based on causing display of the representation of the difference.

XI. Closing

The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations can be made without departing from its scope, as will be apparent to those skilled in the art. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those described herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims.

The above detailed description describes various features and operations of the disclosed systems, devices, and methods with reference to the accompanying figures. The example embodiments described herein and in the figures are not meant to be limiting. Other embodiments can be utilized, and other changes can be made, without departing from the scope of the subject matter presented herein. It will be readily understood that the aspects of the present disclosure, as generally described herein, and illustrated in the figures, can be arranged, substituted, combined, separated, and designed in a wide variety of different configurations.

With respect to any or all of the message flow diagrams, scenarios, and flow charts in the figures and as discussed herein, each step, block, and/or communication can represent a processing of information and/or a transmission of information in accordance with example embodiments. Alternative embodiments are included within the scope of these example embodiments. In these alternative embodiments, for example, operations described as steps, blocks, transmissions, communications, requests, responses, and/or messages can be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved. Further, more or fewer blocks and/or operations can be used with any of the message flow diagrams, scenarios, and flow charts discussed herein, and these message flow diagrams, scenarios, and flow charts can be combined with one another, in part or in whole.

A step or block that represents a processing of information can correspond to circuitry that can be configured to perform the specific logical functions of a herein-described method or technique. Alternatively or additionally, a step or block that represents a processing of information can correspond to a module, a segment, or a portion of program code (including related data). The program code can include one or more instructions executable by a processor for implementing specific logical operations or actions in the method or technique. The program code and/or related data can be stored on any type of computer readable medium such as a storage device including RAM, a disk drive, a solid-state drive, or another storage medium.

The computer readable medium can also include non-transitory computer readable media such as non-transitory computer readable media that store data for short periods of time like register memory and processor cache. The non-transitory computer readable media can further include non-transitory computer readable media that store program code and/or data for longer periods of time. Thus, the non-transitory computer readable media may include secondary or persistent long-term storage, like ROM, optical or magnetic disks, solid-state drives, or compact disc read only memory (CD-ROM), for example. The non-transitory computer readable media can also be any other volatile or non-volatile storage systems. A non-transitory computer readable medium can be considered a computer readable storage medium, for example, or a tangible storage device.

Moreover, a step or block that represents one or more information transmissions can correspond to information transmissions between software and/or hardware modules in the same physical device. However, other information transmissions can be between software modules and/or hardware modules in different physical devices.

The particular arrangements shown in the figures should not be viewed as limiting. It should be understood that other embodiments could include more or less of each element shown in a given figure. Further, some of the illustrated elements can be combined or omitted. Yet further, an example embodiment can include elements that are not illustrated in the figures.

While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purpose of illustration and are not intended to be limiting, with the true scope being indicated by the following claims.