RU2732729C1 - Method for integration of peripheral devices of software and hardware systems - Google Patents

Abstract

FIELD: data processing.SUBSTANCE: invention relates to means of integrating peripheral devices as part of software and hardware systems. Software and hardware system includes at least one peripheral device connected to central computing unit, equipped with a Linux-like operating system (OS). System-wide software (SWS) is installed on each computing unit. Integral unified means of information exchange of software and hardware systems are provided. Guaranteed protected interaction between end applications and peripheral devices of software and hardware systems is provided by means of system-wide software interfaces. Protected storage of configuration settings and current conditions of peripheral equipment of software and hardware systems is formed. Transparent control of arbitrary peripheral devices of the software and hardware systems is realized by means of installed end applications through system-wide software (SWS), compatible with XFS 3.20 and higher standards specifications, OPOS and OPC UA. Final software and hardware systems are formed to perform the required range of functional tasks of software and hardware systems.EFFECT: technical result consists in providing uniform (unified) data exchange and control of these peripheral devices.8 cl, 1 dwg

Description

The technical field to which the invention relates

The present invention relates to computer technology, and more specifically to a method for integrating peripheral devices as part of software and hardware complexes (PAC), which are combined in a single construct (case) of terminal devices of different purpose (monitors (screens), printers, scanners, readers , cameras, switches, etc.) connected to a central computer (built-in personal computer).

State of the art

Currently, there are several different proposals for ensuring the integration of information resources and the implementation of a unified computing process within the framework of automation systems (KSA), software and hardware complexes (HSC), as well as distributed networks of automation objects (OA).

So, in the patent of the Russian Federation No. 2359319 (published on May 11, 2007), a method for integrating heterogeneous information resources in heterogeneous computer networks is disclosed. In this method, in order to ensure a unified computing process, specialized software (software) is implemented, which provides a unified addressing of network objects and unified means of bringing heterogeneous information to these objects. This software belongs to the class of system-wide software (OSPO), often called middleware - software of the "middle layer" developed to solve various integration problems in the interests of "large" systems and complexes and providing the functionality of specialized "glue" that is absent in general software ( OPO), which includes, for example, operating systems (OS) or database management systems (DBMS).

This solution refers to network devices that are combined into a single computing process using stack protocols. IP, which refers, rather, to the formation of the KSA of the automation object, rather than the PAC of the product. In the PAK, the main buses providing interaction with peripheral devices are the COM and USB buses, implemented at the PAK OS level, and not the KSA network.

In the patent of the Russian Federation No. 2008108965/08, (publ. 08.08.2006), an architecture and a device for managing heterogeneous resources on a field basis are described. The integration of field devices into a single complex is realized through an intelligent interface module, which contains at least one connection port for data transmission, configured to connect to a data transmission network, as well as at least one connection port for communication with the process, configured to be connected to a field device bus, comprises a controller and a memory coupled to the controller. This arrangement allows one or more field devices and / or field device buses to be connected. Higher-order functions provide calibration and diagnostics of a complex device, implement the narrow task of creating a distributed control system, including virtual field (remote) devices.

The implementation of the integration entity under this patent is to create a separate integration gateway - a hardware module built into the control system. The question of scaling such a device, depending on the number and types of various peripheral devices included in the PAK, remains unknown. Again, the specified device is assumed to be a network device. Not any PAK construct can provide the placement of such an additional device in its composition from purely spatial and design features, as well as power capabilities.

In the patent of the Russian Federation No. 2013147099, (publ. 03/29/2012) discloses a method and device for transferring files describing configurations of a peripheral device to the host computer, which is necessary to support a specific version of the peripheral device. The method includes the following steps: connecting a peripheral device to a host computer with the ability to exchange data in order to install a peripheral device in the process control system, obtain description and configuration data of the corresponding version of the peripheral device, access a configuration file contained in the memory of the peripheral device, and transferring the device description file from the peripheral device to the host computer. The task is implemented using a specialized hardware controller that provides data exchange between the device and the host computer.

In the application for this patent, it is not entirely clear what the said controller is, which implements the functions of storing and transferring configuration files of devices. Typically, these kind of controllers are built-in expansion cards (for example, on the PCI or PCI-X bus), for which there may simply not be room in a particular PAC. In addition, the driver of such a controller must be supported by the current PAK OS. Otherwise, the functionality of the controller is not provided. If the mentioned controller is an additional network device, then for a specific PAK, its integration may be structurally impossible due to dimensional problems or power issues.

Application No. 2018117162, (published on 05/08/2018) reveals a way to integrate equipment into automated control and accounting tools, which is necessary, first of all, for centralized management and accounting of various equipment of automation systems, Smart Homes, music and audio-video systems, data accounting servers and resources. The key task to be solved is to ensure the compatibility of dissimilar equipment within the Smart Home system (and similar systems) for centralized control. To solve this problem, a control server with a database containing the API of a specific equipment and a driver for this equipment is described. Through this bunch of entities, the equipment is controlled by the user, the interface of which is also implemented as part of the server.

The issues of forming the mentioned driver remain unclear, especially in the case of a large number of different types of equipment. In this case, the mentioned API functions of each unit require additional storage and embedding in the management interface. Thus, the number of integration tasks into the integration server will be equal to the number of the declared PAK peripheral equipment. In addition, the API functions of each peripheral unit vary significantly from manufacturer to manufacturer. Thus, the range of integration problems to be solved increases proportionally.

The solution described in document US 2016170390 (A1), (publ. 06/16/2016) concerns the control of external devices connected to the control device, and the control device includes: a communicator configured to receive a service rule from the server, including a trigger condition and device performing an action; and a controller configured to select one of the devices connected to the control device based on the received service rule, change the received service rule, and control the selected device using the modified service rule.

The disadvantages of such a solution are, for example, the need to make changes to the control system when connecting new equipment, increased requirements for computing resources and low speed in information processing and equipment management, as well as the well-known scaling disadvantages described above.

In patent No. 2002104360/09, (publ. 07/19/2000) and in application No. US 00/19699 () (publ. 07/19/2000) describes the formation and improvement options for specialized PAK for the banking industry - automated cash registers (AKM) and their functioning in global networks. The description indicates that the networks that use AKM and other types of automated banking machines are usually private with limited access. This is to prevent fraud or tampering with the network or user accounts. Private networks are also commonly used to carry credit card messages and other financial transaction messages. Access to such a credit card processing system is also limited, primarily to maintain security. This is an outdated invention, if only because the currently existing ATMs work well on the Internet. This is an important disadvantage of this application. However, an interesting aspect of the description is the statement that in the exemplary embodiment of the invention, the ATM tasks are accomplished by an automated banking machine that includes output devices such as a display screen, input devices (touch screen and / or keyboard). The banking machine further includes peripheral devices such as a cash dispenser, a printing mechanism, a card reader / writer, a depository mechanism, and other functional transaction devices that it uses to execute banking transactions.

