ITBO20120050A1 - MULTIMEDIA DYNAMIC AND INTERACTIVE INFORMATION SYSTEM - Google Patents

Description

DESCRIPTION

The present invention relates to a dynamic and interactive multimedia information system, comprising a central unit and a plurality of peripheral units.

In particular, the system can be used between a centralized command and control system and a plurality of remote bases in the field of conferences, theaters, sporting events, didactics and for cultural or recreational purposes.

Documents US20040008635, US2005015815, US20050206721, US20050289615, US7019723, US7046137, US5739869 describe multimedia systems that are negatively characterized by drawbacks that determine functional and structural limitations. The typical drawbacks of such systems are described in WO2008 / 149396, a document in which a system is described which provides an effective solution to these drawbacks. This document describes a multi-channel multimedia system equipped with remote units expressly dedicated to the purpose, with on-chip audio / video and graphics interfaces and accelerators, suitable for making the circuit extremely compact; the system described in WO2008 / 149396 has a high calculation capacity combined with low consumption with lower thermal dissipation, very useful in case of application in environments without the possibility of exchanging hot air to be disposed of, such as when the devices are installed inside armchairs; moreover, the absence of moving or noisy parts such as fans or hard-disks makes the application particularly suitable for environments with very specific acoustic requirements.

The invention which is the subject of the present patent application is part of the technical sector of the system described in WO2008 / 149396, providing, with respect to what is described in this document, a different solution to the drawbacks of the known art.

In particular, the system of the present invention provides the following advantages:

- the possibility of piloting and remote control of the peripheral units via Internet connection or other network with or without wires;

- the presence of a high definition (HD) video camera integrated with the remote units;

- a level of protocols dedicated to security and authentication;

- the presence of self-diagnostic and remote control procedures from the central unit; - the possibility of driving touch-controlled screens of any size;

- the ability to support bi-directional audio / video streaming (HD video).

- management of advanced graphic functions (3D graphics and video playback in HD formats). In other words, with the present invention, it is possible to realize interactive systems without geographical limitations and with an extreme flexibility of network configurations, such as to make them adaptable to a very wide range of applications.

Further advantages of the present invention derive from the possibility of distributing audio / video multimedia contents, of collecting information from peripheral units, of individual brightness control, switching on / off of peripheral units, of management of operating system updating of remote units.

Furthermore, with the solution object of this patent application, the following functions are allowed:

- remote peripheral management via proprietary protocol on an IP network;

- authentication and automatic identification by the central unit of the peripheral units;

- enabling and disabling of the application modules of the remote units, even independently between the different remote units;

- remote configuration and reconfiguration of remote units;

- enabling VoIP connections between the remote units and between the remote units and the central unit; - possibility of integration into the system of mobile devices (smartphones / tablets) connected via wireless with functions similar to those of remote units;

- distribution of audio / video multimedia contents of different formats and resolutions on the same network;

- collection of information from users of peripheral units, either through a magnetic media reader and / or a USB port, or through a camera with a somatic traits recognition program;

- dynamic management of the graphical interface for the user, in a differentiated way up to the single device, to make the distribution of contents flexible and change it in real time according to the different contexts in which the user finds himself;

- communication also extended to devices external to the network such as, for example, external servers, personal devices (smartphones / Tablets / Pda);

- remarkably high modularity for the remote units, with the possibility of dynamic management not only of the contents but also of the software functions of the remote unit, based on the context;

- bi-directional interactivity, with the possibility not only to receive data in â € œpushâ € mode from the central unit, also to request data directly in â € œpullâ € mode from outside (also via web);

- management of latest generation multimedia devices (webcams, 3G modems, gyroscopic sensors, magnetometers, etc., NFC systems);

- management of several interactive screens connected to a single client unit in the system, even of different sizes and manageable at the same time.

These and further advantages and characteristics of the present invention will be better understood by every person skilled in the art from the following description and with the help of the attached drawings, given as a practical example of the invention, but not to be considered in a limiting sense, in which :

- Fig.1 is a diagram relating to a possible example of the network architecture of a system built in accordance with the invention;

- Fig. 2 is a block diagram showing a possible structural and functional connection between central unit and peripheral units in a schematic way;

- Fig. 3 is a general diagram relating to a possible structure of the central unit of the system object of the invention;

- Figs. 4 and 5 show diagrams relating to possible examples of the distribution of contents in the system object of the invention;

- Fig. 6 is a diagram relating to a possible example of the structure of a main server, with the functions integrated within it and the connections with the other parts of the network;

- Fig. 7 is a diagram relating to the software architecture of the system.

For an easier understanding of the attached drawings, the schematic representation of some of the components illustrated can be combined with a numerical reference and / or with terms in Italian or English that specify the function of the component to which they are combined.

With reference to the attached drawings, in particular to the diagram of Fig. 1, a system made in accordance with the present invention is based on a network architecture with two hierarchical levels, in which a central unit (1), equipped with a relative main server (11) (Main Server) controls a cluster of subnets and remote devices. In the diagram of Fig.1 a cluster, identified with A, comprises a network of remote units (2â € ™) built, from the structural point of view, in accordance with the system described in WO2008 / 149396; in this way it is possible to extend the functionality of this system without geographical limitations, managing the entire cluster of subnets as a single network. At the same time, the introduction of remote units (2) including the intelligent devices object of the present invention allows to extend the field of application of this technology to many areas.

The remote units (2), in their generic basic structure, have some of the peculiar properties of the remote units described in WO2008 / 149396; in practice, these units (2) contain: - non-PC hardware architecture, for example based on latest generation dual core multimedia processors; - very low consumption: - possibility of being connected to other units in â € œdaisy chainâ € mode; - no noise generated thanks to the absence of moving parts (fans, etc.); - wired and wireless connectivity.

In addition to the aforementioned aspects which are present in the remote units described in WO2008 / 149396, the units (2) of the present invention are characterized by:

- possibility of piloting and remote control via Internet connection;

- integrated HD camera;

- layer of protocols for security and authentication;

- advanced self-diagnosis and remote control systems;

- possibility to control touch screens of any size;

- ability to support bi-directional audio / video streaming (HD video).

In addition, additional features are added such as:

- remote peripheral management via proprietary protocol on an IP network;

- authentication and automatic identification by the central unit of the peripheral units;

- enabling and disabling of the application modules of the remote units, even independently between the different remote units;

- remote configuration and reconfiguration of remote units;

