SK8605Y1 - Connection of zero clients with the server for providing remote desktops via computer network - Google Patents

Abstract

The connection of zero clients (K) with the server (S) for providing remote desktops via computer network (7) consists of at least one zero client (K) having hardware (B) and software (A) connectable to the peripherals (P). The zero client (K) is connected via the network (7) with at least one server (S) having operation system (1) or maternal operation system (M) with hypervisor (H) and plurality of virtual operation systems (2).

Description

The solution involves engaging null clients with a server to provide remote desktops over a computer network, and sharing the computing power and server resources (or group of servers) between multiple remote desktops provided by the server, and transferring data between the server and null clients.

BACKGROUND OF THE INVENTION

Similar solutions are either predominantly hardware-based as 'thin clients', which on the client's side consist of simpler hardware than a conventional PC. Thin clients also include special software that performs some of the calculations on a connected server. However, thin client software (OS, drivers, applications) is more complex than zero client software.

In the simplest case, the server side is usually solved by connecting clients to a single physical server through a remote access service or through a dedicated operating system process, or on the server running virtualization software that provides each client with its own virtual operating system .

The second category of similar solutions is purely software. However, these software do not run on dedicated minimal hardware, but under conventional operating systems on a normal personal computer hardware. They also allow the screen and audio to be transmitted over a network from a remote computer (physical or virtual) and in the other direction they transmit peripheral input data, but they divide the computer's computing power with other applications.

In the case of software remote access, the server part is solved similarly as in the case of thin clients (as described).

The essence of the technical solution

A null client is a hardware device with software. A null client allows the user to work with the remote desktop of the server operating system, thereby virtually transmitting the remote server's performance over the computer network to the null client. The user perceives and uses the remote desktop via the zero client as if he were sitting behind a classic computer.

The number of servers involved in the whole system and the configuration of making the server operating system available to zero clients can vary, depending on the degree of redundancy (performance backup) and performance sharing required.

Hereinafter, a single term "remote operating system" (VOS) is used for different configurations, meaning the server-side operating system (or virtual operating system) that provides remote desktop service to one or more null clients. The term "remote desktop" refers to the null client connection service to the VOS for the virtual transfer of server performance and its resources to the null client. One remote operating system can provide remote desktop service to multiple users.

A null client connects to a conventional computer monitor with conventional speakers, and a null client connects common peripherals (e.g., a computer mouse, keyboard, and others). The only task of the zero client is to transfer the status of the peripherals connected to it to the VOS and to transfer the video and audio data (or data of other output peripherals) from the VOS in a suitably encoded form. Depending on the null client setting, this can be done in parallel over multiple networks or network connections, both for the fastest possible data transfer, as well as for network backup (to maximize network availability in the event of a single network provider) and security. The entire Zero Client hardware and software is designed so that Zero Client can handle only this single task, making it highly cost-effective and cost-effective.

Before transferring data from the null client, the data is encoded into l'onny, which allows for minimum transfer time and latency. After being transmitted to the VOS, the data in the "encoder-decoder" software module is decoded to the original l'onny and sub-VOS as if the peripherals were connected directly to the VOS. Zero client coding and decoding is handled by software running on the zero client: a simple operating system and programs running on it that provide the above zero client functions. The advantage over other existing solutions is just a very simple software package on the zero client, because this is the whole performance of the zero client dedicated only to encoding, decoding, exchange and display data.

In the remote operating system, the software module "encoder-decoder" is running, which similarly encodes the data in a suitable form before transferring data to the zero client.

The VOS can be configured to dynamically redirect the initial client connection to another

S K 8605

VOS, if the current VOS is overloaded. Also, in the event of a VOS availability failure, the null client automatically switches to another VOS if set (the VOS list it attempts to connect to in the event of a failure is stored by the null client in its fixed internal memory).