The central computer in an exemplary embodiment of an automated banking machine further includes a software interface portion for communicating with devices. The software interface part for communicating with devices is designed to receive messages from the device control application part and to force the devices to operate through corresponding hardware interfaces. In one embodiment of an automated banking machine, the document processing part, the device control application part, and the software interface part for communicating with the devices are each residing on the same computer and communicating via different IP ports.

The mentioned part of the software interface for managing peripheral devices operates under MS Windows and meets the requirements of the standard for financial transactions between the modified J / XFS kernel and the WOSA / XFS administrator. The solution itself, which implements the "bank-client" exchange, is implemented in the JAVA language and operates under the control of a JAVA virtual machine. In the description of the invention there is no information on how exactly the mentioned part of the program interface functions in MS Windows.

In patent No. 2002134905/09 (published on May 23, 2001), as well as in applications No. US 60 / 207,043 (published on May 25, 2000), US 01/16775 (published on May 23, 2001) describes the PAK of the same class - automatic cash registers for financial transactions. The technical result consists in the creation of a machine that operates on different platforms of automatic cash registers. The machine includes a computer and many operational functional (peripheral) devices, many driver components corresponding to the specified functional devices. Drivers act in response to XFS-level communication to control the operation of operational function devices. The machine includes a terminal application and an open device service layer, which contains many components corresponding to drivers and responding to the terminal application, providing control of the operation of operational functional devices from the driver side through communication with the XFS layer.

The above-mentioned part of the software interface is here called a level, the concept of operating device drivers is introduced. The aforementioned machines include MS Windows, the program code of terminal (end) applications is also written in the JAVA language. The implementation of the standard for interaction with peripheral devices is provided by embedding the J / XFS kernel at the runtime level (virtual JAVA machine), and the counterpart of the unified device management system is implemented at the MS Windows OS level in the form of a WOSA / XFS administrator (with ODS storage), using the components Windows ActiveX framework.

The patent No. 2017102415 (published on 01/25/2017) also describes the standard for ensuring the management of PAK peripheral devices in the banking sector - WOSA / XFS. These devices are integrated into an ATM-type PAK and are described as financial devices. They also function on the MS Windows platform. The technical result of the invention is to improve the security of said financial devices. In general, the information system of the device contains a configuration subsystem containing an interconnected module for identifying executable files, a module for identifying and generating a list of service providers, which are separate executable files that implement the WOSA / XFS SPI software interface, which provides identification of service providers based on analysis executable files detected by the executable file identification module, and generating a list of identified service providers, and a module for generating a list of applications that are allowed access to service providers, as well as a subsystem for controlling access to service providers, containing a module for intercepting application calls to service providers, which ensures that the requested service provider is in the list of service providers, and a blocking module that provides access to service providers to an application that is in the list of applications that are allowed access to service providers, and blocking access for an application that is not in the list of target applications.

The above invention relates generally to the field of protecting the information systems of said financial devices managed using the extensions for Financial Services (XFS) standard, and more specifically to means of protecting service providers of peripheral devices of automatic banking machines and other financial devices from unauthorized access.

In the document US 7493286 B1 (published on February 17, 2009), a filtering module for a transaction processing system is disclosed. This invention proposes to extend the WOSA / XFS standard, which will allow filtering of transactions by embedding filtering modules into the current architecture. This solution also offers XFS device architecture modification and reconfiguration.

This invention requires hardware intervention in the existing configuration of the financial device (due to the implementation of an integrating entity that supports the XFS standard as a hardware module), which significantly complicates its formation and increases the cost of maintenance.

GB 2319102 A (publ. 13.05.1998) also discloses a security module for a transaction processing system within financial devices. In this invention, it is proposed to use a security module through which all calls according to the open standard WOSA / XFS from banking (application) software will pass. This module is responsible for identifying the end application that attempts to access the ATM equipment and in response allows or denies interaction with the devices.

The disadvantage of this technical solution is that it offers to build in a hardware security module and change the existing hardware and software structure of the ATM. For example, you need to modify the installed XFS manager, service provider files, and the MS Windows system registry. This is undesirable, especially if a complete setup has already been performed and the device is functioning properly. This decision also applies to ensuring the security of the current hardware and software infrastructure of the PAK.

Finally, in the application No. 2017120494, (published on 07/01/2015), as well as in the PRC application No. 201410728132.6 (published on 12/03/2014), the general architecture of the CEN / XFS standard on the Linux platform and a method of its implementation for solving financial problems on financial devices self service - PAK mentioned above. The Linux-based CEN / XFS architecture for the financial self-service appliance contains: an application programming layer, an XFS control layer, a service provider (SP) layer, and a peripheral driver layer. In this architecture, the XFS control plane is divided into: the special application layer, the universal application layer, and the system services (OS) layer. This invention is the first to describe a method for implementing the CEN / XFS standard on the basis of the Linux operating system, since previously similar PACs were implemented on the MS Windows operating system. There was no CEN / XFS implementation on Linux in the prior art.

The invention discusses several options for the implementation of the CEN / XFS standard using the known system resources of the Linux operating system, for example, the Linux OS system service for managing logs is used to provide logging and logging, the Linux OS system service for managing registries is used for read configuration information, the Linux OS system service for memory management is used to manage memory, the Linux OS system service thread management is used to support mutually exclusive access for multiple applications, the Linux OS system service for communication management is used to uniformly manage the semaphore and message handler, etc. ...

All these and some other developments solve particular and general problems of integrating peripheral devices for various purposes, type and manufacturer as part of a single computing process provided by some software and hardware complex (HSC). Most often, such a PAC represents terminal peripheral devices (monitors (screens), printers, scanners, readers, cameras, keyboards, manipulators, etc.), combined in a single construct (case), connected to a central computer (built-in personal computer, operating under OS control).

There are quite a few PAKs for performing specialized computing operations, especially in the branches of the power unit - these are various simulators, AWPs for officials at control points, etc., equipped with various peripheral devices such as screens, keyboards, information security hardware, manipulators. The most prominent representative of the PAK are also modern remote financial self-service devices (ATM - Automated teller machine). These are PACs designed for the automated issuance and / or acceptance of cash, both with the use of payment cards and without, as well as performing other operations, including payment for goods and services, drawing up documents confirming the relevant operations. In addition to those mentioned above, they are equipped with specialized peripherals such as bill scanners, card readers, currency dispensers, cameras, etc.

