Systems and methods for automated module-based content provisioning

• US 10,601,942 B2
• Filed: 06/27/2018
• Issued: 03/24/2020
• Est. Priority Date: 04/12/2018
• Status: Active Grant

• Current Assignee: Pearson Management Services Limited (Pearson plc)
• Original Assignee: Pearson Management Services Limited (Pearson plc)
• Inventors: Walsh, James, Khaki, Suhail
• Primary Examiner(s): Khan, Atta
• Application Number:
  US16/020,927
• Publication Number:
  US 20190320005A1
• Time in Patent Office: 636 Days
• Field of Search: 709219
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: 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
• CPC Class Codes: G06F 16/907 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 21/12 Protecting executable software
• CPC Class Codes: G06F 40/30 Semantic analysis
• CPC Class Codes: G06F 9/4451 User profiles; Roaming
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: G06N 20/00 Machine learning
• CPC Class Codes: G06N 5/02 Knowledge representation; Symbolic representation
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/5051 Service on demand, e.g. definition and deployment of services in real time
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 63/0254 Stateful filtering
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 65/65 : Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 65/75 : Media network packet handling
• CPC Class Codes: H04L 67/01 : Protocols
• CPC Class Codes: H04L 67/02 : based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/025 : for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/04 : specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/108 : characterised by resources being split in blocks or fragments
• CPC Class Codes: 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]
• CPC Class Codes: H04L 67/141 : Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/306 : User profiles
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/53 : using third party service providers
• CPC Class Codes: H04L 67/535 : Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/567 : Integrating service provisioning from a plurality of service providers
• CPC Class Codes: 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
• CPC Class Codes: 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

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

1. A system for hybrid content provisioning of remote content stored on a remote content platform and native content stored within the system, the system comprising:

a memory comprising;

a content library database containing native content; and

an asset database comprising a plurality of package-data assets each comprising a link directing to content, wherein the content comprises native content and remote content, wherein the remote content is stored on the remote content platform;

at least one server comprising;

a communications microservice;

a data packaging module;

a model building module; and

an engagement delivery module, wherein each of the data packaging module, the model building module, and the engagement delivery module are configured to send data to the communications microservice and receive a digest from the communications microservice, and wherein the at least one server is configured to;

receive first content information associated with first content stored on the remote content platform;

package the received first content information into a first package-data asset comprising a link directing to first content stored on the remote content platform and enrich the first package-data asset with metadata relating to the received first content, wherein the received first content information is packaged and wherein the first package-data asset is enriched via the data packaging module;

receive a first content request;

identify a first package-data asset associated with remote content;

deliver the first package-data asset to a user device;

receive a second content request;

identify a second package-data asset associated with native content; and

deliver the second package-data asset to the user device.

2. The system of claim 1, wherein the first package-data asset is deliverable to the user device subsequent to receipt of an indicator of completion of enriching from the digest from the communications microservice.

3. The system of claim 2, wherein the at least one server is further configured to:

receive second content information associated with the second content, wherein the second content comprises native content;

package the received second content information into a second package-data asset comprising a link directing to the second content; and

enrich the second package-data asset with metadata relating to the second content.

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

5. The system of claim 4, wherein the at least one server is further configured to:

store the first package-data asset and the second package-data asset in the asset database.

6. The system of claim 5, wherein the metadata enriching the first package-data asset identifies a first content type and wherein the metadata enriching the second package-data asset identifies a second content type.

7. The system of claim 6, wherein the first content type specifies a file type of the first content linked by the first package-data asset and the second content type specifies a file type of the second content linked by the second package-data asset.

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

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

10. A method for hybrid content provisioning of remote content stored on a remote content platform and native content, the method comprising:

receiving at least one server first content information associated with first content stored on a remote content platform;

packaging with the at least one server the received first content information into a first packaged data-asset comprising a link directing to content stored on the remote content platform;

enriching with the at least one server the first packaged data-asset with metadata relating to the received content;

receiving at the server a first content request from a first user device;

identifying a first package-data asset associated with remote content;

delivering the first package-data asset to the first user device;

receiving at the server a second content request from the first user device;

identifying a second package-data asset associated with native content; and

delivering the second package-data asset to the first user device.

11. The method of claim 10, wherein the at least one server comprises:

a communications microservice;

a data packaging module;

a model building module; and

an engagement delivery module.

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

13. The method of claim 12, 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.

14. The method of claim 13, wherein the first package-data asset is deliverable to the user device subsequent to receipt of an indicator of completion of enriching from the digest from the communications microservice.

15. The method of claim 14, further comprising:

receiving second content information associated with the second content, wherein the second content comprises native content;

packaging the received second content information into a second package-data asset comprising a link directing to the second content; and

enriching the second package-data asset with metadata relating to the second content, wherein the received second content information is packaged via the data packaging module, and wherein the second package-data asset is enriched via the data packaging module.

16. The method of claim 15, further comprising storing the first package-data asset and the second package-data asset in an asset database comprising a plurality of package-data assets each enriched with metadata and each comprising a link directing to associated content.

17. The method of claim 16, wherein the metadata enriching the first package-data asset identifies a first content type and wherein the metadata enriching the second package-data asset identifies a second content type.

18. The method of claim 17, wherein the first content type specifies a file type of the first content linked by the first package-data asset and the second content type specifies a file type of the second content linked by the second package-data asset.

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

20. The method of claim 19, further comprising:

determining a type of each of the first package-data asset and the second package-data asset.