- enabling VoIP connections between the remote units and between the remote units and the central unit; - possibility of integration into the system of mobile devices (smartphones / tablets) connected via wireless with functions similar to those of remote units;

- distribution of audio / video multimedia contents of different formats and resolutions on the same network;

- collection of information from users of peripheral units, either through a magnetic media reader and / or a USB port, or through a camera with a somatic traits recognition program;

- dynamic management of the graphical interface for the user, in a differentiated way up to the single device, to make the distribution of contents flexible and change it in real time according to the different contexts in which the user finds himself;

- communication also extended to devices external to the network such as, for example, external servers, personal devices (smartphones / Tablets / Pda);

- remarkably high modularity for the remote units, with the possibility of dynamic management not only of the contents but also of the software functions of the remote unit, based on the context;

- bi-directional interactivity, with the possibility not only to receive data in â € œpushâ € mode from the central unit, also to request data directly in â € œpullâ € mode from outside (also via web);

- management of latest generation multimedia devices (webcams, 3G modems, gyroscopic sensors, magnetometers, etc., NFC systems);

- management of several interactive screens connected to a single client unit in the system.

The main server (11) of the central unit (1) allows to manage, through the Internet, all the subsystems of the architecture of the system in question.

The services and applications that will be run on this machine allow complete remote management up to the last branch of the underlying networks, and, in particular, are able to:

a) Control and manage the Client Servers (25), sending them operational commands and all the contents to be redistributed on the networks of the peripheral units.

b) Receive and process the data arriving from the underlying networks, for example to provide reports and statistics on the use of the devices of the underlying networks.

c) Interact with third-party servers that will have to provide (based on the final application to be created) access to remote contents, databases, etc ...

d) Interact with multimedia servers both of the system manager and of third parties, in order to convey (or reprocess) multimedia contents to be distributed on the underlying networks, which may also include the technologies DESCRIBED IN referring to the patent WO2008 / 149396

e) To manage data exchange services via the internet through Web Services and similar technologies. The hardware of the remote units (2) is based on a microprocessor equipped with graphics and audio / video accelerators; as previously mentioned, the microprocessor can be of the latest generation dual core multimedia type.

Again with reference to Fig. 1, with (12) is marked a main switch that connects the main server (11) and the associated devices (if they are physically located in the same point) on the same network, which will then be interfaced to the web .

Between the central unit (1) and the connection network (3) that connects to the prefecture units (2) there is a router with a firewall (10) which constitutes the interface between the server systems of the central unit (1) and all the other devices on the network (3) that will communicate via the Web. Similarly, a local switch (21, 21â € ™) will be the intermediate connection device between the Client servers of the remote units (2) (or, in the case stand-alone system, between the network and peripheral units). All the devices of the local network will be connected to it, as well as the Wireless Access Points for connecting the Wireless devices.

The W.A.P. it is connected / integrated in the local switches of the remote unit network (2), to allow the connection of both wireless units (2) and tablets and smartphones equipped with a Wi-Fi interface.

The units (2) represent the final point of the system architecture chain. Their function is to provide multimedia content and interactivity to the end user, through the various applications in which they will be integrated.

The remote units (2â € ™), with wired connection, or remote units with a structure substantially equivalent to that of the remote units of WO2008 / 149396, are considered within the network of the present invention as a separate system, as already made according to well-defined specifications.

The integration of a system of the type described in WO2008 / 149396 will be aimed above all at the Server side, as it is intended to leave the Fw management part of the peripheral units referred to in WO2008 / 149396 unchanged and, therefore, allow their use in parallel with the system of the present invention.

The server (25) is able to communicate with the devices at a higher network level (Main Server (11), third-party Server) in order to be able to receive and send content and information.

The system object of the present invention is also open to consumer devices such as smartphones and tablets (schematically represented in the block marked by B in Fig. 1). These devices must be able to communicate freely with the remote units (2) regardless of the operating system they are equipped with (Android, iOS, WindowsPhone etc ...).

“Porting” and integration of applications by the system supplier for mobile devices for Android-type devices may be envisaged, in order to exploit the “open” architecture of these systems.

The system architecture allows all â € œsmartâ € devices to communicate with the remote units (2), and to exchange information with the system servers (whether they are Main (11) or Client (25) servers).

The third-party servers (25â € ™) can be freely integrated within the network (2), and must communicate with the Main Server, for the sharing of information and contents, or for the management of integrated processes.

The units (2) are equipped with means to reproduce and display contents and information that could potentially come from any point on the web. For this reason, in addition to what resides on the Main Server (11), other operators will also be able to send (and request) useful information on the network for their applications.

Applications running on third party servers will share data via standard network protocols (HTTP / HTTPS etc ...) and dedicated web services.

The above also applies to multimedia servers, dedicated to the processing and distribution of audio / video content. Similarly to the application servers, these devices are also able to communicate with the devices (2), guaranteeing the sending of streaming streams with the standard protocols currently in use (UDP, RTP, HHTP, etc ...). Encoders and / or streaming apparatuses, schematically represented in block C of Fig.1, can be connected directly to the Main Server (11), or they can send their data flow over the network as previously indicated for third party servers. These devices will be dedicated above all to the management of â € œLiveâ € events that will require the encoding of standard video signals in a digital streaming with very low latency.

The configuration of the system object of the invention is modular and scalable, according to the needs required in each different application. The versatility of the remote unit (2) guarantees the possibility of adapting the management method of the equipment network to each different market request.

In Fig.1, with block D, a stand-alone system is schematically represented. In this particular configuration, the system includes only one remote unit (2), connected on the web through the router-firewall (20), without the presence of an intermediate Client Server for local management. This solution is the basis of the system architecture and allows the creation of compact interactive and multimedia devices, which can be easily repositioned and at low costs.

The connection of the remote unit (2) to the router-firewall (20) can be made in two ways: Wired, through wired LAN ethernet, or Wireless, through WLAN (in this case a router is required -Wi-Fi Firewall). For the configuration shown in block D of Fig.1, the use of a local network switch is not envisaged, as the only unit present in the LAN has no associated other devices. In the case of a Wi-Fi network only, it is possible to associate external devices such as smartphones and Tablets with wireless connectivity.

In Fig.1, with block E, a structured Stand-Alone system is schematically represented, comprising a network of peripheral units (2) connected to the network (3) through the Switch-Router and Firewall Solution (20). In this second solution, similar to the basic stand-alone system, the use of several units (2) connected to a single routerfirewall (20) is envisaged (which in this solution must also provide functionality as a network switch for managing more wired units). As for the basic Standalone solution, also in this configuration the connection possibilities of the units (20) are Wired or Wireless.