Many of these types of devices are network devices and are connected to a central computer (a computer from the PAC) via the network, through a switch, which is also part of the PAC. However, not all devices are networked. The most common system buses for connecting specialized peripheral devices in PAK are serial buses COM and USB. Therefore, many peripheral devices are connected directly to the system buses. This speeds up the processes of operational management of such devices, but somewhat complicates the methods of managing them. If we talk about the central computer, then most often it is a fairly powerful embedded personal computer implemented on the Intel (AMD) platform with x86 architecture (32 or 64 bits) with MS Windows operating system from Microsoft Corporation. This important fact emphasizes that there are still no real implementations of PAK on platforms with processors of other architectures - ARM, MIPS, RISC-V, Elbrus, Bakal, etc. Until recently, at the mentioned level of technology, there was no implementation on Linux, and on the indicated architectures even now.

The first and most urgent task of creating a multifunctional HSS for carrying out a variety of user (for example, financial) operations based on the collection and analysis of operational information about the state of peripheral devices of the system is to ensure reliable information interaction between applied tasks operating on the HSS and peripheral devices that the user accesses. ... The task of ensuring the interaction of end applications and HSS devices using various drivers, data formats, configuration features within the framework of a single HSS computing process sooner or later confronts the designer of any HSS. Information security issues should have the highest priority and be the fundamental functionality of the PAK, especially if we deal with remote financial self-service devices.

Thus, the main decision on the creation of information technology support for the PAK, including on the basis of the above comments, is the decision on its architecture. As we can see from foreign practice, a two-tier architecture with a logical separation of "levels", "parts of the program interface", "integration modules", etc. has been used for many years (see above). One way or another, this means that applied tasks interact with peripheral devices almost directly, each time changing the mentioned "software interfaces" or "integration modules" when changing the type of device or its manufacturer when forming the hardware part of the HSS. It is necessary to strictly unify such interaction not only on the basis of some standardized protocol (for example, XFS or OPOS), an OPC UA platform for the implementation of the Industrie 4.0 standard, but, above all, with the implementation of a three-tier architecture for organizing the computing process on each HSC.

This means that as part of the software component of the HSS, it is necessary to implement the usual three-tier architecture with the use of software (software) "middle layer" related to the system-wide software (OSPO). Then all the applied tasks of the PAK (subsystems) will not work directly with the peripheral devices of the PAK (although there is also such a method), but through some additional "middleware", which not only levels the differences between devices, not only performs the functions of information logical interconnection of heterogeneous applications, solving the problems of routing, guaranteed information delivery, access control, but also provides a unified security policy in such a heterogeneous environment, creates an internal storage of configuration data, works out general regulations for interaction with system buses, etc. On the formation of this type of software and ways of operating the OSPO with information resources, see patents # 2306600 (publ. 11.04.2006), 2359319 (publ. 11.05.2007), 2361366 (publ. 29.11.2007) and 2415466 (publ. 15.07 .2009).

Such an architectural approach today is the most promising one, allowing to solve the problems of joint functioning of heterogeneous peripheral devices of various types and manufacturers within the framework of a particular PAC. As a general method for integrating various network information resources in geographically distributed heterogeneous networks, it is discussed in detail in the aforementioned application No. 2359319 (publ. 05/11/2007), but applies to network devices in heterogeneous networks. The general architecture for solving the problem of integrating peripheral devices of various types as part of a single UAC based on the creation of OSPO tools is shown in Fig. 1.

Note that the implementation of integration in this case is only equal to the number of integration tasks for each peripheral device with the OSO ("bottom" (200) based on the use of various system capabilities of the OSO, the SPI interface - Serial Peripheral Interface, SPI bus - the serial peripheral interface, the SPI bus), as well as an additional number of integration tasks for specific end applications (“top” - 100) with a new entity for them - OSPO, which provides an open set of API functions to the application level, which are embedded in the application level at the programming stage. Those. the number of integration tasks is finite and invariant with respect to the application level, provided that the HAC software environment remains unchanged, as well as the peripheral level when the condition for standardizing the control interface and the capabilities of the system buses of the OS and OSPO is met. In the case of integrating the APC application level directly to the level of functioning of peripheral devices, the number of integration tasks (pair number of combinations) depends on the number of devices such as N * (N-1) / 2, multiplied by the number of applied tasks, which is very large and varies depending on device type and manufacturer. With this approach, the creation of a PAK is possible with a minimum number of devices (N). However, in the well-known PAC such as financial service devices, dispatcher's workstation, etc., the number of peripheral devices can reach 10, which makes the integration problem as a whole not solvable.

An essential feature in the formation of the PAK is also the decision on the platform of its central computer. For a long time, such a platform was formed on the basis of x86 architecture (32 or 64 bits) using Intel or AMD central processing units (CPU 300). And today, most of the options for application software in financial service devices (ATM), for example, runs on MS Windows OS of rather old versions that are no longer supported by the manufacturer (for example, MS Windows XP OS), and only a few options in the world of application software for such devices function on a Linux-like OS running an Intel CPU. For this particular industry, the financial services regulator issued the WOSA / XFS standard (version 2.0) and submitted this standard to the European Committee for Standardization (CEN). According to the latest data, the CEN WOSA / XFS working group has published version 3.30 of the specified standard. The WOSA / XFS Protocol is also called the CEN / XFS Protocol. Open System Architecture for MS Windows (WOSA for short) is the software architecture proposed by Microsoft Corporation for the MS Windows operating system, and WOSA / XFS (Windows Open System Architecture Extensions for Financial Services) are extensions for implementing financial services based on WOSA ... Many applications in the HSC of this industry, operating under the MS Windows OS on the x86 platform (Intel, AMD), use the capabilities of this standard in the formation of the HSC ATM software environment (see above).

It is known that OS of the MS Windows family, especially those discontinued and not supported by the manufacturer represented by Microsoft Corp. - MS Windows XP and MS Windows 2000 are not reliable enough not so much for performing financial transactions as for functioning on remote self-service devices in general due to the imposition of automatic modifications and updates, as well as because of the widely documented undeclared opportunities for an intruder to access stored information ... Thus, there is a need to develop a PAK on a software platform with a Linux-like OS, including exclusively Russian-made. And also - a hardware platform with the use of components of exclusive Russian production, for example, central processors "Elbrus", "Baikal", etc. The main condition for the development of applied software in the financial sector is the implementation of the CEN / XFS protocol at the OSPO level in a Linux-like OS and ensuring the functioning of such an architecture of the computing process as part of a PAC with different microarchitectures of central processors - x86, ARM, MIPS, Baikal, Elbrus, RISC -V, OpenPower, etc. The same applies to the OPOS standard, which is used to integrate software and hardware systems intended for the automation of trade and the service sector, the so-called POS terminals, where POS - Point of Sale - is a specialized workstation of a point of sale seller.

