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.

IPC Classes  ?

• H04L 67/567 - Integrating service provisioning from a plurality of service providers
• G06F 9/445 - Program loading or initiating
• G06F 9/54 - Interprogram communication
• G06F 11/20 - Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
• G06F 16/40 - Information retrievalDatabase structures thereforFile system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
• G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• G06F 40/30 - Semantic analysis
• G06N 20/00 - Machine learning
• H04L 9/40 - Network security protocols
• H04L 41/0803 - Configuration setting
• H04L 41/50 - Network service management, e.g. ensuring proper service fulfilment according to agreements
• 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 65/65 - Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• H04L 65/75 - Media network packet handling
• H04L 67/00 - Network arrangements or protocols for supporting network services or applications
• H04L 67/10 - Protocols in which an application is distributed across nodes in the network
• H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
• H04L 67/141 - Setup of application sessions
• H04L 67/306 - User profiles
• H04L 67/50 - Network services
• H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
• 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
• H04L 67/01 - Protocols
• H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
• H04L 67/04 - Protocols specially adapted for terminals or networks with limited capabilitiesProtocols specially adapted for terminal portability

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.

IPC Classes  ?

• G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
• 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
• H04L 67/10 - Protocols in which an application is distributed across nodes in the network
• G06F 11/20 - Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
• G06F 9/54 - Interprogram communication
• G06F 16/40 - Information retrievalDatabase structures thereforFile system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• 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/50 - Network service management, e.g. ensuring proper service fulfilment according to agreements
• H04L 65/60 - Network streaming of media packets
• H04L 65/65 - Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• G06N 20/00 - Machine learning
• G06F 9/445 - Program loading or initiating
• H04L 67/306 - User profiles
• H04L 67/00 - Network arrangements or protocols for supporting network services or applications
• H04L 67/141 - Setup of application sessions
• H04L 67/50 - Network services
• H04L 41/0803 - Configuration setting
• H04L 29/06 - Communication control; Communication processing characterised by a protocol
• H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
• G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
• H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
• G06F 40/30 - Semantic analysis
• H04L 67/04 - Protocols specially adapted for terminals or networks with limited capabilitiesProtocols specially adapted for terminal portability
• H04L 67/01 - Protocols
• H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

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.

IPC Classes  ?

• H04L 67/567 - Integrating service provisioning from a plurality of service providers
• H04L 67/10 - Protocols in which an application is distributed across nodes in the network
• G06F 11/20 - Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
• G06F 9/54 - Interprogram communication
• G06F 16/40 - Information retrievalDatabase structures thereforFile system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• 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/50 - Network service management, e.g. ensuring proper service fulfilment according to agreements
• G06N 20/00 - Machine learning
• G06F 9/445 - Program loading or initiating
• H04L 67/306 - User profiles
• H04L 67/00 - Network arrangements or protocols for supporting network services or applications
• H04L 67/141 - Setup of application sessions
• H04L 41/0803 - Configuration setting
• H04L 9/40 - Network security protocols
• G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
• H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
• G06F 40/30 - Semantic analysis
• H04L 65/65 - Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• H04L 65/75 - Media network packet handling
• H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
• 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
• H04L 67/50 - Network services
• H04L 67/04 - Protocols specially adapted for terminals or networks with limited capabilitiesProtocols specially adapted for terminal portability
• H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
• H04L 67/01 - Protocols

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.

IPC Classes  ?

• G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
• H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
• G06F 11/20 - Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
• G06F 9/54 - Interprogram communication
• G06F 16/40 - Information retrievalDatabase structures thereforFile system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• H04L 12/24 - Arrangements for maintenance or administration
• H04L 29/06 - Communication control; Communication processing characterised by a protocol
• G06N 20/00 - Machine learning
• G06F 9/445 - Program loading or initiating
• G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
• G06F 40/30 - Semantic analysis

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.

IPC Classes  ?

• G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
• H04L 67/567 - Integrating service provisioning from a plurality of service providers
• H04L 67/10 - Protocols in which an application is distributed across nodes in the network
• G06F 11/20 - Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
• G06F 9/54 - Interprogram communication
• G06F 16/40 - Information retrievalDatabase structures thereforFile system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• 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/50 - Network service management, e.g. ensuring proper service fulfilment according to agreements
• G06N 20/00 - Machine learning
• G06F 9/445 - Program loading or initiating
• H04L 67/306 - User profiles
• H04L 67/00 - Network arrangements or protocols for supporting network services or applications
• H04L 67/141 - Setup of application sessions
• H04L 41/0803 - Configuration setting
• H04L 9/40 - Network security protocols
• G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
• H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
• G06F 40/30 - Semantic analysis
• H04L 65/65 - Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• H04L 65/75 - Media network packet handling
• H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
• 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
• H04L 67/50 - Network services
• H04L 67/04 - Protocols specially adapted for terminals or networks with limited capabilitiesProtocols specially adapted for terminal portability
• H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
• H04L 67/01 - Protocols

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.

IPC Classes  ?

• H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
• G06F 11/20 - Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
• G06F 9/54 - Interprogram communication
• G06F 16/40 - Information retrievalDatabase structures thereforFile system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• H04L 12/24 - Arrangements for maintenance or administration
• G06N 20/00 - Machine learning
• G06F 9/445 - Program loading or initiating
• G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
• H04L 29/06 - Communication control; Communication processing characterised by a protocol
• G06F 40/30 - Semantic analysis

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.

IPC Classes  ?

• G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
• H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
• G06F 11/20 - Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
• G06F 9/54 - Interprogram communication
• G06F 16/40 - Information retrievalDatabase structures thereforFile system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• H04L 12/24 - Arrangements for maintenance or administration
• H04L 29/06 - Communication control; Communication processing characterised by a protocol
• G06N 20/00 - Machine learning
• G06F 9/445 - Program loading or initiating
• G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
• G06F 40/30 - Semantic analysis

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.

IPC Classes  ?

• G06F 15/173 - Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star or snowflake
• H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
• G06F 11/20 - Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
• G06F 9/54 - Interprogram communication
• G06F 16/40 - Information retrievalDatabase structures thereforFile system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• H04L 12/24 - Arrangements for maintenance or administration
• H04L 29/06 - Communication control; Communication processing characterised by a protocol
• G06N 20/00 - Machine learning
• G06F 9/445 - Program loading or initiating
• G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
• G06F 40/30 - Semantic analysis

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.

IPC Classes  ?

• G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
• H04L 29/08 - Transmission control procedure, e.g. data link level control procedure
• G06F 11/20 - Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
• G06F 9/54 - Interprogram communication
• G06F 16/40 - Information retrievalDatabase structures thereforFile system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
• G06F 16/957 - Browsing optimisation, e.g. caching or content distillation
• H04L 12/24 - Arrangements for maintenance or administration
• H04L 29/06 - Communication control; Communication processing characterised by a protocol
• G06N 20/00 - Machine learning
• G06F 9/445 - Program loading or initiating
• G06F 16/907 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
• G06F 40/30 - Semantic analysis