In Fig. 1, blocks F and G are schematically represented two structured systems, including a Router with Firewall Solution for connection to the network (3), a local client server (25), and a Local Core Switch (21, 21â € ™) connected to the local network (30, 30â € ™); in the case of a wireless network (30â € ™) the switch (21â € ™) is connected to a W.A.P.

The structured system represents the most complete solution of the system network architecture. This system envisages the use of a Client Server (25), which distributes on the network of devices (2) connected to it (through a series of Core and Local switches) the contents and information arriving via the web from Main Server (11) and any other devices.

As for the other solutions, a router-firewall is used to guarantee the connection to the web (and its security), while for the distribution of the local network, core and local switches are used for wired networks, and wireless access points to allow connectivity. Wi-Fi of both devices (2) and other external devices (smartphones and tablets).

The sub-networks connected to the Client Server can be divided into several branches, and freely configured, allowing the coexistence of several devices.

As previously said, remote units (2â € ™) can also be connected to the Main Server (11), again with the use of a dedicated Client Server.

The structured system is also able to function autonomously even when it is not necessary to have an external Main Server with which to exchange data via the Web. The Client Server system (when configured in this way) can locally manage content and information to be send to the connected units, as well as guarantee a functional check on them.

All the units (2, 2â € ™) connected to the Client Servers (25) can be divided into functional groups, and recognized and identified also through this discriminant. This distinction is made to facilitate the recognition of the various devices which could also be located in physically different points from each other.

In Fig. 2 a peculiar characteristic of the system object of the present invention is represented in a schematic way. The remote units (2) are equipped with a hardware system and a resident software capable of constituting a plurality of functional modules, represented by the elements (22) in the drawing. The central unit (1) is equipped with means of remote management of the remote units (2) suitable for remotely configuring and reconfiguring the same remote units, or for enabling and disabling the modules (22) in each of said units. remote (2) independently from other remote units. In the drawing, the models (22) have been colored in different ways to represent the possible activation or deactivation of the modules themselves.

Furthermore, block (23) schematically indicates a device for recognizing the user, consisting, for example, of a camera equipped with a program for recognizing somatic traits. In this way, a device used also for other purposes in the remote unit is used (2). Alternatively, other suitable means of recognition may be provided.

The diagram of Fig. 3 shows a possible structure of the Main Server (11) of the central unit (1), which indicates the minimum functions to be integrated within it, as well as how the other parts of the network it can interact with. Figs. 4 and 5 represent diagrams relating to possible examples of the distribution of contents in the system object of the invention, while Fig. 6 is a diagram relating to a possible example of the structure of a main server, with the functions integrated within it and connections with other parts of the network.

The Main server (1) can be managed by a â € œnâ € number of users, who may not even be physically located in the same place where the server resides. It is therefore necessary for the management of the Main Server and all its functions to be guaranteed the possibility of accessing both directly and from the web via client PCs connected to the server itself.

Access is made through a web-based interface, which allows you to control and manage all the functions of the various services / applications. All accesses to the Main Server (1) are controlled and managed on the basis of the privileges assigned to the various users.

Data exchange with External Servers is carried out through the implementation of Web Services dedicated to data exchange.

These components will be developed and / or modified according to the specific needs of the application. All external data exchange mechanisms that will exploit web services have a high degree of security, therefore all the necessary security policies must be defined by the developers.

In order to guarantee data exchange with most external devices, the Main Server (1) is able to exchange data through the FTP protocol. This type of data exchange must take place only if a data exchange through the use of web services is not applicable. In case FTP is not considered secure enough as a protocol for data exchange, it is possible to switch to the use of a Secure FTP protocol (SFTP or similar).

The Main Server (1) manages and configures the entire network of remote units (2) to which it is connected, and specifically:

A) for Client Servers (25):

- Control all Client Servers (25) connected to the network of remote units (2), monitoring their status and allowing remote management (even with remote desktop solutions). This control is carried out through a graphical interface that allows a quick consultation of the network status (GUI with interactive topographic diagram).

Through this interface it is possible:

- Check the status (Active / Inactive) of the Client Server

- Check the status of the network connection (bandwidth consumed by the Server â € œxâ €) - Manage the Boot / Reboot / Shutdown of the Client Server (Wake on Lan?)

- Access the Client Server root directory

- Run applications and troubleshooting via remote desktop sw

- View and check the status of the sub-networks connected to the Client Server (displayed via macro-blocks)

- Send local multimedia contents to Client Servers or from applications on external servers, via the web (web services / ftp etc ...), organized according to a logical hierarchy established in two different ways: from external server or internal scheduler.

- Monitor in real time the content distribution activities on the Client Server, and in particular:

- the status of the audio / video / text channels available for content distribution (Active / Inactive);

- the type of active streaming (Local / from Web) and data flow parameters:

- protocol used (UDP / RTP etc ...)

- type of data distribution (Unicast / Multicast etc ...)

- video stream data (Codec / Profile / BitRate / Resolution)

- audio stream data (Codec / BitRate)

- Request data and reports from the Client Server regarding the use of the (2) / Wireless devices used in the sub-networks

- Allow updates of the control / management applications installed locally on the Client Server

B) for units (2) / Wireless Devices / Stand Alone Networks:

- Control and monitor all (2) / Wireless devices connected to the Client Server (25) sub-networks. The Main server must be able to identify and monitor up to the single unit connected to the network.

Specifically, the Main Server will have to:

- Check the power status of the unit (2) / Wireless (Active / Not Active), and change it remotely.

- Check the activity status of the unit (2) / Wireless (In use / Waiting for user / Standby) and modify the conditions remotely - the conditions may vary according to the application in use

- Show and configure the network parameters of the unit (IP, sub mask etc ....)

- Show and configure the parameters relating to the Fw / Sw installed on the single unit (2) / Wireless

- Allow the update (at any time) of the Sw / fw of the unit (2) / Wireless

- Show the content currently displayed on the unit (2) / Wireless (Streaming, image, text, etc. with related transmission parameters).

- Receive and manage all the data relating to the actions performed by the end user and transmit the related feedback in real time:

- Choice of multimedia contents (audio / video / text)

- Multimedia channel selection (where present)

- Polling / Voting (where present)

- Text Input / Output

- Purchase / merchandising operations

- User identification operations

- Operations related to identification

- Any actions dedicated to particular Hw devices connected to the device (barcode readers, smart cards, USB key ids, NFC readers, etc.)

