# US 2019/0320030 A1 · System and method for automated hybrid network creation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0320030 A1
- Document ID: US20190320030A1
- Status: Published application
- Kind: A1
- Application number: 16/020,977
- Filed: 2018-06-27
- Published: 2019-10-17
- Earliest claimed: 2018-04-12
- Assignees: Pearson Management Services Limited
- Applicants: Pearson Management Services Limited
- Inventors: James Walsh; Suhail Khaki
- Web page: https://patentgrep.com/patent/US20190320030A1

## CPC

- G06F 16/958: Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F 9/4451: {User profiles; Roaming}
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 9/546: {Message passing systems or structures, e.g. queues}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 11/2023: {Failover techniques}
- G06F 16/40: of multimedia data, e.g. slideshows comprising image and additional audio data (retrieval of still image data G06F16/50; retrieval of audio data G06F16/60; retrieval of video data G06F16/70)
- G06F 16/907: Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
- G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links}
- G06F 16/9574: {of access to content, e.g. by caching}
- G06F 21/12: Protecting executable software
- G06F 40/30: Semantic analysis
- G06N 5/02: Knowledge representation; Symbolic representation
- G06N 20/00: Machine learning
- H04L 41/0803: Configuration setting
- H04L 41/5051: Service on demand, e.g. definition and deployment of services in real time
- H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
- H04L 41/5096: {wherein the managed service relates to distributed or central networked applications}
- H04L 63/0254: {Stateful filtering}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 65/65: Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
- H04L 67/025: for remote control or remote monitoring of applications
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/108: {characterised by resources being split in blocks or fragments}
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L 67/306: User profiles
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L 67/53: using third party service providers
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- H04L 67/567: Integrating service provisioning from a plurality of service providers
- H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70)
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/04: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A global architecture (GLP), as disclosed herein, is based on the thin server architectural pattern; it delivers all its services in the form of web services and there are no user interface components executed on the GLP. Each web service exposed by the GLP is stateless, which allows the GLP to be highly scalable. The GLP is further decomposed into components. Each component is a microservice, making the overall architecture fully decoupled. Each microservice has fail-over nodes and can scale up on demand. This means the GLP has no single point of failure, making the platform both highly scalable and available. The GLP architecture provides the capability to build and deploy a microservice instance for each course-recipient-user combination. Because each student interacts with their own microservice, this makes the GLP scale up to the limit of cloud resources available—i.e. near infinity.

## Claims

### Claim 1

A system for hybrid content graph creation, the system comprising:
a memory comprising:
an asset database comprising a plurality of package-data assets each comprising a link directing to content, wherein at least some of the content is stored on a remote content platform; and
a capability database including information identifying capabilities of a plurality of microservices; and
at least one server comprising the plurality of microservices, wherein the at least one server is configured to:
identify a set of package-data assets from the asset database of the memory;
retrieve a content model associated with the set of package-data assets;
automatically determine a sequencing of package-data assets in the set of package-data assets, wherein the sequencing is partially adaptive-based and partially non-adaptive-based; and
generate a graphical representation of the set of package-data assets based on the determined sequencing

### Claim 2 (depends on 1)

The system of claim 1, wherein the content model is retrieved from the memory.

### Claim 3 (depends on 2)

The system of claim 2, wherein the at least one server is further configured to identify a first group comprising at least some of the set of package-data assets as having a first asset type and identify a second group comprising at least some of the set of package-data assets as having a second asset type.

### Claim 4 (depends on 3)

The system of claim 3, wherein the at least some of the set of package-data assets included in the first group are different than the at least some of the set of package-data assets included in the second group.

### Claim 5 (depends on 4)

The system of claim 4, wherein the first asset type comprises content-type package-data assets and wherein the second asset type comprises non-content-type package-data assets.

### Claim 6 (depends on 5)

The system of claim 5, wherein the at least one server is configured to: (a) select a one of the package-data assets in the set of package-data assets; (b) determine a sequencing type for the selected one of the package-data assets, wherein the sequencing type identifies at least one of adaptive sequencing, non-adaptive sequencing, and partially adaptive sequencing; and repeat (a) and (b) until a sequencing type for all of package-data assets in the set of package data assets is determined.

### Claim 7 (depends on 6)

The system of claim 6, wherein determining the sequencing comprises, for non-adaptive package-data assets: retrieving sequencing information; and sequencing the non-adaptive package-data assets according to the retrieved sequencing information.

### Claim 8 (depends on 7)

The system of claim 7, wherein determining the sequencing comprises, for the adaptive package-data assets: determining a skill level for package-data assets having and adaptive sequencing type; and identifying prerequisite relationships between the package-data assets.

### Claim 9 (depends on 8)

The system of claim 8, wherein the at least one server is further configured to store non-content type package-data assets in the memory.

### Claim 10 (depends on 9)

The system of claim 9, wherein the at least one server is further configured to link content-type package-data assets and non-content-type package-data assets.

### Claim 11

A method of automatic hybrid content graph creation, the method comprising:
identifying a set of package-data assets;
retrieving a content model associated with the set of package-data assets;
automatically determining an initial sequencing of package-data assets in the set of package-data assets, wherein the sequencing is partially adaptive-based and partially non-adaptive-based; and
generating a graphical representation of the set of package-data assets based on the determined sequencing.

### Claim 12 (depends on 11)

The method of claim 11, wherein the content model is retrieved from a memory.

### Claim 13 (depends on 12)

The method of claim 12, further comprising identifying a first group comprising at least some of the set of package-data assets as having a first asset type and identifying a second group comprising at least some of the set of package-data assets as having a second asset type.

### Claim 14 (depends on 13)

The method of claim 13, wherein the at least some of the set of package-data assets included in the first group are different than the at least some of the set of package-data assets included in the second group.

### Claim 15 (depends on 14)

The method of claim 14, wherein the first asset type comprises content-type package-data assets and wherein the second asset type comprises non-content-type package-data assets.

### Claim 16 (depends on 15)

The method of claim 15, further comprising: (a) selecting a one of the package-data assets in the set of package-data assets; (b) determining a sequencing type for the selected one of the package-data assets, wherein the sequencing type identifies at least one of adaptive sequencing, non-adaptive sequencing, and partially adaptive sequencing; and repeating (a) and (b) until a sequencing type for all of package-data assets in the set of package data assets is determined.

### Claim 17 (depends on 16)

The method of claim 16, wherein determining the sequencing comprises, for non-adaptive package-data assets: retrieving sequencing information; and sequencing the non-adaptive package-data assets according to the retrieved sequencing information.

### Claim 18 (depends on 17)

The method of claim 17, wherein determining the sequencing comprises, for the adaptive package-data assets: determining a skill level for package-data assets having and adaptive sequencing type; and identifying prerequisite relationships between the package-data assets.

### Claim 19 (depends on 18)

The method of claim 18, further comprising storing non-content type package-data assets in the memory.

### Claim 20 (depends on 19)

The method of claim 19, further comprising linking content-type package-data assets and non-content-type package-data assets.