It is also known that many specialized AWPs have long been operating under Linux-like OS (for example, MS VS OS), and even on hardware components of HSS with other architectures than x86, for example, MIPS, but without the formation of a dedicated OSP that implements the integration protocol into the form of an integration bus in the PAK, as described in this invention.

From all of the above considerations, natural requirements follow for the system-wide OSPE tools that implement a three-level approach when implementing interaction in a single computing process of a software and hardware complex:

- The functioning of the system-wide means of the OSPO integration bus on peripheral devices of various types and manufacturers through the unified SPI interface.

- The functioning of the system-wide means of the OSPO integration bus on various types of final HSS applications from different manufacturers through a documented API.

- Implementation of a local storage system for the configuration of the PAK of various types by means of an open ODBC / JDBC interface (400) to the system storage facilities or saving to a file.

- Unification of access of end-use PAK applications to heterogeneous data of PAK peripheral devices using system-wide OSPO tools.

- Implementation of synchronous and asynchronous exchange of system-wide data between end applications and peripheral devices, mainly in the form of messages in the JSON format.

- Configuring and managing an agreed information security policy when working with information objects (documents / files / messages) within the HSC by means of the HSC OS and OSPO.

- Support for guaranteed service of application requests and storage of your own data on the local storage of the PAK configurations.

- Unification of means for monitoring the state of the PAK storage facility with the general system means of OSPO.

In the interaction of end applications within the HAC, as we see, it is necessary to ensure not only their "physical", channel connectivity, but also the "logical" connectivity of the system objects as a whole, i.e. to create a unified information space, realizing, on the one hand, a common language of "communication" of processes (applied tasks) of the HSS, on the other hand - a unified space of peripheral devices, leveling the difference in the types and manufacturers of these devices. In general, these are the stages of one process - the creation of a single information space for the PAK.

The traditional solution based on data exchange through point-to-point software interfaces and applications working directly with peripheral device drivers, “squarely” reaches a dead end with an increase in the number of interacting applications and the number of devices, as well as the complexity of the application interaction logic. Considering not only the high cost of such solutions, but also the high cost of ownership, the need for significant modernization of applied tasks in the event of changes in the devices themselves within the limits of even a known fleet of peripheral equipment is obvious. This solution, despite a number of advantages, is no longer relevant today.

Thus, the solution to the general problem of integrating end applications and peripheral devices in this formulation is reduced only to the rules of information exchange along the vertical of the software-OSPO-DBMS-FILE-OS, to the use of system-wide means of storing configuration information about each device, the speed of operation of the mentioned OSPO interfaces, as well as the speed of "parsing" of JSON messages by system-wide data transmission facilities.

The essence of the invention

There is a need to implement a common secure system-wide environment for the execution of the PAC with the integration of various peripheral devices to ensure a uniform data exchange between the central computer and the mentioned devices for all end application tasks through unified (standardized) exchange regulations.

To solve this problem, a method is proposed for integrating peripheral devices within the framework of a single computing process of the PAC, which includes at least one peripheral device with a driver for a Linux-like operating system (OS) connected to a central computing installation that operates on one of the listed hardware platforms - x86 (Intel, AMD), ARM, MIPS, Baikal, Elbrus, OpenPower, RISC-V and is equipped with a Linux-like operating system (OS) different from others, and in the context of this OS, at least one terminal the application of this computing unit, which consists in installing general system software (OSPO, middleware) on the central computing unit to obtain a single secure information exchange highway between all arbitrary peripheral devices of the PAK connected to the specified computing unit ... In addition, for each PAK peripheral device, they provide unified unified means of informational synchronous / asynchronous exchange with the central computing unit of the PAK, realizing the physical connectivity of the mentioned peripheral devices within the mentioned protected information exchange highway through the serial interface of peripheral devices (SPI - Serial Peripheral Interface ); provide guaranteed secure interaction between the end applications installed on the said computing installation of the HSS, through the mentioned means of information exchange through the automatic interaction of each said end application operating in the context of the OS with the installed OSPO, through the application programming interface created by the mentioned OSPO (API - Application Programming Interface) ; create a secure data storage on said computing installation by means of said OS using the ODBC (Open Database Connectivity) / JDBC (Java Database Connectivity) database access programming interface or saving to a file; save in said storage of said computing installation configuration settings and operating data on the current state of the peripheral devices of the UHC necessary for the operation of the final applications on it; provide guaranteed secure control of said peripheral devices through end applications installed on the said computing installation of the PAC, provided by said means of information exchange of the OSE, as shown in FIG. 1.

A feature of the method according to the present invention is that it forms the said system-wide software (OSPO) in the form of a background daemon process (daemon) by installing OSPO tools and adding a base set of peripheral interfaces and protocols (COM, USB, etc. .), designed to connect peripheral devices from different manufacturers, as well as a set of system calls and functions to provide synchronous / asynchronous application-level data exchange (API); as well as a single secure information space of the said UAC by streamlining the information exchange between the mentioned end applications by providing intermediate reassignment of information flows, automatic conversion of extracted data formats for their uniform presentation (for example, in JSON format) in the interests of the joint functioning of the mentioned end applications and peripheral devices PACK; provide a uniform implementation of the system for presenting and transmitting data within the mentioned HAC, including in the conditions of pronounced heterogeneity of software and hardware implementations of the mentioned HAC peripherals; save in the said storage of the mentioned computing installation the configuration settings of all peripheral devices of the PAK; carry out guaranteed processing of uniform data, regardless of the features of the functioning of the above-mentioned final applications of the PAK on the mentioned computing facility PAK.

Another feature of the method according to the present invention lies in the fact that the said interaction of the end applications of the UAC according to the client-server technology is carried out by reconfiguring the interfaces of each of these end applications for synchronous data exchange with other end applications by redirecting information flows between end applications through the corresponding connections, provided by means (API) of the mentioned OSPO; the mentioned reconfiguration of the end application interfaces in this Linux-like operating system is implemented by redirecting information flows between end applications through the corresponding functions and calls using PIPE or Socket technologies, implemented by means (API) of the said OSO.

In addition to the previously mentioned add-on of a Linux-like operating system, a basic set of peripheral interfaces and protocols is implemented by reconfiguring the resources of the said operating system to unified means of providing synchronous / asynchronous information exchange with peripheral devices from the said OSO; provide a guaranteed possibility of extracting heterogeneous data from the peripheral devices of the PAC operating both in the context of the said OSPO and in the context of the mentioned Linux-like operating system of the said PAC; provide storage in the said storage of the said computing installation of configuration settings and data on the current operating state of all peripheral devices of the PAK in order to ensure their control through the final applications of the PAK, as well as the guaranteed possibility of transparent control of the mentioned peripheral devices of the PAK, functioning both in the context of the said OSP, in the context of said Linux-like operating system of said PAC, by means of end applications installed on the central computer installation of said PAC; implement compatibility with XFS (extensions for Financial Services not lower than 3.20), OPOS (OLE for Retail POS) and OPC UA (Open Platform Communications Unified Architecture) standards.