- As for the Client Servers, also the single units (2) must be monitored through a graphic interface that shows the main operating parameters of the devices. The visualization must be done both in a general way for â € œgroupsâ € of units, and for single units (foresee expanding menus).

For the management of wireless systems, the three different conditions that the Main Server manages are:

a) Units (2) connected to the Client Server / Stand Alone via Wi-Fi

b) External devices (Tablets / Smartphones) connected to the Client Server / Stand Alone System via Wi-Fi on which the system's â € œcloneâ € application is running (2)

c) External devices (Tablets / Smartphones) connected to the Client Server / Stand Alone System via Wi-Fi on which the RM application is not installed, but with which you want to interact (e.g. via browser / instant messagingâ €)

In the first two cases, the management of the units (2) / other devices is to be carried out in the same way and as previously described.

If instead you want to interact on consumer devices without installing dedicated applications, the Main Server (11) interacts with the device:

- By integrating the device into the Wireless network (2) (then manage DHCP addressing etc ...), after passing the authentication process.

- Exchanging multimedia contents via browser / universal instant messaging systems

- Offering the ability to download applications for mobile devices for greater interactivity

In the database of the server (25) all the data relating to the network of the units (2) are stored. At an indicative level, these are the data divided into macro-categories: System Data; Main Server user accounts data; Unit network configuration data (2) (Associated devices, sub-network configuration etc ...); Local storage data contained; Main Server applications and services configuration data.

A Db or a series of Db is used to manage the system data, which allow a dynamic and simple use of the data in use, without resorting to components that make the management of data within the applications cumbersome and difficult. The access to data by both applications and users takes place quickly to avoid creating impediments in the use of the system (extremely long loading, waiting in carrying out routine sw operations, etc ...). All the data of the various applications are always configurable within the applications themselves (via the GUI interface that will act on the configuration files that can be edited), and above all the portability of the data between different applications and also between different servers must be guaranteed.

The Main Server (11) can query all the Client Servers (25) and the units (2) / Wireless connected to it (in Standalone networks for example), requesting data and reports on the use of the device and the related applications running .

These data will then be collected by the Client Servers (25) for structured systems, while â € œcapturedâ € directly by the Main Server (1) in the case of Stand alone networks.

Any particular application that will run on the (2) / Wireless devices must be configured to transmit generic or specific data.

The generic data can refer to: basic operation of the remote unit (2), number of ignition cycles, average time of use of the device by the user; number of uses of the Hw devices connected to the unit (eg: CC reader, etc.), etc.

Data of a specific type can be related to: operation of a specific application; most requested multimedia content; average income of each device (if connected to sales / merchandising functions); use of customer loyalty programs through personal cards / keys; etc...

All the data required by the Main Server (11) can be configured by the Server user (via GUI where he can compose the report autonomously using configurable templates) and can be managed with output files in common formats (pdf, xlsx, docx, csv , etc...).

To allow the organization of the contents directly through the Main Server, a special application must be created to schedule the various multimedia files to be sent over the network (2).

The scheduling SW must be organized according to a precise hierarchical order, which allows (also based on specific applications) to divide the contents according to the needs of the users.

In particular (see Fig. 5) the organization will be divided into:

a) Zones: logical groups of Remote (2) / Wireless units (associated or not with a Client Server), organized according to their purpose of use / location. One or more schedules (on each of the available channels) can be assigned to each zone.

b) Channels: channels dedicated to broadcasting audio / video / text information; they may differ in number depending on the applications used on the (2) / wireless units.

c) Schedules: groups of two or more playlists linked together and organized according to a precise timeline

d) Playlists: list of content files to be distributed and played on network devices (2) e) Content files: Audio / Video files; Image files; Text File

The scheduler must have a graphical interface, which allows the Main Server user to control and edit all the components of the content sorting hierarchy.

At the entrance to the program there will be all the contents coming from the different internal / external sources, which can be organized in two ways:

- With internal scheduling / by Main Server user: all decisions regarding the organization of the contents are made by the user who accesses the scheduler directly from a client PC (with the relative account).

- With external scheduling / from External Server: the organization of the contents is always done by the schduler, which however manages the input of a scheduling file coming from a device external to the Main Server, which will provide the priorities for the transmission of the contents. Method and format of the external scheduling are to be defined from time to time according to the different applications that will be integrated into the system (2).

For all encoding and video streaming needs that cannot be achieved through devices external to the Main Server, it is necessary to use a software encoder.

This software will work using the files contained in the Main Server Storage as a basis for content, and will allow the encoding and retransmission of audio and video streams over the network (2).

The A / V output flows from the program must be compatible with those foreseen in use on the (2) / Wireless devices. These flows will be managed subsequently by the scheduler which will control their diffusion to the interested network nodes.

The Main Server (11) is equipped with storage media containing all the multimedia contents used by the remote unit systems (2), including the temporary processing data of the files themselves (e.g. encoding / conversion processes, etc.) .

This area will be accessible to the users of the Main Server (those with the appropriate privileges), to ensure "top" control of the data flow.

The data exchange protocols between the Main Server and all the other network components are defined in the related applications. As a general guideline, standard network protocols are used, reliable and currently used in digital content distribution systems The diagram of Fig. 6 shows a possible structure of the Client Server (25), where the minimum functions to be integrated to the inside it, as well as the other parts of the network with which it will have to interact.

For the Client Server the access of the users will be direct, therefore limited to the operators who will be physically present in the place where the machine is positioned.

Access will be password protected and the user who accesses the machine will only have the possibility to manage and configure the applications for the functioning of the unit network (2); all aspects of system administration and management will be managed remotely both through the Main Server (11) and through remote desktop applications.

The data exchange with the Main Server (11) follows the same logic seen for the communication between the Main Server and the external devices (Server, Encoders etc ...).

The use of Web Service will therefore be envisaged for the exchange of information and contents, and an eventual FTP data exchange to guarantee compatibility with all systems connected to the local network (2).

The unit management activity (2) will follow the basic lines of what has already been seen for the Main server, but in a more â € œlocalâ € way. The user will have the possibility to manage a command interface via web based application, which will act not through the web network, but through the local LAN (s) of the equipment (2).

The functions to be implemented in the software partly reflect what has already been seen for the Main Server. Similar operation is provided for the graphic interface created for the web based application, which will have to display in an organized (and hierarchical) way all the components of the unit network (2) connected to the Client Server (25), and allow the management of graphic layouts for the arrangement of the units.