The system is ready to work with traditional security features such as anti-virus, virus threats, DOS / DDOS protection services, intrusion detection systems and the like. The entire computing and graphics performance is delivered by the server side, and the data is stored on the server side, which makes it possible to radically simplify zero-client hardware and software down to the simplicity of single-chip computers. Compared to conventional PCs, the advantage is backup and dynamic distribution of computing power and graphics performance, as tens to hundreds of zero clients are typically connected to a physical server (depending on the size of the organization using the system). Server power resources (CPU, GPU, RAM, disk space, or other resources) are automatically assigned to zero clients according to the current VOS program needs. There is no phenomenon common with a classical computer that the performance (or RAM, disk and other) of the purchased physical computer is not used.

Generally, the "hypervisor H" component, which, in conjunction with the "performance and backup management" software module, controls the allocation of the server resources, is generally any platform for operating system or resource virtualization, such as a native hypervisor, software hypervisor, or container-level virtualization system.

Dynamic allocation of performance (computational, graphical, possibly other performance) and dynamic allocation of server resources (CPU, GPU, RAM, or other server resources) is meant to allocate performance or server resources to a remote desktop, depending on their immediate or usual need.

The dynamic allocation of performance and the radical simplicity of zero client hardware makes it possible to significantly reduce the cost of computing. It also saves the environment, as only a fraction of the electronic waste is produced (mainly the server is renewed, zero clients have a life span of 10 years) and is saved by electricity. Advantages include remote management of zero clients over the network (installing a new firmware, changing zero client settings, and other tasks), as well as remote management of the VOS itself, as the technicians in the organization no longer have to move physically to the job in the vast majority of cases.

For the functionality of the entire system, it is necessary to have a stable, fast, fast network connection with low latency data transfer between zero clients and remote operating systems. If this condition is met, then the physical server, respectively. servers can also be located in the data center. The system for maximizing data rate and network availability can be configured to use multiple network connections and multiple networks in parallel, in terms of multiple physical networks, e.g. Wi-Fi and wired connection. In the event of a single network outage, zero clients and VOSs can continue to automatically communicate over the remaining networks without the need for system reconfiguration or human intervention.

The overall solution includes the central management software module on the VOS side, which can provide the administrator with the following functions:

• Display reduced views of remote desktops across the department - in real-time, the administrator can see everything users do across the group.

• Sharing the remote desktop image and sound of an administrator to selected users • Remote user support, i. j. take full control of the user's remote desktop.

• Send notifications to a selected group of users as a chat or with no feedback.