Finally, a number of other features of the method according to the present invention consist in the fact that further integration of the final PAK begins with the installation of a central computer (embedded personal computer - PC) in the said PAK, which is implemented on one of the listed platforms - x86, ARM, MIPS, RISC-V , Baikal, Elbrus with 32- or 64-bit architectures; after which the peripheral devices are selected from the group, which includes at least: screens (monitors), printers, scanners, card readers, biometric control devices, cameras, dispensers, uninterruptible power supplies, network devices, etc.; then, the mentioned subsequent manipulations (connections) with peripheral devices from the group are performed for further integration of the final PAK, including: a case, a screen (monitor), a central computer, a network device, an uninterruptible power supply device, a set of other necessary peripheral equipment; and to complete the integration of the final PAC, installing and configuring the Linux-like OS, the PAC configuration storage system, as well as the aforementioned end applications and system-wide software (OSFS) are performed.

Brief Description of Drawings

The invention is illustrated by the following drawings:

FIG. 1 represents the integration technology in the method of the present invention;

Description of the invention

On each specific hardware-software complex, there is a so-called "vertical" synchronous / asynchronous information exchange, i.e. The end applications installed in the HSC carry out routine synchronous / asynchronous data exchange between themselves and various peripheral devices installed in the HSC with predetermined formalized data, linking the necessary business processes within each of the HSC end applications with the operations of the user-operator controlling the said HSC. In this case, information interaction is implemented through the described and developed software interfaces, one of which is the so-called SPI - Serial Peripheral Interface, which standardizes the procedure for applying software to access peripheral device drivers that provide control using the system services of the PAK OS. Usually, along with the operating systems of the OS developer, they supply drivers for key hardware components, without which the system cannot work. However, some devices (such as a video card, printer, scanner, reader, etc.) may require special drivers, usually provided by the manufacturer of that device. A device driver is a special program that ensures the operation of a peripheral device as part of a well-defined OS, for example, Microsoft Windows, AltLinux, MC VS, etc. and implements the general scheme of "vertical" interaction: USER - APPLICATION - OS - EQUIPMENT. It is quite obvious that a peripheral device that does not include such a driver for a specific OS (OS family) will not function as part of a PAC with this OS. There are also possible features in the functioning of specific peripheral devices under the control of specific OS on hardware platforms implemented on ARM, MIPS, RISC-V processors, etc. the ideal case of a completely adequate operation of a specific peripheral device is the presence of a special driver for this device, designed to work as part of a specific software and hardware platform of the said PAC.

This circumstance significantly complicates the final integration of the PAK itself from the set of compatible devices. Even under the condition of ensuring the correct functioning of the device as part of the PAC (for example, printing receipts on a thermal printer), there remain quite tangible difficulties in ensuring its operability from under the control of the final application developed by a different manufacturer (than the manufacturer of the printing device itself). To solve this problem, the manufacturer of the end application must provide a call to a peripheral device either directly working with the driver of this device, or by referring to some unified entity, for example, the SPI interface, through which the call to the device driver is standardized. It is quite obvious that such unification is the most adequate. It is this circumstance that proves the need to move this interface and the entire software infrastructure that provides it to the level of the basic unified transport environment, which is based on the general system software of the "middle layer" of the MOM class - Message-Oriented Middleware (middleware oriented to messages) ... Above, we noted the use of JSON messages as part of such an OSPO as the most modern version of the exchange of formalized data. In this way, the most relevant today asynchronous interaction is implemented, which involves a one-time exchange procedure (message transmission) without the need to support the exchange channel during the entire exchange process.

This happens in the case of implementation of synchronous information exchange (for example, in client-server technology). In this case, the OSPO acts as a "server" for both the final application through the API interface, and for the device through the SPI interface. It is the OSPO that responds to the support of the "communication channel" between the application and the peripheral device to weed before the completion of the PAC operation, which requires synchronous interaction. An important purpose of the OSP is the presence in its composition of a specialized storage of configuration information that unambiguously identifies a specific device from a specific class of devices, which verifies this device to determine its current state from a separate storage of working information about it.

Thus, the implementation of the system in a single technological key is achieved, while ensuring the solution of basically the same target tasks of device management as based on direct end-to-end use of devices, in fact, unreasonably raising the bar for achieving the goals of integrating applications and devices as part of the PAK. This approach allows us to solve a very important problem: to reduce the exchange between tasks and peripheral devices within the PAK to virtual (not physical) interaction with a new entity for them - a server-like OSO for implementing synchronous interaction, and an OSO of the MOM class - for asynchronous tasks.

The proposed method for integrating peripheral devices is intended to be implemented within an arbitrary PAC, which includes at least one peripheral device with a driver for a Linux-like operating system (OS) connected to a central computing installation that operates on one of the listed hardware platforms - x86 (Intel, AMD), ARM, MIPS, Baikal, Elbrus, OpenPower, RISC-V and is equipped with a Linux-like operating system, and in the context of this OS, at least one final application of this PAK operates. The method of integrating information resources in such a heterogeneous computer network is carried out by performing the following actions (steps).

First, system-wide software (OSPO) is installed on the central computing unit as part of the PAK to obtain a single secure highway of information exchange between all end applications and peripheral devices of this PAK. An example of such an OSPO is the information and computing complex "IVK Jupiter ™", developed by the employees of the owner of the rights under this application. The main functionality of this complex is described in the journal "Open Systems" No. 7-8 for 2003.

In addition, for each PAK peripheral device, they provide unified unified means of informational synchronous / asynchronous exchange with the central computing unit of the PAK, realizing the physical connectivity of the mentioned peripheral devices within the mentioned protected information exchange highway through the serial interface of peripheral devices (SPI - Serial Peripheral Interface ); provide guaranteed secure interaction between the end applications installed on the said computing installation of the HSS, through the mentioned means of information exchange through the automatic interaction of each said end application operating in the context of the OS with the installed OSPO, through the application programming interface created by the mentioned OSPO (API - Application Programming Interface) ...

Next, a secure data storage is created on the said computing installation by means of the said OS using the ODBC (Open Database Connectivity) / JDBC (Java Database Connectivity) database access programming interface or saving to a file; save in said storage of said computing installation configuration settings and operating data on the current state of the peripheral devices of the UHC necessary for the operation of the final applications on it; provide guaranteed secure control of the said peripheral devices through end applications installed on the said computing installation of the PAC, provided by the mentioned means of information exchange of the OSPO.