The contents can be received either from the outside (via the web connection with the Main Server or other external devices such as Streaming Servers or Encoders) or locally (upload of contents directly to the Client Server (via storage media, network download etc.). ..).

In both cases, all contents (which do not require immediate transmission such as Live Streaming) are stored locally in dedicated folders and accessible only to the main Client Server user (or to the Main Server users who will access - with their privileged accounts - remotely to the machine).

Any storage space can be dedicated to the â € œbufferizationâ € of â € œLiveâ € content arriving from local / Web, in order to make network traffic management more fluid.

The Client Server (25) sends the contents received from the outside / local on the last stretch of the network (30) to the remote units (2).

The management of this data is carried out through an application component (indicatively called â € œScheduling Interpreterâ €) which manages two distinct mechanisms for transmitting information, based on the concept of the application running on the remote unit and the type of approach to be proposed to the end user.

The applications will then have to manage the contents in the following way:

- Push: the Client Server (25) autonomously sends (or upon instruction of the Main Server 11) the data to be displayed to the remote unit, which displays them in the order established in the relative scheduling.

- Pull: the Client Server (25) receives a request from the remote (2) / wireless unit and displays the content chosen by the user, who will have direct control over the available content.

The interpreter who is in charge of this management must therefore:

- sort the received files, streams and files present locally on the Client Server (25), interpreting the external / local schedules received, and catalog them (via tag / metadata) so as to be always available (indexed) for transmission to the devices remote (2);

- start data sending â € œsessionsâ € in push mode, and check that the remote units are actually receiving and displaying the data set by the Client;

- manage the requests of the (2) / wireless units and take immediate action to send the content or information requested by the device.

All the interactive functions that are integrated in the different applications of the remote units (2) must communicate bi-directionally with the Client Server (25) (firstly) and with the Main server (11) (secondly).

The management application will have to receive all the requests of the remote units, process them in real time regardless of their number and provide immediate feedback based on the type of need of each of the units. In addition to the feedback output on the remote unit, the Client Server user must also have a visual feedback of all the activities carried out on the unit (commands sent, received, network diagnostics, etc ...).

The features to be managed will be described later in the description.

The Client Server application will have to take care of collecting data and statistics on the use of the contents, in both ways of managing the contents (push / pull), storing them in the Local DB, in order to be managed for the generation of report both on the Client Server and remotely via the Main Server.

Some characteristics of the system object of the invention and possible uses of the same will be described below.

The remote unit supports connection to dedicated monitors, sized from 4.3 to 60 ", through a dedicated IF card.

As previously said, the remote unit (2) can have an interface with 1080p camera / webcam in video and audio acquisition, as well as a microphone and line audio input. More than one remote unit can be enabled to send the audio channel.

The connection of the remote unit can include ethernet network, Daisy Chain type network, wireless connection.

Experimental tests have highlighted the possibility of managing a considerably high number of remote units, of the order of a few thousand.

The remote units can be equipped with a â € œpass-throughâ € wiring on an external board: two power connectors that can be used indifferently as input or output without the need for HW or SW configuration.

Each remote unit (2) will be conveniently equipped with fuses and / or internal protections against overcurrents, overvoltages and inversions on the power input. Furthermore, a possible power-fail of a single remote unit must not cause the interruption of the power distribution to the other units in the chain, in the case of using a unit with a â € œPS Boardâ €.

The brightness of the remote unit display (2) must be adjustable from the central unit (1) with adjustment segmentation on a 0-100% basis (0% = screen off - brightness reset / 100% = maximum brightness ). The display can be turned off from the remote unit; in such conditions it must not emit any â € œflareâ €.

The Ethernet ports (SB / Ethernet Board) have autocrossover functionality (“straight” or “crossed” cables can be used to connect to these ports); also duplex mode and speed (10/100/1000) auto-negotiation must be provided.

It is important to underline that the noise level of the remote units (2) is equal to 0dB. In practice, the unit must not emit any hum, rustle, under all operating conditions

If the connection is with a wired network, the wired network communication will be based on the TCP / IP protocol. The data exchange protocols for wireless applications must reflect what is used in the wired architecture, in order to maintain good uniformity in the case of mixed systems (wired / wireless).

The application layer protocols are HTTP and FTP. The HTTP protocol will allow the transfer of documents in HTML format

The remote unit (2) must be able to receive A / V streams from the network, through the UDP and RTP protocols. The A / V streams will be sent as MPEG2-TS. The remote unit (2) must support decoding of the H.264 standard

With regard to system performance, the boot time must be limited, and in any case it must be less than 30 seconds overall, including the loading of the OS operating system and all the various components of the applications that must be run on the device.

In the case of audio latency, differentiations can be foreseen according to the applications. For example:

- Content streaming (â € œdelayedâ €): acceptable latency <1 sec

- Content streaming (â € œLiveâ €): acceptable latency <0.4 msec

- Conference-like system management: acceptable latency <= 10 msec

Even in the case of video latency, differentiations may be envisaged according to the applications. For example:

- Content streaming (â € œdelayedâ €): acceptable latency <1 sec

- Content streaming (â € œLiveâ €): acceptable latency <0.4 msec

The content download speed will be related to the type of download management; for example, for direct download from Usb the speed will be the standard USB 2.0, while for download via Wi-Fi / Bluetooth to an external device the speed will be based on the type of wireless network implemented.

Listed below are some of the possible applications (with related functionality) for the remote unit (2). All possible applications can be implemented as needed.

An application is of the â € œShelf â € œIntelligentâ € or â € œRetailâ € type. The purpose of this application is to display information and content on multimedia players in a retail environment, recognize the consumer and provide interactive services (via touchscreen interface and any other devices to be associated with the remote unit 2), and collect a series of data on the use of the device itself.

In this type of application, the remote unit can include the following group of HW devices:

- a card with wired / wireless network connectivity in fixed installation, for example on a shelf or display;

- an LED screen (with dimensions between 4 and 12â €);

- â € œtouchscreenâ € type input device;

- card reader (Barcode / Magnetic Stripe);

- possible connection to a second display.

As an alternative to the above, the remote unit can include the following second group of HW devices:

- card with wired / wireless network connectivity in mobile installation with mechanics that can be integrated into a mobile element (for example a trolley), with battery power; - Webcam association for customer assistance / dialogue with operators / monitoring of the sales area;

- association of â € œintelligentâ € measurement devices for acquiring data on consumers / products;

- association of devices for purchase (POS / CC Readers - Chipcard / NFC).

Regarding the Sw functionality, it is possible to:

- data reception (audio / video / text) in Push mode from Client Server / Main Server, and visualization of the same through a dynamically manageable graphic interface (through visualization templates managed by server users).

- user identification via magnetic card, and display of dedicated content;

- the collection and sending of statistical data to the Client / Main server;

- the control of a second screen on which to display additional contents always received from the Client / Main Server;

- the management of interactive functions requested by the user, such as: choice between channels with different contents; possibility of voting / polling; call for assistance / booking services (â € œCallâ € functions); purchase / booking of special services; creation of a local WLAN for sending specific contents to mobile devices (smartphones and tablets); interaction with other devices of the same network / area of use; Voip functionality management (bidirectional) when a suitable device (webcam / microphone) is associated; internet browser management (with the possibility of restrictions in use) and integration of the plugins necessary for the use of third-party applications (flash, html5, java, quick time etc ...)

Another type of application is that of Remote Assistance or Helpdesk, with the creation of interactive kiosks (stand-alone or associated with existing devices) to allow users to interact in real time with an operator (voip video call) for assistance on emergency call services and products / devices.

In this type of application, the remote unit can include the following group of HW devices:

- card (with wired / wireless network connectivity) in fixed installation on the shelf / display;

- LED screen (sizes between 4 and 12â €);

- â € œtouchscreenâ € type input device;

- webcam with microphone;

- external hw buttons for managing special functions (emergency calls etc ...).

In this application, the hardware can include integration with user recognition device.

Regarding the Sw functionality, it is possible to:

- data reception (audio / video / text) in Push mode from Client Server / Main Server, and visualization of the same through a dynamically manageable graphic interface (through visualization templates managed by server users);

- Voip functionality management for video calls from the M26 terminal (management via touchscreen GUI);

- the possibility of exchanging information in real time with the operator of the remote assistance center (viewing pdf documents sent by the operator on the M26 terminal etc ...); - the possibility to download contents on the user's personal device (USB key etc ...); - the collection and sending of statistical data to the Client / Main server.

Another type of application is that of â € œInteractive Digital Signageâ €. The application aims to create stations for viewing digital signage content on large screens, with interactivity and services for the end user.

In this type of application, the remote unit can include the following group of HW devices:

- card (with wired / wireless network connectivity) in fixed installation on the shelf / display;

- LED screen (sizes between 30 and 40â €);

- â € œtouchscreenâ € type input device, with USB interface.

In this application, moreover, the hardware can include the association to a webcam; the association with â € œintelligentâ € measuring devices for acquiring data on consumers / products; the association of devices for user recognition; the association of devices for purchase (POS / CC Readers - Chipcard / NFC).

Regarding the Sw functionality, it is possible to:

- data reception (audio / video / text) in Push mode from Client Server / Main Server, and visualization of the same through a dynamically manageable graphic interface (through visualization templates managed by server users);

- the possibility to download contents on the user's personal device (USB key etc ...); - the collection and sending of statistical data to the Client / Main server;

- the management of interactive functions requested by the user, such as: choice between channels with different contents; possibility of voting / polling; assistance calls / service booking (â € œCallâ € functions); purchase / booking of special services;

. the management of internet browsers (with the possibility of restrictions in use) and integration of the plugins necessary for the use of third-party applications (flash, html5, java, quick time etc ...).

Another type of application is that of proximity / recognition systems. The purpose of the application is to create information points, for example â € œintelligent kiosksâ € that allow users to be recognized through dedicated devices, and that provide services also through autonomous applications running on remote devices.

In this type of application, the remote unit can include the following group of HW devices:

- card (with wired / wireless network connectivity) in fixed installation on the shelf / display;

- LED screen (sizes between 4 and 12â €);

- capacitive â € œtouchscreenâ € input device, with USB interface;

- measuring / recognition devices / proximity sensors;

- â € œStand-aloneâ € kiosk structure.

Regarding the Sw functionality, it is possible to:

- data reception (audio / video / text) in Push mode from Client Server / Main Server, and display of the same through a dynamically manageable graphic interface (through visualization templates managed by server users):

- user / product identification through dedicated devices;

- the management of applications running locally on the application to manage interactive functions (for example: if a hw device recognizes the sex / age / weight of the person, a dedicated application records the data and processing them provides feedback with results of this processing - as a BMI calculation etc ...);

- the collection and sending of statistical data to the Client / Main server;

- the management of internet browsers (with the possibility of restrictions in use) and integration of the plugins necessary for the use of third-party applications (flash, html5, java, quick time etc ...).

Other applications consist of an improvement in the functionality of the system described in WO2008 / 149396 for large scale applications in public environments such as theaters / stadiums / conference rooms.

In this type of application, the remote unit can include the following group of HW devices:

- card (with wired / wireless network connectivity) in fixed installation on the shelf / display;

- LED screen (sizes between 4 and 12â €);

- capacitive â € œtouchscreenâ € input device, with USB interface;

- association of devices for purchase (POS / CC Readers - Chipcard / NFC);

- association of person recognition devices (USB interface / smart card / barcode reader).

The application can also be equipped with the following hw devices:

- interfacing with existing external â € œConferenceâ € systems;

- loudspeaker for external audio management;

- courtesy light integration.

Regarding the Sw functionality, it is possible to:

- data reception (audio / video / text) in Push mode from Client Server / Main Server, and visualization of the same through a dynamically manageable graphic interface (through visualization templates managed by server users). Contents dedicated to the LIVE environment, therefore low latency both audio and video;

- the management of interactive functions requested by the user, such as: choice between channels with different contents; possibility of voting / polling; assistance calls / service booking (â € œCallâ € functions); purchase / booking of special services;

. user identification;

- dynamic management of audio via IP network;

- the collection and sending of statistical data to the Client / Main server;

- integration with third-party systems for special applications (ticket offices, catering management, emergency systems, etc ...);

- integration with third-party systems for conferences;

- the possibility of downloading contents on the user's personal device (USB key etc ...);

- Internet browser management (with the possibility of restrictions in use) and integration of the plugins necessary for the use of third-party applications (flash, html5, java, quick time etc ...).