• Restore remote desktops to their default state (clean up the user's desktop with a single click).

• Centrally copying files and directories with a defined mask from the disk directories of all users in a given department to the default disk directory of the administrator (eg collection of elaborated assignments at the end of the written work).

• Set disk directory rights for the selected user group (directory visibility, read, write).

• Permissions and disabling of running specific programs or defined program masks (eg disabling all programs except the listed programs).

• Blocking intemet pages.

• Block selected peripherals P including keyboard and mouse.

• Add and remove zero client K from the department and change its settings.

• Viewing monitored data in real time or at a selected time interval: running programs, usage time, requested web pages, network connection statistics (protocol, port, direction, bit rate).

• Search in monitored data history: the administrator defines a group of one or selected

With K 8605 kritériíί criteria, where the criteria are either a time interval or refer to the data itself - searching by substring in the data, searching for a particular data by comparison with a specific value by operators is less than "," equals "," greater ".

Central management functions can be supplemented with new functions as needed. The central management functions can be used by the administrator at the same time to several zero clients, while the group of zero clients is defined by the administrator.

Wiring can be used wherever classic personal computers are used, even when deployed from one piece of zero client. The only condition is a high-quality and fast computer network. Remote desktop provides the same interface and features as a classic computer, so the user does not need to be trained. All commonly used programs of a given organization can be installed on the CI, so the system is widely applicable to different types of organizations.

The benefits of engagement will be maximized in organizations that use tens to thousands of computers, such as schools, universities, offices, banks, hospitals, but also in offices, shops and other private businesses. The more zero clients an organization uses, the greater operational cost savings, greater energy savings, higher levels of remote management and security, more space that would otherwise occupy large computers, less annual production of electronic waste and CO2, as well as longer IT life. The method of supervising the operation of remote desktops and the associated audit and communication functions available to the administrator are a great advantage in schools where frequent or continuous supervision of student performance is required, or frequent control of a particular remote desktop or blocking unwanted content.

In schools and universities, the "reset remote desktop" wiring feature is often used when the next class needs to start an hour, or electronic writing in a verified desirable remote desktop state (without the results of previous activities on that remote desktop, such as saved files). Similarly, a group of remote desktops can be quickly put into a state where specific programs and content that are directly related to the current subject or lesson are available on the remote desktop.

It is also possible to connect special peripherals necessary for teaching, such as microscopes, digital USB oscilloscopes, headphones and microphones and the like, required for special teaching programs (eg language learning, chemical laboratory, physical laboratory, etc.).

Engagement is the platform for “information technology as a leased service” solution: at the business center, the tenant, in addition to the office, also leases a set of zero clients with peripherals and server performance, and does not have to worry about any own hardware. If the tenant is interested or has a legal necessity, the system is also ready for the operation of the type “physical server in the company premises”, ie also on each floor of the business center.

In households, the zero client will find great application also in connection with server service solutions in data centers, from providing a remote desktop to the level of installation and maintenance of VOS applications, for example through the services of a telecommunications operator. Families would completely eliminate the hassle of managing the operating system, common applications, repairing and upgrading hardware, backing up data, securing hardware against theft, and software against viruses and malware. Operating a null client instead of a normal home computer will not only make it easier for a home user, but also a significantly cheaper alternative to owning hardware. The operator will also be able to determine the price for this service dynamically, depending on how much resources and performance on the server side the user actually consumes or orders. The operator will also be able to provide zero clients for rent, similar to settopboxes. Through the system's administrator software, the parent gets a platform for better monitoring of children's activity in real time as well as historical data on remote desktop usage. In cooperation with the operator will have a tool to secure the remote desktop from unwanted content

Zero client in connection with server service realized in datacenter will find application also in private sector, eg. in the form of "IT for rent", eventually also in state organizations using national data centers.

Involvement also offers added value for use in hospitals. The doctor can log in to any null client in the entire hospital and immediately see his open remote desktop with the data in progress in his programs, without the need for a long boot and opening applications. Login can be done by smart card, which makes it even more convenient and faster to log in. The doctor will have a unified approach to the patient's medical records and the conclusions of the examinations throughout the system. The patient can use zero clients at the ward where he / she is located to view the documentation of his / her person (planned examinations, findings, medication dosing, etc.).

Both the Zero Client and VOS are ready to work with a large group of peripherals that make it easier to use or increase security, such as a holographic keyboard and mouse, holographic display, projector, smart card reader, fingerprint reader. The holographic keyboard and holographic display can also be built in

S K 8605 Υ1 into the body of the zero client. When the Zero Client is turned on, the holographic display pops out and the holographic keyboard and mouse are displayed. In conjunction with a zero client battery and a zero client Wi-Fi connection, it will be a totally portable device for desktop computing with a remote operating system

The zero client can also be optionally equipped with a hardware module for connection to the telephone network, so it can be called as from a regular telephone. The same goes for the camera.

The zero client can also be made in a “tablet” or “mobile” version, where a touch screen in the desired size is used as the primary I / O peripheral. The zero client hardware, including the battery, is then stored in a common case with the display

For banks, engagement will offer total data security, as the zero client does not locally store any remote desktop data to which it provides access. Therefore, stealing a null client does not mean data leakage. Data flow between the null client and VOS is encrypted, the algorithm and configuration of the used cipher is adjustable. The connection is ready to connect zero clients to the data centers, and thus the bank has the possibility to choose a structure provider that meets the required level of physical and data security and reliability.

Involvement can be used in almost all multiple organizations. Sharing computational and graphical performance along with backing up data and network connections ensures system robustness and reliability. Centralized management and high security enable the system to be used for JT forrent purposes. Involvement will bring huge economic, environmental and user benefits to companies.

BRIEF DESCRIPTION OF THE DRAWINGS

In the picture no. 1 (which is an example of Embodiment No. 1), a block diagram is shown when there is a single physical server running one operating system and multiple null clients can log on to it via the network connection software module at a time.

In the picture no. 2 (which is an example of Embodiment 2), a block diagram is depicted when there are multiple physical servers the same as in the first case, with zero clients set to connect to a particular server and connect to another server only when their server is unavailable primary server.

In the picture no. 3 (which is an example of Embodiment No. 3) is a block diagram of a physical server running a single parent operating system and running a hypervisor under which multiple virtual operating systems are running. Multiple null clients can log on to each virtual operating system on a given physical server with and.

In the picture no. 4 (which is an example of Embodiment No. 4), a block diagram of L physical servers is shown, each of which is a third case situation, and in addition, the individual virtual operating systems from all physical servers are interconnected and provide each other user data backup service. In case of unavailability of the current virtual operating system, they enable switching of the zero client to another virtual operating system (performance backup), even on another physical server.

EXAMPLES

Example 1

Connection of zero clients K to a server S for providing remote desktops via a computer network 7 is characterized in that at least one zero client K comprising hardware B and software A connectable to peripherals P is connected via network 7 to one server S containing the server operating system (abbreviation) OS) 1, peripheral driver 3, network link module 4, encoder and decoder 5, monitoring 8, power and backup management 9, and central management 6. Upon power up, Zero client K reads software A from its permanent internal memory in hardware B and starts it. . Software A retrieves the configuration from the non-volatile internal memory in hardware B and the server operating system 1 address from it. The user enters their login data into the null client K login screen (or logs in using a P peripheral, eg smart card or fingerprint reader). After initiating a user login, the zero client K initiates a connection to operating system 1 and allows the user to work with a remote desktop Dynamic allocation of graphics performance, CPU, RAM, disk space, or other server resources, managed by multi-user desktops in OS 1.

