IP Library › Granted Patent US 12694198

Granted Patent B2

US 12694198 · App. 18/588,979 · Granted Jul 28, 2026

Model creation and management using a model management service

Inventors: Michael Roybal (Woodinville, WA); Matthew Heyer (Saint George, UT); Wilson Huang (Pleasanton, CA)

Assignee: AT&T Intellectual Property I, I.P.

G06F40/117 G06F40/197

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 12694198
App. No.: 18/588,979
Granted: Jul 28, 2026
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

Model creation and management using a model management service can include obtaining model management data that comprises modeling data that defines a project to model, the project including a network flow, a network system, a device, or a process; detecting, in the model management data, a selection of a template to apply to the project to generate the model; and creating, based on the model management data and the template, the model. The model can include a directory, a data structure, and a diagram that describes the project. The model can be converted into a device-agnostic format version of the model and loaded to a data storage resource as model data that can include the device-agnostic format version of the model.

Claims (80)

1 . A system comprising a processor and a memory that stores computer-executable instructions that, when executed by the processor, cause the processor to perform operations comprising:

obtaining, via a network connection and from a user device that has authenticated with a model management service, model management data that comprises modeling data that defines a project that is to be modeled, wherein the project comprises a network flow or a process that is performed at the user device;

obtaining, from a code repository and based on the project that is defined by the modeling data, code associated with the project;

identifying, based on the project, scripts that are to be executed by the user device during modeling of the project;

identifying, based on the model management data, a template that is to be applied to the project to generate a model;

providing, to the user device and via the network connection, the template, the code, and the scripts, wherein the user device creates, based on the project, the template, the code, and the scripts, the model by generating a directory, a data structure, and a diagram that describes the project, wherein the user device creates the model in a proprietary format;

obtaining, from the user device, the model in the proprietary format;

converting the model from the proprietary format to a device-agnostic format version of the model;

storing, at a common repository, model data that comprises the device-agnostic format version of the model;

receiving a request for a model history view relating to the model;

obtaining model data and a model history from the common repository, wherein the model data describes the model, and wherein the model history describes lifecycle events associated with the model;

generating the model history view, wherein the model history view depicts model update events associated with the model and versions of the model; and

enabling interactions with the model history view by the user device via portal.

2 . The system of claim 1 , wherein the device-agnostic format version of the model comprises hypertext markup language or extensible markup language.

3 . The system of claim 1 , wherein the model history comprises data that describes creation of the model and a history of updates and iterations of the model over the history of updates.

4 . The system of claim 1 , wherein the computer-executable instructions, when executed by the processor, cause the processor to perform operations further comprising:

detecting a model update comprising a request to update the model;

retrieving, from the common repository, the model data;

updating the model based on the model update;

generating a model update event that defines an update to the model;

adding the model update event to the model history, wherein the model history is stored at the common repository; and

storing the model update event and an updated model history at the common repository.

5 . The system of claim 4 , wherein the model update event comprises an addition to the model, and wherein updating the model comprises:

obtaining an asset from an asset catalog, wherein the asset relates to the addition and comprises a portion of the project in a modeling language; and

updating the model data associated with the model based on the asset and the model update event.

6 . The system of claim 1 , wherein the diagram comprises a unified modeling language model.

7 . The system of claim 6 , wherein the model history view comprises depictions of at least two model update events associated with the model, the model update events being obtained from the model history, and wherein the model history view provides access to at least two versions of the model.

8 . A method comprising:

obtaining, via a network connection and at a server computer comprising a processor and from a user device that has authenticated with a model management service, model management data that comprises modeling data that defines a project that is to be modeled, wherein the project comprises a network flow or a process that is performed at the user device;

obtaining, by the processor and from a code repository based on the project that is defined by the modeling data, code associated with the project;

identifying, based on the project, scripts that are to be executed by the user device during modeling of the project;

identifying, by the processor and based on the model management data, a template that is to be applied to the project to generate a model;

providing, by the process and to the user device via the network connection, the template, the code, and the scripts, wherein the user device creates, based on the project, the template, the code, and the scripts, the model by generating a directory, a data structure, and a diagram that describes the project, wherein the user device creates the model in a proprietary format;

obtaining, by the processor and from the user device, the model in the proprietary format;

converting the model from the proprietary format to a device-agnostic format version of the model;

storing, by the processor and at a common repository, model data that comprises the device-agnostic format version of the model;

receiving a request for a model history view relating to the model;

obtaining model data and a model history from the common repository, wherein the model data describes the model, and wherein the model history describes lifecycle events associated with the model;

generating the model history view, wherein the model history view depicts model update events associated with the model and versions of the model; and

enabling interactions with the model history view by the user device via portal.

9 . The method of claim 8 , wherein the device-agnostic format version of the model comprises hypertext markup language or extensible markup language.

10 . The method of claim 8 , wherein the model history comprises data that describes creation of the model and a history of updates and iterations of the model over the history of updates.

11 . The method of claim 8 , further comprising:

detecting, by the processor, a model update comprising a request to update the model;

retrieving, by the processor and from the common repository, the model data;

updating, by the processor, the model based on the model update;

generating, by the processor, a model update event that defines an update to the model;

adding, by the processor, the model update event to the model history, wherein the model history is stored at the common repository; and

storing, by the processor, the model update event and an updated model history at the common repository.

12 . The method of claim 11 , wherein the model update event comprises an addition to the model, and wherein updating the model comprises:

obtaining an asset from an asset catalog, wherein the asset relates to the addition and comprises a portion of the project in a modeling language; and

updating the model data associated with the model based on the asset and the model update event.

13 . The method of claim 8 , wherein the diagram comprises a unified modeling language model, wherein the model history view comprises depictions of at least two model update events associated with the model, the model update events being obtained from the model history, and wherein the model history view provides access to at least two versions of the model.

14 . A computer storage medium having computer-executable instructions stored thereon that, when executed by a processor, cause the processor to perform operations comprising: