System Architecture

From Oxygen.next Wiki

General System Design and Interaction of Components

Contents 1 Oxygen Management Suite 2 Oxygen API 3 Content Distribution Network 4 Database 5 Players 6 Transfer Matrix Method 7 Rights Management 8 Team 9 Player 10 User 11 Security Groups 12 Rights Management for Categories and Multimedia Content

[edit] Oxygen Management Suite

Via the Oxygen Management Suite (OMS) the user administers any number of players. An encrypted connection can be established via SSL. In the OMS the user can e.g. add, remove and configure users, teams, categories and multimedia content. The user’s content is uploaded to the OMS server via Port 80 (WebDAV) or via an upload form (applicable for files < 100MB).

[edit] Oxygen API

Further applications or frontend extensions can be created based on the Oxygen REST API. This layer guarantees flexible access to the system and independence from the respective graphic user interface. This API not only allows to administer databases but also the Content Distribution Network as well. The API can also be accessed via web services (REST).

[edit] Content Distribution Network

The Content Distribution Network (CDN) consists of any number of index, worker and file servers. The CDN is responsible for the distribution of all content so that the players can carry out performant content updates at any time. In this process the individual servers connect to the databases. The server’s mode of operation and the update process are described in the following chapter.

[edit] Database

The databases constitute the whole model of the system. Any number of databases can be addressed to via the OxygenAPI so that they can thereby synchronize with each other as well. Thus a cluster system can be applied to assure performant access to the data and to spread the load during access. At least one database must be available.

[edit] Players

The players connect to the CDN to update the available content of a system. Optionally an individual local frontend can be created for each player that allows to configure the player’s settings separately on-site.

[edit] Transfer Matrix Method

Once a player detects that a specific content item must be updated or has to be made available it will connect to an index server in the CDN first that will determine which worker server is currently available and can process the request. The worker server will then create a list of content and the associated performant file servers. Pursuant to this list the player can download the required data. The individual transmissions can also be carried out encryptedly. The number of servers is scalable so that they can also be set up in several data processing centers.

[edit] Rights Management

[edit] Team

A workgroup (“team”) can contain further teams. Players and users are defined in a team.

[edit] Player

A player plays multimedia content and is assigned to a specific team.

[edit] User

Any number of users can be added to a team. These users have access to players within the team and to subordinate players.

[edit] Security Groups

To simplify user administration users are integrated into security groups such as user or administrator. Groups can be defined as desired with appropriate rights.

[edit] Rights Management for Categories and Multimedia Content

For each created category and for each available content specific rights can be set. It is definable whether they can be configured locally only or via the Management Suite. The visibility of a category or a content item can be adjusted as well so that e.g. a category is not visible to users. The Management Suite has the right to deprive local users of the administration. Like in a file system specific rights for a category or content item can be assigned to security groups and users. An example: User Y can read and edit category Y but may not delete category Y.