# US 2020/0287984 A1 · Systems and methods for automated module-based content provisioning

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

- Number: US 2020/0287984 A1
- Document ID: US20200287984A1
- Status: Published application
- Kind: A1
- Application number: 16/827,441
- Filed: 2020-03-23
- Published: 2020-09-10
- Earliest claimed: 2018-04-12
- Assignees: Pearson Management Services Limited
- Applicants: Pearson Management Services Ltd
- Inventors: James Walsh; Suhail Khaki
- Web page: https://patentgrep.com/patent/US20200287984A1

## 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

(canceled)

### Claim 2

A system for content provisioning, the system comprising:
a memory comprising:
a content library database containing educational content; and
an asset database comprising a plurality of learning assets each comprising a link to content;
at least one server configured to:
receive first content information associated with first educational content;
package a first learning asset comprising a link directing to the first educational content, wherein the first learning asset is formed from the first content information;
enrich the first learning asset with metadata relating to the first educational content, wherein the first learning asset is packaged and enriched via a data packaging module of the at least one server;
receive a first content request; and
deliver the first learning asset in response to the first content request.

### Claim 3 (depends on 2)

The system of claim 2, wherein the at least one server comprises a communications microservice configured to generate a digest based on inputs from other microservices of the at least one server; and wherein the first learning asset is deliverable subsequent to inclusion of an indicator of completion of enriching in the digest.

### Claim 4 (depends on 3)

The system of claim 3, wherein the at least one server is further configured to:
receive second content information associated with second educational content, wherein the second educational content comprises content in the content library database;
package a second learning asset comprising a link directing to the second educational content; and
enrich the second learning asset with metadata relating to the second educational content, and
wherein the first educational content comprises content stored on a remote content platform.

### Claim 5 (depends on 4)

The system of claim 4, wherein the received second content information is packaged via the data packaging module, and wherein the second learning asset is enriched via the data packaging module.

### Claim 6 (depends on 5)

The system of claim 5, wherein the at least one server is further configured to: store the first learning asset and the second learning asset in the asset database.

### Claim 7 (depends on 6)

The system of claim 6, wherein the metadata enriching the first learning asset identifies a first content type and wherein the metadata enriching the second learning asset identifies a second content type.

### Claim 8 (depends on 7)

The system of claim 7, wherein the first content type specifies a file type of the first educational content linked by the first learning asset and the second content type specifies a file type of the second educational content linked by the second learning asset.

### Claim 9 (depends on 8)

The system of claim 8, wherein the file type of the first educational content is the same as the file type of the second educational content.

### Claim 10 (depends on 9)

The system of claim 9, wherein the at least one server is further configured to determine a type of each of the first learning asset and the second learning asset.

### Claim 11

A method for content provisioning, the method comprising:
receiving first content information associated with first educational content at at least one server;
packaging with the at least one server a first learning asset comprising a link directing to the first educational content from the first content information;
enriching with the at least one server the first learning asset with metadata relating to the first educational content;
receiving a first content request at the server; and
delivering the first learning asset in response to the first content request.

### Claim 12 (depends on 11)

The method of claim 11, wherein the at least one server comprises: a communications microservice; a data packaging module; a model building module; and an engagement delivery module.

### Claim 13 (depends on 12)

The method of claim 12, wherein the received first content information is packaged via the data packaging module, and wherein the first learning asset is enriched via the data packaging module.

### Claim 14 (depends on 13)

The method of claim 13, wherein each of the data packaging module, the model building module, and the engagement delivery module send data to the communications microservice and receive a digest from the communications microservice.

### Claim 15 (depends on 14)

The method of claim 14, wherein the first learning asset is deliverable subsequent to inclusion of an indicator of completion of enriching in the digest from the communications microservice.

### Claim 16 (depends on 15)

The method of claim 15, further comprising:
receiving second content information associated with second educational content, wherein the second educational content comprises native content;
packaging a second learning asset comprising a link directing to the second educational content from the first content information; and
enriching the second learning asset with metadata relating to the second educational content, wherein the received second content information is packaged via the data packaging module, wherein the second learning asset is enriched via the data packaging module, and
wherein the first educational content comprises remote content stored on a remote content platform.

### Claim 17 (depends on 16)

The method of claim 16, further comprising storing the first learning asset and the second learning asset in an asset database comprising a plurality of learning assets.

### Claim 18 (depends on 17)

The method of claim 17, wherein each of the plurality of learning assets comprises a link to associated content, wherein each of the plurality of learning assets are enriched with metadata, wherein the metadata enriching the first learning asset identifies a first content type, and wherein the metadata enriching the second learning asset identifies a second content type.

### Claim 19 (depends on 18)

The method of claim 18, wherein the first content type specifies a file type of the first educational content linked by the first learning asset and the second content type specifies a file type of the second educational content linked by the second learning asset.

### Claim 20 (depends on 19)

The method of claim 19, wherein the file type of the first educational content is the same as the file type of the second educational content.

### Claim 21 (depends on 20)

The method of claim 20, further comprising: determining a type of each of the first learning asset and the second learning asset.