After successfully logging on to OS 1, the video and audio state of the desktop will be transferred in real time from the operating system 1 to the zero client K via the network 7 (via multiple network connections if the K-client is configured). for example, a picture or sound are transmitted from the operating system 1 to the null client K. In the opposite direction from the null client K to the operating system 1, the data about the peripherals P connected to the null client K are transferred,

With the K 8605 Υ1 control system 1 through the peripheral driver 3 so that OS 1 handles them as if the peripherals were connected directly to it. The software of both parties (operating system 1 and zero client K) encodes and decodes the data in real time. OS 1 does this in the "encoder-decoder" module 5 and the null client K part of the data in module A and, if configured, part of the data in the hardware module B. The data is coded so that it can be exchanged in parallel over several network connections (or serially if software is configured) from network connection module 4 over network 7 and to minimize overall transmission and decoding time. The system encrypts all network communication, while the cipher algorithm and cipher configuration (eg key length) is adjustable. Server-side monitoring 8 monitors the overall network load 7 and provides load data to the encoder-decoder 5 on OS 1 and software A on the zero client K. Depending on the network load values, both OS 1 and the zero client K can use different compression techniques data and network communication control, thus ensuring fast data exchange between OS 1 and all zero clients K even under conditions of high network load 7.

Monitoring 8 monitors multiple user actions and values measured in their remote operating system 1: active and running programs, websites visited, CPU, GPU, RAM, network connection usage, remaining capacity of accessible disk directories, and more. Monitoring 8 provides this data to the central management module 6, from where it is made available to the network connection module 4 and from there through the network to the system administrators for debugging system performance and management. Operating system 1 provides a pre-configured set of directories on disks accessible from operating system 1 to a user from the zero client K.