The mentioned system-wide software (OSPO) is formed in the form of a background daemon process (daemon) by installing OSPO tools and adding a basic set of peripheral interfaces and protocols (COM, USB, etc.) to the mentioned operating system, intended for connecting peripheral devices from various manufacturers, and also a set of system calls and functions to provide synchronous / asynchronous application-level data exchange (API);

A single protected information space of the mentioned HAC is created by ordering information exchange between the mentioned end applications by providing intermediate reassignment of information flows, automatic conversion of extracted data formats for their uniform presentation (for example, in JSON format) in the interests of the joint functioning of the mentioned end applications and PAC peripherals ... A uniform implementation of the system for presenting and transmitting data within the framework of the said HAC is also provided, including in the conditions of pronounced heterogeneity of the software and hardware implementations of the mentioned HAC peripheral devices, the configuration settings and operating parameters of all HAC peripheral devices are stored in the said storage of the said computing installation. By means of the OSPO PAK, guaranteed processing of uniform data is carried out, regardless of the peculiarities of the functioning of the above-mentioned final applications of the PAK on the said computer installation PAK.

In general, the interaction of final applications of the UAC using client-server technology is carried out by reconfiguring the interfaces of each of these final applications for synchronous data exchange with applications and devices by redirecting information flows between the final applications through the corresponding connections provided by means (API) of the OSF. This reconfiguration of the end application interfaces in this Linux-like operating system is implemented by redirecting information flows between end applications through the corresponding functions and calls using PIPE or Socket technologies, implemented by means (API) of the mentioned OSO.

In addition to the previously mentioned add-on of a Linux-like operating system, a basic set of peripheral interfaces and protocols is implemented by reconfiguring the resources of the said operating system to unified means of providing synchronous / asynchronous information exchange with peripheral devices from the said OSO. This provides a guaranteed possibility of extracting heterogeneous data from the peripheral devices of the PAC operating both in the context of the said OSPO and in the context of the mentioned Linux-like operating system of the said PAC.

It also provides storage in the OSPO storage of configuration settings and data on the current operating state of all PAK peripheral devices in order to ensure their control through the PAK end applications, as well as a guaranteed possibility of transparent control of PAK peripherals operating both in the context of the mentioned OSPO and in the context of the mentioned Linux-like operating system PAK, through the end applications installed on the central computer installation of the said PAK.

Basic compatibility is implemented here, for example, with the XFS standards (extensions for Financial Services not lower than 3.20), OPOS (OLE for Retail POS), OPC UA (Open Platform Communications Unified Architecture) and other proprietary standards that have a standardized description of the API interface.

Finally, further integration of the final PAK begins with the installation of a central computer (embedded personal computer-PC) into the said PAK, which is implemented on one of the listed platforms - x86, ARM, MIPS, RISC-V, Baikal, Elbrus, etc., from 32 or 64-bit architectures, after which peripheral devices are selected from the group, which includes at least: screens (monitors), printers, scanners, card readers, biometric control devices, cameras, dispensers, uninterruptible power supplies, network devices, etc. , connections of peripheral devices from the group are performed to further integrate the final PAK, the Final PAK includes: a case, a screen (monitor), a central computer, a network device, an uninterruptible power supply, a set of other necessary peripheral equipment. To complete the integration of the final PAC, the installation and configuration of a Linux-like OS, a storage system for PAC configurations and working data files, as well as the aforementioned end applications and general system software (OSPO) are performed.

It also provides a uniform representation of the powers of all officials admitted to work with protected information resources (end applications, OS and OSPO system settings) of the PAC, including those implemented by various OSPO DBMS, which also have their own systems for differentiating access of officials (users) to resources storage of configuration settings of peripheral devices.

The exchange of end applications and peripheral devices, due to the peculiarities of the functioning of the devices themselves, can be implemented in two ways: synchronous and asynchronous. The subject of exchange in the case of the implementation of the OSPO means as MOM (see above) can be short formalized messages in the JSON (or XML) format. The essence of synchronous exchange is the constant synchronization of the transmit / receive time between the sender and the receiver, i.e. between the application process and the peripheral. Most often, such interactions are implemented in the form of requests of specific application processes to the functions of the OSPO API, which acts here as a kind of "server" using socket technology. The OSPO means receive a request for interaction and address it to another mentioned OSPO interface - SPI, waiting for a response to a connection with a specific PAC device from the OSPO stored in the OSPO list under a unique ID (identifier) and OS system log. After receiving a response to a specific application process from a specific device, the configuration and state of which is checked by means of data in the OSO repositories and OS system logs, message transmission is ensured and control action from the end application controlled by the user is implemented. For example, information is read from a plastic card that the user inserted into the card reader slot. For interaction between end applications and peripheral devices as part of the PAC, both standard serial system interfaces (for example, COM, USB, etc.) and network connections can be used. The use of OSPO tools in this case is completely justified, accordingly, the transfer of the tasks of organizing synchronous requests to the OSPO level is expedient precisely because of the need for time synchronization of the reception and transmission processes by some third party (OSPO server), as well as the "routing" of information exchange between application processes and peripheral devices, without saving the actual transmitted formalized message by means of OSPO, but only reflecting information about this event in one of its logs. The aforementioned scheme of organizing information exchange "task-device" is completely valid for the reverse exchange - "device-task".

The OSPO tools are used in a completely different way to ensure guaranteed information exchange of the asynchronous type. In this case, the receiver and the sender exchange formalized data (messages) without time synchronization and the need to establish a blocking synchronous transmission channel for the duration of the transmission itself. Of course, the type of actual messaging depends on the peripheral and is determined by the API function of the called device itself. However, in this case, a queue of messages to its address is associated with each device, and the same queue of responses to requests is associated with each application process. Moreover, these queues are unique and have their own identifiers. Therefore, the task of "routing" messages between the queues of incoming and outgoing messages is also relevant and is implemented by means of OSPO. In addition, the message queues themselves are stored in the OSF repository and are available through the ODBC / JDBC interface. Thus, asynchronous exchange is implemented by redirecting formalized messages in JSON format (or otherwise, for example, XML) from a unique sender queue to an equally unique recipient queue. The sender and receiver can be both terminal peripherals (for example, a PAC screen), and applied tasks (for example, virtual "buttons" on the screen), and vice versa.

Thus, the guaranteed secure interaction between the final applications of the HSC and various peripheral devices of the PC is provided through the created means of "in-machine" synchronous and asynchronous exchange within the HSC. This is achieved through the automatic interaction of each end application with a peripheral device operating in the context of the OSPO, through the created queues of outgoing and incoming formalized messages in the JSON format (or others) stored in a specialized storage of the OSPO, as well as directly through the API-SPI interface, also implemented by the OSPO ... This interaction is provided by automatic exchange of messages between the queues of incoming / outgoing messages of each application and hardware node, as well as by sending a message directly after establishing a blocking connection between them (nodes).