Another application concerns the use of the system as â € œConference / Hybrid Systemâ €. In this application, very low latency (<10 msec) bidirectional audio data exchange systems are created with the association of video and additional services (through the basic functions of the system via IP.

In this type of application, the remote unit can include the following group of HW devices:

- card (with wired / wireless network connectivity) in fixed installation on the shelf / display;

- LED screen (sizes between 4 and 12â €);

- capacitive â € œtouchscreenâ € input device, with USB interface;

- interface for TDN bus management;

- microphone management (with relative signaling LEDs provided on the stem);

- management of external Hw buttons for signaling / requests (call etc ...).

Regarding the Sw functionality, it is possible to:

- data reception (audio / video / text) in Push mode from Client Server / Main Server, and visualization of the same through a dynamically manageable graphic interface (through visualization templates managed by server users). Contents dedicated to the LIVE environment, therefore low latency both audio and video;

- conference-like management with calls and low latency audio sending / receiving (<10 msec) via TDN bus, to be carried out bidirectionally, and superimposed on the audio content arriving from the IP system;

- microphone management and related accessories;

- the management of external hardware buttons for the audio call functions described above.

Another application is related to the â € œDesktop On-the-goâ €. In this type of application, pc-like workstations are created through remote units (2), which users can access via a personal device (smart card / USB key) and load a live OS that allows to replicate an environment desktop with all the user's personal data. The data will be encrypted and the personal device must be able to be removed at any time without consequences both for the system object of the invention and for the device itself.

In this type of application, the remote unit can include the following group of HW devices:

- card (with wired / wireless network connectivity) in fixed installation on the shelf / display;

- LED screen (sizes between 4 and 12â €);

- â € œtouchscreenâ € type input device, with USB interface;

- device with OS image (Usb key / Smart Card with USB interface);

- any HW devices (keyboard / mouse / external storage);

- connection of wireless / bluetooth devices (smartphones / tablets).

Regarding the Sw functionality, it is possible to:

- data reception (audio / video / text) in Push mode from Client Server / Main Server, and display of the same through a dynamically manageable graphic interface, only for the â € œStandbyâ € mode of the device;

- recognition of the user's personal device and personal OS loading (by reboot of the machine);

- â € œsafeâ € management of the external device and its removal from the remote unit (2); - interfacing with any control devices (keyboard / mouse);

- interfacing with any wireless / bluetooth devices such as smartphones / tablets for uploading / downloading content;

- ethernet / wireless network management to allow the personal OS to access the internet (with all relevant controls and restrictions).

In conclusion, it is possible to state that the system object of the present invention consists of the following main hardware / software elements:

- Main server (11) also known as (MS) with management software;

- Client server (25) also known as (CS) with management software;

- Remote unit (2) also known as (UR).

The software present on the MS will allow the management of the entire system and the supply of contents for the CS or directly for the URs.

The Client Server CS will generally be located at the customer's premises (store, theater or other) and will allow, through a specific management software, the administration of the individual URs or groups of URs (for example all the terminals present in a given department of the store). The management software will allow both the assignment to the UR of contents received from the CS and the direct insertion of original contents.

The Remote Unit (2) will be the interface with the end user and will allow the visualization of the contents and the interaction with them (customer recognition, possibility to make choices, surveys or other), through the â € œtouch screenâ € monitor. €, camera and any other peripherals connected to the UR device.

The remote unit (2) or (UR) will be equipped with software conceptually based on a three-layer (3-layer) architecture. The three identified layers are as follows:

- Application Base;

- Common Application Interface;

- Specialized App Module.

The design analysis that led to this type of architecture focused above all on two key points:

- the heterogeneity of the applications to be implemented on the platform of this system. The applications that can be used range from â € œsimpleâ € Digital Signage to potentially very complex interactive applications. For this reason, the approach to the system is as â € œmodularâ € as possible. The heterogeneity of applications also implies a certain heterogeneity and â € œpredictabilityâ € of external devices and peripherals that can be used.

The block diagram of the SW architecture is shown in Fig. 7.

The lower layer or Layer 1 (in Fig. 7 called Application Base) will be entrusted with communication functions between the application and the operating system, the implementation of the communication protocol between the UR and the CS and between the UR and the MS and the startup, shutdown and control operations of the individual Specialized App Modules present in layer 3 (Layer 3 in Fig. 7). Specifically, this system will communicate to the CS the information necessary for monitoring the UR, such as the state of the hardware, the presence of any peripherals, the active / running module.

To meet the needs dictated by the heterogeneity of the required functions and the unpredictability of the specifications of future applications, specific modules have been developed (Specialized App Module, see Layer 3 of Fig. 7) which will implement the individual functions required (Streaming video, VOIP , survey, Mod. 23, Digital signage and others). These modules will be independent from each other and will be controlled by means of the functionalities made available by the â € ™ Application Baseâ € and by the control protocol, described further on.

The specific peculiarities of each single module may require connections via network to external services (web services, remote servers, SIP gateway, HTTP requests, video streaming, etc.) or to services made available by the CS. These needs will be met by specific software implementations included in each single module.

To facilitate the implementation of future applications and standardize the approach to programming new specialized modules, each Specialized App Module will implement a common abstract interface (Common Application Interface - Layer 2 in Fig. 1), the methods of which are indicated in a later section.

This will allow the individual modules to communicate with the lower Application Base level (and consequently with the operating system and the CS) through a common protocol.

Starting from the general architecture of the Framework, the implementation of the individual Specialized App Modules and, more generally, the creation of the Common Application Interface will take place through the creation of a Class called BaseActivity which extends the Activity Class. Methods with basic functionality (essentially â € œreturn trueâ €) will be defined in this Class.

The implementation of each single Specialized App Module will take place through the extension of the BaseActivity Class and the redefinition of the aforementioned methods for the specialization of the module's functionality.

A license file is required on each UR containing the limitations and operating specifications of the software, specifications which are different depending on the customer to whom the software is released.

The file contains the following information:

- list of modules purchased and therefore usable. For each module, it is a question of inserting a key that uniquely identifies the module (it can be the path of the module class in the package);

- verification checksum of the configuration file, which can be an md5 of the entire configuration file.

The contents of the license file are obfuscated so that they cannot be read in the clear.

Each UR has a configuration file containing a series of settings. The values of the configuration file can be modified by the unit software and can be overwritten by the CS using the appropriate command.

Each module has (optional) a configuration file. The configuration file must be sent to the module when it is started by a command launched from the CS, or it can be pre-installed on the UR during device setup. The configuration file has a basic structure which foresees the presence of one or more <section> nodes, which represent a grouping of configuration values. Depending on the meaning of the section, its structure may vary from a simple text to a data subtree.

In the case of a Stand-alone Network, the software installed on the local CS server allows the management of the M26 local network and the control of the individual URs present in the network. The main functions of the software will be:

- control and configuration of the RUs;

- organization and local delivery of content (provided by the central server or uploaded by the operator);

- local reporting management;

The general architecture of the management software installed on the CS will be similar to that used for the software on the RU (described above), to meet the same flexibility and adaptability requirements for future requests.

The software will then be divided into three layers:

- base system (client server application base);

- common interface (client server application interface);

- specific modules (module manager).

The Client Server Application Base will allow the management of the local network and the sending of specific instructions to individual RUs, in addition to the basic configuration of the RUs and the definition of groups of RUs. The basic system will also provide the operator with the tools necessary to manage the contents - locally loaded or received from the MS - and make them available to individual RUs or groups of RUs.

Communication with the RUs is managed using a proprietary protocol.

The management of the individual modules (Specialized App Module) available on the UR will be carried out using dedicated tools, identified as â € œModule Managerâ €.

Each Module Manager has been designed taking into account the specific needs of the modules (Specialized App Modules) installed in the UR, providing the tools necessary for their operation (for example server for VOIP module) and any configuration tools or features.

Client Server Application Base will use a specific Module Manager to manage each Specialized App Module.

The Module Manager modules will implement a common abstract interface in order to simplify module development and facilitate the integration of new features with the Client Server Application Base.

The architecture of the software installed on the MS will be similar to that of the CS software, thus allowing the direct management of RUs and RU groups.

The MS can actually be considered a CS, with the addition of functionalities related to the management of the entire network of remote units (2).

The software will in fact allow the diffusion of contents to the entire network of remote units, to individual CSs or URs and the monitoring of local networks.

The operator can also use the software on the central server to perform secondary operations such as updating the software of a CS (TBD) or an UR, to restart / enable / disable a remote unit or a single module (specialized module). Commands sent by the central server have priority over any conflicting commands sent by the local server.

In order to optimize the installation process of a network, the system provides a process through which it is possible to automatically detect the URs connected to the network.

In practice, the protocol provides for an authentication mechanism for the actors involved in the exchange of messages. The goal of using an authentication system is to ensure that each actor receiving a message is able to verify the authenticity of the sender.

What we want to avoid is the possibility that a â € œCS fakeâ € is inserted on the network which sends unauthorized commands and contents to the URs, or vice versa that unauthorized URs can communicate with a CS. The same thing is true even if you go up to the higher level where communication takes place between CS and MS and also directly between UR and MS, where the means of communication, ie the web, is completely open.

The package structure is inspired by the most popular network protocols such as HTTP, SMTP or FTP and SIP. A TCP Based protocol has been created where the commands that are exchanged between CS and UR are made up of three distinct sections:

- header size: must always be present and must be 4 bytes in length and must contain an integer value that indicates the length of the header in bytes;

- header: it is the textual part of the message. It contains a first line representing the sent command or response code and a series of multi-line key-value pairs; - Message-Data: Contains the data attached to the message. It can contain from 1 to n attachments (files of any type). Its composition is indicated in the header.

The command and control members of the elements described above and illustrated in the attached drawings are of the type known to those skilled in the art and, therefore, may not have been described in further detail for simplicity. Furthermore, the details of execution may in any case vary in an equivalent manner in the shape, size, arrangement of the elements, nature of the materials used, without however departing from the idea of the solution adopted and therefore remaining within the limits of the protection granted by this patent. .

Claims (10)

CLAIMS 1. Multimedia and interactive information system that can be used for conferences, theaters, sporting events, didactics, shopping centers, for cultural or recreational purposes; system comprising one or more central units (1) and a plurality of remote units (2), each equipped with a display, a graphic interface for the user and audio / video and graphic accelerators arranged on a microprocessor having a high computing capacity and connected, in bidirectional mode, to the central unit via a transmission network (3); said remote unit being of the low energy consumption type, and made without moving or noisy parts, so as to allow reduced thermal dissipation and total operating silence; system characterized by the fact that the connection between said one or more central unit and remote units is such that said remote units (2) form autonomous sub-networks or single units in stand-alone mode; in that the system is equipped with both proprietary hardware devices, or configurable custom boards, both commercial or consumer, on which a complete operating system is resident, capable of managing a plurality of functional or application modules (22 ) in multitasking mode; and by the fact that said one or more central unit (1), operating through the transmission network (3), remotely manages the modules (22) of the remote units (2), enabling and disabling the said modules (22) on each of the units (2 ) of the sub-networks or single units, with the possibility of dynamically configuring both the multimedia contents, resident or streaming, on the said remote units (2) and the relative user interfaces suitable for the use of the same. 2. System according to claim 1, is characterized by the fact that said remote units (2) are provided with image display and / or processing means for graphic management in HD and 3D resolution. 3. System according to claim 1, is characterized by the fact that said management means of said one or more central unit (1) are suitable for the authentication and automatic identification of the connected remote units (2), thus to manage and monitor the same remote units (2) through centralized supervision software that communicates with the local resident software. 4. System according to claim 1, characterized by the fact that the remote units (2) can receive data from the central unit (1) automatically in push mode or on request in pull mode also from sources external to the system and to it connected via the connection network (3) or other external networks. 5. System according to claim 1, characterized by the fact that VoIP type connections are provided between the same remote units (2), between remote units (2) and central unit (1) and between remote units (2) and external units on other networks. 6. System according to claim 1, characterized in that wireless connection means are provided for mobile devices which are connected to the central unit (1) with the same functions as the remote units (2). 7. System according to claim 1, characterized in that the said means for remote management of the remote units (2) suitable for enabling and disabling the said modules of the peripheral units allow the distribution of audio / video multimedia contents of formats and resolution different to remote units (2) of the same network, with the possibility of reproducing such contents both locally after storage, and in live mode via direct streaming according to a data transport protocol. 8. System according to claim 1, characterized by a multi-user management by the remote units (2), so as to allow selective access to the different functional modules loaded on the operating system, being provided means of identification of the users through software methods , or codes and / or passwords, or hardware, such as smart cards and / or USB keys and / or NFC cards. 9. System according to claim 1, characterized by the fact that the remote unit (2) is provided with means for collecting user information from the units, means which include a camera and a program for recognizing the somatic features , and that means of storing and / or processing the collected data resident locally on the remote unit (2) and / or on the central unit (1) to which they are transmitted via network (3) for the creation of reports and / or database. 10. System according to claim 1, characterized in that each remote unit (2) is provided with several interactive screens, even of different sizes and managed simultaneously.