The operating system 1 is able to send the zero client K over the network 7 an upgrade of any part of the zero client software (client operating system, applications, settings, etc.). This upgrade will be stored in non-volatile memory K in hardware B and will be used by the next management (which can be enforced by central management 6 over the network connection).

For configured system users who are assigned to the “department administrator” group (in school conditions, this is the teacher account for the class), the central management module interface 6 is available over the network.

Example 2

The connection of zero clients K to servers S for providing remote desktops via a computer network 7 is characterized in that at least one zero client K containing hardware B and peripheral P software A is connected via network 2 to at least one server S containing the server operating system ( abbreviation OS) 1, peripheral driver 3, network link module 4, encoder and decoder 5, monitoring 8, power and backup management 9, and central management 6.

After power-on, the client K reads software A from its non-volatile internal memory in hardware B and starts it. Software A retrieves the configuration from non-volatile internal memory in hardware B and from that list a list of the user's server operating systems. The user enters his or her login data in the null client K login screen (or logs in using a P peripheral, such as a smart card or a fingerprint reader). If the null client K has stored multiple operating system addresses 1 for a given user in the internal memory in hardware B, then the null client K shows the user their list, for example "1. Company A "," 2. Company B "," 3. At home". The user has a pre-selected first operating system 1 from the list and can change the option before logging on.

After the user initiates a login, the null client K initiates a connection to the selected operating system 1 and allows the user to work with the remote desktop If the selected operating system 1 is not available over the network, the null client K selects the backup address of selected OS 1 from internal memory in hardware B it will try to sign in. It repeats these attempts sequentially with all OS 1 that it has on the backup OS 1 address list until a connection is established. When it comes to the end of the backup OS 1 list, it starts using it again from the beginning. After sending the login data, the operating system software 1 through the network connection module 4 may assign a different client operating system 1 to the zero client K if it itself is too busy.

Dynamic allocation of graphics performance, CPU, RAM and disk space, or other server resources, among desktops of multiple users connected to OS 1 is controlled by the Performance and Backup Management 9 software running on OS 1.

After successfully logging on to OS 1, the video and audio state of the desktop will be transferred in real time from the operating system 1 to the zero client K via the network 7 (via multiple network connections if the K-client is configured). for example, image or sound, are transmitted from operating system 1 to null client K. In the opposite direction from null client K to operating system 1, data about peripherals P connected to null client K is transmitted, and this data is pushed to the operating system 1 via driver 3 peripherals so that OS 1 handles them as if the peripherals were connected directly to it. The software of both parties (operating system 1 and zero client K) encodes and decodes the data in real time. OS 1 does so in module "encoder-decoder" 5 and zero client K part of the data in module A,

The data is coded so that it can be exchanged in parallel over several network connections (or serially if the software is configured) from the network connection module 4 over the network 7 and that the total transmission and decoding time is kept to a minimum. The system encrypts all network communication, while the cipher algorithm and cipher configuration (eg key length) are adjustable. Server-side monitoring 8 monitors the overall network load 7 and provides load data to the encoder-decoder 5 on OS 1 and software A on the zero client K. Depending on the network load values, both OS 1 and the zero client K can use different compression techniques data and network communication regulation and thus ensure fast data exchange between OS 1 and all zero clients K even in conditions of high network load 7.

Monitoring 8 monitors multiple user actions and values measured in their remote operating system 1: active and running programs, websites visited, CPU, GPU, RAM, network connection usage, remaining capacity of accessible disk directories, and more. Monitoring 8 provides this data to the central management module 6, from where it is made available to the network connection module 4 and from there through the network to the system administrators for debugging system performance and management. Operating system 1 provides a pre-configured set of directories on disks accessible from operating system 1 to a user from the zero client K.