The mentioned guarantee of informational synchronous / asynchronous exchange is provided by the following built-in mechanisms (technologies) of OSPO.

1) Guaranteed delivery of messages within the PAC by returning service messages (receipts) to the address of the sending node about the delivery of the outgoing message to the receiving node and thereby completing the transmission process.

2) Guaranteed storage of incoming and transit messages in a secure storage until the completion of the guaranteed delivery process (handshake).

3) Guaranteed processing of the message body by specifying the identifier (ID) of the final handler application (function) or peripheral device with which the message body should be opened (processed), and sending a service message upon processing to the address of the sending node (confirmation of processing ), which completes the processing cycle of the delivered message. 4) Guaranteed identification of outgoing / incoming (transit) messages through the use of a built-in mechanism for identifying application processes and devices. The implementation of all these mechanisms guarantees the full-fledged execution of the general computational process that provides the applied functionality of the HSS in any capacity - ATM, POS, AWP or other.

The use of OSPO PAK as a means of protecting information (SIS) from unauthorized access is also quite justified. Indeed, all identifiers (IDs) of application processes and peripheral devices are stored in the OSPO storage. The aforementioned API functions of these standards, built into the HAC application processes, uniquely define a specific device, process and order of interaction of these entities. Or, in other words, local “routing” of requests and messages as part of a single computational process of the HSS. Changing the specified lists of local exchange participants is possible only with the consent of the administrator when configuring the entire HSS. Additional installation of peripheral devices or unauthorized installation of applied tasks in the HSS is controlled by the OS IS and OSPO. Of course, no interaction between the application level and the level of peripheral devices is possible without the use of OSF tools, which fully implements the prohibitive principle of information protection in the HSS. As a technical result for the OSPO that implements a certain exchange standard, we get a trusted means of controlling access of applied processes to peripheral devices when performing the following natural steps:

- Formation of a list of PAK peripheral devices and executable files that implement the functionality of these devices;

- Formation of a list of end applications that are allowed access to devices;

- Interception and "routing" of requests to devices from applications;

- Blocking requests from target applications that are not in the list of allowed target applications, which is stored in the OSPO storage, as well as to devices that are not in the list of allowed devices, with subsequent writing to the system log.

The list of HAC peripherals and applications that are allowed to access them can be generated by the HAC administrator or automatically.

It is obvious that the reconfiguration of the interfaces of the operating system or the final application for data exchange with the peripheral devices of the HSS is carried out by redirecting information flows between them through the appropriate software interfaces available in the OSPM, and not through proxy connections. Such proxy connections can be performed in the same manner as described in US patent No. 5898784 or US application No. 2004/0260941.

In addition, the identifier of each final software application operating in the context of the OSPO is stored in the secure storage of the OSPO, together with its checksum, as well as the incoming / outgoing queue, with which you can subsequently control the integrity of the OSPO and application software, and maintain their version control.

In the described embodiment of the present invention, the implementation of standardized calls, for example, XFS, OPOS or others, on a hardware and software platform with Linux OS and processors of various microarchitectures (see above) is fully applicable not only to remote financial self-service devices, point-of-sale terminals, but also to specialized AWPs, which are built according to the specified standards. One of the components of the PAK software stack is the mentioned OSPO, which actually implements these standards. As a result, the general PAC software stack includes the application software level, the OSO level, the peripheral device driver level, and the system level (OS level). In this architecture, OSPO interacts with the application software layer through the API interface, and with the peripheral device driver layer through the SPI interface. At the same time, the involved system-wide resources of the OSPO PAK are used to create and store the general configuration of the software and hardware parts of the PAK, form a transport medium for transmitting formalized messages from the application level to the peripheral level and vice versa, synchronize the times of receiving / transmitting messages in the case of synchronous information exchange, forming queues messages - in the case of asynchronous exchange, as well as "routing" messages to addressees. This method of organizing the computational process in HACs of various nature (with the implementation of various exchange standards and various hardware implementations) is the basis for the development and execution of applied software on the Linux platform, which solves a general technical problem, which consists in the absence of software implementations of these standards, as well as in contributes to the solution of the problem of import substitution in the creation of the PAK.

Figure 1 illustrates a general technology for integrating various application processes with PAC peripherals. The main idea is to introduce some kind of arbiter who will store all the current and configuration information about the state of processes and UAC devices, as well as, according to certain rules in accordance with certain standards, "route" (redirect) information flows from the sender to the receiver, accepting into account the type of exchange.

Thus, in the method according to the present invention, the OSPO solves the following problems:

- creation of a system-wide operating environment with the provision of standard services for data exchange and operational control of peripheral devices within the framework of a single computing process of the HSS;

- ensuring interaction and control of a unified computing process (solving functional application tasks of the HSS) and routing data flows within the HSS using unified interfaces (API, SPI, ODBC / JDBC, file), compatible with the XFS standards (not lower than 3.20), OPOS, OPC UA or otherwise;

- ensuring the interaction of an arbitrary (finite) number of PAK peripherals of various types and manufacturers based on the use of current standardized methods for distributing data in the system, a modern information protection and coding system, providing the final functional applications with the necessary API and SPI interfaces for organizing the control of PAK peripherals ;

- ensuring the protection of information within the internal structure of the PAK with the possibility of creating a single consistent security policy, implemented by means of protection tools built into the Linux-like OS PAK, as well as OSPO tools;

- ensuring the functioning of the PAK as a whole by means of a central computer (embedded PC), implemented on one of the listed platforms - x86, ARM, MIPS, RISC-V, Baikal, Elbrus with 32 or 64-bit architectures.

- storage of configuration and working (current) information about peripheral devices of the PAK in a single data warehouse of the OSPO, accessible through the ODBC / JDBC / file interface and controlled by the means of the OSPO PAK,

- organization of access to a single repository of configuration and operating information of OSPO based on a programming interface compatible with ODBC / JDBC / file, implementation of additional measures to close data transmission channels using specialized means of cryptographic information protection from the HSC, as well as possible information leakage channels.

It should be specially noted that, although some actions of the method according to the present invention are organizational in nature, however, such operations as installation of general system software (OSPS) on a central computing facility, reconfiguring interfaces and creating a local storage of configuration information are actions on material objects using material resources. Those. the claimed method cannot be considered a program as such. The method relates, first of all, to purely material entities, such as the various mentioned peripheral devices from the PAK, namely, to control these entities from the side of a purely material object, which is the central computer. Often it is a specialized embedded personal computer equipped with a Linux-like operating system and controlled by the user. In addition, the implementation of such an integration method provides unified control of various types of peripheral devices and their different sets within the UAC, which, of course, is a technical result. And since in the current level of technology no sources have been identified describing such a method, and no sources have been identified, information from which together could make up such a method, the present invention satisfies the conditions of novelty and inventive step.