Data from operating system 1 (specific files listed in the system configuration and specific operating system settings 1) can be backed up to another configured operating system 1 during use. If the operating system 1 currently in use fails, the null client K searches for in the backup OS 1 list, another operating system 1, and then the performance and backup management module 9 of the newly merged operating system 1 restores the user data from the backup and the null client K continues to run on the new operating system 1.

The operating system 1 can send the zero client K over the network 7 an upgrade of any part of the zero client K software (client operating system, applications, settings, and others). This upgrade will be stored in the non-volatile memory in hardware B by the client K and will be used at the next restart (which the central management 6 can enforce through the network connection to the client K).

For configured system users who are assigned to the “department administrator” group (in school conditions, this is the teacher account for the class), the central management module interface 6 is available over the network.

Example 3

The connection of zero clients K to the server S for providing remote desktops via the computer network 7 is characterized in that at least one zero client K comprising hardware B and peripheral software P connected via network 7 is connected to one server S containing the parent operating system M s hypervisor H with multiple virtual operating systems 2 (abbreviated as VOS) 2, configurably comprising central management 6 and performance and backup management 9, each virtual operating system 2 on server S comprising a peripheral driver 3, a network connection module 4, an encoder and a decoder 5, monitoring 8, performance and backup management 9 and central management 6.

After power-on, the client K reads software A from its non-volatile internal memory in hardware B and starts it. Software A retrieves the configuration from the non-volatile internal memory in hardware B and from this list the server's virtual operating systems 2. The user enters his or her login credentials into the null client K login screen (or logs in via P, eg smart card or fingerprint reader). If the null client K has more virtual operating system addresses 2 stored for that user in the internal memory in hardware B, then the null client K shows the user their list, for example "1. Company A "," 2. Company B "," 3. At home". The user has a preselected first virtual operating system 2 from the list and can change the option before logging on.

After the user initiates a login, the zero client K initiates a connection to the selected virtual operating system 2 and allows the user to work with the remote desktop. If the selected virtual operating system 2 is not available over the network, the null client K selects the backup address of the selected VOS 2 from the internal memory in hardware B and attempts to log on there. It repeats these attempts sequentially with all VOS 2 that it has on the VOS 2 backup list until a connection is established. When it comes to the end of the VOS 2 backup list, it starts using the list again from the beginning. After sending the login data, the virtual operating system software 2 through the network connection module 4 may assign a different client virtual operating system2 to the zero client K if it is too busy itself.

The dynamic allocation of graphics performance, CPU, RAM, disk space, or other server resources is also controlled on the physical server side S by the hypervisor H in cooperation with the power management and backup management software 9 running in the parent operating system M, power allocation can be delegated to individual modules power management and backup 9 running in virtual operating systems 2. From the null client K perspective, hypervisor H is transparent - null client K connects to a specific VOS 2.

N E 8605 Υ1

After successfully logging in to VOS 2, the video and audio status of the desktop will be transmitted in real time from VOS 2 to null client K via network 7 (via multiple network connections if Kconfigured). Output data for P peripherals, such as the image or sound is transmitted from the virtual operating system 2 to the null client K. In the opposite direction from the null client K to the virtual operating system 2, data about the peripherals P connected to the null client K is transmitted, and this data is pushed to the virtual operating system 2 driver 3 of the peripherals so that VOS 2 handles them as if they were connected directly to it. The software of both sides (virtual operating system 2 and zero client K) encodes and decodes the data in real time. VOS 2 does so in the "encoder-decoder" module 5 and the null client K part of the data in module A and, if configured, part of the data also in module hardware B. The data is coded so that it can be exchanged in parallel over several network connections (or serially if software is configured) from network connection module 4 over network 7 and to minimize overall transmission and decoding time. The system encrypts all network communication, while the cipher algorithm and cipher configuration (eg key length) are adjustable.

Server-side monitoring 8 monitors the total network load 7 and provides load data to the encoder-decoder 5 on VOS 2 and software A on the null client K. Depending on the network load values, both VOS 2 and null client K can use different compression techniques data and network communication regulation and so ensure fast data exchange between virtual operating systems 2 and all zero clients K even under high network load conditions 7.

Monitoring 8 monitors multiple user actions and values measured in its virtual operating system 2: active and running programs, websites visited, CPU, GPU, RAM, network connection usage, remaining disk directory capacity, and more. Monitoring 8 provides this data to the central management module 6, from where it is made available to the network connection module 4 and from there through the network to the system administrators for debugging system performance and management.

Virtual operating system 2 provides a pre-configured set of directories on disks accessible from virtual operating system 2 to a user from the zero client. The disk array (or disk) in the server hardware S accessed by hypervisor H provides capacity to each virtual operating system 2 on server S dynamically.

Data from the virtual operating system 2 (specific files listed in the system configuration and specific virtual operating system 2 settings) the system may back up to another configured virtual operating system 2 during use. In the event that the currently used virtual operating system 2 fails, it is zero. client K searches the backup VOS 2 list for another backup virtual operating system 2, and then the performance and backup management module 9 of the newly merged virtual operating system 2 restores the user data from backup and the null client K continues to operate on the new VOS 2. backups 9 in conjunction with hypervisor H, depending on the configuration, can also make backups with storing the state of the entire virtual operating system 2, including the RAM state, and thus restore operation, including the status of running programs. Virtual operating system2 knows zero client Send over network 7 an upgrade of any part of the zero client software (client operating system, applications, settings and more). This upgrade will be stored in the non-volatile memory in hardware B by the client K and will be used at the next restart (which the central management 6 can enforce through the network connection to the client K).

For configured system users who are assigned to the “department administrator” group (in school conditions, this is the teacher account for the class), the central management module interface 6 is available over the network.

Example 4

Involving null clients K with servers S to provide remote desktops via computer network 7 is characterized in that at least one null client K containing hardware B and peripheral software P connected via network 7 is connected to at least one server S containing a parent operating system M s hypervisor H with multiple virtual operating systems (VOS) 2, configurable containing central management 6 and performance and backup management 9, each virtual operating system 2 on server S comprising a peripheral driver 3, a network connection module 4, an encoder and a decoder 5, monitoring 8, performance and advances management 9 and central management 6.

After power-on, the client K reads software A from its non-volatile internal memory in hardware B and starts it. Software A retrieves the configuration from the non-volatile internal memory in hardware B and from that list the user's virtual operating systems 2. The user enters his or her login data in the null client K login screen (or logs in using a P peripheral, such as a smart card or a fingerprint reader). If the null client K has more virtual operating system addresses 2 stored for that user in the internal memory in hardware B, then the null client K shows the user their list, for example "1. Company A "," 2. Company B "," 3. At home". The user has a preselected first virtual operating system 2 from the list and can change the option before logging on.

S K 8605

After the user initiates a login, the zero client K initiates a connection to the selected virtual operating system 2 and allows the user to work with the remote desktop If the selected virtual operating system 2 is not available over the network, the zero client K selects the backup VOS 2 backup address and try to sign in. It repeats these attempts sequentially with all VOS 2 that it has on the VOS 2 backup list until a connection is established. When it comes to the end of the VOS 2 backup list, it will start using it again from the beginning. After sending the login data, the virtual operating system software 2 through the network connection module 4 may assign a different client virtual operating system2 to the zero client K if it is too busy itself.

The dynamic allocation of graphics performance, CPU, RAM, disk space, or other server resources is also controlled on the physical server side S by the hypervisor H in cooperation with the power management and backup management software 9 running in the parent operating system M, power allocation can be delegated to individual modules power management and backup 9 running in virtual operating systems 2. From the null client K perspective, the hypervisor is transparent - the null client K connects to a specific VOS 2.