Examples of options for implementing the HAC in different industries have been described with links to specific software components and features. Other embodiments of the invention may include different or different standards and software components that provide the required functionality.

New PAK according to the present invention will be able to quickly solve the aforementioned stated problems, eliminate the difficulties that exist in the design of various devices on Russian-made platforms (Elbrus, Baikal, etc.), as well as using domestic Linux-like OS (Alt, AstraLinux, ROSA, MS VS, etc.), solve the problems and achieve the required results described above.

In the description above, some of the terms and definitions have been used for brevity, clarity, understanding and are intended for broad interpretation. In addition, the descriptions and illustrations are given by way of example only, and the invention itself is not limited to the details shown and described. In the following claims, any feature described as a means for performing a function is to be construed as encompassing any means known to those skilled in the art to accomplish that function, and is not limited to the specific means shown in the foregoing description or their simple equivalents. The features and principles of the invention, the way in which it is created and used, the advantages and useful achieved technical results are described; new and useful structures, devices, elements, interfaces, parts, combinations, systems, equipment elements, operations, procedures, processes and relationships are set forth in the appended claims.

In this description, the present invention is disclosed through several examples of its possible implementation in the implementation of remote financial self-service devices (ATM), merchant payment terminals (POS) or special industrial devices operating in the paradigm of Industrie 4.0. However, these examples are illustrative only and not limiting, and the scope of the present invention is determined by the appended claims in view of any possible equivalents.

Claims (26)

1. A method of integrating peripheral devices as part of a software and hardware complex that includes at least one peripheral device with a Linux-like operating system (OS) driver connected to a central computing facility that operates on one of the listed hardware platforms - x86 ( Intel, AMD), ARM, MIPS, Baikal, Elbrus, OpenPower, RISC-V and is equipped with a Linux-like operating system (OS), and in the context of this OS, at least one final application of this computing installation functions, which consists in the fact that : - on the central computer installation, the system-wide software of the middle layer (OSPO) is installed to obtain a single secure highway of information exchange between all arbitrary peripheral devices of the software and hardware complex connected to the specified computing installation; - provide for each peripheral device of the software and hardware complex uniform unified means of information exchange with the central computing unit of the software and hardware complex, realizing the physical connectivity of the mentioned peripheral devices within the mentioned protected information exchange highway through the serial interface of peripheral devices created by the said OSPO (SPI - Serial Peripheral Interface); - provide guaranteed secure interaction between the end applications installed on the said computing installation of the software and hardware complex through the mentioned means of information exchange by means of automatic interaction of each said end application operating in the context of the OS with the OSPO installed through the application programming interface created by the mentioned OSPO (API - Application Programming Interface); create a secure storage of configuration and operating data on the said computing facility using the means of the said OS using the ODBC (Open Database Connectivity) / JDBC (Java Database Connectivity) database access programming interface or saving to a file; save in said storage of said computing installation configuration settings and current states of peripheral devices of the software and hardware complex necessary for the operation of the final applications on it; provide guaranteed secure control of the mentioned peripheral devices through the end applications installed on the said computer installation of the software and hardware complex, provided by the mentioned means of information exchange of the OSPO. 2. The method according to claim 1, in which: - the mentioned system-wide software (OSPO) is formed by adding the mentioned operating system with a basic set of peripheral interfaces and protocols (COM, USB) intended for connecting peripheral devices from different manufacturers, as well as a set of system calls and functions to ensure the exchange of application-level data (API) ; - form a single protected information space of the mentioned software and hardware complex by streamlining information exchange between the mentioned end applications by providing intermediate reassignment of information flows, automatic conversion of extracted data formats for their uniform presentation in the interests of joint functioning of the mentioned end applications and peripherals of the software and hardware complex ; - provide a uniform implementation of the system for presenting and transmitting data within the framework of the mentioned software and hardware complex, including in conditions of pronounced heterogeneity of the software and hardware implementations of the mentioned peripheral devices of the software and hardware complex; save in said storage of said computing installation configuration settings and current states of all peripheral devices of the software and hardware complex; - carry out guaranteed processing of uniform data, regardless of the features of the functioning of the mentioned end applications of the software and hardware complex on the said computer installation of the software and hardware complex. 3. The method according to claim 1, wherein: - the mentioned interaction of the end applications of the software and hardware complex is carried out by reconfiguring the interfaces of each of the end applications for synchronous / asynchronous data exchange with other end applications by redirecting information flows between end applications through the corresponding connections provided by the means (API) of the said OSO; - the mentioned reconfiguration of the interfaces of end applications in this Linux-like operating system is carried out by redirecting information flows between end applications through the corresponding functions and calls using PIPE or Socket technologies, implemented by means (API). 4. The method according to claim 1, in which: - said add-on of a Linux-like operating system with a basic set of peripheral interfaces and protocols is implemented by reconfiguring the resources of the said operating system to unified means of providing information exchange with peripheral devices from the said OSPO; - provide a guaranteed possibility of extracting heterogeneous data from the peripheral devices of the software and hardware complex, functioning both in the context of the said OSPO and in the context of the mentioned Linux-like operating system of the said software and hardware complex; provide storage in said storage of said computing installation of configuration settings and current states of all peripheral devices of the software and hardware complex in order to ensure their control by means of end applications of the software and hardware complex; provide a guaranteed possibility of transparent control of the mentioned peripheral devices of the software and hardware complex, functioning both in the context of the said OSPS and in the context of the mentioned Linux-like operating system of the said software and hardware complex, by means of the said software and hardware complex of end applications installed on the central computer installation; implement compatibility with XFS (eXtensions for Financial Services not lower than 3.20), OPOS (OLE for Retail POS) and OPC UA (Open Platform Communications Unified Architecture) standards. 5. The method according to claim 1, in which further the integration of the final software and hardware complex begins with the installation in the software and hardware complex of a central computer (embedded PC) implemented on one of the listed platforms - x86, ARM, MIPS, RISC-V, Baikal , Elbrus with 32- or 64-bit architectures. 6. The method according to claim. 1, in which the peripheral devices are selected from the group including at least: screens (monitors), printers, scanners, card readers, biometric control devices, cameras, dispensers, recorders, uninterruptible power supply devices, network devices. 7. The method according to claim 1, in which the mentioned subsequent manipulations (connections) with peripheral devices from the group are performed for further integration of the final software and hardware complex, including: a case, a screen (monitor), a central computer, a network device, an uninterruptible device power supply, a set of other necessary peripheral equipment. 8. The method according to claim 1, in which further, to complete the integration of the final software and hardware complex, the installation and configuration of the Linux-like OS, the storage system for the configurations of the software and hardware complex, as well as the mentioned end applications and general system software (OSPO) are performed.

Images