After successfully logging on to VOS 2, the network video (over multiple network connections if Zero Client K is so configured) will transmit real-time visual and audio status of the desktop from the Virtual Operating System 2 to Zero Client K. Output data for peripherals P, such as video or audio, is transmitted from the virtual operating system 2 to the null client K. The opposite direction from the null client K to the virtual operating system 2 transmits data about the peripherals P connected to the null client K, and this data is pushed the virtual operating system 2 via the peripheral driver 3 so that the VOS 2 processes them as if the peripherals were connected directly to it. The software of both sides (virtual operating system 2 and zero client K) encodes and decodes the data in real time. VOS 2 does this in the “encoder-decoder” module 5 and the null client K part of the data in module A and, if configured, part of the data also in module hardware B. The data is coded so that it can be exchanged in parallel over several network connections (or serially if software is configured) from the network connection module 4 over the network 7 and to keep the total transmission and decoding time as low as possible. The system encrypts all network communication, while the cipher algorithm and cipher configuration (eg key length) are adjustable.

Server-side monitoring 8 monitors the total network load 7 and provides load data to the encoder-decoder 5 on VOS 2 and software A on the null client K. Depending on the network load values, both VOS 2 and null client K can use different compression techniques data and network communication regulation, so ensure fast data exchange between virtual operating systems 2 and all zero clients K even under high network load conditions 7.

Monitoring 8 monitors multiple user actions and values measured in its virtual operating system 2: active and running programs, websites visited, CPU usage, GPU, RAM, network connection, remaining disk directory capacity, and more. Monitoring 8 provides this data to the central management module 6, from where it is made available to the network connection module 4 and from there through the network to the system administrators for debugging system performance and management. Virtual operating system 2 provides a pre-configured set of directories on disks accessible from virtual operating system 2 to a user from the zero client. The disk array (or disk) in the server hardware S accessed by hypervisor H provides capacity to each virtual operating system 2 on server S dynamically.

Data from the virtual operating system 2 (specific files listed in the system configuration and specific virtual operating system 2 settings), the system can back up while in use to another configured virtual operating system 2. If the currently used virtual operating system 2 fails, the null client K retrieves another backup virtual operating system 2 from the backup VOS list 2, and then the performance and backup management module 9 of the newly merged virtual operating system 2 restores the user data from backup and the null client K continues running on the new virtual operating system 2. Performance and backup management modules 9 in conjunction with hypervisor H, depending on configuration, can also make backups while storing the state of the entire virtual operating system 2, including the RAM state, and thus recovering operation, including running program states. Virtual Operating System 2 can send a zero client K over the network 7 to upgrade any part of the zero client software (client operating system, applications, settings, and others). This upgrade will be stored in the non-volatile memory K in hardware B and will be used at the next restart (which the central management 6 can enforce over the network connection to the zero client K).

For configured system users who are assigned to the “department administrator” group (in school conditions, this is the teacher account for the class), the central management module interface 6 is available over the network.

S K 8605 Υί

Industrial usability

Engagement is a unique, common solution, and as a whole it offers a unique way to use and manage computing power (including graphics performance). Although similar elements already exist, such a connection 5 to the shared use system is a unique solution. Also, there is a unique total transfer of computing and graphical performance to the server and immediate automatic switching of the zero client to another available remote operating system. available servers in a different data center, the client status is restored from backup and system operation continues. In the event of a single network outage, zero clients and the server side can continue to automatically communicate over the remaining networks, without the need to reconstruct the system or human intervention. There is no need for null client care by the user, since all data backups take place on the server side and also the maintenance of the entire wiring, including operating systems, can be provided by the system administrator.

Claims (1)

Connection of zero clients (K) to a server (S) for providing remote desktops via a computer network (7), characterized in that at least one zero client (K) comprising hardware (B) 5 and peripheral (P) software (A) ) is connected via a network (7) to at least one server (S) comprising either an operating system (1) or a parent operating system (M) with a hypervisor (H) with multiple virtual operating systems (2).